I have a strange bug on my computer, I suspect driver issues but I am not sure. When I export a video with a transition, and if there is at least one GPU effect (for example, Contrast), then the transition is completely buggy and colored with red.
This does not affect playing inside Shotcut, only after export.
I mean, any filter which can be applied on a video, which is categorized as “GPU” effect. For example, change of contrast, saturation, or sharpness.
Is it possible to use these filters as well as transitions without GPU processing enabled ? If I try to uncheck it, then I cannot open my project anymore and I should edit the mlt file to remove the movit functions, which ends up removing transitions and video filters…
This is no workaround. GPU Effects were/are experimental, and work differently from one computer to the next, meaning either you had excellent results, to having Shotcut crash every time the project was opened. GPU Effects are now disabled/hidden with 18.11.18, and are not supported.
As @brian pointed out, three posts up, there no clean way to fix the project.
Best practice: Use the newest version by >> downloading here <<, and to start a new project instead. Or if you choose to use an older version, leave GPU effects off. And if you want to experiment with GPU effects. Have a master copy of your project, duplicate/copy that to projectGPU.mlt then with a copy of the mlt, experiment with GPU effect.
Having backup copies of your projects files, as you work, is just good practice. If you work on a project daily, then every day would be a new version save. The mlt projects save files take such little room, as they are not video file, but lines of XML code.
Totally NOT a Best Practice. 18.12.23 (which automatically installed itself today) is unstable even with GPU disabled, and it totally disables the use of Screen 0 as an External Monitor, which was working perfectly before and had and has become essential for my editing work.
multiple clicking back and forth between the three available choices, now it finally has resumed working as before.
This after many crashes, some of them bringing down the operating system with it.
It would seem that the “fix” was that when I re-installed Davinci, that install corrected whatever Linux or video driver parameters etc. that the upgrade to 18.12.23 had broken.
I have no doubt that 18.12.23 is stable on Windows 10 (I wish Windows 10 was working on my computer, but that’s another story) However, Shotcut 18.12.23 is highly unstable when running under Ubuntu Linux.
Re: " leave GPU effects off. And if … experiment with GPU effects."
The ONLY reason I switched to Shotcut from a competitor, originally, was that Shotcut supports the GPU. Without using the GPU, Export uses all of the CPU power for unacceptable long periods (385% of a possible 400% on an AMD-64 with 4 cores, for upwards of an hour). By enabling GPU effects, CPU consumption is reduced to 230% out of 400%, allowing for other productive work during exports, and the total export time is reduced by 20% to 50%, thus increasing productivity by reducing turnaround.
The minor instabilities of Shotcut GPU are a small price to pay for such a performance increase.
The instabilities of 18.12.23 under Linux appear to be, if anything, worse when the GPU is disabled.
18.11.13 is great. Reversion to that version, and redefining 18.12.23 as “beta”, would be a good idea.
The performance improvements of 18.11.13 arr marvelous. Nevertheless, if filters are used, the performance of 18.11.13 suffers. Enabling GPU on 18.11.13 drops the CPU usage to acceptable levels while cutting about 20% from the processing time for Export.
As a software (and microcomputer hardware) engineer with more than five decades of experience, I would speculate that the focus on fixing performance and bug issues in Windows 10 (which is, granted, by far the largest market) caused a tunnel-vision that overlooked the effect that those “fixes” would have on other OS’s that Shotcut also supports, such as Linux.