Unacceptable Lag when moving large amounts of clips in complex sequences

Hello everyone,

Premiere Pro has a serious problem when it comes to moving large amounts of clips around (normal clips, adjustment layers with effects, stacked on top of each other and so on): [check the attachment]

To reproduce this: Just place a few clips next to each other, add transitions, effects, add mutliple adjustment layers above them, paste this creation a bunch of times until you reached 15-30 minutes.

I hope this issue gets prioritized as the current state does not allow to edit large videos without losing a lot of time on nothing. This problem in my exaggerated sequence example will also happen in real large complex sequences.

The only solution I found is to nest the sequence into multiple parts to reduce the load of clips.

The same issue appears when you have a sequence like that and want to select everything using CTRL+A. It takes roughly 3-5 seconds until it all is selected. But when you use the "Track Select Forward/Backward" tool, it is nearly instantly selected. So the solution for that would be to replace the current "select all" code with the code from that.

And besides all of this, I think most features that are worked on by the development team are pointless and nobody cares about them.

There are so many great upvoted ideas on this forum that would actually genuinely improve the editing experience for everyone.

Who uses "Ranged markers", "Sequence Index" or who asked for "Improved Menu Organization"?

What about improving the scripting API?

What about eliminating all performance issues on large complex sequences like the one I demonstrated here?

What about making all native effects (like "Posterize Time") GPU accelerated and therefore improve the render speeds?

Why is it that THOSE very features that EVERYONE wants and needs are not in the "In development" section when you open up the "What's new" page?

Sorry for the little rant, I just think it totally is a joke that in 2026 we still have problems like that.

Fingers crossed this gets fixed ASAP.