An error occurred while saving the commentSam Gordon commented
Astonishing that this hasn't been fixed yet.
As Wes noted, we are looking at many areas for optimization and have made strides in the last few releases already.
We recognize there are still many areas to improve performance and we are investing in appropriate areas.
Threads that are catch-alls are often non-actionable. Please keep giving us specific feedback on what workflows are slow for you.
Technical solutions may not always be as obvious as some people may be suggesting as the application architecture is often very different than people’s conception.
Short answer. Yes, we want to and will make it faster.
As Jim Simon noted, there is already a request for this so certainly upvote that request.
This is an area we are looking into for future versions to make auto-save more reliable and out of the way.
491 votesUnder Review · 44 comments · Premiere Pro » Effects & Transitions · Flag idea as inappropriate… · Admin →
Thanks for all the feedback. It’s pretty clear that we’ve got to look into the workflow using this format more closely, there are enough reports about gaps at this point to reopen this item. I’ll post more info about next steps shortly. In the meantime, a couple of questions are easy to answer:
- The plugin is designed for Premiere Pro. It currently doesn’t provide support for After Effects.
- It does work with AME, so if you want to use it for batch processing, that’s very doable
- If you’ve started a project with Autokroma, there’s no easy way to transfer it to be running with the new plugin.