Leandro Posted May 9, 2020 Share Posted May 9, 2020 (edited) Just as the title says... I wanted to export and this is the message I got: I was able to export successfully yesterday. The only modifications today was minor volume changes in some tracks, a plugin effect removed from one of the tracks, and some automation. The song plays fine. I just got this message when I tried to export. I restarted Cakewalk but the problem is still there when I try to export. Edited May 9, 2020 by Leandro Link to comment Share on other sites More sharing options...
Leandro Posted May 10, 2020 Author Share Posted May 10, 2020 No one knows? I was able to export by using the output bus (I get the message above when I export using Entire Mix). I unfroze a couple of tracks and when I tried to freeze back, I got the same message... Link to comment Share on other sites More sharing options...
Scott Mossman Posted June 28, 2021 Share Posted June 28, 2021 Just got the same message. Did you happen to find a fix from your issue 13 months ago? Link to comment Share on other sites More sharing options...
Noel Borthwick Posted June 28, 2021 Share Posted June 28, 2021 Do you have any mono only plugins in your project? Link to comment Share on other sites More sharing options...
Jeff Gajewski Posted January 8, 2022 Share Posted January 8, 2022 I'm having this problem, too. Is there a solution? I have a workaround in my scenario. Took me hours to isolate my problem. When I delete from the tracks all FX Chain Presets used, re-save the project, shut down the program, re-open the project, and then re-add the same FX Chain Preset, the problem goes away, and I can export. Some of the steps above may not be necessary, but this series of steps in fact resolved my issue. Link to comment Share on other sites More sharing options...
Jeff Gajewski Posted January 8, 2022 Share Posted January 8, 2022 Here is an update as the above fix I posted did not work on one occasion. Here's what I did differently: Delete the FX Chain Preset and run the export command but DO NOT complete the process. Allow Cakewalk to advance to the point where it asks you if you wish to proceed. Then click Cancel instead of OK. Add your FX Chain Preset back to the track, and export as usual. This resolved my issue. I hope this helps the Cakewalk techs to address a bug. Link to comment Share on other sites More sharing options...
Noel Borthwick Posted January 10, 2022 Share Posted January 10, 2022 Please send a link to a project file with the issue as well as the steps to reproduce it including the name of the fxchain preset Link to comment Share on other sites More sharing options...
Tone Ranger Posted December 18, 2022 Share Posted December 18, 2022 Seeing the same behavior on occasional projects on latest build (see pic below). My workaround is similar to that of Jeff Gajewski above, except I simply bypassed the FX chain preset in the FX rack. With it bypassed, I ran the Export, then un-bypassed it, and was then able to successfully run the Export again as desired (choosing in this case to overwrite the previous Export). Note that I was Exporting directly to MP3. Link to comment Share on other sites More sharing options...
Tone Ranger Posted June 4, 2023 Share Posted June 4, 2023 (edited) Bump... (edited) This is still happening here on a fairly regular basis. The workaround that I posted above is no longer successful. New workaround: Bypass FX racks with FX chain presets, save and close CbB application, reopen the app+project, un-bypass the desired FX racks, and export then works as would be expected. Of course, I save the project afterward. Note, sometimes I reflexively hit Ctrl-S (save the project) before the export and it seems to also work. Hopefully this use-case can help with debugging this annoying and persisting issue. Running (reportedly) latest version 28.11.0.21 Edited June 5, 2023 by Tone Ranger Link to comment Share on other sites More sharing options...
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now