So much has been reported about GPU acceleration that much is misunderstood.
If GPU acceleration is enabled and properly configured, you shouldn’t think that ONLY the GPU does all the computing work, like with the 3D program “Blender”.
The Shotcut internal GPU acceleration only calculates the codec calculation with the rendering process.
Filters, effects, transitions are still calculated by the computer CPU.
A big disadvantage of the activated GPU acceleration is that the final result is bad or even rendered incorrectly.
It is calculated faster, but the file is disproportionately larger.
Read the FAQ (link at the top of this page when you scroll all the way up) about how GPU is used and not. Then, see all those video tracks in your screenshot. The time spent working on the video on the CPU is much greater than time spent in GPU encoding.
His GPU is obviously idling… apart from a spike for something unrelated to Shotcut.
On Windows I am getting from 30% to 100% utilization with nvenc on my GT 640.
On Hackintosh on the same computer I am getting 0% GPU utilization with h264toolbox (Adobe Premiere/Media Encoder uses my GPU from 30-60% depending on encode).
On “kosher MacBook Pro” with GT7xxM I am getting the same 0% GPU utilization with h264toolbox (Adobe Premiere/ME uses that GPU about same 60%).
Bottom line: on MacOS h264toolbox appears not to be using GPU most, if not all, of the time; on Windows, thanks to NVENC, Shotcut encodes about 150% faster vs. same encode on OSX.
well, it doesnt matter, its fast anyway using my CPU.
ive read the FAQ and i think my video is not using any special effect or anything that need my GPU to cover, because i saw the very first time it render, my GPU spike up, then idle. i think the GPU render it all in front, then go to next part for CPU.
as i said, it doesnt matter. for 10 minutes videos, i can render for 4-7 minutes, and im happy with that.