Icon V1-M/V1-X

Cubase
,
168

Hi @thomas_martin,
I can’t get the script running. The Cubase MIDI Remote sias, that there is no controller connected. With mackie control my V1-M works.
Any idea what can be wrong in my cubase configuration. I followed the installation description of bjoluc for his script.

169

I still have trouble to get the V1-M running with the script. Steinberg support doesn’t really help for sevberal months now.- Only sending me request to delete preferences, install older Cubase versions and so on.
Now they’ve sent me another script for an Arturia device to check, if I can export it. It’s obviously possible but that script has the file extension midiremote. But it seems, that the Steinberg support is not testing the import of the V1-M script and they don’t answer concrete questions about the accepted file extensions of scripts.
I really don’t know how to solve the problem. What might be wrong in my configuration ?

170

Hello Björn and everyone!
I want to use a V1-M and a P1-M together with 2 P1-X extenders:
V1-M - P1-M - P1-X - P1-X
Is this possible?
Has anyone done this before?

1 Like
171

Hi bjoluc,

I just started using your script, Bravo!

Thanks for your time. It works great. The only issue is that sometimes my midi remote shows two v1-m options, so I need to reinstall the script.

1 Like
172

HI…The GitHub link comes up as 404…is there somewhere else to obtain the ICON V1-M script ?

Thank you.

173

It doesn’t seem so, just checked. Maybe a temporary problem.

174

Meanwhile you can find the script to download on the iCON product page for the V1-M.

I con has installed an own engineering team. bjoluc isn’t active anymore.

As well as installer for the iMAP configuration application. I wrote a document with many issues and requests regarding the V1-M with Cubase and the MIDI remote script. I have sent it to the iCON support but I am not sure ift engineering really will take care.

As well I am on the way to write a more detailed manual about the usage. If wanted I can share the documents.

175

This would be great!!!

Even if Bjoluc did a great job, Steinberg midi remote protocol maybe because is too young and MCU because is too old seem having some trouble and not performing so well as EUCON did on Avid controllers and that’s really annoying. My meters for an example start dancing together flashing all the bar led at the same time on some projects…

So thanks to all that help us using our controller at the best with Cubase.

Cheers Eriberto

176

If someone was willing to take pity on a tech luddite and go through the process of properly installing the V1-M + extender script into into Cubase, it would be GREATLY appreciated…:expressionless_face:

177

@march_media Sure thing:

  • Download the latest V1-M MIDI Remote Script (a .js file)
  • Navigate to C:\Users\<Username>\Documents\Steinberg\Cubase\MIDI Remote\Driver Scripts\Local (Windows) or /Users/<Username>/Documents/Steinberg/Cubase/MIDI Remote/Driver Scripts/Local (MacOS)
  • Create a directory named icon in there (if one doesn’t exist already). Within that directory, create another directory named v1-m. Open that directory and copy the downloaded script (a .js file) into it.
  • Restart Cubase to make it pick up the script.

That’s the procedure for a V1-M-only setup. For the V1-X, you’ll need to edit a line in the top section of the .js script file (which is just a text file, really). I’ll quote the docs here:

To use a combination of multiple devices, open the script file with a text editor and find the line reading devices: ["main"] at the top of the script. This is where you can configure your devices. For instance, to use a main unit and an extender unit, replace devices: ["main"] with devices: ["extender", "main"] (or devices: ["main", "extender"] if you have your extender on the right side of the main device) and save the file.

The full procedure is described in the Setup section here. If anything is unclear, feel free to ask. I want the docs to be as comprehensible as possible, so I’m open to rephrasing things there if it helps.

178

Hi @kaldib, I hope you were able to figure out a solution. For the record: "V1-M+P1-M+P1-X+P1-X” is not natively supported in terms of device surfaces shown in Cubase, but can well be done functionally by configuring the V1-M script as devices: ["main", "main", "extender", "extender"], and manually selecting the ports in the lower MIDI Remote pane in Cubase. That’ll show two V1-Ms and two V1-Xes visually, but since V1-M and V1-X are both MCU-compatible, the P1-M/X should work with the V1-M/X script too.

179

A thousand thank you’s…:folded_hands: :folded_hands: :folded_hands:

1 Like
180

I must be doing something incorrectly…I’ve created the necessary file structure, altered the script to accommodate the main and extender units…yet when I attempt to add the units in the MIDI remote pane, ICON V1_M does not appear as a selectable option (?)

181

Anyone ?