Mizuki Tachibana

1 hour ago, David Baay said:

If you draw tempo changes, it's easy to end up with more tempo changes than necessary. I recommend drawing tempo changes with snap enabled at a resolution that matches the interval between notes in the region. Your issue may also be specific to Kontakt or the specific patches you're using. You might try it with different instrument in a copy of the project just to compare.

You might also try setting a non-zero BounceBufSizeMsec= value in  AUD.INI (Preferences > Audio > Config File). By default (BounceBufSizeMsec=0), Cakewalk uses the real-time ASIO buffer size to process audio offline. Setting a higher value in AUD.INI, can improve rendering performance.  I have mine set to 20. Values up to 200 are reasonable.

 

 

Thank you for your advice! I did not solve it.... but I have found a few things.
Fast Bounce works normally when KONTAKT6's "External Sync" is off. Fast Bounce also works normally even if KONTAKT5's External Sync is on with the same project file.
Perhaps, I think that KONTAKT6 on the latest version of CbB (with lots of tempo change data) is the cause of the bug.

20 minutes ago, reginaldStjohn said:

Are you saying the bug is that it exports slowly or is there some other issue?  Do you have audio files that are being stretched with the tempo changes?

Yes, it exports slowly. MIDI-only project file without audio files. I used KONTAKT, but tempo-sync audio data was not included.

Exporting to Wave with lots of tempo data will cause extremely slow bug. This bug does not occur when there is no tempo change, or when Fast Bounce is off.
Does anyone have the same bug?

Cakewalk by BandLab version:2019.11 (Build 63, 64bit)
VSTi:KONTAKT 6.2.1
OS:Windows 7 Professional 64bit latest
Audio Interface:M-Audio Fast Track C600 (ASIO)
CPU:Core i7 3770
Memory:32GB
Graphic:Radeon RX 570

Mizuki