Re: DP7.1 - Record Enable Next/Previous w/Arrow?

[Shooshie]

I'm using DP 7.1 at the moment, and for some reason the tracks are not Record-Enabling with the arrow keys. I need to be able to switch from track to track using the arrow-up or arrow-down, but for some reason it is not doing that.

I checked the COMMANDS window, and it is indeed set correctly. I've been looking for new features that might have changed something, but so far nothing.

So, is it just happening here? Or is the same thing going on for anyone else?

Shooshie

[Shooshie]

Figured it out:

Yes, the Commands Window was still set for the up/down Record enable, but MOTU has added "Nudge Up" and "Nudge Down" commands, as well as "Nudge" commands for the Custom Console Window, and they assigned the up/down arrows to all of them!

That's all well and good, but I'm going to have to find a new set of commands for either the Record-Enable or the nudge commands; they can't share the same arrow keys.

So, if you have this problem, the answer is to reassign some commands in the Commands Window which are assigned the same keys. Specifically, these are:

Track

• Record Enable Next Track
  Record Enable Previous Track

Custom Console Window:

• Nudge UP
  Nudge DOWN

More Edit

• Nudge UP
  Nudge DOWN[/b]

Now, let me tell you what I just realized. With the nudge up/down commands set to your arrow keys, ANYTHING THAT IS SELECTED WILL BE TRANSPOSED when you hit the arrow keys. Let me show you my Undo History:



See all those transposed tracks? Those were altered while I was attempting to change the record-enabled track. Furthermore, any time you happen to hit the arrows by accident or for any other reason, you will have just transposed a note, selection, or whole track or group of tracks by a half-step for each time you struck the key.

It is essential that you change the command from arrow keys to something that can only be hit deliberately.

I'm thrilled to have the ability to move notes up and down in pitch with a keyboard command, but the Arrow Keys were a very unfortunate choice for default keys, for obvious reasons. If you think you may have hit these keys since you installed DP 7.1, please check your UNDO History for any possible unintended transpositions you may have inadvertently caused.

Good news/bad news. But the bad news is easily fixable if you are aware of it. I'm just trying to make everyone aware of it. Also, it would help if anyone with some free time on Monday would call MOTU and let them know about this potentially hazardous problem.

Shooshie

[Sergievsky]

Thanks Shooshie, that record enable/arrow thing was bugging me too bigtime...needed it back.

[Kubi]

Thanks, this is why I hang out at this board.

Just updated my DP to v7.1, remembered there was an issue with the up-down arrow commands, found the thread, went into my commands window, fixed the "record enable next/prev track" to be cmd-ctrl-arrow dwn/up, and saved myself probably at least one occurrence of "What the f*** just happened?!!??"



And: I'm very happy that we can now nudge MIDI notes up and down in the graphic edit window. Always bugged me that I could do left/right, but not up/down. Very cool addition indeed.

[rthorderson]

Shoshie,

Superb find...I did the same search you did in the commands but somehow came up empty (must have missed them). I use the folders a ton and thought it was because of changes they made to folder behavior...and I gave up trying to fix it.

Thanks so much!

[Shooshie]

I'm considering sticky-fying this thread for a while. It's really important information, considering how many of us naturally reach for the arrow keys to change the record enable. Now, with the current command defaults, if you have anything selected in a track, you're going to transpose it if you do that. Big no-no on MOTU's part for setting that default, but I'm sure it's a case of the right hand not knowing what the left hand is doing; one younger programmer probably set it up, unaware of the deep past default (since the beginning of Performer) of using that key for Record Enable.

No problem as long as everyone gets the message, but it's not hard to imagine situations that could quickly become disastrous for someone's files. After a few strokes with a scattered selection, you could have notes all over the place! Then imagine the thread title we'd see here: DP arbitrarily transposing my notes!!! Grrrr!!!

So, we need to nip that one in the bud and get everyone on board.

Shooshie

[rsaltmarsh]

I'm considering sticky-fying this thread for a while. It's really important information, considering how many of us naturally reach for the arrow keys to change the record enable. Now, with the current command defaults, if you have anything selected in a track, you're going to transpose it if you do that. Big no-no on MOTU's part for setting that default, but I'm sure it's a case of the right hand not knowing what the left hand is doing; one younger programmer probably set it up, unaware of the deep past default (since the beginning of Performer) of using that key for Record Enable.

No problem as long as everyone gets the message, but it's not hard to imagine situations that could quickly become disastrous for someone's files. After a few strokes with a scattered selection, you could have notes all over the place! Then imagine the thread title we'd see here: DP arbitrarily transposing my notes!!! Grrrr!!!

So, we need to nip that one in the bud and get everyone on board.

Shooshie

Shooshie, this just goes to my point that MOTU rushes these releases out the door without any real user beta-testing. C'mon, is it really yours, mine or any one else job to find a work around for such a blatant error? To be frustrated out of our minds looking for the problem ANY ONE who uses Dp would have discovered it in a heart beat. This is bordering on Microsoft-ish marketing: Get it out the door, well fix it in the update- but with Vista it never quite happened...

I appreciate your positive outlook and encouragement, but as one who doesn't have the time to chase down such grievous errors, and ask my wife, I don't need any more stress and frustration in my life... let's put 'some' of the responsibility back where it belongs... on the developer. Just my $.01348 after taxes.

[Dan Worley]

I've had trouble with Commands, too. A lot of duplicates and even triplicates. I thought maybe I just picked the wrong option in the Commands merge window when upgrading (and I may have). MOTU's wording in that window confuses me.

When a command doesn't work for me, I apply it to something else to find out where else it's been applied (talk about confusing wording).

At least there's a fairly simple fix to all this.

c-ya,

Dan Worley