Great fun - I have taken to increasing the 128 value to 512 or higher for the more glitchy looping (not sure if it needs to be those specific values though). Plus, we now have automatable loop points!
I really want to hook a meta-device up to this,
and now I know it’s possible.
just haven’t figured out the important first part of porting it over to work in the GlobalOscActions file.
something about observable device parameters and notifiers, I think.
somehow it’s possible to link meta-device parameters to an OSC client, route this internally to the OSC server that controls the start and end points.
the meta-device parameters to an osc client were discussed but the method didn’t surface,
client and server communication has been discussed with examples courtesy of vV.
The last piece of the puzzle that shows the methodology in a different shape,
is right here courtesy of It-Alien.
No,I clearly messed with the wrong variable - but it still gave me finer loop points. upon increasing it to 15000, it enabled me to do some glitchy style loops, but the range was limited to the 1st quarter ot the sample, but I understand this is a limitation of having just 128 values. Maybe implementing a LSB/MSB controller wil give us finer tuning?
Still, it’s nice to see all these little scripts popping up - it makes all this scripting lark a bit easier to absorb - I just wish I went a bit further than basic back in the days of amstrads and VIC-20’s!
two other MIDI actions could be added to let the user select the instrument and sample number of the target sample, so this script could be used in non-live situations, or in general to change the loop range of non selected samples
I don’t think there is anything in the API which allows to determine the current snapping mode, so there should be another MIDI action to define it. This done, it should be quite simple to accomplish.
by reading my last two messages, you probably have guessed that I’m out of spare time right now