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.

When using a Watch Folder, ME moves the original file to a folder called Source and places it under a sub-folder named with the date and time.

This means that locating the original file requires knowledge of when it was processed. Not a big deal when managing only a few files, but a huge pain for a large number of files, particularly when multiple editors need to locate those files.

At a bare minimum, I would like the be able to set the sub-folder name to the same as the original file. Appending a "_#" tot he folder name in the event of duplicated file names would be acceptable.

Even better would be to be able to configure multiple settings for what happens to the master file after processing. I understand the need to move it, but let me specify the name of the "Source" folder and decide if each file needs its own sub-folder or not. If so, let me specify how that folder is named.

This software is called media ENCODER so technically this doesn't really fall under it's rubric but, since one can queue multiple encodes to different locations it would also be helpful to have post encoding options such as the ability to copy a finished job to multiple locations, this allows one to automatically output to all needed locations, but also avoid unnecessary re-encoding. It's just a convenience thing.

I am often encoding to an external drive to be used as a delivery medium, but that is not the location that will be used for archiving of the project. A given encode can be quite large and take a long time to copy and an even longer time to encode. It would be good to queue the encode to go to the delivery drive first, so that it's on there as quick as possible but also have it copy to the archive storage location afterwards. This will allow me to go away and do other tasks while media encoder works and have everything be in it's place on my return, but also minimise how long that hiatus needs to be.

Naming rules for files and folders.
As we have presets for encoding preferences, such should be for naming convention of files and the automation of creating new folders.

for example:
For the "save to" folder I selected: D:\Projects\MyMovie\
Enecoded file, JPG SEQ named: Scn1_####.jpg
and third place output in the outputs list
with a QT preset named "QTpreview":

A naming rule such: \%FileName\%index_%FileName.ext

will save as: D:\Projects\MyMovie\Scn1\3_Scn1.mov
*Underscore and numbers should not be included unless
a different rule is used.

A naming rule such \%index\%preset.ext

will save as D:\Projects\MyMovie\3\QTpreview.mov

More rules can be used such as date, Time code extra.
every output can have a preset rule and and outputs selected together can simultaneously with a click of a button change their preset together

Since upgrading from 2017 to 2018 we can not use the Media Encoder batch processing feature any more. After 1 or 2 processed videos Media Encoder fails and we get the following error message:

Export Error
Error compiling movie.

Accelerated Renderer Error

Unable to produce frame.

Writing with exporter: QuickTime
Writing to file: R:\5760-Cineform\Incoming\ATM00442-Australia-Kangaroos-on-Beach-5760x2880-29-97fps-Cineform-2-Min-Col-Stereo-Sound.mov
Around timecode: 00;02;49;19 - 00;02;49;23
Rendering at offset: 130.998 seconds
Component: QuickTime of type Exporter
Selector: 9
Error code: -1609629695

We would love to be able to render overnight again, rather than rendering each file from Premiere for 30-40 minutes before being able to work on the next video.

This is a major bottle neck for us that costs us a lot of time and we would be thankful if someone could look into this.

Thanks,

Eric

AME does not use all cores, because of unknown reason (OpenSource encoder can do this). I have an 32 Core CPU (Threadripper) and only 5 Cores used.

Either AME should scale encoding processes (without GPU) to more cores, or AME should allow to start multiple instances (without GPU) to use the other cores in parallel.

In my case encoding into DNX 4K takes only 5 cores with only 200Mb/s and waste the other cores with doing nothing. Encoding takes two times than the length (approx. 30fps). I could render 6 streams in parallel without any problems, but i can't and waste insane time.

So please:

-1-
Scale non GPU rendering to a configurable CPU core amount.
This will require massive rewrite of rendering code and this is maybe unrealistic

-2-
Allow to run multiple non GPU rendering AME at same time. Let the user decide how many instances.
This would require just a little piece of code without rewrite the entire render pipeline.

Conclusion:

Please stop ignoring multi core and multi processing, time is over to have a CPU with just 4 or 8 cores :-)