GreenLight

It would be so very time-saving to be able to select a default preset for each and every VST plugin. The preset would then always be the default loading state when a specific plugin is instantiated. Please consider it for the new and flashy soon-to-be Sonar.

I will check my current setting and get back to you. Although I thought that setting only concerned MIDI messages? Thanks for your input!

Hi fellow Cakewalkers! Has anyone else experienced problems with SuperPlate v5.4.1 (current version)? Occasionally, I get loud reverb tails/bursts from the plugin, when it should be silent. Yesterday it happened just as a project finished loading, which was a bit disconcerting. Unfortunately I haven't yet been able to reproduce it consistently, making it hard to both report and fix. 🤔

Fantastic that you can repro it! 👍 You can actually contribute to getting the problem fixed once and for all. To quote Noel (from two posts above yours): "The take away from this is for problems like this its very important to try and get a repro and send us a dump/project."

If you can reproduce it and record it as a short animated GIF (with for example LICECap) then I'm sure the Bakers will fix it. 👍 I've reported numerous bugs and every one with a clear repro has been fixed. 😃

I just noticed this new behavior as well (it's mentioned in the release notes under "Misc" as "Inconsistent AutoXFade with split clips"). Even if it's a small feature change, I think it's a pretty "big deal" workflow-wise that the Automatic crossfade setting now also affects split operations and I think it's good to spread the word. It's potentially a huge time-saver! But I can definitely see a use case where it would be good to be able to directly perform splits with and without crossfades, without having to toggle Automatic crossfades first. Maybe two different keyboard shortcuts would be something for the new Cakewalk Sonar?

Muchas gracias for the information, Jorge! Sounds great. 😃👍 Loving SuperPlate here, btw, brilliant for massive and dreamy synths... especially the 240 algorithm!

Great news, thanks a lot for the update, Gustabo! 👍 Has anyone tried the 5.4.2 beta? Did it fix all of the issues? I've only installed SuperPlate VST2 yet, and didn't dare to update any of the VST2 plugins, nor have I installed the VST3 versions... Don't wanna disturb my current production spree!

Just to follow up - did you (or anyone else) send a detailed repro to Noel about this?

Good to know, thanks. I asked because someone on Gearspace (someone from here?) reported issues when Cakewalk auto-replaced VST2 versions of plugins with VST3 versions (which it is configured to do by default). I'm not sure if the problem was that the VST3 versions were buggy or if it was that the presets were not migrated correctly during the VST2->VST3 replacement.

Brilliant, thanks! So if you avoid installing the VST3 versions, everything is smooth sailing as usual with the SoundToys 5.4 package?

So is the new SuperPlate working well in Cakewalk as a VST2? (If yes, what version?) I have been hesitant to buy it until people confirm it's working well...

It's certainly not dead! In a recent thread about Cakewalk workflow & usability tips, @Promidi shared information about his very extensive usage of CALs. And if I remember correctly, I think it was @Heinz Hupfer who had some impressive CAL workflows as well. Update: But I agree with @Mark Morgon-Shaw's earlier comment that several of those smart CAL features could/should be part of the standard MIDI tools.

Yes, I got the two new products part, but didn't really realize the "going independent brand" part. What kind of effects do you foresee this corporate change to have on your operation and business, going forward?

Ah, that you now operate independently under Bandlab is a brand-new reorganization thing?

I think the model you mentioned is great. But I think it's important to consider why many people misunderstood the message. I think it is/was due to semantics. "Annual" feels like a very ambiguous word for what it is, it implicitly implies an annual subscription payment. If you'd call it "including 12 months of updates", that's immediately a lot clearer even if it refers to the same thing. I am also one of those who prefer single payments to subscriptions. (That's what I was taught as a kid, how to be an economical consumer: always keep all your recurring costs to a minimum.) For non or semi-professionals especially, there are several problems with music software subscriptions in addition to the ideological ones: what if you go on vacation? What if you're just not using your tool for 5 weeks? What if you get a divorce/dog/get severely sick and are unable to produce for 3 months? Who wants to pay for that time? There's a reason gyms love subscriptions... 😉 Anyway, as a long time user I'm very excited by the further development of Cakewalk! 😃 And I would be really happy if the new Cakewalk Sonar implemented a competitively priced model of "single payment with 12 months of updates included- last version permanently unlocked". Even if it was called a "subscription"... 😉

Great input! I use both, but not enough, I think... I'd like ProTools style import of tracks & buses from other projects... would be useful when you realize "I'd like that sound from that project".

Really cool! Did you program all those yourself? A lot of the controller stuff you list that you do with CALs I'd love to have implemented in Cakewalk as "automation style" envelopes but for controllers...

I've been looking at the Streamdeck... looks really nice. What kinda stuff do you do with the shortcuts, transport?

Oh, sorry, I probably worded it weirdly. I know what CAL is, but I wondered what your CAL scripts do specifically?

What do the CALs do? *curious*

It would be great to get a thread rolling with peoples' personal workflow/usability tips for Cakewalk. This could be anything: external controllers you use, special settings or features in Cakewalk that you use in a special way, a favorite pet that somehow enhances your inspiration (ok, maybe not that one.... then we'd all have to get a hamster?) or something else. I'm sure there are a lot of great ideas out there! 😃 My personal two workflow staples are: Custom keyboard binding: ALT + X for "Start/stop audio engine" I run CPU heavy projects all the time and I don't want my CPU to max out during all the breaks when the project is not running. I use this constantly. Custom keyboard bindings: numbers 1-7 for setting snap grid size to whole note, 1/2, 1/4, 1/8, 1/16, 1/32 and 1/64 note Also a complete life saver for all audio and MIDI editing. Also onstantly in use for me. I could fill a whole topic of my custom keyboard shortcuts... 😂

Thanks for the input! Very interesting: as you say, clicking on the control bar button "Input Echo" two times, will actually dim the input echo button on MIDI tracks even when in "Always on" mode. But unfortunately it doesn't seem to work as expected, at least not in my scenario. Cakewalk still echoes MIDI data on that track, causing some kind of MIDI loop, which causes the arp on the Moog Subsequent 37 to continuously restart from the beginning, which is not my wanted behavior. I just realized that as a workaround, I can just place focus on another MIDI track before playback to avoid the MIDI echo loop.

The setting "Always Echo Current MIDI Track" is brilliant in its convenience and something I always want enabled. But for example, for the arp on the Moog Subsequent 37 hardware to work properly, it requires that MIDI input is turned off in Cakewalk. And the only option is to turn off "Always Echo Current MIDI Track" entirely. It would be much more convenient to be able to disable MIDI echo for individual tracks instead of having to turn it off entirely. Thanks for considering it!

I take it you're monitoring external instruments via VST effects? If yes, you have to try the enabling the setting "Override automatic plug-in delay compensation on live inputs" in the Control Bar. (This button is called "Live Input PDC Override" in the manual, see p367.) It will make latency a lot better when monitoring external inputs!