You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The parser freaks out on some embedded images, it seems completely random as to what images do and don't trip it:
Uncaught node.js Error
Error: Index out of range.
at Object.ID3Frame.parse (/home/damon/projects/tunes/node_modules/id3js/dist/id3.js:696:13)
at eval (/home/damon/projects/tunes/node_modules/id3js/dist/id3.js:943:24)
at eval (/home/damon/projects/tunes/node_modules/id3js/dist/id3.js:118:4)
at Object.wrapper [as oncomplete] (fs.js:454:17)
As you can see it kinda just cuts off part way through parsing the image.
If I delete the image from the ID3 tag, it parses that file fine and then breaks on a later one.
The only thing the breaking images seem to have had in common is that they're mostly fairly high res (both this and the previous one were 800x800) though there have been ones smaller such as 400x360 which have broken in the same way.
There should really be an option to skip parsing images so those getting this issue can just bypass the image parsing and so this module will still be usable.
The text was updated successfully, but these errors were encountered:
The parser freaks out on some embedded images, it seems completely random as to what images do and don't trip it:
An example of one it's breaking on: http://pastebin.com/1RRDqknW
As you can see it kinda just cuts off part way through parsing the image.
If I delete the image from the ID3 tag, it parses that file fine and then breaks on a later one.
The only thing the breaking images seem to have had in common is that they're mostly fairly high res (both this and the previous one were 800x800) though there have been ones smaller such as 400x360 which have broken in the same way.
There should really be an option to skip parsing images so those getting this issue can just bypass the image parsing and so this module will still be usable.
The text was updated successfully, but these errors were encountered: