VST Connect & VST Connect SE - Solution Thread
-
- Junior Member
- Posts: 123
- Joined: Tue Feb 08, 2011 12:23 am
- Contact:
VST Connect & VST Connect SE - Solution Thread
Has anyone been able to get this to successfully work?
I followed the instructions in the YouTube video and I give the performer the keycode. But when the performer hits "Connect" we BOTH get a message that says:
Sorry, connection failed: no reply. You may try again later.
The fact that both of us get the message means there's some type of connection happening. I just haven't been able to figure out what the problem is.
Was so looking forward to trying this awesome feature out.
Any ideas?
I followed the instructions in the YouTube video and I give the performer the keycode. But when the performer hits "Connect" we BOTH get a message that says:
Sorry, connection failed: no reply. You may try again later.
The fact that both of us get the message means there's some type of connection happening. I just haven't been able to figure out what the problem is.
Was so looking forward to trying this awesome feature out.
Any ideas?
-
- Junior Member
- Posts: 75
- Joined: Wed Dec 15, 2010 5:10 pm
- Location: Frankfurt
- Contact:
Re: VST Connect not connecting?
Do you have the "VST-Connect Cue Mix plug" active?
Should be in the "To Performer" group.
Should be in the "To Performer" group.
-
- Junior Member
- Posts: 123
- Joined: Tue Feb 08, 2011 12:23 am
- Contact:
Re: VST Connect not connecting?
Yes, the VST Connect SE Cue Mix plug in is on the "To Performer" group. And the VST Connect SE plugin is on the actual Input Channel labelled "T/B Performer"
-
- Junior Member
- Posts: 75
- Joined: Wed Dec 15, 2010 5:10 pm
- Location: Frankfurt
- Contact:
Re: VST Connect not connecting?
O.K., but is the PlugIn active ? I mean, is the active button blue? I had the same error message and it was because I did not had the Cue mix on.pondwalden wrote:Yes, the VST Connect SE Cue Mix plug in is on the "To Performer" group. And the VST Connect SE plugin is on the actual Input Channel labelled "T/B Performer"
- musicullum
- Member
- Posts: 660
- Joined: Wed Dec 05, 2012 7:31 pm
- Contact:
Re: VST Connect not connecting?
The cuemix plugin is not required to establish a connection, but for providing the headphone mix to the Performer. Other than in the video tutorial you are advised to use sends like you would in a local studio situation.The Oracle wrote:O.K., but is the PlugIn active ? I mean, is the active button blue? I had the same error message and it was because I did not had the Cue mix on.pondwalden wrote:Yes, the VST Connect SE Cue Mix plug in is on the "To Performer" group. And the VST Connect SE plugin is on the actual Input Channel labelled "T/B Performer"
The message means that a peer to peer connection can not be established. This mostly happens when one party is behind a restrictive firewall (school, university, personal firewall etc). In this case he has to open ("forward") the relevant ports (51113 if I remember correctly). See the manual (klick the question mark).
musi
-
- Junior Member
- Posts: 169
- Joined: Fri Feb 04, 2011 6:47 pm
- Contact:
VST Connect SE problem
Has anyone got this to work?
I am trying with someone and all we get is a "no reply" message after he puts in the key I give him after I log in.
Any help would be appreciated.
I am trying with someone and all we get is a "no reply" message after he puts in the key I give him after I log in.
Any help would be appreciated.
Cubase 10.x, I7 8 5960k Core, 32 gb
Halion 6.x, Large VE PRO setup with about 3000 Tracks
https://www.samplefuel.com
Halion 6.x, Large VE PRO setup with about 3000 Tracks
https://www.samplefuel.com
-
- New Member
- Posts: 13
- Joined: Mon May 09, 2011 4:31 pm
- Contact:
Re: VST Connect SE problem
Judging from your sig line, it is because you are still running Cubase 6.04
Seriously, haven't tried VST Connect yet. Interested to see if you can get it to work.
Mike

Seriously, haven't tried VST Connect yet. Interested to see if you can get it to work.
Mike
Mike Hummel
-
- Junior Member
- Posts: 169
- Joined: Fri Feb 04, 2011 6:47 pm
- Contact:
Re: VST Connect SE problem
Has anyone tried this and got it to work yet?
Cubase 10.x, I7 8 5960k Core, 32 gb
Halion 6.x, Large VE PRO setup with about 3000 Tracks
https://www.samplefuel.com
Halion 6.x, Large VE PRO setup with about 3000 Tracks
https://www.samplefuel.com
-
- New Member
- Posts: 4
- Joined: Tue Jan 04, 2011 5:34 pm
- Contact:
Re: VST Connect SE problem
Tried doing it here with two computers in my own house (both connected to the internet), but can't get it to work. Logged in from studio computer after setting it up per the PDF manual instructions. Then, when try logging in with the key id on the "performer" computer, it says that a studio with that id is not logged in.
Stephen Sherrard
Professional Mixing Engineer
DBAR Productions & MusicTECH
LoopLibrary.com
Professional Mixing Engineer
DBAR Productions & MusicTECH
LoopLibrary.com
-
- New Member
- Posts: 4
- Joined: Tue Jan 04, 2011 5:34 pm
- Contact:
Re: VST Connect SE problem
Also tried doing it with their built-in template on a new project. When I try to connect on the "performer" computer, it just gives me an "unknown error".
Stephen Sherrard
Professional Mixing Engineer
DBAR Productions & MusicTECH
LoopLibrary.com
Professional Mixing Engineer
DBAR Productions & MusicTECH
LoopLibrary.com
- musicullum
- Member
- Posts: 660
- Joined: Wed Dec 05, 2012 7:31 pm
- Contact:
Re: VST Connect SE problem
you can not connect within your local network, a connection requires two different ip addresses. Currently, "Unknown error" is beeing reported, the next update will tell you exactly this.
musi
-
- Junior Member
- Posts: 169
- Joined: Fri Feb 04, 2011 6:47 pm
- Contact:
Re: VST Connect SE problem
I am trying to connect to other locations with no luck.
-D
-D
Cubase 10.x, I7 8 5960k Core, 32 gb
Halion 6.x, Large VE PRO setup with about 3000 Tracks
https://www.samplefuel.com
Halion 6.x, Large VE PRO setup with about 3000 Tracks
https://www.samplefuel.com
- musicullum
- Member
- Posts: 660
- Joined: Wed Dec 05, 2012 7:31 pm
- Contact:
Re: VST Connect SE problem
if it says "No connection, you may try again later" that means the connection server has accepted the key and everything, but the peer to peer connection fails. In this case, one of you has to open ("forward") UDP port 51113. See the manual (click the question mark icon).
musi
-
- Member
- Posts: 700
- Joined: Fri Feb 18, 2011 8:20 am
- Contact:
Re: VST Connect SE problem
i have the same "unknown error" problem. if anyone wants to test it with me send me a private message with a the log in key and I'll connect, or vice versa.
Core i7 3930k
ASUS P9X79 PRO
Corsair XMS3 64GB (8x8GB)
Nvidia GT 640
RME HDSPe AIO
Focal Solo 6
Windows 10 Pro 64-bit
Cubase 10
User of Cubase since Cubase 5.0
http://www.andrewpooletodd.com
ASUS P9X79 PRO
Corsair XMS3 64GB (8x8GB)
Nvidia GT 640
RME HDSPe AIO
Focal Solo 6
Windows 10 Pro 64-bit
Cubase 10
User of Cubase since Cubase 5.0
http://www.andrewpooletodd.com
-
- Member
- Posts: 700
- Joined: Fri Feb 18, 2011 8:20 am
- Contact:
Re: VST Connect SE problem
see if you can connect to key: 36803 84717
Core i7 3930k
ASUS P9X79 PRO
Corsair XMS3 64GB (8x8GB)
Nvidia GT 640
RME HDSPe AIO
Focal Solo 6
Windows 10 Pro 64-bit
Cubase 10
User of Cubase since Cubase 5.0
http://www.andrewpooletodd.com
ASUS P9X79 PRO
Corsair XMS3 64GB (8x8GB)
Nvidia GT 640
RME HDSPe AIO
Focal Solo 6
Windows 10 Pro 64-bit
Cubase 10
User of Cubase since Cubase 5.0
http://www.andrewpooletodd.com
-
- Member
- Posts: 700
- Joined: Fri Feb 18, 2011 8:20 am
- Contact:
Re: VST Connect SE problem
changed it to 73934 65739
Core i7 3930k
ASUS P9X79 PRO
Corsair XMS3 64GB (8x8GB)
Nvidia GT 640
RME HDSPe AIO
Focal Solo 6
Windows 10 Pro 64-bit
Cubase 10
User of Cubase since Cubase 5.0
http://www.andrewpooletodd.com
ASUS P9X79 PRO
Corsair XMS3 64GB (8x8GB)
Nvidia GT 640
RME HDSPe AIO
Focal Solo 6
Windows 10 Pro 64-bit
Cubase 10
User of Cubase since Cubase 5.0
http://www.andrewpooletodd.com
-
- Member
- Posts: 700
- Joined: Fri Feb 18, 2011 8:20 am
- Contact:
Re: VST Connect SE problem
I tried it out with my buddy and it worked!
Core i7 3930k
ASUS P9X79 PRO
Corsair XMS3 64GB (8x8GB)
Nvidia GT 640
RME HDSPe AIO
Focal Solo 6
Windows 10 Pro 64-bit
Cubase 10
User of Cubase since Cubase 5.0
http://www.andrewpooletodd.com
ASUS P9X79 PRO
Corsair XMS3 64GB (8x8GB)
Nvidia GT 640
RME HDSPe AIO
Focal Solo 6
Windows 10 Pro 64-bit
Cubase 10
User of Cubase since Cubase 5.0
http://www.andrewpooletodd.com
-
- New Member
- Posts: 9
- Joined: Wed Dec 15, 2010 7:15 pm
- Contact:
Re: VST Connect SE problem
Hi
I can't get this to work. I am using the mac version of cubase 7 and VST Connect performer.
My router is configured to accept udp port 51111-51113.
The studio computer is on a raw internet line without router/firewall.
Both firewalls in the Macs are off.
I have made a wireshark trace to see what´s going on.
Both computers connects to the Steinberg server: ip: 194.6.195.159
But when the peer to peer connection is to be established both computers send on port 51111 and 51113 to each other but nothing happens in the apps. The packets data includes the data "hello version 28" which seems to me to be a sort of keep alive message. After a while it times out.
It also seems a little bit odd of which computer that starts the negotiation after the server connection is established. I have tried different connection methods and therefore different IP-adresses. It seems that the computer with the highest address starts the ptp negotiation. This means that the one with lowest IP needs to have its router/firewall configured correct. This is not good since that cannot be the clients task (performer). It shall always be that the performer has to establish the ptp connection. The studio shall be the "server" and the performer shall be the "client".
Anyway Steinberg: The VST Connect SE is a terrific idea but right now it does not work. And make sure you are using correct client/server behavior so firewalls/routers in the way can be configured correctly. Maybe using uPNP is something to consider as most people using Cubase are musicians and not computer networking guys.
Regards
Anders
I can't get this to work. I am using the mac version of cubase 7 and VST Connect performer.
My router is configured to accept udp port 51111-51113.
The studio computer is on a raw internet line without router/firewall.
Both firewalls in the Macs are off.
I have made a wireshark trace to see what´s going on.
Both computers connects to the Steinberg server: ip: 194.6.195.159
But when the peer to peer connection is to be established both computers send on port 51111 and 51113 to each other but nothing happens in the apps. The packets data includes the data "hello version 28" which seems to me to be a sort of keep alive message. After a while it times out.
It also seems a little bit odd of which computer that starts the negotiation after the server connection is established. I have tried different connection methods and therefore different IP-adresses. It seems that the computer with the highest address starts the ptp negotiation. This means that the one with lowest IP needs to have its router/firewall configured correct. This is not good since that cannot be the clients task (performer). It shall always be that the performer has to establish the ptp connection. The studio shall be the "server" and the performer shall be the "client".
Anyway Steinberg: The VST Connect SE is a terrific idea but right now it does not work. And make sure you are using correct client/server behavior so firewalls/routers in the way can be configured correctly. Maybe using uPNP is something to consider as most people using Cubase are musicians and not computer networking guys.
Regards
Anders
Cubase 7, Cubase Elements 6.03, Wavelab 7, MR816CSX, RME, Apogee, Alesis, MacPro, MacBookPro, iMac
-
- Junior Member
- Posts: 87
- Joined: Fri Dec 31, 2010 2:57 am
- Contact:
Re: VST Connect SE problem
Even in a local network computers have different ip addresses ....musicullum wrote:you can not connect within your local network, a connection requires two different ip addresses. Currently, "Unknown error" is beeing reported, the next update will tell you exactly this.
-
- New Member
- Posts: 9
- Joined: Wed Dec 15, 2010 7:15 pm
- Contact:
Re: VST Connect SE problem
True, but if you are behind a router the steinberg server will se the same ip address and since the udp ports are fixed there is no way of port forwarding to the right computer.mink wrote:Even in a local network computers have different ip addresses ....musicullum wrote:you can not connect within your local network, a connection requires two different ip addresses. Currently, "Unknown error" is beeing reported, the next update will tell you exactly this.
Regards
Anders
Cubase 7, Cubase Elements 6.03, Wavelab 7, MR816CSX, RME, Apogee, Alesis, MacPro, MacBookPro, iMac
-
- Junior Member
- Posts: 169
- Joined: Fri Feb 04, 2011 6:47 pm
- Contact:
Re: VST Connect SE problem
I would love to see this work.....I cannot get it to work.
Does anyone have this working reliably at this point? If so did you have to set up your router any way special?
I can log in and get a key, but the 2 machines fail to connect to each other.
Does anyone have this working reliably at this point? If so did you have to set up your router any way special?
I can log in and get a key, but the 2 machines fail to connect to each other.
Cubase 10.x, I7 8 5960k Core, 32 gb
Halion 6.x, Large VE PRO setup with about 3000 Tracks
https://www.samplefuel.com
Halion 6.x, Large VE PRO setup with about 3000 Tracks
https://www.samplefuel.com
-
- New Member
- Posts: 9
- Joined: Wed Dec 15, 2010 7:15 pm
- Contact:
Re: VST Connect SE problem
You have to port forward udp ports 51111 to 51113 on both sides. But I can not get it to work even after that.dlpmusic wrote:I would love to see this work.....I cannot get it to work.
Does anyone have this working reliably at this point? If so did you have to set up your router any way special?
I can log in and get a key, but the 2 machines fail to connect to each other.
I can see the traffic coming to the computers on each side but nothing happens.
Cubase 7, Cubase Elements 6.03, Wavelab 7, MR816CSX, RME, Apogee, Alesis, MacPro, MacBookPro, iMac
-
- Junior Member
- Posts: 73
- Joined: Fri Jan 21, 2011 8:06 pm
- Contact:
Re: VST Connect SE problem
I was able to set this up with a buddy. We could see each other from the webcams (The video is flaky to say the least)and hear each other from the To Performer and Performer monitor but I could not record his audio using the built in template. No audio is passed through the "Performer Rec" channel when sourced to "TB/Performer". I have followed the guide and the video to the T but with no success.
Windows 10 Pro X64. 1 PC for Nuendo 10, WaveLab Pro 9.5.25
Windows 10 Pro x64. 1 PC for Pro Tools 12.8 HDX MADI
ASRock Fatal1ty X399
EVGA RTX 2080Ti
AMD RYZEN Threadripper 2990WX 32 Core
128GB DDR4 3600 Memory
RME HDSPe Madi-FX
RME HDSPe AES x 2
Avid AM713 x3, MA703 x2, DM714, MD704, FC726, ML530
Avid System 5 Console, 300 channels with Colin Broad P2MMC-USB for transport control from desk to Nuendo and PT
Genelec 1038B Mains, 7271A Sub x 2, 8240A surrounds
TC Music 6000 MKII, Lexicon 960L, Bricasti M7, PCM Native, Waves Mercury, Izotope 8, Slate Trigger 2
Windows 10 Pro x64. 1 PC for Pro Tools 12.8 HDX MADI
ASRock Fatal1ty X399
EVGA RTX 2080Ti
AMD RYZEN Threadripper 2990WX 32 Core
128GB DDR4 3600 Memory
RME HDSPe Madi-FX
RME HDSPe AES x 2
Avid AM713 x3, MA703 x2, DM714, MD704, FC726, ML530
Avid System 5 Console, 300 channels with Colin Broad P2MMC-USB for transport control from desk to Nuendo and PT
Genelec 1038B Mains, 7271A Sub x 2, 8240A surrounds
TC Music 6000 MKII, Lexicon 960L, Bricasti M7, PCM Native, Waves Mercury, Izotope 8, Slate Trigger 2
-
- Junior Member
- Posts: 87
- Joined: Fri Dec 31, 2010 2:57 am
- Contact:
Re: VST Connect SE problem
Then the implementation on steinbergs side is insufficient , as the combination of ip/port should be unique for each machine.Duracell wrote:True, but if you are behind a router the steinberg server will se the same ip address and since the udp ports are fixed there is no way of port forwarding to the right computer.mink wrote:Even in a local network computers have different ip addresses ....musicullum wrote:you can not connect within your local network, a connection requires two different ip addresses. Currently, "Unknown error" is beeing reported, the next update will tell you exactly this.
Regards
Anders
Networking for beginners....
-
- New Member
- Posts: 9
- Joined: Wed Dec 15, 2010 7:15 pm
- Contact:
Re: VST Connect SE problem
So true, and the server should respond to the client source port not the fixed 51111 or 51113.mink wrote:
Then the implementation on steinbergs side is insufficient , as the combination of ip/port should be unique for each machine.
Networking for beginners....
Cubase 7, Cubase Elements 6.03, Wavelab 7, MR816CSX, RME, Apogee, Alesis, MacPro, MacBookPro, iMac
Who is online
Users browsing this forum: No registered users and 12 guests