Bug Reports

Hello everyone! I support a team that produces media for TV broadcast and we use two primary file types.Our broadcast playout and capture format is primarily MXF OP-1a wrapped XDCAM HD (or EX) files with embedded caption data (EIA-608 & 708).We use AME to transcode those broadcast format files to H.264 with sidecar SCC caption files for upload to our on-demand platform. This specific transcode is where AME has been broken for several versions now. I'm trying to determine if the bug that Adobe announced regarding AME verison 15.0 has been resolved yet. This bug kept all caption export options from appearing if your source media had embedded captions. My team is currently stuck on AME version 14.9 because we need this feature and that's the last version that had it working. There is a work around involving exporting from Premiere into AME, but that requires two apps and complicates what was a simple workflow, so not a long term solution. I've tested every major version of A

I have a series of EXR files tagged in the metadata as 60fps, but AME and Premiere both ignore this, and instead import the sequence as the indeterminate frame rate set in preferences, which defaults to 29.97fps. Therefore, if I were to export to another 60fps video format, AME would perform an unnecessary frame rate conversion on the clip.

MEDIA ENCODER trial expired before I got all of Adobe pgms installed. Newest verson. windows 10with all latest updates.

I am working on a project that includes a lot of 4k .mxf footage captured using a Sony Fx9.  When exporting multicam sequences the .mxf camera is output as a scrambled image (see attached).  The footage will play normally, in the premiere pro timeline, but I cannot seem to be able to get the footage to export properly. This has happened in multiple projects in both multi-cam and regular sequences.   I have tried to delete and re-import the affected clips in Premiere Pro.I have tried to delete and rebuild the media cache by deleting it from within the app and by manually deleting the cache from the library.I have updated the sequence settings and switched preview files to quicktime, pro res 422.I have updated to the latest version of Media Encoder v23.3 Build 57 None of these has worked and I am at wits end - please help!  Here are my export settings: Editing on a 2022 Mac Studio M1 Max system. Thanks in advance! 

I am currently using Adobe Media Encoder Version 23.2.1 and have noticed that the export time of a video created in Adobe After Effects 23.3 has greatly increased. I am currently exporting a 40 second video and it has taken 20 hours and still states that there is 2 hours and 40 mins left. The footage I have used is 1920x1080 (1080p Resolution) and the plugins I have used are Twixtor and Sapphire. Other edits made were basic 3D Camera Tracker and simple position and scale transformations. Im not sure why it is taking this long just to export a 40 second video as previous video using similar plugins have taken much less time. For previous video exports I used both 2022 Media Encoder and After Effects. Computer Specifications:PC: Alienware Aurora R7OS: Windows 10 HomeOS Build: 19044.2728Processor: Intel(R) Core(TM) i7-8700 CPU @ 3.20GHz 3.19 GHzRam: 16.0 GBGraphics Card: NVIDIA GTX 1070 

I've noticed if I set up a large number of files to proxy or transcode, over time my system gets slower and slower and slower and the items in AME get slower and slower and slower to render. and the application is so, so sluggish to respond. I find I have to constantly quit the software (which can take a long time to properly do), and restart it to get it to a normal render pace again. For large lists I end up using other, more reliable and speedier applications. But I would prefer to just use AME. 🤷‍♂

So Media Encoder Strictly Refuses to do its job across 4 of my computers, the main computers have the following hardwareGTX-3060 12gb2TB of Storageit has been around 4 months of not being able to render anything from Media Encoder, nothing i try works, about a week ago there was an update for my Pc and Media Encoder and then i was able to Render one short video, the next day...Nothing! My computer should have no isssues with these Renders as they are just short recordings of my work in Maya. Even when i rebuild the project on a laptop nothing works for me, What is the Deal with Media Encoder?? Does anyone have any clues on how i can get PC Rendering again??it sometimes says my usable memory shoots down to between 1 and 3 GB when using media encoder, which makes no sense, This PC is Rather beastly Can somone please help me?? im using current Versions of everything, im trying to Render in H.264 i have tried quicktime, nothing wants work, i have erased the cache, gave media

Projects from Premiere Pro were rendering slowly. They started fairly fast, then slowed down as the render continued. I rolled back to v23.2.1 and it is not rendering much, much faster. In fact, it finished an hour long project in 7-8 minutes. With 23.3, the same project ran for 10 minutes, slowed down, and the remaining time counter started going back up instead of counting down. I eventually stopped the render, rolled back to the previous version, and finished the job in a jiffy. There's definitely an issue in v23.3.

when i export with PR is so good, but when  render in Adobe Media Encoder, Final video only display: "Media Offline" , Im use PR and ME is version newest by i had buy them with auto update

When trying to change or edit the title of a video in AME, using the arrow keys causes the Save As screen to close instantly.

Hi, I have a new problem that I didn't have before in this program. I get this error message when I try to export a file from After effects to media encoder. Does anyone know how this can be solved?  

When encoding a PP sequence in ME, if the source range is set to Work Area when in PP in the Export pane, I am having the in-out points change when more than one preset is applied to a single source. In ME I check the export settings for that source, the first instance will show the in-out points to be the full work area from PP when I apply a any number of additional presets and check the export settings those instances all will show a truncated in-out points on the out point end.  (see screen captures of the in-out points).  Changing the range to Entire Range will return the in-out points the full sequence (work area).  Or I can manually extend the out point - which creates a Cusotm range.   This behavior does not happen when encoding a PP sequence in ME if the source range is set to Entire Sequence when in PP. Am I missing something?

I've got a lower 3rd, created in after effects, then exported and used several times in Premiere Pro. The first line of text has the font as all caps. This works in AE, and Looks fine in Premiere. It Previously even worked in Media Encoder. Suddenly (probably after the latest AE update), the titles are staying all caps, Except for "h" and "v". There could be other letters, but of the few names, those are the two letters that it happened to. It only happens in Media Encoder, so seems related. If not, well, it's still a bug that Adobe should look into.

When transcoding from Canon MXF to ProRes 422. Media encoder seems to use excessive CPU resouces, is slow and then crashes part way though the batch convert. Wondering if other have had this problem and is Adobe aware of this? I'm using Mac OS Monterey 12.6.4 

Hello,When certain projects are exported from Premiere Pro and sent for encoding to Media Encoder an error message is popped up saying “A font that is required for this encode has changed. Please restart the encode”. See the following screenshot.The issue is intermittent. This happened when the system font is used, and Monotype is not used. Please let me know how we can mitigate this.

Media Encoder stops uploading when the window is minimized!

Hello, I am a user of a macMini M1 with 16gb of ram. I was using Media Encoder version 2022 and when I upgraded to version 2023I noticed that exports were extremely slow. What used to take 2 hours now takes 6.Has anyone had the same problem? I ended up downgrading to version 2023 againas the edit pack update didn't bring much benefit. Kind regards.

When rendering a simple 3min 1080p video, AME is using excessive CPU power and taking over an hour to render. This wasn't an issue until I updated to AME & Premier Pro 23.  Activity Monitor: Here are my computer specs: Tried switching hard drives, exporting to different locations. Tried both Hardware and Software encoding. CBR and VBR 1 Pass. The issue still persists. Any else experiencing this issue or have suggestions on how to fix it? 

Hello,have a  Workstation (Windows 10 Pro) based on Supermicro Mainboard X11DAi-N, BIOS 3.8a with 2 Intel Gold 6240R CPUs.If in the BIOS under   Advanced / ACPI Settings                 NUMA    disabled The Encoding stops with Error message.If in the BIOS under   Advanced / ACPI Settings                 NUMA    enabledEncoding is OK.Has any one an idea ??Thanks in advanceHeinz1 April 2023 

I am experiencing the following when exporting an MPEG file from Media Encoder (based on the H264 export preset). The file that is output always has an extra frame added to the end (displayed as black). So a 15 sec video becomes 15 secs and 1 frame. If I deselect "export audio" inside the export settings the file exports without this extra frame. I've seen a fair amount of discussion about a similar issue on Premiere Pro forums, but to be clear this happens without Premiere Pro involved. So it is something else. I have exported an MPEG of the same file directly from Avid Media Composer and there is no extra frame at the end. Does anyone have any thoughts on this one? And no it has nothing to do with export range before you start explaining about playhead position and in and out points. Even if I reduce the outpoint the new file will have an extra frame of black added.

Program wont launch, hangs up on the start screen.  All other Abobe programs run fine.  Seems to hang up while loading Arriraw.prm 

I used Media Encoder 23.2 via Premiere Pro 23.1 on Win11 to create a series of PNG sequences from a couple of videos. The sequences were put into separate directories. After the processing was done, I found that in about 25% of cases, the outputed PNG files had switched to a different frame size at some point while processing. It's clear from the file dates/times that it happened while it was processing the whole sequence. How could this happen? It "acts" as if when I had PP adds a new job row to ME, the new job's frame size causes the current "in progress" job to switch frame sizes, as if the frame size if a single global variable. This is very time wasting and I cannot believe a bug this basic is present.

My ME version is 23.2.1,Windows 11 25324.1000.I'm not sure if the problem I encountered can be reproduced on other computers, so I'll say what I encountered and how to deal with it:After the update, my ME can not open, first read ImporterARRIRAW.prm unresponsive, then delete, read ImporterMXF.prm stuck there, no unresponsive, after deleting I can enter the software.So is this a problem with my system or is it a software incompatibility problem?

Dear community,maybe you can help me out with my issue.I am using AME (currently 2023.2.1) in 4 instances, each running on DL360 with an nVidia P1000 hardware, overall running pretty smoothly. The encoders are orchestrated by Helmut4 IO by Moovit which assigns each instance its encoding jobs.When encoding is done or failed, the source files are moved to a folder, either "processed" or "unprocessed". Since some time now, some MXF files are kept AME so that they cannot be moved or deleted, though the encoding process is finished - this leads to a whole bunch of files in the watchfolder. Other filetypes like MP4, MOV, MPG and so on are doing fine.The only way to move or delete the files is to close the AME app - even a restart of the AME doesn't help here, the files are still kept from deletion by AME after a restart.As closing, moving the file and reopening the application after each transcoding takes a bit of time, I'd like to have it the way it was. Nothing unusual in the AME logs.UPDA

And this has been bugging for years.On Intel Macs and My M1 Max 16" Macbook pro. AME 2021, 2022 both do not finish packaging the file resulting in a 51kb file. Generally if I go back to 2020 it will work properly but now I can't download that version.