Greetings,

We are using the Essential Graphics Panel shared library to add motion graphics to Premiere timelines. We are sometimes rendering our timelines to a render machine which is using a Watch Folder setup. The problem we have is that the motion graphics content is shown as offline and not rendered but the rest of the timeline renders fine. The Motion Graphics Template Media folder is on the same server as all of our other media and should be easily located by AME. I'm guessing that the Watch Folder functionality hasn't been updated to take into account the new workflow of the Essential Graphics panel. Has anyone else had the same experience? Fixes?

I have seen similar posts, but no resolution?

I have just done a complete Fresh install of windows 10 and installed the Adobe CC 2018 apps I use. Computer is Intel i7 4.0ghz, 24gb Ram, Geforce  GTX1080TI.

Never had this issue with any other version. When I export from PremPro to Media Encoder, It appears in Media Encoder but when I hit start, nothing happens. Just sits there as if I haven't started it yet? I have tried latest Video card drivers and previous version. I have deleted preferences and tried again, I have uninstalled encoder and reinstalled it.

It will work? When I bring in the sequence via Media Encoder Directly which leads me to think it may be some kind of linking issue, but then again I don't know enough about it.

Is there any resolution to this issue??? A little cumbersome doing it through Media Encoder.

Would appreciate any suggestions.

Thanks Tony.

Hi,

I've been searching online and reading through the forum articles about exporting from Premiere and AME with the 'Fast Start' encoding option for quicktime movie files in the h.264 codec.

A lot of the information I've gathered is around the 'moov atom' and how it's commonly placed at the end of a file. For the progressive nature of playback to occur this atom apparently needs to be at the beginning of the file. Forum articles and others have suggested using third party, line based applications to change this atom position. This seems ridiculous to me as it complicates my workflow.

I have recently switched from the Apple Studio products to Adobe's and in the past I would simply check 'encode for fast start' on the export menu and this would encode the file properly.

Does Adobe have this function built into the program? Am I overlooking something? Is there is a better workflow that I am unaware of?

How best can I encode my videos so that they will buffer a small amount and then progressively download the rest as the viewers watches it?

Thank you all kindly in advance for your help.

The FCP xml sent to AME has an ampersand in the filepath used in the <pathurl> tag as shown below

//localhost/DEMOSERVER/MediaStore/HighRes/test&amp;test/test.mxf

And AME couldnt accept ampersand even its escaped as &amp;  or %26

Please could you advise.

I recently installed both Premiere Pro CC 2018 and Encoder 2018. But when I export media and choose "queue" it does not go to encoder (it goes nowhere).  How to I get the dynamic link to work?

I am having some weird experience with Adobe Media Encoder (and Premiere) on my MacPro Late 2013, OS X 10.12.6, Running latest Adobe apps.

This started when i deleted about 300 fonts from my font book (Main HD>Library>Fonts).  This disabled Premiere for some reason and Premiere would not start (Just try to open and shut down). So I added the fonts back in and Premiere started back up.  I went through the same fonts and trashed them (about a dozen at a time), each time starting Premiere to make sure it was still starting up. I did this until they were all deleted again.  But this time Premiere started. So I think everything is back to normal until today when i sent my premiere project to Media Encoder.

Premiere exports the files just fine. I exported a video file through Media Encoder with no issue. But when a Premiere project tries to export, the encoding shows no progress and no image (I have tried only exporting H.264 and Quicktime H.264 files). After a while of waiting, nothing happens.  I hit stop, it stops.  But then I cannot delete the file (until i restart Media Encoder). When I try to quit, it locks up. I have to force quit the program.  After that, if I was to open it and close it (Without doing ANYTHING), it would still stall out and not close without a force quit.

I have uninstalled Media Encoder several times.  I have uninstalled it, restarted the computer and installed.  I have uninstalled Media Encoder and Premiere at the same time and rebooted and reinstalled both.  Nothing has worked.

Any other options I could try?

I'm trying to encode 4K portrait h.264 .mp4 and I get the following message "Frame dimesions are not supported. Please check that both width/height alues are within limits."

As a temporary work around I'm rendering Landscape 3840x2160 with my content rotated 90 degrees. This will not be good enough in the long run though as I have to produce content for a digital signage player that outputs portrait 2160x3840.

Is there a way to force 2160x3840 or will this resolution be supported in the near future?

Cheers,

R Wallace

I've been running Production Premium on my new Windows 7 64bit, 6GB i7 system for several weeks now and haven't had any issues exporting to the Media Encoder.

I installed the trial version of Dreamweaver without any of the add-on's as I thought they might mess up my licensed installation.

Every attempt to export -> media -> queue get's the following error in AMEEncodingErrorLog.txt

- Source File: C:\Users\Rob\AppData\Local\Temp\someproject.prproj
- Output File: C:\Users\Rob\Videos\someproject.mov
- Preset Used: Custom
- Video:
- Audio:
- Bitrate:
- Encoding Time: 00:00:00
7/8/2010 10:14:34 AM : Encoding Failed
-------------------------------------------------
Encode failed because the source duration is nil.

Doing the export directly from PP works without error, but I don't want to wait for each export to complete.

Any ideas other than reinstall PP?

TIA

We just updated to 2018, and I don't see the same pulldown presets as we had before. First question - what is the different between the System presets (right), and the presets you can get in the pulldown menu in the queue (left)? Second question is how do I recover the longer list of options that we had in 2017?

Hi all,

I have written a 'proof-of-concept' GPU-accelerated H264-encoder for Adobe Media Encoder (CS6).  It requires an NVidia 6xx/7xx series "Kepler" GPU (CUDA capability 3.0), and uses the dedicated GPU's builtin hardware-encoder (NVENC) to offload the H264-encoding process from the host-CPU.  This software is "proof-of-concept", so it's missing some critical features (no interlaced-video support, no AAC-audio or Dolby AC-3 audio), and of course, it could be buggy!  But it's free.

!!!! Disclaimer: NVENC-export is third-party software that is not supported by either Adobe or NVidia.  It comes with no warranty -- use at your own risk.

Software/hardware Requirements:

(1)Adobe Premiere Pro CS6 or Media Encoder CS6 (Windows version)

Sorry, MacOSX is not supported. (NVidia NVENC SDK doesn't support MacOSX.)

(1)NVidia KeplerGPU <GKxxx> with 1GB VRAM or more  (GTX650 or above, GT650M or above)

(Sorry, NVidia Fermi <GFxxx> is NOT supported, it doesn't have the NVENC hardware feature)

Note,if you have MPE-acceleration enabled, keep in mind the NVENC-plugin consumes some additional VRAM because it uses your GPU to perform H264-encoding.

Strongly recommend a 2GB card

(2) Microsoft Visual C++ 2010 SP1 x64 redistributables

          (download this from Microsoft's website)

Installation instructions:

     In Adobe Premiere Pro CS6:

     (1)      On your system, locate the installation-directory for Premiere Pro CS6.

               Usually, this is C:/Program Files/Adobe/Adobe Premiere Pro CS6

    (2)     Copy the included file Plug-ins/Common/nvenc_export.prm

               to <installation dir>/Plug-ins/Common/

     -> To choose the NVENC-plugin in Premiere Pro,

          In the format-menu, select <NVENC_export>

     In Adobe Media Encoder CS6:

     (1)    On your system, locate the installation-directory for Media Encoder CS6.

          Usually, this is C:/Program Files/Adobe/Adobe Media Encoder CS6

     (2)     Copy the included file Plug-ins/Common/nvenc_export.prm

          to <installation dir>/Plug-ins/Common/

     -> To choose the NVENC-plugin in Media Encoder,

          in the format-menu, select <NVENC_export>

Performance & quality notes:

(1) How much faster is NVENC-export than Adobe's built-in Mainconcept H264 encoder?

Depends on your PC system.  On my test-system, which is ordinary desktop PC with Intel i5-3570K (4-core 3.4GHz), NVENC-plugin is roughly 4x faster than Mainconcept. On a dual-socket Xeon Ivy Bridge-E system, NVENC would probably only be 2x faster (in Media Encoder.)

(2)How does the video-quality compare?

Comparing similar settings/video-bitrate, Mainconcept performs better at lower-bitrates(less artifacts).  At medium-high bitrates, NVENC is comparable to Mainconcept.

(3) How does NVENC-export encode the video?

The plugin fetches videoFrames from the Adobe application, then converts the frames from YUV420 to NV12 surface-format (using host-CPU.)  Then it passes the converted frames to the NVENC front-end.  From here, NVENC hardware takes over, and handles all aspects of the video compression. When NVENC hardware is done, it calls the plugin to output write the elementary bitstream (to the selected filepath.) NVENC-hardware does NOT encode audio, nor does not multiplex the A/Vbitstreams -- this is still done in software (on the host-CPU)

The NVENC hardware block has very little CPU-overhead.  But since video-encoding is just 1 step in the entire Adobe rendering path, CPU-usage will likely still be quite high when using NVENC-plugin.

(4) What's the maximum-size video NVENC-export can handle?

H264 High-profile @ Level 5.1, which works out to roughly 3840x2160 @ 30fps. (Note the actual encoding-speed will probably be less than 30fps.)

(5) How fast is the NVENC-export hardware in Kepler GPU?

Assuming the Adobe application host is infinitely fast (i.e. can send video to plugin in zero-time), NVENC-hardware will encode High-profile (CABAC, 2 refframes, 1-bframe) 1920x1080p video @ ~100fps. At 3840x2160p (4k video), the hardware encode-speed drops to roughly 20-25fps.  That is still faster than a desktop PC.

NVENC-speed is generally same across the Kepler family - the high-end Geforce GTX Titan (or GTX780) is no faster than the entry-level Geforce GTX650, because all Kepler models share the same NVENC hardware-block, which is totally separate and independent of the GPU's 3D-graphics engine.

In premiere Pro 6, MPE acceleration will greatly affect how quickly Adobe can render video to the exporter.  So a more powerful Kepler GPU will probalby complete projects faster than a less powerful one (up to NVENC's performance ceiling.)  For more info, please refer to NVidia's NVENC whitepaper at their developer website (public)

(6) I have a multi-GPU setup, can I encode with multiple GPUs?

No, NVENC targets and uses only a single physical GPU.  (You can choose which one.)

Known limitations and problems:

NVENC-plugin is a 'proof-of-concept' program -- it is not a finished product.  So it's missing some features, and other things are known to be broken:

• Interlaced video encdoing does not work at all (not supported in current consumer Geforce drivers)

• Audio support is very limited: uncompressed PCM)

no AAC or Dolby-Digital

• Multiplexer support is very limited: MPEG-2 TS only, using an included third-party tool TSMuxer.EXE

no MPEG-4 muxing (*.MP4)

• When the muxed MPEG-2 TS file in Windows Media Player (WMP), there is no sound.  This is because WMP doesn't recognize PCM-audio in mpeg-2 ts files.  You have 2 choices; you can use a third-party media-player such as MPC-HC or VLC.  Or you can postprocess the audio-WAV file into a compatible format (Dolby Digital/AC-3)

• in the pop-up plugin User-interface, the <multiplexer> tab is missing or not shown properly.

(To fix: Select a different codec, then re-select NVENC_export.)

• Doesn't support older NVidia GPUs (GTX5xx and older, GT630 and lower)

Sorry, NVENC hardware was introduced with NVidia's Kepler family (2012)  Anything older than that will NOT work with the plugin.

Hi,

So I managed to get a hold of the plugin to be able to use .webm files in Adobe and wanted to convert a .webm file at 2MB to "Animated GIF" but it ends up being 150MB. Tried to tweak the settings, but didn't help much. Any solutions? Gif file is too big in other words

Thanks in advance.

AME terminates a job stating: "YouTube - YouTube - File size upload limit is 64GB". The correct file size limit for youtube is 128GB.

This should be fixed

Hi,

I'm using extended script for developing some panel plug ins for media encoder. I'm facing some problem where i have to get the details of each job items. Is there any option to get the details of queue items through extended script in Media encoder?

Hello,

I have been experiencing some serious issues while exporting with Media Encoder CC 2015.2 Release (Build 9.2.0.26, but the problems happened regularly in earlier versions too). The problem occurs when the GPU Acceleration (OpenCL) is switched on, but never with the "Software only" scenario.

The export contains visual glitches (as per the image attached, the face has been deliberately blurred) and happens no matter what the preset is being used to export. As mentioned before, this happens regularly and really slow things down. It happens both with individual exports as well as with a batch export. I've tried cleaning the cache files, delete previews, render files etc... All of these can temporary solutions, but don't guarantee that the glitch won't happened with the next attempt of exporting.

I am working on a Mac Pro with the following specification: Processor: 3.5 GHz 6-Core Intel Xeon E5, Memory: 16 GB 1866 MHz DDR3 ECC, Graphics: AMD FirePro D700 6144 MB. The footage that I usually work with is mxc (Sony FS7), but happened with footage from other cameras too.

As this has been an ongoing issue, I'd really appreciate your assistance and look forward to hearing what the solution may be.

Thanks,

Artur

Hi There,

I've been looking through a number of threads but none of them are particularly new (and therefore outdated) or have answered my question specifically. In short, I am trying to burn a DVD of a short film that I just finished editing. I have zero issues rendering the movie digitally but when it comes to actually burning to a disk directly, I'm out of luck.

The information I'm finding keep instructing me to pick settings best suited for DVDs and then click "Queue" where it will send me to Adobe Encore where I then can work with Menus, timelines, chapters, etc. But this is sending me to Adobe Encoder instead. I'm assuming this is an updated version of Encore since I can't find it anywhere under the Creative App options for Encore.

If this is so, I would think that the instructions would be translatable from the one program to the other but I'm not finding any of these functions at all nor am I finding any options that allow me to burn to a disk outright.

Thanks in advance,

Remington

I Queue my video I made in Premiere pro 2018 and it sends it to Media Encoder.  I am trying to send it to my usb drive and after 2 hours of encoding it says it is done, but there is NOTHING on my usb drive.  Earlier I was receiving a error message:

11/16/2017 03:06:22 PM : Queue Started

- Source File: C:\Users\owner\AppData\Local\Temp\Kyle & Angela  -  Full Ceremony_2.prproj

- Output File: G:\Kyle & Angela - Full Ceremony.mp4

- Preset Used: Custom

- Video: 1920x1080 (1.0), 23.976 fps, Progressive, 01:03:35:11

- Audio: AAC, 320 kbps, 48 kHz, Stereo

- Bitrate: VBR, 2 pass, Target 15.00 Mbps, Max 40.00 Mbps

- Encoding Time: 02:53:37

11/16/2017 05:59:59 PM : File Encoded with warning

------------------------------------------------------------

File importer detected an inconsistency in the file structure of Kyle & Angela - Full Ceremony.mp4.  Reading and writing this file's metadata (XMP) has been disabled.

Adobe Media Encoder

Could not write XMP data in output file.

------------------------------------------------------------

11/16/2017 05:59:59 PM : Queue Stopped

    I searched here and they told me to uncheck the write xmp id  and change the export options to none.  therefore I did but now I am getting nothing on my drive.   Please help  I really don't want to dump all of my work.

hi all,

when i try to render a afx project from media encoder i get the following message

"Could not read from the source. Please check if it has moved or been deleted"

i've read on the forum that this is due to an old installation of Premiere.

I'm using a brand new computer. the only software installed is my cs5 master collection and the updates from adobe website.

win7 pro

i7

16 gig ram

cheers

s

I am a recovering Final Cut Pro user. Switched over about version FCP X 10.3. The railroad tie that broke the camel's back for me was a removed feature I am hoping I can do with Premiere in some way.

In FCP 7 and even FCP X up to 10.3, you had the option of sending a render job to their version of Media Encoder (Called "compressor") just like Premiere Pro can do now. However, you had the option of being able to use a "render cluster" by where if compressor was loaded onto other macs on your network, it would send the job out to one of those nodes or even split it up and send parts of it to several computers to parallel encode the job. Made large jobs faster and allowed you to not have to bog down your processors on you main computer with a render job. Apple just took it out with 10.4, which was a deal breaker for me.

I know Premiere/Media Encoder does not have the ability to split the job up, but was wondering if there as a way I could send a render job to Queue up on the Media Encoder of another system...say my Mac mini server which also has Media Encoder on it. Is there any way to select the path to the Media Encoder and thus have it deploy the render job to the other machine?

Thanks.

This may be a stupid question, but why is AE making so many .aep files? They all start with "tmpAEtoAMEProject", so are they created every time I export to AME? It's making for very hefty folder sizes.

I have a video I created in AE CC 2017.  Never had a problem exporting it to media encoder and rendering H.264 with the Vimeo 1080p preset.  I upgraded to 2018 the other day and today had to make an edit to that video.  I sent it to media encoder and no matter what format I try it continues to fail.  Can anyone suggest a reason why or advise what else I can try?  Here's the log file.  Thanks.

- Encoding Time: 00:39:15

11/21/2017 04:37:42 PM : Encoding Failed

------------------------------------------------------------

Export Error

Error compiling movie.

Accelerated Renderer Error

Unable to produce frame.

Writing with exporter: H.264

Writing to file: \\?\G:\Audio_Video\Career Fair\Short Video Edit 11-13-17.mp4

Writing file type: H264

Around timecode: 00;02;53;04

Rendering at offset: 171.471 seconds

Component: H.264 of type Exporter

Selector: 9

Error code: -1609629695

------------------------------------------------------------

- Encoding Time: 00:39:31

11/22/2017 08:41:49 AM : Encoding Failed

------------------------------------------------------------

Export Error

Error compiling movie.

Accelerated Renderer Error

Unable to produce frame.

Writing with exporter: H.264

Writing to file: \\?\G:\Audio_Video\Career Fair\Short Video Edit 11-13-17.mp4

Writing file type: H264

Around timecode: 00;02;53;04

Rendering at offset: 171.471 seconds

Component: H.264 of type Exporter

Selector: 9

Error code: -1609629695

------------------------------------------------------------

- Encoding Time: 00:39:12

11/22/2017 09:27:58 AM : Encoding Failed

------------------------------------------------------------

Export Error

Error compiling movie.

Accelerated Renderer Error

Unable to produce frame.

Writing with exporter: H.264

Writing to file: \\?\G:\Audio_Video\Capital Video\Graphs v2018_AME\Short Video Edit 11-13-17.mp4

Writing file type: H264

Around timecode: 00;02;53;04

Rendering at offset: 171.471 seconds

Component: H.264 of type Exporter

Selector: 9

Error code: -1609629695

------------------------------------------------------------

- Encoding Time: 00:39:17

11/22/2017 10:12:03 AM : Encoding Failed

------------------------------------------------------------

Export Error

Error compiling movie.

Render Error

Render returned error.

Writing with exporter: H.264

Writing to file: \\?\G:\Audio_Video\Capital Video\Graphs v2018_AME\Short Video Edit 11-13-17_1.mp4

Writing file type: H264

Around timecode: 00;02;53;04

Rendering at offset: 171.471 seconds

Component: H.264 of type Exporter

Selector: 9

Error code: -1609629695

------------------------------------------------------------

- Encoding Time: 00:39:18

11/22/2017 10:53:25 AM : Encoding Failed

------------------------------------------------------------

Export Error

Error compiling movie.

Render Error

Render returned error.

Writing with exporter: H.264

Writing to file: \\?\G:\Audio_Video\Capital Video\Graphs v2018_AME\Short Video Edit 11-13-17_2.mp4

Writing file type: H264

Around timecode: 00;02;53;04

Rendering at offset: 171.471 seconds

Component: H.264 of type Exporter

Selector: 9

Error code: -1609629695

------------------------------------------------------------

- Encoding Time: 00:39:27

11/22/2017 11:33:19 AM : Encoding Failed

------------------------------------------------------------

Export Error

Error compiling movie.

Render Error

Render returned error.

Writing with exporter: H.264

Writing to file: \\?\G:\Audio_Video\Capital Video\Graphs v2018_AME\Short Video Edit 11-13-17_3.mp4

Writing file type: H264

Around timecode: 00;02;53;04

Rendering at offset: 171.471 seconds

Component: H.264 of type Exporter

Selector: 9

Error code: -1609629695

------------------------------------------------------------

- Encoding Time: 00:00:00

11/22/2017 11:42:29 AM : Encoding Failed

------------------------------------------------------------

QuickTime Export Error

QuickTime for Windows cannot export H.264 on computers that have more than 16 CPU cores due to a problem in the Apple H.264 compressor component.

Export Error

Incompatible Video Codec found in the preset. Preset load failed.

Exporter returned bad result.

Writing with exporter: QuickTime

Writing to file: E:\Audio_Video\Short Video Edit 11-13-17.mov

Around timecode: 00;00;00;00

Component: QuickTime of type Exporter

Selector: 9

Error code: 27

------------------------------------------------------------

- Encoding Time: 00:39:19

11/22/2017 12:23:47 PM : Encoding Failed

------------------------------------------------------------

32-bit QuickTime support ending

Support for import/export of legacy 32-bit QuickTime media will be discontinued in a future version of Premiere Pro. Transcode to a non-legacy format to continue using the media in Premiere Pro after legacy support has ended.

Export Error

Error compiling movie.

Render Error

Render returned error.

Writing with exporter: QuickTime

Writing to file: E:\Audio_Video\Short Video Edit 11-13-17.mov

Around timecode: 00;02;52;19

Rendering at offset: 171.471 seconds

Component: QuickTime of type Exporter

Selector: 9

Error code: -1609629695

------------------------------------------------------------