Skip to main content

Notice

Please note that most of the software linked on this forum is likely to be safe to use. If you are unsure, feel free to ask in the relevant topics, or send a private message to an administrator or moderator. To help curb the problems of false positives, or in the event that you do find actual malware, you can contribute through the article linked here.
Topic: WAV tagging odd file size bug (Read 3707 times) previous topic - next topic
0 Members and 1 Guest are viewing this topic.

WAV tagging odd file size bug

Hi,

I've just started with FB (1.2.6) and played around in a test directory with my WAV files and noticed that the file size gets an odd number - which is not correct.

E.g. an empty WAV file has 35.778.668 bytes.

After adding the value "ABBA" to the artist, the file size is 35.778.735 bytes - which is definitely incorrect. A WAV (or AIFF) file MUST HAVE an EVEN number of bytes.

Here are the latest bytes added to the file:

0221f060h: 00 00 00 00 00 00 FF FF 00 00 FF FF 4C 49 53 54 ; ......ÿÿ..ÿÿLIST
0221f070h: 12 00 00 00 49 4E 46 4F 49 41 52 54 05 00 00 00 ; ....INFOIART....
0221f080h: 41 42 42 41 00 00 69 64 33 20 21 00 00 00 49 44 ; ABBA..id3 !...ID
0221f090h: 33 03 00 00 00 00 00 17 54 50 45 31 00 00 00 0D ; 3.......TPE1....
0221f0a0h: 00 00 01 FF FE 41 00 42 00 42 00 41 00 00 00    ; ...ÿþA.B.B.A...

Last 4 bytes in the first line starts the LIST chunk, and on 0221f086h starts the "id3 " chunk with a total length of 21h (33) bytes. The stored length is correct, but when a chunk has an ODD number of bytes a WORD PADDING BYTE ("00") must be added (the stored chunk size is still 21h (33) !).

So the last line should look like:

0221f0a0h: 00 00 01 FF FE 41 00 42 00 42 00 41 00 00 00 00    ; ...ÿþA.B.B.A....


Please fix this ASAP in a hotfix - otherwise foobar2000 is NOT usable for WAV and AIFF files.

THANKS A LOT

WAV tagging odd file size bug

Reply #1
Thanks for the bug report, the problem will be fixed in the next update.

I would like to point out that:
  • The part of your report about AIFF is simply false as there's no such bug with AIFF files, a padding byte is added correctly.
  • The affected WAV files are still readable by foobar2000 and the bug has been present for several versions without anyone reporting it so I'm guessing the files are still readable by most software out there; I can assure you they will stay readable by in future foobar2000 versions in case you wish to recover your destroyed collection.
  • It's difficult to call these files destroyed as no data has been lost.


It would be also very helpful if you can name which piece of software that you use has problems with odd-size WAV files.
Microsoft Windows: We can't script here, this is bat country.

 

WAV tagging odd file size bug

Reply #2
Thanks for the bug report, the problem will be fixed in the next update.


THANKS!


I would like to point out that:
  • The part of your report about AIFF is simply false as there's no such bug with AIFF files, a padding byte is added correctly.


Sorry, yes - the last sentence is not correct. Didn't test it with AIFF but I thought it might be the same implementation logic.

  • The affected WAV files are still readable by foobar2000 and the bug has been present for several versions without anyone reporting it so I'm guessing the files are still readable by most software out there; I can assure you they will stay readable by in future foobar2000 versions in case you wish to recover your destroyed collection.


THANKS - I'm sure foobar2000 will read the files. :-)

Of course - some other software might read them.

I've reported the same bug to Tag & Rename (and 3.6.6 works correct) and Serato Scratch Live (SSL). SSL 2.4.4 works correct but before (or 2.4.2/3?) it has reported the track as corrupt and won't play it.

As I can remember Wavelab 7 reports these kind of files as a corrupt file and won't open it but since last week Wavelab 8 is available and I've updated to it. I'll test tonight. Wavelab 8 also now supports ID3 in WAV. :-)

  • It's difficult to call these files destroyed as no data has been lost.


Sorry for the hard wording - but before SSL has fixed it - and Wavelab, they showed "corrupt file". Might be horrible for people who don't know the details.

    It would be also very helpful if you can name which piece of software that you use has problems with odd-size WAV files.[/li]
[/quote]

Due my bug reports 2 pieces of software have been fixed which I'm using. I've to test Wavelab 8 tonight. Maybe other software which burns files on CD might have problems too.

Due the big features with foobar2000 I'm planning a lot of mass updates on my WAV files but I have to wait for the fix to avoid unplanned troubles and big backup/sync processes.

Thanks a lot!