Icecast - Aug 2004 - cannot get icecast and ices totalk...authenticationfailed

> On Wed, 9 Apr 2003, Eric L. Brown wrote:
>
>> WARN playlist-builtin/playlist_read Corrupt or missing data in file
>>
>> When I try to play a basic playlist with 2 files (that are fine, and do
>> exist).
>
> You're not trying to play MP3 files, by any chance?  Ices2 only plays
ogg
> and raw PCM at this time.
ah.
Ok, so is there any way to play my mp3 files (i.e. convert to ogg
on-the-fly or something)?

My goal is to be able to take my collection of CDs (now in 256k mp3
bitstream) and distribute through the house over the wireless network
(har-line network for other stuff).  Just trying to play with some of the
existing technologies before getting the hardware.  The next step is to
have different ices services, serving multiple icecast streams for a
virtual
'multi-room' system.
>
>> I have set the sample and nominal bitrates at 256000, which is
>> also the encoding for the song...
>>
>> Does the bitrate of the song have to be exactly the same as in the
>> ices.xml?  This might present a little problem with playing songs
>> recorded
>> at different bitrates, as well as variable bitrates...so I'm
gurssing
>> this
>> cannot be?
>
> If you just want ices to send out your files as they are, regardless of
> bitrate, you can do that.  Just don't specify any of the re-encoding
> options (see the second example in the sample playlist config).  Sending
> them out as is works fine because vorbis is designed to allow for chained
> streams with different bitrates and samples/channels.  If you do want the
> stream to be at a set bitrate, that's fine.  As far as I understand it,
> all
> files will be re-encoded, and therefore it again won't matter if the
files
> are of varying rates since they will be decoded and re-encoded before
> being
> sent out to icecast.
>
> Geoff.
>
>
> --- >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.

> You might run into trouble if you plan on playing the same stream in
> more than one room coming from a non-wired (audio cables) source.  When
> it's all wired (speaker wire, RCA, digital) there is no (apparent)
> latency.  If you are playing the same stream on two different computers,
> even in your ethernet wired home network, they won't be totally
sync'd
> up.  Latency on a wireless network is even more apparent.  Of course
> 256Kbs is pretty fast and I haven't tried doing it with this speed, so
> the clients may stay "together" for longer, but there is no
garuantee
> they will stay in sync for any amount of time.
> 
> Of course, none of this matters if the rooms are far enough apart and
> you aren't worried about hearing sound carrying over from one set of
> speakers into another area that is playing the same stream.  The echo
> delay can get really annoying and unbearable otherwise.
> 
> Todd
Is there some way to keep two listeners synchronized?  I'm thinking NTP +
some time-code metadata that the server puts into the stream every so
often (sent-at or play-at).  Then the player would buffer the audio
enough that both play more or less in sync.  Anybody played with this
before?

Luke

-- 
  Luke Stodola
  minus273point16c@fastmail.fm

-- 
http://www.fastmail.fm - Accessible with your email software
                          or over the web
--- >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.

On Wed, 9 Apr 2003, Eric L. Brown wrote:
> > You're not trying to play MP3 files, by any chance?  Ices2 only
plays ogg
> > and raw PCM at this time.
>
> ah.
> Ok, so is there any way to play my mp3 files (i.e. convert to ogg
> on-the-fly or something)?
ummm.  Well, not at the moment.  At one stage, Michael did say that this
would be a desirable feature but that he wasn't personally interested in
coding it.  If all your files are 44100Hz stereo, you could possibly do
something with the stdinPCM fascility.  hmmm.

Question though - why do you want to broadcast in ogg if all your files are
in MP3?  I merely ask because you could simply use icecast2 with ices 0.x
(CVS) and stream in MP3, re-encoding to 256KBPS or whatever.

Geoff.

<p>--- >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.

> -----Original Message-----
> From: owner-icecast@xiph.org [mailto:owner-icecast@xiph.org] 
> On Behalf Of Eric L. Brown
> My goal is to be able to take my collection of CDs (now in 256k mp3
> bitstream) and distribute through the house over the wireless 
> network (har-line network for other stuff).  Just trying to 
> play with some of the existing technologies before getting 
> the hardware.  The next step is to have different ices 
> services, serving multiple icecast streams for a virtual 
> 'multi-room' system.
Eric,

You might run into trouble if you plan on playing the same stream in
more than one room coming from a non-wired (audio cables) source.  When
it's all wired (speaker wire, RCA, digital) there is no (apparent)
latency.  If you are playing the same stream on two different computers,
even in your ethernet wired home network, they won't be totally sync'd
up.  Latency on a wireless network is even more apparent.  Of course
256Kbs is pretty fast and I haven't tried doing it with this speed, so
the clients may stay "together" for longer, but there is no garuantee
they will stay in sync for any amount of time.

Of course, none of this matters if the rooms are far enough apart and
you aren't worried about hearing sound carrying over from one set of
speakers into another area that is playing the same stream.  The echo
delay can get really annoying and unbearable otherwise.

Todd

--- >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.