RP 10/Win, RMFF Metadata Section - little endian?

Just FYI, I have been bouncing this around internally and it
could
well be a RP10 bug. RP10 for windows does not use dtdrive,
it uses
a metadata import plugin which isn't related to dtdrive.

Not much help I know....

--greg.


Eric Hyche wrote:
> 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-bounceshelixcommunity.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
> 

_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev

I put 2 examples at ftp://cifarelli.net/pub.  Sorry I didnt
have any 
non-copyright material, so these should be for debugging 
purposes only!   


They were created with:

RealPlayer (tm) (win32)
Version 10.5
Helix Powered
with Harmony(tm) Technology
Build 6.0.12.1465
Distribution RN30PD

Of course, for the year, I can work around the problem, at
least for the 
next 65000 years, give or take  - but that
doesnt work in general, so
I just wanted to verify that the intention is for all
sections, including the
metadata section, to be big-endian.

Thanks,
Paul

On Wednesday 04 January 2006 13:20, Greg Wright wrote:
> Just FYI, I have been bouncing this around internally
and it could
> well be a RP10 bug. RP10 for windows does not use
dtdrive, it uses
> a metadata import plugin which isn't related to
dtdrive.
>
> Not much help I know....
>
> --greg.
>
> Eric Hyche wrote:
> > 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-bounceshelixcommunity.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

_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev

Thanks, Paul - I'll take a look. 

> -----Original Message-----
> From: Paul Cifarelli [mailto:paulc2optonline.net] 
> Sent: Wednesday, January 04, 2006 11:12 PM
> To: Greg Wright
> Cc: ehychereal.com; player-devhelixcommunity.org; 
> helix-client-devhelixcommunity.org
> Subject: Re: [Player-dev] RE: [Helix-client-dev] RP
10/Win, 
> RMFF Metadata Section - little endian?
> 
> I put 2 examples at ftp://cifarelli.net/pub.  Sorry I
didnt have any 
> non-copyright material, so these should be for
debugging 
> purposes only!   
> 
> 
> They were created with:
> 
> RealPlayer (tm) (win32)
> Version 10.5
> Helix Powered
> with Harmony(tm) Technology
> Build 6.0.12.1465
> Distribution RN30PD
> 
> Of course, for the year, I can work around the problem,
at 
> least for the 
> next 65000 years, give or take  - but that
doesnt work in 
> general, so
> I just wanted to verify that the intention is for all 
> sections, including the
> metadata section, to be big-endian.
> 
> Thanks,
> Paul
> 
> On Wednesday 04 January 2006 13:20, Greg Wright wrote:
> > Just FYI, I have been bouncing this around
internally and it could
> > well be a RP10 bug. RP10 for windows does not use
dtdrive, it uses
> > a metadata import plugin which isn't related to
dtdrive.
> >
> > Not much help I know....
> >
> > --greg.
> >
> > Eric Hyche wrote:
> > > 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-bounceshelixcommunity.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
> 


_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev

Paul,

We verified from these two files and others that the
Year is indeed stored as little endian. The code that
reads and writes this meta-data in .rm files is actually
not yet part of the Helix community code (still part
of RealNetworks-only RealPlayer code), so there is a
different team within RealNetworks responsible for it.
So I can't guarantee when it will be fixed.

So I think in the meantime, you should just assume
that the Year property is an exception and assume
it should be parsed as little-endian. I will try
and update the documentation on the .rm file format
to reflect this.

Eric 

> -----Original Message-----
> From: Paul Cifarelli [mailto:paulc2optonline.net] 
> Sent: Wednesday, January 04, 2006 11:12 PM
> To: Greg Wright
> Cc: ehychereal.com; player-devhelixcommunity.org; 
> helix-client-devhelixcommunity.org
> Subject: Re: [Player-dev] RE: [Helix-client-dev] RP
10/Win, 
> RMFF Metadata Section - little endian?
> 
> I put 2 examples at ftp://cifarelli.net/pub.  Sorry I
didnt have any 
> non-copyright material, so these should be for
debugging 
> purposes only!   
> 
> 
> They were created with:
> 
> RealPlayer (tm) (win32)
> Version 10.5
> Helix Powered
> with Harmony(tm) Technology
> Build 6.0.12.1465
> Distribution RN30PD
> 
> Of course, for the year, I can work around the problem,
at 
> least for the 
> next 65000 years, give or take  - but that
doesnt work in 
> general, so
> I just wanted to verify that the intention is for all 
> sections, including the
> metadata section, to be big-endian.
> 
> Thanks,
> Paul
> 
> On Wednesday 04 January 2006 13:20, Greg Wright wrote:
> > Just FYI, I have been bouncing this around
internally and it could
> > well be a RP10 bug. RP10 for windows does not use
dtdrive, it uses
> > a metadata import plugin which isn't related to
dtdrive.
> >
> > Not much help I know....
> >
> > --greg.
> >
> > Eric Hyche wrote:
> > > 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-bounceshelixcommunity.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
> 


_______________________________________________
Player-dev mailing list
Player-devhelixcommunity.org
http://lists.helixcommunity.org/mailman/listinfo/play
er-dev