Icecast - Aug 2004 - Client Woes

> Jack's instructions on making/using .m3u files will make the stream
play in
> Winamp. To have it play in RealPlayer, use an identical file - but with a
> .ram extension.
Making it a .ram file will ONLY allow it to be played in RealPlayer.
RealPlayer will also play m3u's.  The basic choice is:

Do I let the user pick a player, or do I choose it for them?

jack.

--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

Uh, looks like I didn't read closely enough to recognize the depth of the
problem :-).

Jack's instructions on making/using .m3u files will make the stream play in
Winamp. To have it play in RealPlayer, use an identical file - but with a
.ram extension.

-bg
> > The URL looks like this:  http://www.RainbowRadio.com:8000/club.mp3
> >
> > My goal is to instruct users as how Winamp may be brought up to play
> > the stream automatically.  I am migrating from Real Audio to
> > Icecast, but I cannot complete the migration with users having so much
> > trouble with the streams.
>
> So what did you expect to happen just having people click on an MP3?
>
> Here's how browsers work.
>
> Click.
>
> Oh, a file.  I'll download it.
> [ After download ]
> What type a file is it. Oh mp3!  I'll hand that to application X.
>
> The way to prevetn this download, or rather to work around it, is to use
> a small intermediate playlist file.  In order to get maximum client
> support, m3u files are best.  Just make an m3u file called  stream.m3u
> and in it put:
>
> http://www.RainbowRadio.com:8000/club.mp3
>
> Then point your users to that file.  Which will quickly download, get
> sent to the player registered for M3u's, and then the player will
> connect and start to stream that file.
>
> jack.
>
> --- >8 ----
> List archives:  http://www.xiph.org/archives/
> icecast project homepage: http://www.icecast.org/
> To unsubscribe from this list, send a message to
'icecast-request@xiph.org'
> containing only the word 'unsubscribe' in the body.  No subject is
needed.
> Unsubscribe messages sent to the list will be ignored/filtered.
>
--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.

What is usually done is that you provide *both*.  That's the only way to
truly allow a choice.

I certainly would never suggest using a .ram file only. But RealPlayer
doesn't handle .m3u or .pls files properly (though it *will* claim that
association & refuse to give it up) - so if you want to make your stream as
accessable as possible, you need 2 links.

-bg
> Making it a .ram file will ONLY allow it to be played in RealPlayer.
> RealPlayer will also play m3u's.  The basic choice is:
>
> Do I let the user pick a player, or do I choose it for them?
>
> jack.
>
--- >8 ----
List archives:  http://www.xiph.org/archives/
icecast project homepage: http://www.icecast.org/
To unsubscribe from this list, send a message to
'icecast-request@xiph.org'
containing only the word 'unsubscribe' in the body.  No subject is
needed.
Unsubscribe messages sent to the list will be ignored/filtered.