Sergio Sanchez
My feedback
-
47 votes
An error occurred while saving the comment -
7 votesSergio Sanchez
supported this idea
·
-
39 votesSergio Sanchez
supported this idea
·
-
45 votesSergio Sanchez
supported this idea
·
-
489 votes
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.
Sergio Sanchez
supported this idea
·
-
162 votes
We are investigating these reported issues. Thanks for the feedback.
Sergio Sanchez
supported this idea
·
-
1,551 votes
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.Patrick
Sergio Sanchez
supported this idea
·
Same here...
I'm on a 1080Ti with driver version 451.48