jimlynch22

Before upgrading to 2012.12, CW would respond immediately when I made changes to midi notes during playback. Changes such as muting a clip or transposing notes. Now CW takes several seconds to respond. I do this sort of thing a lot to preview changes in real time. What changed? Is there a buffer setting that might impact this? Thanks!

Awesome, thanks!

Don't you think this is a bug?

Ok, thanks for the advice.

But come to think of it, why would articulations be correctly copied if you select clips one by one, but not when you use lasso to select the same clips??

Well that explains the behavior I see, but not to say I like it :-). Basically, it makes cut/paste operations rather cumbersome.

I try to use ripple edit when I have a clip or clips with multiple time signatures, or tempo changes or markers that I want to copy or move, and preserve those attributes at the destination. What is the intended use for ripple edit?

If “Select Track Articulations with Clips” is on, and you lasso a clip, all the articulation are selected in the track are selected; this prevents you from moving the clip correctly. If you right-click to select a clip one at a time, you don’t have this problem. Lasso should only select articulations that fall within the selected clip.

Perhaps I don't fully understand how RIPPLE EDIT is supposed to work, but this example in the attached screen shots seems incorrect to me.

The cursor tool intermittently stops functioning in PRV. Cannot draw notes, or erase/mute. Oddly, you can select & drag, but there is no visual feedback of the action, i.e. you can’t see the note(s) while they are being dragged. The mouse still works normally in other views. Version 2021.09

I tried disabling "Always Stream Audio Through FX" and Cakewalk CPU usage still went from under 10% to over 50% with the transport not running, just by opening the Cakewalk Adaptive Limiter plugin. So other things can be at play when looking at CPU. Just saying. So now I just don't open the adaptive limiter unless I need to see it.

Yep. culprit turns out to be cakewalk Adaptive Limiter plugin. Just closing the plugin window reduces CPU to 0 when not running. Playing back with Adaptive Limiter functioning but not displaying a GUI yields CPU =12 %

Yep, I'm looking at task manager

Why does cakewalk use 50% CPU when it's but idle for more than an hour? Normal?

I think my map has only "simple key-switches" but I changed the chase mode to full and now it works for me. Thanks so much. This forum is great!

agreed.

Yes, that was it! Voila!

A function that would control the height of all or selected automation lanes. Options could be the same or similar to operations that can be performed on normal lanes, such as "fit", "select and resize multiple lanes", "lock height", "auto track zoom". A variation of "fit" would minimize all normal lanes. This would be great when mixing to be able to see & edit envelopes for as many track as possible.

If Snap-to-Scale settings could be saved at various HH:MM:SS in the project, similar to how articulations are save for each track, it would really help writing melodies in the PRV. To simplify, they could be saved like tempos, applying to all tracks. Applying on Snap-to-Scale setting across all tracks which would be a more usual usage, having all tracks snapping to a single scale.

It would be great if articulations would chase. That way when playing from any point, the correct articulations would play.

This issue started with 2021.04 build 175. When selecting clips with right button lasso/copy, all volume envelope nodes and articulations in the track are selected (not just the ones bounds by the clip). This prevents correct dragging of the clip.

Started with my last update to 2021.04 build 175.

I'm having the same issue on W7. I tried "refresh activation" in bandlab assistant, but nothing seemed to happen. Both Edge /Webview and Cake are up to date. Bandlab assistant in not up to date, as the update in failing for me. Interestingly, after updating to "update 1" , a new "refresh activation" dialog in cakewalk is presented. It's goofy, as keystrokes typed into the username box are passed through to the app (for example typing "C" opens the control bar). I got around that by pasting in my credentials. However, after clicking "login", cakewalk gives a "network error - try again later". My network connection is fine and I tried it with my firewall turned off, to no avail. Anyway, I performed an "offline reactivation" and it seemed to work, but there was no confirmation one way or the other. I'm crossing my fingers in hopes I don't get locked out in 12 days. One wonders why a reactivation is being enforced, since the software is free?

Can you re-upload here? That would be great!

I changed all the Chase Modes as you suggested, and also changed the Play At setting from "duration" to "start", which seems to make more sense. Thanks for the suggestion. Miroslav Solo.artmap