JK
My feedback
-
14 votesJK
supported this idea
·
An error occurred while saving the comment -
32 votesIn Progress ·
AdminFergus Hammond
(Product Manager, Video & Audio Cloud Workflows, Adobe DVA)
responded
Hi,
This something we're aware of and working on. I don't have a date for a fix but the work is well underway - we know exactly what the issue is and the correct way to solve it.
Regards, Fergus
JK
supported this idea
·
-
27 votes
An error occurred while saving the comment JK
commented
There is definitely a memory issue. It uses up all the wap memory while editing and throws error
I have a new laptop with 32gb ram, never had this issue before on older setups.JK
supported this idea
·
-
2 votesJK
shared this idea
·
-
2 votesJK
supported this idea
·
An error occurred while saving the comment JK
commented
Yes v22 broke hlg3 > rec709 workflow.
Even if i import hlg3 from sony camera footage is overexposed. You need to > modify > Interpret the footage first and set colour space to rec709. But then proxies doesn't respect that... -
12 votesJK
supported this idea
·
-
5 votesJK
supported this idea
·
-
546 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.
JK
supported this idea
·
-
669 votes
This is a great request that is certainly something we want to implement. Rest assured our engineers DO understand the importance of this feature and how to get the job done. We also know that the performance and stability of the app should be our #1 priority and that is where our focus is right now.
JK
supported this idea
·
-
50 votes
An error occurred while saving the comment JK
commented
Please add this!
JK
supported this idea
·
-
626 votesJK
supported this idea
·
-
698 votes
This is something we are looking into. Thanks for the feedback.
JK
supported this idea
·
-
7 votesJK
supported this idea
·
-
2 votesJK
shared this idea
·
-
117 votesJK
supported this idea
·
-
113 votesJK
supported this idea
·
-
210 votesIn Progress ·AdminFergus Hammond
(Product Manager, Video & Audio Cloud Workflows, Adobe DVA)
responded
Hi all,
This issue will be fixed in the next version of Premiere Pro: whatever frame rate entered in Interpret Footage will be used by Media Encoder to create proxies.
Regards,
Fergus
JK
supported this idea
·
-
439 votesJK
supported this idea
·
-
649 votesUnder Review · 64 comments · Premiere Pro » Effects & Transitions · Flag idea as inappropriate… · Admin →JK
supported this idea
·
-
510 votes
Thanks everyone for your feedback. I am moving this to Under Review.
An error occurred while saving the comment JK
commented
voted. Please fix. It even generates a separate Proxy. So annoying. i sometime forget i had already imported a clip and then i find i have two.
JK
supported this idea
·
Please fix this. Its unusable as is.