Bristol_Jonesey

Just to elaborate a bit, you should be setting your gains according to the signal level coming into Sonar. Adjust each track so that the highest peak on the track is between -9dB & -12dB. This is with your track fader set at 0dB. (This process is known as gain staging) Once this is done, don't move the gain control again! If you do, you'll be affecting the amount of signal being "seen" by your compressors & other dynamic type plugins, so if their input level changes, you'll have to revisit all your threshold settings, which in turn could mean you have to change the ratio & makeup gain. Set and forget.

Very few systems outside of the DAW world will play at 32 bit. But it makes sense to export at the highest rate possible if you intend to do further processing on the track and import it back into Cakewalk.

I think this is exactly as designed. If you put a send to another track, you're essentially sending a copy of the original across - there is nothing in the routing which would mute the send.

It's a registry entry Computer\HKEY_CURRENT_USER\Software\Cakewalk Music Software\Cakewalk\Core\Presets\{FDEA90C0-FCFC-11CF-953F-00AA00A76449}

To create and remove a symbolic link named MyFolder from the root directory to the \Users\User1\Documents directory, and a hard link named Myfile.file to the example.file file located within the directory, type: mklink /d \MyFolder \Users\User1\Documents mklink /h \MyFile.file \User1\Documents\example.file rd \MyFolder del \MyFile.file

What do you mean? Sorry. Should have thought about that a bit.

Hold down the Ctrl key while dragging

The Track Control Manager is here

Always try and get DP working in standalone mode before attempting to load it into Cakewalk. You might also need to run the installer "as Administrator" I believe the latest version was 1.5.5.16

Is your main recording drive an SSD?

I have a few monster projects. Four or five full orchestra mockups with 135 tracks each, a couple of album projects which run to nearly 2 hours. Admittedly, plugin counts on these is pretty low, but saving is nearly instantaneous. I have many other projects of 60/70 tracks with multiple busses & plugins and save times are similar. Like @Glenn Stanton said above - where are the files stored on your system(s)

If saving is as slow as you say, using either method, then this indicates to me there is something fundamentally wrong with your system.

Another thing to try - delete the contents of your picture cache. Let the program re-compute the waveforms next time the project is loaded. Obviously only delete the cache when Sonar is not running.

Here, bottom right

That's only partially true. CbB did receive a maintenance update quite recently. There simply will no longer be any new feature updates.

Not seeing it here either. All knobs behave smoothly

Try bouncing the clip to itself

I hate telling a seasoned user like yourself this, but until you read the manual you will struggle. I neglected to do this and struggled for weeks until I downloaded the manual and it's pretty easy once you understand the workflow.

FWIW, I tested it running Sonar 2024.08 Build 019 on a Win 11 laptop

Nope. The Browser stays exactly where it was.

Yes the Browser doesn't appear to expose itself to Workspaces. If you switch Screensets, say from 1 to 2, hitting the relevant number on your qwerty keyboard will load up the saved version. Apart from that there's not a lot I can suggest

1 - Make sure Workspaces is set to None, or save the current one when you're happy with it 2 - Make sure the current Screenset isn't locked.

Have you tried doing a real time audible export?

Do you mean there's a glitch in the export or in the project after exporting?