https://bugs.kde.org/show_bug.cgi?id=365887

            Bug ID: 365887
           Summary: git master: internally added (mix/composite)
                    transitions getting out of sync with project
           Product: kdenlive
           Version: unspecified
          Platform: Other
                OS: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: Effects & Transitions
          Assignee: vpi...@kde.org
          Reporter: wegwerf-1-...@gmx.de

I've written a Kdenlive project XML analyzer (which is nothing more than a
tricky XSLT stylesheet at this time) and put several of my both older and newer
Kdenlive projects to the test.

There is basically no project of mine where the internally added transitions
match the project's timeline track setup. Internally added audio mixers usually
are mostly fine, with the exception of the mixer for the topmost track missing
(yet this is been fixed recently, thank you!). However, I still see several
projects where some mixers are missing and some are duplicates ... and this in
particular explains the erroneous behavior of some of my older projects.

But when it comes to internally added compositing transitions then things get
out of hand. A recent project I just started some days ago has 234(!)
internally added composite transitions for only 9 timeline tracks.

I would thus like to propose that Kdenlive does some sanity cleanup whenever
loading a project. In particular, all existing internally added transitions
(both mixers and compositors) should be removed and only then all necessary
internal transitions be built up right from the ground according to the current
track setup.

This would have several advantages:
0. no more fornicating internally added compositing transitions, 234
compositing transitions for only 9 tracks surely shows that this is quickly
getting out of control.
1. after loading all projects return to a well-known (minimal) state. If in
doubt, save and reload.
2. no more difficult to track mixing or compositing issues and bug reports.
3. automatic upgrade to new compositors, qtblend in particular.
4. easy change between movit-based and cpu-based internal compositors.

Reproducible: Always

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to