Parameter Window for DAW's or for Reason

6 posts / 0 new
Last post
q-logic
q-logic's picture
Parameter Window for DAW's or for Reason

Hi there all

I am using the B-Controllers from Behringer both BCR and BCF2000 in Reason DAW. What I was wondering is:
Is there a way to use BC Manager to have a parameter Window that show what all knobs and buttons do in the different Rack Extentions in Reason via monotoring the USB data traffic. The thing is that these controllers do not have any LCD diplay that show what the knobs or buttons is used for so you the have to use overlays. This overlays are not easy to make. But if there was a way to intercept the data that goes between the controller and Reason so that it could show what each knop and button does in a layout as the controller, that would be nice. :)

Do any of you know of any way to do this?

 

Q-Logic

Mark van den Berg
Mark van den Berg's picture

BC Manager already contains a facility to show which Reason parameter each BCF/BCR button/encoder/fader controls, if that is indeed what you're after.
In the B-Controls window, execute 'Import Reason map' from the B-Controls pull-down menu and open BCF2000.remotemap or BCR2000.remotemap from your Reason installation. This should create one or more new BCF/R2000 'contexts', in which the assignments of each Reason device are shown in a BCF/R preset.
See section 21 of the BC Manager manual for further details.

Actually I'm not sure if this facility still works with Reason versions later than 7:
Propellerhead have often changed the format of these remotemap files, so I used to lift these files from the demo of each new version and then adapt the import routine accordingly, but I stopped doing that when Propellerhead started requiring people to register even for the demo. So if you have Reason 8 or 9, please let me know if the import routine still works, and if it doesn't please send me the remotemap files so I can adapt the import routine.

q-logic
q-logic's picture

Hi Mark.

and thanks for the reply.

Yes this is cind of what I needed but stil not there.

  1. Import of .remotemap files still Works in Reason 9.1
  2. If you want I can't send you all the new .remotemap files in a zip so you can still continue to implement them?
  3. The layout of the map is not graphically easy to use when it doesn't look like the BCR or BCF. So I was wondering, is there a way to make the view of the controller graphically like. With rotary knobs and buttons? The other thing is the value return from Reason, is that posible to get in a box under the name of parameter?
  4. Behringer made a Java software to these controllers and there are all the graphics for the layout, if you need it?

 

But stil it helped some. :) So thanks so much for a good solutions.. :)

Q-Logic

Mark van den Berg
Mark van den Berg's picture

1. Good to hear, and in fact somewhat surprising, given the frequent format changes Propellerhead applied to these files along the way from Reason 3 to 7.

2. Yes, it would be very helpful if you could zip Reason 9.1's BCF and BCR remotemap files and mail them to me.

3a. When I developed BC Manager, my first priority was getting it functionally correct, i.e. concerning the editing of all data structures. That's one reason why the 'Layout' windows don't attempt to be a 1-to-1 graphical match of the actual BCF and BCR.
I'm not sure how useful a separate, 'graphical' window would be: at least concerning the writing of presets, the current Layout windows are hard to beat functionally. And some people already complain heavily about BC Manager's 'steep learning curve', in part because of its large number of windows... But I'll think about it.
However, BC Manager does provide a 'print strips' command: you can cut out the printed strips and put them on a real BCF/BCR, possibly glueing them on an overlay. Hopefully the next version of BC Manager (>=2017) will print these strips in the colors defined for each button/encoder, and maybe it will even print actual overlays so that you only have to cut out the holes for the button and encoder rows, although I'm not sure how practical that's going to be.

3b. 'Value return from Reason': you mean when you rotate a knob on Reason you want to see the value displayed in BC Manager? That's tricky:

  • Assuming you're using the BCF/R's USB connection (rather than its MIDI I/O sockets), you have to create a virtual MIDI device (or 'pipe' as I call it in the BC Manager manual). On Windows I recommend loopMIDI; IIRC this facility is in-built in OS X.
  • You must direct the MIDI pipe's output to the BCF/R and to BC Manager. On Windows this can be done via MIDI-OX.
  • In Reason you must redirect the MIDI output for the BCF/R to the MIDI pipe's input.
  • In the current version of BC Manager (and MIDI Tools) you can use the MIDI controllers window (main window -> View -> MIDI -> Controllers) to display the raw MIDI values that are being received. Developing a more sophisticated display tailored to Reason would be a lot of work.

4. Are you talking about Behringer's bc editor (which IIRC was abandoned at the alpha stage)? Anyway, I'm not very familiar with Java, but thanks for the tip: I'll take a look at it if and when I try to come up with either a 'print overlay' facility or a graphical window.

Mark

Mark van den Berg
Mark van den Berg's picture

Thanks for sending me Reason 9.1's BCF/BCR remotemap files.
The very same files were already used by Reason 6.5.1, so it's obvious why BC Manager's 'Import Reason map' is still working with 9.1. smiley

Mark van den Berg
Mark van den Berg's picture

I haven't kept up with Reason in the last 4 years, so I'm just curious:
On https://en.wikipedia.org/wiki/Reason_(software) I see that lots of new devices have been introduced since 6.5, so why haven't any of these made it into the BCF/R remotemap files? Have Propellerhead just given up on these files?

From versions 3 to 6.5 I had to adapt BC Manager's 'Import Reason map' routine whenever Propellerhead had added a new device and/or altered the file format, which practically happened with every new version - much to my despair. So in a sense I'm glad these files have stayed the same for the last 4 years...