williamcopper
Maybe someone can improve my workflow: I spend endless hours taking a single track, derived from a printed score, and breaking it into many tracks in order to make an instrument with many different articulations: staccato, accent, legato, spi-ccato, quiet, loud, sustained, crescendo, diminuendo.   So lots of selecting small units, cutting from the source track, and pasting into the destination track.

Again this may be totally bogus, so take it for what it's worth and I'm sure someone computer-savvy will correct me if I'm wrong...but computers deal in blocks of memory. My hard drive is partitioned in 4K blocks. So this means that even a text file with 256 bytes will take up 4K. I have all kinds of little files (asset files and such) yet they cannot take up any less than 4K. Don't know if RAM works the same way, but those zillions of little edits might add up. I certainly experience something similar in Sony Vegas, where I have many more tiny edits than I would ever do in SONAR. After an hour or so I save a Vegas project, close it, and then re-open it. Crashes and weirdnesses pretty much disappear when I do that.

Answering a question from earlier, what are all the minimized windows: it's my attempt to sanitize and sanify the horrible nature of the PRV controller pane.    See screenshot attached, the result of deciding to add one more midi track to a group of related tracks in one of those windows:   after having pared down all the extraneous controller lanes to just the velocity, CC1, and CC11, I get the view as shown.   And I have to click in the tiny tiny "minus-sign-in-a-box" in each lane, accurately, to close ONE of them.  Then the screen jumps, all the lanes reposition themselves, and I have to click in the next tiny tiny "minus-sign-in-a-box", accurately, to close a second one.   Then the screen jumps, all the lanes reposition themselves, and I have to click in the next tiny tiny "minus-sign-in-a-box", accurately, to close a second one.   Then the screen jumps, all the lanes reposition themselves, and I have to ... you get the idea!   (Though the programmers, so far, don't seem to ...)

icontakt, I tried your suggestion, and it doesn't seem to work as described?   I select notes in one track, in PRV, click in track view, turn off num-lock, press 8 on the number pad, and the track focus shifts to the previous track, but the notes remain where they were.    Am I doing something wrong?

williamcopper
icontakt, I tried your suggestion, and it doesn't seem to work as described?   I select notes in one track, in PRV, click in track view, turn off num-lock, press 8 on the number pad, and the track focus shifts to the previous track, but the notes remain where they were.    Am I doing something wrong?

 
It should work as I described. Try it in a new project.
Does Process > Nudge > Up or Down in the menu bar not work, either? 

Process - nudge - down/up works.    I think I may have unbound the number pad numbers  in an attempt to stop sonar from going crazy when I accidentally type a number without properly giving focus.  
 
Of course, the keyboard shortcut name is hardcoded in the menu text, whether it works or not     Sometimes I really wonder about who they get to program around here.