bondagit
commented
6 months ago Checkout the master branch of the aes67-linux-daemon repository and use the instructions at how-to-build-and-setup-the-daemon to compile. This will use the patched version of the Merging driver.
After compilation is successful you can test your configuration using the platform-compatibility-test.
For example, for 5 minutes test with 16 channels at @96Khz:
./run_test.sh S24_3LE 96000 16 5
If this is successful it means you should be able to use such configuration, if not you can try decreasing the number of channels.
If you are interested in the end to end latency you can run the platform-latency-test
Returning to your questions:
Is this at all possible with either Raspberry Pi 4 or 5 and if so, which latencies would be possible?
On similar boards, Dante reports 1.2ms to 1.5ms latency.
Also, I read that the public build of the Merging driver is limited to 8 I/O - is this limitation still valid?
No, it is not. I tested up to 64 channels.
Raspberry Pi 5 adds support of Precision Time Protocol (PTP). Is PTP actually required or would it be beneficial for lower latencies?
No.
Has anyone experience using the Merging driver with the RT-Kernel?
I tried it, but I could not benefit from it.
joerg-wille
Play-AV
(Sorry, did not find any other channel to ask questions?) I would like to use a Raspberry Pi to stream 16 channel @96kHz audio in and out. Is this at all possible with either Raspberry Pi 4 or 5 and if so, which latencies would be possible? Also, I read that the public build of the Merging driver is limited to 8 I/O - is this limitation still valid?
Raspberry Pi 5 adds support of Precision Time Protocol (PTP). Is PTP actually required or would it be beneficial for lower latencies?
Has anyone experience using the Merging driver with the RT-Kernel?