Thanks, DG. I knew there was a preference for chasing "something", but couldn't remember what it was right off. It was for event chasing, and it works well.
The thing about KS's is that it's not quite the same as CC data. As far as DP is concerned it is note data, even though it is really patch change data in function only. Dealing with note data functioning as some other controller is a tricky in concept. Most all of what I've found on the internet about KS is either from spec sheets stating that a particular app or plugin was KS-capable, or from other forums where users are pondering much of what we're discussing here.
I won't deny that DP might have some minor feature needs, but then I'm not using the latest version, either. Note data is conveniently sounded when the scroll bar crosses over a note on or note off point, but DP doesn't know a keyswitch from a regular midi note and as far as I know won't simply play a note when the scroll bar starts at a point between the note-on or note-off location.
While I like the idea of KS's-- and appreciate them much more in VI than in PE, it seems that some of the behavioral issues might be better handled as Patch Change data instead. I can't even fathom the idea at this point of reconfiguring all of my matrices to wean them off of KS's. It would take at least a month.
I'll do my homework, and then I'll make a stink with MOTU about it. In the meantime, I'm curious to hear how Dave made out with splitting the extended KS notes at his marker points. For now, that seems like the easiest solution.
The thing about KS's is that it's not quite the same as CC data. As far as DP is concerned it is note data, even though it is really patch change data in function only. Dealing with note data functioning as some other controller is a tricky in concept. Most all of what I've found on the internet about KS is either from spec sheets stating that a particular app or plugin was KS-capable, or from other forums where users are pondering much of what we're discussing here.
I won't deny that DP might have some minor feature needs, but then I'm not using the latest version, either. Note data is conveniently sounded when the scroll bar crosses over a note on or note off point, but DP doesn't know a keyswitch from a regular midi note and as far as I know won't simply play a note when the scroll bar starts at a point between the note-on or note-off location.
While I like the idea of KS's-- and appreciate them much more in VI than in PE, it seems that some of the behavioral issues might be better handled as Patch Change data instead. I can't even fathom the idea at this point of reconfiguring all of my matrices to wean them off of KS's. It would take at least a month.
I'll do my homework, and then I'll make a stink with MOTU about it. In the meantime, I'm curious to hear how Dave made out with splitting the extended KS notes at his marker points. For now, that seems like the easiest solution.