Skip to main content
L
Laura24181386ed1z
Participant
November 16, 2023

Media Encoder stuck on 'Ready' when encoding mxf files

  • November 16, 2023
  • 12 replies
  • 1405 views

Frequently we are finding that Media Encoder is unable to encode when the source video is MXF. It never progresses from a ‘Ready’ status.

 

Steps to Reproduce:

  • Create a new project in Premiere with the MXF loaded
  • File -> Export -> Send to Media Encoder
  • Go to ME
  • Start  Queue
  • Start button becomes a ‘Pause’ button
  • The job stays in a ‘Ready’ status and does not encode (screenshot attached)

 

Tested using Premiere 23.6 & 24.0 and ME 23.6 & 24.0.2 on a VM with spec:

  • Windows OS 11
  • NVIDIA Tesla T4 16GB Graphics Card
  • 28GB RAM
  • AMD EPYC 7V12 4-core 2.65ghz CPU
  • (also on laptop with much reduced spec)

 

The test was to encode as H.264 mp4 format, preset - match source. Changing encode options / presets doesn’t seem to have any effect.

 

I've attached the media info for an mxf file that we used to replicate.  

 

We found various community posts with a similar sounding problem but none of the fixes worked.

 

 

12 replies

Greg Bracco
Greg Bracco
Participant
December 18, 2023

I recently upgraded the version of PP and ME to 24.1 and all is working now.

A
Assaf Hermel
Participant
December 17, 2023

I got the same problem with the MXF. for years I transcoded mxf with encoder, Now in the 2024/23 version it crush the encoder. the Premiere have reading problem of MXF and don't open projects with Mxf inside.

I really don't get it, How come that we in the 25 version of premiere and encoder and we got new problem from thing that work great before????

    E
    Adobe Employee
    eckiAMETeam
    Adobe Employee
    November 24, 2023

    I tested with MXF (from Sony FX9) on Windows 11 version 21H2 on a Surface Book3 (GeForceGTX 1600 Ti with Max-Q Design) using Adobe Premiere Pro 24.1.0.85 and Adobe Media Encoder 24.1.0.68. Seems to work fine here. Can you share an example of those MXFs that you are facing issue? I can private message you with instructions.

    L
    Laura24181386ed1zAuthor
    Participant
    November 23, 2023

    Hi, 

    We have tried both with and without acceleration to no avail.

    Thanks,

    E
    Adobe Employee
    eckiAMETeam
    Adobe Employee
    November 22, 2023

    In the Queue Panel, you can switch to "Mercury Playback Engine - Software Only" to switch off GPU acceleration.

    Technical Director
    Technical Director
    Known Participant
    November 22, 2023

    I am finding the same issue. Butr today after reading this postingn I decided to try some files other than .mxf. I used .mp4 and low and behold the issue I was having on my system went away. ME worked no problem

    L
    Laura24181386ed1zAuthor
    Participant
    November 21, 2023

    That's right.

     

    Can you confirm what you mean by software only?

     

    We tried to toggle the import sequences natively option but it made no difference.

     

    Lads

    E
    Adobe Employee
    eckiAMETeam
    Adobe Employee
    November 21, 2023

    So on Windows 11 would be to send MXF-based projects from Premiere Pro to AME and encode them to H.264 using H/W Acceleration, right?

    Did you try Software only? Did you try to toggle "Import sequences natively"? Please LMK any outtcomes.

    L
    Laura24181386ed1zAuthor
    Participant
    November 21, 2023

    Hi,

    We're tried these steps and are still facing the same issue. 

     

    Laura

    E
    Adobe Employee
    eckiAMETeam
    Adobe Employee
    November 20, 2023

    Did you try the following standard recipes? –

    Can you please try the following:

    1. Make sure that versions of all apps match (required for DynamicLinkManager to work correctly).
    2. Verify your own AntiVirus / GateKepper setup. If applicable, deactivate temporarily to verify.
    3. Quit all DVA apps.
    4. Use Activity Monitor / Task Manager to kill DynamicLinkManager if it still runs. (On Windows, you need to open the Details tab to see dynamiclingmanager.exe in TaskManager.)
    5. Launch AME first.
    6. Open & export the project again.


    Please let me know if this workaround works for you.

    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