Using hecv_nvenc encoder in the supplied ffmpeg executable "FFMPEG batch convertor for Windows" results in considerably longer run times for the encoder to do it's job compared to running the same encoder on the command line, all other parameters being the same. Identical FFMpeg executable. Any reason as to why? Almost double the time for an encode using the gui.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Abel, I'm sorry but I do not know where to look for a session log on Windows 10. If you could advise I would be happy to put everything together and send it to you for appraisal. [session log, parameters used, gpu used, method sequential, etc]
Vic
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
By the way, I have tried about 8 different gui's for ffmpeg and yours is the best of all of them for nooby's and experts alike. Scripts are maybe simpler and\or faster but not as error proof as yours.
Vic
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry for the delay, I am using one file at a time and then reloading the program fresh for the next file.
I believe I have found the problem. I became aware of a program called "mediainfo" and started looking at the source files I am trying to encode. Some files take more computer cycles to decode than others before the gpu can encode. I have two Nvidia Cards installed and the program is sometimes selecting one over the other. It makes a huge difference so I'm deep diving into ffmpeg command settings in order to always select the faster of the gpu's.
I believe that's been the problem all along. I'm sorry for not doing more trouble shooting before raising a false alarm. When I have everything configured correctly this program is a huge time saver.
Sincerely, Vic
Last edit: victor alger 2022-09-08
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for debugging and the detailed report. It will be useful in the future.
I hope you find the right parameters to choose your preferred gpu encoder.
Cheers
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Using hecv_nvenc encoder in the supplied ffmpeg executable "FFMPEG batch convertor for Windows" results in considerably longer run times for the encoder to do it's job compared to running the same encoder on the command line, all other parameters being the same. Identical FFMpeg executable. Any reason as to why? Almost double the time for an encode using the gui.
No reason that I know, what are you using, sequential or multi-file? What parameters?
Can I see a session log file?
Abel, I'm sorry but I do not know where to look for a session log on Windows 10. If you could advise I would be happy to put everything together and send it to you for appraisal. [session log, parameters used, gpu used, method sequential, etc]
Vic
By the way, I have tried about 8 different gui's for ffmpeg and yours is the best of all of them for nooby's and experts alike. Scripts are maybe simpler and\or faster but not as error proof as yours.
Vic
Thanks, by now the most important thing is to know if you are using sequential or multi-file, and your video card model.
Okay, I always use sequential and the video card is a Nvidia GeForce RTX 2070 32 gig memory.
Vic
Last edit: victor alger 2022-08-29
How many files do you encode in sequential mode, is it big files, or many small files?
Hav eyou tried at settings the 'Quick file listing' mode?
Sorry for the delay, I am using one file at a time and then reloading the program fresh for the next file.
I believe I have found the problem. I became aware of a program called "mediainfo" and started looking at the source files I am trying to encode. Some files take more computer cycles to decode than others before the gpu can encode. I have two Nvidia Cards installed and the program is sometimes selecting one over the other. It makes a huge difference so I'm deep diving into ffmpeg command settings in order to always select the faster of the gpu's.
I believe that's been the problem all along. I'm sorry for not doing more trouble shooting before raising a false alarm. When I have everything configured correctly this program is a huge time saver.
Sincerely, Vic
Last edit: victor alger 2022-09-08
Thanks for debugging and the detailed report. It will be useful in the future.
I hope you find the right parameters to choose your preferred gpu encoder.
Cheers