Jump to content

Noel Borthwick

Staff
  • Posts

    4,195
  • Joined

  • Last visited

  • Days Won

    46

Everything posted by Noel Borthwick

  1. Possibly assuming he is using 32 bit plugins. I did a test rendering a large project with over a hundred tracks and a hundred plugin instances. I bounced the whole project to a new track with a buffer size of 10 msec. Then I did the same test at 350 msec. Not only did the two renders align perfectly, they null cancelled when I phase inverted. So if there is a problem is isn't in the actual bounce code.
  2. @Toy there is no difference between setting bounce buffer size or manually or changing the audio latency to a higher number and redoing the bounce. Behind the scenes it has the same effect except its not changing the driver latency. If you are seeing differences its due to the plugins in your project and out of our control. You can repeat this test by changing the playback buffer size and redoing the bounce each time with the default "PlayBack Size" option selected. i.e. Do this test: Export with bounce buffer size set to 20 Export with playback buffer size set to 20 and bounce set to Follow playback Compare the two wave files. They should be identical assuming you set the buffer size the same Another thing to try: Bypass all your plugins and do the test again. If the audio aligns then the issue is caused by one of the plugins. You can use a process of elimination to find the problem.
  3. @Helene Kolpakova Re 1 the sources are per project while export presets are global. So this isn't really possible without having a concept of per project presets which seems a bit overkill. I'm not sure I understand your workflow and why you need it to remember that state though. We could possibly consider remembering the selected sources state for the duration of the editing session but I'm not sure how useful that would be. Re 2 its already available. Go to the media browser tab and choose the "Project Audio Export Folder" preset. That should take you there automatically.
  4. Fast bounce is not related to the buffer size option directly. All it means is that Cakewalk exports as fast as it can and is not gated by realtime playback. The custom buffer size itself only applies when Realtime playback is unchecked in the 2021.09. The only change in 09 is that fast bounce is now renamed to "Render in real-time". So to do the equivalent of a fast bounce make sure render in real-time is unchecked.
  5. Please keep this thread related to the 2021,09 release specific features. For other general inquiries create new threads.
  6. >>Up to E.A.134, all "BOUNCE BUFFER SIZE" settings are invalid in ASIO. Yes this was a bug that was fixed >>-As a result of the setting being enabled in E.A.137, there are no options other than "PlayBack Size" in my plug-in. I'm not sure what you mean. In the latest release you can either use playback size or any other buffer size. If you leave it at playback size it uses the driver latency setting otherwise its whatever value you specify. As described in the release notes depending on plugins used, use conservative buffer sizes such as up to 50 msec. The only benefit to larger sizes is to speed up export time.
  7. Its impossible to understand looking at a screenshot. You will have to send the project file if this is a change in behavior and describe the steps you are taking. Most likely there is an audio routing issue in your project.
  8. @Skyline_UK There should be no decrease in bounce speed. The only new step added is to flush effects tails. Please read the release notes there is a way to disable that if necessary. In fact if you are bouncing the entire project it should be faster because we no longer duplicate the project in memory in that scenario. Also check your audio buffer size. If its set low bounces will be slower unless you use the new bounce buffer size to set it to a higher value.
  9. I think you may be confusing it with an issue that was fixed in the EA. There was a bug where in ASIO mode it was not respecting the bounce buffer size and defaulting to the playback buffer size. In the final release it will use the bounce buffer size unless it is set to "follow playback buffer". If you are using a high bounce buffer size some synths do not handle it properly so this could be what you are seeing. If so set bounce buffer to "follow playback buffer"
  10. Are the dropouts actually impacting your work or is the message and audio stopping bothering you? If so you can turn off the dropout detection here:
  11. Not seeing any issues with selection in tasks. I created multiple tasks some with entire project and some with specific selections and they all rendered properly with source category Entire Mix
  12. The bounce buffer size is global and is not saved per task. This is intentional
  13. Thank you everyone for the incredible feedback and participation this early access! 2021.09 has now been officially released. Please use the main 09 release feedback thread for any further comments.
  14. @Toythis is probably a synth specific problem. Were you exporting at a high buffer size or same as the audio latency size? Try a smaller buffer size or do a realtime bounce.
  15. Can you please try this on a different PC. There is likely something specific to how you have Cbb setup on this PC that is throwing this since we're not seeing it on multiple setups. Perhaps a video showing what you are doing might illustrate the issue better. Are you also seeing this with any project you open and export or only with specific ones?
  16. Its possible that you are running into some weird Win7 specific issue since we are unable to reproduce this here so far.
  17. Can you screenshot what you have set in Preferences | Folder Location for Export audio files?
  18. @James Argo As Morten said "Can you please post a screenshot of the entire project folder path in Windows Explorer?" This will help us understand what your full project name looks like in windows explorer.
  19. Not seeing that here. Can you send across the project file that throws this error?
  20. We tried this here and there were no issues switching driver modes. Its may be specific to your hardware. Did you try this in earlier releases? Changes should work while a project is open - there is no need to restart the app. Re WASAPI I'm not sure what devices you have on your system. Some pro audio devices don't work well with WASAPI. For example Focusrite plays poorly in WASAPI mode. This is why we default to ASIO mode when an ASIO driver is available. In any case the new driver warnings are just a suggestion to users that there are known problems with certain drivers. You can still choose to use it.
  21. Thank you for your great support and feedback so far. A final build 137 was posted (see start of thread) containing the following fixes. If you can please test this build and report back ASAP if you find any regressions. In particular, try exporting in ASIO mode and specifying a larger bounce buffer size. Please note that some plugins are unstable with larger buffer sizes (> 50 msec) Hang exporting project with arrangements containing IK Multimedia Plugins Bounce buffer size value was not respected in ASIO mode Exporting project with mono sidechain track send could cause problems flushing effects tails Exporting tracks with sidechains doesn't work if you don't make a direct track selection File Export dialog should default to Arrangements when launched from Arrangements Inspector Add new default config variables for "BounceFlushTailsMaxDurationSec" and "BounceFlushTailsThresholdDb"
  22. For activation please read this FAQ on Activation, especially the section on in-app activation.
  23. @Xel Ohhthanks for the report. We'll investigate this. Act chance you can share a link to a zipped project folder where this happens?
×
×
  • Create New...