[kdenlive] [Bug 364012] git master: optimization for loading existing preview render chunks may conflict with change clip invalidation

https://bugs.kde.org/show_bug.cgi?id=364012 Wegwerf changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED

[kdenlive] [Bug 364012] git master: optimization for loading existing preview render chunks may conflict with change clip invalidation

https://bugs.kde.org/show_bug.cgi?id=364012 --- Comment #3 from Wegwerf --- Probably some project token, sich as a hash, but can be even simpler, would suffice. It gets updated with each project edit after a save. The cache, in turn, remembers the most recent project token

[kdenlive] [Bug 364012] git master: optimization for loading existing preview render chunks may conflict with change clip invalidation

https://bugs.kde.org/show_bug.cgi?id=364012 --- Comment #2 from Jean-Baptiste Mardelle --- I will check this problem tonight. Regarding your second comment, currently we proceed like this on project opening: We check the project file's last save date/time and compare it with

[kdenlive] [Bug 364012] git master: optimization for loading existing preview render chunks may conflict with change clip invalidation

https://bugs.kde.org/show_bug.cgi?id=364012 --- Comment #1 from Wegwerf --- By the way: on the other hand, reloading a project after a full preview render starts with the old preview rendering zone being red. Kdenlive does not pick up the existing preview chunks. Could that