Ok. I tested some video rendering times. And it's just plain stupid.
Earlier today @Greg_Gauthier included the following in a post.
"One 30 minute 720p video, with almost NO visual activity on it at all (4 terminals with text on them) is going to take 55 minutes to render on my little old laptop here. Whereas, on the Lenovo desktop, even with that cranky old NVidia GPU, this would have taken 12 or 14 minutes to render."
Rendering 720p videos... man. I do that a lot. And the time it takes to render them -- on my Framework laptop running Linux -- has been an almost constant annoyance.
So I ran a test today.
I made a simple Kdenlive project. With a roughly 10 minute video clip. Two small images (at the beginning and end for roughly 20 seconds each). A replaced audio track (no cuts). All at 720p.
Rendered that same thing on three configurations (all using a latest Kdenlive available):
- Framework 13 running Debian
- Microsoft Surface Go 1 running Ubuntu
- Microsoft Surface Go 1 running Windows 10
All using software rendering (because GPU rendering is flakey as heck in Kdenlive anyway).
The results were absolutely ridiculous. And annoying.
The Framework 13 running Debian rendered the project in roughly realtime (about 10 minutes).
The Surface Go running Ubuntu took around 15 minutes.
The Surface Go running Windows 10 took around 8 minutes.
Yeah. Windows, even on the underpowered gen 1 Go, waaaaay outperformed Kdenlive on Linux on a crazy faster system.
And, on the same Go, rendering under Windows was roughly twice as fast as under Ubuntu.
Which makes me wonder... WHY? It makes no sense to me. And what would the results be with the Framework 13 if I were to install Windows 10 on there (I know... blasphemy).
Again, none of these results were with complex projects. And all using a software encoder (no GPU help). Would be interesting to see how the GPU rendering would differ between OS's.
