Remote: Selecting Previous/Next Single Mixer Channel

[Tiefflieger Rüdiger]

When remote controlling a single mixer channel (https://docs.reasonstudios.com/reason13 ... xer#533093), is there a way to select the previous/next single mixer channel from the external controller?

I want to build a remote map that controls a single mixer channel's properties (Level, Input, EQ, Dynamics, ...). For this to be useful, it should be possible to quickly switch to another channel without using the mouse. The only ways I found to do this at all are surface locking to the mixer's channel (requires mouse) or by selecting the mixer channel in the sequencer (if available) or in the rack on its grey arrow at the left side (again, requires mouse). So far, I haven't found a way to do this from an external controller.

There's the scope "Reason Master Section" which has "Remote Base Channel Delta", "Next Remote Base Channel" and so on. While that would work, it is a hack as it influences also the base channel of other controllers which I don't want.

[electrofux]

It is possible but since the Mixer is big with alot of parameter it requires alot of mapping and some coding. Basically you need to write your own codec or heavily adjust an existing one.

Basically you can adress the whole mixer as one device with all its parameters and define eg 64 groups (1 per channel). It is going to be a bit complicated programmingwise because i assume you dont have 64 buttons to select each channel individually but with some knowledge of the Remote API you can program a stepping through the Channels with two buttons or an encoder. it is just not something that you can do within minutes and not solely in the mapping file.

[Tiefflieger Rüdiger]

It is possible but since the Mixer is big with alot of parameter it requires alot of mapping and some coding. Basically you need to write your own codec or heavily adjust an existing one.

In which way would the codec have to interact with the remotemap? I wasn't aware that was even possible, but the doc I found was for Reason 6, so this might have changed ...

Basically you can adress the whole mixer as one device with all its parameters and define eg 64 groups (1 per channel). It is going to be a bit complicated programmingwise because i assume you dont have 64 buttons to select each channel individually but with some knowledge of the Remote API you can program a stepping through the Channels with two buttons or an encoder. it is just not something that you can do within minutes and not solely in the mapping file.

Interesting idea. I could write a small script that takes care of generating the final result from the first channel.

I wonder if this will work out though. I have a controller with 16 knobs, so I might need 3 to 4 groups to map all controls of a single channel to the device. Would your suggestion require to switch groups three/four times until I'm at the next channel? Or can groups have hierarchies so that the channel groups would be one level up requiring only a single group change?

[jam-s]

I think the Remote SDK has those questions covered. You can find it here: https://developer.reasonstudios.com/dow ... r-products

[Tiefflieger Rüdiger]

The SDK says that you can have up to ten variations per scope (the SDK seems to call this sometimes Groups and sometimes Variations). So with a 16 knobs controller needing somewhat 3 to 4 pages for all controls per channel, at roughly the third channel I'd run out of available variations for the scope. So I guess this approach won't work?

[jam-s]

Mapping the controls of one complete mix channel and then two additional controls to increase/decrease the mix channel base should work just fine. Maybe stripping down or editing the BCR codec from Mixer Jaëxx could be a good option: https://www.jaexx.com/blog/reason-using ... nel-strip/

[Tiefflieger Rüdiger]

Mapping the controls of one complete mix channel and then two additional controls to increase/decrease the mix channel base should work just fine.

That's what I currently do. But moving the base channel affects other control surfaces like my D 400F fader bank which is why I wanted to avoid this.

[electrofux]

I have a codec with 32 Groups so i guess Variations and Groups are treated differently.

[Tiefflieger Rüdiger]

I have a codec with 32 Groups so i guess Variations and Groups are treated differently.

Then there must be a difference between the two. Thanks for clarifying. I'll try to solve this with groups as we initially discussed. Maybe I'll also understand the difference between variations and groups along the way.

Do you know if it's possible to ensure that with one button I'm switching to the group of the next mixer channel and with another button I'm switching to another mapping (like from EQ to dynamics) of the current channel?

[electrofux]

i mean in the codec alot is possible. Once you are in remote process midi and have detected your controllers midi from eg the next/previous buttons you can act upon this with all the programming methods available. But for the Mixer this is a huge task because of the sheer number of items to keep track of and assign conditionally.

What controller do you use?