Hello, I am using two custom user script made by user @m.c , the issue I have after my new setup on macos, is that both devices just vanish each time I reboot cubase;
Both are using virtual midi ports, and they work fine, apart from this issue.
The first device is called “Tempo” and the midi ports in and out are named “To NOB CONTROL”. the device appears in grey, and the status says “disconnected”, I can assure you it is not disconnected, because I was using it at that very same moment.
@bensmir.hbs , when changing the port names afterwards, inside the project that originally hosted the midi remote with different port names, there is usually stored this particular remote instance, at least this is what I understood, but I might be wrong.
Nevertheless, as a side note, instead of having multiple remotes, with different port names, especially in the case of script I share, we can always place them in one script using just one pair of ports, in the case of course they are virtual.
So you think it’s better to group the 2 scripts above ?
I also heard about some weird workaround to manually create a new remote device and giving it the same name, vendor etc. And then we would have both a js file and a json file, but then cubase ask for 4 midi ports when creating the device the next time we start cubase. I feel like I am speaking non sens. I’ll try to to re read the thread Martin linked
For sure. And even more. Ideally you could have just one script for running at least everything depending on virtual ports. Even hardware controllers canbe joined inside just one script, but by using their own MIDI Ports obviously.
