tonight i've compiled Liquidsoap from Source with AAC+ but i can't make it work with airtime.
I tried copying binary from liquidsoap/src, and creating also symlink…without results
According with some post on savonet wiki, Liquidsoap was compiled with libaacplus, without fftw support
Where i'm wrong?
From: Daniel James <daniel.james@so...> - 2012-10-09 09:17:05
> tonight i've compiled Liquidsoap from Source with AAC+ but i can't make it work with airtime.
I assume you're using Airtime 2.2.0-RC1 or following the 2.2.x git
branch? Earlier versions don't support any form of AAC.
In the 2.2.x series there is support for AAC decode, but not streaming
in AAC. I don't know of any tests on AAC+, so far.
Are you trying to stream in AAC+, or do you have AAC+ files in the
Airtime library that you want to decode? What do the logs say when you
try to do that?
From: David Baelde <david.baelde@gm...> - 2012-10-09 11:41:09
To know what's supported on the liquidsoap side you can look at the
output of "liquidsoap --list-plugins | less". On my machine, I have an
entry "AAC" in file decoding (corresponding to decoding using libfaad)
and entries "AAC" and "AAC+" in the encoding section, corresponding
respectively to voaacenc and libaacplus libraries.
(You'll also find enable_external_faad_decoder for enabling decoding
using the faad binary.)
This tells you what liquidsoap can do. What airtime will use is a
different question, which Daniel started to address.
From: Daniel James <daniel.james@so...> - 2012-10-09 13:01:37
> I'm using airtime 2.1.3 with custom liquidsoap script...
So the AAC+ is being used for an output stream, then? Please post full
details of the problem.
> Where i can find log? Pypo airtime liquidisoap log doesn't say usefull info
/var/log/airtime/pypo-liquidsoap/ls_script.log is already using the
--verbose option by default. See the ls_path option in the file:
Get latest updates about Open Source Projects, Conferences and News.