I have made a TouchOSC (Mark II) iPad touch control screen for Scaler3 Leader Instance. Aside from some minor value issues (see below), everything WORKS.
I have some screenshots, and the actual TouchOSC file, here: (a fully secure/malware filtered dropbox public folder) :
Unzip the archive, and you’ll find five (5) screenshots plus the TouchOSC MkII file - which has some blank tabs, but notice the Leader tab and its two subtabs, Bind Zones and Main Chords Motion & Humanize.
QUESTION:
What of all the controls having configured host automation for Scaler3 and as I have setup successfully for a LEADER, would be useable (at all) on FOLLOWER instances? ie., controls having host automation separate for that channel that would NOT break the follower instance out.
Once we are clear on that, we will quickly lay in and show the blank Tabs with suitable for follower instances.
WIth only the most basic TouchOSC skills, anyone can easily change the MIDI channel or messages, colors, label names, and well you have the TouchOSC file, free for use or modification.
Our Scaler3 Leader Instrument Rack’s Macro Names, are humbly suggested of course (hopefully are useful, compact and clear). The MIDI learns to those MACROS can be absolutely anything as well, but I show a convenient range of continuous controllers (cc’s 16-31).
As our own suggested convention, and as part of a larger public domain MIDI specification for DAW users we are recommending for use with FreeSpace (non-contact) MIDI controllers and expoliting various supporting M4L and other devices and techniques, we are using a dedicated MIDI Channel 12 for Scaler harmonic and performance controls. This is implemented and up and running now in an Ableton Live 12 complex environment setup for up to 5 separate live performers and multiple external synth tracks each with its separate “follower” Scaler3 instance. Currently, this is complrised of one LaserHarp Guitar (beams sideways), one LaserHarp floor model (beams up), and choice of any mix of three additional keyboards and/or Akai MIDI Pads.
NOTE - a few of the Scaler3 provided host parameters had their data values spread unevenly (non-integer), so that no contiguous TouchOSC with mutual exclusivity (without extensive OSC programming), can cleanly show all the values needed and maintain exclusivity between that group of buttons. Perhaps, if there isnt another solution that I could be missing, Scaler3 might want to consider spreading out its host automation control values so that any grid or matrix control with an INTEGER gap in values can be used. It can start at any base value. Several Scaler3 parameters have non-integer gaps, which unfortunately are literally impossible to handle in a contiguous grid control maintaining exclusivity. And each of those Scaler3 controls’ respective data points must be exclusive since you can only select one at a time. So this was a challenge. Some grid control buttons in my experiment in TouchOSC in the zip, you’ll find, do not yet “hit” the desired CC value, but once I handle those (there is more than one possible way -however none are easy), I will update the TouchOSC here on the Scaler3 Forum.
