[kdenlive] [Bug 389624] Automatic scene split does not work in newer versions
https://bugs.kde.org/show_bug.cgi?id=389624 B Stewart changed: What|Removed |Added CC||every-...@outlook.com --- Comment #6 from B Stewart --- 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.
[kdenlive] [Bug 389624] Automatic scene split does not work in newer versions
https://bugs.kde.org/show_bug.cgi?id=389624 --- Comment #7 from B Stewart --- Created attachment 117731 --> https://bugs.kde.org/attachment.cgi?id=117731&action=edit Here is my script (Python3) I'm not a programmer as such, I've just dabbled around with things. This may not be the best written Python script but it works for me. There must only be 1 clip which should be placed at time 0 on the timeline. The project frame rate must equal the clip frame rate for it to work. (I picked up the project frame rate rather than the clip frame rate). run the script from a command line with the kdenlive filename (and path) as the first command line argument. Alternatively on Ubuntu 18.10 place the script in ".local/share/nautilus/scripts". The script can then be run by right clicking on the kdenlive file to work with. A new file is created with "_new" added to the filename. As usual,given in good faith, use at your own risk. Brian -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 389624] Automatic scene split does not work in newer versions
https://bugs.kde.org/show_bug.cgi?id=389624 --- Comment #10 from B Stewart --- Hi John, I typed in a lng step by step how to do it as a reply to your post but you must have added your last comment while I was typing and I lost it all. The important steps are:- 1. Start with a fresh project. 2. Open one clip only. 3. Make sure the project framerate matches the clip framerate. 4. Add the clip to the timeline at time 0. 5. Right click the clip in the "Project Bin" and select "Clip Jobs/Automatic scene split" and tick "Save result in metadata clip" 6. Wait until the progress bar finishes - can take a while for long clips. 7. Save the project - eg "Save As test" creaates test.kdenlive. 8. Run my script on the created file - a new file appears eg test_new.kdenlive. 9. Open the new file in kdenlive. If its "oversensitive" ie you have markers early on where there is no scene change, this happens if steps 3, 4 or 5 are not done in order! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 389624] Automatic scene split does not work in newer versions
https://bugs.kde.org/show_bug.cgi?id=389624 --- Comment #11 from B Stewart --- John, You asked "Where do I find the 'shot change list'?" you'll find it in the "Clip Properties" window, scroll down the icons to the right of the window to the icon that looks like an eye "Analysis data". This can be exported to a text file by clicking the middle icon under the window. The list looks like:- shot_change_list=1=25382/0:0x0:0;300=7663;648=6540;827=5105;1416=7401;1716=6503 The number following each ";" is the frame number of each shot change. This has to be divided by the framerate to create a time in seconds at which to set the "guide" marks. If the framerates for the clip don't match the project a load of low numbers seem to appear - don't know why. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 496639] Effect "Freeze" together with "subtitle" causes loss of contrast
https://bugs.kde.org/show_bug.cgi?id=496639 --- Comment #1 from B Stewart --- Further investigation today (25th Nov 2024) I can confirm that this bug was also in Kdenlive 24.08.1 using Ubuntu 20.04, KDE 6.5.0 and Qt 6.7.2 Kdenlive 23.08.4 with Ubuntu 20.04 and KDE 5.112.0 and Qt 5.15.10 was working OK - this bug was not present. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 496639] New: Effect "Freeze" together with "subtitle" causes loss of contrast
https://bugs.kde.org/show_bug.cgi?id=496639 Bug ID: 496639 Summary: Effect "Freeze" together with "subtitle" causes loss of contrast Classification: Applications Product: kdenlive Version: 24.08.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Video Effects & Transitions Assignee: j...@kdenlive.org Reporter: every-...@outlook.com Target Milestone: --- SUMMARY adding the "Freeze" effect to freeze a frame in combination with adding a subtitle causes the video to become greyish - loss of contrast, for the duration of the freeze frame. STEPS TO REPRODUCE 1. Select a short clip and apply the "Freeze" effect. Works as it should. 2. Add a subtitle track, the project monitor window looses contrast. Performing the subtitle before adding the "freeze" effect also has the same issue. The loss of contrast also appears in the rendered output. 3. I even tried adding the "freeze" effect without the subtitle, then adding the edited sequence to a new sequence with just the subtitle, but the problem still exists. OBSERVED RESULT When the "freeze" effect is used in combination with a subtitle track the video for the duration of the freeze has lower contrast. EXPECTED RESULT Adding a subtitle track should not change the contrast of output. SOFTWARE/OS VERSIONS Linux: Ubuntu 24.04 LTS Windows: not tried macOS: not tried (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma:Kdenlive 24.08.03 appimage KDE Plasma Version: ??? KDE Frameworks Version: 6.7.0 Qt Version: 6.8.0 MLT 7.28.0 ADDITIONAL INFORMATION Workaround found. use (right click - Extract frame to project) from Project Monitor window and then add the extracted frame as a clip instead of using the "freeze" effect. Add subtitle as required - no loss of contrast. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 496639] Effect "Freeze" together with "subtitle" causes loss of contrast
https://bugs.kde.org/show_bug.cgi?id=496639 --- Comment #2 from B Stewart --- Snap package of Kdenlive 24.08.3 with Ubuntu 24.04, KDE 6.6.0, and Qt 6.7.2, MLT 7.24.0 seems to be OK. It's possible that this bug is confined to the AppImage package mentioned in the bug report. -- You are receiving this mail because: You are watching all bug changes.
