SirWillyDS12

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...

@David Baay The latency is round trip as reported to Cakewalk by my Motu 828es... I use the maximum buffer size 1024 with a safety offset buffer of 256 at 48kHz while mixing... The input latency is 26.7 ms. the output 48 ms and round trip 74.7 ms... I use this "setup" only when mixing... I use the Asio drivers from two of my keyboards input into DS WASAPI ASIO Router Mixer which is then routed back to my 828es... From the 828es the tracks are routed into Cakewalk... I input echo all my keyboards (live inputs) through Cakewalk and mix with recorded audio and soft synths tracks.. All my key tracks are recorded to midi tracks and while recording I direct monitor through the 828es... When recording I use a buffer size of 64, safety of 16 with 1.7 ms input latency... When I work on mixing a song after recording I pre- delay my midi tracks to make up for the round trip latency of my Motu 828es to align the input echoed live inputs with the audio and or soft synth tracks in Cakewalk... This setup gives me great flexibility, I can use VST effects on any of my keyboard tracks or even a mix of tracks... I can edit the "voice" of any of my key programs at any time or even select a different voice and not have to re-record "audio"... I render all of my mixes in real time recorded from the Master Output as all my keyboards midi tracks are playing in real time... I can have up to 64 live keyboard inputs at one time... Latency is not an issue at all by offsetting my tracks so I use the maximum buffer size for CPU conservation... For the most part I try to use zero latency plugins on the "live inputs"... I also have four hardware effects processors that are digitally interfaced with my 828es that I use as FX sends from Cakewalk, also rendered in real time with the "Mix" if I use them...

It's the new frozen track, the Un-Nudgable... 😃... So I believe I know what is happening here... You are clicking on the new Audio clip in the track view and that doesn't select the track, can't Nudge... The underlying "midi track" in the instrument track which is now frozen is the original track and is not selected when you click on the new audio clip... If you open up the Piano Roll View with the Track View also visible you will see it... When the underlying original midi clip is selected (as long as the entire track is not selected...) you can Nudge the poor little "sucker" all over the place, Numlock and all and it doesn't "un-select"... Both the original midi and the new audio both move...

No, really it's not... I use three different Asio Devices... I use DS WASAPI ASIO Router Mixer and loop back both my Yamaha Motif XF6 Asio (Up to 16 tracks Asio...) and my Roland Fantom 7 (Up to 32 tracks Asio...) to my Motu 828es... My 828es is interfaced with Cakewalk and I can send 128 tracks by Thunder Bolt to Cakewalk... I am not limited to the Analog outputs from my keyboards and all tracks are digital... To do so I have to adjust for Latency for the loop back (75 ms @ 1024 buffer setting) by nudging the midi tracks sent out 75ms before the Start... It work beautifully...

You just never know... I start all my projects at measure two... After recording and during the mixing stage I will Nudge the start times of my tracks left if they are going to outboard gear that will be returning to Cakewalk to adjust for Latency...

If your clip starts at Time Zero (1:01:000) and you are trying to nudge it left it will not move... It is Un-Nudgable...

The version I'm using is in English... 😀

OBS Studio got around this limitation by using a re-written Asio SDK... The ASIO plugin for OBS-Studio is capable of using multiple Asio devices at the same time, as well as using WASAPI or WDM\KS... But OBS is open source and I don't think they really care much about Steinberg's licensing...

Not true... You can use Linked Clips... With linked clips edit one clips and all others will have the same edits across different tracks... And as far as MIDIChFilter, it does work quite well... (Thanks @scook) I set it up with just one instance and was able to drive three different sets of soft and hardware synths... I used three different midi channels with the same instance of MIDIChFilter... But, for the record I am all for expanded midi capability... Feature Request: Add Midi Sends and Midi Aux Tracks