VST Connect & VST Connect SE - Solution Thread

Most probably, you have activated the Loopback function (“Mon” button on the right side). This is only for controlling what the Performer actually hears, do not activate it for recording. The next version throws a warning when you activate this function for the first time.
Does that solve it?

Hi Musi!

Very Cool . . . . uh . . .when?

OK. Yeah, I missed that. Great.

I understand. I got a bit carried away in my post. That particular functionality - which you correctly interpreted - is really a whole different product requiring a ton of development.

My BIG Request that I buried in there was the “Rehearse” thing - though it’s not really a rehearse feature.
It would allow the STUDIO side to add things to the project while the Performer side LISTENED (only) in full fidelity.
And then, with a press of a button, the PERFORMER side could add something while the Studio side listened (as it already works), and so on . . .

Looking forward to it!!
Next week, you say??

Hugh

Yep. Just as I thought . .

Thanks, Musi!

Hugh

So I noticed connect pro is out supporting OSX 10.9, if I buy this product do you think it will work ok with Mavericks even though Cubase 7 doesn’t officially support it?

VST connect Pro should be included with Steinbergs “Pro” application Cubase 7! Is this Steinbergs future business model? Include a version that doesn’t work properly with Cubase (just look at this thread), and is a mess when it does, just to drum up business for an outrageously expensive “Pro” version.

I, for one, will not waste money on this and I hope that more follow suite, just to make a point that we don’t fall for this kind of behavior. If not it will not be long before Cubase becomes a collection of broken features that is only meant to drum up sales of expensive “Pro” versions of the features!

Cubase for €4000, anyone?

I’m sorry Svenne, but I don’t see anything in this topic that indicates that this doesn’t work. What I do see is a dedicated developer working to sort people’s problems out and helping them with setting this up.
It seems by far most people get this working with some help so I don’t know what you’re talking about.

Feel free to make a point by not buying though.

… VST Connect Pro runs fine with Mavericks, but it needs Cubase 7. And the current version 7.06 has some problems with Mavericks. In fact, you could run in problems when you run Mavericks, Cubase and VST Connect Pro. But the upcoming Cubase update will fix that.

/Michael.

This new thread dedicated to VST Connect is probably worth a look:

[/quote]
Most probably, you have activated the Loopback function (“Mon” button on the right side). This is only for controlling what the Performer actually hears, do not activate it for recording. The next version throws a warning when you activate this function for the first time.
Does that solve it?[/quote]

I had direct monitoring set on the UR824. Once I undid that I was fine. They should probably include that in the “quick start” instructions somewhere…

Thanks for your help.

Thanks Michael looking forward to the update. VST Connect is something that really appeals to me, I can’t wait to get it going

Hi all,

After reading all the information here I am still at a loss because I cant get VST Connect SE to work properly!

In a nutshell I can hear the artist, he can hear me, he can hear the recording when it starts, it starts to record then suddenly the recording drops out! The artist can still hear the music track and he doesn’t hear it stop the audio track just stops recording what he is playing!! I have 2 full blue bars at the top so I would appear to have good signal strength in both directions, and they never go into the red area!

My sig is below and we are both using Steinberg CI 1 interface, I have altered all the parameters I can at both ends, as instructed in the manual, we have both gone to a wired connection as opposed to wireless, but no change!! I am stumped!

Basically I have run out of options so am I missing something simple here?

And before anybody chimes in with RTFM, I already have and I have used Musiculums post on how to set up VST connect within a programme, but still didn’t get it working properly!

I am using a piece of music with 6 audio guitar parts and 2 midi parts on it as a “test” project and the artist is trying to put a drum track on the piece! I am bouncing the entire piece (audio & midi) down to one and using that as the track I am sending to the artist. As I always record in Flac format that is the file I am using, is there any reason that would cause this issue?

This is the first time I have played with this since the latest Cubase 7.06 update and I know, with other issues on this forum, one of the normal solutions is to “trash the preferences” so do I need to something like that here?

Anyway I am stumped and that is a great disappointment to me because even the SE version would be a very useful tool if I could get it to function properly!

So if anyone has any ideas or could offer any advise it would be greatly appreciated.

Jim B

just some that come to mind:

  • basically all seems to be set up right. VST connect can not make a recording stop in Cubase, so there must be other reasons within Cubase that cause this to happen.
  • what exactly happens on your end: does Cubase continue to play without stutter and just punches out? If so, stupid question: are you sure to not have auto punch out activated?
  • with the very same project but not beeing connected: can you record your own mic without Cubase dropping out of recording?
  • activate the VST Performance Meter: any overloads there?
  • make sure ASIO Guard is off
  • make sure Constrain Delay Compensation is off - you probably have that anyways as it won’t work in the first place
  • if all else fails: load the VST Connect template, connect your mic, bring in your playback mix and try to record your partner: will it still fail?
    Hope that helps…

Thanks Musi,

I’m at work now but I will try all that tonight and let you know what happens!

Jim B

Hi Musi,

I went through the various check lists, sent by yourself and various other people on the forum, this evening and it was Asio guard that was the culprit!!

I have never knowingly activated this but, once I found it and deactivated it, VST connect SE runs a smooth as silk!

I tried 7 takes tonight with my drummer and each one was perfect! I am totally knocked out by this and very tempted by the PRO version!

Thanks for your help in this!!

Jim B

Hello!

A few days ago I was trying to get to work VST Connect SE, and after a few attempts I got this error:
YOU ARE ALREADY IN A SESSION. I restarted the modem, router and the computer (Mac 10.8),
but this message kept showing up.

Anyone has an idea of what to do?

Thanks for your help.

Roger

Hi Roger,

When I was experimenting with this I sometimes forgot to log out from each VST connect session before attempting a new one and I seem to remember getting a very similar message!

You may not think so at the moment, but trust me, when you get this to work you will be mighty impressed!

I’m looking forward to the 7.5 update as this programe has also been improved :smiley:

Good luck,

Jim B

Today I was trying VST Connect SE and got a message that I needed to either change my sample rate, or the sample rate of my performer as they were not matching. I changed mine because it was the easiest thing to do. But I couldn’t figure out how to change his sample rate. Is it something I can do from the VST Connect SE control panel or do I need to do it on his computer? If so, where are these settings?

He has a presonus audiobox, but he was NOT using that. He was using a Bue Yeti usb microphone (had to install ASIO4ALL in order to get it to see the VST Connect SE). But the presonus audiobox was still connected. Could this have been set to 48k? I didn’t see any 44.1k/48k settings on the ASIO4ALL control panel. Any ideas would help.

Can I get a refund on Connect Pro? If I would have been aware of the massive amount of issues I would not have purchased it today. I love Cubase and just upgraded to 7.5 but in regards to ‘Connect Pro’ …I feel like I just bought something broken.

Can you let us know what the problem is? I take you cannot connect? I have personally had several successful connections to the US (from Germany).