ReasonUser wrote: ↑19 Aug 2017
Well I've got the bcr2000 and excited to have the drivers installed and codec up in Reason. I've not updated the remote map with your RE updates yet.
Regarding Reason's internal synths... Are they fully mapped? Malstrom for instance is not complete, and the preset <- -> buttons don't seem to do anything to get the extra controls. Are the mappings listed anywhere or is it just trial and error for the core devices? Remote override does not give the details for core devices.
Regarding the hardware, I love having the physical knobs and visual led rings for current values. My top row of push dials do seem slightly 'off' in that the one all the way to the left requires a bit of force to turn and the one all the way to the right is super light to turn. Cheers!
UPDATE: So I noticed even the core devices are included in the bcr2000.remote file. It's interesting why the "remote override" function shows the correct mappings of everything but the core devices. These seem to default to some "standard mapping" of one of my sound card's MIDI-out port. Even though, the BCR2000 is controlling the core device per the remote map file's designations.
Oenkenstein, your maps are working great so far. Is there any documentation on working with the bcr2000.remote file, or remote maps in general? I probably have some REs that have not been mapped yet and could contribute to the work already done.
Not all the native Reason devices have all their properties fully mapped. Malstrom is one of them, as you can see when you go to the Remote Override Edit Mode.
- MalstromMapping.jpg (114.53 KiB) Viewed 5378 times
The Preset < and > buttons are assigned to a 'next page' with mappings for only the Rack Extensions supported by my BCR2000.remotemap. The native or core devices, like the Malstrom, which have a lot of properties are using the 4 Encoder Group buttons on the BCR2000 to go to 'the next page'.
Thank you so much for offering your help with adding the uncovered Rack Extensions. Information about how to alter an existing remotemap can be found on this forum, but the information is scattered in several threads or sources. I am really busy at the moment (developing / beta testing) and it takes some time to explain the whole process, but I'll hope to provide a step by step guide on how to change an existing remotemap this weekend.