Today I worked with a performer through VST Connect and VST Connect Performer. All went fine, until we experienced a “timeout”, and we got disconnected.
After that, we tried to reconnect, using a new “key”, but nothing worked. The performer sees different connection errors, like “You are already in a session. Make sure not to use the same name as the Studio” (which wasn’t the case!)
Or: “Studio with key **** ***** is not logged in! Make sure both sides use the same and up-to-dat version!” I was logged in, we both use the same version.
We tried it several times, did restarts of our computer, performer re-installed VSTConnect performer.
Any suggestion how to solve this problem? At first it worked fine, but now these connection errors (which are not applicable) keep popping up.
I have used 5.60.10 several times since it came out and had no problem connecting, even with people on 5.60.
Today I tried to use it and every single time the person using Performer or Studio Pass got ‘Connection Error Studio with Key xxxxx xxxxx is not logged in! Make sure both sides use the same and up-to-date version!’
I even tried it on a different network on my end with the same results.
I don’t know if this makes a difference, but VST Connect would only generate a new key if I quit Cubase and started again - if I simply disconnected and reconnected using the button next to my name, it always presented the same key.
We both restarted our computers on each end, but no luck
Just tried again with Studio Connect on an iPad connected to 4G and my MacBook on Starlink this morning and the same result. I then swapped the network connections on the devices - no change
Is there anyway I can confirm that the Studio side of the connection is good before someone tries to connect? If the Studio side is getting a Key code, does that mean it should be connected, or does it generate the key in the app?
It’s a 2-stage process. The key is generated by a server, but the connection is established either peer-to-peer if applicable, or via a relay server. The latter is up and running fine.
You may want to check if you changed something on your system, like adding a service or app. We also recommend to not install any so called “internet security” or virus protection programs, as the OS does good enough of a job already.
Nothing has changed with any of the devices trying to connect.
However, I finally got it working with Studio Pass on my iPod, running on the same networks as I tried before. This time, I got an error message that I hadn’t seen before saying something about not being able to open a socket and that I might need to restart. I simply tried it one more time, and it worked.
This indicates that another service or app in the network is using the same connection that VST Connet tries to use. As suspected before, it is likely that you installed some.
The socket error has only appeared once. And nothing has been installed or changed since the last successful session.
However, since the socket error message appeared, I have been able to connect via Studio Pass twice. Still have to test in a real session with someone using Connect.
I attempted a session between the UK and the US today. We were able to connect once after several failed attempts.
We then needed to drop the connection to make some instrument changes on the performer end. We were then unable to connect even after about 20 attempts and each of us doing a full restart of our computers. There were no configuration changes made to either machine after the successful connection. Every single time it failed the message was the that the studio end was not connected.
The only thing that changed before the single successful connection was that on a hunch I disabled Sidecar - I had been using my iPad as a third monitor. It remained disabled throughout the rest of the attempted connections.
Based on the fact that we had a single successful connection and then were unable to connect immediately afterward the problem can’t be related to a change in configuration.
I just tried a test connection using Studio Pass on my iPhone over a 4G network. It connected to the session but still said “Not Connected” at the top of the screen.
I then disconnected and attempted to connect again and immediately got the connection error message saying the studio was not logged in.
in your Profile i read, that you use Cubase Pro 12.0.6.
There is 12.0.70 downloadable.
But i don’t think, that this will change anything.
But maybe it’s a good idea, to remove the VST Connect, after starting Cubase and then create a new one.
I use Cubase Pro 13.0.55 with VST Connect Pro 5.6.10.751
When i do the last connections with my performer, we had at first time problems with Connection, Talkback and Camera settings.
After the beginnings we have no problems anymore
I was able to connect from the UK to the US once today after about four attempts. We stayed connected for a couple of hours, then lost the connection because I had to change the audio card buffer size to fix a problem.
After that we were not able to connect again. It seems to be very random whether we can connect or not.
When I disconnect and reconnect I keep getting the same key number. On rare occasions, I will get a new key number.
I’ve opened a support ticket, but I’m guessing that the response there will also be from @musicullum, but I do want to get it registered as a problem in the support system.
This is very frustrating as I’ve been using the product for many years, and have just released an EP where all tracks were created using VST Connect.
Ok, it appears that the problem exists between the chair and the keyboard.
The person using VST Connect Performer had been hitting the connection button multiple times when the connection wasn’t instantaneous. Since I discovered this and told him not to do that, we’ve had much better luck with our connections.
Because I’m not fond of blaming the user, perhaps some sort of UI clue that the connection is in process of being made would be a good feature for a future version.