Re-write Warp Stabilizer code and improve performance
Isn't it about time Adobe Premiere SW Engineering team did a complete overhaul of the Warp Stabilizer function?.
Its a very useful tool but painful to use - even with a very fast system. It appears the code running it is stuck in glue and efficiency is bad.
Even on a relatively fast system it does not appear to be making full use of CPU resources.
Competition products seem to be able to do this - so please add to priority engineering Software development list please.
Richard van den Boogaard commented
This follows from your request at the Adobe support community. Adobe should consider allowing the user to determine how much resources will be devoted to the warp stabilizer at any given point. It is currently designed as a background process, allowing the user to continue editing while Warp Stabilizer does its thing in the background. Some prefer to work this way, others prefer to have this effect calculated as fast as possible so they can adjust and finish this edit before moving on.