Bug Reports

Good day Adobe, Ever since the 2023 update, and it took us a while to discover, when we export MP3s at 16K, the encoding automatically ups to 32K. Whether we export the MP3s manually or use a preset (old or new), from Premiere Pro or send over to Media Encoder, the 16 kbps automatically exports as 32 kbps as reflected in both file size increase and what the files properties detail tab shows. Furthermore, this is reproducable on multiple  workstations. Example screenshots attached. Screenshots 

I've encountered a bug when making proxies from DJI footage (h.265 HEVC). I've been doing this for years with Premiere/Adobe Media Encoder, but the process is now broken in the 23.5 version (possibly earlier versions of 23 as well). Essentially, when I create the proxy file in Adobe Media Encoder, it rapidly transcodes the file (much faster than it used to take) and the resulting file is unplayable, either inside Premiere or using a standard video player. The frame freezes up rather quickly in the video and it won't play. The original file will also no longer scrub in the timeline. The proxy file plays back as black. To test whether it was something I was doing, I ran the same file through Adobe Media Encoder 22.6.4 and it plays back just fine. Something seems to have changed in version 2023. If I switch AME 2023 to software engine only, the resulting file will scrub, but I'll get something like 1 frame every 2 seconds. Horrible latency which was never present in earlier vers

Bonjour à tous, Après avoir créé mon dernier projet sur after effect, je l'ai ajouté sur média encodeur, comme d'habitude, mais mon rendu est décalé: la partie gauche de la vidéo se retrouve à droite. C'est la première fois que cela m'arrive et j'avoue être dépassé.Merci pour votre temps. - After Effect v23.6- Média Encodeur v23.6

As of yesterday, Media Encode crashes without opening with the below crash report.I have not installed any new fonts or made any significant changes since previously opening it with success. The PC is an MSI Gaming i7 10th Gen, 32GB RAM, 500GB HDD with 172GB free running Win 11 PHome 22H2.Follwing Error Crash Report: Process: Adobe Media Encoder.exe [2288]Path: C:\Program Files\Adobe\Adobe Media Encoder 2023\Adobe Media Encoder.exeProduct Version: 23.5.0.51File Version: 23.5.0.51Code Type: x64Parent Process: explorer.exe [10692]Date/Time: 2023-08-10 13:56:58 E. Australia Standard TimeOS Version: 10.0.22621.2070Report ID: 48bef4b8-089a-4efe-8dd4-ab4449603aec Time Awake Since Boot: 528 secondsCrashed thread: 9 [15248] THREAD_PRIORITY_NORMALException Code: EXCEPTION_ACCESS_VIOLATIONException Parameters: Access violation writing location 0x000000b9a6a00ef4Exception Message: 3221225477 The instruction at 0x%p referenced memory at 0x%p. The memory could not be %s.Application S

My export comes with weird color : yellow/unsaturated when exporting on Media Encoder (see pictures to compare) Even with different settings (had to export projects H.264 and MFX). When I render directly on Premiere it is fine. Someone could help me with that? 

I have turned on 'Burn subtitles into video' in the export settings, but it doesn't work. Flicking it on and of sometimes does the trick, and it's not clear why. Checked it multiple times, also updated everything. Seems like a bug, and a pretty annoying one if you have numerous amounts of assets in different formats. 

I keep on recieving an error for my video, its supposed to come out around 50 minutes but sometimes when I export it I recieve an Error and the other times I export it it will play for 8 minutes or so then skip to the end even the the mp4 file reads 50 minutes. Here is the info for the error:Error compiling movie.Export errorError finishing encode.writing with exporter: h.264writing to file: C:Users\goblin\OneDrive\Desktop\videosyt\dishonored1_3.mp4around time code 49:27:37component: H.264 of type exporterselector: 9Error Code: 39Really hoping not to lose this footage, its the 3rd video of a series.

M2proのMacでMediaEncoder 23.6を使っていますが、選択肢の中にDCPがなくなっていました（IntelのMacで使っていたときにはDCPデータの書き出しができました）。ネットでいろいろ調べたらアプリケーションの情報を見るで「Rosettaを使用して開く」の項目にチェックを入れて再起動したらDCP書き出しが使えるようになるようなことが書かれてあったので、挑戦してみましたがダメでした。

In the latest version of this program none of the upload direct to social media features work. I have tested with various sized videos (1920x1080, 1080x1080, 1080x1920). All videos under 5mb and 10 seconds long. Twitter fail message: "The video must be 1920 by 1200 or less, 60 FPS or less, 140 seconds or less and 512MB or less, progressive, mono or stereo AAC audio"All videos work uploading direct to Twitter. Vimeo fail message: " Vimeo - Could not obtain upload ticket" Please help i am using this automated step regularly. Thanks 🙂 M 

Tried restarting both AE and Encoder, cleaning preferences, and cache, reinstalled to 23.0 version, nothing works. Both AE and Encoder are the same version.

Hello, Since the update to AME 23.2.1 encoding of H264 video is very, VERY slow. I noticed that the media browser is also messed up since the newest version. Literally nothing shows up there. Also, trying to rename your output files (woich SHOULD bring up an explorer window) frewezes AME for minutes. Preparing the audio/video files seems to crash the app, but if you wait for more than an hour you'll find out it's just REALLY slow. Rendering after that, works just fine. Reverting to v23.2 fixed the problem on my laptop, but not on my desktop. I'm running W11 with the latest updates on both systems.

I export from Premiere Pro to Encoder and the MOGRT files I use in the videos will incredibly often not load the fonts correctly. It will load PARTS of a font correctly, but in the same text element have random letter swapped out for lower-case characters. These are fonts I'm using from Adobe Creative Suite, which is also running.The top is the preview in Premiere Pro, the bottom is the useless garbage Encoder renders. I have wasted countless hours re-rendering videos due to this issue that has persisted for nearly a year.  I just gave up rendering with Encoder for a while, but I'm sick of having to render in Premiere Pro and being unable to get more work done at the same time due to this.Make paying for this software make some sense.

Drag and Drop often not working.Not sure whyCould be to do with Windows pointless huge Icons that appear when dragging.Maybe they are overlapping with something.Could be another UI scaling problem as UHD screen at 125% UI.Sporadic and I have yet to understand what causes it(Latest OS/AME/NvidiaStudiodrivers  - AMD 3655WX/Geforce4090Omniblack/128GB nonECC/3xSamsung 980Pro for OS,Storage and cache)AND STOP FORCING ME TO TAG TOPICS

MacPro Intel, 96 GB RAM, macOS 13.5 - Adobe Encoder 23.5 - Vimeo Premium.There is a problem for automaitc uploading a rendered file directly from Media Encoder to the VIMEO platform. The existing link cannot be undone and reinstalled - even after clean-re-install. The location of the link from ME to Vimeo is unknown. On VIMEO the link can be removed, but it is still displayed in ME after a restart. Strange... Who can help? Thank you!

Bug in Encoder 23: Die Verknüpfung mit VIMEO lässt sich nicht aufheben, obwohl die Bewilligung seitens VIMEO aufgehoben wurde...

When using an image sequence from a network location as a source, encoding to NotchLC .mov, the resulting video regularly skips be to the first frame and resumes.These dropped frames coincide with the following log message;<2412> <dvacore.StructuredLogging> <4> We have timed out on an async source. This probably shouldn't happen and will result in performance problems, media: "foo_00000.dpx", frame: 8 Storage server is a 100GbE storage system.Codec  - https://notchlc.notch.one/#downloadWindows 10 - Adobe Media Encoder 23.5 - Build 51When we do the same from local drive, we don't have the issue. Can you shed any light on this?

<fullPathToAMEbinary> --console es.processFile "C:\Hello World\test.js" // doens't work<fullPathToAMEbinary> --console es.processFile "C:\HelloWorld\test.js" // worksIs there anyway to escape the whitespace in a path?

Boa noite! Estou com o seguinte erro na hora de renderizar um vídeo, podem me ajudar?Agradeço!!! Erro na exportaçãoErro ao compilar o filme.Erro na renderização aceleradaNão foi possível gerar o quadro.Gravando com o exportador: H.264Gravação no arquivo: C:\Users\gabir\OneDrive\Documentos\Curso Motion Insider\Maratonas\MARATONA AE 1\Vídeo_AME\Projeto_Final_2.mp4Gravando tipo do arquivo: H264Timecode do entorno: 00:00:01:00 - 00:00:01:16\ nRenderização no deslocamento: 1,000 segundosComponente: H.264 do tipo ExportadorSeletor: 9Código de erro: -1609629695

I have been using watch folders for DNxHD and H.264 transcodes, as well as stripping audio. Seems like anything I run through media encoder that outputs uncompressed audio is shifted about half a frame early (848 samples) compared to the original. I have recreated this issue across multiple systems, even with new presets made from scratch. This has been the case for a long time and it's consistent. This doesn't happen with my preset that outputs AAC audio, but it does happens when I output only WAV audio files (no video), or a DNxHD video with uncompressed audio (that's all I've tested so far). This is a huge problem, I often conform my audio (in Pro Tools) based on the waveform of the guide audio embedded in these videos. A lot of the work I've done in the last few years has all been half a frame early because of this. Has anyone seen this before? How can I make Media Encoder output sample accurate audio without shifting? 

Connecting to the Dynamic Link Server is not working; I see a lot of questions about it. And I've tried every solution suggested, but none of them works. I restarted the system, cleared the cache, and reset the media encoder settings and both AE and ME are updated to the latest version.

Media Encoder 2023 suddenly stopped rendering H.264 videos yesterday and it continuosly fails to render any video exported from After Effects 2023 in the queue. I have tried exporting through After Effect directly, but that is not ideal long term. I have alsi tried using the cleaning tool and reinstalled Creative Cloud and all applicable applications and it is still failing to render. My MacOS is up to date with MacOS Ventura 13.4.1. 

Media Encoder no longer is able to properly detect .dpx or .cin files as being image sequences on import.The only option is to stitch the files.AE can import these sequences as a sequence propertly.  ME can not!This was working and now it's not.  Is this a licensing issue with Kodak or a bug or a coding oversite?

Greetings.  I have having issues with media encoder overwriting files instead of automatically adding the _1 or _2 etc. extensions.  The box is checked to do that.  I have reset the status in the encoder, and dont want to lose all my work.  Why is this happening all of a sudden?

I made a video, and wanted to render it. When i preview it in media encoder the left side of the video is slipping. It is fine if i render it from After Effects 23. Here is a photo of it

Hi, When rendering an EXR sequence from After Effects, the naming convention did not work properly. MCH_010_0010_v006_[#####] should have been rendered as MCH_010_0010_v006_1001 (frame number), instead it was rendered as MCH_010_0010_v006_[#####]001. Now I have to rename all the frames manually. Version of the app: Version 23.5 (Build 51)Platform and OS version: Windows 10 HomeBasic steps to reproduce the problem: EXR sequence set up in After Effects and rendered multiple projects in Media Encoder Diego