Cakewalk export window... milliseconds or samples ?

[Sheens]

Just wondering if with export you can select milliseconds buffersize.....or is it samples ?

If it's samles...-> awesome, but if it IS milliseconds....who on earth wants to export with 200 ms buffer ?

Edited December 3, 2023 by Sheens

[David Baay]

As the dropdown header indicates, it's milliseconds, though it should technically be "(ms)" instead of "(MS)".

Since latency doesn't matter, offline rendering allows using much larger buffer sizes which may be more efficient, and thus faster, for some types of processing. I've had my default at 20 for a long time just to avoid issues that some plugins have when rendering offline at very low buffer sizes. The only caveat is that larger buffer sizes use more RAM which could be an issue in a project with tons of plugins and tracks (e.g. orchestral scores) at 200ms, but probably not so much anymore with most serious DAWs having upwards of 32GB these days.

 

[Sheens]

David, I think you want to keep latency as low as possible (not so much while mixing but on export).

Anyway, thanks for confirming it's milliseconds !

[David Baay]

13 hours ago, Sheens said:

David, I think you want to keep latency as low as possible (not so much while mixing but on export).

Latency is strictly a realtime phenomenon; it's not applicable to non-realtime "offline" rendering to file by bounce or export.

[Sheens]

Edited December 4, 2023 by Sheens

[David Baay]

The only time I have seen that is with audio rendered from a Bitbridged 32-bit synth plugin in x64 Cakewalk. This was due to a bug in Bitbridge. Otherwise it should not happen. 

[Sheens]

Thanks David, will choose 'playback size' just to be shure  

Edited December 4, 2023 by Sheens