Terry Kelley

I never figured out why the buffer size changed it. I have my suspicions but I've learn that the complexities often go way beyond logic. This what it took and it's been the solution ever since. Same with some Arturia plugins like the Augmented plugins. It works. I'm happy. The performance meters are very helpful but it's unwise to try and draw too much conclusion from them. Once you start seeing them getting "busy" and you have crackling/cutouts/noise, start freezing (or bouncing) and nail down which track/affect it is. I'm glad they are available though. It's an indicator to start checking your CPU load. And heaven knows I can load the living %&$* out of it. Some plugins are just brutal. So where is the new Cakewalk release?

They're trying to create a new revenue stream. It will take time. So far, we aren't a revenue stream.

I worked with early Ambisonic back in the 70's. Sounds like it's improved a lot. I haven't heard of anyone here working with it, but here's a bump just in case.

I came across this and figured I should give the answer: The CPU can’t keep up. Bounce the harmonizer track to another track (just freezing it won’t include any midi control.) Melda MHarmonizor like Waves and many other plugins are CPU hogs. My i7 can’t keep up. Don’t go by the CPU performance bars. They can’t tell the whole story fast enough for you to determine the CPU is being beat to death.

I've been fighting an issue with the surround panner mouse being jerky and slow when the tracks are playing. Stopped, it's fine but once I start playback the panner is very slow. After messing with far too many thing I came upon your comments. Lo and behold, raising the Vertical Zoom factor to anything above 1 (like 1.001) stopped the jerkiness. Not sure why but I am thankful I came upon your comments. If I figure out the "why" I'll post it.

Several measures isn't Snap. I don't think you can Snap that far. But Arranger moves is a good suggestion.

I say we strike!

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.