Another small problem: with the newest Liquidsoap compiled today from the
git repo, I cannot play the following AAC+ stream:
When I look into the logs, I see:
2013/01/31 00:08:04 [decoder:3] Method "AAC" accepted "audio/aacp".
> 2013/01/31 00:08:04 [http:3] Decoding...
> 2013/01/31 00:08:04 [http:2] Feeding stopped: Faad error: Bitstream value
> not allowed by specification
> 2013/01/31 00:08:06 [cross_5292:3] No next track ready yet.
> 2013/01/31 00:08:06 [lang:3] URL now
> http://3043.live.streamtheworld.com/SAM04AAC89_SC (change: false)
> 2013/01/31 00:08:06 [lang:3] New track inside HTTP stream
> 2013/01/31 00:08:06 [lang:3] status: polling
> 2013/01/31 00:08:06 [lang:3] need to cross: false
> 2013/01/31 00:08:06 [lang:3] remaining inf sec before, 0. sec after
Liquidsoap was compiled with libfaad enabled. The version of libfaad on my
system is 2.7 which appears to be the latest version released:
Running this stream with mplayer works fine (however ffmpeg + faac are
I'm a little confused since I can't find any official documentation as to
whether libfaad actually supports AAC+ and in the PACKAGES file, AAC+ is
only mentioned for encoding - however, I could have sworn this stream used
to work in Liquidsoap and either it never did and I'm going crazy or the
stream was recently switched from AAC to AAC+.
Has Liquidsoap ever supported decoding AAC+ with libfaad, or do I need
another library enabled.
Open source radio in the cloud. Get yours now! ---> http://airtime.pro
Software Developer, Sourcefabric
720 Bathurst St. Suite 203
M5S 2R4, Toronto, ON, Canada
+1 (416) 892-8420 (Cell)
Get latest updates about Open Source Projects, Conferences and News.