Skip to main content
E
ExodusCry3
Participant
October 24, 2013
Answered

Media Encoder won't queue

  • October 24, 2013
  • 39 replies
  • 113537 views

I'm running the latest build of Premiere CC. I can export sequences without issue but if I try to 'Queue' and send to Media Encoder, it won't show up. Basically, Media Encoder will launch automatically as it should be no job actually get's added...It just sits there. I've waited close to 30 minutes with no success. The behaivor is identical to whenever I just launch Encoder on it's own. Thoughts?

    This topic has been closed for replies.
    Correct answer Mark Mapes

    The AME team is investigating similar reports from other customers. While they have not yet nailed down the cause, the workaround they're recommending is to clear your AME preferences. The easiest way to do this is to hold Shift while launching AME.

    39 replies

    Noel_Sufrin
    Noel_Sufrin
    Participant
    November 30, 2018

    Hi,

    I'm on a PC running the latest CC builds, and with Network access to projects.

    This also happens to me frequently, but I've found that shutting down Media Encoder after it fails to queue, then deleting the temporary files created by Media Encoder in the working project folder will allow me to queue it.

    Hope this helps someone with similar issues.

    Frank Vitale
    Frank Vitale
    Known Participant
    July 16, 2018

    I am having the same problem. I'm on a windows 10 machine.

    Launching AME from AE takes several minutes. I've purged all memory, saved my file, quit and opened it back up.

    Once AME is open there is no file in the que. Adding it again from AE has no effect... I just cant get the file into the AME.

    I'll try a restart,  hopefully it will work, it was working last week (slow but working)

    Frank

    YULoveHIT
    YULoveHIT
    Participant
    April 30, 2017

    this worked for me

    The AME team is investigating similar reports from other customers. While they have not yet nailed down the cause, the workaround they're recommending is to clear your AME preferences. The easiest way to do this is to hold Shift while launching AME.

    S
    St3ph3nH4rv3y
    Participant
    February 22, 2017

    was this ever fixed by adobe - im still getting these problems - ill send 30 files over to encoder to encode and will typically only get about 23-25 over. the other ones i have to do manually within premiere

      hoptocopterfilms
      hoptocopterfilms
      Participant
      September 6, 2016

      We were able to fix this problem (on a Mac) by going to...

      Documents>Adobe>Adobe Media Encoder

      Documents>Adobe>Premiere Pro

      ...and deleting everything out of there while both AME and Premiere Pro were closed. Then we restarted the programs, which rebuilt those folders. Sorry, not sure exactly which of those folders were the one that fixed the problem, but one of them definitely was.

        M
        massimom12881131
        Participant
        May 31, 2017

        hoptocopter2​

        Wow! This has worked for me, thanks a lot!

        We were able to fix this problem (on a Mac) by going to...

        Documents>Adobe>Adobe Media Encoder

        Documents>Adobe>Premiere Pro

        ...and deleting everything out of there while both AME and Premiere Pro were closed. Then we restarted the programs, which rebuilt those folders. Sorry, not sure exactly which of those folders were the one that fixed the problem, but one of them definitely was.

          G
          GKubera
          Participating Frequently
          July 27, 2016

          Damn...as soon as I "upgraded" to PremierePro 2015.3 and Media Encoder 2015.3, ALL functionality in Media Encoder STOPPED.

          Well...I CAN add files to the Queue, but after that NADA.  Can't open the Pref's or Save the Queue!  When I try to start the Queue, it simply sits there.  I have a 2-hour concert I'm trying to get finished, as we have another shoot TONITE!

          I've tried most of the suggested fixes...Shift @ startup for AME, un-install & re-install...same old stuff.

          The software DOES work on my laptop however, but I don't have all the plug-ins available on that machine to do 3D, which is my big thing these days.

          Mac OSX 10.9.5 (Maverics) on both machines, and the latest CC apps installed...

          I SIMPLY DON'T HAVE TIME FOR THIS!!!

          pax-

          GKubera/HyperopicMedia

          G
          GKubera
          Participating Frequently
          July 27, 2016

          ...then the damn thing crashes with the following error report:

          Process:         Adobe Media Encoder CC 2015 [498]

          Path:            /Applications/Adobe Media Encoder CC 2015.3/Adobe Media Encoder CC 2015.app/Contents/MacOS/Adobe Media Encoder CC 2015

          Identifier:      com.adobe.ame.application.CC10

          Version:         10.3.0.185 (10.3.0)

          Code Type:       X86-64 (Native)

          Parent Process:  launchd [231]

          Responsible:     Adobe Media Encoder CC 2015 [498]

          User ID:         501

          Date/Time:       2016-07-27 13:42:07.529 -0500

          OS Version:      Mac OS X 10.9.5 (13F1911)

          Report Version:  11

          Anonymous UUID:  DA9A622B-4AEE-4FCA-A357-889CCC920875

          Crashed Thread:  0  Dispatch queue: com.apple.main-thread

          Exception Type:  EXC_CRASH (SIGABRT)

          Exception Codes: 0x0000000000000000, 0x0000000000000000

          Application Specific Information:

          terminating with unexpected exception of type dvacore::filesupport::dir_not_found_exception: The directory '/Users/greggkubera/Documents/Adobe/Adobe Media Encoder/10.0/Presets' could not be found.

          abort() called

          Thread 0 Crashed:: Dispatch queue: com.apple.main-thread

          0   libsystem_kernel.dylib         0x00007fff936a5866 __pthread_kill + 10

          1   libsystem_pthread.dylib       0x00007fff939aa35c pthread_kill + 92

          2   libsystem_c.dylib             0x00007fff9312fbc6 __abort + 145

          3   libsystem_c.dylib             0x00007fff9312fb35 abort + 140

          4   libc++abi.dylib               0x00007fff93fcdf31 abort_message + 257

          5   libc++abi.dylib               0x00007fff93ff393a default_terminate_handler() + 240

          6   libobjc.A.dylib               0x00007fff942f4322 _objc_terminate() + 124

          7   libc++abi.dylib               0x00007fff93ff11d1 std::__terminate(void (*)()) + 8

          8   libc++abi.dylib               0x00007fff93ff1246 std::terminate() + 54

          9   libc++abi.dylib               0x00007fff93ff3969 default_unexpected_handler() + 23

          10  libc++abi.dylib               0x00007fff93ff1195 std::__unexpected(void (*)()) + 6

          11  libc++abi.dylib               0x00007fff93ff1b82 __cxa_call_unexpected + 129

          12  com.adobe.AMEFrontend.framework 0x00000001018b0f32 AME::Frontend::AMEFrontendMain::Release() + 130

          13  com.adobe.AMEFrontend.framework 0x0000000101894a42 AME::Frontend::TerminateAMEFrontend() + 34

          14  com.adobe.ame.application.CC10 0x000000010001ab77 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 10103

          15  com.adobe.ame.application.CC10 0x0000000100053919 main + 409

          16  com.adobe.ame.application.CC10 0x00000001000032d4 start + 52

          Model: MacPro3,1, BootROM MP31.006C.B05, 8 processors, Quad-Core Intel Xeon, 2.8 GHz, 16 GB, SMC 1.25f4

          Graphics: NVIDIA GeForce GTX 680, NVIDIA GeForce GTX 680, PCIe, 4096 MB

          Memory Module: DIMM Riser B/DIMM 1, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x802C, 0x3138484632353637324A4438304545314434

          Memory Module: DIMM Riser B/DIMM 2, 2 GB, DDR2 FB-DIMM, 800 MHz, 0x802C, 0x3138484632353637324A4438304545314434

          Memory Module: DIMM Riser A/DIMM 1, 1 GB, DDR2 FB-DIMM, 800 MHz, 0x80AD, 0x48594D5035313241373243503844332D5335

          Memory Module: DIMM Riser A/DIMM 2, 1 GB, DDR2 FB-DIMM, 800 MHz, 0x80AD, 0x48594D5035313241373243503844332D5335

          Memory Module: DIMM Riser B/DIMM 3, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x802C, 0x333648544635313237324638304545314434

          Memory Module: DIMM Riser B/DIMM 4, 4 GB, DDR2 FB-DIMM, 800 MHz, 0x802C, 0x333648544635313237324638304545314434

          Memory Module: DIMM Riser A/DIMM 3, 1 GB, DDR2 FB-DIMM, 800 MHz, 0x802C, 0x3948544631323837324A5938304545314434

          Memory Module: DIMM Riser A/DIMM 4, 1 GB, DDR2 FB-DIMM, 800 MHz, 0x802C, 0x3948544631323837324A5938304545314434

          AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (5.10.131.36.16)

          Bluetooth: Version 5.2.7f4 15858, 3 services, 22 devices, 1 incoming serial ports

          Network Service: USB Ethernet (en2), Ethernet, en2

          PCI Card: NVIDIA GeForce GTX 680, Display Controller, Slot-1

          PCI Card: NVIDIA GeForce GTX 680, NVDA,Parent, Slot-1

          PCI Card: pci104c,8235, IEEE 1394 Open HCI, Slot-3@7,0,0

          Serial ATA Device: WDC WD1003FZEX-00MK2A0, 1 TB

          Serial ATA Device: ST2000DM001-9YN164, 2 TB

          Serial ATA Device: WDC WD2002FAEX-007BA0, 2 TB

          Serial ATA Device: Samsung SSD 850 EVO 250GB, 250.06 GB

          Parallel ATA Device: PIONEER DVD-RW  DVR-112D

          USB Device: Hub

          USB Device: TranzPort

          USB Device: Mass Storage Device

          USB Device: USB2.0 MFP(Hi-Speed)

          USB Device: Bluetooth USB Host Controller

          USB Device: Hub in Apple Pro Keyboard

          USB Device: USB-PS/2 Optical Mouse

          USB Device: Apple Pro Keyboard

          FireWire Device: ProFire 2626, M-Audio, Up to 400 Mb/sec

          FireWire Device: built-in_hub, Up to 800 Mb/sec

          Thunderbolt Bus:

          Kevin-Monahan
          Community Manager
          Kevin-MonahanCommunity Manager
          Community Manager
          July 28, 2016

          Hi GKubera,

          I would look at 2 things.

          1. NVIDIA drivers could possibly be too new.
          2. OS X may need to be updated to OS X 10.10, or later.

          Regards,
          Kevin

          Kevin Monahan - Sr. Community and Engagement Strategist – Adobe Pro Video and Audio
          T
          tombone98
          Participant
          July 12, 2016

          This worked for me after a lotta frustration.

          I went Window > Workspaces > Reset "Default Workspace"…

          Bam, there was the queue with all the sequences I had tried and failed to load up. : )

          Tommy

          cs6

          M
          marcoshirano
          Participant
          July 12, 2016

          Thank you so much @tombone98. This was ridiculous!

          It was just a matter of missing Queue window! Unbelievable.

          Anyway this would never bother me again. lol

          T
          tombone98
          Participant
          July 14, 2016

          well my Queue window was there okay, it was blank and I couldn't find a way to add anything to it.

          I kept coming back trying different things every day, giving up every day.

          So Window >Workspaces > Reset "Default Workspace"… worked for us. yay!

          A
          Anonymous
          April 4, 2016

          Have just started having this problem with AME 9.2.0.2.6. Premiere 9.2.0.

          I can drag into the queue and open via AME, but hitting queue from prem doesnt load it into AME.

          Have tried holding shift to reset preferences upon launch. Have also tried reinstaing Premiere and AME to no avail 

          I've filed bug report. I encourage others to do the same: Feature Request/Bug Report Form

          J
          jakejake89228495
          Participant
          January 12, 2016

          I have the same problem above, for now just continue exporting it directly in premiere. I also noticed that I can not send the sequence from Premiere to After Effects. This might also be part of the glitch. This is weird. Thanks

          N
          nicholtl
          Participant
          January 13, 2016

          Has Adobe figured out a solution to this yet, now that we're all freshly updated to CC 2016?  Holding down the shift key (which I've not yet tried) isn't really the best permanent solution...

            PZombley
            PZombley
            Participant
            February 25, 2016

            Mac 10.10.5

            Premiere Pro Release 2015.2 build 9.2.0 (41)

            Media Encoder Release 2015.2 build 9.2.0.26

            restarted

            opened premiere pro and queued (unsuccessfully)

            quit media encoder

            held shift and started media encoder

            quit media encoder

            held shift and started media encoder (held shift down until it finished loading)

            This worked for me.

            Robbie. W
            Robbie. W
            Participant
            December 22, 2015

            I found a pretty convenient work around, as I'm also having the same problem.

            Instead of trying to "Queue" the sequence from Premiere Pro, simply open Media Encoder, and drag the sequence from the project window in Premiere Pro that you wish to export and drop it onto the Media Encoder application window.

            OR

            In Media Encoder, you can hit the '+' symbol in the top left corner, or File > Add source... or ⌘+i and find the Premiere Pro project you're working on, and open that. You'll then be prompted which sequence you'd like to import.

            It's not the best solution, but it is a solution for now and will let you export multiple sequences at once.


            Hope that helps!

            Show more replies
            Terms & ConditionsAccessibility statement
            Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices