Samuel Neff
My feedback
4 results found
-
222 votesIn Progress ·
AdminFergus Hammond
(Product Manager, Video & Audio Cloud Workflows, Adobe DVA)
responded
Hi all,
There are two parts to this request:
1. Ensuring that proxies are created respecting changes that have already been applied to media via Interpret Footage.
2. Ensuring that changes in Interpret Footage are applied to proxies that have already been created.
The first part was done and is in v23 or later of Premiere Pro and Media Encoder. The second part is being worked on but I don't have a release data to share at this time.
Regards,
Fergus
An error occurred while saving the comment Samuel Neff
shared this idea
·
-
22 votesSamuel Neff
supported this idea
·
-
79 votesSamuel Neff
supported this idea
·
-
6 votesSamuel Neff
supported this idea
·
Amazing. I'm the original person who posted this "idea" for Premiere Pro over 4 YEARS ago. Realistically, this should have taken 3 months for Adobe to see and fix this in a bug fix update. In fact, this was ignored for so long that I stopped my Adobe subscription and moved to greener pastures. Now Adobe is finally addressing it by...putting duct tape over it, and leaving the original headache entirely in place. All the other comments in the last day are hitting the nail on the head. This is not a solution. "whatever frame rate entered in Interpret Footage will be used by Media Encoder to create proxies" is NOT a solution. Any video editor can (and has) explained this below. Adobe needs to do better, and I'm not waiting around to see if they do. Bye.