Specifically allow media encoder to add either custom text or source file name as a prefix/suffix to the output file. In my work my After Effects project are given job numbers and the output file also must be named with the same job number to keep track of files.

We have also created templates to ease with production, currently our output comps simply start with "XXXXX" and we do a batch rename after rendering is complete. But with custom prefixes/suffixes we wouldn't have a need for that step.

This could be added as an option to encoding presets or to Media Encoder preferences. I think as an encoding preset it would allow for more flexibility.

My renders keep predictably crashing due to Premiere/Media Encoder's inability to manage VRAM.
For example, in order to reliably render this 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.

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.

Please improve 10bit encoding using GPU, at the moment you dont support 10bit export, I have tried for the last 4-5 days to keep 10 bit all the hdr rec2020 and use hardware encoding which reverts back to software encoding which is no good very slow , 10bit 4k with hdr rec2020 is the way forward and include in you adobe media centre + adobe premier pro for a new pre-set for this, when I select x265 custom pre-set and select main 10 , tier high, rec2020, hdr, and include hdr10, straight away I receive a message , your system hardware does not support hardware acceleration for the current settings , I know it does Because I use a program called StaxRip
which does this and keeps all metadata for 4k 10bit x265 NVidia GPU acceleration. please could you create a complete new 10bit 4k x265 support for GPU encoding, I will attach a file with the issue I am facing, and I am not the only one a lot of customers are facing this issue , also
I got the info about 10bit export not being supported from adobe community forum, so please could you improve this. Thanks
Regards
Sean Oakley

After Effects and Adobe Media Encoder 2020 are rendering h264 codec MP4s too bright. The colors are washed out slightly and what I'm assuming is a gamma shift. I'm using Windows 10, After Effects v17.1.4, Adobe Media Encoder v14.4, and Nvidia driver 451.77.

This issue does not exist on After Effects 2019 and Adobe Media Encoder 2019. The MP4s look as you would expect, using identical settings for export.

One additional finding was that using After Codecs plugin, I'm able to export an MP4 using the x264 codec and the colors are correct. That is also using AE and AME 2020. So, from what I'm gathering there is definitely an issue with AME 2020.

I find this annoying issue with nearly every release of AME, and have had it pop up off and on since 2004. This is not an issue with playback between video players, but specifically a color shift in the actual render. I'm not using any display profiles, and have After Effects set to not use a Workspace color profile in Project settings. Have also tested rendering the files with and without Hardware encoding turned on.

Would be happy to send additional info or files if needed. Thank you!

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.

There is the ability to Apply a Name overlay to any clip but it remains limited in using the stitch clip function. Currently if you add the effect to a stitched clip it would add the name of the overall stitched clip and not the name of each individual clip.
I am advocating for the addition of a radio button to enable per clip naming.
The current work around is exporting all clips to be stitched through media encoder individually with the effect > name enabled and then take all of those exports and create a stitched video from it. While a bit redundant and potentially tedious, this current workflow functions but could be streamlined.

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...