I don't suppose there is NOT currently a way to have SPLAT search back specific custom keyswitch notes in a specific range, for instance C0 through D1
but wouldn't it be a nice idea to have a place to input specific custom search back for KS notes?
And also on a per channel basis?
Maybe the KS notes could be somehow linked to an unused controller # or those outer odd things I never have used like RPN and NRPN?
hummmmm ....

What a good idea! It could be implemented as "find prev" and "find next" options added to the context menu in the PRV.

Not sure I understand how you're seeing it but that's ok.
I think you're talking about how to make it work if it were an addition to the software?
---
An other thought ... there is still a program change search back that works in SPLAT?
I haven't used program changes since cwpa9 so I'm not sure.
Maybe it could be tied to that function in some way.
That was always (obviously) on a per channel basis.
Giving the PGC the ability to send a note number would get it done quite easily.
Is it possible that is already do able?
---
Oooo ... what about using banks in Kontakt? I belive bank numbers are tied to the ancient Midi PGC thing in some way.
---

Anyway... more detail ...
... I'm suggesting (or looking for) a way to have SPLAT automatically seach back the same way it does controllers.
Reason is, when I'm jumping around in a piece I'm working on that uses KS and have played a passage that uses C0 and then jump to the middle of a passage that uses C#0 without playing over the KS note at the front of that passage the instrument will play the C0 articulation as opposed to the correct one for that passage, 'because' there is no search back in the same way controllers like CC07 or CC11 will get a search back.

I wonder if there's a way to assign notes to be triggered by unused CC numbers.
There are enough unused midi CC to cover an octave of notes.
Problem might arise that one KS instrument might have different KS notes than an other so that's why I think about having it on a 'per track' basis.

Steve_Karl
Problem might arise that one KS instrument might have different KS notes than an other so that's why I think about having it on a 'per track' basis.

So per track "Search back events..." dialog, with precise selection possibility (key ranges, CC ranges, etc.)
User friendly approach will be to automatically detect that when possible. So may be "named sets", with a possibility to attach them to VSTi, or even create them, including on the fly, when possible (NKS?). Dreams 
 

Steve_Karl
I wonder if there's a way to assign notes to be triggered by unused CC numbers.
There are enough unused midi CC to cover an octave of notes.
Problem might arise that one KS instrument might have different KS notes than an other so that's why I think about having it on a 'per track' basis.

Such workaround will involve at least 2 steps:
1) after the track is recorded, convert required notes to CCs (permanently! otherwise CC search back will not work)
2) enable MFX processor which convert CCs back to notes in "real time"
Yes, possible. But it will work only if:
1) CC search back is really working well now (I have not checked for a while)
2) searched back CCs are sent throw MFXes (should be, but hard to be sure without checking)

Yea ... too complicated for me.

I think getting Program Change to have a category for note numbers would be the ideal way.

This would be awesome!
 
Right now I use a couple of scripts to convert Key Switches to CCs on the way in and then CCs back to Key Switches on the way out. It works, but it is a kludge. More libraries now support CCs for articulation changes, so it is becoming a little less of an issue, but YES to this FR!!!

I've just been dropping the KS notes in the obvious places when I'm jumping around.
A bit time consuming but bullet proof.

I would love Sonar to work with NKS so colours on the PRV corresponded to the colours on my keyboard for keyswitches, and have the ability to look back.

Pipe dream probably but where key switches are defined by a drum map it should be possible to implement something to better visualise and implement key switching.

Yes, my mind immediately went to a manual search rather than the automatic search-back feature you were talking about. That's because it would be much easier to implement and still help mitigate the issue of starting playback after a keyswitch event and having the wrong articulation.
 
The problem with search-back on a note value is that there is no way for SONAR to distinguish between keyswitches and regular notes. You'd have to specify a note range for the search-back. That setting would be both instrument-specific AND patch-specific. Not an easy thing to implement, especially if the instrument has more than one contiguous range of keyswitches.
 
And it would be prone to user error, since it would up to the user to inform SONAR where they are. If you were to substitute a different library or even a different patch, you'd have to then redefine the keyswitch regions.
 

bitflipper
Yes, my mind immediately went to a manual search rather than the automatic search-back feature you were talking about. That's because it would be much easier to implement and still help mitigate the issue of starting playback after a keyswitch event and having the wrong articulation.
 
The problem with search-back on a note value is that there is no way for SONAR to distinguish between keyswitches and regular notes. You'd have to specify a note range for the search-back. That setting would be both instrument-specific AND patch-specific. Not an easy thing to implement, especially if the instrument has more than one contiguous range of keyswitches.
 
And it would be prone to user error, since it would up to the user to inform SONAR where they are. If you were to substitute a different library or even a different patch, you'd have to then redefine the keyswitch regions.
 

Yes. Redifine for each instrument ...
maybe similar to the way Sonar maps for specific keyboards with instrument definitions
and be able to load any from that (continual work in progress) collected library of KS maps onto an individual track.

Damn the user errors. If you can't figure it out then shame on you. :-)

The way I find the KS notes now is I know the general range for that instrument
and just collapse the PRV and look in that range and there they are. Not that complicated.