Re: [Jack-Devel] jackd on low memory embedded systems

Thanks for the question.

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.
Jack also uses LPC based compression over the network - which is 
lossless. That is normally a minimum of 2 times compression.

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 ?

Matt

On 20/07/15 06:34, Harry van Haaren wrote:
> On Sun, Jul 19, 2015 at 2:40 PM, Matt Flax <[hidden] 
> <mailto:[hidden]>> wrote:
>
>     I can run jackd1 on this embedded system with very limited resources.
>
>
> 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.
>
> Cheers, -Harry
>
> -- 
>
> http://www.openavproductions.com

1437351384.31688_0.ltw:2, <55AC3DCD.40806 at flatmax dot org>