https://bugs.kde.org/show_bug.cgi?id=389624
--- Comment #9 from John Bell <bell...@gmail.com> --- I have got it so it created _new.kdenlive which has the original clip with markers at the scene changes it has found (a little more sensitive than I would expect, but that is an error in the right direction) but without splitting the scenes as it used to do with earlier versions of Kdenlive. But I can live with this as a workaround. New versions is being promised later this year - I hope this can be fixed in the base Kdenlive including the scene split. Somewhere they need to give guidance on making the project frame rate match the clip frame rate as it was not obvious to me at the time. Thanks Brian, John On 1/30/19 1:24 PM, John wrote: > Thanks Brian. Where do I find the 'shot change list'? > > From your other email I think part of my problem may have been not > having the project frame rate match the clip frame rate, but fixing > that has not been a complete fix - still trying to make it work. > > I tried your script and again cannot find the output from it but I am > still looking ... > > John > > On 1/30/19 8:24 AM, B Stewart wrote: >> https://bugs.kde.org/show_bug.cgi?id=389624 >> >> B Stewart <every-...@outlook.com> changed: >> >> What |Removed |Added >> ---------------------------------------------------------------------------- >> >> CC| |every-...@outlook.com >> >> --- Comment #6 from B Stewart <every-...@outlook.com> --- >> Created attachment 117730 >> --> https://bugs.kde.org/attachment.cgi?id=117730&action=edit >> screen shot after running my script >> >> This is also a problem for me, and it seems to have been around for a >> few >> years! >> >> I'm currently using kdenlive 18.08.2 on Ubuntu 18.08 >> >> I have a temporary workaround that works for me. >> >> >> If the (Save result in clip metadata) is checked from (Clip >> Jobs/Automatic >> scene split) then the clip is analysed (can take a few minutes to >> complete) and >> the scene change frames are available as a "shot change list". >> The number between each ";" and "=" is the frame number where the scene >> changes. >> This info is also available in the saved .kdenlive file. >> >> I have written a Python3 script (about 70 lines of code) which reads the >> kdenlive file and creates a copy of it with "guide marks" at each >> shot change. >> This can be opened with kdenlive, which then shows where all the shot >> changes >> occur. >> >> It is a simple workaround to a problem that seems to have been around >> for ages. >> > -- You are receiving this mail because: You are watching all bug changes.
