mirror of
https://github.com/jellyfin/jellyfin.git
synced 2026-07-16 05:43:54 +03:00
A video is said to be remixed when there is seemingly no reason to do so. #6805
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @lesha-co on GitHub (Mar 8, 2025).
Description of the bug
So I have an .mp4 file with h264 (
h264 (High) (avc1 / 0x31637661)) and AAC (aac (LC) (mp4a / 0x6134706D)) and trying to play it from different browsers.Firefox (Mac OS and Windows), Chrome (Windows) and Safari have no issues with playing file as-is (Playback Info says
Play method — Direct playingand there is no ffmpeg process). The "Original Media" section also states thatContainer — mp4.However, when watching the same file with Chrome (Mac OS) I see the different result:
Play method — Remuxingand somehowContainer — mov. There is no ffmpeg process though so I guess there is no actual remuxing happening.Reproduction steps
Allow video playback that requires conversion without re-encodingWhat is the current bug behavior?
Chrome on Mac OS stops with the message that "Playback failed because the media is not supported by this client."
What is the expected correct behavior?
either
a) Chrome should not do that. I guess that's likely a Chrome's problem and you can't do anything about it
b) or it shouldn't error out as there is no remuxing happening?
Jellyfin Server version
10.10.0+
Specify commit id
No response
Specify unstable release number
No response
Specify version number
No response
Specify the build version
10.10.6-24
Environment
Jellyfin logs
FFmpeg logs
Client / Browser logs
Relevant screenshots or videos
Left is Firefox, right is Chrome (Mac), playing the same file
Additional information
No response
@gnattu commented on GitHub (Mar 8, 2025):
Such probe result is something from older version of jellyfin. You can try replace all metadata so that it would result in a single mp4 result (I think).
ffmpeg will report all these during probe so we have to pick one. On earlier version we just store all of them and it may confuse some browser.
@lesha-co commented on GitHub (Mar 8, 2025):
I tried ffprobe version 7.1.1 (latest) and have these results:
so refreshing metadata won't help
but again it looks to me that there is no actual remuxing happening on a jellyfin side so that means that the "no remuxing" rule is not broken as far as jellyfin concerned so playback should be possible?
@gnattu commented on GitHub (Mar 8, 2025):
Why don't you try refreshing once instead of speculating? The server will do no additional process for those results and the raw ffprobe means nothing.
Because you disabled remux permission for that user so that the native player is forced to load that file. It may or may not work but for this file it works.
@jellyfin-bot commented on GitHub (Jul 7, 2025):
This issue has gone 120 days without an update and will be closed within 21 days if there is no new activity. To prevent this issue from being closed, please confirm the issue has not already been fixed by providing updated examples or logs.
If you have any questions you can use one of several ways to contact us.
@jellyfin-bot commented on GitHub (Jul 28, 2025):
This issue was closed due to inactivity.