Skip to content
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

Handbrake issue with referance frames exceed max #674

Closed
ausrobperth opened this issue Apr 14, 2017 · 6 comments
Closed

Handbrake issue with referance frames exceed max #674

ausrobperth opened this issue Apr 14, 2017 · 6 comments
Assignees
Milestone

Comments

@ausrobperth
Copy link

ausrobperth commented Apr 14, 2017

Please describe the problem or feature request in detail:I have put the same video through both Handbrake and Any Video Converter for the purpose of adding Subtitles and ability to play on DVD player.

Prefer Handbrake as subtitles can be hard (burned in) or soft (switchable on or off)
The conversion runs OK through both programs but the Handbrake version now has problems with the video breaking up.
Wondering if there are settings in Handbrake that may stop this happening
Following link is to folder with 3 small video clips
m2ts is the original , mkv is the handbrake (with problems) and mp4 is the AVC version (no problems)
The picture breaks up when the character stands up from the sofa
I have also used mp4 through Handbrake and problem remains

What are the steps to reproduce this problem: Check the 3 clips from Link Below

What version of HandBrake you are running:latest

What operating system and version and you running (e.g. OSX 10.11, Windows 7, Ubuntu 14):Windows 7

Was there any error message or error dialog, if so please detail or provide screenshots: No

Please provide the full activity log for the encode or scan attempt. You may attach the log as a file, post a pastebin URL to the log, or place the log inline below:No

Place your log in-between these back-ticks
Quote from 3rd party

ffmpeg complains at that point:
[h264 @ 0000000000436120] number of reference frames (0+5) exceeds max (4; probably corrupt input), discarding one
[h264 @ 0000000004b0c700] number of reference frames (0+5) exceeds max (4; probably corrupt input), discarding one
ffmpeg can handle this error but it seems HandBrake does something special which results in a visible problem. Report to HandBrake developers.
https://github.com/HandBrake/HandBrake/issues

A workaround would be to use HW decoding but DXVA got removed at 1.0 because it was too buggy. I believe QuickSync decoding is activated by default so I assume your PC doesn't have it. But you can check in settings to be sure. (Requirements are listed there.)<
3 small clips are here
https://www.dropbox.com/sh/63r0rtqj26vto2e/AAAI75R504Pu9H8RpmRaD9rZa?dl=0

@sr55
Copy link
Contributor

sr55 commented Apr 14, 2017

Your dropbox link doesn't work. You also need to post a full activity log.

HandBrake doesn't use ffmpeg so that's a moot point. We use libav and it looks like it's complaining bout your source being broken.

We can submit a file upstream to them and they can decide whether to add a workaround or leave as-is.

@sr55
Copy link
Contributor

sr55 commented Apr 14, 2017

Can you also do me a favour and try a nightly build to see if that helps

@sneaker2
Copy link

The link text is working but the link got messed up somehow.
https://www.dropbox.com/sh/63r0rtqj26vto2e/AAAI75R504Pu9H8RpmRaD9rZa?dl=0

Same problem (picture breaks at 00:27) with HandBrake-20170414-5dd46e3_x86_64-Win_GUI.exe nightly. Activity log in attachment.
log.txt

@jstebbins
Copy link
Contributor

Thanks for the sample. There is an error in the file at that position, but libav seems to be handling it poorly. I'll look into it and see if I can find a way to improve behaviour.

@jstebbins jstebbins self-assigned this Apr 14, 2017
@ausrobperth
Copy link
Author

Thanks sneaker2
Thanks jstebbins

@bradleysepos bradleysepos added this to the 1.2.0 milestone Jun 14, 2017
@sneaker2
Copy link

Problem isn't there anymore in latest nightly HandBrake/libav. (Don't know when it was fixed.)

@sr55 sr55 closed this as completed May 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

5 participants