In both cases, the audio goes out over USB and gets recorded to disk, it's just a question of what route does it continue on to get to the bus that drives the phones/monitors. which can either be the short post-fader path in the X32 or all the way through the DAW and back into the X32 via USB returns channels. There are many other ways to approach your monitoring, but can definitely flexibly switch between direct and through the box monitoring. This is not relevant because the Behringer x32 only does USB 2.0, but I'm pretty sure USB 3 is capable of (much) lower latencies. This is a phenomenally confusing way to kick off a discussion in an audio forum about the abstract theoretical limits of USB round trip times in non-audio applications. For at least one specific combination of protocol-mode, chipset, on an RT kernel that can't run desktop software, and possibly on a custom/toy driver. it is possible to transmit a single packet with a very short round trip time. As you note, this finding is completely irrelevant to audio interface latency, though. It's definitely not true that USB-3 "is capable of (much) lower latencies" than USB-2 for audio delivery. And in the usb modes used by audio interfaces, there are protocol considerations that contribute to the practical latency lower bound, such as the framing of data in URBs and scheduling them on the millisecond rather than sending data as soon as it is available during each polling period.The Behringer X32 instantly became a milestone among mid-priced digital mixing consoles when it first appeared, and it has lost none of its appeal since then.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |