<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thanks for the question.<br>
<br>
Jack has network audio working well - this is a big bonus, as on
these limited systems you can't do too much audio processing as they
have limited resources and power.<br>
Jack also uses LPC based compression over the network - which is
lossless. That is normally a minimum of 2 times compression.<br>
<br>
Can you tell me how you would approach this ? I understand that by
getting rid of Jack, you would free up a large amount of already
limited memory on these devices ... but how would you do network
audio in a standard fashion ?<br>
<br>
Matt<br>
<br>
<div class="moz-cite-prefix">On 20/07/15 06:34, Harry van Haaren
wrote:<br>
</div>
<blockquote
cite="mid:CAKudYbOD6-2HpRwpB=inoFnYLRYoViYyXUUVCp+3ion8CSTiOw@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Sun, Jul 19, 2015 at 2:40 PM, Matt
Flax <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:flatmax@flatmax.org" target="_blank">flatmax@flatmax.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">I can
run jackd1 on this embedded system with very limited
resources.<br>
</blockquote>
<div><br>
</div>
<div>I'm interested in why you're choosing JACK instead of
"just" using the native (I'll presume ALSA) API for your
audio backend? Not that I'm opposed to JACK - its a
wonderful way of connecting audio applications in
innovative and professional ways - but that doesn't mean
its the best fit for every use case.<br>
</div>
</div>
<br>
</div>
<div class="gmail_extra">Cheers, -Harry<br clear="all">
</div>
<div class="gmail_extra"><br>
-- <br>
<div class="gmail_signature"><br>
<a moz-do-not-send="true"
href="http://www.openavproductions.com" target="_blank">http://www.openavproductions.com</a></div>
</div>
</div>
</blockquote>
<br>
</body>
</html>