I was pretty sure when you wrote about your need about visibility agents that I had a workaround for you, I just didn’t have the energy/time to investigate but let me know if this is a solution for you. Now perhaps you have a very complicated template/setup with your tracks then perhaps it is not as simple with the example I am gonna demonstrate, but all you need to do is create a macro starting with the visibility config then follow up with a selection of the track you want to show.
I have same colors for all Drums, electric guitars etc, so I just create a preset inside the Project Logical Editor which selects the color name of the track I want to show.
So for example for my drums the macro looks like this
Channel & Track Visibility - Visibility Configuration 1
Process Project Logical Editor - Select Tracks - Blue
For whatever reason if you throw in a “deselect tracks” afterwards it won’t register to the P1-M, but this is one way you could do if you really would like the decibel values + the visibility config synced to the controller.
Thanks so much for the idea. Not sure I follow….does this just navigates to where the row of tracks “start?” Or would it allow the p1 to “skip “ tracks and show a selection of non-congruous faders (that’s what I really need).
I am not sure I follow what you mean xd.
What is one visibility agent for you? In my example I gave you it is exactly the same - the only difference is that the drum tracks are selected.
I choose to select all drum tracks (color blue) because this seem to guarantee it shows the track furthest to the left as number 1 on the p1-m.
I guess everything depends on how you have things setup. Play with selection macros and you will probably find a way.
I still will not switch from the MCU since MCU delivers global sends which the Midi Remote script does not, and I really like the global send option.
Ok. I probably won’t get back to the script for awhile but I’ll update here if I do.
What I’m not following is I didn’t think that the script respected what tracks were visibile, under any circumstances, and always displayed ALL trakcs.
What I need is the ability to display SOME tracks. Say, bus 1, 3,4,5,7,14,15,18 shown together on the 8 faders in front of me.
Right. Like you will be able to modify the macro to suit your need, all you need to do is making sure that the tracks are selected. Now if you are not working with the same template every time and you have to edit the macro for every new project, that’s tedious and I would definitely not do it then. But if it is more simple like my example then the workaround is not too bad.
Yea I thought I’d just let you know. Personally I want the global sends to work, I really like that option. The other hand I have less issues with the script… We will see.
For track visibility I use the mixer configurations: In the mixer, hide the channels that you don’t want to see, then create a new mixer configuration for this. For example: I always like to have a configuration with only my groups visible. With a press of a button you can simply show only those channels.
The problem with the V1-M/X using the Bjoluc script is, that this visibility is’n mirrored on the control surface. It simply shows all the channels, always. (in Mackie Control mode the channel visibility does work). This is due to a missing argument in the API (as far as I know).
As long as Steinberg (and / or Icon) don’t have a solution for this, the actual mixer layout / visibility can’t be mirrored by the controller. Or does anybody have another solution?
@Misja_van_Waterschoo Absolutely, all of this! Maybe you didn’t use the dedicated V1-M script?
Ha, sorry
No worries @SrOrtegon I may be unresponsive at times (doing this in my free time), but I don’t have any plans to abandon the project in the foreseeable future!
@Misja_van_Waterschoo You shouldn’t need to do this: There’s an IMAP preset that comes with the script, mapping the unassigned buttons to virtual Cubase Midi Remote buttons via MIDI notes, so you can assign them directly in the script. Just hit any button (when you’ve loaded the IMAP preset) on the orange layer and assign it in Cubase’s mapping assistant
This shouldn’t happen. What are your port names, please?
I suspect this is caused by a Cubase quirk which can be worked around by disabling and re-enabling the controller script (as shown in the Readme). Hope that solves it!
@vagglyren Hard to say – it might be a combination of the Midi Remote itself and the actions performed in the script. There might also be room for performance optimization in the script (at the cost of script complexity), but I’m not too optimistic as to whether that would result in a noticeable speedup. It is definitely not due to the beta status.
I’ve never worked with the global send option myself and didn’t pay much attention to it when implementing the script. I should look into this in a free moment – thanks for pointing it out @vagglyren!
Yup thanks very much for your script. Haven’t focussed on the icon desk for a bit - i often run Nuendo/Cubase without it if I am testing other things.
I noticed when reading through your github project that what we are waiting for is for steinberg to update the midi remote api more so that we can get more fine grade features. I’m particularly thinking about the ‘setfollowvisibility’ function which I think you said steinberg have not implemented in the api as yet.
Not sure how to apply pressure on them at present. They haven’t refined the api in a couple of years. If this function got properly implemented I’m assuming that icon V1 -M/X would automatically follow cubase mixer if you hid single or groups of channels in the mixer view - is that right?
Many thanks.
Curious from anyone here using a P1/V1
Does this script enable it so you could map the 8 focus quick controls to the faders (or knobs) and the parameters for those QCs are listed in each of the screens/scribble strips?
Hello,
I hope to get tips here. I own a V1-M. I just saw that bjoluc was reading and resüonding here. @bjoluc I highly appreciate your work.
I had the script working for a while and have been testing and writing comments. But then the script didnt work in Cubase anymore. I dont know why. Maybe a Cubase update ?
Confusing for me: I tried to import the script but when I navigate to the folder containing the script, the MIDI remote manager doesnt show the script file but its there. Don`t know why.
The download has expired, i am writing a scrip for the V1-M in FL Studio, i was hoping your script may contain a hardware address for the 2 lines of text above the colour band, also if you can share any other information about the hardware cpde interpretations, kind regards, Steve
Hello,
in Cubase 13 I had this working for a while. At some point, maybe a Cubase or other update it didn 't work anymore.
I tried to install and configure it new with Cubase 14 Pro, but Cubase doesn’t pick the script. Any ideas how to fix it ?
It seems, that iCON is not working anymore to bring it to a release. The state that 45 commits are waiting to be merged as shown on github stays the same for several months.
Hi all, just a quick note that I have officially released the V1-M/V1-X script on GitHub – I don’t have much time to reply here right now, but will come back to you when I find some free time again
With the relased version I still have trouble. The V1-M works fine with the Mackie protocol, so it’s connected to my computer. But when I remove the mackie control devices, cubase doesn’t pick the script.
I have downloades the released version and followed the installation description from scratch.
The MIDI remote dialog in Cubase sais no MIDI remote controller available.
I’m using Cubase 14 Pro. The V1-M firmware is 1.23.
Any ideas ?
Hi!
I’m not sure this is related to your issue but i ran some tests last year because I was very disappointed by the time it took to update the fader bank in MIDIRemote compared to Mackie Control protocol.
Here is the results of my tests MIDI Remote latency
Unfortunately, no words since then.
I haven’t tried to update these tests with newer versions of Cubendo but haven’t seen anything about optimization in the latest release notes either.
My conclusion is that for some reason that probably only Steinberg can figure out, MIDI Remote is quite unresponsive.
I believe it is. The latency is overall more using the midi remote script. The Mackie protocol feels quick and reactive compared to the midi remote, all I can say. Now the midi remote is not terrible, but being used to the Mackie it feels somewhat like a downgrade in a sense.
It depends on how many parameters you send per channel on banking and how many channels.
For me it’s unusable for now because i’d like to use 24 channels per bank with something like 200 messages per channel (mostly CCs or NoteOn but also NRPN and SYSEX messages). This adds up real quick…
Plus, the inability to disable auto-banking is annoying because each time i select a track that isn’t in the bank, i have to wait for a refresh…
I may be unresponsive at times (doing this in my free time), but I don’t have any plans to abandon the project in the foreseeable future!
