@R Neil Haugen my experience with warp is that it really crushes the user interface, and it hates doing multiple clips at the same time. The issue for me is that I can have 40 clips I want to do, that each take 5 to 15 min to do, and hang around waiting for each one to complete to que up the next one. If nothing more than getting warp stabilize to do one at a time in order of application, it would get me 90% of the way there. But by extension, if you can que up different clips, and have them start after the one prior is completed, then I would also like a user definable option that says, do one at a time, or do two, or three. let the user have some input. What happens to me now is the user interface will run very poor with even one warp processing running. so, I will in fact force a second or 3rd clip to start processing, and that can get me to 80% CPU utilization. Premier interface is running very poorly and takes a long time for mouse clicks and other elements to update - but the clips process in the background, and eventually get done, and I can do something else. In fact, there is plenty of resources left over, depending on exactly how many warp clips are processing, for me to use the NVENC encoder to transcode video to ProRes, or at times, I will in fact run topaz, and have it process clips for noise reduction normally at the same time. Overnight, it would be ideal if the system doesn’t have any free time and it’s always doing something, not waiting on that simple click to do the next task. My main point is let me que up tasks so the system can be busy with something to do, at or near 100% utilization - so when I'm on the phone, or at a meeting, sleeping, watching a hockey game - it’s still chugging along at whatever max utilization I want to be at. But over and above that, there are simple things that can be fixed without too much architecture design, such as warp process should not come to stand still when a render and replace is requested! Some of the other ideas to add in a small visual token mark on the clip to show if warp is applied, in progress, stopped or completed is helpful too. There are considerable ways in which to improve these small things. I hope to get some ideas out, so that Adobe can consider them at least. Frankly it doesn’t stop one from getting work done, but it sure does make it a little harder - when you’re doing stuff that takes so long to process, but that process finishes when you’re in a meeting, or a conf call, it would be nice that it could start the next thing for you so you strand the time between calls/meetings/sleeping, driving as unused by your system when all it needed was someone to 'click' on something for the next task to start. Maybe I'm not explaining it well enough, but I hope the main concept of the avoiding of idle time for the system, but giving it the power to do things in an order - is what comes across well enough - to avoid system idle time when there is work to do.
... View more