-
Notifications
You must be signed in to change notification settings - Fork 165
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
Files containing unknown streams cause an Internal Server Error #584
Comments
Does the server die with any particular panic message? would be useful to get that 🙏🏻 |
When it's run through the command line it seems more stable, or perhaps this file is just different. When running as a service, the internal service error repeats a few times.
With the server, I'll see the error repeated. In the case where it required a restart, the error repeated about 6-8 times:
|
Here's another one with a specific error about EBML header parsing:
|
I'm seeing the same thing. I'm new to this project, so maybe I'm doing something wrong. But I can't get a single file to play, even after using the proposed ffmpeg re-encoding. Using the docker image dim:dev, which seems pretty recent. I don't have any logs that seem relevant outside of what's been reported above. |
Describe the bug
The
server diessession until theservice is restartedbrowser is refreshed if I try to play a file where any of the streams are unknown to ffmpeg. Examples might include bitmap subtitles from blurays.To Reproduce
Not sure how to create such a file, but attempting to play one will cause it.
Additional context
This can be worked around with a simple copy so that the unknowables gets stripped from the file. For example:
The text was updated successfully, but these errors were encountered: