Example: If I exported an image sequence 1000 frames long, but decided I wanted to replace frames 50-100. I could select those frames as my in In Point & Out Point and click a box that says "take frame numbers from composition" or something, then the exported image files would be called XXX0050 - XXX0100 automatically.

Similar to Compressor on macOS — add the ability for users to queue and export a Premiere Pro timeline on another workstation(s). Editors can be liberated to work on the next project as the last finishes in a queue on another computer.

Please add the multi-audio export for H264.mp4 setup ... (like it's possible for MXF)

AAC 5.1 are not enought ... (because channel 4 are compressed and lowerred because it is SubBass track).
I want to use the H264 export setup option with a multi-audio mono (or stéréo) tracks like it existe for MXF file...

The LUT Sleclt button does not work under Effects > Lumetri Look/LUT

Instagram options should be included in the Social Media area.

I have i9 7900x with Nvidia 1080ti and 64gb ram Win 10. Was excited to hear about hardware encoding for h264 and h265 (finally!!!). Was stunned to find out it's only for intel integrated graphics - it's an April Fools 2018 joke, right? I guess I'm still transcoding in other (free) software until Adobe catches up...

I would like to be able to add to a media encoder queue running on a separate computer on shared storage.

Ticks = 65409 <4525426112> <Assert> <0> Debug Assert failed!
Expression: false
If you see this assert fire log a bug please.
Process: Adobe Media Encoder CC 2019
Process ID: 3296
Thread ID: 4525426112
File: /ame13.0.2/releases/AME/amedynamiclinkclient/src/AMEDynamicLinkClient.cpp
Line: 967
Function: virtual AMEDLClient::AMEDynamicLinkManager::~AMEDynamicLinkManager()
Assert Dialog Show:false
Callstack:
AMEDLClient::AMEDynamicLinkManager::~AMEDynamicLinkManager()
AMEDLClient::AMEDynamicLinkManager::~AMEDynamicLinkManager()
AMEDLClient::AMEDynamicLinkManager::Terminate()
AME::app::AMEAppInitializer::~AMEAppInitializer()
AME::app::AMEApp::TerminateApplication()
exo::app::AppBase::Terminate()
AME::RunTheApp(exo::app::AppInitArgs&, std::1::vector<std::1::basicstring<unsigned short, std::__1::chartraits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::1::allocator<std::1::basicstring<unsigned short, std::__1::chartraits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&)
main
start

Continual forced Windows updates destroying workflow. I am converting hundreds of videos in an archive. My queues can take days of processing. If a forced-boot update is pushed to the computer, the queue is lost.

In EXPORT SETTINGS in Premiere:
- when I have both 608 and 708 caption file on my project, I hit "Queue", it will only export the 608 text. However, in Premiere if I don't hit "Queue" and hit "export" it will export both.

So, exporting in Media Encoder does not for some reason export the 708 caption stream. Only the 608 one.

Please add an option to Set Limit File Size!

Thanks

After AME is finished with a render, display the time it took to complete. This information is available in the log file, but who wants to open that (and then convert seconds to hours/minutes) every time you render?

Nothing to describe, it is basically that: Output JPEG 2000 Sequence in XYZ Colorspace

Currently, none of the available GPUs in AWS, Azure or GCP are listed under the "accepted/certified" list for Premiere/AME (https://helpx.adobe.com/premiere-pro/system-requirements.html#SystemrequirementsApril2018121releaseofPremiereProCC). We are not seeing ANY added efficiency on export/rendering from Adobe Premiere when there are any of the following NVIDIA GPUs present and working on the cloud compute instance:

NVIDIA M60
NVIDIA P100
NVIDIA P4

Please add these to the list so we can get a performance boost when exporting/rendering on cloud instances.