similar to: compiler warning

On Friday 21 November 2003 13:17, Dave St John wrote: > Anyone know of the correct header that are sent to the icecast2 server? > > example the ones sent to a shoutcast server are > icy-name:whatever station > icy-genre:Industrial, EBM, Electronic > icy-pub:1 > icy-br:256 > icy-url:http://www.mediacast1.com > icy-reset:1 > > just need to know what the equivelant is

the problem is probably that nsvcap most likely tries to attach using the "shoutcast source" protocol, which is some strange variation of HTTP (but definitely not HTTP).... It's strange-ness and non-HTTP-ness is the reason why icecast doesn't support connecting the Shoutcast DSP to it. So I don't think any magical combination of headers will get live NSV

Ok i got a few questions when a client connects (winamp) what are the incoming headers icecast looks for to signify what type(ogg or mp3) of stream the client is requesting? example (for shoutcast winamp sends icy-metadata:1) shoutcast server then recognizes its a player capable of streaming media so it sends the icy-metaint:8192 to winamp, along with a slew of other icy headers. o here is my

Here is some code i wrote to send a mp3 file to a shoutcast server, with a little modification im sure you could change it and use it to connect to icecast2 and write various things etc... not sure but here it is ------------------------------------------------------ <?php $port = '8000'; $ip = '127.0.0.1'; $fileplay = './whatever.mp3'; $password = 'changme'

Hello Everyone! My name is John Silvers PD/CE of Pirate Radio 100.3FM (KQLZ Los Angeles) I wanted to introduce myself to everyone. We are switching over from our 2072 Shoutcast streams to Ogg with the help from Dave at Mediacast1. It seems mp3PRO is just not catching on but the I think the ogg sounds way better then mp3PRO and not just one player can hear the difference plus no plug-in to push

relaying a shoutcast stream via icecast2 is pretty much unlistenable -- it constantly stutters. for example, shoutcast relay -- http://205.188.234.1:8030/listen.pls icecast2 relay -- http://liveradio.indymedia.org:8001/sf-hifi.mp3.m3u --mark --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a

> What I did notice is that the date field is not first, even though it's > date ordered. I personally didn't like that, so I just moved the date > field. opinions ? Please don't change the ordering of the fields. It's quite deliberately ordered for compatibility with the Apache Common Log Format. (hmm... or is it the Combined Log Format? I forget...) Mike --- >8

Under windows all you need to do is edit your php.ini file under C:\WINDOWS\ (xp) or C:\WINNT (2000) Look for the the following lines ;;;;;;;;;;;;;;;;;;;;;; ; Dynamic Extensions ; ;;;;;;;;;;;;;;;;;;;;;; then find ;extension=php_shmop.dll extension=php_sockets.dll ;extension=php_sybase_ct.dll ;extension=php_tokenizer.dll make sure sockets is uncommented you will also need to set the path you

this is what i have so far that works, well sorda ------------------------ Content-type:audio/mpeg ice-mount:/crap ice-name:[L A T E X - T V] - LIVE!! ice-genre:Industrial, EBM, Electronic ice-public:0 ice-bitrate:280 ice-url:http://www.latexradio.com ice-description:boooo ice-audio-info:bitrate = 280, 152kbps video, 128kbps audio <p>content type works cant figure out the mount or how to

yes this is darkice. perhaps we could work in 'icy-public' support...? --mark On Tuesday, Jul 8, 2003, at 19:58 US/Pacific, Arc wrote: > On Tue, Jul 08, 2003 at 03:40:42PM -0500, oddsock wrote: >> what source client is generating that ? > > I believe they run darkice, Mark Burdett would have to supply more > specific details as this is a relay of their lofi-mp3

Hi, I would like to try to switch from CentOS 3.4 => CentOS 4 beta. I hava a couple of questions: -is possible to upadte/upgrade my test box from 3.4 => 4 and what are the yum.conf settings/requirements? -is it easy to update your CentOS 4 beta => CentOS 4 when the stable version comes out? Thanks in advance! -- Kind Regards, Michiel van Es

At 03:58 PM 7/8/2003 -0400, you wrote: >That isnt the only bug. One one of our icecast servers the third >stream, sf-lofi.mp3, is not being announced to YP servers at all. On my >local diagnostics (logs all connections to the liveradio.indymedia.org >YP server) I see that icecast isnt even trying to add it. The other YP >servers are not showing this stream either. It doesnt

http://forums.winamp.com/showthread.php?s=&threadid=172236 its like they think there the only webcasting solution out there, does xiph have anyone promoting the directory for icecast.org? <p>Regards Dave St John Mediacast1 Administrator <p>--- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list,

On 08/03/2016 06:13 PM, Chris Adams wrote: > Once upon a time, Alice Wonder <alice at domblogger.net> said: >> Something in the curl build will always link the binary against >> OpenSSL if the openssl-lib package is present, and will always link >> the library against OpenSSL if any TLS option is enabled in the >> configure. > > No, it doesn't. You can

On Wed, Jun 25, 2003 at 11:34:07AM +1000, Michael Smith wrote: > > > 2) Should relay icy/x-audiocast stream metadata when connecting to > > icecast1/shoutcast/etc so that this information is available to YP > > Eh? It does. I even tested that with someone's shoutcast stream. It works. > Just add >

Scott, > Thats what i do.. just relay. Exactly how are you doing it, and what software are you using (shoutcast version / icecast version / what streaming software are you using)? I'm running icecast 1.3.10, shoutcast 1.8.0, and irpd 0.16 to stream. When I try to relay from shoutcast to my main icecast server, I get the following: <03/15/01@22:38:06> [main] dns thread starting

On Sun, 7 Mar 2004, oddsock wrote: > neat, how ironic is it that you can stream mp3pro with the Shoutcast DNAS, > but their YP will not let you list if you do so...talk about your mixed > messages... I think what they're trying to do here is not only block non-SCDNAS servers, but also as many non-Shoutcast sources as they can. Think about it - if you're streaming MP3Pro without

Hi, <p>I moved this to icecast@, since none of these are icecast development related questions and issues. Macsym wrote: > I didn't know so many people in the Icecast-Dev list were running Linux PPC! Oh well, I'm neither a developer nor running Linux PPC. ;) > Anyway, I understand that you guys don't have the time to help me with that > because you wouldn't be

On Wed, Jun 25, 2003 at 03:33:25PM +1000, Michael Smith wrote: > > Is the metadata relayed to connecting clients. i.e. take a client that > supports shoutcast-style metadata, like winamp (and probably most others). > Connect as a listener to the relay. Do you get metadata? You should. If you > don't, the metadata relaying could have been broken (I think this is >

Scott, > If you go look at the result codes for errors, it says this for #3: Where are these codes, in the source or somewhere on shoutcast's website? > once you fix this.. You'll get error #404: > > 404: This typically means you're running software that isn't a > SHOUTcast > DNAS server. The only supported software for listings in the > SHOUTcast