This is a follow up to the thread:
It’s a pretty logical FR and till it gets implemented, I thought that this can be a good case to demonstrate the power of the Direct Access functionality found in the newer MR API versions.
The Sampler objects, are similar to the Instrument ones, they have a slot which holds the parameters. So if one logs the parameters exposed, can then control them with relative ease using the methods of DA.
Here’s the midiremote installation file of the snippet I’ve prepared:
Test_Sampler Track.midiremote (10.5 KB)
I use loopMIDI ports (under Win) but you can obviously change them to your liking.
I recommend to have a look at how I handle the host values involved, by taking advantage not only of DA but also of the custom Host Values entities.
The Sampler parameters are setup in the file samplerParams.js. You can alter the position of the various parameters in order to comply with the way you want them shown in each parameters’ bank.
For testing purposes, I created a tiny HTML MIDI Remote surface, which can be found in the script’s folder after installation.
Finally, the script handles instrument tracks as well. Whenever we select an instrument track, the controls properly adjust to these of instrument (synth) type, while when we select a sampler track the custom handlers get activated. This is done by toggling through two subPages.
A short video demonstrating the snippet:
