Sterioevo wrote: ↑28 Feb 2021
The max device allows you to map standard midi messages directly to RRP parameters you have configured to be available In the RRP rack container. To save these mappings you would need to group these devices and save as an Ableton Rack.
Once saved, this template can then be reloaded and used without any further configuration. This also means you can change track and the controller will follow, as it uses track midi messages that are exposed and can be mapped directly to control the RRP.
OK, so it sounds like it has the advantage of using the track midi rather than the remote MIDI in Live, so I am not locking controls to those parameters. It's still unfortunately a bit of an inspiration-breaking workflow for me, if I have to:
1) load devices / patches into RRP
2) map parameters into Live's device container
3) map the max device to those controls in the device container?
4) map my midi controls to the max device.
and then repeat for each track and if I change device in RRP....
there seems to be no consistency between the parameters that the RRP exposes for different devices
I'm not sure I follow this as for me *all* the parameters I'd expect in RRP are "exposed" as they are mappable to Live's device container.
Or did you mean there is no conistency between the numbers assigned to the parameter? I don't think there can be. You can have multiple devices in RRP. So if you have 6 subtractors, a NNXT, a player device, and some effects etc, then the filter cutoff for subtractor 5 cannot be the same parameter number in Live as subtractor 1 or 2 for example. RRP/Live needs to assign these paramater numbers in a bespoke fashion every time as each rack can be different.
By taking this approach you should then be able to hotswap templates with a consistent controller layout, as well as switch from track to track as required.
I don't think this can work, unless you have exactly the same rack configuration each time, in which case you can probably save a Live Instrument Rack without using the m4l device; even then I am not sure if the same parameter numbers would be assigned every time and if it could break the mapping if not - would need to check. I don't think it would be able to create "presets" for the m4l device that are going to work with whatever Rack you put together in RRP.
Appreciate the discussion and suggestion, please reply again if anything I have misunderstood, but I don't think this really solves the issue for me. I do think it would be quite easy for Reason Studios to provide this functionality. I made two suggestions in my message to them, but thinking it through my second suggestion makes most sense - for them to just implement right-click midi learn within the RRP.