|
|
Post by EmRR on Oct 12, 2023 10:11:49 GMT -6
I can get it to stream fine to another DAW, but I can't get it to accept a stream from another DAW without a rhythmic sync stutter. Have tried every imaginable variation of audio engine for each DAW, aggregates, mixed aggregate and non-aggregate.
Generally seems flakey about remaining in the I/O window, I can open that and sometimes it's just gone, all the assignments gone, aux I/O suddenly unchecked.
|
|
|
|
Post by Ward on Oct 12, 2023 11:17:32 GMT -6
Getting all DAW designers/engineers to adopt a standard would solve so many problems.
Getting that to happen would take a miracle or a military backed court order.
|
|
|
|
Post by drumsound on Oct 12, 2023 12:31:14 GMT -6
Getting all DAW designers/engineers to adopt a standard would solve so many problems. Getting that to happen would take a miracle or a military backed court order. PREACH! |
|
|
|
Post by EmRR on Oct 12, 2023 13:05:02 GMT -6
I'll add that I gave up and used Blackhole to stream PT to another DAW no problem, curious if Bridge is proving to be unidirectional for anyone else. Probably very few use it anyway.....
|
|
|
|
Post by lee on Oct 12, 2023 17:20:11 GMT -6
Hmmm, it's working fine here. Are you using an aux or an audio track (in input) to stream into?
Also, if you're losing it in I/O Setup, what happens if you click on "Restore from session"?
|
|
|
|
Post by EmRR on Oct 12, 2023 20:34:17 GMT -6
Hmmm, it's working fine here. Are you using an aux or an audio track (in input) to stream into? Also, if you're losing it in I/O Setup, what happens if you click on "Restore from session"? Audio track. Honestly don’t understand PT aux tracks so far. Restore from session has pulled up some previous thing, lacking Bridge, even though it’s been saved/closed/reopened and been present. Then just…poof…and restore made a bigger mess at that point. Perhaps i changed audio engines in between and that blew it up. |
|
|
|
Post by lee on Oct 12, 2023 22:29:25 GMT -6
Hmmm, it's working fine here. Are you using an aux or an audio track (in input) to stream into? Also, if you're losing it in I/O Setup, what happens if you click on "Restore from session"? Audio track. Honestly don’t understand PT aux tracks so far. Restore from session has pulled up some previous thing, lacking Bridge, even though it’s been saved/closed/reopened and been present. Then just…poof…and restore made a bigger mess at that point. Perhaps i changed audio engines in between and that blew it up. Luckily you can close without saving... I've not seen what you're seeing, and have been using bridge since it was released. I'll try to poke around a bit though. Sorry you're having a bummer. |
|
|
|
Post by lee on Oct 13, 2023 11:10:02 GMT -6
Other questions that might jog a solution:
What is Pro Tools’ buffer setting? Have you altered that, not just other Playback Engine settings?
Can you try something other than another DAW to feed into PT? Try changing the computer’s sound output preferences to audio bridge. I usually have an aux track in my template that puts any Mac sound or other app on a fader that I can control. This would include YouTube, Spotify, Tidal, etc. But none of these are DAWs strictly speaking, and I wonder if two apps using mission critical clocking is somehow causing this for you.
There’s one more thing about I/O Setup that I suspect, but I need a minute to confirm what I’m thinking.
|
|
|
|
Post by kbsmoove on Oct 13, 2023 13:08:11 GMT -6
I've used it with varying results. Pumping tidal into PT to reference other mixes only works sometimes. Seems like higher buffer settings work better.
I've used audio bridge to bring audio in from Ableton a few times with no problems at all.
|
|
|
|
Post by EmRR on Oct 15, 2023 19:00:54 GMT -6
Other questions that might jog a solution: What is Pro Tools’ buffer setting? Have you altered that, not just other Playback Engine settings? Can you try something other than another DAW to feed into PT? Try changing the computer’s sound output preferences to audio bridge. I usually have an aux track in my template that puts any Mac sound or other app on a fader that I can control. This would include YouTube, Spotify, Tidal, etc. But none of these are DAWs strictly speaking, and I wonder if two apps using mission critical clocking is somehow causing this for you. There’s one more thing about I/O Setup that I suspect, but I need a minute to confirm what I’m thinking. Thanks OK, buffer was 256, now 1024. No diff. Works fine via Blackhole, Bridge has same stutter on input monitor, go into record - sometimes a CPU overload warning, but none seen in Activity Monitor. Analog out is through a MOTU 16A, that's second in an aggregate with Bridge, drift comp checked on 16A. Tried other DAW as just Bridge output, and as part of same aggregate. OK, YouTube into PT via Bridge with System Preferences/Sound selected to both I/O as Bridge does the trick. It took 2 toggles of output to Bridge to actually make sound. The thing getting lost in the selections is the 16A. It's now not selected as an output, but sound is still coming out the previously selected pair. Weird. I noted if I am in PT playback with an aggregate engine and the output is getting to the 16A with a Bridge assignment name, if I switch to 16A as the engine the output monitor path changes to the 16A, but the output assign names don't change. |
|
|
|
Post by lee on Oct 16, 2023 14:41:39 GMT -6
Other questions that might jog a solution: What is Pro Tools’ buffer setting? Have you altered that, not just other Playback Engine settings? Can you try something other than another DAW to feed into PT? Try changing the computer’s sound output preferences to audio bridge. I usually have an aux track in my template that puts any Mac sound or other app on a fader that I can control. This would include YouTube, Spotify, Tidal, etc. But none of these are DAWs strictly speaking, and I wonder if two apps using mission critical clocking is somehow causing this for you. There’s one more thing about I/O Setup that I suspect, but I need a minute to confirm what I’m thinking. Thanks OK, buffer was 256, now 1024. No diff. Works fine via Blackhole, Bridge has same stutter on input monitor, go into record - sometimes a CPU overload warning, but none seen in Activity Monitor. Analog out is through a MOTU 16A, that's second in an aggregate with Bridge, drift comp checked on 16A. Tried other DAW as just Bridge output, and as part of same aggregate. OK, YouTube into PT via Bridge with System Preferences/Sound selected to both I/O as Bridge does the trick. It took 2 toggles of output to Bridge to actually make sound. The thing getting lost in the selections is the 16A. It's now not selected as an output, but sound is still coming out the previously selected pair. Weird. I noted if I am in PT playback with an aggregate engine and the output is getting to the 16A with a Bridge assignment name, if I switch to 16A as the engine the output monitor path changes to the 16A, but the output assign names don't change. Weird. I have also had trouble getting the renamed busses to show up where you expect them to. It's inconsistent. It sounds like PT vs Core Audio, maybe. I don't run in aggregate mode (and am inexperienced with it), so I don't have anything intelligent to say about it. When I'm not running HDX or HD|Native, I'll run like an Apollo Twin or a Scarlett, but I run them straight up in the playback engine and have not experienced any funny business. And before Bridge, I ran Source Nexus which was solid, but incredibly overpriced. Didn't tried Black Hole. I wish I knew how to solve it. |
|
|
|
Post by EmRR on Oct 16, 2023 21:11:07 GMT -6
Interesting I didn’t have to mess with pref/sound going the other direction. The other DAW is DP which has a checkbox to either follow or ignore system pref, so maybe to do with that.
Drift correction in aggregate mode is basically resampling on the fly, and will cycle phase on anything split across 2 different devices, so you really only want to use it for non-critical things like non-critical playback.
|
|
|
|
Post by lee on Oct 16, 2023 23:35:04 GMT -6
Interesting I didn’t have to mess with pref/sound going the other direction. The other DAW is DP which has a checkbox to either follow or ignore system pref, so maybe to do with that. Drift correction in aggregate mode is basically resampling on the fly, and will cycle phase on anything split across 2 different devices, so you really only want to use it for non-critical things like non-critical playback. If you disable drift correction does it behave better (apart from likely clicking errors)? |
|
|
|
Post by EmRR on Oct 17, 2023 8:09:50 GMT -6
Interesting I didn’t have to mess with pref/sound going the other direction. The other DAW is DP which has a checkbox to either follow or ignore system pref, so maybe to do with that. Drift correction in aggregate mode is basically resampling on the fly, and will cycle phase on anything split across 2 different devices, so you really only want to use it for non-critical things like non-critical playback. If you disable drift correction does it behave better (apart from likely clicking errors)? No effect on PT. |
|
