hi everyone,

JFI, I gave the CuBox ( http://www.solid-run.com/products/cubox ) a try 
with Liquidsoap. It features an ARM v7 Sheeva @ 800Mhz, which is quite 
close to what the Raspberry Pi offers, a bit beefed up though.

After having bricked the box several times I finally managed to use a 
bare armel port of Debian along with the Liquidsoap package maintained 
by Romain (dllliquidsoap.so had to be separately compiled though)

The poor little CPU cannot handle a single dynamically compressed (using 
the compress() operator) 128kpbs MP3 stream, that's really a shame. I 
doubt the armhf port of lame will do much better, I may be wrong though.

According to my tests, you need at least an Atom N270 or a 1.2Ghz Via 
Nano to get such a stream running seamlessly. I use a couple of N330 in 
production, each processor can easily handle two 128kbps MP3 streams 
(one per core, between 3% and 70% of CPU usage depending on the work to 
perform on the track) with on-the-fly transcoding, normalization, and 
companding, and yet there's still a lot of CPU headroom: the 2 
hyperthreading threads remain available for everything else.

HTH

-- 
best regards,

okay_awright
<okay_awright AT ddcr DOT biz>
[PGP key on request]

On 26/06/2012 15:27, Dave Pascoe wrote:
> I haven't tested Liquidsoap on the Raspberry Pi yet, but I can confirm that
> running two instances of Darkice streaming 16kb/s MP3 streams is not an
> issue.  A third *might* be possible but it will be close CPU-wise.
>
> Dave
>


------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to