R15 Bug: CONTENTGROUP mislabelled "Style"
Collapse
X
-
Re: R15 Bug: CONTENTGROUP mislabelled "Style"
It is how dBpoweramp handles the Style tag, a bit of background...dBpoweramp is tied very much to AMG metadata as the main source of metadata, AMG has a style tag, yet no where for it to go, so for m4a and mp3 Style goes to @grp and TIT1 which are the tags for ContentGroup. There is no such thing as a style tag for these formats. -
Re: R15 Bug: CONTENTGROUP mislabelled "Style"
I think for a particular application of dBpa to use a field for a different purpose is no problem.
I think for the dBpa program to mislabel the field for every user who is using the field for the intended purpose is a problem. I hope you'll fix this.Comment
-
Re: R15 Bug: CONTENTGROUP mislabelled "Style"
If AMG decided on a Style tag, who decided on @grp and TIT1 being called ContentGroup?Comment
-
Re: R15 Bug: CONTENTGROUP mislabelled "Style"
4.2.1. Identification frames
TIT1
The 'Content group description' frame is used if the sound belongs to
a larger category of sounds/music. For example, classical music is
often sorted in different musical sections (e.g. "Piano Concerto",
"Weather - Hurricane").Comment
-
Re: R15 Bug: CONTENTGROUP mislabelled "Style"
>classical music is often sorted in different musical sections (e.g. "Piano Concerto"
That is exactly what Style is used for, hence why they are interchangeable.Comment
-
Re: R15 Bug: CONTENTGROUP mislabelled "Style"
Some may use Style for musical section, but that does not make them interchangeable.
Now does it justify this change of the label from that given in the spec.
Are you planning to fix this?Comment
-
Re: R15 Bug: CONTENTGROUP mislabelled "Style"
If someone rips a CD then that piece of AMG data has to go somewhere, regardless of the format being used (FLAC, mp3, ALAC), we are not planning on changing this sorry because I not believe you have a situation where you need to store different Content group and Style tags, especially as style does not exist in m4a.Comment
-
Re: R15 Bug: CONTENTGROUP mislabelled "Style"
That data can go anywhere you please.
I think you've misunderstood the problem. Content Group and Style are not alternative labels for TIT1. TIT1 is Content Group, period. You may use TIT1 Content Group to store Style, or My Dog's Name, or What I had for Brakfast, or anything you like. But that does not change what label is correct. The label should accord with the the standard, regardless of the particular user's application.
dBpoweramp's mislabelling of TIT1 as Style makes it impossible for a user to discover that this field on the dBpoweramp display is in fact Content Group.Last edited by chrisjj; May 09, 2014, 04:41 PM.Comment

Comment