![]() |
Avid Pro Audio CommunityHow to Join & Post • Community Terms of Use • Help Us Help YouKnowledge Base Search • Community Search • Learn & Support |
|
![]() |
|
Thread Tools | Search this Thread | Display Modes |
#11
|
|||
|
|||
![]()
BlackHole has never let me down on MacOS.
__________________
MacBook Pro: 16GB M1 Pro 8c Hackintosh: MacOS Catalina, i7 6700k, 32GB RAM, RX580 Pro Tools Studio, RME RayDAT PCIe http://www.liamgaughan.com |
#12
|
|||
|
|||
![]() Quote:
I've been struggling too. I run a VO studio, and used Nexus for a big template with Skype, Zoom, Teams, iPDTL... loads of ins and outs, and AUX IO looked great when I set it up and my template halved in size. It started clicking and became unusable though, and I was about to go back to Nexus when I lowered the PBE buffer size and it all worked properly. I don't know why LOWERING the buffer size worked, but a thought occurs - maybe the Pro Tools buffer has to match the Source Connect buffer? I normally want my buffer high-ish in Pro Tools (no reason to keep it low if there's a delay on SC anyway)and low in Source Connect (keeps the latency down). Is it this mismatch that's significant? Either way, for those moving from Nexus to AUX IO, it's been a fix so far for me. Source Connect Standard has a changeable buffer, but it sounds like Source Connect Now has an ultra-low buffer. The lower I can get my buffer in Pro Tools with AUX IO, the better SC Now works, which points towards my theory being correct but I'd like to know what others experience |
#13
|
|||
|
|||
![]() Quote:
Buffers have to match or at the very least they have to go from lower to higher. Not higher to lower. Therefore, if Pro Tools is set to a higher buffer than what it’s sending to, you will have clicking issues or or no audio at all. Aux IO does not have its own buffer setting, nor does it automatically rebuffer to match the destination. |
#14
|
|||
|
|||
![]() Quote:
|
#15
|
|||
|
|||
![]() Quote:
https://avid.secure.force.com/pkb/ar...sked-Questions As for anything not mentioned in the article, it’s just based on my experience and feedback from Avid with Aux IO and sending to/from devices. Clocking errors and buffer errors seem to be the most egregious with Aux IO. It’s frustrating when you don’t know the buffer setting of a software or system you’re sending to or receiving from. |
#16
|
|||
|
|||
![]()
It’s frustrating when you don’t know the buffer setting of a software or system you’re sending to or receiving from.
So it would make sense to set the Source Connect to Auto? |
#17
|
|||
|
|||
![]()
It’s frustrating when you don’t know the buffer setting of a software or system you’re sending to or receiving from.
So it would make sense to set the buffer to Auto in Source Connect? |
#18
|
|||
|
|||
![]() Quote:
Here’s some info on SC buffer setting. https://support.source-elements.com/...ameters-buffer |
#19
|
|||
|
|||
![]() Quote:
Hmmm... Hence my original question and the confusion it's causing. I've just done a SC Now session with a VO in Canada, and he was getting glitches that made the session unmanageable. Dropped PT to 128 and it was as solid as any connection I've ever had. |
#20
|
|||
|
|||
![]()
Yep, I think the lower the buffer setting in pro tools, the higher the success rate with connecting to outside services such as SC Now. Like I said, a higher playback buffer in Pro Tools to an external lower buffer is prone to glitches and dropouts.
|
![]() |
Thread Tools | Search this Thread |
Display Modes | |
|
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Avid CoreAudio Device in System Preferences | Daryl Hughes | macOS | 4 | 01-01-2014 10:41 AM |
Mbox 3 not sticking as system output device | darwiniandude | macOS | 1 | 12-15-2010 01:27 PM |
I disabled Mbox in device manager - How do I enable again? | stev | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 3 | 04-27-2008 02:32 PM |
master clock device for mix system? | digidesigner | Pro Tools TDM Systems (Mac) | 2 | 01-30-2008 01:53 AM |
Digi001 as preferential in\out multimedia system device? | salvo | 003, Mbox 2, Digi 002, original Mbox, Digi 001 (Win) | 0 | 07-02-2000 01:40 AM |