Video file damage or codec problem?

[edharris]

Everything ok reading the MP4 file using VLC or anything else.
I tried multiple conversions using Handbrake, HQs, lowQs, media freezes (audio and video) while time still running out, then recover after 2 minutes of this.

Any idea?

thx

[jagabo]

Check your CPU temperatures while encoding.

[edharris]

Yes, abnormally high: +10°C/+50°F
Though all fans max level and nothing but Handbrake using CPU...
What should I do?
Thanx jagabo

[jagabo]

Yes, abnormally high: +10°C

You mean 10 degrees over ambient? That's not a problem unless your room is at 90 degrees!

If I misunderstood, open up the computer and verify all the fans are working, especially the fan on the CPU cooler. If the CPU cooler has gotten filled with dust, blow it out with a can of compressed air.

[edharris]

Sorry, my fault.
Made some more checks
Room temperature today around 21°C/70°F
CPU temperature after 7min (stop benchmark then) 62°C/143.6°F
Core 76°C/168.8°F

[jagabo]

62 C is getting close to the max for that CPU, ~72 C. Does the temperature continue to rise if you keep encoding?

[edharris]

62 C is getting close to the max for that CPU, ~72 C. Does the temperature continue to rise if you keep encoding?

It seemed to reach a peak around 10min mark, back and forth from 68°c to 67°c. Conversion over. I got other files to convert a little bit longer, ~20min.

Here is the log of the conversion
https://files.videohelp.com/u/294643/activity_log3800.txt

[jagabo]

The CPU is supposed to throttle back before it overheats. But I've seen reports from many people who's computer crashed or locked up instead.

There are other possibilities. A corrupt source file, for example.

[edharris]

There are other possibilities. A corrupt source file, for example.

How can I check this up?

[jagabo]

ffmpeg can detect some errors. Put this in a batch file:

ffmpeg -v error -i %1 -an -c:v rawvideo -f null -
pause

Then you can drag/drop videos onto it to build an error report. If ffmpeg detects any errors you will see them in the CLI window.


[Attachment 53125 - Click to enlarge]

No detected errors doesn't guaranty the file is perfect, just that ffmpeg didn't report any errors.