-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Playback error when playing mkv files without transcoding on version 10.8.0. Worked on older versions #3690
Comments
re scan the library you will be fine |
Same for me. Rescan didnt helped me.
Any idea how to fixit without reverting backup? |
AFAIK, MKV playback in browsers requires Remuxing to be enabled because browsers don't support MKV (but WEBM as a subset). |
If you still have 10.7.7, could you check what method it uses (Playback Info)? Also, what browser? Maybe some can play MKV directly 🤔 |
Hi,
For 10.8
Webbrowser - Chrome - Version 102.0.5005.115 (Official Build) (64-bit) |
Rescan did not fix the problem. |
I have the same problem, i cant play mkv´s without transcoding! |
So it looks like Windows has a problem playing MKV for people who have never installed VLC. @dmitrylyzo Sorry but can you note where this setting is? I'm running Is the I referenced the docs on transcoding and couldn't find the menu -- I'm just trying to do slow CPU transcoding (no devices are passed through). For now I'm just converting |
@t3hmrman it is per user in the Dashboard: As far as I remember, the problem is that browsers (Chrome at least) can only play WebM (a subset of MKV), before 10.8 we had a non-strict condition that passed MKV as is (direct) and it worked (in Chrome), but this MKV support is not documented (by Chrome) and some MKVs (rare?) still don't work (from what I have heard). In 10.8 the condition became strict and cut off MKV. |
Hey @dmitrylyzo thanks for taking time out of your day to explain this -- TIL about WebM being a subset of MKV, I guess it's WebMatroska (? wikipedia doesn't confirm). I will remux to my heart's content! I wonder if a nice sidecar container that watches a directory and does nothing but try and re-mux it would be a good idea. [EDIT] - Just realized Jellyfin has a plugin system, I'm going to see if I can make one! [EDIT2] - Turns out transcoding was already enabled, but I think I'll live with just making sure to convert files with |
Actually, it should be remuxing - copy video and audio as is in the supported container (TS, I think). This is much less CPU usage, but still requires some space in the transcoding folder. EDIT: afair, we are not going to bring this undocumented MKV support back, but some kind of experimental option to customize the device profile (client-side) would be useful. |
Sorry but again I don't see the word "remux" any where in either I just want to make sure I'm not somehow missing another option -- Jellyfin does not do remuxing right -- there's no operation to trigger it for a given file (and there won't be unless someone makes a plugin or something)?
All good, that's very reasonable -- I could make some changes to documentation if you want this to be a bit more pronounced and make a commit. I do want to note that .mkv playback does work on Linux -- it was only on Windows that the error was happening. I suspect that a Windows machine with VLC installed would actually be able to play on the Web (after VLC installed required codecs) and/or be able to play from VLC (ex. via the streaming link). I don't own a Windows machine, so I can't test too easily. |
In my original post I refer to
Aha, MKV seems to be enabled for Edge Chromium on Windows (#1660): jellyfin-web/src/scripts/browserDeviceProfile.js Lines 154 to 156 in 84c007f
In this case it should be DirectPlay (if it really supports MKV). |
Thanks for the clarification -- all of those were checked for me:
This perfectly explains it -- the person who was trying to use my instance is not on Edge Chromium but this makes sense. Thank you for digging through and getting the pointer to the code, looking at it now. |
This is a problem in the Jellyfin WebOS client, which does not seem to be able to reliably detect supported codecs, effectively not just remuxing files that could be directly played before 10.8, but transcoding them instead. |
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media. |
Definitely I did make the order
On Tue, May 2, 2023 at 6:51 PM jellyfin-bot ***@***.***> wrote:
This issue has gone 120 days without comment. To avoid abandoned issues,
it will be closed in 21 days if there are no new comments.
If you're the original submitter of this issue, please comment confirming
if this issue still affects you in the latest release or master branch, or
close the issue if it has been fixed. If you're another user also affected
by this bug, please comment confirming so. Either action will remove the
stale label.
This bot exists to prevent issues from becoming stale and forgotten.
Jellyfin is always moving forward, and bugs are often fixed as side effects
of other changes. We therefore ask that bug report authors remain vigilant
about their issues to ensure they are closed if fixed, or re-confirmed -
perhaps with fresh logs or reproduction examples - regularly. If you have
any questions you can reach us on Matrix or Social Media
<https://jellyfin.org/contact>.
—
Reply to this email directly, view it on GitHub
<#3690 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A6NWLSRZT6EBLA5UV4OFLRLXEG22TANCNFSM5YQHD4UA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
--
Lios
|
I also have the same issue on the latest version of Jellyfin. Only devices that don't play MKV files are Roku 4k and Android tablet. |
This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments. If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label. This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media. |
I am using docker. I get the following error while playing media files that are in mkv containers. MP4 files work fine.
Media info
The text was updated successfully, but these errors were encountered: