I’ve just made the shift from Wavelab to Cubase for my audio processing work mastering projects.
The reason for the shift is that I just bought the Nektar cs12, and it comes with integration with cubase, but not wavelab.
However, today I noticed a strange behaviour. I was mastering an album, and upon rendering I noticed the start of some songs were cut by quite a few illiseconds. (I didn’t check how many)
In a few songs this was enough to cut of the first transient of a track as the mixer has sendt me the songs without any lead-in.
I figure this will be due to using high latency eq plugin such as the fabfilter q4 in linear phase on highest quality.
whats the best way to deal with this?
I compensated by moving all files a couple of bars and exporting them from a bar or two before the file, but surely there is some way of cubase compensating for this during rendering?
But that will disable plugins with higher latency. I don’t see how that is useful, as the sound will change as a consequence.
Cubase will compensate for latency of plugins just fine, except in cases maybe where a plugin reports a wrong latency. I cannot say whether that is the case here, but if a plugin reported a higher latency than it actually used, it might explain the results here. This could be tested by disabling the plugin one by one and re-exporting.
I don’t think there is anything Cubase can do about it, and the workaround would be to leave a little room around the audio event, as OP did.
@frodebass I don’t know how you organized your project, but you could e.g. create a cycle marker for each file, and make it just a little bit bigger than the event itself. If you name those markers, you can also do the export by cycle markers and have each file named by the cycle marker.
