Print

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

[mcphzgig]

I have just added Composer tags to some tracks by adding a Composer field in the Tools > Options> Tree & View Settings.

I notice that MJ9 uses the COMM tag frame for Composer, as opposed to the ID3v2's TCOM Composer frame.

If I use the TCOM tag (via another editor), it is not displayed in the Composer column I have added in the track view panel.

Did I add the tag incorrectly in MJ9, or should MJ9 be using the ID3v2 frame that is available for this tag?

[Matt]

We don't have a mapping table like that in the MP3 plugin yet to know where to put new fields.  We'll figure something better out though.

Are there other common fields that people would create?

We could just make "composer" a default DB field.

[Kurt Young]

We don't have a mapping table like that in the MP3 plugin yet to know where to put new fields.  We'll figure something better out though.

Are there other common fields that people would create?

We could just make "composer" a default DB field.

PLEASE DO!!  Make composer a default field!  Woot!

It would rock if composer was a default DB field... it would make it so much easier for Steve to then work Composer tags into the iPod plugin.

The iPod allows browsing by composer while on the go, but first the iPod's database has to be updated with the info... what better place to get the info than from a standard MJDB field?

[KingSparta]

Matt

The Same Interface You Have But Add A Combo Box

Include All The ID3v2 Tags.

User Wants Composer He pulls it down and selects it, mj now adds that field to the file in standard Id3v2 format easy simple and clean.


Listening to: 'Papa Loves Mambo' from 'The Best Of Perry Como' by 'Perry Como' on Media Jukebox Charted At 04 In 1954

[mcphzgig]

The Same Interface You Have But Add A Combo Box. Include All The ID3v2 Tags.

Way to go KingSparta!

The standalone tag editor I am currently experimenting with, has a range of the ID3v2 frames built-in, including Composer.

I think there are 74 declared frame types in total in ID3v2.3, but a number are aleady in use in the standard MJ9 schema.  74 is still a lot, though.

There are always benefits in conforming to standards - but, admittedly, sometimes limitations as well.  Integrating imported files tagged elsewhere would fall on the benefit side.

The pragmatic (i.e hard) part would be deciding the minimal subset of frame types that would satisfy an 80/20 rule (or similar) on meeting user's needs.  Any wish lists out there?

[Matt]

We'll figure something out.

I'm not sure it makes sense for people to pick an ID3v2 field in the MJ database configuration.  Fancy mapping should probably go in the MP3 plugin configuration, since it doesn't apply to formats like OGG, APE and WMA.

Thanks everyone.

[KingSparta]

>> Fancy mapping should probably go
>> in the MP3 plugin configuration
that does make sence.

Maybe still a Combobox with Pull down Fields Aval

In the Plugin If the field is a Common Id3v2 tag Like "Composer" etc.. Then let the plugin save it correctly as a proper "Composer - TCOM" ID3v2 Tag for MP3's.

Thanks for thinking about this, however it turnes out.

[Matt]

Thanks for thinking about this, however it turnes out.

Trust me -- my thinking about things isn't worth much.

But you've got a good idea -- the MP3 plugin should be able to be a bit smarter.  We'll see what we can do.