2.39 erroneously reporting "failed" encode #153

Open
awgiedawgie opened this Issue Dec 24, 2016 · 9 comments

Projects

None yet

3 participants

@awgiedawgie

The encoder is reporting that it failed, but the resulting file appears to have been successful. It is the right length, has the correct number of frames, the audio is properly synced to the video... everything. I have only tried encoding 2 files with ver. 2.39, and got the same result with both files.
2016-12-23

Brave Witches - 11 (1).txt

@liracobopu

Same. All of my successful encodes are being marked as Failed.
image

@RandomEngy
Owner

What does it say in the encode log?

@RandomEngy
Owner

It looks like the HandBrake engine is reporting it as a failed encode. Do you have the same behavior in HandBrake?

@awgiedawgie
awgiedawgie commented Dec 27, 2016 edited

Never used HandBrake on its own, so I don't know.

UPDATE: Installed HandBrake GUI and encoded with it. Got the same result (libhb: work result = 4) as in VidCoder. There is a line that is in both the HB log and the VC log that was never present in VC2.38 and before:
2016-12-26 1
I see the VidCoder logs (both mine and the one from the other user above) also have another error message immediately following the one I highlighted in the HB log.

@awgiedawgie

FYI, the problem persists in 2.40 Beta

As you said, it appears to be an issue with HandBrake itself, so I know it's not going to go away until they fix it on their end.

@RandomEngy
Owner

I released 2.41 Beta, which uses HandBrake 1.0.0 core. You could give it a try with that version.

@awgiedawgie

Hadn't seen the 2.41 update yet. I'll give it a try, but I'm not holding my breath, since it was the HandBrake 1.0 GUI that gave me the error result I posted on Monday.

@RandomEngy
Owner

Ahh that's right. I don't expect it to be fixed until HandBrake does the fix then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment