View Issue Details

IDProjectCategoryView StatusLast Update
0021312MMW 5Tagging / organizing (properties / auto-tools)public2024-11-01 13:09
Reportermichal Assigned To 
PriorityurgentSeverityminorReproducibilityN/A
Status assignedResolutionopen 
Product Version5.1 
Target Version5.1.1 
Summary0021312: Add support for ID3 tagging to WAV files
DescriptionIt seems, it became de facto standard during last years, that WAV files can be tagged by standard ID3v2 tag in "id3 " chunk. Several tagging SWs support it. It allows to save currently not supported fields, like disk number or artworks, directly to WAVs. Applications should support this chunk or ignore it, but it should not make problems.
It will need new tagging plugin for WAV. This plugin will share core functionality with Android version, it only needs more testing and some enhancements and fixes, and same code could be used for Win version too.

Plugin should use standard fields whenever possible, and only in case it would need to save data like disk number or artwork, it should use ID3 tag.
TagsNo tags attached.
Fixed in build

Relationships

related to 0021286 assignedmichal ID3 Tags: Track # is saved incorrectly when format is x/y 
related to 0015818 closedmichal WAV: WAV files with ID3 tag fail to play 
related to 0019904 closedmichal WAV: Some WAV files with incorrect ID3 Chunk are not playable in MM 
related to 0018337 closedpeke Codec: Some WAV files can't be decoded 

Activities

peke

2024-11-01 12:09

developer   ~0077450

Please note that many devices do not support playback of such WAV files.

Also we should pay attention to ID3 version used and some support 2.3 and some 2.4 some use mixed eg. 2.3 format with 2.4 fields.

Personally I would correctly import it, but leave it separate in extended and make MM behavior configurable (I personally remove it whenever I find it or simply just convert WAV to FLAC).

michal

2024-11-01 12:55

developer   ~0077451

Last edited: 2024-11-01 13:09

I think there is misunderstanding - ID3 tag, which causes, that WAV files are not playable on some devices is something else - it was ID3 segment taken from MP3
format but at the beginning of the WAV file. We will not tag this way at all (in fact we fix such files automatically by removing this thing from the beginning of the file during tagging), it corrupts RIFF WAVE format.
I talk about RIFF format chunk with id "id3 ", this cannot affect playback of the WAV in any device, as it does not corrupt RIFF WAVE format, devices should simply ignore such chunk in case they do not know it, it will be always at the end of the file after audio data.
Also there should not be problem with ID3 version, as identification of the version is part of such data, it is in fact standard ID3 tag wrapped in "id3 " RIFF chunk.