-
-
Notifications
You must be signed in to change notification settings - Fork 41
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
ffmpeg can’t play certain Ogg Vorbis files created between 2017 and now, tagged with EasyTAG #2313
Comments
For the record, the track gets added to the library and is findable. I traced the issue somewhere into here https://github.com/music-assistant/server/blob/6b53fedb0662a389e05256d9a259d479c4806eb2/music_assistant/server/helpers/audio.py#L171 and it seems to be something I think it would be difficult to get a clean traceback though, given that this is async code running on a separate coroutine not actually aware of what |
Update: I tried running several Update 2: ran in container, no error. Removed
|
It might (very unlikely) be the build options used to build ffmpeg. From https://stackoverflow.com/questions/45372501/ffmpeg-ogg-invalid-data-found-when-processing-input :
It might not be that. Might just be a buggy version. The |
Container build options that fail to decode Ogg Vorbis files:
Working FFMpeg build options that successfully decode the file:
I inspected a diff of sorted build config options and did not spot anything that might explain it. |
Extra verbose run of container
|
|
OK, mystery solved. I tracked it down to this https://gitlab.gnome.org/GNOME/easytag/-/issues/8 . I used EasyTAG to tag my Vorbis files many years ago. It fucked with the files.
Reencoding the file with my own
What an absolute disaster. Please update Leaving this ticket open for the |
Our container is based on Debian - ffmpeg on debian is super outdated so we're already relying on the multimedia repo; Looks like their version is also already lacking behind. |
What version of Music Assistant has the issue?
2.0.4
What version of the Home Assistant Integration have you got installed?
Latest
Have you tried everything in the Troubleshooting FAQ and reviewed the Open and Closed Issues and Discussions to resolve this yourself?
The problem
in the log
How to reproduce
I would have to share one of these faulty files.
Music Providers
Filesystem.
Player Providers
This is a metadata scanning issue. Players are not involved.
Full log output
Really, it's only this, over an over again:
Additional information
What I would like to see is a backtrace of this type of exception so I can reproduce it down to the exact byte of the file causing the issue and the exact line of code raising it, but it seems no matter what logging level I set, I cannot actually get a backtrace.
What version of Home Assistant Core are your running
2024.5.0
What type of installation are you running?
Home Assistant Core
On what type of hardware are you running?
Linux
The text was updated successfully, but these errors were encountered: