View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0014963 | MMW 5 | Tagging framework / input plugins | public | 2018-07-12 14:57 | 2020-01-22 02:28 |
| Reporter | michal | Assigned To | |||
| Priority | none | Severity | feature | Reproducibility | N/A |
| Status | new | Resolution | open | ||
| Product Version | 5.0 | ||||
| Summary | 0014963: Add support for new classic music tags introduced in iTunes 12.5 | ||||
| Description | iTunes uses some new tags for classical music from version 12.5. We should probably support them too. They also changed mapping of grouping field! 1) new fields MOVEMENT - movement number. MP4 tag moov.udta.©mvi (number) MOVEMENTTOTAL - total number of movements. MP4 tag moov.udta.©mvc (number) For ID3v2 both saved to non-standard MVIN field, Number/Count. MOVEMENTNAME - name of the movement. MVNM in ID3v2, moov.udta.©mvn in MP4 WORK - the name of the whole musical piece . Saved by iTunes for MP3 to TT1/TIT1 ID3v2 field (previous field for grouping). For MP4 saved to moov.udta.©wrk. 2) changed field - GROUPING. They use non-standard GP1/GRP1 instead of previous TT1/TIT1 for ID3v2. I would read grouping from GP1/GRP1 if exists, otherwise from old TIT1. | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?p=447311#p447311 https://help.mp3tag.de/main_tags.html https://www.dailyrindblog.com/classical-music-metadata-101/ https://hydrogenaud.io/index.php?topic=105591.0 https://yabb.jriver.com/interact/index.php?topic=102633.0 https://www.audiocircle.com/index.php?topic=154957.0 http://age.hobba.nl/audio/mirroredpages/ogg-tagging.html | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
Oh. iTunes 12.7.5.9 writes tags as described. Version 12.8.0.150 does not save ©mvn, ©mvi, ©mvc, and ©wrk at all, it saves all info only to iTunes DB... Mess. Not sure, how to deal with this, they probably removed them, because they are not allowed by MP4 standard, but those tags in ID3v2 are not part of ID3 standard too... |
|
|
Possible solution to new grouping frame, if we decide to handle it somehow now: Reading ID3v2 tags: - read Grouping from TT1/TIT1 frame first. - read Grouping from GP1/GRP1 frame only if TT1/TIT1 frame does not exists or content is empty. Writing ID3v2 tags: - write Grouping into GP1/GRP1 only if the frame already exists - write Grouping into TT1/TIT1 frame if the frame already exists. Add it only if no GRP1 frame has been written. |
