Picture format decoding broken in ID3v2.2 header
See original GitHub issueBug description
For the attached file, I call .parseBlob()
. In the resulting metadata.common.picture[0].format
, I get some Chinese character. I assume this is just corrupt data.
Expected behavior
There is album art in this file that I can see with VLC. It would be great if this library could provide it with a type. If not, I think it should throw an error or not provide the picture.
Let me know if you need more samples… I have a handful of these with the same issue. Thanks!
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
id3v2.3.0 - ID3.org
This document is an informal standard and replaces the id3v2.2.0 ... In the frame header the size descriptor is followed by two flags...
Read more >New MP3 decoder misidentifies MP3 header within ID3v2 tag
I've done a bit of further investigation, and it seems that for the song from Comment 1, the ID3v2 tag breaks parsing -...
Read more >25. Practical: An ID3 Parser - gigamonkeys
Structure of an ID3v2 Tag A tag starts with a header containing information about the tag as a whole. The first three bytes...
Read more >ID3v2.3 Programming Guidelines - id3lib
The Frame Header has been expanded. The Frame ID and Frame Size fields are now four bytes long. Two bytes of Flags have...
Read more >Mp3 ID3 tags, confusing APIC frame structure - Stack Overflow
In case anyone finds this from google, the actual answer is that you have to watch out for the two flag bytes at...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Awesome! Thank you!!
Fixed in v7.1.2