similar to: how to modify ices source?

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

i have the same need, via otto Brendan Cully wrote: [snip] > Ices will reload the playlist file if it changes on disk. So if the > file changes every track, everything will be fine. Alternatively you > could write your MP3 to a FIFO, which ices could pipe to your icecast > server. that looks like an interesting alternative, tho i have no clue how to do that, and particularly in the

On Wednesday, 01 August 2001 at 15:12, Robin P. Blanchard wrote: > > > > Ices will reload the playlist file if it changes on disk. So if the > > > file changes every track, everything will be fine. Alternatively you > > > could write your MP3 to a FIFO, which ices could pipe to your icecast > > > server. > > > > that looks like an interesting

On Wednesday, 01 August 2001 at 14:37, Robin P. Blanchard wrote: > you may or may not be acquainted with the program otto; it is > a web-based jukebox solution. it has the ability to play both > locally as well as to an icecast server via ices. however, as > there is not a static playlist, ices needs to to exit after > streaming an individual song. the author of otto had the

> assuming otto can execute an arbitrary shell command whenever the > track plays (I assume it can call whatever mp3 decoder you want), you > can > a) have a script that does something like > echo $1 > /path/to/playlist.txt > Then ices will reload the playlist file (size: one entry) at the end > of the track. > > b) do > mkfifo ices.fifo > echo ices.fifo >

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

On Wednesday, 01 August 2001 at 16:37, Robin P. Blanchard wrote: > > assuming otto can execute an arbitrary shell command whenever the > > track plays (I assume it can call whatever mp3 decoder you want), you > > can > > a) have a script that does something like > > echo $1 > /path/to/playlist.txt > > Then ices will reload the playlist file (size: one entry)

Hi all, I'm currently trying to set up ices2 with icecast2 along with otto, a jukebox interface written in perl. Otto allows the user to kill a song via the web interface, which in turn kills all running instances of ices, rewrites the playlist and launches ices. This has the bad side effect of terminating the client's connection to icecast and leaving a bunch of ices

> > Ices will reload the playlist file if it changes on disk. So if the > > file changes every track, everything will be fine. Alternatively you > > could write your MP3 to a FIFO, which ices could pipe to your icecast > > server. > > that looks like an interesting alternative, tho i have no clue how to do > that, and particularly in the context of otto (which,

> If you want something broken and stupid, the original patch you posted > will probably work ok. Change 'while (1) {' to just '{'. > > Being young and naive, I am still surprised when people are willing to > work twice as hard to do things the wrong way, just because they heard > about that way first. > being old and lazy i'm willing to take the easy

> i'm not trying to argue that what i want to do is "right"; i just > know that it will be easier to have ices not loop, than to rewrite otto. No one asked you to rewrite otto. But maybe getting the maintainer to do it correctly would be nice. This isn't our bug to fix :) jack. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage:

Just for the sake of clarity, I think he ment to say "You might (write) the maintainers of otto mp3." Aye Jack? :) Scott On Tue, 31 Jul 2001, Jack Moffitt wrote: > Since I'm not familiar with that program, I have no idea what could be > wrong. You might the maintainers of otto mp3. > > jack. > > > ok from the beginning .. > > the "otto

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

ok from the beginning .. the "otto mp3" is a software piece that can take a lot of mp3s , put them in a mysql data base and then can 1. play requests that users make on the web interface out to the sound card 2. stream the song to the browser using icecast and ices. now the icecast and ices in "general" configurations works with either a playlist or mp3s if i am not

i have gone through the docs etc ..and i am having REAL hard time ..configuring icecast /ices i think the install is worked fine and i can start the icecast server from console but i am trying to tie "otto mp3" from www.cardhouse.com/otto/ and ices and i cant seem to do it .. can anyone who is pretty familiar with ices and icecast help .. please ? ===== "Frank, it's after

Hi Michael, I'll try, but just from looking at the code inside im_playlist.c it doesn't appear to check the pl->nexttrack variable inside the 'while(1)' loop unless it reaches the eof on the playlist file. Honestly I don't understand the ogg function calls, but just wondering if code has to be added to check this. Brant At Tuesday 06:24 PM 3/19/2002, Michael

At 12:32 PM 3/19/02 -0500, you wrote: >Hi all, > > I'm currently trying to set up ices2 with icecast2 along with otto, a >jukebox interface written in perl. Otto allows the user to kill a song via >the web interface, which in turn kills all running instances of ices, >rewrites the playlist and launches ices. This has the bad side effect of >terminating the client's

I use the Jukebox program 'otto' (which is really good...), but have been experiencing bugs with 'shout' streaming to IceCast. Thus, I decided to use IceS (yesterday). Otto relies on playing one song at a time (i.e. no playlist), and the streaming program (shout/ices/whatever) to exit after playing it just once. Although the otto author has proviceded a patch which stops IceS from

FYI, I've added a crossfader to the ices0 trunk in subversion: http://svn.xiph.org/icecast/trunk/ices0 It requires LAME support (of course). To use it, either pass -C <secs> on the command line, or add a <Crossfade>secs</Crossfade> node to the Playlist section of the config file. Reencoding must also be enabled on your stream. NOTE: the crossfader can't resample, so all

dimanche 24 mars 2002, 21:42:54, Brendan Cully a écrit : >> I also had strange results when commenting this function (in that case >> it is supposed to stream the name of the song, by reading the IdTag). With >> Winamp, I didn't get anything ("unnamned"), with XMMS, I had the proper >> name, with "unnamned" written after it, and it only worked