Design the future of fashion, win Firefly Pro 👗✨
Bug Reports
Recently active
Hello, I have issue with ME2024. It keeps on crashing during rendering (crashes, jams system not responding at all and eventually reboots Finder) and I haven't found any resolution yet. Sometimes rendering goes complete but most of the tries fails. My system is 16" MBP mid 2019 2,4GHz 8-core Intel Sonoma 14.2.1 installed. I usually transcode large files from prores hq to high quality mp4. Fcpx/Motion user and some supported 3rd party plugins installed. Now trying back 2023 versions. If you have any ideas I could check and would possible give any hint what's going on please help me. BR, Jussi
If you set a custom output name in media encoder, and then click the check mark for 'Use Maximum Render Quality', the custom name is reset back to whatever it was originally. This is particularly unhelpful as the Output Name appears first so if you're going down the list setting all of your output settings, and then check 'Use Maximum Render Quality', you may not realise that the Output Name has been reset. Adobe Media Encoder 2024 24.3 (Build 49)2023 Macbook Pro - Apple M2 PromacOS Sonoma 14.4.1
Antes Renderizaba literal 30 minutos una pelicula de 2 horas, y ahora me tarda 3;45 horas en una pelicula con la misma duracion los mismos graficos que tampoco son la gran cosa, solo textos y una imagen como logo y musica, antes funcionaba bien, ahora con la actualizacion me empezo a hacer eso, luego me consume el 80% del procesador cuanto antes llegaba al 20, porque mientras renderizaba podia perfectamente trabajar con photoshop y ahora, nada se llega a apagar la Macbook pro, si alguien tiene el mismo proble o ya losoluciono agradeceria su ayuda, Gracias
Hi team,I'm attempting to send a raw photo sequence from AE to Media Encoder for export. The photo sequence is edited in Lightroom Clasic and then imported to AE. A comp is then created from the image sequence. The sequence is comprised of about 300 Nikon raw NEF files (a timelapse sequence). I'm attempting exporting in Qucktime Proress HQ format, using the original image size, at 30 fps. In ME this is the error seen in the log:Export ErrorError compiling movie. Accelerated Renderer ErrorUnable to produce frame.Writing with exporter: QuickTimeWriting to file: /Volumes/Raid4/Timelapse/2024-04-20_stars/2024-04-20_stars-PROJECTFILES/2024-04-20_stars-AE_AME/2024-04-20_stars comp.movAround timecode: 00:00:02:12Rendering at offset: 2.333 secondsComponent: QuickTime of type ExporterSelector: 17Error code: -1609629695 I always reders a few seconds of the sequence and then errors out. I am able to export the same sequence directly from AE with no issues. Prores fil
We have a watch folder set up to encode videos when we move video clips into it.Usually after the clip is placed into the "Watch" Folder the encoding begins and the completed clip is placed in a folder named "Output" and the origanal clip is moved into a folder named "Source".Now the origanal clip stays in the folder it where it was first placed and nothing is in the "Source" folder and the completed clip is placed in a folder named "Output".The problem is that the encoding process will start again the next time Encoder is run, as the clip is still in the "Watch" folder.Adobe Media Encoder 2024V. 42.3 (Build 49)
I have a very recurring problem, from time to time the media encoder does not finish completing the render, it always takes a second to finish, it stays for hours without moving, until I stop it and try again with the same result. I clear cache, restart, I have updated all Adobe apps, video drivers and it always happens, no matter the format, h264, avi, quicktime.Windows 11, 32Gb ram, 4060 TI 16Gb, Ryzen 7 5700X, AME 24.3. any ideas please
I do all my editing on my primary system, then save the project file to a folder on Dropbox. A remote computer running Media Encoder has that folder setup as a Watch folder to automatically pickup and export the sequences in a project. A number of computers will save projects to that folder and it is supposed to just truck through them, as headless a possible.At some point we'll notice that projects have stopped rendering and when checking the machine Adobe Media encoder has frozen, and there's a system warning to force quit apps because the computer is out of memory. It's been a relatively consistent issue, but moreso lately.After force quitting Media Encoder and re-opening it, it picks up with any files that hadn't finished, and goes on it merry little way until it runs out of memory again. The files that it got stuck on proceed through without issue, so it's not centered on the projects or footage themselves, it seems that Media encoder isn't releasing the the memory it uses when pr
Hello,This is an older problem as described in this posthttps://community.adobe.com/t5/adobe-media-encoder-discussions/estimated-file-size-issue/m-p/9412143#M4318But the bug itself if that when the Metadata option is set to ""create sidecar file" in the export settings box in Media Encoder the program still writes the Metadata INSIDE the file. The other 2 options that are always greyed out are write Embed in Output File and Create sidecar AND Embed in Out file. This is s H264 file that we are talking about. Media Encoder 23 and the latest 24 both behave the same. Thanks.The only option is to turn it off.Turning it off also solves that dreaded size bloating of the file which took me couple of hours today to figure out.
He estado varias horas tratando de exportar una serie de videos, pero se congela.Actualmente tengo un archivo de 8 minutos de duración, lo puse a codificar hace 3hs. El programa avanzo hasta el 99%, media encoder me muestra que que le falta 1 minuto para terminar de exportarse, pero no avanza. Me tiene molesta esta situación, es tiempo de laburo perdido... Win11 - Media Encoder 2024 (Versión 24.3 - Comp 49)
I decided to leap out of Beta and back into the regular versions of PP and ME.In my very first operation I asked PP to send stuff to ME to create proxies.All seemed weel. I set up a very small set of interviews which, based on past history, should have taken about 1 hour to create proxies.I went to bed and returned this morning (almost 7 hours later) to find it still working on them. I encountered this issue before where ME just gets slower and slower and slower the more it keeps encoding.I posted about it and eventually it was fixed. Well, it seems to be back. MacPro 2019 Intel 96gigs of RAMBrand new project
AME 24.4 Beta Build 32: I'm trying to render an SD sequence (720x480), and it's telling me hardware rendering is not supported. I have nVidia RTX 2080Ti, which has worked flawlessly with previous builds. Is this a beta bug for today?
I've been having an issue everytime rendering with media encoder. Video preview in AME looks fine, no errors, but the final clip looks like the images attached. When I render directly from Premiere or After effects it renders fine. I tried updating the card's driver, and reversed the driver back to previous versions. I also tried unistalling software and re installing. I also did it to the whole adobe suite and the issue continues.
Hi, When I select h.264 format, I am used to select some presets, and by default, the first preset of the list remains selected what ever I do. Is the new preset selected really selected even if the check in the list is not updated, or is the new preset selected really not selected.... ? So it's a mess. And when I close Adobe Premiere AND Adobe Media Encoder, I can have fatal error... It seems that the default presets "Correspondance à la source - Débit élevé" and "Correspondance à la source - Débit moyen" are bugged...
In Adobe Animate when I export to video I can select 'Start Adobe Media Encoder Render Queue immediately' so that Adobe Media Encoder will start immediately exporting the video. Ever since I've updated Adobe Media Encoder to version 24.3 (build 49) however this doesn't make Media Encoder start the encoding process. It just waits for me to click the 'start queue' button. Used to work fine in the previous Media Encoder version (where I also used the latest Adobe Animate version).
When I export any video to H.264, medium or high vibrate, the result is a damaged video. The audio is complete, but image got like attached picture. It happens with Premiere pro and Encoder. Quicktime or AVI output doesn't have any export issue. It is not a custom preset or any damaged footage, It happens with any project. Please help. 😞
Hello So im getting a random "failed" error in media encoder when rendering my files I can add the file to the queue again change no settings and its does it fine here are the settings: Preset Used: Youtube- Video: 2560x1440 (1.0), 60 fps, Progressive, 203 (75% HLG, 58% PQ), Hardware Encoding, Nvidia Codec, 00:14:25:11- Audio: AAC, 320 kbps, 48 kHz, Stereo- Bitrate: CBR, Target 80.00 Mbps As i say when it fails i can click duplicate in media encoder and it will try again and completes it fine Any ideas why this happens
Hey, i do not know if anyone had this problem already.I render a list of ae comps and at the beginning it looks all fine.Aftter a while - always different - the process stops during rendering a video when the video has reachend 100%. So when I check media encoder again for example after 3 Hours I see the last frame of the film in the preview and it has stopped. Then I have to restart media encoder and it works again. Does anyone know this problem and can help me? I have Windows and the newest version of Media Encoder. I tried to remove the cache, does not help. I use cuda rendering .. but I already tested several options. Thanks for your helpAndi
I am exporting from Premiere Pro to AME. Timeline video is in 4K with MOGRTs and PNGs. Playback is fine in Pr. Even the preview is fine when rendering in AME. Codec is H.264 with a LUT. After the render is complete I try to play it in multiple players including VLC and the video is greyed out. I even tried removing all LUTs, PNGs, and MOGRTs from the render and still the same problem. However, when I render in H.265 the output is exactly what is expected. Does anyone know why this might be happening? Thanks. OS: Windows 11. AME/Premiere: 24.2.1 (Build 2)All Video shot with GoPro 9 and DJI Mini 3 Pro. (Used with no issues multiple times before.)
Hello ive been having this problem with encoder 2023, Iwas doing an after effects composition an the when i send it to encoder and clicked in dinamic link the file looks like this (In the picture above) it doesnt look that way in after effects and there is not a layer underneath it. I tried with other videos exporting them from after effects and the same happens,. How can i solve this
Media Encoder 24.2.1. Attempting to encode a Quicktime ProRes 4444 W Alpha video from a 2000 frame image sequence. If "Interpret Footage" is used with "Assume Framerate" (24fps in this case), the frames only encode properly partway into the finished video. At some point, the motion gets stuck on a single frame, and that single frame is encoded into the remainder of the video, frozen in place until the end. Previous versions of Media Encoder tested and do not have this issue (Currently switched back to 23.5 which works fine)
I have had several crashes trying to encode a 4K video I edited in Premiere and am exporting with Media Encoder that is 11.5 hours and takes 45 hours to encode with the export settings I'm using. I have had 8 crashes so far, and most of them anywhere from 50 to 75% of the way through the encode, so you can understand my frustration here. First off, my specs:CPU: 5950xGPU: 3080TiRAM: 64GB DDR4Source Footage is on two 8TB SATA SSDs striped together, roughly 1 GB/s read speeds as a resultSaving to a 12 TB SATA HDD I am encoding using Voukoder, an export plugin that allows me to export using x265, which I prefer over the built in encoders, for certain specific reasons that I need for my exports. I know Adobe's first response may be to try to blame Voukoder, but I've had that plugin crash in the past. It produces its own log, and its crashes also don't look like what has been happening here, so I don't suspect it's Voukoder at fault here. I actually successfully e
Will only render part of the clip when slowing down footage shot at 60fps to 23.976fps with 'Interpret as...' in AME. Both 'Source' and 'Output' are set to 'Entire Clip'. This has been an issue before, but was fixed. Now it's broken again. Reverting to AME 2023 for now, where this works. MacOS 12.7.4 MacBook Pro M1Max 64GB RAM; AME 24.2.1
I created two similar H264 output presets - the only difference is one has captions burnt in and the other is clean. If I apply them individually (ie duplicate the source with only one output) then everything works as expected howeve if I apply them as two outputs to the same clip the captions do not get burnt in on the preset with burnt-in captions. The workaround is .... to apply them individually. I have other similar H264 presets which do work.... go figure. I tried to attach the presets but the forum won't accept them. AME 24.2.1
when i edit a footage like 50fps then i changed into interpet footage to 25 fps then make to proxy its not make complet proxy, with original 50fps footage work well in proxy ... why???????
Hi, I would like to encode a project from After Effects with Media Encoder, but it says: Adobe Media Encoder has encountered an unexpected error and cannot continue. Cache-SSD is empty. What can I do? Media Encoder is also not starting as Standalone. Renderqeue in After Effects is working.I am working on Windows 10 Pro, Version 22H2, Betriebssystembuild 19045.4046, AE and ME, nvidia-driver are newest versions dated today. I am stuck.Cheers, Albert
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.