SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Insert a video in the timeline 2. Apply the "scratches" filter in the "Effects" section to achieve an old movie effect 3. No scratches even by increasing all the options of this effect OBSERVED RESULT No visual stripes on the preview video and even if we make a final rendering, the "effect" has no effect EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 Professionnel 21H2 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION
Created attachment 152252 [details] Capture video
*** Bug 459737 has been marked as a duplicate of this bug. ***
*** Bug 458533 has been marked as a duplicate of this bug. ***
It looks like the oldfilm/lines effect is generating invalid X positions on Windows, which get saved into the XML. For example, on Linux it may generate a reasonable value like line5=920px, while on Windows it may generate line5=92142796. It may be a bug in MLT, but not sure. I tested and was able to reproduce on Windows standalone 22.08.1. Because the generated random numbers are saved in the XML, opening a project with scratchlines created on Linux will work fine.
(In reply to erjiang from comment #4) > It looks like the oldfilm/lines effect is generating invalid X positions on > Windows, which get saved into the XML. For example, on Linux it may generate > a reasonable value like line5=920px, while on Windows it may generate > line5=92142796. It may be a bug in MLT, but not sure. > > I tested and was able to reproduce on Windows standalone 22.08.1. Because > the generated random numbers are saved in the XML, opening a project with > scratchlines created on Linux will work fine. Thank you very much for these explanations and spending time trying to find a solution. I have good news for the Windows version: I just installed the latest version of the software (22.08.3) and I was pleasantly surprised to see that the bug had disappeared. So installing the new version solves this problem. Thanks again for your help.