Noel Borthwick

Follow this thread on Win 11

Its apparently a virtual memory paging error. May be worth passing the info along to them in case they have received other reports of it.

FYI Re AMD systems https://www.tomshardware.com/news/amd-windows-11-slows-cpus-up-to-15-patch-coming

As Morten wrote there is no error. Its working as designed.

@Laurence Levin If the program is exiting on start the most likely reason is that something has corrupted your C++ redistributables. Please download the latest redists or try reinstalling Cakewalk. Does it fail to load the application itself or is it failing to load a specific project file. If you are having an issue with a specific project please make sure you are running the latest EA build which is 145 and retry it.

This is a Roland driver bug. Drivers are supposed to handle abnormal termination properly. You have to power cycle the device after a crash.

The link in the main thread has been updated to Build 145. Thanks to Kim Strong for his assistance tracking down this issue. Issues Resolved in Build 145: S-Gear 2 VST3 plugin crashes on some systems when inserted

In every release of Cakewalk by BandLab we include a link to "Rollback installer" along with its product release notes. All historic product release information can be found here with links to the corresponding rollback installers. If you encounter a problem after a new release, you can try and rule out whether the problem is specific to that release by using a rollback installer. Running a rollback installer will revert the installed version to the last publicly released version before the installed version of Cakewalk you are running. NOTES Please note that the rollback installers are specific to each release. i.e. you cannot use a rollback installer downloaded for an earlier release on the latest release because it will fail to run. If you need to, you can also go back to past versions by downloading and running rollback installers in succession. To get back to the latest release after running a rollback installer go to Help | check for updates and reinstall the latest update. PS: We only support the most current version of the application. Since Cakewalk is always evolving, older versions may contain bugs and certain features may not function properly due to back end changes. Always work with the most current version of the application and directly report any problems to Cakewalk should you find any.

Another build posted today with the following fixes. Link in main post. Issues Resolved in Build 144: MP3 options dialog does not show recalled task settings Export as MIDI exporting whole project if selection at time zero Intermittent crash when closing Arranger Section Context Menu Windows notification sound when opening export audio dialog in some projects

@Jean Corivo thanks for the update. I'm glad its ok now but I'm not sure what could have caused that. Perhaps it was related to the fact that the bounce was doing unnecessary resampling if the project sample rate was different from the default sample rate...

That isn't a dropout. The plugin is failing to load. Either its not installed properly or its a plugin authorization issue. You would have to follow up with iZotope on that if the problem persists.

We're pleased to announce Early Access for Update 1 of 2021.09! This release includes a small handful of user reported stability issues. If you have encountered any of these issues, please check out this release and and confirm that your issue is resolved before we release the official public version. Please note that Early Access installers are update installers, which only update from a specific version. To install the 2021.09 Update 1 Early Access build, you must be on the latest public release of 2021.09. Download Cakewalk 2021.09 Update 1 EA installer If you haven't already done so, please read about the Early Access Program before participating. Please keep responses specific to problems or comments on this release. Unrelated bugs or feature requests should be posted in other threads or the feature request channel. Thanks again for your participation! The Bakers Issues Resolved in Build 145: S-Gear 2 VST3 plugin crashes when inserted Issues Resolved in Build 144: MP3 options dialog does not show recalled task settings Export as MIDI exporting whole project if selection at time zero Intermittent crash when closing Arranger Section Context Menu Windows notification sound when opening export audio dialog in some projects Issues Resolved in Build 143: Bounce to track dialog forces render sample rate to 44100 always Export audio dialog uses default project sample rate instead of actual project sample rate Bounce to Tracks should always use project sample rate to prevent unnecessary sample rate conversion Large bounce buffer sizes cause flatline audio when exporting or bouncing clips with 96K or higher sample rates Bounce to clips unexpectedly uses bounce buffer size from export audio dialog Exporting audio with plugins on a surround bus can hang the export while flushing plugin buffers In rare cases certain plugins could hang export while flushing plugin buffers Export task fails with no meaningful message if drive or path is invalid Export as MIDI File should not show audio track warning message Warn if duplicate filenames in export task queue Changes to Notes tab are not reflected in the ID3 MP3 Options dialog until CbB restart. MP3 Options dialog should default to 256 kbps Export with External encoder was not functional Expand width of file overwrite prompt when exporting multiple files and make the list scrollable

I think you are overanalyzing this. This is not something that requires a ton of documentation for something beyond what's already there - which is it provides higher resolution for mixes. The documentation is for users not computer scientists For those who are curious for more detail there are the white papers referenced or the web.

Not at all. Bit depth and sample rate are unrelated.

I was referring to the File name field not the new dialog itself. Sorry we don't plan on having two different dialogs in place. Its not practical.

Nothing forces you to use this. Change the file name to what you want it to be. It defaults to a tag thats all. Please read the release notes or follow the video tutorial posted in this thread to understand how to use the new features.

@Ty Ener-Chi please post in the main feedback thread and provide a project that has a repro. Its impossible to diagnose without knowing exactly what you are doing. Have you tried rolling back to the prior release to check if its a new issue or not?

Performance is mentioned primarily to explain that using double precision doesn’t mean you will get half the CPU performance because there are secondary optimizations in modern processors. The main benefit is the higher precision. Compare these two formats: 32 bit float https://en.m.wikipedia.org/wiki/Single-precision_floating-point_format Sign bit: 1 bit Exponent width: 8 bits Significand precision: 24 bits (23 explicitly stored) And 64 bit: https://en.m.wikipedia.org/wiki/Double-precision_floating-point_format Sign bit: 1 bit Exponent: 11 bits Significand precision: 53 bits (52 explicitly stored) In practical terms, the second has much more than 24 bit resolution so you could literally go through a huge number of gainstages, bounces or mixes and the noise floor would be inaudible. With modern CPU’s why not use the best resolution.

That is not a net performance gain in general. It Is talking about specific mix operations in the engine. And the avx thing is talking about gains with avx processing rather than double precision vs single precision. The only reason I quoted that paper was because modern processors have abilities to handle 64 bit operations more efficiently. Processing twice the amount of data for streaming is always going to have a cost.

I don't think we ever claimed a net performance gain. It's about precision and noise.

The 64 bit engine can be turned on in preferences or in exporr. The first is applied while playing the second while rendering. They both affect the engine by telling out to use 64 bit float when mixing and streaming. Bit depth only affects the file capture at the end of the signal chain when exporting or bouncing.

Modern as in circa 2005 lol. This is not new technology - we led with it a long time ago. I’m surprised this thread is even being discussed in 2021, Using 64 bit however requires twice the buffer size so it has a higher memory hit and takes a bit more cpu to handle the extra data being streamed. Also even today there are a few plugins that don’t handle it properly so there are a few downsides. An example of 64 bit gains is discussed in another white paper that we published with Intel several years ago. http://www.noelborthwick.com/2011/07/14/utilizing-intel-avx-with-cakewalk-sonar-x1/

These links should help. http://forum.cakewalk.com/64bit-Audio-engine-vs-double-precision-engine-and-a-dithering-question-Noel-please-m3804976.aspx https://www.cakewalk.com/Press/Release/1047/White-Paper-Benifits-of-x64-for-Audio-Workstations Essentially the 64 bit engine uses double precision floating point numbers from end to end assuming that plugins support it. The main advantage of 64 bit computing is that its very tolerant of errors that build up over thousands or millions of computations and has a massive dynamic range. You can literally do multiple mixing gainstages that clip > 0dB or go to very low levels and then scale back up with no audible errors creeping in. In fact the original white paper had a test project that did something like that. Not only is it advantageous for mixing, it is actually more efficient for modern CPUs to process. As far as the export settings go, its simply a way to control whether you want the export to use the 64 bit engine processing or not. I.e you can have it disabled in preferences and enabled in the export or vice versa, (If its disabled in export it will NOT use 64 bit processing even if it’s ON in preferences) The delivery file format is independent of the engine precision. You can choose to export to 16, 24, 32 or 64 bits. Obviously 64 bits will retain the full resolution and integer formats will be dithered down. There are still advantages to mixing in 64 bit even if rendering to 16 bit because the conversion happens at the last stage. Whether you will hear a difference with 64 bit really depends on the processing in the project. In simpler projects without a ton of buses and processing its unlikely that it would be audible.

@Adam can you elaborate further what specifically is broken? If you can attach a simple test project or give a step by step recipe it would help reproduce the issue here. I’m sure it is something minor to fix if its broken. Preferably please post any bugs or regressions to the main 2021.09 feedback thread since we’re tracking that more closely.

It's not. Most encoders write audio directly without first being written to wav. Only the external encoder does that