Icecast - Jun 2005 - IceCast 2.2 MP3 stream and Real Player noise

Just checked using RealPlayer Windows 10.5 latest release.
This also glitches.
This is more than likely due to the differences in metadata between
SHOUTcast and Icecast2.
This is exactly the reason I was asking for the exact differences between
the protocols so I can help get these things fixed with the player folks.
Real is not the only player with this problem.
I may be in the AAC/aacPlus camp, but I can and will help with these issues.
I have many ears right about now, and I would really like to see Icecast2
properly supported.

-g.

----- Original Message ----- 
From: "Karl Heyes" <karl@xiph.org>
To: "Fred Black" <fred@batanga.com>
Cc: "icecast" <icecast@xiph.org>
Sent: Friday, June 03, 2005 8:57 AM
Subject: re: [Icecast] IceCast 2.2 MP3 stream and Real Player noise

> On Fri, 2005-06-03 at 16:37, Fred Black wrote:
> > Sorry about that, didn't have port 8000 open to that box from the
outside!
> > Try it again...
>
> I'm connected, and I haven't heard of any playback problems for the
10+
> mins I've been connected for.  The realplayer I've used is 10.0.4,
can
> anyone check the windows version of realplayer?
>
> karl.
>
> >
> > -----Original Message-----
> > From: Karl Heyes [mailto:karl@xiph.org]
> > Sent: Friday, June 03, 2005 11:33 AM
> > To: Fred Black
> > Cc: icecast
> > Subject: Re: [Icecast] IceCast 2.2 MP3 stream and Real Player noise
> >
> > On Fri, 2005-06-03 at 16:21, Fred Black wrote:
> > > Sure:
> > > Make a pls file with this in it:
> > > [playlist]
> > > File1=http://mp31.batanga.com:8000/live
> > > Title1=Test
> > > Length1=-1
> > > NumberOfEntries=1
> > > Version=2
> >
> > cannot connect to that server
> >
> > karl.
> >
> >
> >
> > _______________________________________________
> > Icecast mailing list
> > Icecast@xiph.org
> > http://lists.xiph.org/mailman/listinfo/icecast
> >
>
> _______________________________________________
> Icecast mailing list
> Icecast@xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>

On 6/3/05, Greg <greg@indexcom.com> wrote:
> Just checked using RealPlayer Windows 10.5 latest release.
> This also glitches.
> This is more than likely due to the differences in metadata between
> SHOUTcast and Icecast2.
> This is exactly the reason I was asking for the exact differences between
> the protocols so I can help get these things fixed with the player folks.
> Real is not the only player with this problem.
> I may be in the AAC/aacPlus camp, but I can and will help with these
issues.
> I have many ears right about now, and I would really like to see Icecast2
> properly supported.
We only send mp3 metadata when it's explicitly requested by the
client, and we implement the same protocol as shoutcast. The only
difference I know of is that we have a different default metadata
interval. Since that metadata interval is signalled to the client as a
pretty core part of the protocol, it'd be somewhat astounding if Real
managed to screw it up.

Mike

On Fri, 2005-06-03 at 17:38, Greg wrote:
> Just checked using RealPlayer Windows 10.5 latest release.
> This also glitches.
does that mean earlier version had the problem as well ?
> This is more than likely due to the differences in metadata between
> SHOUTcast and Icecast2.
>From a quick test, it looks like realplayer is requesting metadata and
is getting an interval of 16000.  As mike said, real player may be
having problems with this
> This is exactly the reason I was asking for the exact differences between
> the protocols so I can help get these things fixed with the player folks.
if it is metadata related then the player should be reading the 16000
figure returned from the server and check that many bytes of mp3. If
real is assuming say 8192 (is shoutcast fixed at that?) then that would
cause playback problems. 

by all means try changing the setting in format_mp3.c
#define ICY_METADATA_INTERVAL 16000

The trunk code does allow of overriding it in the XML. In <mount> state

 <mp3-metadata-interval>8192</mp3-metadata-interval>
> Real is not the only player with this problem.
Who else is ?
> I may be in the AAC/aacPlus camp, but I can and will help with these
issues.
> I have many ears right about now, and I would really like to see Icecast2
> properly supported.
The default can be changed to 8192 easily enough but if there is some
parsing issue with real then that would be useful to know.

I suspect that for some reason the real player is ignoring the
icy-metaint header causing the playback problem.


karl.

On 03 Jun 2005 19:33:21 +0100, Karl Heyes <karl@xiph.org>
wrote:
> > I may be in the AAC/aacPlus camp, but I can and will help with these
issues.
> > I have many ears right about now, and I would really like to see
Icecast2
> > properly supported.
> 
> The default can be changed to 8192 easily enough but if there is some
> parsing issue with real then that would be useful to know.
We might need to have a black-list of broken players, where we fall
back to very basic behaviour - using the shoutcast default here, and
probably disabling some other functionality. We don't want to change
global defaults just because one client is broken - that way lies
madness.

> 
> I suspect that for some reason the real player is ignoring the
> icy-metaint header causing the playback problem.
Obviously not ignoring it entirely, but possibly just triggering off
the presence/absence of this header, rather than parsing it.

Mike