Noel G. wrote:
This has been requested since Record V1.0 was released. When do you plan to release your tutorials on this?
Thanks!
For all my genius, I am currently rebuilding my life after a rocky forced relocation from the rural area where I had been living. That's a whole different story, but it suffices to say that I am presently unable to put together these tutorials indefinitely. I would have to fund that endeavor entirely through crowd sourcing and that's ridiculous.
The reason I have not dashed something together is because I am currently revamping the architecture into something that will potentially work much better.
Currently, as I have said elsewhere, each fader must be manually setup by the user inside of the Remote Override Edit Mode. This is clunky. My new design will make it possible to create fader groups by typing in suffixes at the end of channel names. This will allow fader group assignment to be dynamic without the user needing to go to a lot of extremes.
Also, this goes far beyond mere fader grouping. Faders can link to device controls, CV can be sent over EMI to drive adjustments in the SSL, and with the new architecture even things like VU meter levels will be unlocked and capable of acting as data sources that can be used to make manipulations somewhere else.
The architecture, collectively known as RackNode (previously bundled inside the MetaPads family of experiments), currently works by taking a host control and sending its value out across up to 128 outputs that can each be programmed to have their own min and max settings, complete with automatic inversion. This is all whiz bang and terrific, but you need to set everything up and it takes a long time.
The new architecture will be able to work with the current one, but it focuses on surface locking to specific device types. Instead of having to setup source controls manually, they are all setup automatically as auto inputs within the remote map and the script simply gains focus for the targeted device once it's locked. From there, the data can be routed in Remote Override Edit Mode from a list of available remotable items named for each data source and output number (Attack Out1, etc).
My biggest challenge in the redesign is the SSL. It's a mammoth monster of a nightmare to wrangle with 92 items per channel strip, 64 channels supported, 101 items in the master section, and almost 200,000 items in total at last count (including the planned number of outputs).
So, as a super long winded answer to your question: I am swamped right now. This is not just fader groups, this is a sot patch to the core app written in Lua and loaded in using Remote. But I'd love to be able to make videos about it. I know people are excited to see it working.
Thanks for the encouragement, I'm still working really hard on these things.