hiya. i'm using ices 0.2.2 with icecast 1.3.10 and otto 1.0
(a web/db playlist mgmt tool). overall, i'm very pleased
with the setup, but i'm having a few problems.
1) whenever otto plays a track (by exec'ing ices), that same
track keeps playing over and over. i have to direct otto to
kill the track (and the ices process) in order to get it to
play the next track.
i notice this comment in the source for ottojockeyd (the
program that actually execs ices):
# note: you may need to hack the ices source code so that it will
# exit after playing one song (instead of looping forever)
is there any real way to tell make ices play a single track
from its playlist and then exit? or do i truly have to
modify the source? if so, what's the right place to make the
change?
2) at any given time, there are two identical ices
processes:
root 29336 0.0 1.6 3096 1012 pts/2 S< 20:11
0:00 /usr/bin/ices -s -S builtin -h localhost -p 8001 -P
xxxxxx -n Nirvana Jukebox -u http://10.0.0.1/ -m / -F
/tmp/playlist.1
root 29339 0.0 1.6 3096 1012 pts/2 S< 20:11
0:00 /usr/bin/ices -s -S builtin -h localhost -p 8001 -P
xxxxxx -n Nirvana Jukebox -u http://10.0.0.1/ -m / -F
/tmp/playlist.1
does ices fork or something? if not, maybe otto is keeping
two alive for some reason. maybe if the ices processes were
exiting after playing a single track re above, i wouldn't
see this.
3) whenever i have the system play tracks encoded at 160,
they sound great. but when one of my few 224 tracks is
played, it's majorly skippy and crap. from my reading of the
icecast and ices manuals, it seems that they will just
stream at the file's bitrate if reencoding is not configured
(i have not). so what could be wrong?
4) what clients support title streaming?
thanks for your help! :)
--- >8 ----
List archives: http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-request@xiph.org'
containing only the word 'unsubscribe' in the body. No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.
On Wednesday, 24 October 2001 at 20:24, brian moseley wrote:> > hiya. i'm using ices 0.2.2 with icecast 1.3.10 and otto 1.0 > (a web/db playlist mgmt tool). overall, i'm very pleased > with the setup, but i'm having a few problems. > > 1) whenever otto plays a track (by exec'ing ices), that same > track keeps playing over and over. i have to direct otto to > kill the track (and the ices process) in order to get it to > play the next track. > > i notice this comment in the source for ottojockeyd (the > program that actually execs ices): > > # note: you may need to hack the ices source code so that it will > # exit after playing one song (instead of looping forever) > > is there any real way to tell make ices play a single track > from its playlist and then exit? or do i truly have to > modify the source? if so, what's the right place to make the > change?You should search the archives for 'otto' to see a good summary of your options here. Running ices to read from a FIFO and having ottojockeyd simply cat each song to that fifo should work fine.> 2) at any given time, there are two identical ices > processes: > > root 29336 0.0 1.6 3096 1012 pts/2 S< 20:11 > 0:00 /usr/bin/ices -s -S builtin -h localhost -p 8001 -P > xxxxxx -n Nirvana Jukebox -u http://10.0.0.1/ -m / -F > /tmp/playlist.1 > root 29339 0.0 1.6 3096 1012 pts/2 S< 20:11 > 0:00 /usr/bin/ices -s -S builtin -h localhost -p 8001 -P > xxxxxx -n Nirvana Jukebox -u http://10.0.0.1/ -m / -F > /tmp/playlist.1 > > does ices fork or something? if not, maybe otto is keeping > two alive for some reason. maybe if the ices processes were > exiting after playing a single track re above, i wouldn't > see this.ices is threaded. Presumably one of those processes is the metadata update thread.> 3) whenever i have the system play tracks encoded at 160, > they sound great. but when one of my few 224 tracks is > played, it's majorly skippy and crap. from my reading of the > icecast and ices manuals, it seems that they will just > stream at the file's bitrate if reencoding is not configured > (i have not). so what could be wrong?icecast 1.3.10 had some problems with bitrates higher than 160. You might want to try 1.3.11, which had a fix specifically for this.> 4) what clients support title streaming?on which platforms? I think just about everything but mpg123 does these days, but xmms does have some bugs in shoutcast-style streaming which may cause it to chew up the stream after a while. I sent in a bug-report and a half-assed patch to bugs.xmms.org about this... -b --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
On Wed, 24 Oct 2001, Brendan Cully wrote:> You should search the archives for 'otto' to see a good > summary of your options here. Running ices to read from > a FIFO and having ottojockeyd simply cat each song to > that fifo should work fine.whoops, sorry. i searched for a few other things, but should have thought of that. duh. i patched stream.c to exit instead of looping. it's an ok workaround. i like the fifo idea tho. i'd come up with a real patch for ices but i'm not a c coder. i can however write a patch for otto, if you make the change to ices :)> ices is threaded. Presumably one of those processes is > the metadata update thread.oh, duh. yesterday was a headhole day for me.> icecast 1.3.10 had some problems with bitrates higher > than 160. You might want to try 1.3.11, which had a fix > specifically for this.good to know. 1.3.10 is bundled with my distro (suse 7.2). i'll upgrade and see what happens.> on which platforms? I think just about everything but > mpg123 does these days, but xmms does have some bugs in > shoutcast-style streaming which may cause it to chew up > the stream after a while. I sent in a bug-report and a > half-assed patch to bugs.xmms.org about this...hmm, i'm using xmms (1.2.4) and xaudiocast streaming. xmms only seems to display the title of the first song in the stream; it never updates. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
I've been through this on the list a while back. Unfortunately what you are asking is not possible, nor are the authors of ices interested in solving your problem :) I'd recommend ices-0.0.1.beta5.tar.gz (as recommended by otto's author) and seeing otto/misc/icecast/ices.readme. I use the recommended setup things run great. brian moseley wrote:> > hiya. i'm using ices 0.2.2 with icecast 1.3.10 and otto 1.0 > (a web/db playlist mgmt tool). overall, i'm very pleased > with the setup, but i'm having a few problems. > > 1) whenever otto plays a track (by exec'ing ices), that same > track keeps playing over and over. i have to direct otto to > kill the track (and the ices process) in order to get it to > play the next track. > > i notice this comment in the source for ottojockeyd (the > program that actually execs ices): > > # note: you may need to hack the ices source code so that it will > # exit after playing one song (instead of looping forever) > > is there any real way to tell make ices play a single track > from its playlist and then exit? or do i truly have to > modify the source? if so, what's the right place to make the > change? >-- ------------------------------------ Robin P. Blanchard IT Program Specialist Georgia Center for Continuing Ed. fon: 706.542.2404 fax: 706.542.6546 email: Robin_Blanchard@gactr.uga.edu ------------------------------------ --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.
On Wednesday, 24 October 2001 at 08:12, Robin P. Blanchard wrote:> I've been through this on the list a while back. Unfortunately what you > are asking is not possible, nor are the authors of ices interested in > solving your problem :) I'd recommend ices-0.0.1.beta5.tar.gz (as > recommended by otto's author) and seeing otto/misc/icecast/ices.readme. > I use the recommended setup things run great.I remember this discussion. I wasted a bunch of time proposing different simple ways to solve otto's problem (like having ices read from a fifo and having otto cat to the fifo) which were a lot nicer than connecting and disconnecting to the icecast server every track (which is bad). I also remember reading over a patch to have ices exit at the end. but between your hostile, demanding email and the demands of real life (like being evacuated from my downtown NYC apartment for a couple of weeks last month), I haven't had either the time or, honestly, the inclination to add this code. -b --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages sent to the list will be ignored/filtered.