How to save remote override as default?

This forum is for discussing Reason. Questions, answers, ideas, and opinions... all apply.
Post Reply
soguy
Posts: 22
Joined: 07 Jul 2016

22 Jul 2016

I'm using the Remote Override Edit mode to quickly map my MIDI controllers however, the settings are saved for the currently loaded device and patch. Is there a proper way to persist it as my default setup (not a template)? For example, let's say I would like my controller "A" to always control the NNXT FREQ knob using CC80. I know I can save custom mapping on my controller if it supports it but customizing it using the Remote Override Edit mode is easier and also not all controllers supports that.


I'm using the "<Other> MIDI Control Keyboard" setup in the Preferences.

Thanks in advance,
Guy

User avatar
jam-s
Posts: 3035
Joined: 17 Apr 2015
Location: Aachen, Germany
Contact:

22 Jul 2016

The best way would be writing a proper remote codec for your controller.

User avatar
motuscott
Posts: 3420
Joined: 16 Jan 2015
Location: Contest Weiner

22 Jul 2016

Can you not save your settings as a template song and have that song as your default song (prefs, general)?
Who’s using the royal plural now baby? 🧂

User avatar
Raveshaper
Posts: 1089
Joined: 16 Jan 2015

23 Jul 2016

If you want to create a specific mapping that happens automatically every time a certain situation takes place, this can't be done. You will always have to map the remote override, or lock the remote codec to the device (if it's written to do that).

Any method will involve having to set something up.
:reason: :ignition: :re: :refillpacker: Enhanced by DataBridge v5

User avatar
ljekio
Posts: 962
Joined: 21 Jan 2015

23 Jul 2016

You can save song as template with custom override and use it when start new project.

OverneathTheSkyBridg
Posts: 377
Joined: 15 Jan 2016

09 Dec 2018

I know this is old but I'd like to revive this. If an answer to this exists in another thread feel free to chime in! :)

I've got a Nektar Panorama so the thing esentially maps itself to most Reason stock devices and earlier REs. My favourite of those being the two Korg synths and my newly found Antidote. My question which I think lines up with the previous ones are: Wouldn't it be nice if you could set multiple remote mappings PER DEVICE in the same way you do it manually in Reason? If you could customize it so that every time Reason selected that type of device, no matter what the circumstance, YOUR pre-programmed remote settings would always persist.

My Korg Monologue never maps to the right function that the knobs are labeled. I understand the concept of CC MIDI messages and not everything lines up, but it would be cool to save device specific CC mapping to automatically adjust all mapping every time you select a different instrument (each of which could be programmed to your liking).

timbuk295
Posts: 11
Joined: 02 Dec 2018

09 Dec 2018

Agree. This would be cool.

Would having a 'global' remote overrides set resolve this problem?


Sent from my iPhone using Tapatalk

Patrickuk100
Posts: 6
Joined: 01 May 2019

29 Nov 2019

OverneathTheSkyBridg wrote:
09 Dec 2018
I know this is old but I'd like to revive this. If an answer to this exists in another thread feel free to chime in! :)

I've got a Nektar Panorama so the thing esentially maps itself to most Reason stock devices and earlier REs. My favourite of those being the two Korg synths and my newly found Antidote. My question which I think lines up with the previous ones are: Wouldn't it be nice if you could set multiple remote mappings PER DEVICE in the same way you do it manually in Reason? If you could customize it so that every time Reason selected that type of device, no matter what the circumstance, YOUR pre-programmed remote settings would always persist.

My Korg Monologue never maps to the right function that the knobs are labeled. I understand the concept of CC MIDI messages and not everything lines up, but it would be cool to save device specific CC mapping to automatically adjust all mapping every time you select a different instrument (each of which could be programmed to your liking).
Hi, Just found this as I was looking for a solution myself. I just built a custom controller and wanted to map CC's. I still haven't found a solution (well I have but it's not ideal). Firstly I read that Reason should be hacked to map my controller - not happening because this (IMHO) should be taken care of by the developers - I mean saving the CC not mapping my controller :) Secondly, it can be done by saving as a song (as mentioned previously), but not ideal because how do I have all my instruments as a template and decide up front which ones I want to use? (unless I'm of course talking nonsense). Thirdly, and the way I found out that I CAN save my mapping AND it will load automatically with any instrument is to ... erm...use Ableton. But there are many smarter people out there than me, so if there's another solution, PLEASE HELP :)

rmtcvolte
Posts: 205
Joined: 15 Nov 2018

29 Nov 2019

Hi Patrickuk100,

there is no need to "hack" Reason. Why you dont want to sign in as a developer and write your own codec and mapping?
Do you ever watched this: https://www.reasonstudios.com/developers

User avatar
Oquasec
Posts: 2849
Joined: 05 Mar 2017

30 Nov 2019

They give you all the propellerhead developer options if you ask em : /
Producer/Programmer.
Reason, FLS and Cubase NFR user.

Patrickuk100
Posts: 6
Joined: 01 May 2019

04 Dec 2019

Oquasec wrote:
30 Nov 2019
They give you all the propellerhead developer options if you ask em : /
Thank you. I will go down this route.

Patrickuk100
Posts: 6
Joined: 01 May 2019

04 Dec 2019

rmtcvolte wrote:
29 Nov 2019
Hi Patrickuk100,

there is no need to "hack" Reason. Why you dont want to sign in as a developer and write your own codec and mapping?
Do you ever watched this: https://www.reasonstudios.com/developers
Thank you for the link; it looks very interesting.

rmtcvolte
Posts: 205
Joined: 15 Nov 2018

05 Dec 2019

For me it looks like Reason Remote is a totaly underestimated tool. Maybe it helps you any further to share where I'm found informations helping me getting started:

https://www.reasonstudios.com/blog/control-remote
https://www.soundonsound.com/techniques ... ason#para4
http://www.reasonremoter.uk/
https://koshdukaimusicreason.blogspot.c ... emote.html
https://refigur8tor.readthedocs.io/en/l ... eason.html

But the doorbreaker for me was to sign up as a codec developer and getting the sdk and tools from ReasonStudio. As long as you are using standard midi cc's and nothing unusual with your midi controller, it should be not a big deal to write a codec. If you face problems, feel free to ask.

User avatar
Luxuria
Posts: 149
Joined: 17 Mar 2016

05 Dec 2019

rmtcvolte wrote:
05 Dec 2019
For me it looks like Reason Remote is a totaly underestimated tool. Maybe it helps you any further to share where I'm found informations helping me getting started:

https://www.reasonstudios.com/blog/control-remote
https://www.soundonsound.com/techniques ... ason#para4
http://www.reasonremoter.uk/
https://koshdukaimusicreason.blogspot.c ... emote.html
https://refigur8tor.readthedocs.io/en/l ... eason.html

But the doorbreaker for me was to sign up as a codec developer and getting the sdk and tools from ReasonStudio. As long as you are using standard midi cc's and nothing unusual with your midi controller, it should be not a big deal to write a codec. If you face problems, feel free to ask.
Thanks for this post! This was exactly what I needed to realize I'm right in that my MIDI gear isn't being used to it's fullest potential.

I'm going to try to map RE's customizable to my AKAI LPD8.

Were the dev tools for codec easy to get?

kefkekeyser
Posts: 36
Joined: 24 Feb 2015

05 Dec 2019

Why do we need to edit text files to automatically map a controller? Why is Reason stuck in the 90's? Other hosts like Studio One have a system that they call focus mapping: you just map you knob or whatever to a knob in a plugin (via the GUI like a normal person) and that mapping is saved. The mapping is then automatically loaded the next time when you open the plugin and the plugin is in focus. No drama with trying to figure out what the hell all that shit is in those remote files, just do all via the GUI.

Reason should really do a total rework of how mapping works, fiddling with text files is so 90's and it make me angry that they still did not change that.

User avatar
MannequinRaces
Posts: 1543
Joined: 18 Jan 2015

05 Dec 2019

kefkekeyser wrote:
05 Dec 2019
Why do we need to edit text files to automatically map a controller? Why is Reason stuck in the 90's? Other hosts like Studio One have a system that they call focus mapping: you just map you knob or whatever to a knob in a plugin (via the GUI like a normal person) and that mapping is saved. The mapping is then automatically loaded the next time when you open the plugin and the plugin is in focus. No drama with trying to figure out what the hell all that shit is in those remote files, just do all via the GUI.

Reason should really do a total rework of how mapping works, fiddling with text files is so 90's and it make me angry that they still did not change that.
Agree with this 100%. For a company that prides themselves on ease of use and make music faster the remote codec needs an overhaul.

rmtcvolte
Posts: 205
Joined: 15 Nov 2018

06 Dec 2019

Hi Luxuria,
dont know how it is today, when I'd sign in it was easy. Fill out the form, sign in, give them a few days.

And for the complainers:
If you are satisfied with simple mapping, the aproach of StudioOne is OK. But if you like to go beyond simple one to one cc matching in 0-127 range, you will end up with scipting a *.xml file, without any documentation.

By the way, there was an anouncment in this forum for a tool to generate mappings a few days ago.

User avatar
mcatalao
Competition Winner
Posts: 1824
Joined: 17 Jan 2015

06 Dec 2019

MannequinRaces wrote:
05 Dec 2019
kefkekeyser wrote:
05 Dec 2019
Why do we need to edit text files to automatically map a controller? Why is Reason stuck in the 90's? Other hosts like Studio One have a system that they call focus mapping: you just map you knob or whatever to a knob in a plugin (via the GUI like a normal person) and that mapping is saved. The mapping is then automatically loaded the next time when you open the plugin and the plugin is in focus. No drama with trying to figure out what the hell all that shit is in those remote files, just do all via the GUI.

Reason should really do a total rework of how mapping works, fiddling with text files is so 90's and it make me angry that they still did not change that.
Agree with this 100%. For a company that prides themselves on ease of use and make music faster the remote codec needs an overhaul.
I'm working on a tool to edit the remotes in a graphic way. Release is very near, but i still have some quirks to work out...


User avatar
raymondh
Posts: 1776
Joined: 15 Jan 2015

06 Dec 2019

mcatalao wrote:
06 Dec 2019
MannequinRaces wrote:
05 Dec 2019

Agree with this 100%. For a company that prides themselves on ease of use and make music faster the remote codec needs an overhaul.
I'm working on a tool to edit the remotes in a graphic way. Release is very near, but i still have some quirks to work out...

That's very cool!

disco81
Posts: 4
Joined: 31 Dec 2022

08 Jan 2023

raymondh wrote:
06 Dec 2019
mcatalao wrote:
06 Dec 2019


I'm working on a tool to edit the remotes in a graphic way. Release is very near, but i still have some quirks to work out...

That's very cool!
I second that, please give us heads up when this is going ahead, looking forward to it! :puf_smile:

Post Reply
  • Information
  • Who is online

    Users browsing this forum: TheSixthUndead and 18 guests