Hi,

this thread is a bit old, but I would like to raise the topic again.


Am Fri, 27 Mar 2015 15:47:56 +0100
schrieb Juliane Holzt <[email protected]>:

> I have two machines (VMs) which are basically likewise. Both have Debian
> Testing installed. There are some differences in the installed packages but
> when it comes to liquidsoap, it is the exact same version from the Debian
> packages repository with the exact same libraries (for ogg, vorbis, etc.)

I experienced the same situation. There are two machines with the same set of
packages (Debian Jessie, stable, v1.1.1-7+b1) and the same set of liquidsoap
scripts listening to the same source stream.
One of these liquidsoap instances is decoding ogg streams successfully.
The other one shows the errors reported by the original poster.


> 2015/03/27 02:48:32 [decoder:3] Method "OGG" accepted "application/ogg".
> 2015/03/27 02:48:32 [http_4761:3] Decoding...
> 2015/03/27 02:48:32 [http_4761:2] Feeding stopped: Ogg stream does not
> contain required data

This error is repeated continouosly for  ogg streams (ogg/flac as well as
ogg/vorbis). Thus liquidsoap fails to read from that source.


We had another machine before. That one worked with vorbis input streams but
not with flac. Our third sever was working with flac input flawlessly all the
time.


I tried to play around with the installed modules in order to solve this issue.
I noticed that the above error disappeared after I removed the "opus" plugin
from the plugin directory.
For now this is a good workaround for me.


I tried to dig further around the weird difference between these three servers.
My theory is that the module loading order could influence this behaviour.

Thus I collected it from these hosts:

= A: vorbis and flac works =
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/mad.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/alsa.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/lame.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/cry.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/voaacenc.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/ogg.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/opus.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/vorbis.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/flac.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/flac_ogg.cmxs.

= B: vorbis decoding works, flac fails =
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/mad.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/flac.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/ogg.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/flac_ogg.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/voaacenc.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/opus.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/lame.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/cry.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/vorbis.cmxs.

= C: neither vorbis nor flac works =
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/ogg.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/vorbis.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/flac_ogg.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/opus.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/mad.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/flac.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/voaacenc.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/lame.cmxs.
Loaded plugin file /usr/lib/liquidsoap/1.1.1/plugins/cry.cmxs.

I am tempted to conclude that vorbis and flac_ogg only work if they are loaded
_after_ opus. But this is just wild guessing.
The plugin loading order seems to be determined by the order of files in the
plugin directory (see "ls -U"). Sadly I did not find a way to enforce a
specific order of file entries in a directory - otherwise I could have gathered
more input for proving (or falsifying) the above theory.

Cheers,
Lars

------------------------------------------------------------------------------
_______________________________________________
Savonet-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/savonet-users

Reply via email to