[kdenlive] [Bug 469070] Project Loads with Incorrect Clips in Timeline
https://bugs.kde.org/show_bug.cgi?id=469070 Martin Bolding changed: What|Removed |Added CC||martin.bold...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 491257] Incorrectly identifying imported clips as having variable frame rate
https://bugs.kde.org/show_bug.cgi?id=491257 --- Comment #4 from Martin Bolding --- I have confirmed this is also a problem with 24.08.0. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 491257] Incorrectly identifying imported clips as having variable frame rate
https://bugs.kde.org/show_bug.cgi?id=491257 Martin Bolding changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 491257] New: Incorrectly identifying imported clips as having variable frame rate
https://bugs.kde.org/show_bug.cgi?id=491257 Bug ID: 491257 Summary: Incorrectly identifying imported clips as having variable frame rate Classification: Applications Product: kdenlive Version: 24.05.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: martin.bold...@gmail.com Target Milestone: --- SUMMARY Versions 24.5.1 and 24.5.2 of kdenlive on Win 64 incorrectly identify imported clips as having variable frame rate. STEPS TO REPRODUCE 1. Open a new project using kdenlive > 24.5.0 2. Import a stitched GoPro Fusion clip (which has 5504x2752 pixels @ 23.976 frame rate) OBSERVED RESULT 3. Warning dialogue about clip having variable frame rate, and therefore unsuitable for editing/use. Convert clip yes/no. EXPECTED RESULT Successful import of clip SOFTWARE/OS VERSIONS Windows: 11, build 23H2 22631.3958 ADDITIONAL INFORMATION Using GoPro Fusion Studio 1.4 to stitch raw clips for import into kdenlive. I can supply sample clip for diagnostics if required. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 491257] Incorrectly identifying imported clips as having variable frame rate
https://bugs.kde.org/show_bug.cgi?id=491257 --- Comment #2 from Martin Bolding --- (In reply to Jean-Baptiste Mardelle from comment #1) > Could you provide a short video sample so that we can test this further ? 1sec video is c. 130Mb, so provided via Dropbox Link. I have reconfirmed that 24.05.0 is OK, but 24.5.1 and 24.05.2 give an error. https://www.dropbox.com/scl/fi/5p4wnt4j875foeu6cgfkv/TEST.mov?rlkey=cea13t1ac4wp39uvguhsle42a&st=731or6qx&dl=0 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 491257] Incorrectly identifying imported clips as having variable frame rate
https://bugs.kde.org/show_bug.cgi?id=491257 --- Comment #5 from Martin Bolding --- ...and 24.08.1 -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 491257] Incorrectly identifying imported clips as having variable frame rate
https://bugs.kde.org/show_bug.cgi?id=491257 --- Comment #7 from Martin Bolding --- That doesn't alter the fact that these files are NOT variable frame rate, whether MediaInfo says so or not. I have tested with version 24.12.1 of kdenlive and it flags a warning that the clips are variable frame rate but seems to let me continue to use them, so I guess that will have to do for now. Your response does not explain how versions of kdenlive prior to 24.05.1 were quite happy to process these files but subsequent versions are not. I do appreciate that this difference may be caused by a change to a software component over which you do not have change control. However, it is a significant inconvenience to me as a long time kdenlive user. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 491257] Incorrectly identifying imported clips as having variable frame rate
https://bugs.kde.org/show_bug.cgi?id=491257 --- Comment #9 from Martin Bolding --- Thanks for that additional info. I didn't realise it was an issue reported with other GoPro products or that it was potentially an issue with MLT not reporting that it had determined that the file had a variable frame rate. As you may know, GoPro fusion footage has to be "stitched" (using "GoPro Fusion Studio") to create a single .mov (or .mp4) file for each clip prior to futher editing. Opening the "raw" front and back camera files, MediaInfo reports a constant frame rate of 23.976 but, after stitching, (I agree that) the reported frame rate *mode* is "variable" (despite the stitching process being spatial not temporal). Possibly a bug in the GoPro code or its subcomponents (which hasn't been changed since 2018). My issue may well be that Fusion Studio is incorrectly flagging the output as VFR, a fact which has hitherto been ignored (or at least not reported by) MLT. As long as I can continue to use kdenlive to edit my footage (albeit with a warning about clips being flagged with variable frame rates), I'll be happy. I have certainly never noticed any judder on the output from kdenlive with frames being dropped, repeated or interpolated to give me a constant 23.976 output. I'll maybe stick with 24.05.0 for as long as I can. I definitely DON'T want my clips to be temporally converted on input. Thanks again. -- You are receiving this mail because: You are watching all bug changes.
