Sergey Berengard

Hi Leonardo,

Thanks for your informative reply!
I figured it out by looking into it exactly like you said, stopping the service and running the client in console mode instead.
What I found was that the FFmpeg job was running with logging level set to 100 causing it to spit out every tiny bit of tracing and debugging information during the transcoding process. All that overhead was what was causing it to run x3 times slower.

So I modified the FFmpeg python template to have it run with logging level 16, which would only print out errors if they occur, otherwise FFmpeg runs silently without any unnecessary overhead. And that totally worked!
Just a thought, but maybe it had also to do with the fact that I was using QSV for FFmpeg’s hardware acceleration, which works on the CPU, causing it to jam…? Will see how it compares when I switch to CUDA.

But it works now. Thanks for your all your help!
Cheers!

-Sergey.