I know this issue has been discussed several times, e.g.
sofar it seems that the origin of the problems is not 100% identified, otherwise the issue wouldn’t come up again and again. But it appears more than regularly with external instruments which is very annoying. I assume and am pretty sure, that this CPU which it refers to suggests more an ASIO CPU problem than a real CPU one. Anyway…
I’d like to collect once again all the knowledge concerning this issue in this Post to help others and perhaps myself if someone comes up with some good new know-how.
Insofar I noticed several things when this happens:
- during the export of one (external instrument) track, all other tracks are playing too. This is silly, specially as they haven’t interlaced routings. It would be CPU saving to just play the track which is exported (or all tracks connected to…) this wouldn’t be hard to program
- It seems to happen often with external instruments (though also VSTi’s provoke that issue… but the freezing option’s easier there). But arguing with external instruments: if it would be like that, then Cubase would have a severe programming failure (IMHO). If you can’t export external instruments, why include them? (Ok, problem is not always appearing)
- why don’t I get a CPU overload exception if I reroute the audio-signal from one channel to a new audio-channel and record it there or when I just listen to the track? this is supposedly the same or even more CPU-consuming than just “Export” or Bounce it.
Until now I have found several solution-suggestions:
- increase buffer size
- freeze all possible tracks
- reroute the audio signal to a new audio track and record it there (but with delay which needs to be compensated manually)
but as far as I noticed, these are just workarounds for the real problem… Buffer Size doesn’t always help, much less with external instruments, freeze is not possible on all chanels and doesn’t help if you can’t freeze the channel you like to freeze . Only the rerouting solution seems the most viable one, with the negative side-effect of needing to manually compensate the delay…
Again I’d like to bring up that issue, becuase I think it is highly annoying to have sooooo much CPU overload exceptions to create Audio-signals frm external instruments. Why the function if the use/export is not supported? Or in other words: If I can listen to the track or reroute the audio signal and record it there without a CPU overload exception, why do I get one during export? An additional write to HD shouldn’t be an ASIO or CPU issue…
Is there any more know-how or possible solutions I forgot to mention?