2019.07 Feedback

[Jonathan Sasor]

On 8/18/2019 at 1:17 PM, Twisted Fingers said:

My HelpText_EN.dat is not up to date. See attached screen shot. How do I update it.

 

The files in AppData will get automatically copied from the C:\ProgramData\Cakewalk if they're moved/deleted from your existing AppData folder. You can clear AppData\Roaming\cakewalk\Cakewalk Core\Help Module and when you open CbB, they'll get updated. 

[Bill Phillips]

1 hour ago, Jon Sasor said:

The files in AppData will get automatically copied from the C:\ProgramData\Cakewalk if they're moved/deleted from your existing AppData folder. You can clear AppData\Roaming\cakewalk\Cakewalk Core\Help Module and when you open CbB, they'll get updated. 

Good to know. Thanks  

[Grem]

On 8/19/2019 at 12:37 PM, Morten Saether said:

To clarify:

Cakewalk has a master list of global keyboard shortcut assignments. These are the shortcuts that are active when lenses are set to "None".

You can override the global shortcut assignments per lens by enabling "Keyboard Shortcuts" in Lens Manger, then assigning new shortcuts and resaving the lens.

Any lens that has "Keyboard Shortcuts" disabled in Lens Manager inherits shortcut assignments from the master list ("None"), or from the previously selected lens.

This was a great explanation Morten. Having never used Lens before, this has me thinking I may want to investigate them a little further.

[Bill Phillips]

On 8/19/2019 at 1:37 PM, Morten Saether said:

To clarify:

Cakewalk has a master list of global keyboard shortcut assignments. These are the shortcuts that are active when lenses are set to "None".

You can override the global shortcut assignments per lens by enabling "Keyboard Shortcuts" in Lens Manger, then assigning new shortcuts and resaving the lens.

Any lens that has "Keyboard Shortcuts" disabled in Lens Manager inherits shortcut assignments from the master list ("None"), or from the previously selected lens.

Looks like keyboard shortcuts you want to add for all lenses & "none" should be added with "none" selected in lenses.

[Giorgio Gabriel]

Just installed 2019.07 and tried for a very short time (till now), but I am very happy with this new version. Thanks to all!

Bye,

Giorgio

 

[Morten Saether]

20 minutes ago, Twisted Fingers said:

Looks like keyboard shortcuts you want to add for all lenses & "none" should be added with "none" selected in lenses.

Correct. As I mentioned in my previous reply:

"However, if you prefer to always use the same shortcuts regardless of which lens is selected, you should set lenses to "None" before making any global keyboard shortcut assignments."

[Frank Cheney]

How about an optional purchase of a Cakewalk Sonar version

that can be registered offline with just a serial number, and could coexist

with the Bandlab version?

To me, that ease of use would be well worth $30. I've had an issue on

one of my computers, first installing, and then registering, as mentioned

in a nearby forum topic.

The update sounds epic to me, even though I don't use most daw features.

It speaks well to Sonar being a more solid and enjoyable daw

for years to come, even for a minimalist like me.

Cheers

[winkpain]

On 8/19/2019 at 1:37 PM, Morten Saether said:

To clarify:

Cakewalk has a master list of global keyboard shortcut assignments. These are the shortcuts that are active when lenses are set to "None".

You can override the global shortcut assignments per lens by enabling "Keyboard Shortcuts" in Lens Manger, then assigning new shortcuts and resaving the lens.

Any lens that has "Keyboard Shortcuts" disabled in Lens Manager inherits shortcut assignments from the master list ("None"), or from the previously selected lens.

Yes, this clarification certainly helps a lot when dealing with bindings and lenses, Morten.  Thank you.

I am now going down a road of trying to get a handle on other Key Bindings irregularities that I experience. So, can you tell us this: when we first go to Lenses/None to activate the "master list of global keyboard shortcut assignments" and then open Preferences/Keyboard Shortcuts and choose the command to  "Zap all" thereby clearing all key bindings (so the documentation says), why are there still bindings that remain?  And where can we see a list of those??  And I'm not talking about just the basic, reserved ones like Spacebar for Play and such. I am finding certain very specific and obscure bindings that just persist no matter what, even when reassigning keystrokes to other commands, and even when "Zapping all" - even when, in the list of bindings, the keystrokes that are having an effect are notated as "Not assigned" and the command that is instantiated shows no keystroke bound to it....

Sorry if this is confusing. The simple starter questions are, again: What key bindings persist when Lenses/None is chosen and Zap All has been applied?? Why does Zap All not clear these? And whatever those are, do they take precedence over any custom chosen bindings?? Where can we see a list of these???

[Morten Saether]

11 hours ago, winkpain said:

when we first go to Lenses/None to activate the "master list of global keyboard shortcut assignments" and then open Preferences/Keyboard Shortcuts and choose the command to  "Zap all" thereby clearing all key bindings (so the documentation says), why are there still bindings that remain?  

The Zap All command only removes your custom shortcut assignments, not the default hard-coded shortcuts. To see a list of default shortcuts, go to Help > Keyboard Shortcuts, or click here.

[winkpain]

1 hour ago, Morten Saether said:

The Zap All command only removes your custom shortcut assignments, not the default hard-coded shortcuts. To see a list of default shortcuts, go to Help > Keyboard Shortcuts, or click here.

Interesting!

So, what I am saying is, when "Zapping all" and returning to the default shortcut assignments, there seem to be some bindings that remain that are not represented in the Preferences-Keyboard Shortcuts window. In other words, the keystroke shows as "Unassigned" and nevertheless has a very obvious function.  Specifically, and one that has caused me literally years of confusion until today, is the number keypad NUM 0 key. This is hard-coded to an obscure (to me) "Enhanced editing with keyboard" function that I had never heard of or seen talked about, nor is there even  a corresponding menu item in the menu bar!

I have to say that inadvertently hitting the NUM 0 key, a very easy thing to do, causes profound confusion in regards to cursor behavior when editing clips. This NUM 0 key engages Enhanced Keyboard Editing with no indication other than a secondary cursor line appearing at a track row (and only on one track) location somewhere in the project that can very easily be completely hidden to the user given whatever zoom level or screenset you may be using. And then, being completely oblivious to the fact that you are in keyboard editing mode, the normal cursor no longer behaves as one expects with edits and inserts happening at locations that seem totally random.

Wow, has this driven me nuts! And I'm happy to now know the cause. But... what of this keyboard editing function?  Why no mention in the menus and otherwise no indication of the mode being engaged or not? Why is such an important default keystroke (NUM 0) shown as unassigned??

[Morten Saether]

Thanks for reporting this. We'll investigate and see if there are ways to improve the UI.

[Roger Wicks]

Yes, PLEASE make this new timeline behavior an optional feature. I've been using it a few weeks now, and I just don't like it !!!  ?

[mdiemer]

I'm having a problem with the select tool in staff view. Suddenly today it decided to become a move tool instead of a select tool, even though I have the select tool chosen. Sometimes I can get it behave if I am deliberate enough in how I select or lasso notes. Very weird.

[Noel Borthwick]

On 8/23/2019 at 8:00 PM, Cosmo Kramer said:

Yes, PLEASE make this new timeline behavior an optional feature. I've been using it a few weeks now, and I just don't like it !!!  ?

@Cosmo Kramer which behavior are you referring to? If its the click to set now time that is already configurable..

[Roger Wicks]

Hi Noel - Yes, it's because after editing, there is usually some part selected, and I'm used to de-selecting while I'm playing back. I'll do this after I'm satisfied with my editing while playing back. If I want to play back and keep something selected, I must click on a very tiny area around the timeline.  Also, I don't like having the selected part show in the timeline with the new markers.

Is this configurable ??

[Noel Borthwick]

Yes you can turn off the click behavior not the selection handles. See the feature overview topic.

Quote

Clicking in the Clips pane or bus pane during playback will set the playback position. This allows you to easily audition playback starting from a waveform peak. This behavior can be customized via the new Click Behavior> Set During Playback option in the Track view Options menu. 

Regarding unselecting there are hotkeys to do that. Num-5 or CTRL-Shift-A will deselect.

[RobertWS]

1 hour ago, Noel Borthwick said:

Regarding unselecting there are hotkeys to do that. Num-5 or CTRL-Shift-A will deselect.

Num-5 unselects?  Not on my box (I wish it did!).

[marcL]

I thought that the overwriting of clips in take lanes has been fixed!? But this is not true if I set the now position, select a take lane and use the "Import Audio" menu. Although I have selected e.g. a new take lane (top left and name is marked!) the imported audio is inserted in arbitrary other lane (that contained another clip) !!! ?

[Noel Borthwick]

4 hours ago, marled said:

I thought that the overwriting of clips in take lanes has been fixed!? But this is not true if I set the now position, select a take lane and use the "Import Audio" menu. Although I have selected e.g. a new take lane (top left and name is marked!) the imported audio is inserted in arbitrary other lane (that contained another clip) !!! ?

Dragging from the browser respects the drop location and will insert clips contiguously on lanes. If you drop on a lane that has data it will autocrop it like this.
If you drag to to the main comp track it will drop starting from the first lane and crop any data that lives there. This is by design.
If you want to insert new lanes just drop to the last lane or insert a new lane and drop there.
EXAMPLE: Dragging MIDI and audio clips from Browser to add take lanes

EDIT: I see you mentioned the import audio menu. Make sure that the target lane you want to import to is selected by double clicking the lane.
I'll check if  the import audio menu respects the selected lane position. 

[Noel Borthwick]

8 hours ago, RobertWS said:

Num-5 unselects?  Not on my box (I wish it did!).

@RobertWS make sure that num lock is OFF before doing that. Its the "gray" num-5 key that unselects. I use it all the time.