View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0013674 | MMW v4 | Framework: Tagging | public | 2016-11-23 15:14 | 2016-11-23 19:42 |
| Reporter | lowlander | Assigned To | |||
| Priority | high | Severity | major | Reproducibility | always |
| Status | new | Resolution | open | ||
| Product Version | 4.1.16 | ||||
| Summary | 0013674: User should be able to determine read order when multiple tags can be read for one field value | ||||
| Description | The example here is TYER and TDRC, but this should go for all such cases. MediaMonkey writes both v2.3 TYER and v2.4 TDRC. However other taggers often only update one of those values (as they either support ID3v2.3 or ID3v2.4). This results in a file having different values for the Date field in MediaMonkey. Through the ini the user should be able to set the order in which MediaMonkey reads the value for Date (this should go for all fields with multiple tags for all tagging standards). This should be independent of tag writing settings. In the short term as a quick solution I suggest that MediaMonkey reads TYER first than TDRC as MediaMonkey is an ID4v2.3 application. | ||||
| Steps To Reproduce | Something like [TAGREADING] ID3_DATE=TYER;TDRC which instructs MediaMonkey to first read the TYER tag and if it is empty MediaMonkey will try the TDRC tag. | ||||
| Additional Information | ROI-747-78228 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
As talked on IM if some application is known that Write/Update only TYER MMW can be set to update/read only that one, like this from 0004078 [MP3Tagging] DisableFrames=TDRC;TDAT EnableFrames=TYER |
|
|
Correct, but with many having files from many sources it'd be best to have the option to determine read order preference. This way if TYER is empty it would then read TDRC. This extends to any fields with multiple tags. |
