Monitoring problem

I’ll give it a try and let you know. Thanks.

This happened to me too on a session lastnight! Once it started working, it stayed working though. Sync was better than the previous day, so maybe it was temporarily due to the internet bandwidth (performer was in the US and subject to bandwidth throttliing – thanks Donald!).

Now I just have to figure out how to get talkback working (but I know that’s my fault somewhere).

One pitfall with Talkback is that there are actually two places where it needs to be enabled, one in the Master section of the Control Room, and one for VST Connect Cue (which is coupled with the VST Connect plugin Talkback button).

the 2 green buttons in the pic

(talkback and TB)

FWIW - it’s really worth reading up and understanding the Control Room setup

Good point re bandwidth issues. I’m not sure if this is talked about enough. I’ve seen this a few times and got the end user to check using https://www.speedtest.net to see what’s happening. Most are unaware of the issues around bandwidth. Some have 50mb download speeds but barely reach 4mb on the upload. I remember upgrading my connection to have more parity for both up and down. I did this when I started using Source Connect a few years back. I’ve not had any issues with connecting to users with a min spec of 50mb download and 20mb upload.

@musicullam has there been any tests done regarding internet connection bandwidth?

yes, and I keep repeating that in 99% of all cases speed is not of any concern. Quality is, and there are enormous differences (mostly Internet Providers and local differences).
For VST Connect with default settings, even less than 1 MBit upstream is quite sufficient. The problem is timing. Netflix can buffer for 10 seconds, we can’t, and thus have to rely on data to be provided within required timeframes.

I’ve had issues with people with much more bandwidth than that.

If you monitor the bandwidth being used you can see that drop as low as a few hundred kb/s if you set the video/audio bandwidth to the lowest settings. 4Mb/s upload ‘should’ be plenty. Sync issues are not to do with bandwidth (IMO) - many other factors at play here (buffer sizes - cpu load (?) - latency variation)

Been playing with some of the other remote recording software (source connect / session link pro / cleanfeed) - apples and oranges obviously but didn’t have any dropouts or sync errors


(just spotted musicullum replied whilst I was typing this)

even at 5 seconds delay I get sync errors on high bandwidth connections

5 seconds doesn’t make sense, more than 3 is counter-productive 2-2.5 recommended.
We try hard but requires some concentration we don’t get.

2 - 2.5 gave sync errors - so tried more. Made no difference

Thanks, it’s good to have a benchmark re expectations. If you’re repeating it a lot then there must be a reason the info isnt gettig through to newbies and others alike. I also don’t think many here will understand what you mean though by timings in general. If you mean the ping time, it would be good to know for clarification etc. I’ve attached a screenshot of a speed check I’ve just done.


I don’t use my studio computers for anything other than audio, and ensure there are no background apps running that would interfere with the network.

I’ve noticed that I only get reliable recordings when both parties are;

  1. on the same software version
  2. record at 44.1 anything higher produces clicks and dropouts
  3. when both connections are min 30mb dl and 10 mb ul, ping time below 10 secs
  4. they don’t have anything else using bandwidth or running at the same time. i.e. windows update running in the background.

I started a project today with VST Connect with a voiceover artist (first time with this client) they met all the reqs. Session started all was going well and then sync issues / dropouts. After a few mins they advised that they had facebook, whatsapp and mac mail notifications coming in. We switched to a different system for the project in the end for convenience.

VST Connect is a BRILLIANT and ever improving product that I have total faith will be THE ONE to use at some point. But for a hassle free experience, and as there’s no way to write a manual for every existing comp config, a clear baseline re settings and other key factors for successful use to help with expectations is still required.

UAD will say on their site for instance, min reqs and supported hardware etc. If your system and connection, doesn’t meet the spec then basically don’t come moaning to us about it not working. The absolute ideal would be some sort of calibration tool that you run on your system that lets you know where your system and connection stands for use with VST connect. The two connection and sync lights presently offer little insight.

@musiculllam I write this as a MASSIVE fan of the product and someone who wants to see it continue to succeed. If a spec was written out inc connection specs, I’d arrange to have the comp built and the connection installed, that’s how useful and important I feel this tool is. It opens up alt business opps. For those like me who also use Source Connect, it’s not the same and doesn’t offer the same functionality. I personally don’t like the product or the way manage things. Similar but different tool sets where VST Connect especially the pro, is way more advanced and useful.

great, but that’s not my (or other people’s) experience and I’ve been using this (or attempting to) since late 2012. Honestly, I do know what I’m talking about

Hi dr, I only pointed out my own experience, no one else’s. Can I not offer my experience as well? I started using VST Connect Pro in 2013

apologies - it’s been a long long day :blush:

No worries :blush:

hi fuzzydude, thanks again for your support. We really need it, as things are getting crazy since the Corona spread.
First, I agree to all you said, except for these:
“2. record at 44.1 anything higher produces clicks and dropouts”
We absolutely cannot confirm that, I work 48k all the time. Of course, this is a demanding system and high sample rates like 96k may cause problems, but that depends on your systems’ capabilities and buffer sizes.
“3. when both connections are min 30mb dl and 10 mb ul, ping time below 10 secs”
You probably mean 10 millisecs. That’s also not trrue. I had a glitch-free working connection from Hamburg to New Zeeland, where the speed of light alone takes approx. 66 ms to travel in one direction (if there was a direct cable - there is not). We had ping times around 250 ms and all was fine, recording with Remote Latency of 2.5 seconds.
As for better documentation - you are perfectly right, and we take whatever we can get. We’re a small team and set up connectvst.com, but currently we have to put all forces to get video sync and increase quality - stability has been improved very much already, almost no crash reports anymore. Step by step :slight_smile:

can’t remember the last time I had a crash (actually I can but it wasn’t recently :smiley: ) - your efforts are greatly appreciated… Thank you both.

thanks!

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Absolutely! I think you are doing fantastic work on this. :sunglasses:

Firstly, you’re most welcome. It’s such a great tool to have. This is great info and I’m not surprised re the upsurge in interest as a consequence of the Corona virus. I expect that eyes have been opened re the possibilities of remote working, and I don’t imagine they will close again even after we’re through to the other side of it. There’s a clear business opp here for engineers etc.

I have a good connection and high spec systems, so I can look into other areas re my setup. I’ve not had a crash or lock up ever with VST Connect. I will get to the bottom of it and share what I find. (I’ve sent you a PM) :smiley:

I’m using a pretty high spec PC here - and have access to multiple gig of internet…that’s not the issue IMO. I’ve has sessions that have been glitch free, for hours. And sessions where you can’t get reliable sync at all.

you’ve not been using it long enough :smiley:

The last few months has been a radical change for VSTC - was unusable before (I can list the bugs but trust me - if you looked at it the wrong way or clicked on the wrong thing it would crash - normally taking the host with it)