Source Connect Issue

[ShadeTek]

Is anyone having Source Connect issues since updating to the 2022+ version?
We hadn't used SC in over a year and went to use it only to find we were getting #120 issues, only curable by uninstalling and reinstalling SC. This however then caused PT to crash to desktop as it loaded the SC plugin.

The only way PT would start if SC was completely uninstalled.

I am on Z440 win 10 hdx/x-mon, sync-hd set up.

[its2loud]

2022+ version? That’s very vague as there are 6 Pro Tools versions released in 2022 thus far.

What version of Source Connect?

Do you have Source Nexus?

Did you have a look at this?

https://support.source-elements.com/...arch=101727071

And this

https://support.source-elements.com/...nk-and-windows

[cubivore]

did you ever figure this out? i'm having the same issue and have tried everything i can think of.

Originally Posted by ShadeTek

Is anyone having Source Connect issues since updating to the 2022+ version?
We hadn't used SC in over a year and went to use it only to find we were getting #120 issues, only curable by uninstalling and reinstalling SC. This however then caused PT to crash to desktop as it loaded the SC plugin.

The only way PT would start if SC was completely uninstalled.

I am on Z440 win 10 hdx/x-mon, sync-hd set up.

[sw rec]

I highly recommend reaching out to Source Connect on this one. Their tech support is fantastic. (SC-Pro Tools-Windows is a tricky enough combination that the self proclaimed famous “engineering guru” from LA ghosted me altogether, but SC’s tech had me up & running trouble free in 15 minutes.)

[cubivore]

thanks for the tip! source elements have been closed during the holidays so i'll try tomorrow.

Originally Posted by sw rec

I highly recommend reaching out to Source Connect on this one. Their tech support is fantastic. (SC-Pro Tools-Windows is a tricky enough combination that the self proclaimed famous “engineering guru” from LA ghosted me altogether, but SC’s tech had me up & running trouble free in 15 minutes.)

[sw rec]

Good plan. In the interim, make sure you have the latest installer. Once SC set it up for me, it performed flawlessly on Windows….setup on MAC was about as easy as it gets.

[The Weed]

I second S-C's support, they are normally very helpful. The only issue I've had with v3.8 on Windows is when using the AAX Link Plug-in. I would have intermittent squeaks and squawks in the signal coming from the remote end. No problem with my signal going to the remote end. S-C support suggested using a separate interface for S-C, but, since I have RME's TotalMix, I stopped using the Link plug-in and route my signal to and from the Standalone version. This issue on Windows is supposed to be fixed in the so far vaporware v4.0. (One other issue I have run into is not being able to hear the remote end if they do not have port: open, but that is a known issue for some whether on PC or Mac. I always have port: open at my end.)

If you don't need Source-Connect, or as an adjunct to S-C, have a look at www.sonobus.net. Similar to and in many ways superior to Source-Connect - and it's free.

[sw rec]

I use SC exclusively as a standalone, with a Focusrite Scarlett 2i2 front end. If I need to run Pro Tools simultaneously, all my Pro Tools audio goes thru my UA Apollo 8. I do keep the two separate, so do NOT use SC as a plugin.

[albee1952]

My solution was to run it on a separate machine(laptop) and route audio to/from by using a small 2 IO interface on the laptop.

[cubivore]

interesting tips on the second interface. I already do this with a DigifaceUSB for SCNow and browser audio for protools HDIO, but always ran the aax link for SCPro. I don't think i'm having any issue with the link plugin since I can't even log in (error120) and do a port test (grayed out), and I've tried running just SCPro with no PT running and get the same results.