The midi files are what are known as tab delimited text files, meaning each piece of text is placed specifically in a grid pattern by using the character created by the Tab key to separate strings of characters into columns. The best editor for these files is a Spreadsheet editor (like OpenOffice). The bare minimum required by a ".remotemap" file is the following code:Ĭode: Select all Propellerhead Remote Mapping FileĬontrol Surface Manufacturer Manufacturer Name You can have zero automatic mappings defined in the map file if you prefer, but you must know what the required bare minimum is before gutting stuff out. Essentially this is the template file for how the MIDI hardware interfaces with items in the Rack if a device is right-clicked and "Lock to device" is selected. The ".remotemap" file defines automatic routing of the controls that were defined in the codec file. You can get a simplified list of the reserved CC numbers by placing an External Midi Instrument into a Combinator, selecting it in the programmer, and looking in the available items in the "Target" dropdown list named "MIDI CC.". You can define your own CC values and are not restricted to specific numbers, as long as you don't use the reserved CC numbers. Everything else is essentially a variable whose name can be anything. Only the names of the parameters within Reason that you intend to control matter. By that I mean you define what controls you want to use on your hardware by giving them names and then assigning values and CC numbers to them. The ".midicodec" file defines the names and CC assignments of all the controls on the MIDI hardware. In this folder you will find ".remotemap" files whose names match those of their ".midicodec" partners (this is important).īefore editing any default MIDI files, always immediately "save as" to a new file, then start working. On PC, they can be found in the following locations:Ĭ:\ProgramData\Propellerhead Software\Remote\Maps Together, these two files make one codec. These are actually made up of at least two files, one being the codec itself and the other being a Remote map file. MIDI hardware use files called "codecs" to run in Reason.
![propellerhead reason 7 control surface not detected propellerhead reason 7 control surface not detected](https://dt7v1i9vyp3mf.cloudfront.net/styles/news_large/s3/imagelibrary/r/reason2addedevolution-8Z7XUAKZpMpUfer2M4xfbrnbDCeDGl5z.jpg)
What I can do is try to shed some light on where you can start getting answers. I'm using your experience to highlight what badly needs to be fixed, as of several years ago.
![propellerhead reason 7 control surface not detected propellerhead reason 7 control surface not detected](https://www-vintageking.com.imgeng.in/media/catalog/product/cache/c8660c81d7196df55c33284290821786/s/t/studiologic-sl-mixface_114964_1.jpg)
There is no defensible explanation as to why this is so in this day and age. I'm not riffing on a lack of experience on your part or poking fun at all, this is just the way of it. I am sorry that this is such a daunting task for you, GushingDizzy. It is seen as an advanced feature that you must already be knowledgeable in to make use of.It is difficult for people to control Reason using hardware.
![propellerhead reason 7 control surface not detected propellerhead reason 7 control surface not detected](https://dt7v1i9vyp3mf.cloudfront.net/styles/news_large/s3/imagelibrary/r/reasonv301combi-u18WN685a8K22391xGCMyK96v55pr6ZV.jpg)
Work must be carried out across multiple files - each with differing syntax - without the option of opting for the in-app interface to cut down on the work involved. There is no robust in-app midi mapping GUI. I couldn't think of a better way to say it. Just describing the confusion is itself confusing.
#PROPELLERHEAD REASON 7 CONTROL SURFACE NOT DETECTED HOW TO#
Please take note of the disorientation regarding establishing an understanding of where to start, of why things that have been tried aren't working, of how to fix the problem(s), of what can or should be done, of when things should be done, and of why the things that should be done must be done instead of other things. "my MIDI controller has no map, how can I make my own?" If somebody from Propellerhead is reading this thread at some point, please pay attention.Ī newcomer to this forum has taken the sum total of their posts to date since joining to seek what should be simple answers to a basic problem: Even with the UC-33e I'm still about a half-dozen knobs/faders/buttons short of being able to have immediate hands-on for all the parameters of the NI Pro-53, which is my current favorite softsynth.(Caution: wall of text ahead, this got me in a mood.) With "endless" knobs, you can often avoid the sudden jumps in parameters described above, without having to visually reset the knobs to match the screen image.Ĭan't get enough faders and knobs and buttons AFAIC. The knobs are not the "endless" kind - in other words, they are at "zero" far left, and "full-scale" at far right, where they can't be turned any further either way.
![propellerhead reason 7 control surface not detected propellerhead reason 7 control surface not detected](https://thumbs.static-thomann.de/thumb/orig/pics/prod/227531.jpg)
That way you don't get a big jump in the paramters the first time you move a particular knob/fader. The "fix" is to get a visual look at where the knobs/faders are on the computer screen and move the UC knobs/faders to match them. (It would take a pretty expensive piece of gear to do this). One thing - when you change patches in the softsynth, the UC-33e cannot automatically move the faders/knobs to the same settings as the new patch. It's well designed, and gives you lots of faders/knobs/buttons. I use the UC-33e with a bunch of softsynths.