Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[dsully]

Media Center appears to write out COMM tags for including it's ReplayGain information. Unfortunately, this isn't a very friendly format for automatically parsing those tags, or simply viewing them in another application.

          'COMM' => [
                      'Media Jukebox: Tool NameMedia Center',
                      'Media Jukebox: Tool Version11.0.314',
                      'Media Jukebox: Replay Gain-2.7524500000000001',
                      'Media Jukebox: Peak Level0.43817',
                      'Media Jukebox: Rating5',
                      'Media Jukebox: Intensity4'
                    ],

The tags lend them selves much better to the TXXX keyNULLvalue format that the ID3 spec defines.

I'd like to request that a future version of Media Center use the TXXX tags instead of COMM for this information.

Thanks.

[hit_ny]

Ok Fine.

what about the rest of ppl who have already analysed and got RG in the COMM tag ?

Re-analysis of many 10s of thousand files !!!!

[qwert73]

Ok Fine.

what about the rest of ppl who have already analysed and got RG in the COMM tag ?

Re-analysis of many 10s of thousand files !!!!

That is exactly the reason why i don't say "give us fuul support of ID3v2", but the possibility to decide from field to field if you want to store a tag in the comment-field or to the frame where it belongs by standard.  Once again what i posted here: http://yabb.jriver.com/interact/index.php?topic=28958.150

When I create a new field i would like to type in the configuration something like COMm, TXXX(userdefined) or T???(standard frames)

So everybody gets what he wants!

Once again: The tagging is the one and only very poor point of MC and i hope this is going to be changed in MC12 because i need interoperability to other applications! Why should i scan my files two times: one time in MC, the other time in Foobar?? ?

[hit_ny]

This might not be too hard on second thoughts. All that is required is they create the standard field and user move/copy field ought to do it.

How to tell the diff between RG (std) & RG (COMM) is the question ?

I guess JRiver were waiting to see how things panned out, even tho there is a std for certain tags it appears that it's not followed very strictly among vendors. Meanwhile they did it the proprietary way.

[dsully]

Alternatively, MC should use RVA / RVAD / RVA2 tags to store the RG information.

[Raysy]

It would be great  if MC supports all offical ID3-Tag frames from id3.org  - I'm using WCOP (Copyright) and TPE4 (Interpreted, remixed, or otherwise modified by), which are not supported now. The standard of ID3v2 is clearly declared here: http://www.id3.org/id3v2.3.0.html#sec4.

This might not be too hard on second thoughts. All that is required is they create the standard field and user move/copy field ought to do it.

MC could automatically copy the information from COMM to the correct frame in the tag. It would go fast, because it don't has to analyse the files again.