I'm afraid that we started out speaking two different languages
You see PD as a black box that is supposed to do whatever you tell it to and then saw a competing product apparently able to do the same thing much faster. I didn't have enough information for a ready answer and I jumped straight into troubleshooting mode, trying to explain why the edits you made would take lots of processing power without addressing why PD might take so much longer to produce. Apologies for missing the gist of your concern.
I'm not sitting with you and can't see what you see, so I tried breaking this down into discrete steps to try and figure out what was actually happening.
It's kind of like you telling your mechanic that your new sports car doesn't "go fast" and expect that they'll somehow know what's wrong; when in reality they'll have to take a detailed look under the hood to find what's working properly and what isn't.
I don't know if you're interested in doing that with PD here, but if you are we can try this a couple of different ways:
Option #1
Create a new project with only the bare clips and then produce. If SVRT is available, you should be done in a few seconds. I would also ask you to
uncheck SVRT and use hardware encoding to see how long that takes, as that would be the first step in doing an apples-to-apples comparison with Resolve.
If producing the bare clips
still takes many minutes, then something is seriously wrong with how PD is configured on your computer. We would want to address that before doing anything else.
If instead PD can produce the bare clips very quickly, then try adding one edit (one colour correction or speed change) at a time and then produce the project.
Do not be surprised when the SVRT box becomes greyed out at some point. That is expected when the kinds of edits you've made are added to the project, and is not an indication that anything is wrong.
Produce a test clip after each new edit and see at which point the producing time take a big hit. NOTE: you actually don't need to wait for the entire thing to finish, just let it produce long enought to see what the estimated remaining time is and look for a noticeable change there.
That will tell you which particular correction (or speed change) is taking a long time to produce, which can help us figure out where the problem might lie.
This should only take a few minutes to try, and hopefully we'll have a clearer picture of what's happening.
Option #2
Share the original project by uploading it to a cloud folder on Google Drive or similar service. I and other members would be able to examine the project and test it on our machines to see how long it takes to produce and identify possible bottlenecks.
Please only do that if you're comfortable sharing your clips online!
To do this, use Pack Project Materials under PD's File menu to choose the desired output folder, either directly on the cloud server or on your local hard drive to be uploaded to the cloud later. Please send me a private message if you don't have easy access to cloud storage and would like to upload the project to a folder on my OneDrive or Google Drive account.
YouTube/optodata
DS365 | Win11 Pro | Ryzen 9 3950X | RTX 4070 Ti | 32GB RAM | 10TB SSDs | 5K+4K HDR monitors
Canon Vixia GX10 (4K 60p) | HF G30 (HD 60p) | Yi Action+ 4K | 360Fly 4K 360°