| Summary: | The "scratchlines" effect does not work on Windows | ||
|---|---|---|---|
| Product: | [Applications] kdenlive | Reporter: | bertrand767 |
| Component: | Video Effects & Transitions | Assignee: | Vincent PINON <vpinon> |
| Status: | RESOLVED FIXED | ||
| Severity: | critical | CC: | arlin.chuang, erjiang, miamotobg |
| Priority: | NOR | ||
| Version First Reported In: | 22.08.1 | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Microsoft Windows | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: | Capture video | ||
|
Description
bertrand767
2022-09-20 07:46:35 UTC
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. |