similar to: ices2 + stdin + metadata

Ok, so i have to know the PID of ices to send the update-signal. I've added this to my ices.xml: <pidfile>/home/www/bin/ices.pid</pidfile> (directly under the node <ices>) I thought i've seen this somewhere in the manual. However, when i start ices, no pid-file is created :-/ Is this the right way? <p>----- Original Message ----- From: "Karl Heyes"

On Tue, 2004-02-03 at 15:05, Thomas Weber wrote: > Hi, > > does anybody know some info about posting metadata to ices2 via stdin? > My system is based on a PHP-script wich sends PCM-data from the player > (mpg123 or ogg123) over a pipe to ices2. As i understand the documentation, > metadata is sent as normal clear text within the PCM-data when using stdin. no it's

Hi there! I am currently developing a broadcast solution with ices2 (feeded over pipe, stdin). I use a metadata-file and signals to update the streams metadata. The problem is, names of songs and artists are cut off at special chars like & or at a german umlaut. For example: artist=Test title=foo & bar is sent to the clients as "Test - foo ". Do i have to use some kind of

Hi, as I am sending PCM-data over the stdin to ices2, i need a good mp3-player wich runs at the console and is able to output pcm to stdout. So far i tried mpg123 and xaudio, but each had problems. mpg123 wasn't able to play some songs, particularely with varibale bitrate and xaudio played some songs and afaik most mp3pro-shit in double speed, even if it's 44.1khz. Does anyone know a

On Sun, Feb 01, 2004 at 07:20:40PM +0100, root wrote: > I have more info about that problem... > curl | oggdec | ices will never work to my opinion with fallback setup on source > because when transfering listeners to fallback, no ogg headers are sent, so > whatever we do, oggdec will not be happy with the data received... I took a look at this. It is true that oggdec does not

I reported this several months ago. I was using Oddcast to send and Winamp to listen. Winamp showed the title truncated at any extended character. >From memory, status.xsl didn't show the title correctly either. Regards, Ross Levis. ----- Original Message ----- From: "Michael Smith" <msmith@xiph.org> To: <icecast@xiph.org> Sent: Wednesday, March 03, 2004 4:27 PM

I just had contact with an ices-developer about this issue. This is not a bug in ices, it is a documentation-bug. What the documentation not says is, that the metadata should be sent in UTF-8 encoding. Simply change from Ascii to UTF-8 and ALL esoteric characters will be sent, i've just tested this. ----- Original Message ----- From: "MacSym" <macsym69@yahoo.fr> To:

Hello, oggdec is a very simple ogg decoder, and it fails in the following case: a source A has a fallback A' transcoder curl | oggdec | ices2 is transcoding to lower bitrates ogg A fails, all the listeners are transfered to A' oggdec fails because the stream content changed: [2004-01-29 18:44:47] OggDec 1.0.1 [2004-01-29 18:44:47] Warning: hole in data <p><p>[2004-01-29

Hi, i have got a linux debian woody box with icecast2 and ices2 on it. I'm running a 24/7 stream with a huge playlist on my server, but I've got some questions about it: 1. Is it possible, that ices updates Metadata (Artist - Track) to the icecast Server in playlist mode? 2. Is there any possibility of controlling ices2 by a webinterface with functions like nextrack, stop and play,

Hi everybody, I'm in charge of an ices2 setup that's broadcasting a local radio station on the Net, and I'm currently under fire because one of our streams has been down twice in two days, forcing me to restart ices2 on each occasion. Our client is understandably unhappy about this. OUR SETUP: I've got ices2 installed on a local machine, broadcasting to an icecast server across

On Mon, Sep 26, 2005 at 05:30:11PM +0200, Michael Smith wrote: > > Assuming this is correct, the next question that arises is "Is Vorbis > > when used this way truly gapless?" > > Yes, it is. ... and I can confirm this. No gaps were perceivable decoding in ogg123. However, an interesting effect can be had if all the parts have the same serial number. You get a bump

On Sunday, 24 June 2001 at 22:24, Jack Moffitt wrote: > > I decided to make a few shell scripts that can be used to connect to > > icecast, decode/reencode a stream, and then send the result back to icecast. > > > > I guess this can be done with liveice, but this seemed like a simpler > > solution for my needs. I have it triggered by a cgi script that i click

Mike... did you look into this? I posted a waveform from a file generated by ogg123 dumping to a wav (so that audio driver problems were eliminated). It looks to me like ices2 is restarting the vorbis encoder in a non-gapless way when it stops and starts the encoding (to change the stream id and update the metadata). Because I'm doing crossfades from one track to another, this shows up.

>BTW: Will ices support live streaming for vorbis? Or are there other live >streaming sources out there (like MuSE, which I like, but haven't gotten >a chance to really stress-test yet.) ices2 (which is a seperate program, written by different people) does vorbis streaming. It also does live streaming. Feel free to ask me for any features that are missing. Michael --- >8 ----

On Mon, Sep 26, 2005 at 12:41:00PM +0200, Michael Smith wrote: > On 9/23/05, Paul Martin <pm@nowster.zetnet.co.uk> wrote: > > Mike... did you look into this? I posted a waveform from a file > > generated by ogg123 dumping to a wav (so that audio driver problems were > > eliminated). > > > > It looks to me like ices2 is restarting the vorbis encoder in a >

Hello Folks: Every now and then my ogg123 quits while loistening to the stream. It isn't a bandwidth problem because my ogg123 is on a machine which is just a few feet from the server and is in fact on the same machine with ices2 doing the streaming. It happened this morning and I decided to take a look at the log and found some curious messages and thought maybe I'd post them here and

I'm using ices2's metadata facility to update the name of a track in a vorbis stream: <input> <module>alsa</module> <param name="rate">44100</param> <param name="channels">2</param> <param name="device">hw:1,0</param> <param name="metadata">1</param>

Hello, Yesterday evening, I installed icecast kh13 with your latest libshout. We have to wait 1, 2 or three days to see what is happening... Yes, the samplerate 19404 is exactly what I asked ices to do... Just a compromise between bitrate and samplerate to have a better sound quality. Regarding to that, I didn't found the option to set the ouput rate in ices kh47, and also I was wondering how

Perhaps I've done something similar but on Debian and not know if it will work in Windows. I've used vlc to receive any audio from the Internet and ices2 as a source client. It works perfectly fine as a repeater. El s?b, 09-02-2013 a las 22:23 +0100, Xabier Oneca -- xOneca escribi?: > Is the stream a MP3 stream? If so, you can use Icecast as a proxy (see > documentation). >

Hi, currently I'm plaing around with the original shoutcast and use libshout for transmitting to the server. It works mostly perfect, with one little problem: The streams bitrate is not correctly reported to shoutcast. I tried the following: $conn->set_audio_info(SHOUT_AI_BITRATE => 128); $conn is the shout-object. Is this for icecast only? Is there another way to transmit the correct