Notifications
Clear all
Unify Feature Requests
4
Posts
2
Users
0
Likes
585
Views
Topic starter
June 7, 2020 2:41 pm
This suggestion arises from the Reason Rack Plugin but may be more general..
With Unify macro controls, when linking to parameters inside the Reason Rack Plugin VST, this essentially works very nicely and I couldn't be happier. However one thing I've noticed is that the linkage is tied to the device patch name rather than the device instance. This has the effect that linkages become invalid if the device patch is changed.
For example I can create a macro parameter link to inst/1/plugin/'My Bass:Filter Freq' corresponding to an instance of a Reason Subtractor device, but the parameter link becomes invalid if the Subtractor's patch is changed to anything other than 'My Bass'.
I can see some advantages to this, but is it possible that parameter links could be addressed to the device itself rather than the device patch? eg. inst/1/plugin/Subtractor1/'Filter Freq' or possibly inst/1/plugin/Subtractor1/CC:74
This would be a great help in creating re-usable macro presets. It would also be a great help if parameter links could be saved per macro knob and subsequently loaded to merge or replace the existing knob settings.
June 7, 2020 3:28 pm
What you're asking for is very challenging. In your first example, the "inst/1/plugin/" part of the path is under our control, but the "'My Bass:Filter Freq'" comes as one fixed lump out of Reason Rack, and is not something we can control.
I'd suggest sending this question to Reason Studios (ideally with a bit of background about Unify).
Topic starter
June 7, 2020 6:14 pm
"'My Bass:Filter Freq'" comes as one fixed lump
Oh ok, that's a shame. I presume it doesn't also offer an alternative parameter ID which persists regardless of the patch loaded.
Might it be possible to expand on the numbers of CC messages passable to a plugin from Unify?
Might it also be possible to pass CC messages out of a plugin to Unify?
These two questions obviously form a circle for the possibility of using MIDI effects capable of outputting CC messages to other plugins which are capable of receiving CC messages; but also as regards macro parameter links - it might be a workable [additional] option if CC's were addressable: eg. inst/1/plugin/CC74
For Reason at least, this would allow creating a workable macro preset for a whole range of devices which in this case use CC74 for filter cutoff, and the parameter link would remain valid even if the device patch was changed or the device itself was swapped out.
Topic starter
June 7, 2020 9:38 pm
For anyone else who might be interested, I have found a partial workaround, and that is to manually label the device(s) inside the Reason Rack instead of allowing the default automatic re-labelling of a device according to the patch name.
eg. Edit the device label and call it My Device. This name will persist regardless of patch changes and your Unify macro parameter links will remain valid. Yay.
