Thanks. Still confused but I appreciate your help.
Hi guys. here is what i do with bome midi translator pro. here they are keyboard shortcuts that make plugin inserts. next step (tomorrow) my bcr2000 will send an NRPN midi message and bome will do the same job for you. in 500 milliseconds you will insert and control your VSTFX. when i finish this part i will do the VSTI part
1 Like
bome midi translator also tells the bcr2000 to put on the correct preset in order to edit the vstfx. the bcr2000 uses the graphic formatting of the parameters. so visually we have the parameters which are distributed in the same way on the screen and physically on the bcr2000.
1 Like
Eh? For standard (vast majority of) controllers it will just be a case of entering the control type (Endless/Standard Knob, Fader or Button), and what the CC value is. Everything else will be mapped within Cubase as per the users preference, so there’s no wasting of time as we all have preferred workflows.
I’d imagine the API would only be responsible for informing Cubase what hardware controls exist and how it communicates. I very much doubt the mapping to each plugin goes through it, that’s part of the new Remote Editor screen.
i.e. i’d imagine it would be something along the lines of:-
So you could go in and add 4 more faders (fader5,6,7,8 etc) and their midicc values which matches your hardware setup by copying and pasting. OR map your hardware as per the cc values that exist already - i mean, there’s going to be standard templates for a starter which will cover most 8x fader, 8x rotary style setups, and variants of.
If there was a chance to position those elements freely too, they could then encapsulate those id’s such as:-
<id=‘fader1’ posx=‘10’ posy=‘10’ height=‘25’ width=‘25’ />
<id=‘fader2’ posx=‘50’ posy=‘10’ height=‘25’ width=‘25’ />
<id=‘fader3’ posx=‘90’ posy=‘10’ height=‘25’ width=‘25’ />
<id=‘fader4’ posx=‘130’ posy=‘10’ height=‘25’ width=‘25’ />
It’s quicker/easier to do than clicking around an interface, which is fixed and reliant on Steinberg to maintain. Not to mention prone to many bugs. At a later date Steinberg can just add new parameters to the API without having to worry about updating or managing a GUI for it, meaning more chance of this progressing as key commands list does.
i.e. if they added an option to rotate elements on screen it could just be used in the supporting files:-
<id=‘fader1’ posx=‘10’ posy=‘10’ height=‘25’ width=‘25’ rotate=‘45’ />
i.e. If they added ability to bring an image in:-
<type=‘image’ src=‘…/companylogo.png’ posx=‘25’ posy=‘5’ />
At least, i’m hoping that’s where Steinberg are taking this. 
Cool! Can you link to the documentation?
Very excited for this to become a reality!
Better automation for routing and setting up tracks would be great.
I also hope we can get selected track name, info, plugins etc for for automation software.
1 Like
MIDI API will be released with maintenance update ?
No. As @Matthias_Quellmann said there’s no more that the SB staff can say.
I think it would be best to close this topic for the moment.