mackatini 4 Posted March 24, 2020 Posted March 24, 2020 Hi there, I've just updated to the latest version 4.4.0.40 from 4.3.1.0. Since upgrading, there are issues with transcoding of certain files. Not all. I have tried turning hardware transcoding on and off, but I get the same result. Attached are the logs for the same video from both versions of Emby Server. One that works and one that doesn't. Cheers, Version 4.4.0.40.txt Version 4.3.1.0.txt
softworkz 5077 Posted March 24, 2020 Posted March 24, 2020 Thank you very much for reporting that issue. Could you provide a file for testing? (the smaller the better)
sudokusam 0 Posted March 25, 2020 Posted March 25, 2020 I'm experiencing this problem too. Some files that played fine in 4.3.1.0 no longer play in 4.4.0.40. I narrowed it down to transcoding files with an m4v extension. All m4v files I've tested are affected, regardless of the codec. If I rename them to mp4 they play fine. I think I found the reason in the log files: 4.4.0.40: ffmpeg.exe ... -f m4v ... ffmpeg.exe ... -f mp4 ...
softworkz 5077 Posted March 25, 2020 Posted March 25, 2020 I'm experiencing this problem too. Some files that played fine in 4.3.1.0 no longer play in 4.4.0.40. I narrowed it down to transcoding files with an m4v extension. All m4v files I've tested are affected, regardless of the codec. If I rename them to mp4 they play fine. I think I found the reason in the log files: 4.4.0.40: ffmpeg.exe ... -f m4v ... ffmpeg.exe ... -f mp4 ... Well done, you hit the point! ,,,even though I had already seen this :-) The problem seems to be that there are two different container specs claiming the .mv4 extension: One is from Apple, meaning something like mp4 + DRM=> this is what Wikipedia tells . The other one is supposed to be a single RAW MPEG4 video stream and used by various video cameras and Adobe applications=> this is what ffmpeg considers m4v to be I was still interested in a sample file because I'm curious about whether there's any difference at all between those files and normal mp4 files..
mackatini 4 Posted March 25, 2020 Author Posted March 25, 2020 I renamed the files to MP4 and they started playing. When i try use ffmpeg to cut a snippet from the video it gives me an error so I can't send a small test file at the moment, but based on Sudukosam's find, that might be the issue. Great find there..
mackatini 4 Posted March 25, 2020 Author Posted March 25, 2020 Well done, you hit the point! ,,,even though I had already seen this :-) The problem seems to be that there are two different container specs claiming the .mv4 extension: One is from Apple, meaning something like mp4 + DRM=> this is what Wikipedia tells . The other one is supposed to be a single RAW MPEG4 video stream and used by various video cameras and Adobe applications=> this is what ffmpeg considers m4v to be I was still interested in a sample file because I'm curious about whether there's any difference at all between those files and normal mp4 files.. I can send you the complete file. 439Mb if you're happy with that?
sudokusam 0 Posted March 25, 2020 Posted March 25, 2020 Well done, you hit the point! ,,,even though I had already seen this :-) The problem seems to be that there are two different container specs claiming the .mv4 extension: One is from Apple, meaning something like mp4 + DRM=> this is what Wikipedia tells . The other one is supposed to be a single RAW MPEG4 video stream and used by various video cameras and Adobe applications=> this is what ffmpeg considers m4v to be I was still interested in a sample file because I'm curious about whether there's any difference at all between those files and normal mp4 files.. My files were transcoded by Handbrake so they're actually mp4 files. I think quicktime will only read chapters and ac3 audio if they're renamed to m4v, so that's why handbrake (optionally) does this. On the other hand ffmpeg seems to do something different depending if they're mp4 or m4v. I haven't had a chance to look into it further.
softworkz 5077 Posted March 26, 2020 Posted March 26, 2020 This issue should be fixed with the next update. Thanks a lot for reporting to both of you!
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now