Master the art of compression, share and learn.
Recently active
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!
Hi there,I have a custom Windows computer with a 10 core Intel i9 10900K, with an Nvidea 3070TI. Whenever I render heavy 8K footage, both hardly get over 30% of usage, with some brief spikes for the CPU of 50 to 60%. I have read through multiple posts on Reddit and this forum and I understand that they shouldn't be on 100%. My question for you however is; is this normal, or can I change some setting for Media Encoder or Premiere Pro for it to utilize the horsepower in my PC more. Thanks in advance!
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.
Windows 10 Pro 21H2Driver nvdia: 516.9448-core AMD Threadripper CPU, 96 GB of RAM, RTX 3090 GPU, and all hardrives are SSD.After effects 22.2Adobe Media Encoder 22.6.4 An editor told me the AME encoder is more slow than after effects on this machine. Should Adobe Media Encoder encode as fast as the After Effects Render with the multi-frame rendering option activated? When i am encoding from after effects and one 1080p composition takes 10-5 min to complete on a mov file but on the AME takes almost 1h-40min. The cpu on After Effects encoding reach to the 20% and the ram reach the 80Gb but on AME encoding the cpu reach the 2 % and the ram 5Gb on the AME process and on After proccess reach 2% and 20 GB. When i send a composition to the AME queue, the AME puts the codec h264 and it doesn't keep the codec and the container especified on AFter Effects when i sent it. Is it normal? Do you have noticed this diferent times of encoding? Or maybe something wrong on this machi
When I render videos from AE (H-264), Media Encoder stops working. I reset my computer and redownloaded AE + ME because I thought it was a storage / RAM issue but it's still not working.
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 I have the following problem when upscaling a 1920x1080 mp4/mxf to 3840x2160p. Media Encoder 23.1 in Windows 11 always generates 23.9761 FPS instead of the set 23.976. However, this file cannot be configured e.g. generate as UHD with Tsmuxer. The resulting UHD is then unreadable. Only after the Mp4 runs again with 23.976 in DVDFab can the file be used without any problems, e.g. to create a UHD and burn it to disc. Is that a bug from Adobe or is there a special setting? Does anyone kows how to solve the problem?
I'm trying to make a custom preset in ME to export a bunch (like 100) .dpx files with a custom LUT but I can't get the LUT to appear in the dropdown menu. I've tried using the "select" option and I've made LUTs/Creative and LUTs/Technical folders and restarted ME but only the preinstalled LUTs are displayed. I can add the LUT in DaVinci and export each clip one at a time but that would be very time-consuming. I haven't tried Premiere but it would be a boat of similar size and shape. Am I doing it wrong or is there a workaround? I don't work with LUTs or ME often so any help would be appreciated!
Since the death of flash, many web developers are scrambling for ways to animate websites. WebM is emerging as one of those file types that works well for web. Please add this to the Media Encoder so we can better animate for web AND have small file sizes.
Hey, I am sure that most of us experienced the error that when I put something in queue and the file cant be overwritten, Media Encoder just ditch the render. This happens so many times when you work over local network and its not pleasing when you're dealing with a lot of files, which have to be named correctly. The good thing with Encoder is that it tells you in advance, in Premiere it just renders the whole video and throws it all away just because of this error.There is a simple solution for it... If the error occurs, give me the warning in advance and a new window to save it with other name, dont just delete the whole render... Or just add "_1" to the file name, save and show the error.Deleting the render is the worst option, because I have to render it again just because somebody else is watching the old video... Thanks.
Tried about 20 times and gets stuck at 100%, I've tried all youtube videos. So bought Adobe Encoder and it is the same. QuestionWhen I add the premiere pro file to adobe encoder via add sequence why does it make 10 differnet nested sequences? Is this a error?
Hello, I recently updated my After Effects and Media Encoder to v 23.0.1. In my After Effects, when I go to File --> Export --> Add to Adobe Media Encoder Queue, the file doesn't load into the queue. I've tried adding the aep file to the queue in Media Encoder and I've tried to Add to Render Queue instead of add to Adobe Media Encoder Queue. I've tried turning off parallel encoding in Media Encoder and I have tried changing the renderer to Mercury Playback Engine Software Only in Media Encoder. Neither have worked. Any ideas?
Mac OS 10.11.6Mac Pro 2009 2.7Ghz 8 core20GB 1066 MHz DDR3 ECCNVIDIA GeForce GTX 660 3072 MBSo apparently, AME had the same problem in the 2015 version, it was fixed an now it's back. If I add a Lumetri Color effect to a clip or adjustment layer and queue the timeline to Media encoder, no color effects are render when exporting to AME, only straight from Premiere. Please Adobe, fix it. It was fixed before fix it again.
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
HelloI have a problem with Media Encoder ( error 205)I disabled my antivirus but doesn't work.Do you have a solution please ?Best regards
I am editing a TV commercial and these are the exporting specs requested by the channel. how could i do that? Technical Specifications of Marketing Material for TVC use:VideoMXF Op1a XD CAMHD with Color sub-sampled at a ratio of 4:2:2 50mbps1920 x 1080 pixels in an aspect ratio of 16:9 • 25 frames per second 1080/50i • Long GOP M=3, N=12.AudioTarget Level of -23 LUFS 4ch = 2 Duplicate Stereo Final Mix L1 R1 , L2 R2,Format PCM - Sampling Rate 48.0 kHz Bit depth 24 bits
Windows7 64 bitMedia Encoder CC (7.0.1)AME worked a while. I exported a couple of jobs to it's queue. All good. Tried to cancel the jobs and it seemed to hang. Had to kill the application from task manager.Since then AME will not run. It crashes on startup. No splash screen.. nothing. Appears briefly in task manager then dissapears.I have deleted all files from C:\Users\login\AppData\Roaming\Adobe\Adobe Media Encoder\7.0Have reinstalled PremierProCC after uninstalling and using the cleanup tool.Still no luck. Is there a queue file anywhere that should be deleted? A registry entry maybe?
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.
Hi All,Apologies if this has already been answered somewhere else. We're running a set of 4 AME conforming engines running the latest edition of AME 2017. They're being fed jobs from our asset management system via the webservice & network-based storage and 98% of the time they transcode correctly with no problems. Occasionally we get a failure where it states in the console window "Creating Encoder - Timeout while creating encoder group" and it fails the job. Is there any way of turning on any sort of debug logging in AME? There's nothing about this error in the encoding log and nothing at all in the error log.The AME instances are running on a combination of VMs running server 2012 and Dell servers running 2008 R2. I believe it's more of an issue with our media management system but if there's anyway to get some more information out of AME it'd be greatly appreciated.Thanks
I'm hoping to find a solution to my current issue.At work, we shoot using a BMPCC 6K G2, using Blackmagic RAW.Sometimes, the videographers make minor mistakes with White Balance, or other simple adjustments that are much better and simpler to fix using the BRAW effect rather pulling Lumetri into the equation. Now, when I export directly from Premiere, there are no issues. Output renders as expected. But, when I batch export using Adobe Media Encoder, the output looks the same as the input (meaning the effect was bypassed, and no correction was made). I tried disabling the "Import sequences natively" option, and the issue still persists.I am asking here, since the moderators on the Blackmagic Design forums told me this was an Adobe issue, not a Blackmagic issue. I'm currently working on a Windows 11 Pro PC.64GB RAMAMD Ryzen 7 5800X 8-Core Processor 3.80 GHzGeForce GTX 3070ti Using the latest versions available as of today (2/22/2023) of AME, Premiere, and Black
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
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.