similar to: Ices2; Metadata and special chars

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:

I have the same problem with status.xsl. Special characters such as “é” are truncated. Is there any solution? Cheers, MAX -----Original Message----- From: owner-icecast@xiph.org [mailto:owner-icecast@xiph.org] On Behalf Of Ross Levis Sent: Wednesday, March 03, 2004 4:58 AM To: icecast@xiph.org Subject: Re: [icecast] Ices2; Metadata and special chars I reported this several months

On Wednesday 03 March 2004 14:18, Thomas Weber wrote: > 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 >

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. I tried the following format: \n artist=foo\n title=bar\n (\n is, of course, a normal

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"

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

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>

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

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,

I''m getting the following bug when I try to run rake db:migrate in Rails 3 beta 4: $ rake db:migrate --trace (in C:/Users/Adam/Documents/Aptana Workspace/QuestionBank) default formats are encoded in ISO-8859-1 ** Invoke db:migrate (first_time) ** Invoke environment (first_time) ** Execute environment ** Execute db:migrate == CreateUsers: migrating

Hi folks! I upgraded a red hat linux fileserver (kernel version 2.4.18-14) from samba 2.x to samba 3.02. After the upgrade, the special chars in windows filenames (German Umlaute) were no more visible to clients but either substituted with a little black rectangle or completely suppressed - depending on the client operating system (W2000/W98). Within the archived list I found a hint that the

Dear all, I use Sweave to create my reports. Unfortunately my script crashes whenever I my R code contains special characters like umlauts. Is there a way to to escape special characters in Sweave... This is the line that crashes Sweave: gl_bybranch = ddply(new_wans,.(period,Branchen), function(X) data.frame(Gesch?ftslage=mean(X$sentiment))) Unfortunately I can't just rename it, because I

Hi, I experienced some problems with authenticate. seems like the mail clients like thunderbird send their base64 string in ISO- encoding, which doesnt work on my dovecot setup if there are some Umlauts I am not able to login as "?mer" for example If I authenticate from telnet with an base64 encoded utf-8 string like 'echo -en "\0?mer\0Start12" |base64'

it is possible to play the same song after it finished in ices2? i'm geting this error, even if i rename the song: log: EROR playlist-builtin/playlist_read Cannot play same file twice in a row, skipping [2007-06-16 03:47:23] WARN playlist-builtin/playlist_read Skipping "/var/www/radio/playlist/espaco_vital_080607_conv2.ogg" as the serial number is the same as previous

hi everyone, congratulations on the release of icecast 2.1.0 I presume this is the right place to post about iceS. please correct if wrong. I have a two instance setup, and have been finding that after a network error occurs, the instance does not reconnect. The source server is behind a linux NAT box. I have simulated the problem by using iptables REJECT with tcp-reset and here is the

Hello. I am running an up-to-date cvs snapshot (10 Aug 03) of ices2, and I cannot get the Metadata update from file to work (indeed this has always been true on all previous versions of ices2 that I have used). If I send the ices process a SIGUSR1, then the error log shows that the update is taking place, but immediately followed by a read error from the OSS input module, causing ices to die. I

Hi, On 01/25/2014 11:47 PM, v_2e at ukr.net wrote: > I have tested the newly released IceCast 2.4beta4 and again found a > noticeable memory leak in it. Can you please run Icecast under Valgrind? I'm personally using: valgrind -v --time-stamp=yes --leak-check=full --show-reachable=yes icecast -c /etc/icecast2/icecast.xml With our experiments so far we were not able to see such

Hello. On a PC Pentium III I had a audio server working properly with Icecast2 and Ices2, running on Debian 5.0 (Lenny). Now I've upgraded to Debian 6.0 (Squeeze) and after a few seconds of running everything correctly, successive cuts begin to occur in the audio. For Debian 6.0 I have used the same settings for Icecast2 and Ices2 I used in Debian 5.0. Increasing "burst" only managed

I must be doing something really stupid. I've read the docs for icecast2 and ices2. Icecast2 is running fine; I can get stats.xml and see that it is running. When I run ices2, I get the following error in ices.log: ... [2005-12-07 05:37:51] INFO playlist-basic/playlist_basic_get_next_filename Loading playlist from file "/home/john/playlist.txt" [2005-12-07 05:37:51] WARN