https://bugs.kde.org/show_bug.cgi?id=491257
--- Comment #9 from Martin Bolding <martin.bold...@gmail.com> --- 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.
