Adobe Media Encoder

I keep creating a new preset based on HQ108p but crucially switch the captions to none.I have several videos queued and either when applying this preset or in the middle of the output process, some videos export with burnt in.  The number of times I have created a new preset only to exhibit the above.Any ideas as to why? NB: the videos also get exported low res with sidecar and this works fine.

I'm trying to export a .ts file but it only allows a .m2t file. The video playback system in a hospital only takes a .ts file extensions. I'm choosing:Format: MPEG2Multiplexing: TS What else???Any ideas?

"error": {"code": 401,"message": "Request had invalid authentication credentials. Expected OAuth 2 access token, login cookie or other valid authentication credential. See https://developers.google.com/identity/sign-in/web/devconsole-project.","errors": [{"message": "Invalid Credentials","domain": "global","reason": "authError","location": "Authorization","locationType": "header"}],"status": "UNAUTHENTICATED"}}Help meAlthough I tried searching for related topics, I couldn't find a solution that completely solved this problemWhen I render and publish to YouTube: Small files work successfully, but high-capacity files show the same error.

I am using Windows 11 Pro, and everything is updated to the latest version, including firmware and BIOS. My sound system is the Asus ROG Strix X570-E Gaming, utilizing onboard sound.I have noticed that Adobe Media Encoder (AME) does not save the ASIO renderer, and it seems that AME does not even use it at all. However, my onboard sound works perfectly with other programs, such as foobar2000 with the ASIO plug-in. Tech Specs

When rendering a h264 mp4 through media encoder my video looks broken in certain areas as you can see in the screenshot. It just clips some dark colors. What can I do? This is realy bad as it is really subtle but plain broken. 

I am using After Effecs CC and I am trying to open the .aep file in Adobe Media Encoder CC (to export as a MPEG file).  I am getting an error stating: "Could not connect to Adobe After Effects.  Please verify that Aobde After Effects and Adobe Dynamic Link components are installed".  I have both AE and AME open and running.  In the menu for AE I have the Dynamic Link menu available.  However, when opening the .aep file in AME I always get this error.-Dave

Encoder updated last night I believe and all my presets were wiped. Now when I use ingest it will not encode to a destination even just my desktop. Log says "Cannot find location" Attached images.

Hi all - Hoping to find a solution to save me time. I have two videos built in Premiere that share assets, one built in 1x1 and one in 9x16. Both of these videos have a .psd file in them that contains a date. I need to create this same video in both aspect ratios for roughly ~30 dates. The issue I run into is if I send to media encoder, I need to wait until all files begin encoding before editing the .psd file or the asset gets updated across all the files previously sent (I learned this the hard way.) Ideally, I would like this to be my workflow: (Update .psd file with date > send to media encoder > update .psd file with new date > send to media encoder) times x, and then > encode.  Currently, I have to update .psd > send to media encoder > wait to encode > and repeat. As you can see, this takes significantly longer. Any ideas? Is there any way for the .psd file to be saved to its last state before sending to the encoder, and then it

Hi, I'm trying to automate transcodes of ProRes RAW material by using either Premiere or Media Encoder.Currently, my best option is to use a source effect preset in Premiere to set the source color space and then apply a LUT on export. It is a bit of a manual process though and I'd like to write a script to do it automatically.The best thing would be to just use Media Encoder and not have to involve Premiere at all, but I can't change source settings of multiple clips at once.I was looking through the scripting documentation for both Premiere and AME but couldn't find a way to change the source color space. Am I missing something?

Recently upgraded to Premiere Pro 2024 across 3 edit suites at our UK broadcast place.We have different generation Macs and playout equipment but the results are the same.We've experienced audio glitches whenever we export through Media Encoder at every audio edit point that doesn't have a cross fade or effect on. This includes cuts that are just 'thru edits' (part of the trouble shooting test)Where these cuts are on the sequence corresponds with audio dropout of approx half a frame on whatever audio track has the edit. These are audible dropouts despite the tiny size.This is manifesting across all suites (Studio, iMac, MacMini in Monterey and Ventura) and using a number of output formats: XDCAM MXF, ProRes, Wav, AS11All create the same result on every (hard) audio edit point.Our workaround is to export direct from Premiere Pro as that doesn't seem to create the same issues - but that then precludes the use of ME entirely and makes the workflow quite tricky.There is also another glitch

I am editing my videos on a NAS system with proxie files and attached offline media files.But I cannot export these timelines in Media Encoder. I get a warning that there are missing media files (original UHD files), but I can export every single timeline directly from Premiere without any problems.So I guess this is some kind of bug?I am using an M4 Max Studio with the latest Premiere / Media Encoder version 25.2.3 / 25.2.

Hi everyone,I encounter an issue when rendering a video from Premiere Pro via Media Encoder. The error can be seen in the attached image. Sometimes, I only need to close the Encoder app and reopen it to continue rendering, but other times it requires me to restart my computer to proceed. This can be very inconvenient at times.And sometimes, after closing and reopening the Encoder app, it remembers the links that haven’t been rendered yet. However, other times, it deletes all the links that were either rendered or in the process of being rendered when the error occurred.Can anyone help me fix this error? Many thanks.  

Hallo, ich versuche seit zwei Stunden, ein Video über den ME zu exportieren. Nach nicht mal einer Minute hängt sich der Encoder (jede Version davon) auf. Es ist zum rasend werden. Es ist nicht mein erstes Video, alle anderen haben funktioniert. Seit dem letzten Update ist nix mehr zu wollen. Er friert einfach ein (keine Rückmeldung) und ich muss ihn schließen. Kann mir jemand weiter helfen?

hiim trying to export a video for use in a unity3d ipad app, and im having trouble getting the colour to export correctly.  My video ends in a particular blue colour and ive so far been unable to get an export out of media encoder that will give me the same blue as in the source. would somebody be able to suggest some settings i could tweak? thanksNick

I'm trying to make a time lapse video from still  images from a dslr.   When I stitch clip together, jpegs are 5 seconds long. please advise. Thanks F

Hi,I have a large clip (1-1/2 hours long) I have exported via ME as 4K and it corrupts the finished file after around the 2 minute mark. ME completes the export but with the corruption.I have tried a second time only to receive the same issue.What are the best practice work arounds for solving this issue?Is there a cache file that I should consider deleting?I'm currently rendering the entire clip and hope this helps remove any issues.

I keep trying to export a h.264 but AME keeps exporting an empty mp4 and an xmp file. Is there any way to merge the two or fix the issue? 

   

Hi all!I've spent most of yesterday and last night creating proxy files from my camera footage and it has worked fine but there is one clip that is taking absurdly long. It's from the same camera, same settings, etc but while other clips of similar length have taken 30-45 minutes to convert this one is going strong at 9 hours and planning to need another 12! This seems absurd. Any thoughts on what might be going on?The footage is shot on a Canon R5, mostly at 50 fps (some 25fps), 3840x2160 interlaced. I'm converting from MXF OP-1a AVC to just the standard ProRes QuickTime Proxy-Half that Premiere defaults to. omg I just noticed that it has misinterpreted all of my footage as progressive?! So it thinks all my raw footage is progressive and is therefore matching the proxies to also be progressive. Is this a whole other nightmare or possibly related? Anyhow, I'm on a MacBook Pro 2019, running Sequoia 15.3.2, 32GB Ram, 8-Core intel i9, all the newest app updates installed. (I don

I have a few dozen watch folders, with custom presets for each one. They crop the video (under Preset Source) then apply an overlay.Works perfectly... until today.Every Custom Preset in my list, the Source Crop has been reset to 0, 0, 0, 0. Now the video under the overlay has an extra black bar, because the video is "too wide" under my overlay.Even though I backed up the Preset file, with my customs, I do not see where the CROP LEFT , RIGHT, TOP... etc appears in the file so I might try to fix with a find/replace rather than manually set each preset again.I anticipate having MANY MANY more folders and such Presets in the future, where such a "glitch" would ruin my workloads.Any ideas on how to prevent / lock these Presets from being glitched by updates? Or how to fix the current present file with a search / replace?Thank you! 

This is a question from a user not myself. They can't seem to disable caption burning in Media Encoder 25.2. Wasn't sure how to assist them so I thought I'd ask here

Not sure how to resolve this, but ME takes up gobs of memory during the encoding process no matter what I seem to do to alleviate it in Premiere. You can see screenshots below (but total memory was up to 98.63 GB when it finished). In general, I've been trying to export a 1-hour long video. Originally shot on iPhone (.mov) and encoding to MP4. My system would either crash after an hour or so of encoding. I think converted the MOVs to MP4s and tried that approach before encoding, but same issue. I had to cut the video to 30 minutes just to get an export to work. There has to be a way to improve the memory usage on my system for this task.I'm running an M2 Mac, 24 GB, Ventura (can't upgrade just yet). I had all applications closed and only using ME. I was also using Hardware encoding (Metal). I tried Software encoding but it crashed on that as well (and 10 times longer to encode). I even tried medium bitrate but didn't make much difference.It seems like ME is super inefficient with

I have been trying to figure out how to convert voice recordings to Mp3 so that i could burn them on a cd, so i downloaded this thing. It was working at first... or so I thought. I just wanted to make some bad music to make my friends laugh, but for every couple of songs it converts correctly, It slows down a couple half seed, making it sound lower, and then it cuts off at the same it would if it was going the regular speed. I'm not doing anything different to them and I don't know why they are lowing down. I'm on a time crunch please help me.

My computer specsWhen I exported the videos, the progessfailedHere are the logs - Source File: G:\My Drive\Project\x4.prproj - Output File: G:\My Drive\Final\2025-04-09 21h 14m 22s.mp4 - Preset Used: Custom - Video: 3840x2160 (1.0), 30 fps, Rec. 709, 203 (75% HLG, 58% PQ), Hardware Encoding, Nvidia Codec, 00:42:25:17 - Audio: AAC, 320 kbps, 48 kHz, Stereo - Bitrate: VBR, 1 pass, Target 60.00 Mbps - Encoding Time: 00:29:34 04/15/2025 02:18:31 AM : Encoding Failed ------------------------------------------------------------ Frame substitution recursion attempt aborting after multiple attempts on file: G:\My Drive\Draft\2025-04-09 21h 34m 23s.mp4 Inserting black for frame number 23563 ------------------------------------------------------------ An error was encountered while writing the output file. The output destination could not be found. Check that the output directory still exists. If the output directory is on a network or external device, check that the connection is ac