Good afternoon!
I am currently using Cubase Pro 14 in the trial version, together with the Icon V1-M and V1-X MIDI controllers. I understand that Cubase Pro 14 can use the second 1.14 inch TFT screens of the V1-M and V1-X, as well as the Cubase channel color modes on the 2 inch TFT screens. I have tried several Cubase projects and templates, but these options do not work. Is there a way to fix this?
Hello!
I have the same equipment without V1-X. The solution you can find in another discussion, but without drum track ,mIt some change per Midi Remoute script variant by Bjoluc
That was made for Cubase 13. Installation and description can be found in
following link:
Gruß Zoltan!
I have been testing the script for a while. Generally I like the progress in the functionality using the V1-M. But in my opinion the support of iCON for this product is still poor.
The script can be downloaded from GitHup which is for software developers. It has never been officially released by iCON including notifications for their registered owners of the device.
Since january there’s no more further development of the script for further improvements. Comments aren’t answered anymore.
Featrure requests for firmware improvements aren’t answered.
I really like the hardware and it would have so much potential to become really the best DAW controller if iCON would spend some effort to listen to customers and improve firmware and software accordingly.
I’d say the script by @bjoluc, while beautiful, is not a reliable option. Something that complex needs constant support and updates from either Steinberg or Icon.
The script doesn’t suit my needs now, so I can’t use it despite the awesome extra features it brings to the table. It may suit your needs now, but it will be broken in the future as all software is as other aspects of Cubase get updated.
We need to give them that message though, apparently, as no one from Steinberg, Icon, or any of the major controller devs seems to be willing to make that investment. Nektar and Softube are the exceptions, but from what Nektar says it was a monumental effort to work with Steinberg to get the MIDI Remote API fixed up enough to work properly.
So til all thats sorted, Mackie Control is where its at.
I totally agree, that constant support would be needed. The MIDI remote concept is a really good approach and hopefully will be as succesful as VST in the future.
Allthough the script doesn’t suit my needs as well for me it’s allready some progress compared to Mackie Control. But you are right that there is a risk of incompatibility in the future when the companies do not interact.
Don’t know what to do to convince them to work together to improve the interoperability and to work on feature requests.
Warning !
Last week I updated the V1-M firmware from 1.23 to 1.26. Now the remote script doesn‘t work anymore. The MIDI remote manager is showing two Device instances with 1.19 and 1.23. Both are not connected. The Device still works with Mackie Control Protocol.
I have conversation with iCON Support but no solution up to now.
I have the same problem. Please, please please Steinberg get together with icon to supply the script for the V1-M. Im a music creator not a software engineer. I want to be able to add colour to the lcd screens control surface. Id even be willing to pay for a download!
if only it was easy to integrate Cubase into iCon V1-M the world would be a better place.
And most of the effort has more to do with Nektar and Softube having intermediate software that interfaces with Cubase (Nektarine for Nektar, Softube Console plugins for Softube) and deals with the bulk of the headaches instead of having to deal with MIDI Remote and its API directly. SSL also uses a similar solution with its SSL360 plugins.
Good to See that I‘m not the only one. meanwhile I had a few atemlos to fix it but wasn‘ successful. Yesterday I found Out, that the Script still works with Cubase 13.
I sent that Information to the iCON Support and asked them to Test the behaviour with Cubase 14 on their side. Waiting for response. I will Update here
Meanwhile the iCON Support hast tested with Cubase 14 and it worked on their side.
So I installed the Script on a second PC, a Windows 11 Laptop and there it works as well. and in my Studio PC with Windows 10 ist works with Cubase 13.
So it must be an issue with my Cubase 14 Installation on my Studio PC. Some Version informations about the V1-M Firmware are Stores somewhere and are not removed, when I uninstall and re-install the Script.
Trying to reach the Steinberg Support not successful today.
After having some conversations with the iCON support it‘s working now for me on a new PC with Cubase 14 Pro and Cubase 15 Pro. I had to uninstall the V1-M driver and or remove the folder with the script a few times and finally it worked.
So it seems, that the Installation process isn‘t really reliable up to now. But I‘ve got the Information, that there is an enigeering team working now. I hope, they will fix some other issues I reported to the support as well.