Anthony Gilbert
My feedback
-
45 votesIn Progress ·
AdminFergus Hammond
(Product Manager, Video & Audio Cloud Workflows, Adobe DVA)
responded
As an update, this issue will be fixed in the next version of Premiere Pro, which is shipping in June. You can test the fix right now by using the latest beta.
Thanks,
Fergus
An error occurred while saving the comment An error occurred while saving the comment Anthony Gilbert
commented
I have also wondered if anyone bothers reading these comments. There are lots of people noticing this issue online and no one from either Apple or Adobe wants to acknowledge it. I can’t believe I spent £4000 on a laptop primarily for video editing, that was supposed to significantly reduce my work time with amazingly fast render speeds - but actually it doesn’t save any time if you can’t use hardware encoding! I’m outside of the return window for my M1 Max otherwise I’d have returned it to Apple!
Anthony Gilbert
supported this idea
·
An error occurred while saving the comment Anthony Gilbert
commented
I think I am getting this same issue on M1 Pro chip! Also noticed the same with Rosetta or ARM. Tried previous versions of Premiere Pro too - the same!
-
39 votes
An error occurred while saving the comment Anthony Gilbert
commented
I know right - I don't get why more people are not complaining about this or raising it as an issue. It seems like people are not realising it - maybe they are not perfectionists and just assume all is OK with their exports?! Adobe/Apple need to sort this out! I don't know how to get it escalated to a high up developer to look into.
An error occurred while saving the comment Anthony Gilbert
commented
Tim Cone - no one from Apple or Adobe seem to care to be honest.
Anthony Gilbert
shared this idea
·
-
4 votes
An error occurred while saving the comment Anthony Gilbert
commented
Just realised this is similar to the issue you're experiencing. If you put warp stabiliser above lumetri colour in the effect controls panel the issue goes away...
An error occurred while saving the comment Anthony Gilbert
commented
Are you experiencing any pixelation with Warp Stabiliser on M1 chip?
I've got an issue with 16inch MacBook Pro M1 Pro with warp stabiliser:
A 25fps sequence, with footage shot at 50fps - adding a warp stabiliser to the footage makes it extremely pixelated and it also exports this way. If you add the 50fps to a 50fps sequence and add a warp stabiliser - no issues at all.
Doesn't do this on my Intel Mac or Windows desktop!
-
1 vote
An error occurred while saving the comment Anthony Gilbert
commented
I've just realised this is linked to applying lumetri colour to the clip. If you apply lumetri colour first in the effects panel and then add a warp stabiliser this causes the pixelation. If you move the warp stabiliser above lumetri colour the pixelation goes away and footage returns to its normal quality.
An error occurred while saving the comment Anthony Gilbert
commented
I think this issue is related to this: https://adobe-video.uservoice.com/forums/911233-premiere-pro/suggestions/44368392-issue-poor-hardware-encoding-quality-mac-m1-pr
It seems to be an issue with how the GPU is handling footage from Premiere Pro.
Anthony Gilbert
shared this idea
·
-
1 voteAnthony Gilbert
shared this idea
·
I can confirm I've tried this using the latest release and the exports are still the same. I have been working on a project this week;
Exported with software encoding: 3.2GB
Exported with hardware encoding: 1.7GB and lots of compression artifacts/noise/grain
Running on MacBook Pro 16inch M1 Max.