SirWillyDS12

Select multiple tracks holding down "Ctrl"... Continue to hold down "Ctrl" and right click in the FX Rack and select "Delete All"... Repeat for Busses...

You're very welcome and glad that worked out for you... On a side note... There are a couple of ways to check the channel info of the MIDI note events in your MIDI tracks... Can be very helpful if you are pasting MIDI note events from another MIDI file... One, double left click on the note event in PRV... This will bring up the "Note Property" box where it will show you the MIDI channel of the note... Two, open up the "Event List" for the track... This will show you the MIDI channel for all events in the track including CC events... If your MIDI track is set to "None" Cakewalk will use the channel info in the events which was your problem with the Triton VSTi... With a track set to None you can control more than one MIDI channel of a multi channel VSTi or hardware synth from the same MIDI track... If you select a MIDI channel for the MIDI track Cakewalk will over ride the channel info in the MIDI events and use the channel you select...

Not sure if Audio - Sync and Caching, File System would help your problem or not... The page says "Cakewalk will usually perform best with all caching disabled, which is the default setting." but it might be worth a try... It also says this "if you are playing a large file, and using maximum latency, a too-small I/O buffer size may cause dropouts or crashes. Try increasing the buffer size by blocks of 128."

Are you recording Audio or MIDI? Or both? Cakewalk would be recording right up until the time you press the space bar to stop... So how do you "stop the recording without finishing the recording"?

On top of what David said Cakewalk does have the ability to change the tempo by one of four different curves from one tempo to the other... Jump, Linear, Slow Curve or Fast Curve... All four will give a different result... Jump will change the tempo immediately when it gets to the new tempo in the map... Linear will change it in a linear fashion from one tempo to the next on the tempo time line... And the "Curves" will do just what they are from one tempo mark to the next...

If you haven't figured this out in three years on your own system how do you expect anyone else to when the only info you give is that you stop recording by pressing the space bar? And if you don't really care why should anyone else? If you can't stand it any more perhaps you should take the time to try and diagnose the problem and provide more details about your system and setup with Cakewalk if you wish to receive any help from others...

Pretty sure you need to select a MIDI channel for the Triton vst... The midi clips that you are "pasting" have midi channel information in them and most likely you do not have an instrument on that channel in the Triton vst and that channel is different than the channel info of the note events you inserted with the tool... The Roland JV 1080 vst will respond to any midi channel info so it will play the notes you inserted and the notes that you pasted even though they are on different midi channels... Open up the "Inspector" on the left hand side of the screen... Select MIDI in the track strip at the bottom of the screen, Audio is selected by default... Go up to the MIDI section just below the FX rack, the channel will be assigned to None by default (top button)... Set it to MIDI channel one as this is the channel that you put the instrument on in the Triton vst... All of your notes should play now as the MIDI track for your instrument track is now transmitting on MIDI channel 1 and the Titon vst has an instrument on channel 1... With None selected in the MIDI section of the track Cakewalk will respond to what ever midi channel info is embedded in the midi events, which could be multiple different midi channels...

Hello @Mauro Gaspa So none of these value are extremely out of hand but one thing to note is that the highest DPC routine recorded is from the DirectX Graphics Kernel which works hand in hand with your graphics card... So this was with your project playing, correct? The thing that stands out to me from this LatencyMon graph is the fairly high number of hard page faults... Something on your system seems to be looking for chunks of memory to load from disk into upper memory quite often... This can surely be a cause of program crashes if the page fault is not cleared in sufficient time... In both of your videos, Cakewalk locked up when the play cursor was on the right hand side of the monitor just before it would switch to the next screen... Not quite right at the point but never the less on that side of the screen... Perhaps around that point is a hard page fault that is not dealt with timely between Sonar and your graphics card? So if you could run LatencyMon with Sonar until it locks up and then post screen shots of the other pages in LatencyMon, "Stats, Processes, Drivers, and CPUs as well as Main" we can see more of what is going on behind the scenes on your system that Sonar doesn't like... Some other things to try as well... Does Sonar crash if you are on the Console View or does it play all they way thru? If you zoom your tracks all the way out in Track View so the track screen never refreshes during playback does Sonar crash? A few things to check in the NviDia Control Panel for your graphics card... Under 3D Settings -> Manage 3D setting -> Low Latency Mode... You may want to set this to Ultra if not already on Ultra... Assuming your setting are the same as mine since your graphics card is a different model... And under 3D Settings -> Manage 3D setting -> Power management mode... Set to Prefer maximum performance...

@Mauro Gaspa So I have had this exact same type of "Crash" with Cakewalk by Bandlab... GUI locks up/ freeze up but the song will continue to play till the end... Only way to get out of it is to kill Cakewalk with task manager... I watched both of the last two videos that you up loaded and it looks like the exact same problem I have had on Windows 11 with my Nvidia video card... I have a NviDia GeForce GT 710 graphics card... The NviDia system drivers are well known for having problems with very high DPC latency... Most likely your Nvidia card uses the same kernel driver file nviddmkm.sys and this is very likely the cause of your problem with Cakewalk locking up... I have seen DPC latencies as high as 1500 ms on my Windows 11 system using the default power management profiles from the NviDia driver... On my system I use Firewire for my Yamaha Motif XF6 and I have to use the legacy 1394 system driver for the Firewire card that I have... The legacy drive is very hardware interrupt intensive and if I'm using in on a song project it has the highest number of interrupts of any system driver during playback of a song... With any of the Windows 11 default power schemes the Windows thread schedulers assigns both my Firewire driver and NviDia graphics card driver to the same CPU core... Because it does, as soon as the NviDia driver has a very long DPC system interrupt it locks up the Cakewalk GUI but the song will continue to play till the end... For me this only happens when I'm using my Motif XF6 via Firewire so I had to "tune" my system accordingly... To find out if you may be having some hardware drive conflict problems download and install LatencyMon and run it for a while and see if your are getting unusually high DPC Latency from your Nvidia RTX4060 graphics card... Let LatencyMon run while your are running Cakewalk... Anything above about 800us is probably too high if your graphics card and your audio interface are sharing the same CPU core for interrupts... If you are getting DPC spikes up in the 10's of milliseconds from you NviDia card this is most likely what is locking up the Cakewalk GUI... By doing a lot of System tweaks I was able to get my NviDia DCP latency to below 400us and I no longer have the issues with my Firewire card and the two drivers locking up Cakewalk...

Not that I know of but being able to block a VST is a great idea... I have a few that constantly "Dirty" a project... I shut off "number of edits" for Auto Save and only use after so many minutes because of the nasty VST's that cause the problem...

Seems that they are about 25 years late to the show... They should have done that with Windows XP... Better late than never... But they would have had to pay licensing fees to Steinberg for use of their technology, perhaps they have made a deal with Yamaha for that... To me it seems that MS is just finally admitting that their Audio drivers really suck and always have for Real Time Audio... A point of interest to me in the post was this statement by Pete Brown... That is an understatement... The default Power Management Schemes in Windows 11 are all worthless... I even un-hid the "Ultimate Performance" plan and tried it on my system and can't work on a decent size mix without audio drop outs... The default "Ultimate Performance" plan Parks 15 out of the 16 cores of my CPU and only leaves both logical processors on CPU0 un-parked... The exact same is true of the "High Performance" plan... Both plans steer all hardware interrupts to CPU0 and overload it and the latency is un-godly, sometimes as much as 30 milliseconds... If I wanted a Single Core processor I would have bought one... The "Power Saver" plan actually performs the best on my PC for real time audio of all the default MS power schemes... The "Power Saver" plan, by default has all cores un-parked and I can work on the same mix with that plan that will not run without issue on either "Performance" plan... When I "Down Graded" my system to Windows 11 from Windows 10 I did a complete new install with a new hard drive and kept the Windows 10 installation completely in-tacked on its own hard drive... So the PC is now dual boot with both operating systems... The "Exact" same every thing, only difference being the operating system... I even copied over the power management scheme from Windows 10 to 11 using the Windows Power Plan Settings Explorer Utility and "could not" play the exact same mix using my Yamaha Motif XF6 by Firewire that plays completely without issue on Windows 10... I read in a post somewhere that MS change the "Thread Scheduler" in Windows 11 to accommodate the new Intel Processors and their efficiency cores, perhaps @Jim Roseberry could shine some light on that... So what I had to do with Window 11 that I didn't have to do on Windows 10 was assign my NVIDIA graphics card to it own processor core to get it out of CPU0 or CPU1... Anyone with a NVIDIA GPU running audio knows of their problem, even the gamers... I tried using MSI with the GPU but with Cakewalk running I would get the BSOD "DPC Watchdog"... I also set Interrupt Steering in the power plan to "Any unparked CPU with time delay" and a target load of 2%... I also set minimum unparked cores to %100 so Windows does not Park any cores... By doing that Windows more evenly distributes the hardware interrupts to all CPU's... So after doing all that and more tweaking I can run my Motif Firewire with no issues on Windows 11... The highest latency spikes I get are from the NVIDIA driver, sometimes around 350us but they are all on their own processor that is not used much by Windows or Cakewalk so they cause no problems...

You may also want to delete "Generic Low Latency ASIO Driver" from the Registry Key that @Sock Monkey indicated... Pretty sure that Cubase might install that one as well... And if you do not use the "Magix Low Latency 2016..." for anything get rid of it too... Just another useless "Wrapper" that will cause you grief...

The Behringer x32 does have its own dedicated ASIO driver... If you were using Cakewalk with your x32 in ASIO driver mode one very simple way to determine if the x32 ASIO driver is now causing the problem is to launch Cakewalk with the x32 powered down... Cakewalk should launch correctly with the dialog box "There are no audio devices for the current driver model on your system... ect..." After clicking that notice Cakewalk should continue to launch without issue... If it does not something other than your ASIO driver is causing the problem...

When you have the Pro Channel strip open check to see if you already have a compressor in the setup... If you do it maybe the PC76 U Type... If that compressor is in the Pro Channel right click on it and then Replace Module... The PC4K should be available to replace the PC76 compressor... If you have no compressor in the Pro Channel you should be able to just insert the PC4K...

Piano Roll view Setting the Meter and Key signatures There you go... Read up...

Yes they did, but I missed the simple key binding "D"...

There are probably more than a few ways to do this... If you have Piano Roll open in the Multi Dock you can double click on the "tab" and it will open Track View split screen with Piano Roll... You can re-size the size of either by dragging... You can use the key combination "Alt and 1" and it will open Track View... You can assign Track View to one of the "Screensets" and select Track View from the Screensets Module or the corresponding number on the keyboard (not the number pad...)... Probably many more ways to do what you want also...

Preferences ->Project ->Record ->Recording Modes... You probably have this set to "Comping" which will mute your previous "takes"... Set it to Sound on Sound... This will allow "over dubbing" with the original material recorded...

The FX Sends are ordered from top to bottom in the order of the buses in the bus strip view from left to right... Simply re-order your buses by dragging them into the order you want... In the Console View you can Alt-Click and drag them where you want them... In your screen shot you have your buses left to right... Bus Delay, Reverb bus 2, Bus Delay short... If you want them in the order of your second post change your bus order to Reverb bus 2, Bus Delay short, Bus Delay... You can re-arrange them in Console View or Track View...

So. if I just set the controller to an arbitrary number, say 50 and save the type 1 MIDI file upon reloading there is no CC event... You are correct... If I record the movement of the "knob" as automation (which is what I was doing) Cakewalk will convert that to a MIDI CC upon saving the type 1 MIDI file... When you reload the file it is either a CC91 or CC93 depending on if it is reverb or chorus... But it does not assign it back to the "knob" unless you Convert Envelop... If I inserted the TTS as an Instrument Track and record automation as an instrument track it does not record it to the knob or as a CC with or without a MIDI channel selected... Upon reloading the MIDI file the TTS MIDI Channel will be muted, strange! If I insert the TTS as a split instrument with a dedicated MIDI Channel and record Automation on one of the knobs Cakewalk WILL record it and save it as a CC... When you reload the CC will be there... So this really sounds like a long standing Cakewalk bug that may or may not have been reported in the past... Much like the arbitrary re-assigning of MIDI device bug upon loading a project if the MIDI device is not connected... Added... The same was the case for the "Volume Fader" CC7... If I just set it to a number it is not converted to a CC7 upon saving, If I record Automation it is saved as a CC7 envelop in the standard MIDI file...

Sorry, I missed that in your original post... Saving as MIDI Type 1 does "Print" the controllers from the "knobs" to the standard MIDI file... MIDI Type 0 does not... But upon reloading the file into Cakewalk, CbB does not automatically move the controllers back to the two knobs in the MIDI Strip... They do show up in the PRV and the Event List... If you right click on them in the PRV and Convert MIDI to Envelop it will move them back to the Knobs... Yes, I'm sure that all GM MIDI devices will all respond differently...

MIDI CC 91 - Reverb amount... MIDI CC 93 - Chorus amount... The Cakewalk MIDI Strip, available in the "Inspector" has dedicated control knobs for both reverb and chorus at the top of the module... So adding them to your standard GM MIDI file would not be all that hard...

Or you could use the "Sort by Type" feature and it will sort all your EQ's by EQ type... Or you could use the search feature in the Plug-in Browser...

Use Save As -> Copy all audio with project... This will create an Audio folder inside of your project folder and all your audio tracks will be stored there and the project will reference to that folder and not the Global Audio Folder... Always use the one project per folder approach, every project in it own folder... You can copy the entire Project Folder anywhere you want and the Audio folder goes with it... Audio data will never get "Lost" it will always be with the project... You can open the project from your backup drive and the project will load with the audio from the project Audio folder on the backup drive... The Cakewalk Documentation Save As dialog page is wrong, the Audio folder is just Audio and not Audio Data... Try not to use Reference from and always copy any import files to the Audio folder... I have close to 1500 projects going back over 25 years and my Global Audio Folder is completely empty... All my Audio tracks are stored in the project folder Audio folder... Many of the older projects have been on 7 or 8 different hard drives and I can open them up on my latest PC and the Audio tracks are all there, no need to play "find and seek"......

This ^^^... Also in the Kontakt, Settings -> Engine. there is check box for default volume for new instruments or volume reset, can be set at -6db or 0db, if -6db is checked (default) your instruments can revert to -6db regardless of what they were "saved" at... If I remember correctly what causes the instruments to revert to -6db is if it is set in Kontakt at -6bd and CbB or Sonar has the option Zero Controllers When Play Stops enabled... Edit -> Preferrences -> Project -> MIDI... I'm pretty sure that all the default templates have this option checked... I created my own project templates and unchecked that option on all of them... Another thing, the midi track velocity\volume control will set the volume in Kontakt... If you moved the "slider" and it is no longer set to default (101) or disable control it will change the volume of the instrument in Kontakt... I always disable the control and use the output audio of Kontakt for fine tuning volume or automation...