https://bugs.kde.org/show_bug.cgi?id=361360
--- Comment #8 from Jesse <jesse.dub...@gmail.com> --- A little bit more testing (if it helps) shows that there's much more CPU load when playing clips overlaying each other with track compositing, than playing a clip that doesn't have another clip over or under it. In other words, during playback over a section in the timeline where there's more than one clip present on multiple tracks, my system monitor shows a heftier CPU load. Playing a single clip in a single track results in almost no CPU load at all. Interestingly enough, when I disable track compositing and put an Affine or composite transition in between two clips on the timeline, the CPU STILL revs up. Once the timeline position cursor passes the Affine/composite transition, things start to smooth out to a perfect 24fps, and the CPU goes back to minimal. So, with the current build from the kdenlive-master ppa (May 17, 2016 build) using track compositing OR Affine/composite transitions with track compositing disabled produces the same result: considerable drop in playback speed/framerate, and the CPU revs up, signifying a greater work load (one of my 8 CPU cores goes to 100% during this time). Hope that helps. I feel like this is a pretty significant bug. The last couple of weeks has shown some EPIC feature additions to the Kdenlive master build, but if there's still an underlying issue of playback speed during basic editing functions, I feel like progress is being somewhat crippled. Not a complaint at all, just trying to offer some helpful advice to keep the solid foundation solid, you know? -- You are receiving this mail because: You are watching all bug changes.
