similar to: IceS and perl - patch

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

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

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

hello alexander... 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 following suggestion for stream.c per ices-0.0.1.beta5: --- i modified the

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

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

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

i have installed ices with lame suport (thanks to all who helped!), and it happily reencodes bitrates. i have installed otto, and that too is brillient however i can't get otto to call ices in such a way that it will reencode stuff streamed thru otto... when i have had ices working with reencoding, i've configured it via the xml config file rather than with command line switches

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)

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

> 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 >

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Can anyone comment on the "front ends" they are using to manage their ices/icecast streams? I have done some searching and playing with such web-based products as netjuke, and obsequium, and otto audio jukebox, but none fill the requirements exactly, and none appear to interface with ices/icecast the way I would like. Rather than have

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

> 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:

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

Hi, I'm currently migrating from Shoutcast/MP3 to Icecast/OGG/Vorbis using ices. Unfortunately, when initialising the encoder, ices crashes with a bus error. Is there anything I can look into? Details as follows: icecast2-2.1.0,1 ices-2.0.0,1 libshout2-2.0_5,1 libogg-1.1.2_1,3 libvorbis-1.1.0_1,3 (All were installed from the ports tree) On FreeBSD ares.radiozilvervos.com 5.3-RELEASE-p4

Hi, When I open the stats page on the icecast server, I get the basic info, but images and stuff generate 404's, although all the files are there and readable by the user that icecast runs under: This one works: 80.127.65.160 - - [30/Jan/2005:18:15:08 +0000] "GET / HTTP/1.1" 200 44 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; nl-NL; rv:1.8b) Gecko/20050129" 0

Hi, When I open the stats page on the icecast server, I get the basic info, but images and stuff generate 404's, although all the files are there and readable by the user that icecast runs under: This one works: 80.127.65.160 - - [30/Jan/2005:18:15:08 +0000] "GET / HTTP/1.1" 200 44 "-" "Mozilla/5.0 (Windows; U; Windows NT 5.1; nl-NL; rv:1.8b) Gecko/20050129"

Hi, I'm running dovecot (1.1.7) deliver and sieve (1.1.5) on a Fedora 9 platform, using selinux targetet mode. Most of the mail deliveries goes well, but once deliver tried to copy the mail to the /tmp directory, which it seems it not allowed by selinux. I guess that deliver wants to sanitize the mail or something and therefore copies it to /tmp. Before I ask for selinux to allow this, I

I've been using rsync for a long time, and it's very cool. For the first time, last night, I got a message I don't understand. I am using rsync 2.6.4 on Fedora (FC4) Linux to a Fedora (FC3) Linux machine. The command I am using is: rsync -av --delete-excluded --exclude="*~" --exclude="#*#" <source dir> remove_machine:<dest dir> I got the following