feat: Add an iCON V1-M script variant

[bjoluc]

EDIT: This is released now, so please follow the readme for setup instructions.

---

Hi folks,

here's how to test this:

• Download this zip file and extract icon_v1-m.js from it.
• Follow the setup instructions but using the icon_v1-m.js file you extracted (it's not yet released, hence not uploaded as a release asset).
• Read the V1-M section in the Supplementary Remarks for Individual Scripts section for details about the script and how to use it.

If anything isn't working or could be improved (except the known limitations of course), feel free to leave your feedback here. Thanks!

[Nik7665]

[Page down] / [Page up] clarification.
Which parameter is affected with "PreFadr" ? Couldnt identify what is changed in Cubase
Which parameter is affected with "Monitor" ?

Generally it's a good idea to toggle through different parameters with [Page Up] and [Page Down] to reach tha faster.
In the [Page Down} sequence is a unnecessary free space between "HC-Freq" and "Monitor"

[Nik7665]

2024-07-29 Issue: [Dyxn/Fx/Aux] has no function. It only gets highlightedt (inverted) when pressed and [Pan] changes from highlighted to normal. When [Pan] is pressed afterwards the buttons appearanve changes back.

[Nik7665]

2024-07-29 Issue: [Master] has no function. It only changes to highlighted while the button is pressed.

[Nik7665]

2024-08-02 Issue: Initialization not reliable.
In some Cubase projects the initialization seem to be o.k. [Pan] is active, Button is highlighted, [Page up / down] works
In other projects the initialization fails. [Pan] is not active, not hightlighted. [Page up / down] not working
[Pan] is just one example. The behaviour of other functions is as well not clear

[bjoluc]

Thanks @Nik7665! Most of these things are not up to the script but to Cubase itself. Let me briefly reply to all:

Issue: When Cubase is started, always the first 8 channels are accessed by the controller and marked with the white line.
In the project the mixer may show other channels with higher numbers. The V1-M should start with a selection inside the actual visible channeld.

Not up to the script.

BUT when flipped, the fader controls Pan, but the Rotary still controls Pan instead of Volume

Good point. You're the first person to ask this – I didn't bother to implement "real" flipping because I never used it. I don't have time to implement it right now, and would like to get a majority vote on it first. Don't know what's the best feedback channel for this though 😕 Maybe there should be one thread for all supported devices in the Steinberg forum? Would clearly help avoiding redundant conversations, but might also make the topic hard to handle. I'm already having issues replying to the large amount of messages there...

[bjoluc]

Issue: Cubase allows detailed selections which channels are visible in the mixer. E.g. I have snare top and bottom mics and collected them in snare group. For final mixing I have only the snare group channel visible.
The V1-M shows allways the hidden channels

Known Cubase issue mentioned in the Readme.

2024-07-28: When a project is just loaded the first 8 channels are marked. When switching a block of 8 channels to the right, the first 8 channels are still marked and the next 8 channels as well. So now 16 channels are marked

This happens when you have multiple remote devices set up (other scripts, MCU, etc.)

It would be more convenient if the parameter value would be displayed in a 3rd line underneath the parameter name.

I agree, but the devices don't expose a third line via MIDI.

[bjoluc]

Issue: When walking through the mixer channels up and down by one or by eight the mixer view doesn't follow when the marked channels in V1-M focus are outside the actual mixer view. I have to select a channel on the V1-M and then the mixer view follows to get the selected channel in focus.
The mixer view should follow as well when just walking through the channels so that the V1-M focussed channels are always visible in the cubase mixer view.

Cubase implementation, not up to the script.

Most of the parameters allow to control the same parameter for all channels. But when reachiong Send it controls the levels of the send slots of the selected channel. It should control the level of the selected send slot for all channels.

To control the send slots of a selected channel I would expect to get thsi by pressing the [Send] button.

Which other button are you pressing to control selected-channel sends then?

Issue: [Sends] not working. I would expect that leves of inserts and cue sends could be adjusted

Can't reproduce.

[bjoluc]

Proposal: Displayed parameter values for phase shoud be 0 and 180 instead of On / Off

Good idea! The On/Off labels are provided by Cubase. I would need to map them to 0/180 then.

2024-07-28 Issue: The leftmost 8 channels stay marker in the mixer when switching to the right by 8 channels. When the leftmost channels are reached the 8 rightmost channels are kept marker when switching back to the left by 8 channels. The Main channel is always marked, even when the project is just loaded

The main channel is always marked because it is controlled by the Main fader. Can't change that.

Issue 1: How can the cue pan be controlled

Not at all via the MR API AFAIK.

The fader should control the level and the rotrary should control the pan of the cue. Flip should work between fader and rotary of the cue in this case

Neat suggestion, thanks! Once cue pan can be controlled via the API, this would be awesome!

Which parameter is affected with "PreFadr" ?

Pre/Post of a Send slot

Which parameter is affected with "Monitor" ?

Monitor On/Off of a channel

In the [Page Down} sequence is a unnecessary free space between "HC-Freq" and "Monitor"

That's the track QCs. I realize you are not using the custom IMAP preset published with this script, so you might be missing out on a bit of extra comfort 🙃 There are dedicated buttons on the green function layer for most of the encoder assignments 🙂

[bjoluc]

2024-07-29 Issue: [Dyxn/Fx/Aux] has no function. It only gets highlightedt (inverted) when pressed and [Pan] changes from highlighted to normal. When [Pan] is pressed afterwards the buttons appearanve changes back.

It's mapped to isntrument QC. Please use the custom IMAP preset to avoid those naming issues, or refer to the MCU encoder assignment table in the Readme.

2024-07-29 Issue: [Master] has no function. It only changes to highlighted while the button is pressed.

It's mapped to Mix Console Redo (as per the Readme).

2024-08-02 Issue: Initialization not reliable.

Cubase issue: Other users have described this as well and it is known to be worked around by disabling and re-enabling the controller script. Nothing I can do against it, sadly.

Cheers!

[Nik7665]

Hey,thank you for your support and your effort. I will reply to a few topics when I feeling the nee for any clarification.I only have on device connected via MR, just the V1 M. The 16 Channel issue appears in this configuration

[Nik7665]

Third Line: Does it really have to be exposed via MIDI. Couldn`t this be implemented within the V1-M firmware ? For me it`s only a rule HOW valued are displayed by the controller

[Nik7665]

I will re-test next week, which button I could press to control the sends. Maybe, I haven't found a button working but as far as I remember, some things where working using the Mackie protocol. And I was expecting, tha MR would provide at least that functionality plus additional features like channel colors

[bjoluc]

Couldn`t this be implemented within the V1-M firmware ?

Sure, but that's out of my control 🙃

I only have on device connected via MR, just the V1 M. The 16 Channel issue appears in this configuration

It's nothing I can fix in the script anyway. Have you double-checked that there are no legacy MCU remote devices configured in Cubase (no matter whether their ports are connected or not)?

[Nik7665]

I will try the IMAP preset.   Question: Do you have any constructive discussion with Steinberg to fix issues or complete the MR API. Or am I lost in nowhere land between the compynies Steinberg ans ICON ? Anything I could do as a customer of both vendors ?

[bjoluc]

I will re-test next week, which button I could press to control the sends.

Please do so with the custom IMAP preset provided with the script, or refer to the Readme for what the stock-labeled buttons do.

[Nik7665]

Who can communicate with the firmware developers to place such a feature request ? Shouldn`t this be in the discussions between the internal developers ? Or are you 3rd party developer for ICON ?

[bjoluc]

Question: Do you have any constructive discussion with Steinberg to fix issues or complete the MR API. Or am I lost in nowhere land between the compynies Steinberg ans ICON ?

My only discussions with Steinberg have been in the Steinberg forums so far. Ultimately, they acknowledged some issues but they are not open about their priorities in fixing them.
I am in contact with ICON though and they have been very responsive the whole time (unlike me at times).

[bjoluc]

Who can communicate with the firmware developers to place such a feature request ?

I might bring this up, but there were more urgent issues to be fixed in the past, so I didn't want to bother with "Hey, this would be cool" stuff.

Or are you 3rd party developer for ICON ?

Not a paid one at least 😅

[Nik7665]

Hey bjoluc,   I didn´t answert for a long while because I could not do any further testing. The script did not work in Cubase anymore and I don't understand why.   For some weeks I had communication with Steinberg`s support back and forth and provided them the script. Their final response is, that this script will not work. For me very confusing, because it was working and I didn`t understand what has changed.   But now Steinberg has offered the opportunity for you to get in contact with their expert Jochen Trappe   I would be glad if you could contact him via ***@***.*** referring to my ticket ID #657964) This could be a chance to get the problem fixed and discuss some other points for clarifications.   thank you in advance Nils

[bjoluc]

Thanks @Nik7665. The Script in this PR is thoroughly tested and works, so it should not be an issue with the script itself; maybe with your version of it though. I'd suggest that you download the script again and set it up from scratch once more.

[github-actions]

🎉 This PR is included in version 1.11.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

[Nik7665]

Thank you. I'll give it a try again.   Meanwhile I'm using Cubase Pro 14   Did you get in contact with Steinberg as I wrote ?   regards   Gesendet: Samstag, 4. Januar 2025 um 21:22 Von: bjoluc ***@***.***> An: bjoluc/cubase-mcu-midiremote ***@***.***> CC: Nik7665 ***@***.***>,Mention ***@***.***> Betreff: Re: [bjoluc/cubase-mcu-midiremote] feat: Add an iCON V1-M script variant (PR #38)   Thanks @Nik7665. The Script in this PR is thoroughly tested and works, so it should not be an issue with the script itself; maybe with your version of it though. I'd suggest that you download the script again and set it up from scratch once more. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[Nik7665]

Thank you for your work. I just tried to set the script up from scratch as you mentioned, but noc success. The V1-M has firmware 1.23 and I'm using cubase 14 Pro. The device ist connected to the computer and works using the mackie protocol.   But when I remove the mackie devices the cubase MIDI remote manager sias that there is no MIDI remote controller available.   any idea ?       Gesendet: Samstag, 4. Januar 2025 um 21:22 Von: bjoluc ***@***.***> An: bjoluc/cubase-mcu-midiremote ***@***.***> CC: Nik7665 ***@***.***>,Mention ***@***.***> Betreff: Re: [bjoluc/cubase-mcu-midiremote] feat: Add an iCON V1-M script variant (PR #38)   Thanks @Nik7665. The Script in this PR is thoroughly tested and works, so it should not be an issue with the script itself; maybe with your version of it though. I'd suggest that you download the script again and set it up from scratch once more. —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>