*** the following config:
<input>
<module>playlist</module>
<param name="type">script</param>
<param
name="file">/radio/getnextsongpath</param>
</input>
gets me:
Could not find a valid playlist file.
Ices Exiting...
*** the following header of the config file:
<?xml version="1.0"?>
<ices>
gets me:
XML Parser: Document of invalid type, no ices namespace found
note that this is the header of your distirbuted config files from
ices-2.0.0/conf/
*** the following header(from an unoffical ices help page):
<?xml version="1.0"?>
<ic:root xmlns:ic="http://url.des.namespaces">
<ices>
gets me:
/etc/ices.xml:94: parser error : Premature end of data in tag root line 2
^
XML Parser: Error while parsing /etc/ices.xml
*** also this header...
<ices:ices xmlns:ices="http://url.des.namespaces">
*** Even with ices -v
I do not see which config file is opened so I even do not know
whether I'm editing the right file
strace shows that the right file is opened
*** with google I found a completly different config file format
which should be at:
http://svn.xiph.org/icecast/branches/ices0/ices-libshout_2/doc/icesmanual.html
the request for that file never ends......
but there is google's cache! phew!
with this *OTHER* format containig the header:
<?xml version="1.0"?>
<ices:Configuration
xmlns:ices="http://www.icecast.org/projects/ices">
<ices:Playlist>
the error is gone
*** back to using playlist script:
<ices:Playlist>
<ices:Type>script</ices:Type>
<ices:Module>/radio/getnextsongpath</ices:Module>
produces:
DEBUG: Initializing playlist handler...
DEBUG: Initializing builting playlist handler...
Could not find a valid playlist file.
Ices Exiting...
and this:
<ices:Playlist>
<ices:Type>python</ices:Type>
<ices:Module>myown</ices:Module>
produces:
Initialization of playlist handler failed. [This binary has no support for
embedded python]
Ices Exiting...
:-(
ices 2.0.0 = ices alpha release,
with misleading documentation+example config,
and missing core feature
--
klaus thorn klaus@trillke.net
On Fri, 7 Jan 2005 01:08:15 +0100, klaus thorn <klaus@trillke.net> wrote:> *** the following config: > <input> > <module>playlist</module> > <param name="type">script</param> > <param name="file">/radio/getnextsongpath</param> > </input> > gets me: > > Could not find a valid playlist file. > Ices Exiting...That's a very, very unusual place to put your playlist. Are you sure it's really there?> > *** the following header of the config file: > > <?xml version="1.0"?> > <ices> > > gets me: > > XML Parser: Document of invalid type, no ices namespace found > > note that this is the header of your distirbuted config files from ices-2.0.0/conf/Yeah, but are you actually USING ices-2.0.0? It looks like you're using ices 0.x, which is a completely different application.> > *** back to using playlist script: > > <ices:Playlist> > <ices:Type>script</ices:Type> > <ices:Module>/radio/getnextsongpath</ices:Module>So you ARE using ices 0.x> > produces: > > DEBUG: Initializing playlist handler... > DEBUG: Initializing builting playlist handler... > Could not find a valid playlist file.Does ices 0.x have script playlists? It looks like it's trying to find a playlist file...> > ices 2.0.0 = ices alpha release, > with misleading documentation+example config, > and missing core featureYou're not using ices2 at all. Mike
Michael Smith wrote:> Does ices 0.x have script playlists? It looks like it's trying to find > a playlist file...It does, but it's not a simple script like those supported by Ices 2.x - they need to be either perl or python and need to have a range of functions defined which Ices calls. To the original poster - Maybe start at the beginning and tell us exactly what you're trying to do? Geoff. -- Geoff Shang <geoff@hitsandpieces.net> Phone: +61-418-96-5590 MSN: geoff@acbradio.org Make sure your E-mail can be read by everyone! http://www.betips.net/etc/evilmail.html Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
klaus thorn wrote:> <ices:Playlist> > <ices:Type>python</ices:Type> > <ices:Module>myown</ices:Module> > > produces: > > Initialization of playlist handler failed. [This binary has no support for embedded python] > Ices Exiting...The reason for this one at least is that Ices was compiled without python support. And that's definitely Ices 0.x. Geoff. -- Geoff Shang <geoff@hitsandpieces.net> Phone: +61-418-96-5590 MSN: geoff@acbradio.org Make sure your E-mail can be read by everyone! http://www.betips.net/etc/evilmail.html Please avoid sending me Word or PowerPoint attachments. See http://www.fsf.org/philosophy/no-word-attachments.html
On Fri, Jan 07, 2005 at 02:27:06PM +1100, Michael Smith wrote:> On Fri, 7 Jan 2005 01:08:15 +0100, klaus thorn <klaus@trillke.net> wrote: > > *** the following config: > > <input> > > <module>playlist</module> > > <param name="type">script</param> > > <param name="file">/radio/getnextsongpath</param> > > </input> > > gets me: > > > > Could not find a valid playlist file. > > Ices Exiting... > > That's a very, very unusual place to put your playlist. Are you sure > it's really there?it's not a playlist. its a script that outputs one songpath when called. This is what the documentations clains is possible. And, yes it is there. The script is part of a quite big radio application under /radio> > > > *** the following header of the config file: > > > > <?xml version="1.0"?> > > <ices> > > > > gets me: > > > > XML Parser: Document of invalid type, no ices namespace found > > > > note that this is the header of your distirbuted config files from ices-2.0.0/conf/ > > Yeah, but are you actually USING ices-2.0.0? It looks like you're > using ices 0.x, which is a completely different application.ah, my PATH variable was leading to an old ices, you are right. thank you. the other ices (2.0.0) works ;-) -- klaus thorn klaus@trillke.net