https://bugs.kde.org/show_bug.cgi?id=361360
--- Comment #36 from Jesse <jesse.dub...@gmail.com> --- I can definitely empathize with the technical struggles behind trying to make multiple tracks with clips over them playing back smoothly. I once looked at the code out of curiosity (with no programming background), and I near threw up from the confusion. I paid a therapist for a week to counsel me through the trauma. :) Whatever path you think will get the job done best, I'm all for it. From the end user's perspective, all I can say is this: the expected use and experience from the timeline is to use any number of clips (video, .png, title) in any number of tracks - overlapping each other or not - properly showing transparency on each one, and experiencing smooth playback (if their machine/CPU/GPU with movit can handle it). Having effects/filters/etc. on clips is another matter entirely, and you've given a GREAT remedy with the Preview Render feature -- truly a fantastic solution to the framerate drop when playing back clips with FX. I've used it on multiple projects, already, and it's saved me a lot of time. I know using the composite and Affine transitions over clips may seem like the best course because it's already established, but I've never really been for the Affine or composite transitions since my first encounter with Kdenlive (in the form of yellow bars) for two reasons: 1. Because it really makes the term "transition" confusing. Transitions should be moving FROM one clip TO another; one ending, and the other beginning. At least, that's how the term is used in the Industry. Using a "transition" simply to overlay one clip over another doesn't, to the non-uber-techie end user, make sense. And 2. It's making the user take an extra step to do something that they're expecting the editor to do automatically. Other editors you don't have to do anything to make sure that the transparency in any kind of clip shows normally. It's one of the reasons I was - and am - for composite tracks in the first place: it makes the timeline behave like one would expect. If having the "composite transition" built into the timeline would allow for smooth playback, using multiple clips (3 or more) over each other with proper transparency, would show in the monitor exactly how the rendered video would look, and would allow for real-time playback, then I think that would be a great decision. :) Alright, I won't beat a dead horse about it. I'll keep running some more tests from the git master version. Let's keep working to find an elite solution, you know? -- You are receiving this mail because: You are watching all bug changes.
