4 ms·
> Ironically Pro Tools is still not M1 native. that does not surprise me at all, unfortunately. > One cool thing in MacOS that Windows can't do is aggregate o
by foxhill 4y ago
> Ironically Pro Tools is still not M1 native.
that does not surprise me at all, unfortunately.
> One cool thing in MacOS that Windows can't do is aggregate of audio devices/interfaces.
it does come at the cost of latency & jitter: fundamental issues that ultimately stem from having two separate audio clocks. and it's not really a specific limitation of windows, which tend to use ASIO for low-latency audio. there's nothing stopping a an aggregate ASIO driver from being written, i just can't imagine it'd be that useful, indeed, i've only ever used the macOS aggregate device a handful of times, mostly only to try it out.
- ilyt 4y agoI used it in Linux, but that's because it detected 2-in/4-out audio interface as just three stereo pairs and I needed to split those inputs off to mono. It was a lot of CLI fuckery, not a pleasant experience... and of course pulseaudio can't just remember it, need to be re-applied after every USB reconnect. Can be done with UDEV but not exactly something random user would know how to do.
- steve1977 4y agoThe one time I've actually used an aggregate device, I synced the clock of one device to the other. It worked fine as far as I remember (it's been a couple of years).
- 72deluxe 4y agoMine didn't in practice. I think one was a FireWire audio interface and the other USB. Never could get it to work properly.