-
-
Notifications
You must be signed in to change notification settings - Fork 34
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
ID3v2: URIs in APIC frames are not parsed #247
Comments
I've always put off supporting those, didn't think anyone even used them, especially with them being discouraged by both the ID3v2 and FLAC picture specs. To support this It'd be nice to only make a special case on I don't have any time to work on this at the moment. Would you be interested in working on this approach? |
The URI is the actual metadata. Fetching any content referenced by an URI is out of scope. |
It may or may not be worth it to have a special case for the external images to make them nicer to work with. They work currently, but with |
I agree that mapping URI data from |
ID3v2 allows for URIs to the image in the APIC tag. This is currently ignored and will not parse the image.
https://mutagen-specs.readthedocs.io/en/latest/id3/id3v2.4.0-frames.html#apic
I thought about implementing this functionality myself but the URI could point to a file or a image on the web. Since I don't think lofty should connect to the internet on it's own I would suggest to just return the URI.
The text was updated successfully, but these errors were encountered: