Errors in VRD output

osmium

New member
I use ffmpeg to check my tv recordings for errors:
ffmpeg -hide_banner -hwaccel auto -v level+info -i "D:\input.ts" -f null - 2>"D:\input.ts.log"

Sometimes after processing them with VRD (removing the commercials, in smart mode) and checking the output with the above command, I get this error message in the log file:
[h264 @ 0000000000471f80] [error] number of reference frames (0+5) exceeds max (4; probably corrupt input), discarding one

It is often, but not always, accompanied by other errors such as:
[h264 @ 0000000000472ac0] [error] mmco: unref short failure

[null @ 0000000002f30540] [error] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 8 >= 8

It seems they are caused by VRD because they always appear around the cut points no matter where I place the cut markers in the program and even if the source file has no errors.

I also noticed this only happens with files recorded from specific channels, e.g all recordings from FOX Life have this problem while these from Moviestar - not.
 
Last edited:

Dan203

Senior Developer
Staff member
The first error and second error are likely not an issue. When you do a smart edit we have to recode a few frames around each edit point, and our encoder isn’t capable of matching every single option, so it's possible there is a slight mismatch between the recoded frames and the original file that is triggering the error. But as long as they aren’t causing playback issues there is nothing to worry about. If you want to completely eliminate that issue the only way to do it is to fully recode the entire file so that all frames are recoded and guaranteed to match exactly.

The third error is wrong. The TS spec allows for a DTS value of 0 if the PTS and DTS are the same value, but ffmpeg doesn’t like that and throws this error whenever it's encountered. You can safely ignore it.
 

Danr

Administrator
Staff member
I use ffmpeg to check my tv recordings for errors:
ffmpeg -hide_banner -hwaccel auto -v level+info -i "D:\input.ts" -f null - 2>"D:\input.ts.log"

Sometimes after processing them with VRD (removing the commercials, in smart mode) and checking the output with the above command, I get this error message in the log file:
[h264 @ 0000000000471f80] [error] number of reference frames (0+5) exceeds max (4; probably corrupt input), discarding one

It is often, but not always, accompanied by other errors such as:
[h264 @ 0000000000472ac0] [error] mmco: unref short failure

[null @ 0000000002f30540] [error] Application provided invalid, non monotonically increasing dts to muxer in stream 0: 8 >= 8

It seems they are caused by VRD because they always appear around the cut points no matter where I place the cut markers in the program and even if the source file has no errors.

I also noticed this only happens with files recorded from specific channels, e.g all recordings from FOX Life have this problem while these from Moviestar - not.
What version of VideoReDo are you using (Help>About)?
 
Top Bottom