Adobe Premiere And Media Encoder Are Totally UNRELIABLE On Apple M1 Silicon macOS Monterey

 Premiere 22.6.2 and Media Encoder 22.6.1 have been pissing me off for the past few weeks. I had to take over this project that was started in Premiere, and I have experienced problems after problems with Sony MP4 and GoPro footage.

Image tearing up randomly, no matter what I try, it happens one way or the other. Premiere or Media Encoder, Silicon or Intel version, GPU, no GPU, Hardware accel, not accel, whatever I try, nothing works and I end up with tears and macro blocking on export.

I finally got fed up and transcoded everything to Apple ProRes. It's just 10 x the media size, whatever.

 Guess what. Freaking AME teared random images in the middle of random clips! I kid you not, this is not even edited, this is a raw MP4 clip from a Sony camera, transcoded to ProRes with AME.

And this is happening, at random:

What on earth is going on Adobe? Look at this macro blocking! Two minutes into a 10 minutes clip. This total crap goes on for a full 30 frames!!! An entire second of media screwed by Adobe.

This is a second attempt at the same transcode. Perfect. Wait, what???

Conclusion: Adobe is not ready for Silicon M1 Macs. Do not use Premiere or AME for reliable operation if you are on a Silicon Mac with Monterey.

Adobe, FIX THIS NOW!  And don't tell me it's Apple's fault. FCP and Resolve work reliably with MP4 footage. There is zero reason why this is happening but your laziness. At this point you should give me money to use your a$$ software, not the other way around.

Adobe Media Encoder Stops Encoding In The Middle Of A Job - Warp Stabilizer Bug

Mac M1, macOS Monterey, Premiere Pro 22.6.2, AME 22.6

  Two weeks on Adobe Premiere / AME and I'm fighting hell daily. Premiere is the plague of the business.

OK so after the unresolved issue of Premiere tearing up h264 footage on export, now AME decides to stop in the middle of a job (Premiere Project / Timeline / Export Media / Send to Media Encoder.)

The program is 21min., AME stops at 11min. No warnings, no message, nothing, just stops as if it was done. Whatever Entire Source or In/Out Selection is used, same result.

Checking the Timeline I see that Warp Stabilizer has been used on some clips (I inherited this project) right where AME calls it quit.

In the Timeline it actually shows a black frame at the tail of each of these Warp Stab clips. Why? Another Premiere bug.

I killed all these stabilization effects, and what do you know, it goes through encoding the entire program this time, no problemo.

So basically Warp Stabilizer in Premiere is UNUSEABLE, at the minimum UNRELIABLE and it makes AME stop encoding the program as soon as it is encountered.

Adobe, fix this NOW!

Adobe Media Encoder Create New Ingest Preset Bug on Silicon Mac

 Adobe is such an unnerving company. If you try to create a new Ingest Present for Premiere Pro on a Mac Silicon using the AME Silicon version, you're out of luck and you will go crazy trying to figure out why the stupid app refuses to create a new Ingest Preset.

If you click on Create New Ingest Preset, you will not go anywhere, the Preset won't be saved, and as a matter of facts, the window that opens is not even the correct one, it shows only a "Save As" button that doesn't save the Preset as Ingest Preset, but strictly as an Encoding Preset, unusable for Proxies creation.

It's a BUG Adobe. And it has not been fixed as of AME v 22.5.

To be able to create a new Ingest Preset, one has to use the INTEL version of AME. Accessible to launch under Creative Cloud app, AME, the three dots on the right, Open (Intel.)

Then with AME Intel running, on clicking Create new Ingest Preset you do get the proper window and the Save button, and it does save your preset as an Ingest Preset that works with Premiere.

That no one at Adobe bothered to check if this worked with the Silicon version is telling.

PS: AFTER you've created your first user Ingest Preset using AME Intel, for some reason AME Silicon allows you to create more and behaves as it should. Maddening.

Premiere Pro, Adobe Media Encoder - h264 Exports Problem, Image Tearing Up

  Mac mini M1, macOS Monterey 12.3.1, Premiere 22.5.

 Footage is h264 1080p 59.94. Editing Multicam 2 angles (same thing happens with non Multicam Clips btw.) Hardware acceleration is enabled (Same thing happens when Hardware Acceleration is turned off.) Exporting h264 VBR 1 pass, (the same thing happens with CBR.)

 Why on earth is Premiere Pro crapping up h264 exports? This is what I get in the exported file:

Last image before a "problem" cut, looks fine

First image after the cut, what the hell is this?

It goes on being total crap for 21 frames

Then for some reason it's back to normal at frame 22

 Why is this happening Adobe? What makes it even more infuriating is that it feels TOTALLY RANDOM. Why does it happens on this cut and not on another one? I'm not cutting at the very first frame or at the very last frame of a Multicam Clip.

 They are hundreds of other cuts exactly like this one in this piece. I'm far from fast cutting. The shots in this Sequence are between 2 and 19 seconds. All cuts are fine but for two that are severely damaged on export, like what you see in these picts.

 Note that nothing is visible on playback in the Program window at 1/2 res, it all looks good.

 Sequence is not rendered, but if I force render, the same thing happens. If I check use Previews for Export, the same thing happens.

 When I try to change the position of the cut, the crap goes away on the next export. But then some OTHER cut gets damaged that wasn't before! Totally at random, totally AGGRAVATING!!

 What a waste of time...

 This is painful!!! This should not be happening! Adobe FIX this abnormal behavior now!!!

--- I tried to Flatten the Multicam Clips on each side of the cut, and lo and behold, now I can SEE the tear in the image, but only if I go frame by frame over the cut. Playback is still just fine and shows absolutely nothing. Bizarrely, the tear appears on the second frame after the cut, not the first one like in the exports. If I stop the cursor over the teared image, it goes back to normal after about a couple of seconds!! What??! 

--- If I add an Adjustment Layer over the "problematic" cut, and play frame by frame, the tear is gone. But it's still in the export... Same thing if I overlap the clips a little.

--- If I do not use GPU, same thing happens.

--- If I use Software Only, same thing.

The only thing that works is to change the position of the cut. But since you cannot predict what will happen, you have to change the cut position, export the section with the cut, QC that, and if the image is still tearing up, adjust some more until it doesn't.

THAT"S NOT A WAY TO WORK !  THIS IS WRONG !  I WANT TO BE ABLE TO CUT ANYWHERE !

MAXIMUM AGGRAVATION ADOBE !

Premiere Pro Export Media How to Set the Proper Folder for Output Via Media Encoder (Queuing)

When I export multiple Media from Premiere, it remembers my Preset, but when I hit Queue, Media Encoder Output stubbornly points to the wrong Folder, over and over again.

Its a freaking pain having to click onto the Output Name in AME and setting the proper folder here EACH TIME as it does not remember the previous setting for some reason.

Instead, click on the Output Name in the Export Settings Window BEFORE hitting Queue.

From there, select the proper folder you want to output to. Next time you Export Media from Premiere IT WILL REMEMBER the correct Folder as the proper Output in AME.

It only sticks in AME if you set it first in the Export Setting Window. Doing it in the AME Window doesn't stick when Exporting from Premiere, unlike when you are dealing with a file.

Kind of counter intuitive, but at least this works.

No more Dolby AC3 in Adobe Media Encoder 2018

I can confirm that AME 2018 lacks Dolby AC3 settings.

AME 2018 - No more Dolby AC3. Only Mpeg and PCM

I installed the new version and forgot to uncheck "Remove Old Versions", so I re-installed AME 2017 from CC App Manager.

If you need AC3, go get AME 2017 now while it's still available, and remember DO NOT REMOVE OLD VERSIONS next time you update.

AME 2017 - With Dolby AC3

Interestingly, after two installs of AME 2018 and 2017, I cannot install another older version. Only option now is to Uninstall.

Are we limited to installing two versions of the same App?