SirWillyDS12

Not sure if you are still having these issues? Try "Running as administrator" ... BitBridge on my PC needs Admin permission... Also, it appears that perhaps Plugin Manager was running outside of SONAR X3,... If it is launched directly from PluginManager.exe it will look exactly like your screen shot... Perhaps Plugin Manager also needs Admin permission inside of SONAR X3 for you...

Thanks David, that took care of the transport issues... Thanks, that took care of the Track Strip colors... Yep, this... The font in the control bar is a bit to small for me... So, even after a restart I'm still getting "The above Audio\Midi device has been disconnected from your system" box after relaunching Sonar after closing a previous project... If I start Sonar and do not open a project and then close it, upon relaunch I don't get the Audio device disconnected... Anyone else with a MOTU interface having this problem? I do not have this issue with CbB... After every project I always complete close CbB before opening another one... My Motif VST3 does not play nice and will crash Cakewalk every time if I open two consecutive projects that it is in without completely closing Cakewalk...

So I downloaded and installed the "Backstage Pass Setup"... A few issue right out of the gate... First, every time I start the new Sonar I get the dialog box that my Audio interface has been disconnected from my system, it hasn't been... So I have to click No to keep the current settings... Second, the plugin manager would not open but would show up in task manager... End task and try again, same thing, but now Sonar disappeared from task manager... Had to restart task manager... Third, Bit Bridge would not load 32 bit plugins... So I had to set Sonar to "Run as Administrator"... That took care of plugin manager and bit bridge but not the audio interface disconnect... Then next was the new UI... Unless I'm missing something there is no way to reset to the beginning of the project\song from the transport, thank god for keyboard short cuts... And the song position bar is missing from the transport, so I can't drag it to a position in the song... My custom track colors are now just a little colored bar at the very bottom of the console, not so easy to distinguish all the different tracks... And I didn't care much for any of the available color schemes, these old eyes can barely read any of the text in the control bar... I use a custom theme that I'm quite fond of and is easy to read the control bar...

Is the printer plugged in and turned on? Did you try another network or USB cable? Are you able to print the test page? Have you tried to connect the printer directly to your audio interface with a 5 pin din MIDI cable? Are you able to access the "Print Setup" for the printer from inside of Cakewalk? Have you tried the printer with another application such as Microsoft Turd? Perhaps HP disabled your printer cartridge for not paying their ink subscription fee... ??... But seriously, what Byron said...

Track View -> Options -> FX -> Show Assignable Controls, On... Assignable Controls will show up under the FX Rack bin, four parameters... Right Click the parameter that you want, go to Group ->... Select the Group you want for every FX you want to control... Now all parameters in the group will be able to be controlled as one... If the parameter that you want to edit is not listed right click on any of them and Reassign Control ->... There is a bit of a bug in the grouping... Seem first time you edit not all plugins will update, but after that they all do... Also on my PC if I try to group DX - FX, like the Sonitus Compressor that you have in your screen shot, when I right click the parameter to group Cakewalk crashes to the desktop every time...

You could also try disconnecting the synth... This might be exactly what you want... Connect/disconnect. Disconnect a synth, mute all tracks associated with it, and free up memory and CPU cycles. Using the Synth Rack A. Connect/disconnect (only when floating or docked at top or in the MultiDock)

The latest default value for the buffer is 200ms, it was change in 2019.12 release... Before that it was 250ms... In the early Sonar days the default buffer was 500ms...

The MIDI Prepare Buffer Size is the "look ahead" time for playback of the recorded midi events in your project... Your entire project will be delayed by the setting when you hit the play button... All "live" midi inputs will be processed at the midi latency of your system and are not further delayed by the buffer setting... If set rather high you will really notice the the delay when you start playback... In my experience it has no effect on audio latency... If you are changing "scenes" in Cakewalk when you are playing back live with pre-recorded midi events a slightly larger setting for the buffer can be beneficial as it gives your system more time to process and not effect playback... If it is set really low and you change scenes it can interrupt playback and even crash Cakewalk... I have mine set to 400ms which I really do not even notice that delay at all recording or playing back... I can change to any scene or multi dock in a "fully loaded" project with this setting with no problems what so ever... At lower settings I would sometimes have miner audio playback glitches when changing scenes... 400ms worked out best for my system... You may want to experiment with the setting a bit to see what works out best for your system...

For VSTi instruments that you want to load a default preset you can save it as a "Track Template" with the preset that you want to use or as your go to... Then instead of inserting your VSTi from the Browser or Synth Rack you insert it as a track template by right clicking in either the Track View or Console View... If you use this route your can also save any VST Fx that you always use with the said instrument in the template...

Snap to Grid

Many VST vendors already give you the option to set the Default plugin preset... You may also want to check out the Preset Librarian function in the Cakewalk Plugin Manager... It will let you import or export preset libraries for your vst plugins where you could probably also create you own default settings...

Also, if Mark's (msmcleod) suggestion does not work and before committing to a full re-install rename AUD.INI to AUD.old and TTSSEQ.INI to TTSSEQ.old and try that as well... AUD.INI is your audio setup and TTSSEQ.INI is your system Midi setup... Cakewalk will regenerate both files but you will have to reconfigure your setup... If you do commit to a full re-install and you do not delete the "AppData\Roaming\Cakewalk\Cakewalk Core" user directory I'm fairly sure that cakewalk does not over-write those files and you could still have the same problem... Mark can correct me if I'm wrong on that...

Re-save the "New Project" templates that you always use to create projects with the Zero Controllers When Play Stops unchecked... Then your new projects by default will have it unchecked... That parameter is saved on a per project basis... I did that years ago because of the issues it creates by resetting the controllers on VSTi's and my keyboards...

Try Piano Roll View

Are your midi tracks in your Korg set to Both or External? If they are set to Internal your Krome will not transmit them to your midi out to your PC... To listen to them from the Krome and record them into Cakewalk at the same time they would need to be set to "Both"...

I believe hypothetically would be the best replacement...

I was simply pointing out what was already stated when asked about this... but it will stop re-activating at some point in the future Here are the entire comments... Misha Question for Noel. Please. Current version expires every few months. When final built is released, what happens in a few months? It gets deactivated and dies in de-activated state? Can users purchase current version, if they don't like new versions for any reason, so Bandlab doesn't de-activate Cakewalk by Bandlab when it wants to? ---- What worries me the most, is that it seems intention is to forcefully take away current version from folks " at some point" by simply de-activating it and never activating it again... I have 2 decades of projects in Cake, and that would be a major disappointment. A honest thing would be to give existing users permanent activation to current version and then try to seduce them with new, better product(s) I don't mind Cakewalk becoming a paid software. Obviously not subscription. If it will be subscription only, I will among first to catch a train to another DAW Hopefully that is not the case. Response... Jesse Jost That's effectively what's happening and I can assure you we have no interest pulling the rug out from CbB users. Please understand that we cannot comment on specifics at this time, as pricing details and options are not yet available. In the meantime, we appreciate your perseverance - stay tuned!

So when asked this very question about stopping re-activation of CbB by user Misha on June 6th Jesse Jost replied... "That's effectively what's happening and I can assure you we have no interest pulling the rug out from CbB users." and on the new Sonar webpage under FAQ's it states... Will Cakewalk by BandLab be discontinued? Yes, eventually. We will continue providing community support and maintenance for Cakewalk by BandLab until Cakewalk Sonar becomes publicly available. At some point after the release of Sonar, Cakewalk by BandLab will no longer be supported. Note that existing Cakewalk by BandLab users will be able to continue using the software after the release of Cakewalk Sonar. In the meantime, Cakewalk by BandLab continues to be available here. But by what you are stating here, that re-activation of CbB will cease in the future, the above statements are not true and you will be pulling the rug out from CbB users.

Gary Wright, ‘Dream Weaver’ Singer, Dies at 80 RIP Dream Weaver...

Yes... Using Mix Scenes...

Isn't that what the Arranger tracks do?

You have the track "Armed" to record with input echo enabled... You would be monitoring the input signal to the track and your audio clip will be muted with the default Comping methods...

The ten Screensets are bound to the numbers 1-0 by default... Not the number pad, which if NumLock is on is bound to the "Nudge" funtions...

Now there's an idea... Just use the "Search Box"...

Perhaps it is the BBC Symphony Orchestra Library that is not velocity sensitive or responding to the velocity changes... I've seen it before with some libraries that may have several different velocity scales or settings...