-
Notifications
You must be signed in to change notification settings - Fork 63
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to create a valid image url from ArrayBuffer #12
Comments
That's very interesting. Same the other way around: This might indicate a windows (probably windows media player) only bug. My guess is that windows media player somehow screws with those tags to make it good for windows explorer, but your parser has problems with those files. |
I'll be using this library for now, even though it's pretty slow. |
Sorry about this, I am very short of time so didn't get chance to come on here yet. I'll check this and the other issues out tomorrow :) |
Still seeing this issue - is there a chance this will get fixed? |
I've the same issue.. |
I'm having the same issue. |
Hi Zinggi, |
To anyone else having this problem you can use the following gist to convert array buffer data to base64 image. |
Thanks for you wonderful library, I've already tested this and this before, but yours is way faster.
I've got a question about how to use the returned image data. I'm currently doing it that way:
This works sometimes, however most of the time it fails. Sometimes it just doesn't create a valid file URL, most of the time it creates only parts of the picture and rarely it works perfectly:
All of these mp3 covers are shown correctly in my windows explorer.
The ones that have a nice placeholder image don't have a tags.v2.image attribute. (which is alright, better have nothing then something wrong...)
The last one somehow created an invalid URL, the others show only a part of the image.
Interestingly the Beatles one doesn't show up in my explorer, but your library parses it correctly.
Am I doing this wrong?
The text was updated successfully, but these errors were encountered: