Noel Borthwick

@Heinz Hupfer you said it worked before - hence my response. We'll fix the documentation, thanks. Effects settings should be saved in track templates. Those do not have anything to do with mix scenes. >>Also the Drag and drop mixscenes into a new project doesn't recall ProChannel settings like EQ or Comp! Keep in mind that mix scenes are tied to the project that they originated from. If you drag and drop into a project that was not derived from the same project there is no guarantee that the settings will be recalled because the track ID's may be different. However if you drag a scene into a project that was saved from a version of the original project it should recall fine. In the future we may allow importing scenes from other projects and allowing you to match settings from tracks and buses.

It should only stay if your mouse is over the toast message. If you move the mouse away it should disappear.

@Milton Sica I sent you a message with instructions to troubleshoot further.

@siordanescu just PM'ed you to try and get some more information.

@siordanescu did you retest this just now?

@tecknot Can you describe what problem you are running into with the current performance module? It supports displaying up to 32 cores.

@Heinz Hupfer we investigated this. I think you may be confusing project templates with track templates. Mix scenes do indeed save properly with project templates. Track templates on the other hand do not save mix scenes.

This isn't a problem with Cakewalk. Its poorly written drivers that don't flush their state on abnormal termination. Cakewalk already attempts to shut down drivers whenever an exception is detected. Not all crashes can be caught by the app so this is something that has to be handled by drivers themselves. Most well behaved drivers can survive the program being force closed from Task Manager as well.

The hotfix has been officially released now so you can get it through BandLab assistant if you don't already have it. The build is 25.11.0.63

Thats great. If they need any assistance from us let them know they can contact me.

In newer builds you can directly drop multiple wave files into take lanes and it will create new take lanes as necessary.

Classic symptom of a plugin that has internally crashed and is now generating denormals or bad floating point data.

Tip for the future. Open the project in safe mode by pressing Shift while opening. Then click Yes to All. The project will open intact with all plugins but with any open plugin windows will be closed.

@Milton Sica try setting the StopEngineOnPanelOpen value to true in preferences / audio / configuration file and see if that addresses it.

@David Baay in Preferences | Audio | Audio configuration you can reset the configuration to defaults. This is the preferred way to set the audio configuration to factory defaults. It will keep a backup copy of your current settings should you need to go back as well. No need for manually locating the ini file.

Great to hear that we were able to help resolve this issue for you. A systematic process of elimination is the best remedy when you have system specific issues like this because it can be easy to draw the wrong conclusions. If you could contact the plugin vendors you were in touch with who claimed it was a Cakewalk bug that would be great, so that they don't continue to spread misinformation to other users We'll also try and put together a KB of known third party problems and troubleshooting techniques that might assist others. Now go make some music

For the record this is a 100% third party problem that affects other DAW's on affected systems, not just Cakewalk. Future note to other plugin developers who are quick to blame Cakewalk @AxlBrutality were you able to verify that your Cakewalk LP plugins no longer need the ini file setting to override open GL after you uninstalled Nahimic?

Most ASIO devices will auto switch to the sample rate requested by the host when you load the project, but some require you to explicitly change it via the ASIO driver control panel or via a physical switch on the audio interface. Also note that changing the value in preferences only changes the sample rate for NEW projects. i.e if you load an existing project that is already locked to a certain sample rate, changing the default sample rate value will only affect NEW projects not the currently loaded one.

That's definitely a relevant observation thanks. It's likely what is triggering opengl to do whatever it's doing to hang the Cakewalk UI.

If all you want to do is interactively slow down the clip just slip stretch the end of the clip till it's as slow as you want. Hold down the CTRL key and then drag the right edge of the clip ahead of time to lengthen the clip.

We'll investigate this - thanks.

The message typically means that the sample rate of the project file is not supported by your audio interface. Are you running ASIO or WASAPI mode? The current project sample rate is displayed under the now time. It may be as simple as switching your audio device to that sample rate in case the interface has to be externally switched.

Hi @Billy Buck you have 20 msec because you installed the original .11 release. New users going to this version will have it properly reset to 200. The reason for this flux is in all our testing 20 seemed sufficient. However a few user systems had dropped notes. There is a big internal change from SONAR (which had a bug with the MIDI buffer size interpretation) which is why we adjusted the value. In the new build for most people it should be fine at 20 or 50 but I've bumped it to 200 to cover more corner cases. Sorry for the flux. I may change the final release to reset it to 200 on first run once more.

@Dr. Failure Audio slowdown and distortion while playing is a symtom of overload where audio cannot be processed in time for the driver. You can alleviate this by raising the audio latency. Which driver mode are you using? WASAPI shared mode is the best for devices like headsets but it has an upper limit of 10 msec which might be insufficient. Try using WASAPI exclusive mode and set the audio latency slider to something like 30 msec. Of course this will cause latency so you won't be able to monitor without delay. Please get the latest hotfix since it has some improvements with WASAPI when using different input and output devices.

It may be cheaper and a lot quicker to just try a new video card. Just buy a current gen card and try it - if it doesnt work you can possibly return it.