With regards the unassigned buttons… if i assign these in MIDI Remote directly, does the system remember these or are they lost once the script is reloaded?
When a button lights up while pressing shift, it means it has a dedicated function mapped to it while Shift is held 
There are tiny Layer2-specific buttons below each Layer2-enabled button that you can use to map Layer2 functions individually.
I will consider adding a config option for it 
You can’t remove a factory mapping, but you can overwrite it in the MIDI Remote Mapping Assistant
They are generally remembered but might be lost when updating the script. You can also choose whether you want a mapping to be stored globally or per-project only.
Hi! I have 2 issues on this script… if there is someone who can help me please.
First of all when the script is loaded I get this error:
TypeError: undefined not collable (property ‘makeRepeating’ of [object Object]) (line 4201).
I don’t how to fix this.
And the second problem is that Qcon Pro G2 only works with the MixConsole 1, and all the tracks on the MixConsole 2 are not shown on the Qcon Pro G2.
Before I bought the Qcon Pro G2 I used to have all my sessions on Cubase organized on 2 Mix Consoles because of the resolution of my screen it was easy for me to work this way… so it would be great if the Qcon Pro G2 could handle all the tracks no matter if they are in MixConsole 1 or 2 or whatever.
Thanks!!
thanks bjoluc you are a legend.
Been tinkering around with the script (i’m not a developer but just been curious to figure out some parts).
one line I did add was on row 6518:
pushToggleValue: mixerBankChannel.mPreFilter.mPhaseSwitch
I’ve noticed this before where MCU requires full turn of v-pot to turn Phase on/off, which is a bit laborious. So copied this line from elsewhere and voila it worked!
I also tried turning the Rec buttons into Read buttons as I hardly use them, but ended up turning it back. But it did demonstrated many of these assigns can get moved about.
Thanks for explaining the Layer function. Previously on the F-buttons only F8 worked with Layer 2, but now all 8 work. So if Shift was fixed on the F-buttons that would allow 3 assigns per button.
Regarding the subpages (shift), I note some have them (mainly transport) and some not.
(e.g. Shift+Read was ‘Read All’’ Shift+Pan was ‘Stereo Panning’)
Is this also same current limitation in Midi Remote as with the F-buttons, or more a case of adding to the script?
Hi maikerlburge,
Mackie protocol tracks to MixConsole1.
(But it would be neat if the Shift button could be assigned to open MixConsole2)
Midi Remote does not currently follow the MixConsole Visibility Configuration, but rather adds all tracks in your project. (though in the script some like input/output are excluded).
Steinberg Mod on separate thread has mentioned this is on their backlog of fix/enhancements.
Thanks jed_dexter. It’s sad that Mackie only works with MixConsole1. I can fix it adding all the tracks to MixConsole1 anyway, but wish it could read all the consoles.
Any thoughts on the error that Cubase give when loading the script?
The script is loaded anyway but I don’t know if it can be fixed
The script message:
TypeError: undefined not collable (property ‘makeRepeating’ of [object Object]) (line 4201)
Thanks again
If anyone is interested in a solution for this issue about Mackie protocol only working with MixConsole1.
I ended up open 3 different Consoles at Cubase, so MixConsole1 has all the tracks I like to see on the Control Surface, but I keep it closed, not showing on the desktop screen. And then MixConsole2 and 3 has all the tracks configuration that I wanna see on the desktop screen, and keep them open. That’s it.
Nevermind
@bjoluc (or anybody else 
)
Hi,
Do you think your script will work with an ICON QCON PRO 1st gen.?
I have one lying around and will set up my new recording space by the end of the year, so I can’t try it for myself right now.
Thanks for your insight,
Ralf
@bjoluc
First of all, thank you for the iCON QCon Pro G2 MIDI Remote Script. Great work! How can I assign functions to the function keys “F1-F8”? Unfortunately, I can use the script in Cubase pro 13 and 14, but I can’t edit it because the surface editor script in the Midi Remote Manager is marked with an “X”! Is there a way to add your own functions? FYI: I followed the instructions on GitHub 
Thanks in advance and best regards.
Hi, is there any way to have the track volume values show up in the display screen for the Pro G2?
Hi Bjoluc,
I’m still really enjoying using my G2 & 2 x extenders with this script in Nuendo, and now that N14 makes use of visibility settings it’s even better!
Now for the ‘please sir, can I have some more?’ bit of the post… is it in any way possible for your script to allow the ‘locking’ of specific channels in a project to specific faders? My use case is for film/tv post mixing and I would love to have a group of 8 channels (mainly my Groups) locked to the first 8 faders, with the other 16 faders acting as normal with regards chasing channel selection and changes in visibility?
Cheers and thanks for all your hard work,
Simon
Think I’ve solved my own request by utilising left zones and moving the Groups up to the upper divided track list in the project window. This seems to keep all my Groups (DX, BG, SFX, MX D, Feet, Hands, Props, MX) locked to the main 8 faders, with utilising ‘Show Channels that are Connected to the First Selected Channel’ to then bring up those channels on the 2 extensions 16 faders. Seems to work ok, if a little fiddly from the Project window (anyone know why ‘Show Channels that are Connected to the First Selected Channel’ is not available in the Project window?) - I’ve set up a macro which opens the mixer/triggers ‘Show Channels that are Connected to the First Selected Channel’ then closes the mixer, which leaves my project window with just the desired channels showing (plus a lot of random Folders for some reason). As I said it’s a bit clunky, but seems to be doing the job.
Cheers,
Simon