Paul,
I'm guessing this is probably a bug. But could you
either: a) attach a sample file with this problem;
or b) tell me exactly how you created this file (player
version, what steps, etc.) so I can create one?
I'll confirm the problem. Depending on how it turns
out, we may have to fix the problem and rev some
sort of version number, or we may just document that
the year field is an exception to the big-endian rule.
Eric
> -----Original Message-----
> From: helix-client-dev-bounces helixcommunity.org
> [mailto:helix-client-dev-bounceshelixcommunity.org] On
> Behalf Of Paul Cifarelli
> Sent: Saturday, December 31, 2005 11:39 AM
> To: player-devhelixcommunity.org; helix-client-devhelixcommunity.org
> Subject: [Helix-client-dev] RP 10/Win, RMFF Metadata
Section
> - little endian?
>
> Hi guys,
>
> I've been coding up support in amaroK for reading
realmedia
> file format, and
> I've come across what may be an inconsistency in the
byte
> ordering in the
> Metadata Section.
>
> In all other sections, the byte ordering is big-endian.
> However, the "Year"
> track subproperty is stored as little-endian in the
files I
> created using
> RealPlayer 10 for Windows. Is it always the case, or
is this
> a bug in
> RP10/Win?
>
> thanks in advance,
>
> Paul
>
>
> _______________________________________________
> Helix-client-dev mailing list
> Helix-client-devhelixcommunity.org
> http://lists.helixcommunity.org/mailman/listinf
o/helix-client-dev
>
_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev
|