Beta 2.65 says over 2500 hours to complete converting

MCEBuddy Version: 2.65 Beta (Nov. 7)
Operating System: Windows 10 Enterprise
Summary of the problem:
Hi, I’m not sure if this is a bug or that I should try the 2.64 stable version. I upgraded from 2.57 with a new 1 year license! v2.57 for years was working perfectly which I uninstalled.

After about 25 minutes using the new Beta 2.65 Premium version, the window says over 2800 hours to complete converting…

I suspect my old XEON server with 64gb RAM and 2 processors is not compatible with this version. I’ll try the non beta 2.64 version or a more recent computer to confirm. But I need MCEBuddy to be on the XEON.

Screenshots:

No logs yet, still running and log is 0 bytes.

Attach the partial log (whatever is there so far).

I’ll do it again, right now it’s 0 length and empty text after the video finishes converting but it’s not playable past the first few Seconds. Until then the log while converting had to do with ‘Handbrake failing’ and the log was only a few lines.

Only so far: in the main log (the video file log converting is empty):
mcebuddy.log (138 Bytes)

Also, I tried on my laptop (different computer) both the Stable version 2.64 and the Beta version 2.65; same issue both do not work on the laptop :frowning: .

While waiting for the 2.65 “4th” test to complete on my XEON Server, I installed the 2.57 version on my laptop and it’s working like it always did:

Will need the actual conversion log, make sure your log is set to Debug in the Settings → System Settings page

Can’t tell anything without logs, it’s like a guess with no pointer. If I were to guess with no pointer I’d start by saying turn off hardware encoding in your conversion task expert settings. That’s usually 99% of problems. Again as for resolution can’t say without logs.

The conversion log was empty and hardware acceleration was turned off in the last 4 out of 5 tests.
image

I figured it out! I had to delete these 4 from my %HOMEPATH%

I suspect it was the comskip.ini as I was using a paid comskip.exe from long ago. But it could’ve been 1 of the .conf files. But as we say, as ;long as it’s fixed no need for a root cause analysis (RCA)!