Master the art of compression, share and learn.
Als letztes aktiv
I need to re-install AME 2015.3 but it does not appear as a previous version on my Creative Cloud apps page. Is there some other place I can download and install this version?
AE輸出到AME時,在AME點選格式設定卡在"動態連結連線中",過約20-30分鐘顯示失敗(來源為空)嘗試過重安裝、複製可正常輸出的電腦的安裝資料夾、皆無法,但PR匯入AME點選輸出設定卻正常不過PR卻不能匯入AE的動態連結,AE卻可匯入PR動態連結AE版本CC2017 (14.2.1)PR版本CC2017 (11.1.2)ME版本CC2017 (11.1.2)電腦資訊DELL-Percision T7910CPU- Intel Xeon E5-2630 v4 2.2GHzRAM- 128 GBOS- windows 7 64bit SP1NVIDIA Quadro M2000Disk C -SSD 64/238GB (software were installed in here)F -HDD 890/3630GB-------------------------------------------------------------------------------I have Adobe CC licensed desktop software on my own, and already corrected install Adobe After Effect CC 2017 (ver 14.2.1.34) in C:/Program Files/Adobe/After Effect CC 2017 in my workstation tower ,so do Premiere(CC2017/11.1.2) and Media Encoder(CC2017/11.1.2).When I finished my work in AE, I rendered it with "CTRL+M" then went to Reder Queue, choose "Queue in AME" to Adobe Media Encoder, once I changed my output format setting in AME,the comp just stuck in "DynamicLink server connecting",after few miniutes,it Failed.But Premiere's render queue was wor
Hello forum folks,I've had encoding issues since upgrading to High Sierra / CC2018. on a MacPro 5,1, dual 3.46 6core , 48GB, GTX980ti 6GB, OS 10.13.5.Had almost no issues on Yosemite / CC2017.Now when encoding to h.264. If I encode to 720 I get hardware encoding. If I encode the same file to 1080 I only get software encoding.I've just selected the Vimeo or Youtube presets for either frame size, it doesn't matter.Why would 1080 cause this behaviour?I can repeat this on other similar machines.I've been reading on other forums folks having all sorts of problems encoding and Adobe is saying that the hardware is not compatible.Obviously the hardware is compatible If 720 works perfectly, why cripple the 1080?Bruce
So in my preset I have selected to verify the transfered files, however once Media Encoder is finished the task there is no window to confirm that the files were verified successfully.
Hello!I publish directly to Youtube a lot in Media Encoder. It used to work like a charm but ever since installing CC 2018, it fails almost every time.When I look at the Error Log, it tells me that its because I wasn't logged in or had invalid credentials which isn't true. I have logged in and out and even re-installed 2018 Encoder.Anyone else have this issue and or have a solution?Thanks!
Like, is 40,000 handles enough for working with a 30 or so video clips? What...do you need one per video frame? Left idle the handle count keeps climbing up and up... and up. I don't think I even have to open a prproj...
I'm trying to expedite my transcoding workflow for this particular project, with scores of clips to review.My HPX170 records up to 4 audio channels, and in this case I i have my current preset configured to take channels 1 and 2 as mono tracks, and 3 and 4 as stereo. On testing this is working properly.However, we now know that we ONLY want source channel 2 (cleanest audio) on the output files.I can't figure out how change the preset to map source channel 2 to a single output track. I can delete 3-4 without issue, but when I delete track 1 in hopes of keeping only 2, the resulting output has source channel 1 instead of channel 2 as the lone track.I may be missing something obvious to a more seasoned user.Thoughts?
I have been having trouble on my 2012 MacBook Pro with 8GB ram a 2.3GHz Intel Core i7 and NVIDIA GeForce GT 650M 1024MBIntel HD Graphics 4000 1536 MB graphics. I am not able to import 4k footage and edit in Premiere, so created an ingest setting to make a proxy to work with a smaller file. Adobe support recommended also changing the renderer to the metal version which worked when I was on the phone with them, but each time I am importing footage and using Media Encoder to create the proxy, my computer screen just shuts off. Sometimes the entire system restarts and I get an Apple warning that there was an error that made the system shut down, and sometimes the screen just goes black, and the keyboard stays lit up. In that case I have to manually power down by pressing the power button until it shuts off. I send the reports to Apple when I restart the computer. Anyway, is it because my graphics card isn't strong enough? If I render the footage as 4k in Premiere once in the timeline, woul
I've been using the Adobe suite for about 3 years now. Back when I first started using it in 2015, I swear that when exporting from Premiere through Media Encoder, it would take very little to no time at all for the data to transfer to Media Encoder. I could hit "Queue" in Premiere, then click over to Media Encoder, and the file would already be ready to encode. I could hit the "play" button and start the encode right away. Maybe I would have to wait like 10 seconds at most. No matter how big the timeline/project was (be it 1-min video or a 2 hour video) it would always just shoot right over to Media Encoder once I hit "Queue". I feel like something has changed in maybe the last year or so... now it ALWAYS takes forever to transfer over. Even 1 min timelines take like 5 minutes to transfer. Longer timelines can take ever longer... What changed? Did Adobe change something about the way Media Encoder transfer the data over or something? Why did it go from always working like a dream to a
I have not seen this before. I encode a 720p file using the H.264 480p widescreen codec and get an mp4 with no data and an xmp sidecar file. I have tried using the Vimeo 480p widescreen variant with no success. I encoded two file earlier yesterday with no issues, then this popped up.I am on MacOS 10.13.5 High Sierra, and using the latest version of Encoder. I uninstalled and re-installed Encoder. No luck. I also tried with the 720p codec, but had issues. Another point of note; it took only around 20 minutes to compress a 55 minute piece of video.I went to my laptop, running an earlier version of encoder and MacOS. I was successful on the laptop, but the time was extreme.So, my question is what changed? Are MacOS High Sierra and the most recent version of Encoder incompatible?Any assistance would be appreciated.
I was exporting a 33 minute 4k Timeline from Premiere Pro and usually when I render I hit "queue" and then media encoder does the render. When I was rendering this clip I noticed that after 10 minutes of the render, media encoder gave an accurate time estimation of 6 hours. That seemed a bit ridiculous so I pulled up task manager to see how many resources media encoder was using, sure enough it was only using 17% of my cpu to do the render. So I decided to cancel the render and render it inside of Premiere Pro instead by hitting "export" instead of "queue" to see if It was going to use any more resources. Sure enough the render used 70-80% cpu the entire time and completed in just under 2 hours. Is this supposed to be happening? I was using the same settings for both: H.264 with maximum render quality and render at maximum depth checked. As well as a target bit rate of 25 and maximum of 30Mbps. The file is 4K at 60fps (For YouTube, that's why the low bit rate). I am using t
I have a Premiere project that has footage from a Canon C100, Canon C200, and DJI Mavick.The only other assets in the project are a few mp3 music tracks, .wav recorded audio track, a pre-rendered MP4, and text made in Premiere itself.I have Mojo 2 and Shrinkray from RedGiant applied on most clips.All of these are items I use on a regular basis on daily exports for numerous projects and don't cause any issue.For some reason though, on this ONE particular project, whenever I export, it gets about 3/4th of the way done and then freezes and crashes.More recently, it no longer gives me a freeze and a crash though, now it just closes AME without any warning or notification whatsoever. I come back to look at my export and its no longer up. It doesn't generate a crash log or anything anymore and never even registers it was ever exporting at all.I have reinstalled the entire Adobe CC Suite, cleared all of my media cache, updated my OS, updated my graphics card, cleaned the system with Malwareby
Hello all, I know this is an 'adobe problem' but I thought I'd give it a try since I know lots of bbers use media encoder cc and someone might have encountered the same issue as me :When I'm trying to batch export my stock clips I nested within premiere pro and queued up to media encoder. The queue starts rendering, but after 5/6 exports it starts failing every remaining clip. To solve this I can reboot the program, reset the status of the failed exports and launch queue. Then the same happens again, 5/6 exports then fails. Reboot/reset and good to go for only 5/6 exports... I can't do my full batch in one go it is very frustrating and time consuming I have to babysit the whole process. Any clues as to how to fix this ?
Hi all. I have an edited audio file, to be exported as an mp4 with an unchanging still image, for the full 30 minute duration.If the image never changes, is there a special way to encode this to keep the file size down? Needs to be an mp4 because it'll be loaded in an mp4 player.Thanks
Hello everybody,It's been a while, can't tell exactly since when, that all my presets under the "Devices" section are not working anymore.All of them (from the "Android" section to the "TiVo" one), when dropped onto the file, give a pop-up error:"Preset Error. Incompatible Video Coded found in the preset. Preset loading failed" (or something like this, I have the Italian version).Now, I found a similar thread with the same pop-up error but referred to the .mov format.My problem is not with a specific codec as the pop-up window says (mostly from that section are H264, besides few which are MPEG4 or MPEG2), because all the other presets using the H264 codec (like, for example, the "Social Media" section or the "VR" section) are working perfectly!So, I only have problems with my "Devices" category, weird.
Good morning allCan Adobe (encoder) generate this maxFALL and MaxCLL that some providers are asking me?I am editing hdr content from different studios and when I render the final video, everything seems to be ok apart from that I am missing this txt info. I have reading that for the moment Adobe can´t add this metadata in the hdr video files.Can anyone confirm me that I am not able to do it or explain me how to do it?Thanks in advance[Here is the list of all Adobe forums... https://forums.adobe.com/welcome][Comments is to ask about the operation of the Forum, not a specific program][Moved from the Comments forum to the specific Program forum... Mod]
I'm running 12.1.2 (build 69) trying to convert an H264 to MXF OP1a AVC-Intra Class100 25p and the blighter crashes every time. I can render to DNxHR no problem at all, but the resulting file size is unacceptable for my workflow. This container has had issues in previous versions and comes up in search as a fixed past issue (12.1): List of bug fixes in the Adobe Media Encoder CC 2018 and 2017 releases. Can anybody else get this work, I want to know if this is my system or a global bug?
I am trying to export a premiere project to h.264 and the render will fail about half way through with this error. I am on the latest version of both AME and Premiere, and I am curious to whether it is the update or not. I seem to be able to render to other codecs like DNxHD, but I have a screening this week and for compatibility's sake I wanted an h.264Export ErrorError compiling movie.Accelerated Renderer ErrorUnable to produce frame.Writing with exporter: H.264Writing to file: \\?\J:\dds.mp4Writing file type: H264Around timecode: 01:40:21:17 - 01:40:23:01Rendering at offset: 6021.708 secondsComponent: H.264 of type ExporterSelector: 9Error code: -1609629695Computer Specs---------------------AMD Ryzen 7 1700 Eight-Core Processor 3.00 GHz32.0 GB RAMGeForce GTX 1070Ti
Why does AME need to re-read the entire video file every time I click to change an encoding setting? I imported a 2.5hr video which took a long time to begin with but when I click to change the encoding, it has to re-read the entire file again before I can even change the setting. Then I click on the preset to change settings in there and it yet again, re-reads the entire file before I can change anything. It's taken me an hour to even get to the point where I can start the render.This is not a new issue....the bigger the file, the longer it takes. Why does it need to re-read the file every time I click to change something?Thanks,Shane
Usually when i render my AE projects in Media encoder it works fine but since yesterday everytime i drag the composition into it, it just keeps "connecting to dynamic link server". Tried restarting pc, reinstalling Ae and Media Encoder. Wondering if anyone else has had an issue and knows a solution.Here are my pc specs if necessaryCPU: Intel i7Memory: 2x8GbGpu: Radeon Rx480 4gb
Hi,I'm confused, and I have not seen anyone posting about this.I am trying to author a Blu Ray for my new movie. I've tried rendering H.264 blu ray and MPEG2 and both times it creates 4 files. Why 4? I just need audio and video, what are these 4 files? I can see that one is MP4 and one is .wav, so should I just ignore the other 2?Thanks,-Tim M.
Does anyone share this problem?I tried this several times and the same issue comes up every time in Media Encoder:I have a set of 12 sequences that need exporting to H.264. Footage shot on FS7, slog 3 cine in CINE EI mode. Basis corrections done with Lumetri Color. - Exporting just one of these sequences straight from Premiere results in a video with correct gamma levels. (levels match levels in edit)- Exporting just one of these sequences through Adobe Media Encoder also results in a video with correct gamma levels. Exporting more then one sequence: all video's show a gamma shift! What the hell? No settings were changed! This leads me to conclude Media encoder changes something when adding videos to the render queue. Software error?
The latest version of Media Encoder seems to be very slow to render even short videos. A 15 minute video rendering to an MPEG DVD is taking more than an hour. I've tested with multiple projects, some with advanced effects and others real simple and the results always seem to be consistent: They take too long to render. The previous version would render a video this short in 20-30 minutes using the same codec settings, so it has to be an issue specifically with the latest version. I have tried clearing the media cache which hasn't helped. Any help or suggestions would be great!AME v. 11.0.2.53OSX 10.12.4iMac (Retina 5K, 27-inch, Late 2014)4 GHz Intel Core i732 GB 1600 MHz DDR3AMD Radeon R9 M295X 4096 MB
Hello Adobe Support, I am a Creative Cloud member for several years since 2014 and have just recently encountered strange colored pixilations across on frame of my Premier Pro CC 2014 video files that I send to Adobe Media Encoder 2014.2 for conversion. I have used Media Encoder for years to process my Premier video and just recently (random) video clips will have this issue when Media Encoder is finished with them. The issue never happens on the same clip twice (if I re-send it to Media Encoder again) and it does not always happen at all: just every once in a while (with the very same footage being sent to Media Encoder) does this issue appear so there seems to be no common link to look for clues as to why this happening? The video files are pure as they come directly from Premier Pro CC to Media Encoder and even when the issue happens on one encoding, if I run it through again it never is there the second time...but it may appear in another part of the video file....Please help...The
If I send multiple sequences to AME from Premiere, the first one encodes properly, occasionally the second or third do, but the rest simply encode the first few seconds and then stop. Profile doesn't matter. These are short :90 - 2:00 videos, primarily 4k A7Sii media in a 1080 timeline. No error messages in AME, though today for the first time I got a couple of Ppro headless crash reports, though no app actually crashed.I've given up on dragging and dropping, sequences from PPro to the AME window, 2/3rds of the way through AME hangs. This has never worked.Six month old build:i7830GTX1060 6gb64gb Gskill Ripjaws DDR4 ramAsus gaming 7 boardSSD's for media, boot/PPro, and exportsUninstalled and reinstalled AME, running 12.1.2PPro is 12.0, reluctant to update as I am in the middle of a projectDisable Kaspersky before exporting.Right now, the only way I can reliably export is one file at a time using direct export in PPro.Help extremely appreciated, as I have a high volume of vid
Remix with Firefly Community Gallery
Thousands of free creations to fall in love with and remix in Firefly.
Sie haben bereits einen Account? Anmelden
Noch kein Konto? Konto erstellen
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.