FFmpeg Batch 2.5.4 has started randomly crashing

Free all in one audio/video ffmpeg batch encoder

Brought to you by: eibol

FFmpeg Batch 2.5.4 has started randomly crashing

Forum: General Discussion

Creator: Ronald J Kienle

Created: 2021-10-20

Updated: 2021-10-21

Ronald J Kienle - 2021-10-20

I love this program and rely on it every day. I upgraded to the latest version about a week ago and everything was OK until yesterday. Now the program randomly stops working and crashes in the middle of an encode. It stopped working yesterday morning right at the end of a lon queue of files. It had been running all night. Now every time I try to encode something it fails somewhere through the first file.....and it has happened on several different files so I do not thing the input is the problem. I have included the log file.

Thanks

ff_batch.log

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Abel - 2021-10-20

Hi, I don't think it has anything to do with latest update., ffmpeg version is the same (4.4).

I see you use Nvidia card for encoding (hevc_nvenc). Maybe a driver update changed something

Which parameters are you using? The log file displays some warnings about deprecated options.

Are you using sequential or multi-file encoding? What is your selected encoding priority?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ronald J Kienle - 2021-10-20

I updated the nVidia driver two months ago but yesterday was the first problem I've had. I have probably encoded over 500 files, mostly movies with my current settings and versions of everything (nVidia driver, ffmpeg, and Batch).

I do not understand what a deprecated option is so if you explain I would like to make adjustments to correct. Pardon me but I am still in learning mode with ffmpeg and I am experimenting with options that are a hodge podge from various sources.

My settings are as follows:

-c:v hevc_nvenc -vf "fieldmatch,bwdif=mode=0:deint=1,decimate,format=yuv420p10le" -c:a copy -c:s copy -preset hq -rc constqp -rc-lookahead 60 -spatial_aq 1 -temporal_aq 1 -nonref_p 1 -cq 26

The first Batch crashed I was running it multi-file mode and I was away from my computer and last night it happened in sequential mode. Since it first happened I have not been able to make one successful encode and yesterday morning was my first crash. I had made no changes to my machine in that one day either because the night before I had run the same files through Batch with slightly altered settings.

I leave the encoding priority alone.

Thanks

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ronald J Kienle - 2021-10-21

Is there more than one deprecated option. I found one testing a file a little while ago. I surmise that the following:

[hevc_nvenc @ 0000007d685c64c0] The selected preset is deprecated. Use p1 to p7 + -tune or fast/medium/slow.

I surmise this is referring to the hq preset which upon reading it appears has been replaced with different options in newer builds of ffmpeg?

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Abel - 2021-10-21

Deprecated parameters are usually ignored, so they should not cause any problem. This is going to be tough to solve, I can't reproduce your issue., I tested your parameters successfully with a couple of files (actually h264_nvenc). Something in your system, an operating system update, driver updated, could be the cause.

For diagnostic purposes, I would try encoding with ffmpeg command line. If problem occurrs again, you may try a different ffmpeg version. Also, do not run any other application during encoding.

Last edit: Abel 2021-10-21

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Ronald J Kienle - 2021-10-21

I solved the problem with Batch crashing. It was user error. My app that tells me how much hard drive space I have on each drive (I have 14) was stuck and I did not notice. My target drive was almost full. Sorry about that, but it led me to the problem with deprecated options.

Turns out the deprecated parameter was the preset hq. I tested it with the new parameters. The only problem is I am getting backwards results. P1 is faster then P7 and P1 is supposed to be the highest quality and slowest......it is slower by a bit but P1 produces a file 50% larger so now I am a little confused. Any ideas. The files come out fine. I just have way smaller files than I did with the same settings before I updated to the newest nVidia driver.

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Abel - 2021-10-21

Good to know there's a logical cause for the crash. Maybe a good idea to add some destination drive available space monitoring.

Regarding file size/quality, it makes sense that P1 produces a bigger file, generally higher bitrate = higher quality. But this is always subjective, I would stick with the configuration that produced a satisfactory quality/bitrate ratio.

I don't think that new drivers can reinvent the HEVC encoding as to change quality in a big way.

Cheers

If you would like to refer to this comment somewhere else in this project, copy and paste the following link:

Log in to post a comment.