08-21-2023, 11:32 AM
On the surface it's similar to what is used currently in moOde which is the TRX Realtime audio over IP toolset written by Mark Hills plus some enhancements I added to support integration into moOde. The repo is maintained by @bitlab https://github.com/bitkeeper/trx and the enhancements are in release 0.6.
The main differences between TRX and Bark are below:
TRX does not use clock sync to maintain to-the-ear sound synchronization but rather relies on low network latency (few milliseconds) and packet drop recovery in the Opus CODEC.
Bark includes clock synchronization which is needed to maintain to-the-ear sound synchronization on higher latency (> few milliseconds), inconsistent latency networks or when sender/receiver throughput is inconsistent.
I might ping the dev to see about ALSA support and whether native sample rates can be supported.
The main differences between TRX and Bark are below:
Code:
--------------------TRX------------------------------Bark-----------------------------
Audio format Compressed (Opus) 16/48K PCM Uncompressed 16/48K PCM
Clock sync No Yes
ALSA output Yes No (only Pipewire and Pulseaudio)TRX does not use clock sync to maintain to-the-ear sound synchronization but rather relies on low network latency (few milliseconds) and packet drop recovery in the Opus CODEC.
Bark includes clock synchronization which is needed to maintain to-the-ear sound synchronization on higher latency (> few milliseconds), inconsistent latency networks or when sender/receiver throughput is inconsistent.
I might ping the dev to see about ALSA support and whether native sample rates can be supported.
