Yes, you could use pitchbend messages in order to access more than 128 values. But you might need to get the calculator out to determine what values to send 
These options are for using the SAFP in the global rackspace, and do not use local rackspace variations or snapshots.
By sending the midi message to the “Local GP Port”. This is a special internal midi port that widgets can be learned/linked to.
Song Part Properties
- Access the MIDI Helper Tool.
- Choose the Local GP Port as the MIDI device
- Decide on a CC to use to control the Track Number widget. I’m using CC 84. To select the first SAFP Track, use CC value 0.
Widget Properties
-
After adding the SAFP to the global rackspace, map a knob widget to the Track Number parameter.
-
On the MIDI tab, click the Edit button and then manually choose the Local GP Port and the CC number you chose earlier.
-
On the Value tab, change the Max value to 12.7. This is necessary because the SAFP can support 1000 tracks, while a MIDI CC only has 128 different values. Reducing the max value does mean that you can only access 128 tracks in the SAFP, but that is the maximum number of CC values that you can send, unless you switch to using something like Pitchbend messages, which have 16K values.
The end result is the song has an explicit link to the SAFP track. So even if you change the Song order, it will still select the right track. You just can’t change the track orders in SAFP.
EDIT: If you require access to more than 128 files/tracks in the SAFP, you can instead use Pitch Wheel messages. This csv has the required Pitch Wheel LSB and MSB values to select each track in the SAFP (up to 1000 tracks).
SAFP Pitch Wheel to Track Number Conversion.csv (16.2 KB)