Hi @bjoluc . I’m just testing the MCU script on my Nuendo system with 3 extenders. It looks pretty good so far. A few questions:
How can I disable the “jog wheel - zoom when zoom button is active” function? I would like to have my jog wheel to control cursor position at all times, even when zoom button is activated
When I hide certain tracks / channels in my DAW (Nuendo), the control surface doesn’t hide those channels. All channels remain present. Is there a way to follow the hiding of channels in Nuendo on the controller? (I guess that is the “FollowVisibility” option not implemented yet?)
Is it possible to assign specific channels to certain faders on the controller exclusively? It would be very cool to have (for example) my group channels assigned to faders that will always remain present, even when banking. That way I always have my groups within reach.
Love the work you’ve done so far! I will do some more testing, and perhaps will have some more questions / requests / ideas about this script.
I’ve been following this thread as I’m expecting delivery of an icon v1-m soon.
It seems this thread hasn’t been updated in 16 days, is this because everyone is loving the great work put in by @bjoluc and there is no need to keep talking or is there another place to go and discuss this?
I’ve renamed Plug-In to Focused Insert. The stock Plug-In button wasn’t mapped in the first script version, but I’ve updated the Pull Request on GitHub several times since then and it is also mapped now (with the same functionality as Focused Inserts though).
Right, I haven’t neither. It seems to be impossible via the Midi Remote API, at least I didn’t find a way to do it.
Oh right, you can’t (currently). Thanks for pointing this out – I should add a config option for it.
Yup. It hasn’t landed in Cubase/Nuendo 13.0.40 neither
That’s what left and right mixer zones should allow you to do (one lucky day), but despite options for them already being available in the API, they are not working yet. I really hope this will be addressed soon.
@j1mcrane I’m considering getting a V1-M with extender(s) as well, to replace my Mackie Control Pro setup. I’m really curious of your experience with the V1-M with Cubase/Nuendo.
@bjoluc I just got an Icon V1-m and I’ve imported the cubase mcu-pro script. I noticed that the strip colors and secondary display do not work. Should the colors be visible and the second display show something?
Well, I love the script, but my workflow depends on visibility configurations (which the API apparently doesn’t support) so I’ll have to stick to Mackie Protocol.
Still I’m wondering if anyone knows if the “Pages” functionality in the midi remote could be used to setup something equivalent to mix configs, and if that’d be compatible with the script? I’ve been meaning to try it out but haven’t had the time.
SOLVED: I hadn’t noticed that there was a V1-M script available so I was using the mcu-pro script (how foolish of me). When using the V1-M/X script the colors and secondary display are working great! Als great to see the option to disable the “jog wheel as zoom”. Great work!
I will do some more testing with my new setup (V1M with two extenders), and I will post my findings, issues and suggestions!
Question: On my previous setup with Mackie Control Pro units I had some functions assigned to the 8 “Function” buttons. The V1-M has these buttons also, called F1-F8 and they can be used at the touchscreen… How can I assign functions to these buttons again? I can’t seem to find them in the Nuendo Midi Remote setup.
EDIT: (workaround) I added some buttons via the iMap on the V1-M, which send midi commands. I assigned these midi commands in Nuendo (using the Generic Remote) to the desired functions in Nuendo.
Question: I have setup the V1-M script in the MIDI Remote editor in Nuendo, it works fine. But every time when I startup Nuendo I have to manually add the control surface and assign the midi ports. It looks as if Nuendo “forgets” this setup. Why is that, and how to fix this?
@bjoluc: I’m using the V1-M setup file for imap with all the different functions for the touchscreen on the V1-M. It worked fine, but now, when I am on the second page (green), the buttons for selecting the encoder assignment don’t work as they used to. When I press the desired function (Pan, Pre Gain, Sends etc.) the function is not assigned to the encoder or showing on the display. Only after I press the “Shift” button or press a channel “select” button the correct function is assigned to the encoder.
I have customized some buttons in the imps for personal preference but even after loading the original imap setup file and midi script, the behavior remains. any ideas?
Hi Folks,
I’ve had the Icon V1-M and 2 x V1 X extenders for around a week now. I’ve read here about the great work Bijoluc has done on iMap script additions and that would be good for my Nuendo 13 I am sure. I just wondered whether the script has resolved the track colours appearing on the V1-M and V1-X meter displays?
I’m using Bitwig 5.2 a bit as well - but I am no biggy user of this software. While the track colour strips appear when using Bitwig they don’t appear to match the track colours on the computer display but appear to be a default range of colours duplicated on the V1 frst X1 and second X2.
Any comments on this welcomed either for Cubase/Nuendo or Bitwig. The level of support from Icon is strange - why don’t they just have a standard user forum like everyone else.
Hi there,
I’m hoping Bjoluc or anyone else can help me a bit on this. I’ve got the v1-m js script installed in midi remote in Nuendo 13. I have configured devices as: main, extender, extender within the script - as I need the V1-M to be on the left… The second extender seems not to be responding properly as yet but maybe if I declare some more tracks on it it will pick up more. The hardware set up seems to identify the two extenders automatically as x2 and x3 with the main unit remaining as v1-m.
The other problem is I’m not getting any track (or encoder) colours for the scribble strip. lower region on the meter bridge yet which is a shame.
Also have not yet got the stereo meters on the bridge to show although the master fader is working OK. All this stuff seems to work quite well in Bitwig 5.2 but Nuendo is a bit more like my studio workhorse so I need things to work OK. Can’t seem to get any return to 0 button working either but maybe I just need to assign a hotkey xomewhere for that. Also it would good to have an option to fully switch the jog wheel off - it sure is sensitive.
Many thanks for all your hard work on the V1-m.js Bjoluc - it sure is a big help that you have done all this.
Thanks in hopes and happy to log some feedback in github if it is not too late to do so.
SOLVED – easily solved by removing and readding the midi remote controller and script. Then I could assign the midiport 2 to all three devices reactivate the controller and all my earlier queries were resolved - very happy indeed now
Perhaps someone in here knows the question - What causes the banking to be slower when using bjoluc Midi Remote Script? Is it the Midi Remote itself? Is it a “longer path” for the controller to take so it takes longer? Is it because the script is being beta tested?
Simply curious, I like the potential of the scrip, especially if the Midi Remote gets updated, but it would be a little bummer (not too bad though) if I would move from a very snappy channel banking to a slight slower one.
, but I can’t tell. Don’t know of any other discussions either.
