Terry Kelley

Is it a case of jerky finger on the mouse slightly moving the clip when you tried to select it? Never happens to me. Nope.

This is Worker speaking. Hello.

What? I'm already working on my second 100,000. I gave up on my first.

No. Cakewalk can't support it, well rather, most hardware can't do it. Both interfaces would need to be driven by the same word clock and unless the interfaces have clock in and out (and most don't) it wouldn't work. If you need more outputs - get an interface with more outputs. Just be prepared to have a separate volume control for any outputs that aren't the main outputs. Most interfaces with more than the basic stereo out pair don't provide a hardware knob to change the volume on the other outputs. I wish they did since it would make quad and surround mixing easier.

Yeah, it's one of those things that seem intuitive AFTER you figure it out.

Assuming the VST supports multiple outputs, the process is: 1. Create a new audio track. 2. Go into the VST and tell the kick drum to go out a new output (like the 3+4 stereo pair.) The rest will still go out the normal 1+2 stereo pair. 3. Go to the audio track and change the Input to be the VST 3+4 stereo output. You should now have the kick drum on a separate track. Audio tracks can be told to "listen" to other VST outputs. I use this process or split out my bass drum, snare and overhead. I can add effects to each as I want. You can do this with muli-synth VSTs to give them their own track while only having one instance loaded.

I had old .wrk files that wouldn't load into 64-bit Cakwalk 8.0 (with updates) but would in 32 bit. I would have to re-save them in 32-bit and then they would load into 64-bit. I'll dig some out and see if they will load in CbB. Otherwise CbB has been pretty consistent.

Too fussy in my opinion (to quote my wife.) Since they add it when a synth is loaded, just keep doing it. Or do nothing. I'm easy.

So they could write of bit of code to scan the track name and look for a synth name (and pass it through a small AI module to check for alternate spellings or foreign language) and change the name. Just saying ... Or just insert the new synth name at the front and let us sort it out. But give me vari-speed first.

Left the edited name or changed it to the new synth? I can see both really.

I had the same thought at one time. I always put pertinent information in the track title such as what synth, amp settings, mic used, guitar used etc. When I load a soft synth I add the sound or preset I was using. But when I was switch the synth, the old synth name is still there and I m wondering "Well gee, why didn't CW change the Xpand!2 to Mini Moog for me?" Because that's my job as part of keeping notes and track of what I am doing. At least CW was nice enough to put the synth name there when I loaded it.

You can't save from every window in Cakewalk. The main screen needs to be in focus. Trying to save from a VST focused window or something like notes won't allow a save. Save is only in the main screen.

Paper tape but the boot-loader sequence costs extra.

Maybe we can convince Noel to sell full licenses out of the trunk of his car! Psst. Buddy ...

I can't speak for everyone but in my case it works.

Well, I guess you got them there.

Agreed. Not all questions have been answered and the developers have been clear that they are not prepared to answer these questions yet. So continuing to pound them over it is futile. We will just have to continue to vibrate and squirm in our chairs until they do.

Yeah, I'm saying the same thing Will, if I have interpreted the developers comments correctly. But at some point CbB will end but existing installations will continue to work. Sonar will live on. I think this is a fair concession to the CbB people that helped make it better. If we like the Sonar UI we can switch to it. I'm excited to see it and if I like it, hopefully I can afford it! While we can argue costs, have the Cakewalk developers ever given us crap? A few bugs, yes, but the products themselves have always delivered. That will continue.

Sorry, I thought one of the earlier staff posts mentioned that. I will strike through that. Ah, Next. Ok, I corrected that too.

So it sounds like: 1. CbB will get updates with some new features but that will be the end of the road for it. 2. The CbB core will get a new UI and become Sonar. This is the main product going forward. 3. You're releasing a totally new product called Next directed towards song writers. This will also be ported to MacOS. 4. You're also porting Sonar to MacOS to compete with the big boys. <--- Not true per Noel.

Well FMD!

Is it too early to start suggesting new Sonar features? Just asking for a friend.

That and girls. I've had many an access violation. Seriously, great overview of the issue. C0000005 is frustrating to deal with. And there have been times where the developers were able to point to the specific issue and contact the VST company. It's not silence like some believe.

I'm staring at my Cakewalk for DOS floppy and thinking about how far we have come (users and the developers.) Given some of the issues with the past (such as how Cakewalk ended in 2018) there is no reason people can't express their doubt and concern and it IS justified even if those that made that happen are no longer involved. As one person said (paraphrasing) 'Engineers go about things often far different from marketing.' But considering how CbB and the developers themselves have treated us since 2018, I willing to give them a lot of leeway. And I'll bet they don't forget about us. Maybe we will be the ones that benefit from our willingness to try and help (even when I did ask extraordinarily stupid questions that caused them to burst out laughing.) As long as I can use Cakewalk, I will continue to use it. Hopefully I can. With a little want included.

I'm doing fine. Thanks Bruno!