Open tmo1 opened 4 years ago
Yeah, this was on the wontfix list for a long time, but this will be changed at some point in the future.
Currently Flowblade keeps producing frames at Project fps even when playback is paused, but now that we have async rendering for some project resources we are losing some performance here not just additional power usage.
Okay, thanks. I've currently given up on Flowblade since I realized that since all I really want to do is trim and concatenate video clips, I really want a solution that doesn't involve rendering the output, so I've moved to a simple ffmpeg cli based workflow, but I'll give Flowblade another try if I ever need to do any real editing.
Is there any progress on this issue? Just waiting Flowblade to be done producing frames seems futile. Having fans run at full speed even on idle is very annoying. Flowblade is otherwise great but I can't currently justify this waste of electricity.
Appreciate the explanation. Also noticed this issue but at 60-70% of the CPU on KDE Neon.
Hi,
I'm new to Flowblade (2.4.0 on Debian unstable, from the distro package), and I'm puzzled by its high idle CPU usage. I'm running on a W550s with an i7-5500U @2.4 GHz, and while I understand that this is not the ideal video editing machine, I don't understand why the program uses so much CPU while doing nothing. I simply run 'flowblade' without opening any project or importing any files, and Flowblade uses about 45% of a CPU core, and remains at that usage level indefinitely. Is this normal?