What is your operating system?
(If you are using Linux, you must state how you installed Shotcut as there are too many builds and packages. In general, we do not make the build installed by your distribution package manager unless it installs the Snap. The developers only build, test, run, and support the builds shown on our download page.)
Windows 10
What is your Shotcut version (see Help > About Shotcut)?
Shotcut version 25.03.29
Can you repeat the problem? If so, what are the steps?
(Please be specific and use the names as seen in Shotcut, preferably English. Include a screenshot or screen recording if you can. Also, you can attach logs from either View > Application Log or right-click a job and choose View Log.)
(Hopefully this Time you can directly understand what I mean…)
- I have a Project of one big Video File (~200 GB) and added this as an Video-Track and two Audio tracks
- We are already about 50 Minutes in on the Video File
- I found some coughing and Cut it out on the secound Audio Track and add a Mute-Filter to the Cut-Out Section:
- I am starting the Export/Rendering
Rendering with 2-3 of these small (<1 Second) Sections of Muted Audio takes about 50 Minutes to fully render a 15 Minute Project of 1 Video Track and 2 Audio Tracks
Rendering without these Sections and an untouched Tracks takes around 10 Minutes.
If I have these small Muted Sections I notice in the Task-Manager that as soon as Melt “reaches” these Section in the Rendering it re-reads from Disc these Parts:
-
“Resuming” Bytes from the Audio Track:
-
The Bytes related to the Muted Part of the Audio Track:
-
It “resumes” on the un-muted Audio Track again:
I know that for Melt these are distinct Tracks and thus it reads them from Disk. But can’t it just check if could re-use some of the already loaded data or maybe even keep the read-pointer for the Data from Disk if some neighbor Track could benefit from it? Because now Melt will always start from beginning of the File so seek for the Data to resume and this takes a lot of time actually.