jimlynch22

Here's a little bug with Exclusive Solo. I'm on Version 2022.11 build 021, 64 bit) 1) Turn on Exclusive Solo for a track. 2) Select some notes on the PRV and perform any Process, such as Length... or Scale Velocity. 3) The track is silenced - Cakewalk behaves as if the track is unsolo'd, even though the tracks Solo button is still lit.

what is the Key+ feature?

will do

It would be very helpful to have a high lighted border around the pane that is in focus. Especially useful when using keyboard commands that have different functions depending on whether you're in the TrackView or PRV panes. For example Shift-S\ back spaces in the TrackView but solos/un-solos all tracks in the PRV is in focus. Also useful if you activate the scrub tool, which hangs if you're in the TrackView.

Thanks, I'll repost over there.

It would be very helpful to have a high lighted border around the pane that is in focus. Especially useful when using keyboard commands that have different functions depending on in the TrackView or PRV panes, for example Shift-S, which back spaces in the TrackView but solos/un-solos all tracks if the PRV is in focus. Also useful if you activate the scrub tool, which hangs if you're in the TrackView.

I second this suggestion! I use snap to scale a lot.

I too would find it useful to have some visual clue showing which mode the faders are in. I've fooled myself with this a number of times.

When you are working on a project with several changes of musical key (such as C to E-minor) it would be great if multiple sets of "snap to scale" settings could be saved in the project. When you are working on such a project, moving around from section to section, when there is a change of key, you have to go into each track in the PRV and set/reset the musical key you want in the Snap to Scale for each track. This is quite laborious! Perhaps such a feature could be incorporated in the Arranger model.

I would find this capability useful

I thought of that, but I do not see a way to customize or create drum maps?

Aha! This solved my issue. Thanks so much!

I'm having trouble using keyboard customization. I've made some customizations and saved them to default bandlab.kbn, but the bindings revert to some other default whenever I open a project. When I look at 'default bandlab.kbn' my customizations are still there In Workspaces I have 1) Checked "Apply Workspace on Project Load" 2) Set workspaces to use 'keyboard shortcuts' I've also tried 1) Unchecking "Apply Workspace on Project Load" 2) Set workspaces to not use 'keyboard shortcuts' I don't know if this is bug or not. Any suggestions appreciated!

ditto that

That would be great.

You could view both notes and CCs in seperate windows using the Piano Roll View, as shown in my screen shot/

Thanks, this works for me.

For me, left and right arrow keys in track view moves focus through all the various buttons. I would like the left and right arrows to scroll the track view, same as in the PRV view. Is this a bug? I could not find a "scroll" funtion when I tried to map a keyboard shortcut to accomplish this. Thanks.

I am seeing similar to #1 above. Not using linked clips, but sporadically when lasso-selecting notes and moving them using Numpad-4 or Numpad-6 , not all of the noes are moved. Always, if I ESC before completing the move, and try again, it's fine.

Great, thanks for the info.

With multiple tracks selected, “Lock Height” locks all selected tracks. Seems more intuitive and reduces clicks.

When dragging in the Articulation pane to lengthen an articulation, and in the Arranger Track to lengthen an arranger section, it would be nice if the Articulation Track and PRV pane scrolled when dragging to a point beyond the visible window, the same way it works when dragging the length of a note in the PRV.

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?