Purge All memory and cache worked.
↧
Re: Media Encoder Batch Render freezes entire operating system
↧
Re: Media encoder no longer works in 2018
thank you - I too had to contact them when I couldn't render anything in AME and my client was presenting that day so I had to render to QT in AE and then transcode it with some freeware crap I had to get at the last minute - NOT COOL, ADOBE!
It's not like we have time in our industry to get on the phone or chat with someone for hours so I waited several weeks before doing this and the agent had to take control of my PC and change some prefs files and reset some AE and AME prefs - it took about 2 hours and they acted like everything was all good but it's NOT all good if I can't fix it myself or if a service we pay for monthly, can't be fixed or updated, costing us hours ($$$).
As someone who has been using Adobe products for over 18 years, everytime there's an update, I cringe, finding that the things I use the most are now either obsolete, moved under many menu windows, or otherwise broken.
↧
↧
444 and 444XQ issue after installing HEVC support on Encoder
[moved post from the After Effects Forum]
Hi guys,
just having a nightmare here.
All started when I had to convert in Adobe Encoder a HVEC encoded Mov (Drone footages...). Encoder asked me to download the HVEC codecs, I hit "ok" and it allowed me to start the encoding. Nice on that!
Well, after that... all footages that I have using Prores 444 or ProRes 444xq won't be readable by encoder or, even worst: After Fx.
In After Fx I get this pop up message when opening a project containing a ProRes 444 file:
"After Effects warning: There is a problem accessing the audio or video data in 1 files since you last saved this project. Reload Footage or Replace Footage as needed.
filename.mov"
Even more: when creating a new project, and importing a 444 mov, it comes with audio but no video.
I've managed a workaround for on the clock demands, like today, but i desperately need some help here.
The workaround: managed to export again the footage using 422HQ.
Finder preview: ok.
FinalCut X: ok.
QuickTime Player: ok
Adobe: nope.
The problem affected two MacPros that I own after the encoder download.
Here is my System Configs:
Adobe After Fx Ver. 15.1.2 (Build 69)
Adobe Encoder Ver. 12.1.2 (Build 69)
Computer 1: MAC OS: OS X El Capitan Ver 10.11.6
Computer 2: MAC OS: macOS High Sierra Ver 10.13.6
↧
3D render in AME from AE
Hello,
I've a problem rendering a 3D bended layer in AME.
i try to set my comp in AE in ray-traced or C4D mode and try every option of rendering in AME and here is what i get :
here are my settings in AE and AME :
and here is my expected result (what i see in AE)
Does anyone have a clue for rendering my bended layer in AME ? or i only can to that in AE render queue ?
Thanks.
C.
↧
Re: Media Encoder CC2018 12.1.1 Build 12 Crashing on Batch Queues
What machine are you on and which OS did you update to? I've been having this problem for months!!!
↧
↧
Re: Media encoder no longer works in 2018
OMG! Thank you so much! I have been having this problem for moths and I finally figured out why my video kept failing!
↧
Text Artefacts when Exporting
Exporting a video for YouTube from After Effects through Media Encoder, but the text keeps exporting at a seemingly low quality (especially with purple text below)
Any solutions?
These are my render settings currently:
↧
ame dont want to open
What to do? http://prntscr.com/kv3762
↧
Re: ame dont want to open
Update to the latest version.
↧
↧
Re: Media Encoder 2018 and AE 2018 Dynamic Link Error
Same here... but I have seen this problem since media encoder has been released. I don't get why they moved all the good containers and codecs features from the render queue to this garbage app...at least they should have let us the option to render our videos with the software we want! Right now my workflow is: render a .mov with animation codec in AE, then import the .mov in ME to render my .mp4 with H265... what a wast of time! We use to be able to render those directly with AE but not anymore. Thanks to the broken ME dynamic link...
↧
Re: Creating proxies is very slow and after a while media encoder UI and Premiere Pro UI just goes not responding in the backround.
In the meantime, for all of us frustrated by the slow batching of proxy media in Premiere/AME... Davinci Resolve is excellently fast at batching media reliably. Then it can be reconnected after the fact in Premiere.
But since you're importing clips into a fully featured (free) editor like Resolve anyway, maybe you just finish the project in that software while you're at it. Just thought I'd offer advice seeing as how I've been out of commission for 30 minutes "creating proxy jobs" for 20 RED clips.
↧
Re: Red Screen intermittently and randomly when playing back and encoding premiere pro 2017
"Enable accelerated decoding of intel h.264" does not seem to be an option any more in v12.1. Instead, there is an option "Enable hardware accelerated decoding", however disabling this does not seem to fix the red screen issue. I am generating proxy files for some 4k footage--adobe media encoder does fine for the first few seconds of the clip but then seems to freeze at a specific frame, and then generates red frames for the remainder of the clip it was encoding, about 2 minutes of red frames. Help?
↧
Re: Red Screen intermittently and randomly when playing back and encoding premiere pro 2017
I am also experiencing red frames in Media Encoder. I have 4K .mov files that I am converting to HD H264 .mp4 files in Encoder. However, there is about 7 seconds of red frames in the same spot of the video each time I try to encode. I have emptied the cache, re-booted the computer and tried a few workarounds, but no solution yet. Is there a fix?
iMac Pro
MacOS High Sierra 10.13.6
3.2 GHz Intel Xeon W
Media Encoder CC 2018 v12.1.2.69
↧
↧
Weird Render Failure with Timewarp.
I am rendering a project from after effects into AME. Initially i was getting crashes on a certain stock image so i reduced the size by 50% in photoshop, then replaced it. It went through that section but failed at another image. I did the same thing and it went through fine. Then, it started crashing at the start of a 1920x1080 stock footage clip. I only have time warp on the clip. Settings changed are, Speed: 67.00 Vector Detail: 50.00 Smoothing Iterations: 50.00 Block Size: 4. I've used these settings elsewhere in the past and it rendered fine. I tried using an older user to render it out. With the collected files it renders on the newest user (which the crashes occur on), for 2 min and 50 sec and then at the same frame each time it crashes. Rendering on the old user (no crashes), it would take 20 min to get to the same exact frame in the project, but it wouldn't crash. It would go right through where it would fail. I would just render through this but 25 min on a 3 min render doesn't seem like a great compromise. I tried collecting the files and trying it on a separate computer with better specs, it rendered through the part fine in a normal amount of time. I then decided to do a fresh install of the os, and wipe the hard drive. Doing so and reinstalling all my programs, i tried to render it once again... still a crash. This makes me think that it may be hardware, but if there is a deeper issue i don't know about it would be nice to have an easy fix for this.
My Mac Specs (Where it AME Fails):
iMac (Retina 5k, 27-inch, Late 2015)
Processor: 4 GHz Intel Core i7
Memory: 16 GB 1867 MHz DDR3
Graphics: AMD Radeon R9 M395 2048 MB
3.12 TB Hard Drive
Seperate Mac Specs (Where AME Renders Fine):
iMac (Retoma 5K 27-inch 2017)
Processor: 4.2 GHz Intel Core i7
Memory: 32 GB 2400 MHz DDR4
Graphics: Radeon Pro 580 8192 MB
3.11 TB Hard Drive
Codec: H.264
1920x1080
The Rest is Match Source
Exporting Video and Audio
Performance: Hardware Encoding
Bitrate: VBR, 1 pass
Target Bitrate: 3 Mbps
(There is no audio in any of the video, but is being rendered anyway)
Audio Format: AAC
Audio Codec: AAC
Sample Rate: 48000
Audio Quality: Medium
Bitrate: 192 kbps
------------------------------------------------------------
- Encoding Time: 00:02:46
09/18/2018 09:43:56 AM : Encoding Failed
------------------------------------------------------------
Export Error
Error compiling movie.
Render Error
Render returned error.
Writing with exporter: H.264
Writing to file: /Users/zack/Desktop/---Master_1_5_1.mp4
Writing file type: H264
Around timecode: 00:00:31:18 - 00:00:32:11
Rendering at offset: 31.917 seconds
Component: H.264 of type Exporter
Selector: 9
Error code: -1609629695
------------------------------------------------------------
↧
Adobe Media Encoder CC Version 12.1.2 (Build 69) Doesn't Launch
Adobe Media Encoder CC Version 12.1.2 (Build 69) doesn't launch as a stand alone program. When I try to open the program nothing happens. No error message. Just nothing changes. I can launch AME through Premiere Pro by rendering a project, but wont launch as a stand alone program as I said.
I read various forums and people talking about this problem and the only solution that I found which works for me on a PC running WIndows 10 is by going into the C:\Program Files (x86)\Common Files\Adobe\SLCache directory and opening up a file called X19zbGNfZmVhdHVyZXNfXw==.slc in Notepad. I then delete the contents of the file, save, and AME will open on the following attempt.
The problem is that this solution doesn't work as a one-time, permanent fix. Each time I want to launch AME I have to first go into this file again, delete the contents again, and then save again. I have even tried making the X19zbGNfZmVhdHVyZXNfXw==.slc file "Read Only", but it doesn't help to fix the problem permanently.
Is there a better solution for this problem? Thanks.
↧
AME Update Crashing Mac / Run Out of Memory
Hello Everyone,
I usually set a large batch of renders before I leave work at night, but every morning for the last week I've been coming in to my computer having crashed part way through the render queue and being completely turned off. It booted up fine, I read the crash reports, and ran several tests showing no consistency in duration before crash or preset use; based on another thread I reverted to the last version of AME (12.1.1 Build 12) yesterday.
My machine did not crash last night but it locked up all other applications as well as AME due to lack of memory; freezing the queue after about 7 of 52 renders. Based on several other threads it appears that it is not terminating old PProHeadless processes which eats all of the ram - I'm not sure whether or not this is the culprit, it does look that way (I'm including a screen shot showing the PProHeadless processes on Activity Monitor).
It is worth noting: I am able to render when I am active on the computer (ie: actually at my desk). I have checked the computer sleep settings and set it so the display never turns off, just the screen saver kicks in. I have no idea why this would make a difference.
Has any one else experienced this? Any suggestions on a work-around or resolution?
Thank you!
Computer Specs
Mac Pro: (Late 2013)
Processor: 3.5 GHz 6-Core Intel Xeon E5
Memory: 16 GB 1866 MHz DDR3
Graphics: AMD FirePro D500 3072 MB
↧
Re: why does premiere pro shutting down when i try to export
I have the same problem. Did you solve it? thanks
↧
↧
Is There Way to Upload to a Facebook Page as a Draft?
Can't seem to post to a different privacy setting other than public. Maybe in my PERSONAL Facebook page i could set as "friends only", but I want to upload to Facebook Pages as draft and then schedule the videos from there. Or is this feature not available yet?
↧
Media Encoder CC 2018 - AME Web Service Request Rejected
We are using Media Encoder to convert Cineform files to H264. We are seeing intermittent requests return "Rejected". It doesn't happen all of the time, but a very good portion of the time.
Here's a sample request:
<manifest version="1.0">
<SourceFilePath>D:\mypath\6b964325-75cd-40d9-8f5d-c4c60b3816ab.avi</SourceFilePath>
<DestinationPath>D:\mypath\6b964325-75cd-40d9-8f5d-c4c60b3816ab.mp4</DestinationPath>
<SourcePresetPath>C:\Program Files\Adobe\Adobe Media Encoder CC 2018\MediaIO\systempresets\4E49434B_48323634\01 - Match Source - High Bitrate.epr</SourcePresetPath>
</manifest>
Here's a sample response:
<!DOCTYPE payload><payload version="1.0">
<SubmitResult>Rejected</SubmitResult>
<ServerStatus>Online</ServerStatus>
<JobStatus>Not Found</JobStatus>
<JobId>dfe5aa43-3928-4718-bd31-75bcb64805d2</JobId>
<JobProgress></JobProgress>
<Details></Details>
</payload>
We are making multiple calls before one can complete, so could it be a single threading issue?
Instead of using the web service calls, is there a way to get the watch folders to work without the GUI running? That may be an option for us.
Any other ideas or options to convert CineForm to H264?
Thanks!!
↧
How do I delete all the same encode formats at once?
I want the WAV lines removed. but It's quite tedious to select them one by one
↧