newest Windows 10, Shotcut 26.7.16 (and older versions too). RTX 3060, 26 GB RAM, Intel Core i5 4th generation - a bit outdated, that’s true
I have a project that is 1 hour long, 3 video tracks, 1 audio track, a few dozen FullHD clips with 360p proxy and preview. Not too many cuts, almost no effects. Yet if I zoom in into the timeline, it starts lagging heavily, the more I zoom the slower everything becomes. After that even simplest operations like moving a clip on the timeline takes several seconds to process. Zoom out - and the lags are gone. Generally the longer the project the more severe the issue is. This is counter-intuitive, since the more I zoom there is less data to display in the timeline. I would understand that displaying a whole complicated project requires a lot of processing power, but in this case everything flies even on my old CPU.
I’ve seen this issue reported a few times already, first time dating back to 2017, but I see no solid response nor change in the performance.
It does not only manage objects visible within the scrolling viewport. All clips are still in a canvas and now you’ve enlarged them, which is more work–similar to working with higher resolution video. What it needs is a proxy model that includes only what is currently in view. And a smarter view that understands how to render scrollbars that represent the total and clips that extend beyond borders and respond in realtime to interactive scrolling. I worked on it once and gave up because I suck.
this issue reported a few times already, first time dating back to 2017, but I see no solid response nor change in the performance
Well, first I wanted to know if it’s a bug at all (seems so for me, but maybe I’m doing something wrong) and it’s a work to do (which I didn’t know); second I would need to know current Shotcut source and language (which I don’t) and how to fix it (which I don’t know as well). The issue is not listed in Roadmap nor in GitHub issues section, so please don’t be offended by my question/bug report. Also I don’t reckon you suck but rather the opposite, since Shotcut is a really nice piece of software - well, except that timeline zoom Let‘s document the case and maybe it could go easier afterwards.
It is a known issue, but I do not consider it a bug. Some projects consider any issue or even feature requests as a “bug,” because I guess they want to put them all into one tracking system. However, I prefer to track bugs separately as something clearly broken rather than things that can be improved. Performance is like a bottom-less pit. That might be an English-only expression. Performance improvement is a continual process. Of course, there can be some major performance regression in some area from one version to the next that can be considered a bug. I think you also want to know if it the issue you raise is about something you are doing or a setting, and the answer is: no, I do not believe so. Basically, until we have a breakthrough, you need to workaround the problem by limiting the project size, decomposing it into smaller pieces to combine later, or zoom out to a workable balance of precision and comfort.
Let‘s document the case and maybe it could go easier afterwards.