Hey @hypnosapien, I’m the Arcify author so I have a fair idea where the line between that library and the overall Norns behavior lies at this point.
At this point Arcify doesn’t have a way to hook into those “system” level settings like reverb level or overall volume because it uses the parameters from the script’s param screen. I imagine things like those are available somewhere, so it is probably possible to get Arcify to tap into them, but I haven’t figured It out quite yet. It’s something to put on the roadmap.
It seems like Arcify should be able to control things like the MLR track volume, but it is possible that it has not been exposed as a parameter, in which case you’d have to do that first. I’m not familiar enough with MLR to be sure.
If it is a param, then you should be good. I don’t think MLR has been officially “Arcified” but it should only take 4-8 lines of code plus adding the library to the lib/ folder.
In the short term, I’m intending to make Arcify a core library that’s distributed with the Norns and available to every script - although that doesn’t mean that they’ll all use it, but it will reduce the barrier to entry. Then with some well-placed pull requests we could add support to most scripts.
In the long term, I’d love to find a way to integrate Arcify at the system level so it just works, without users having to write any code at all, much like how midi controller mapping works. This is more complex.
As far as identifying scripts with arc support, they should all be tagged arc on lines and maiden. Most scripts with arc support have a deeper level of support than Arcify, they tend to use it as an integral part of the script (like Mangl)