Every now and then when I convert a file, Emby makes the final file 1200 minutes long. I can cut off the excess and the file is then fine, but it's an odd problem to run into.
1200 Minute Conversion Error
Posted 01 December 2019 - 04:31 PM
Various lengths. from 20 minute shorts to 3 hour films. They are mkv rips of blurays and/or dvds. It seems to be random too. I could convert a season of a show, and two thirds of the episodes are fine but then the other 3rd have this problem.
But it's also seems to just be the timecode that's incorrect. There's nothing actually playable after the end of the film's normal runtime.
Posted 01 December 2019 - 04:43 PM
It shows up with that length when opened in VLC. But if I scroll past the normal runtime, the file closes. Which makes me think there's no actual data added, just the wrong length being put in the file conversion. But every time it happens, it's the same wrong length.
Also, I don't know why the screenshot uploaded like that, but the actual video looks fine after the conversion. It's just the length.
Edited by Bigmack3000, 01 December 2019 - 04:44 PM.
Posted 06 December 2019 - 04:02 AM
You think the type of subtitle is the problem?
Also, none of the conversions last night or today had burned in subtitles and none had the error either.
So, here's what's happening:
Sometimes (or maybe even always in case of PGS subs), the subtitle frames not have valid values for start_display_time and end_display_time.
Like above: 4294967295 is just the maximum for 32 bit uint, but ffmpeg seems to interpret that value.
That is no problem as long as there's another subtitle frame following which indicates the end of the previous one (that next one might even be empty just to invalidate the previous one).
But when it comes to the very last subtitle graphic the end_display time is considered to be a frame event. Ffmpeg considers the 4294967295 to be valid and "waits" for that to happen. Meanwhile. the video main has ended as well, but by default configuration, the overlay filter repeats a stream's image when it has reached its end.
And that causes one additional frame to be added to the output file with an insanely high timestamp value:
That one additional frame is in turn causing the high and incorrect container duration.
This is fixed in the upcoming beta (18.104.22.168)
Edited by softworkz, 06 December 2019 - 04:17 AM.
- Bigmack3000 likes this
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users