similar to: Suggestion: The ability to limit the number of ICY connections

On Fri, 21 May 2004, Jack Moffitt wrote: > Maybe this is a stupid question, but why don't you just use Oddsock's > plugins which support the better protocol? Not a stupid question. There's three considerations. 1. This project has around fifty broadcasters. It has been running for 3.5 years, and whilst some have moved to using plugins like SAM which (presumably) does

At 07:12 PM 5/21/2004, you wrote: >2. This is a project where all the broadcasters, myself included, are >blind. Last time I tried it, and admittedly it was a long time ago, >Oddcast presented some issues with regard to screen reader accessibility. >I should really run it up the stick again to see what it's like nowadays. I released a blind-friendly version of oddcast a long

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 >

Normally icy-metaint is a line in the http header, but some stream only sends it in the response data is self. Where can I find such a stream? Is that compliant to the standard? Implementation that also parses the response data http://stackoverflow.com/questions/8621353/textview-not-updating-shoutcast-stream-metadata-in-android-2-2 Thank Stig -- Best Regards / Mvh Stig Christensen stig

Hello, I'm brand new to this streaming stuff so please bear with me. I have installed and am running icecast 1.3.10, ices latest version: 0.0.1 beta5 and/or shout 0.8.0. No major problems with the exception of the clients like to drop off [and I see this problem posted before but didn't see any fix for it]. Btw... this is on Linux Slackware 7 operating system. My question is

Hello, I have a request for an additional header. This header is needed to inform the client of the burst it is going to receive. Why ? This header could be very usefull for the streaming-client to have an idea of it's delay, and (much more important) to be able to do early-on streaming. The question is not on how to implement this in code (probably send the header in the

Good morning, On Sat, 2018-12-01 at 16:20 -0800, Greg Ogonowski wrote: > UTF-8 is now the universal standard. (ICY context:) Expect if you are in Asia. Or in central Europe. Or maybe in Africa. I'm not aware of servers on the poles, maybe they use..., ... > It supports ALL character sets. As long as "ALL" is defined as what English people need plus all emoji in all skin

On Wed, Jun 25, 2003 at 04:27:58PM +1000, Michael Smith wrote: > > > > notice that, with exception of the last, they're all ice-* not icy-*... > > prehaps this is incompatable with the way most players operate to get > > stream data? Is this a typo? > > No. This is deliberate. There could be a bug in the code that takes these > headers and puts bits of them

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

The short answer, as Geoff says, is to use ices 0.x from CVS with libshout 2. The good news is CVS ices 0 has a number of bug fixes. libshout2 may be found at anoncvs@cvs.xiph.org:/usr/local/cvsroot libshout ices is at anoncvs@cvs.xiph.org:/cvs/ice ices Note the different paths above! Now, a little more detail: On Sunday, 16 March 2003 at 02:41, jeremy@squat.net wrote: > ices0 -b 24 -h

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 >

Greetings Icecast masters! Does anyone know what the supported character encoding(s) are for strings in ICY metadata? The closest I?ve been able to get via a Google search is this thread: http://forums.winamp.com/showthread.php?t=208096&highlight=handle+unicode+characters%3F <http://forums.winamp.com/showthread.php?t=208096&highlight=handle+unicode+characters?> Which would

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

At 05:31 PM 6/25/2003 +1000, you wrote: > > I'm not concerned with how players see anything right now, tho that is a > > concern I guess. I'm concerned with getting the vitals - the stream > > name, genre, and description, to be relayed to a YP server when Icecast2 > > is relaying a Shoutcast stream. Currently it does not, this is missing > > functionality

> That much I figured out. I'm trying to use winamp to set up a remote > broadcast. Where do I tell (either icecast or winamp) what the mount > point is. When I use the shoutcast source it appears to create a mount > moint cammed ice_0. I have no idea where that comes from. If you use Nullsoft's tools, you cannot specify mount points. That's because the Nullsoft team

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

On Tue 26. June 2001 15:55, you wrote: > On Tuesday, 26 June 2001 at 13:20, Darrell Berry wrote: > > hi > > > > don't know if i'm missing something, but how do i name mount points > > using ices? > > > > i assumed this was specified in the > > > > <ices:Stream> > > <ices:Name></ices:Name> > >

I have problem connecting several sources when they are icy sources... If i use liveice i have no problem! But if i use winamp sometimes it doesn't accept encoders I set up 10 sources I have 10mbit connection (it's a private lan) I already tried modifing throttle to 100! Any Idea....?Don't wanna go back to shoutcast!!! Please --- >8 ---- List archives:

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

According to what I've read on this mailing list, it should be possible to stream MP3 data to icecast2 using ices-0.2.3, which I assume also should be the case for any other streaming client based on libshout1. So I decided to test this out to see if we really could dispense with icecast1 altogether on the server I help administer. My results were not promising, to say the least. I wiped out