2.0.26 didn’t resolve it
… sorry. Can you please tell me how do you create so many virtual Ports? Do you use an extra software for it? How can we reproduce it?
Thank you,
Michael.
My studio computer has 11 virtual ports created with loopMIDI.
https://www.tobias-erichsen.de/software/loopmidi.html
4 are mandatory to use StreamDeck devices with Cubase.
I created 7 other virtual ports for 2 reasons.
(All other ports are physical interface devices. (mioXM, MOTU, RayDat, Class compliant controllers…)
1- to facilitate midi routing from controllers to softwares. ex: Cubase, Dorico, Musescore, Kyma, Librairians/editors, MobileSheets and some Stand Alone VSTs etc… are running simultaneously.
All my midi routing is handled by Cantabile so I can chose wich controller goes in what software. That allows me, for instance, to avoid inputting notes in a Dorico score when I track in Cubase, or hearing my standalone piano while I input flute notes in Musescore.
2-to overcome the lack of multiclient support for class compliant devices on windows (microsoft should be ashamed for that!!!)
Typical case: Kawai VPC1 > Cantabile > to Cubase virtual port. I push a button on a StreamDeck device and the routing is now Kawai > Cantabile> Pianoteq standalone + Mobilesheets while Haken Continuum controls Kyma…
This setup proved to be solid as rock since many years and I experienced absolutely zero bugs (unless when I mess up the configuration by myself!)
Not sure what exactly you are up to, but you may consider yourself lucky that this would work in the first place.
That said, VST Live does not support any other audio app to run in parallel, as you appear to do. It may work, even in most cases, but all we can do is to recommend to not use multiple audio applications simultaniously, unless it has been assured to work by all parties involved.
Your setup looks almost unpredictable to me, sorry. You are mixing and mashing various components which have not been tested to work together. Of course we all wish it can work and do our best to be compatible within the limits given by subsystems (like OS), but there is simply no guarantee. And the often heard “it works with Cubase” does not mean that it will also work in the same way with VST Live, or any other audio/MIDI application. Note that services like loopmidi are not considered “application” here, as those are designed to interconnect multiple clients; however that does not mean that using multiple such services at the same time plus multiple MIDI apps will play together seamlessly. We will try to do our best if we know what to do to improve the situation; at this point, we try to conform to system implementation of MIDI best we can and are happy to help if we know how to do so.
Ok I’m done .
For a start, the problem I reported here happens when VST live is on its own with nothing else running at the same time as I mentionned earlier. Also, I tried it on different computers with different windows versions.
Now you are suggesting that I should go back to the good old Atari MIDEX time when running 2 apps at the same time was a special feat! Wow!
That’s a joke. And a bad one.
Trying to explain and help best we can. Not saying you did anything wrong.
If it happens on its own as you say, then that is a different issue and we take the blame for that and try to reproduce it.
So that is not true for the case “VST live is on its own”? Then we can already exclude that, good.
Next, StreamDeck and loopmidi: can you try to exclude one of those? Does it improve the situation?
Sorry, we have literally thousands of requests and cannot remember each threads specifics at all times.
We really try to help and would like to sort it out, which can also benefit other users, so anything that narrows the problem is helpful.
… next week, we will have access to the MOTU Device. Just give us some more time, @kx3, and we’ll get this problem fixed.
/Michael.
Still unusable with V 2.1
I tried on a Win10 computer on wich no other interface is installed, neither USB or virtual. Same issue. Can’t use MidiExpress 128 output at all.
… thank you for the reminder. I’ve connected the MOTU Midi Express 128, installed the driver and started VST Live 2.1. I can use the Interface without any problems. I am trying now to reproduce your setup with the loopMIDI.
Question : VST Live is the only audio application which is running, right? No other audio application is running next to VST Live?
Thank you,
Michael.
… here we go. We’ve found the problem and fixed it. Please re-try with the next Update and let us know your experience.
Thank you for your patience,
Michael.
Is it something that can be relevently shared publicly? Perhaps I could be more helpful to isolate potential similar bugs if they ever appear…
Sure.
The problem was that the Motu uses a colon (“:”) in its port names.
VST Live internally uses colons as delimiters for complete port descriptors, like “Ur44:Midi In 1”. While for inputs, there is provision to ignore the delimiter, for MIDI outputs, that has been forgotten.
It never occured until now, so thanks for reporting and sorry for the inconvenience!
Thanks for sharing. Very interesting explanation (at least, to me!).
I thought there was a common/universal way to address MIDI ports, even with Vendor drivers.
Any hope to see the updated installer in download assistant?
hi @kx3 , I guess it’s fixed already in a pre-release. Can you give a try to 2.1.2 here:
vstlive.net
(leave 2.1.3 and 2.1.4 for now)