Am 11. April 2019 22:44:06 MESZ schrieb Christoph Kuhr <christoph.kuhr@web.de>:

Hi *,

I wanted to start a discussion of what kind of AVB connectivity makes the most sense for jack.
But please keep in mind what AVB is and isn't.

a) Fully functional Backend
b) Media Clock Backend with AVB jack clients

pro a)
- the AVDECC connection management could be done seamlessly in a jack way
- out of the box avb functionality

con a)
- only one talker/listener, single audio interface
- huge programming effort
- no dynamic audio mapping


pro b)
- multiple talkers/listeners with multiple audio interface using alsa api
- avoiding huge code addition to the backend, thus much easier to maintain
- AVDECC handling per client for dynamic audio mapping

con b)
- cpu load... price for multiple talkers/listeners


I'm excited to hear your opinions!

Best,
Ck