Skip to content
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

unpack requires a buffer of 8 bytes #564

Open
alucryd opened this issue Jun 22, 2022 · 3 comments
Open

unpack requires a buffer of 8 bytes #564

alucryd opened this issue Jun 22, 2022 · 3 comments

Comments

@alucryd
Copy link

alucryd commented Jun 22, 2022

Hi guys, trying to import my library into beets, I'm getting a lot of 'unreadable' m4a files, even though they're perfectly fine. Trying mutagen-inspect on them returns the error in the title. I'm using version 1.45.1 on Arch Linux with Python 3.10. Is that maybe a problem running on Python 3.10? Happy to provide more details or one of the files for testing.

@lazka
Copy link
Member

lazka commented Jul 16, 2022

I've just added Python 3.10 testing to CI and everything seems to work fine.

You can send me a file to [email protected] (or post it publicly if there are not copyright issues)

@lazka
Copy link
Member

lazka commented Oct 24, 2022

Thanks, the first file (1.01) fails with:

Traceback (most recent call last):
  File "/mnt/c/msys64/home/user/git/mutagen/mutagen/mp4/__init__.py", line 1203, in load
    self.chapters = self.MP4Chapters(atoms, fileobj)
  File "/mnt/c/msys64/home/user/git/mutagen/mutagen/mp4/__init__.py", line 923, in __init__
    self.load(*args, **kwargs)
  File "/mnt/c/msys64/home/user/git/mutagen/mutagen/mp4/__init__.py", line 947, in load
    self._parse_chpl(chpl, fileobj)
  File "/mnt/c/msys64/home/user/git/mutagen/mutagen/mp4/__init__.py", line 991, in _parse_chpl
    start = struct.unpack(">Q", data[pos:pos + 8])[0] / 10000
struct.error: unpack requires a buffer of 8 bytes

It's a mutagen bug that this error is handled properly, but needs investigating if the file is broken or not.

The second file (1.03) works fine for me (also using Python 3.10).

@alucryd
Copy link
Author

alucryd commented Oct 31, 2022

FWIW the files play fine, and they were all originally managed by beets (both working and non working files). I can try to retag them with another software, see if that helps.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants