Not sure if this is just an error on my part, but here goes.
I open a clip editor, and go to shortcuts. I then assign short cuts to step note forward, and step note back. When i try to use these shortcuts, i get two results. 1. The note doesn't move, but just sounds (when using the step note forward shortcut). 2. When i attempt to use the step not back shortcut, the red playback cursor jumps to bar 28080, or close to it. As enthusiastic as I am at the idea of writing symphony after symphony, i'm not sure I could get to that number of bars in my lifetime.
But here's the odd bit. When i highlight a note, and use just the left and right arrows (which seems to be some sort of default pair already assigned to these shortcuts), the note will step back, but it will not step forward.
On a wider note, can i ask if we have some sort of catchall that tells the user when he's trying to assign a key to a shortcut that's already being used by something else?
And one final question. I use META+left/right to step the playback cursor back and forward. Can these assignments be used in the clip editor as well for the same shortcuts? Or do I have to assign a new set of keys? (which would not make sense to me, as moving the playback cursor back and forth is a global function) They don't seem to function correctly at the moment.
Onwards and Upward.
Alex.
p.s. I know shortcuts aren't glamorous, but they are important for productive workflow, particularly large projects.
re. shortcuts not functioning in the clip editor...
Transport/Step/Note/Backward or Forward are not supposed to move notes around--where did you get that idea? it's supposed to move the play-head (red vertical cursor) to either the previous or next notes onset resp. (and selecting/highlighting those in the process).
that is not expected behavior, at all--can you isolate the track or clip where it occurs and share to debug and fix it?
that is indeed in place: you cannot assign a keyboard sequence that is already assigned (in the same context, either main tracks or MIDI clip editor views)
wait! what is this META key all about? mind you it might not have support from the Qt framework (while prolly it does on the DE/WM/compositor in charge, even with different meaning or semantics, whatever; for instance on KDE/Plasma6 it means the dreaded "windows " key, usually to the right of the left-Ctrl key in a modern standard PC-keyboard ; again this META key, no matter its meaning, is not recognized for keyboard shortcuts assignment, at least in Qt/qtractor I'm afraid, so sorry).
seeya
The META key is indeed the…
The META key is indeed the dreaded WIN key. That gives me a big clue. I'll go through remove all the META key assignments, and see if the rest improves.
Thanks for the heads up.
Alex.
Add new comment