Ok. I’ll use the guide as you (and perhaps anther user) have suggested and hope that everything works. Back to you with an update. Cheers
I have done my absolute best to follow the step by step guide but have failed to successfully set up a working remote session. Previously, the performer could hear the track but not his voice. Today, the exact opposite even though the metering could be clearly seen on the VST mixer. However, I am very bothered by the inconsistent terminology in the directions (i.e. things that don’t match version 10) as well as the assumptions about having read the manual. I am a very tech savvy individual and have engineered some rather successful recordings but, as a Pro Tools user, I find Cubase almost completely unintuitive. To make matters more difficult, I am dealing with an artist thousands of miles away who is not tech savvy at all. Again, I ask if anyone who understands all this would be willing to act as a test artist. We could be on Skype while helping walk me through the set up problems. Thank you
That’s the whole idea, Performer shoud not have to be tech-savvy, and that’s why you are remote-controlling almost all of his assets just like in a real studio.
The mixer displayed in the VST Connect plugin (not the Cubase mixer!) shows what Performer hears. The “Studio” channel reflects the cuemix that you send. If Performer cannot hear his voice, check the “Mic” channel: do meters move when he speaks? If not, make sure the right hardware port is selected on the performer mixer “Mic” channel and that its fader is up.
I will check the manual, it may be outdated and we’re sorry for that. But as a savvy PT user you should get all problems solved reading connectvst.com, it provides precise routing information and covers almost every pitfall. We’re still happy to help with specific questions
“check the “Mic” channel: do meters move when he speaks? If not, make sure the right hardware port is selected on the performer mixer “Mic” channel and that its fader is up.”
Yes, I see the metering as you describe and his Presonus interface is selected within the Performer app on his computer.I see it in the setup on my end as well.
I have also done my best to emulate the Cubase setup shown in the primer for the mixer and Studio control modules and I believe they are the same. However, my TB mic (selected as input one of my Apollo in the routing preferences) can not be selected under the VST Cloud menu (always grayed out). Nonetheless, I see meter activity in the VST mixer when I implement TB. I guess that’s ok.
But one thing is for sure, setting up a new VST Cloud session does NOT automatically configure the session for a successful collaboration. Is there a sequence you recommend I follow to take advantage of this?
After hours of frustration with both Cubase 9 and 10 demos I am still hoping to be able to succeed at setting up a working connection. If and when I do, we will be happy to purchase Cubase.
In the meantime, if there is anyone who would be willing to help me set up a test session, I would be grateful. Thanks again.
Can’t set up a test session at this time, but we have some more details, so let’s see.
I assume that you may not been into Control Room yet. Having experience in studio-recording already, it should come easy.
The Talk Back mic is a function of the Control Room, open up CR editor and assign TB mic there if you haven’t already. VST Connect integrates tightly with the Control Room, so when problems arise, this is your second stop. First is “Create VST Connect”, but this may not solve all issues if you have configured too much yourself, so it counts for an “Empty” project. So, more datails:
“Yes, I see the metering as you describe and his Presonus interface” well then he should hear it. The “Master” channel should also move, as it should receive the input. Master is what should be on Performers’ headphone so if any of these "should"s don’t apply, there’s some serious flaw that we haven’t come across yet, like no master bus or having the direct/daw control on the Interface set all to direct, but then he should hear himself for sure.
So: Cubase Mixer Cue + Talkback -> Control Room -> VST Connect -> Internet -> Performer -> “Studio” Channel. “Studio” + “Mic” + instr + VSTi -> Perfomer “Master” channel. The Master channel also has a bus assignment at its top, I assume you have set that to Presonus Headphone output. Make sure Performer hasn’t messed with Presonus HW mixer.
“Mic” + “instr” + “VSTi” -> Internet -> Cubase VST Connect -> a) track input and -> b) VST Connect Monitor plugin in following Control Room Master (or Headphones).
I repeat that when Performer Mic channel meters move (in the VST Connect Performer Monitor mixer), “Master” must move along with it (plus what is beeing received from “Studio”) and thus be heard by Performer if Master output is assigned to his Headphone port.
“I have also done my best to emulate the Cubase setup shown in the primer for the mixer and Studio control modules” - what “primer” are you referring to? Will check that and the manual, as it appears to be outdated. Just use “Create VST Connect” (with an “Empty” project!) and then let us know what doesn’t work. And look at the LEDs, they should normally all be green (occasional exceptions are ok). Hope that helps.
I do appreciate all your efforts. I will also stop by the booth at NAMM for a hands-on demonstration with one of your associates. And the primer I refer to is the link you provided, https://connectvst.com/. In the meantime, some progress. I set up an empty project and had the artist swap out his brand new Presonus interface for and older M-Audio he had about. I checked the routing and CR setup per the primer and, after selecting the correct input from the interface (input 1) and lowering the M-Audio buffer to 256, he was able to hear the music mix I imported and his voice in reasonable sync as did I. The TB worked as well. Not at all sure what the difficulty is with the Presonus as it functioned unpredictably. Maybe it doesn’t like the latest Mac OS. Unfortunately, Cubase crashed and did not retain the saved session nor any .bak’s. But before this happened, I began to play with the VST mixer levels and EFX. I was not able to hear any reverb, etc. but I hope to get this working next. Well. at least it’s a step in the right direction. Cheers.
Performer reverb is fed by a tiny fader in each source channel (horizontal reverb send fader). Then if reverb is active and level is up it should work.
Sorry to hear that Cubase crashed, it is very stable normally. If you like, you can send the crashlog as a PM to me so we can check. Also Cubase does auto-save (to .bak), but you may have to enable it in preferences.
Thanks for your patience.
Well, made some good progress last night but still have some issues to resolve. First, when I set up a new session with the artist using his old M Audio interface which had worked the night before, he could see metering in the Performer app but could not hear anything as with the Presonus interface. I finally solved this by de-selecting the M-Audio in the app and immediately re-selecting it. Success!! We tried the same steps with the Presonus and it also worked! Perhaps this is a software bug that can be looked in to. Could also be an OS thing. I also noted that before connecting to the artist, the tiny EFX faders you mentioned are labeled EFX. After connecting, the label disappears. Thanks for showing me where to look.
Now that I can make the system function I can begin to focus on optimizing the setup. Even at the lowest resolution for audio and video, we are still experiencing audio glitches (even without video). I am sure this is due to problems with out internet connections. I am currently unable to hard-wire into the modem due to the location of the music room in my home. My Wi-fi speed is generally 25 MBPS DL and 11 MBPS UL. The connect side meter in the VSTC window shows full. The artist’s setup is currently Wi-fi and shows around 29 MBPS DL but only 5 MBPS UL. The performer meter in the VSTC only shows about 30% green. Is this telling me there is more of an issue on the artist side than mine (he will purchase an ethernet cable shortly)? Thanks
As long as those meters show more than 5% at any time, all should be well and there is no reason for audio glitches, but watch out for the LEDs. Does any of those go red when glitches occur? In any case, as you appear to have a very long distance connection and even the speed of light becomes a limiting factor then, you are advised to raise the “Remote Latency” setting to 2 seconds or so. The only disadvantage is that it takes a bit longer for the music to start when you hit play. Also if possible you should connect via Ethernet, not WiFi. Bandwidth is not of concern nowadays, only connection quality.
“de-selecting the M-Audio in the app and immediately re-selecting it” - you should not have to do this. If the problem persists, we would be interested in an exact sequence of operations, what is selected when Performer is started and what else did you do before and after connecting etc.
As far as I can recall, the glitches do coincide with the LED’s going red. I will pay closer attention when we next test the system. Hopefully before I leave for NAMM. Thanks for the suggestion on adjusting the Remote Latency. A small inconvenience if it solves the problem under the current internet connection scenario.
I will try to provide you with an outline of the system status when the de-select/re-select issue arises (each time thus far). Cheers
I ran the latency up as high as four seconds but it did not solve the glitch problem unfortunately. The glitches ‘seem’ to coincide with the red LED flashes as far as I can tell. If you have any other advice, I’m happy to try anything. Thanks
Which LED flashes red?
Anyway, you may write a private mail and we can try something.
Sorry for the late reply. The show was very busy. I visited the Cubase booth but unfortunately there was no VSTC setup due to the exorbitant cost of two internet feeds. My email is email@example.com. Before we try a session, it was recommended by one of your associates that I look into optimizing my router settings first. I will let you know when I am able to get this done. Cheers
Well, after both the artist and I connected via Ethernet cables and after setting to the lowest working resolutions, turning off video, adjusting the modem port settings and increasing the remote latency, the result is that the artist had an improved experience but I still experienced perhaps fewer but regular glitches nonetheless. I have now invested considerable time and money, discovered and solved a bug in VSTC (deselect/select the interface) but am left quite frustrated that I can not experience a glitch-free session. Any suggestions left? Thanks
I will send you a mail.
Sadly you will write him an email. I have also problems with understand and configure vst connect pro in Cubase 9 / vst connect performer.
And bigger for me is, that i am from germany and have to understand all your english explanations.
And the manual in german is not up to date. All the explanations on the website are also not up to date. Just for example: I read on the steinberg-site, that vst connect pro is not included in Cubase 9 pro. But i can choose it from the top line of cubase ???
So, it would be great, if we could read here the end of the story. Just as an example how it could work and where the problems in this case were.
There are two issues here, one is that there appears to be some installation problem that leads to VST Connect PRO appearing where it shouldn’t - the PRO version needs to be purchased and is not supposed to show in the default menu. We are looking into this.
Secondly, there are specific connection quality issues that we try to improve, and this is a long-range case that we treat specifically.
Kannst mir auch auf deutsch schreiben
But not here. Or?
I don’t want to confuse the other more than it has to.
Totally agree. Had this discussion on another thread…I have Cubase 9.5 and VST Connect Pro is working fine for me without a license. In my confusion to get Pro working, I did add a temp trial license from Steinberg. However, I have removed that and it still seems to work.
All very confusing…but I am happy with my Pro so far (as it hasn’t cost a penny!).
… if you have bought Cubase all products will be available for 24 hours. That applies to VST Connect PRO, too. But it is not part of Cubase - only VST Connect SE is part of it. If you still have access to VST Connect PRO (without a valid license) I would like to know how this is possible Could you please open the “eLicenser Control Center” and create a screenshot of your available licenses and send it to me? (m.spork (at) steinberg.de)
Thank you very much,