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.

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!

I'm editing a feature documentary, and many of the archives are made of old DV footage. Unfortunately I can't import any of the material either directly into premiere or into ME to convert into a supported format. Adobe should have kept the codec at least for media encoder. I can't imagine the amount of editors around the world who've had similar frustration and with the monthly subscription service as it is, a creative cloud user, shouldn't have to turn to or pay for additional 3rd party support for a feature that was a part of the older editions. It's absurd to the extreme. An entire generation of archive was shot on the DV format, so the decision to remove it smacks of corporate greed or oversight. Something that could be easily amended on their side, if they so consented.

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

There is a big issue with iphone footage coming in with Variable FR resulting in skewed audio/video throughout the adobe suite. Right now the only fix for it is to upload the footage into third party software and encode the footage to have a Constant FR, which is pretty ridiculous given that we have a media encoder for Adobe and if I wanted to be using open source software, I wouldn't be paying for the adobe suite. I think Media Encoder is the obvious software solution for this but it affects so many of the adobe suite programs that it should be implemented in a way that makes it easy for users to make the change regardless of what program they are using (like how exporting generally moves the file to encoder). This is something that your help desk team is aware of and right now they currently recommend an open source program called "HandBrake" to remedy it. As a software platform that goes out of its way to be Iphone friendly, I think this is a must-have for the program. In the same vein, VLC was able to import the footage correctly without issue as well. I hate to nag on you guys but I find it a little disheartening that so many open source programs get this concept to the point where the solutions are barely even user facing (VLC just corrects it on its own) and Adobe, which is a very expensive suite, doesn't. Please make this crucial update.

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.

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.