<html><head></head><body>pro b) - A discovery factory can spawn avb listener jack clients for each talker on the network <div class="gmail_quote">Am 11. April 2019 22:44:06 MESZ schrieb Christoph Kuhr <christoph.kuhr@web.de>:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> 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</blockquote></div> -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet.</body></html>