Bounce All limitations?

[Brad B]

Hi All,

I seem to be unable to record some jamming to disk (WAV) properly. I open up the sequencer and use the copy from combi option and load in the Orchestra & Timpani EXs3 (one my fav ones - its awesome!) with all TFX and MFX etc.

I then record whatever I am playing with the sequencer and when I play back it sounds perfect - however when I now want to use the bounce all function it does save the recording to disk into WAV format but it sounds incomplete (like some some channels are missing and some effects are screwing things up).

Am I going about this the wrong way? or are there any limitations/considerations pertaining the use of the bounce all function? Ive always used this way to get something over to WAV and never really bumped into this before ...

Regards,

Brad

[Dany]

Hello

I just recently made the experience, that if i tried to bounce alltracks to a WAV, the bassline had some interruptions, as if there weren't suddenly enough voices. This problem occurs only while recording, resp. bounce all tracks to WAV. I guess, that the bouncing process needs some resources which costs some voices. I had to limit some tracks concerning the voices, to be able to get the final WAV without any steeling of notes. This was quite disappointing.

Finally, after owning the OASYS for half a year, i can say, that the OASYS is the world best sounding and most complex and expressiv musical synthesizer on the planet. It is the perfect live instrument. But if you really want to do a whole production just with the OASYS, you won't succeed in the appropriate time. You will need a pen and paper to get the overview over your composition. Everything is fine, if you are working just with a loop and some KARMA.The Sequencer and the inflexible KORG User Structure, which is just the same as in Tritons or in the M3 are really based on the technology level of the 1980's. You can't for example get directly into the edit mode of a program, while in combi or seq Mode. It is just a pitty that if you try to manipulate a sound on the MS20 with the virtual knobs, while beeing in the seq or combi Mode, you won't succeed, because it is NOT possible, again because of the antiquated old KORG System based on the M1. My Yamaha SY77 was able to do that back in the year 1989 !!! If you want to change the drumprograms, you have to go into the global mode, tha same if you want to change the effect routings of some individual drum sounds. Finally if you want to program a good drumtrack, for a long and complex composition, you will begin to hate the OASYS and start dreaming of the ARX Drum Board for the Roland Fantom G. But didn't we buy the OASYS because of the beautiful integrated system.
The OASYS is in every aspect the best Live synth on the world, but one of the worst Workstations on the market due to the antiquated sequencer and the inflexible Structur of the KORG User System. And there are not enough banks to store your programs, which is annoying considering the fact, that a whole bank can either hold just EXi Pprograms ore HD1 Programs. OASYS-Conclusion: Best Synth on the planet, worst Workstation and most inflexible user structure concerning drum editing and storage in general...

[lcmorley]

Have you tried using the sampler. This will give you a stereo wav file as you require. Or at least that is how I have always done it.

Remember, there is more than one way to skin a cat with the Oasys.

[Brad B]

Hi there,

thanks for the replies

@Dany: I would expect that if I can run off the sequencer (playback) without any problems that recording the same playback from L/R shouldnt really require any more resources other than writing to disk.

@Icmorley: Yeah I have also tried the sampling way; same result unfortunately ...

Any other ideas? Anyone tried the same thing with the EXs3 combi and have the same problem?

Brad

[Mike Conway]

I used KARMA and recorded this Combi to the sequencer, then successfully bounced it to a .wav file, with seemingly no loss. I'm positive our playing (how many notes, etc.) differs greatly.

Combis are so layered that they use up a lot of poly and FX. What Dany says, makes sense. I could see that happening with maxed out resources.

Have you tried recording to your Audio Tracks? Set Track 1 & 2 to stereo and the inputs to L/R. Turn Metronome level to zero, on Preferences page. You can then delete all the MIDI tracks and bounce just the Audio tracks to .wav.

[lcmorley]

Stupid question, but are you still running the demo version of the ex3? as this would cause loss of sound.

[Brad B]

Yeah - and this Combi especially is totally packed with programs/effects layers etc. But still dont understand the difference between playing back the sequence (succesfully) and recording it to WAV (unsuccesfully) ...

I will give your tips a go when I get the chance

Thx

Brad

[Brad B]

Nah - fully authored EXs3 no in/out fading stuff here

[EJ2]

Do you have the latest OS update installed?

[Dany]

Hi again Brad

Concerning your unclarity: "But still dont understand the difference between playing back the sequence (succesfully) and recording it to WAV (unsuccesfully) ..."

If you are just playing back the sequencer the Computer-Processor of the OASYS will obviously use less resources than if you are playing back the sequencer and at the same time bouncing, resp. sampling all tracks into WAV. Therefore if you are bouncing a sequence which is already at the voice number and effect resource limit, the last step, the "bounce to all tracks" process will overload the capacity of the OASYS and some voices and possibly some effects, will temporarely disappear. But you may have another problem anyway. But if your sequence is already pushing the OASYS to its voice number limits, than you are probably experinecing the same thing as myself and Mike Conway, whlie trying to bounce all tracks to a WAV...

(I am praying that the NAMM 2009 will surprise us with a seq update for the OASYS...)


[/quote]

[Brad B]

Mike; lots of thanks - your tip worked like a charm . Setting up Audio tracks through the auto HDR setup menu "Bounce Audio Tracks" preps things properly and subsequently Bounce All Tracks works like you'd expect.

Still seems a bit weird though that this DOES work; you'd think the OASYS would be strained even more this way (since it has to do more than the direct bounce all tracks method).

Thanks for all the responses;

@Dany: I understand the system will need to do more when recording; but if you think about it ... HDR limiting polyphony & effects ... To be honest I have enough confidence that KORG have made sure that you can use full polyphony and effects and also use HDR to capture it without any CPU resource problems. I'm sure its just got to do with certain settings etc - or the way the Bounce All is implemented - the fact that it does it fine recording it through Mike's way only emphasizes this I'm guessing.

Regards,

Brad

PS: I still am running 1.3.0 (bit affraid of upgrading - its all working fine for me now ... don't try and fix something that aint .... )

[Dany]

Hi Brad

The experience of me, you and Mike seems to proof that the "bounce all tracks to CD"-Function really eats up some voices if the whole original sequence already pushes the OASYS to its limits. Whatever the technical reason might be.

To avoid this annoying problem in the future (because i push my tracks very often to the OASYS limits) , i will follow the advise of Mike, which seemed to work in consideration of your own experience.

So thanks to you and Mike for having solved my problem parenthetical...

Greetings from Zuerich, Switzerland

[Charlie]

Hm - very strange indeed. I used to bounce all tracks to disk quite often and recorded complete songs (using multiple tracks of audio for vox etc.) and I never lost any voices ...

I remember that in a previous version bouncing all tracks to disk did not work properly, that is, it didn't work at all. But Korg fixed this bug quickly. Since then I didn't experience any troubles with this function. But I do not use it as often as I used to ...