I am posting this in a different category, just in case.
I am noticing 1-2 GB higher VRAM usage when encoding Premiere Pro sequences in Media Encoder than directly in Premiere. So much so, that I must run ME by itself to avoid VRAM-related render failures.

For example, in order to reliably render my documentary in ME, I have to make sure to quit Premiere first before starting my render queue. But then, I am rendering out three different file formats of this show. After the first one completes successfully, and is between renders VRAM usage stays high. Then, when the next render begins, VRAM usage increases further, until the next render crashes partway through. The only way to get them to render, is to quit ME between renders, so ME releases the VRAM. Then, it will render the next sequence. But then, it will fail again if it tries to do the next version.

When PPro finishes rendering a sequence, it releases the VRAM. When ME finishes rendering a sequence, there is no change in VRAM usage until you quit ME.

This is hardware encoding to HEVC, AVC, and then software MXF (XDCAM)

It is a 1080 sequence, but it has 4K footage in it.

Premiere Pro / ME 14.9
Windows 10/64 32GB
GTX 1080 8GB

I will gladly provide any other details.
Thanks for any assistance you can provide.

This appeared to be a bug and a rather frustrating one to work out.

Exporting a sequence from Premiere 14.9 would result in audio effects (applied in audio track mixer) being rendered out properly, but when the sequence was sent to a queue in Media Encoder 14.1, the audio effects weren't applied.

I couldn't figure this out initially and had to re-render my hours worth of material via manually exporting from the export window.

After speaking to someone on the Australian AVPUG on facebook, they explained that it can happen if there's a mismatch between versions, and indeed there was.
Updating ME fixed the issue.

However I don't know if this is a bug or not.
Seems to me that it could easily happen a lot to users.

AME starting from 14.5 till 15.0 beta failes when exporting.

Short description:

Source Material is mainly 4k and above from GoPro Hero 7-9.

This appears only when using Hardware encoding (NVIDIA lastest Studia driver).
Software encoding works but is due to the unacceptable Runtime not an Option.

Exporting the same project again the error is at a different timestamp.

The error appears always between 2 Clips.

unchecking the following setting in AME "Import sequences natively" allows me to export succesful but the runtime is longer, however not as long as with software encoding..
Checking the above item produces the error again. This is reproducable.

Hardware is AMD Ryzen 9 with NVididia 16xx 32GB Mermory and fast M2 SSD Drives.
OS is Windows 10 latest Version.
Any Ideas?

I set up an overnight batch export to make proxy files. Upon returning the following morning Media Encoder insisted on quitting over and over and over and over again. No matter how many times I told it I didn't want to quit, it kept popping up asking me if I wanted to quit. This also froze all exports so basically nothing had actually happened overnight.

Why did this happen? Because Creative Cloud automatically logged me out, for absolutely no reason!

If your software hinges entirely on me being signed in CONSTANTLY, that is unacceptable. I lost time on this project because of stupid authentication.

I can no longer trust that my overnight exports will complete. Batches? Now I have to babysit them to make sure they complete properly and don't fail on some stupid technicality. My Premiere export also failed because a "font went offline" - Why did it go offline? Because the fonts are tied to my profile and when CC logged me out, my fonts disappeared as well.

THIS IS NOT HOW THIS SHOULD WORK

If CC needs to log me out for another pointless update, then the programs should recognize a 30 day grace period.

Get your act together Adobe. You make billions off of our subscriptions and then compromise our projects.

Still waiting on that M1 support...

Trying to export two versions / sizes to H264 MP4 from a source 1080p ProRes file. I'm using CUDA accelerated Mercury Playback Engine. AME behavior is inconsistent. First attempt resulted in one of the two desired outputs being completed successfully, with the second output failing without an error.

Tried switching to CPU Mercury Playback Engine, re-added file to the queue, set desired outputs, but this time both output files failed to render. No error, just failed.

I switched back to CUDA accelerated, re-added file/outputs, and this time both files output successfully.

I'm on Windows 10 Pro, with an AMD Threadripper 3990X, 256GB of RAM, and dual RTX 3090s...on the latest version of Media Encoder Version 14.6 (Build 42).

Also, it would be great to have a Bug category to select when leaving feedback. This is filed under stability because ...