Running latest version of Handbrake on Windows 10.
I've been trying to convert files via Handbrake lately but have not been entirely successful. I use the same custom preset for everything:
Video
- H.264
- Framerate: same as source
- Variable framerate
- Constant quality, 17ish
- x264 preset: Medium
- x264 tune: Film or Animation
- H.264 profile: High, level 4.1
I passthru the audio. MKV container. I've tried a VC-1 (in MKV container) source as well as ripped DVD VOB files as well. What happens is that Handbrake will either crash outright (as evidenced by my latest attempt; log here: http://pastebin.com/LGr3MWd0) or it will go a bit of the way through and then flash to 100% complete with a fraction of the "completed" file available.
Any ideas what's going wrong?
Handbrake "doesn't finish" encode/crashes
Forum rules
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
An Activity Log is required for support requests. Please read How-to get an activity log? for details on how and why this should be provided.
-
- Posts: 13
- Joined: Sat Jun 27, 2009 9:45 pm
Re: Handbrake "doesn't finish" encode/crashes
Do you have the windows crash report from the "outright crash"? It may have clues to why it is failing.
-
- Posts: 13
- Joined: Sat Jun 27, 2009 9:45 pm
Re: Handbrake "doesn't finish" encode/crashes
Maybe. Where do I find it?
-
- Posts: 13
- Joined: Sat Jun 27, 2009 9:45 pm
Re: Handbrake "doesn't finish" encode/crashes
Googled it (should've in the first place, duh); found them. Two logs:
ERROR (source: Application error):
Faulting application name: Handbrake.exe, version: 1.0.2.0, time stamp: 0x5884e843
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000001
Faulting process id: 0x2290
Faulting application start time: 0x01d28a111d1aa6e8
Faulting application path: C:\Program Files\Handbrake\Handbrake.exe
Faulting module path: unknown
Report Id: a66d842b-9adb-4989-af58-fc7f5f9813ce
Faulting package full name:
Faulting package-relative application ID:
ERROR (source: .NET runtime):
Application: Handbrake.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 0000000000000001
ERROR (source: Application error):
Faulting application name: Handbrake.exe, version: 1.0.2.0, time stamp: 0x5884e843
Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0xc0000005
Fault offset: 0x0000000000000001
Faulting process id: 0x2290
Faulting application start time: 0x01d28a111d1aa6e8
Faulting application path: C:\Program Files\Handbrake\Handbrake.exe
Faulting module path: unknown
Report Id: a66d842b-9adb-4989-af58-fc7f5f9813ce
Faulting package full name:
Faulting package-relative application ID:
ERROR (source: .NET runtime):
Application: Handbrake.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 0000000000000001
-
- Posts: 13
- Joined: Sat Jun 27, 2009 9:45 pm
Re: Handbrake "doesn't finish" encode/crashes
Are you able to provide a short / small sample file?
I suspec it's another libav decoder bug. v12.0 was a little buggy.
I suspec it's another libav decoder bug. v12.0 was a little buggy.
-
- Posts: 13
- Joined: Sat Jun 27, 2009 9:45 pm
Re: Handbrake "doesn't finish" encode/crashes
So, I've spent the last many hours running through a bunch of "test runs." I kept the same encoding profile as above, but tried different "speeds" from "ultrafast" through "slower." When I was on 0.10.2 I noticed that I would only fail on medium, but had success on other speeds. I tried that with the most recent release, and interestingly enough I successfully encoded everything, even on medium, though I tried it last.
So I suppose I'll hang back and see what develops, but I have another interesting issue: the files all vary in size. Same source, same length at the end of encoding, but they've all got varying overall bitrates at the same RF. Is this normal? Ultrafast turned out 29.4Mbs, very fast only 16.9, and medium 20.4.
So I suppose I'll hang back and see what develops, but I have another interesting issue: the files all vary in size. Same source, same length at the end of encoding, but they've all got varying overall bitrates at the same RF. Is this normal? Ultrafast turned out 29.4Mbs, very fast only 16.9, and medium 20.4.