View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0017467 | MMW 5 | Tagging framework / input plugins | public | 2021-01-29 20:49 | 2026-07-10 14:48 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | feature | Reproducibility | N/A |
| Status | resolved | Resolution | fixed | ||
| Target Version | 2027 | Fixed in Version | 2027 | ||
| Summary | 0017467: Extended tags: Add non supported MM Tags to Extended tags | ||||
| Description | MM5 support some standard and classified fields, but some are not available even clearly classified in ID3v2 like https://id3.org/id3v2.4.0-frames The change would include that non MM used tags should be shown at extended tags and values can be edited. Solution for reading such tags in this case is to create map of standard tags (HTML5Monkey\Id3lib.pas) from https://id3.org/id3v2.4.0-frames and make them recognized as Tag name correctly eg. for example tag TPE4 -> "Remixed by (TPE4)" where user can edit value but not Tag Name as it is already predefined in standard eg. map supported tags "HTML5Monkey\Id3lib.pas" with descriptions used from https://id3.org/id3v2.4.0-frames Solution for writing such tags into files would be to instruct user to Type standard field eg. TPE4 and MM would fill the rest of Name so it would be clear that tag is standard not part of TXXX NOTE: As they are extended Tags no translation is needed ATM, but will allow users to manage those tags also and be less dependent on third party apps. | ||||
| Additional Information | https://www.mediamonkey.com/forum/viewtopic.php?f=30&t=98293 | ||||
| Tags | No tags attached. | ||||
| Fixed in build | 3515 | ||||
|
|
Fixed in build 3515. I reworked support of extended tags, now it uses own DB table. It allows to add extended tags based on the source format, it offers the most common and used fields during editing. I added column "Raw name" displaying better identification of such tag (so it can be saved to the same place in the file, as sometimes one value can be saved in different parts of the file structure). For WAV user can use more tagging standards (standard RIFF Info chunk or ID3v2 in special chunk, can be selected in the first "Format" column and then it affect what tag names can be used). I think it works quite well and should allow user to have better control and for us to make support of tag fields a lot wider. |
