Apple ProRes 422 (HQ) in Adobe Media Encoder

I have Adobe Premiere Pro and Final Cut Pro installed on my mac. I need to export as Apple ProRes 422 (HQ) in Adobe Media Encoder. I have found the Apple ProRes 422 (HQ) in Premiere Pro. But only ProRes 422 and ProRes 422 (LT) are listed in Encoder. How can I get 422 (HQ) in encoder list? Thanks.

First thing you might want to try is just attempting the round trip keeping all the settings the same without doing anything in AE and see if you get a quality hit. I'm assuming that you're keeping pixel dimensions and aspect ratio unchanged. I'm not sure about the latest version of AE, but if memory serves, fcp and AE work in different color spaces which might be part of the problem.

Similar Messages

Adobe Media Encoder CC: Can I export to Apple ProRes 422 on a Mac?

Hi folks,
I tried to find some information about it, but couldn't really find a definite answer on this.
Unfortunately, my Mac is getting fixed as we speak, so I can't try this out either...
I want to convert mxf files (XDCAM HD 422 1080i 50, 50 Mbit/s with multiple Audio channels) to Apple ProRes 422 using Adobe Media Encoder CC.
Simple question: Is that possible or do I need to look for a different workflow/converter?
Thanks for your help!
Jens
PS: OS is Mavericks...

Hi DataWrangler,
Thanks for posting on Adobe Forums.
Please download proress presets for Adobe Media Encoder from here : http://www.adobe.com/support/downloads/detail.jsp?ftpID=5411
Please update if this helps.
Regards,
Sandeep

ProRes 422 MOV files offline in Adobe Media Encoder 2014 (but online in Premiere)

The question is NOT about exporting PreRes files from a Windows PC, which is what I keep finding in my searches.
My client gave me ProRes 422 MOV files. I imported them into Premiere Pro CC 2014. I could see and edit them fine. But when I export them via Adobe Media Encoder, they appear to be offline. BTW, other media sources exported fine, such as the PNGs and JPGs I cut to. (I don't think it matters, but I'm attempting to make h.462 mp4s, which I do all the time, and have done with ProRes sources before using CC 2014.)
I tried exporting a short video clip (using same ProRes 422 source) from Premiere and it worked fine. Why not Adobe Media Encoder? I need to encode batches of videos with ProRes sources overnight, so exporting from Premiere is not a good option.
I'm on a Win 7 PC and I have QT Pro and iTunes (which I think also installs codecs).

Everything seems to be working fine now, though I don’t know why. I did update my iTunes (which I’d rather not even have installed on my PC because I never use it, but removing it seems to mess things up). I’ll also make sure to keep my QT updated. I thought it was because I upgraded to the paid version a couple months ago hoping to fix a similar problem, but again, it seemed to get fixed when I updated iTunes.
Thanks for getting back to me!
Bill

Does CC 2014 eliminate the need to have Final Cut Pro and/or Compressor installed to access Apple ProRes 422?

Hello:
Just today, I was working on a Mac system that does not have any of the applications that I would have expected to need to have installed in order to do more than just decompress movie files compressed with Apple ProRes 422.
I was expecting to have to install Final Cut Studio 3, Final Cut Pro X, Compressor 4, and/or QuickTime 7 with the QuickTime Pro key; however, none of those applications are installed and I am able to create custom QuickTime Apple Pro Res422 Sequences in Premiere Pro as well as export using Apple ProRes 422. After Effects and Adobe Media Encoder also show all the Apple ProRes variations.
Does CC 2014 eliminate the need to have Final Cut Pro and/or Compressor installed to access Apple ProRes 422? Is it something happening on the OS or QuickTime level that would affect CC or CS6 in the same way?
I've done a web search, but haven't really come up with anything other than older articles about needing to have FCP installed (and I typically work on systems with Final Cut Studio 3 installed as well as CS6, CC, or CC 2014). If more detailed information is available, it would be great to be able to read up on it.
The system is a 21.5-inch iMac running Mac OS X 10.8.5, QuickTime Player 10.2, and Adobe Premiere Pro CC 2014 (8.0.0 - I know an update is available for PrPro, but it's not my system to make that change).
Thanks in advance,
Warren Heaton

Hi Emil:
I use ProRes all the time as well, but I have Final Cut Studio on my workstations.
I had not come across MindPower009's YouTube video. That explains how ProRes could be showing up without FCP or Compressor.
So, the answer to my question would be, "No, CC 2014 does not eliminate the need to have Final Cut Pro and/or Compressor installed to access Apple ProRes 422; however, if you are willing to be in violation Apple's terms of use, you can install the ProRes codecs anyway."
Even though MindPower009's YouTube video comments claim "FREE and LEGAL", it's clear from both the Apple download page and the ProRes codecs installer that Apple expects you to own at least one of their applications.
Thanks again for the link!
-Warren

Both After Effects & Adobe Media Encode CC giving are not letting me export.

Dear All,
Both After Effects & Adobe Media Encode CC giving are not letting me export movies.
Some times they will, but after one file both programs give me the following error messages.
After effects:
“[file path and name].mov. An output module failed. The file may be damaged or corrupted. (-1610153464)"
AME:
"Can't read from source."
I've went through the forum and found threads & pages discussing the problem.
E.g.
http://blogs.adobe.com/aftereffects/2013/08/solutions-for-problems-with-quicktime-files-in -after-effects-cc-12-0-because-of-conflict-with-dvcprohdvideoout-quicktime-component.html
http://forums.adobe.com/thread/1252092
After following all the tips and suggestions (from deinstalling quicktime components & audio components to completely reinstalling CC) I'm still experiencing the problems.
Which leaves me in a bit of a squeeze. I need to export over 144 movies in the coming 2 days and the only way to do this is to quit and open media encoder (or AE) after each single export.
Not really an option.
Both problems have the process Adobe QT sever in common, I took this from the console:
9/26/13 1:02:44.517 PM com.apple.launchd.peruser.501[171]: ([0x0-0x42042].com.adobe.Adobe QT32 Server.application[331]) Job appears to have crashed: Segmentation fault: 11
9/26/13 1:02:44.672 PM ReportCrash[354]: Saved crash report for Adobe QT32 Server[331] version 7.0.1 (7.0.1.0) to /Users/martijn/Library/Logs/DiagnosticReports/Adobe QT32 Server_2013-09-26-130244_martijns-MacBook-Pro-2.crash
System information:
Retina MacBook Pro (Mid 2012) (16gb ram)
Mac OS X 10.8.5 (12F37)
Running Adobe CC (for teams), all apps are up-to-date.
I don't no why Adobe puts out such a buggy piece of software (I know it has to with Apple's poor 32bit quicktime implimentation, but hey, this was known information no?).
Upgrading to CC has given our office nothing but problems.
Hope someone can help to find a work around until Adobe realeases a proper update and solves this problem once and for all.
All help is much appreciated.
Kind regards,
Martijn

Hello Tim,
Thanks for the really quick response!
Regarding the crash log: it doesn't reference com.apple.audio.CoreAudio (though it did before, so I followed all the steps in your blog post before I posted to this forum).
I've uploaded the crashlog to:
http://martijnlambada.com/TMP/AdobeQT32servercrash.zip
If you want to inspect it. It mentions the DXV codec (which I also uninstalled), but the crash keeps occuring. Also I need to export to DXV since it's the only codec the d3 media
server accepts (http://d3technologies.com).
I followed all the steps in the troubleshooting steps.
Codecs used: I've tried everything from animation to Apple ProRes (including: h264/motion jpeg/uncompressed). With all codecs the Adobe QT32 server keeps crashing (though I can't always reproduce).
Export destination: Internal SSD (same as where the OS is installed on) + External raid (via firewire & thunderbolt) + external HD via usb 3.0 (tried everything).
When does the problem start: Really hard to specify, sometimes a day without crashes, sometimes every export for days on end. Sometime after restarting (tried logging out, restarting, switching off and on the computer). With other programs running and with out. Now checking every process active when exporting, and comparing log files.
Can you export to other formats: See question 1, sometimes I can, sometimes not.
When you launch AE and/or AME, is QT32 Server running? At what point does it stop running? Still runing when I open the program. It crashes when exporting (ofter after finishing the first export).
What component files are in your Library/QuickTime folder?: Currently the folowing:
AppleAVCIntraCodec
AppleHDVCodec.component
AppleIntermediateCodec.component
AppleMPEG2Codec.component
AppleProResCodec.component
DesktopVideoOut.component
DVCPROHDCodec.component
DVCPROHDMuxer.component
DVCPROHDVideoDigitizer.component
DVCPROHDVideoOutput.component
DVCPROHDVideoOutputClock.component
FCP Uncompressed 422.component
iChatTheaterPreview.component
IMXCodec.component
LiveType.component
Hope this helps.
Cheers,
Martijn

Adobe Media Encoder CC constantly crashing during batch encodes

Hello!
We just made the big switch to Premiere Pro CC for our TV shows and now that it's time to finalize our first few episodes we are having some major problems batch exporting segments of the show. Sometimes it works, sometimes it works half way through the batch list then crashes, sometimes it crashes right away. There is no consistency, other than crashes are happening all the time. Here's what is happening:
• AME 7.2.0.43 (64-bit)
• Mac OS X 10.9.1 on 2x2.66 GHx 6-Core Intel Xeon, 40 GB 1333MHz DDR3 RAM
• Startup disk is SSD w/ 4GB free space (all footage is on external storage)
• Using Premiere Pro CC to export via AME.
• All recent updates insatlled as of 3/10/14.
The source footage is ProRes 422 720p 59.94 footage from AJA KiPros. Each project has 16 segments - these are individual sequences. There are 7 tracks of audio and 4-5 tracks of video in each. In addition to the video there are targa files that include the score bug, full screen graphics, etc (this is sports). There are also some Adoby Dynamic Link After Effects elements throughout.
Editing has been fairly crashless - however when I File > Export > Media and queue it up in AME, that's when the fun starts.
I can rarely get through an entire batch list - generally within a few files the preview window at the bottom shows that it has halted and nothing further will encode. There is no way to stop or close the program without force quitting. When I have tried to encode from Premiere Pro CC directly, it works, although it is much slower and will only do the one sequence at a time.
I have been trying to encode to two different formats from within AME:
1.) ProRes 422 720 59.94 (just like the source footage) with 4 channels of audio.
2.) ProRes 422 1080i29.97 with 4 channels of audio.
We have different broadcast partners so we need to deliver in these two difference specs. I get crashes regularly on both outputs.
Possibly unrelated but also weird - I've noticed that when AME starts this crashing cycle sometimes Premiere CC won't let me save anyome. The status bar comes up like it's going to save the project but it goes nowhere. I have to quit without saving. Weird.
Can anyone help me further troubleshoot? This is bordering near deal breaker to continue using this software if I have this much trouble when trying to get my project outputted. Thank you!

Agreed, I now have a project to GET OUT, and AME crashes consistently 1/3 into the render. It appears to halt all processing after (real time) 00:02:30
Am seriously considering uninstalling CC as I am beginning to find other issues in some apps, and going back to CS6/MC just so I can get work out. Durn it Adobe this is AWFUL!!
Alright, let's try to be constructive instead of throwing rocks... but the frustration level is high, and I have material on deadline. Let's get with this, guys...
What OS Win7, 64-bit
What version of AME/PPro (Please be specific by getting the full version number in the About Adobe Media Encoder screen) 8.2.0.54 Ppro: 8.2.0 (65)
When is it crashing (Again, the more detail here about where it was in the encoding process the better) roughly 1/3 into the sequence, always on exactly the same frame - tried replacing the clip with something different to see if it was a timeline error, and NO EFFECT.
What is your source (PPro project or media file (what kind?)) PPro
If the source if a PPro project, does it work when exporting directly from PPro? NO
What format are you exporting to? H.264, QT, WM, tried everything my client can play.
Do other formats work? MPEG2, QuickTime, etc? NO
Have you tried with GPU rendering on? How about turning it off by switching to Software-only mode? Mine doesn't have any choice, it's software-only.
Have you tried disabling Native Sequence Loading? (AME Preferences: General > Enable Native Sequence Loading) No effect
Other things I tried: uninstalling/reinstalling AME, setting cache to a fast local disk.

Adobe Media Encoder CS6 Random Crashing Mid-Render

Hello -
I've been dealing with this issue for enough months and across enough computers to finally seek out some advise here, hope it works out...
Basically I've got a 2 hour long film that I've been trying to export using Adobe Media Encoder CS6. It's never made it all the way through. I can usually skim through the generated quicktime file up to the point where the crash occurred. I've tried using that as a reference to check out my sequence in Premiere but there is never anything suspicious going on there. Most frustratingly the crash occurs randomly. Sometimes it will go through 10 minutes of the film; sometimes an hour. Regardless I get a crash with a report that has no specific information.
Footage:
r3d - Various resolutions, all being cut in a 2048x1152 sequence.
Quicktime mov - ProRes4444 for the most part.
Machine(s):
I had been attempting to render this for the past few months with a Macbook Pro running OSX 10.8.4 w/ 16GB RAM, 2.7 GHz Intel i7, NVIDIA GeForce GT 650M 1024MB - never made it through a render longer than 50 minutes of the 2 hours.
We recently got one of the new 2013 Mac Pro systems running OSX 10.9 w/ 16GB RAM, 3.5 GHz 6-Core Intel Xeon E5, AMD FirePro D500 3072 MB
The hope was that this new powerful machine would overcome the issues we were running into with these renders. Since I'm posting this now you can probably figure out that it didn't really work out that way...
Software:
AME- 6.0.2.81
Premiere - 6.0
I know there are updates to be used here, but whenever I update Premiere from just 6.0, the project itself becomes a buggy mess, crashing constantly. I also run Creative Cloud and have tried to just jump over to Premiere CC hoping all my problems would vanish, but instead, I again get a buggy project that constantly crashes. The only version of Premiere that seems to work with this project is 6.0, so general updates have not been useful (and instead damaging, I've wasted several days trying everything I possibly can to make the project work in the updates).
Any help appreciated. Thanks.

Thanks for the reply MMeguro.
Last night I was able to get my first full render through by doing a combination of things (so I'm not sure what did the trick in the end).
To answer some questions first, never attempted to do the FULL render directly out of Premiere, always switched over to AME for that, so that potentially could work too. Smaller renders have worked directly out of Premiere Pro, but they've also worked out of AME.
The initial render attempts that had been failing for the last few months were on the MBP which did not support GPU accleration due to an incompatible graphics card. I assumed the issue must be tied to something else because of this and was using it on the renders with the new 2013 Mac Pro. Using the workflow of Pr6.0, AME 6.0 and GPU rendering turned ON, I was failing to render to both Quicktime h264 and ProRes 422.
What worked for last night's render:
1. Convert Pr6.0 project to PrCC project (when I've done actual editing in CC after converting this project it tends to crash, but I figured just generating the project itself without doing any editing in it might satisfy what I was attempting to do).
2. Open AME CC and import PrCC Sequence. Used custom ProRes 422 setting.
3. Turned OFF GPU acceleration.
So as long as I the PrCC project I create stays stable long enough to save it (without crashing, which has been a problem with that Pr6.0 to PrCC conversion) then it seems like this will work. Kind of an annoying couple extra steps but I'm just out of my mind glad that I can actually render this thing finally. We're still in the rough stages so being able to turn around a review version within a day is very important.
Wish I could do more tests to figure out exactly which combination actually made this work for the benefit of others, but can't afford to do multiple 10 hour+ renders with random crash times.
Anyway, thanks again for the reply MMeguro much appreciated.

Adobe Media Encoder timecode doesn't match Premiere sequence

Hi, I'm having an issue when exporting through Adobe Media Encoder. My source sequence is 23.976 fps; I've set the Display Format in AME to 24 fps (options are 24, 25 and 30) and the export setting to 23.976 but the time codes don't match; AME seems to be adding frames. Over the course of a 90 minute export AME is adding about 6 seconds; the Premiere sequence is 01:33:52:13 while the AME export settings show 01:33:58:04.
I'm exporting this in chunks so I'm concerned that when I string them all together with the audio there will be a sync problem.
Version: AME CS6 6.0.2.81 64bit
Using with Premiere CS6; have entire suite installed
Most recent update installed
Mac OS X 10.7.3
Creative Cloud: No.
Working with a mix of RED 5k, 4.5k and 4k footage; all shot 23.976
No error messages
Is the problem only occurring with a specific output format or encoding preset? If so, which one? - same on all outputs; exporting to prores 422 1920x1080 23.976
Running Premiere at same time
Mac Pro, 2 x 2.4 GHz 6-core intel xeon, 64 gb ram, solid state boot drive, red rocket, black magic, decklink hd extreme 3d+
Are you using Mercury Playback Engine GPU Acceleration in Premiere Pro? - yes by default? no cuda / opencl
An unrelated problem I've also been having is when I try to export the full sequence, or even half, the export will freeze around 40%. No error message, just stops.

How are you checking the exports?

Adobe Media Encoder CS6 hangs while encoding Quicktime movies

Every day I am enoding 2-3 videos 15-40 min long with AME CS6 and every second day it freezes or slows down to almost zero. The source material is mostly Quicktime ProRes 422 LT 1080 25p or Quicktime XDCAM EX 1080 25p. Target files are H264 videos in different sizes. The workstation is a MacPro 5.1 Xeon 8core, 12GB Ram and Nvidia Quadro 4000 with OSX 10.8.2. Only restart of the computer helps but just for a while then it slows down or freezes again. I am also using Davinci Resolve 9 lite which is sometimes not able to adress the QTencoder when AME is open ... ?
Any Ideas for a solution?
Thank you!

I think it is a problem of Adobe QT32 Server. Adobe Media Encoder is encoding all Quicktime Movies through this Adobe QT32 Server, which is somehow the link between Adobe and Quicktime. But since Adobe QT32 Server is a 32bit application and Adobe Media Encoder a 64bit application it somehow blocks the Media Encoder. And if you have other applications running which somehow try to use Quicktime codec when Media Encoder is using the Adobe QT32 Server than everything slows down or collapses. These are my observations so far. I avoid any other video application as long as AME is open. For example: I close Davinci Resolve when I want to launch AME and close AME when I want to launch Davinci Resolve. This helps so far.

Adobe Media Encoder CS6 completely missing from Mastercollection CS6

Computer Environment:
MacBook Pro Early 2011
Graphics AMD Radeon HD 6490M 256 MB
Memory 16 GB 1333 MHz DDR3
SSD with 512GB; about 81GB are still free
Mavericks OS X 10.9.5
Adobe Mastercollection CS6
Quicktime Player (Standard)
Problem:
I am currently missing the sidekick Adobe Media Encoder (AME), even though I succesfully can run After Effects and Premier Pro.
I cannot locate the AME app anywhere on my hard drive to launch it manually.
Steps/general information:
I initially was able to run AME, after fixing another problem with launching it by deleting the ExportQuickTimeHost.bundle / QuicktTimeHost.bundle as I have described in another post (https://forums.adobe.com/message/7221143#7221143 – #26 is my post).
Unfortunately, the presets for Quicktime (I needed prores) were missing, even after I have done a workaround, by copying prores-codecs into AME plugins, as described in this post: martin-thoburn.com » Install the Apple ProRES codec without Final Cut or ProApps
The next time launching QuickTime, I was not able to open it again.
I uninstalled, reinstalled and updated After Effects and Premier Pro three times now and took away the QuickTimeHost.bundle from AME and Premiere Pro
I also tried resetting ACL (through Utilities, when starting the MacBook with option key pressed down) as suggested by Seth Goldin in the post https://forums.adobe.com/thread/1010136
I already tried wiping down the whole Adobe Suite, using the Cloud Cleaner Tool, delete the presets in the user library and then reinstall the apps: Photoshop, Illustrator, Indesign, Acrobat, After Effects and Premiere Pro. There is now only the CS6 (and not for example some CC apps) on my Computer. All apps are up to date.
I didn't install any other codecs by accident.
Since AME was again not launching (Splash screen wasn't showing me any plugins, AME could have loaded). I simply deleted AME by trashing it.
Now it's completely gone, even after reinstalling (and launching) After Effects and Premier Pro.
By trying to install AME's updates (6.0.1 and 6.0.2) I naturally get an error message, since the main app is missing.
I have battled with AME about half a year now, so things like reinstalling Lion and then Mavericks has occurred before as well.
And unfortunately, I am in the middle of a big project, which is due in a month and two days. Hope the links are not too confusing
– please look through them though, as the solutions I tried out are very clearly written in those posts.
Any help would be greatly appreciated.

Update in chronological order:
I uninstalled the Cloud, which I kept for making updates; I also uninstalled everything from Adobe (CS6 mastercollection)
I ran the Cloud cleaner tool
I reinstalled only Photoshop, Illustrator, Indesign, Premier Pro, After Effects and Acrobat. Bridge and AME were installed as sidekicks of Photoshop and AE/PP.
So this has solved problem 1 already.
On to problem 2 (update only):
updated all adobe software, incl. DynamicLinkMediaServerRetail-1.0.1-mul-AdobeUpdate
I installed Final Cut Pro 7
I (re)installed Quicktime 7.6.6*
I downloaded the Prores Presets for AME (as you suggested in post #2)
I tried opening AME – that did not work, as it hung on the ExporterQuicktimeHost.bundle
Went to AME app, right clicked on app icon to get "Show package content">Contents>Plug-Ins>Common and deleted ExporterQuickTimeHost.bundle and ImporterQuickTimeHost.bundle
repeated last step with Premiere Pro and AE
I opened AE
I tried importing the presets through AME>import>presets... That did not work. I get this pop-up message:
restarted my computer
tried again to import AME without luck
tried the solution of this discussion Re: Quicktime Export options are missing (only in AME) (post #8)
since I noticed that mine was changed back after the reinstallation. No luck.
restarted the computer again. No luck.
Put back only the ExporterQuicktimeHost.bundle into AME's package content
tried to open AME without luck
removed the Quicktimebundle once more to open AME (worked)
opened PP to check if I could export in queue: AME does not open by itself, still.
I tried opening a prores file (end as .mov) that I encoded at university (not on my provate computer) – did not worl
I checked if I could open a mov-file which was not encoded to prores: that worked.
I looked into Martin Thoburn's method again to try one more time in AME to find the settings "Quicktime". No luck.
I also have a third problem that may be linked to this, since it also has to do with PP and AE:
Re: Can anyone help? "DynamicLink" not available attempting to open Mov in Photoshop CS6
My post there is #22.
But now that I absolutely made sure that I do have the prores codecs,
I strongly suspect that it may also be a problem, which is discussed here:
Are the ProRes codec and .MOV file no longer supported?
...namely, that the codecs are just not visible. Unfortunately, this discussion is not resolved either.
HarleyTDavis's post #30 of this discussion Are the ProRes codec and .MOV file no longer supported?
suggests something complicated (because I yet would need another Adobe version), which I may try at some point.
Alright. That is all the effort that I can afford in time for this. I am too exhausted to go on so I'll do a workaround in FCP
– now that I got it – and will ask someone else to encode my outcome to a prores-Version.
If I feel like it – and yeah, I'd rather work with the Adobe Suite CS6 mostly – I'll come back to this discussion after a having clean wiped my computer and reinstalled everything.
Thanks to both of you for looking into this with me. I'm positive this can be solved – just not now.

Apple prores 422

Hello,
I have a question about importing a movie file.
When I import a 5dm2 Movie in Final cut pro X 10.1 and select that I want to encode it to Apple prores 422 or a proxy file it still imports as a original movie Quiktime -H264.
I tried all sorts off setting and prefferences but I never succeeded to import the file as a Apple prores 422.
With compressor it is possible, but then I have to fill in for all movies about 50 what export file I want. Not very practical.
It must be possible with Final Cut pro X.
Any help is welcome.
thank's
Richard

Hello,
I am still wondering about one thing.
When I imprt my 5dmark2 video intoo a nw library then after importing I select ttranscode media I check on
apple pro res and apple ro res proxy than the encode high quality files goes intoo the library folder called transcoded files.
Now question is will final cut pro x now automaticly uses these high quality prores files?????
because I allready asked before the movie info in the project sees the movie as H264.
sorry if I ask the same question but I am just wondering about this.
thank's again
Richard

Need advice about H.264 and Apple ProRes 422.

When exporting a "master file" I can encode the video as H.264 or Apple ProRes 422 (etc). The H.264 is more compressed but still in 1080p? Does this mean that I do not have to compress the file with "Compressor"? What is the advantage of using ProRes and what is the advantage of using H.264? I want of course the files to be as small as possible but still at the best quality. Any advice?
Thanks.

ProRes is an editing format. If you are archiving a finished project, you can create an extremely high quality "print" with H.264. ProRes 422 will use approximately three times as much memory. ProRes 422(HQ) roughly four times and ProRes 4444 up to 10 times (compared to the size of the file FCPX will export as H.264).
FCPX exports (shares) H.264 in highest quality (over 45Mbits/sec [if needed] for 1080p), you have no options to adjust for smaller files (or lesser quality from FCPX.)
To get "as small as possible," you'll need to learn more about compressing video. As a comparison (to FCPX), YouTube limits a maximum bandwidth of 8Mbps (used to be 5Mbps -- I *still* compress to 5Mbps before uploading.) Even compressed this highly, H.264 provides excellent results. [Compressing in ProRes is going from 4444 down to 422 Proxy (not to be confused with proxy media used in FCPX which is 1/4 resolution, i.e. 960x540 for 1080, ProRes 422.) You cannot compress each of the different ProRes flavors individually.]
You'll need other software to compress further than FCPX. I use Quicktime 7 Pro. Compressor is another way to go (Compressor will let you set "compression markers" so you can vary the bitrates through various sections of your work). The way to figure out your compression level is to find a section (less than a minute) with the highest motion high contrast (and/or changing gradients) and export at different bitrates. Watch for "jpeg artifacts" (blocking) and once you've gotten past that, that's the bitrate you should compress to. (I've had some clips that required at least 20Mbps.) It just takes a little practice to get a feel for it.

Adobe Media Encoder CS4 runtime error

I am wondering why I am getting a runtime error while
attempting to use Adobe Media Encoder CS4...As soon as I launch
Adobe Media Encoder CS4, it crashes I have installed and
reinstalled Flash a couple time, to see if this corrects the
problem, which it doesn't, and just last week it was working
fine...Does anybody have a ideal what is going on?

Don't know if this helps anyone else, bt the runtime errors i have been getting occur when I try to build and burn a blu-ray file. And they happen intermittently. In fact, on this project, I had burned several test blu-rays without difficulty. When I made one minor change on the penultimate version, and tried to burn again, the system crashed with a run time error. Then it crashed 9 more times over the course of the week.
Finally in frustration, I created an interim ISO file in Encore- ie in the build workstream, i selected burn an image file rather than burning a blu-ray disk. After this intermediate step completed, i then did a separate burn in encore but burned from the image file. No snags.
Not sure why but this program has trouble doing a sequence of activities. As it is, I already render and save the file before burning. Now I have another interim step to create an image file before burning.
In my next hardware change, I am going to switch to make Mac and Apple software. Enough of MS Windows and Adobe, the GM and Chrysler of the software industry. Hopefully what my friends tell me is true; that Apple stuff actually works.

Adobe Media Encoder (Error compiling movie) Unknown error when writing to Isilon OneFS 6.5.5.18

Adobe Media Encoder (Error compiling movie) Unknown error when writing to Isilon OneFS 6.5.5.18 while using Adobe Premiere Pro.
Process:         Adobe Premiere Pro CC 2014
Path: /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
Identifier: com.adobe.AdobePremierePro
Version:         8.1.0 (8.1.0)
Code Type: X86-64 (Native)
Parent Process: launchd [2538]
Responsible:     Adobe Premiere Pro CC 2014
Date/Time: 2015-01-06 14:04:23.500 -0700
OS Version:      Mac OS X 10.9.2 (13C64)
Report Version: 11
Crashed Thread: 55 Dispatch queue: com.apple.root.default-priority
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000
Customer created test export with 777 permissions and set mount parameters to the following:
mount_nfs -o vers=3,tcp,rdirplus,intr,nolocks,async,rsize=32768,wsize=32768
-- Original mount options:
     General mount flags: 0x40 async
     NFS parameters: vers=3,tcp,nolocks,rsize=32768,wsize=32768,rdirplus
-- Current mount parameters:
     General mount flags: 0x4000058 async,nodev,nosuid multilabel
     NFS parameters: vers=3,tcp,port=2049,nomntudp,hard,nointr,noresvport,negnamecache,callumnt,nolocks,quota, rsize=32768,wsize=32768,readahead=16,dsize=32768,rdirplus,nodumbtimr,timeo=10,maxgroups=16 ,acregmin=5,acregmax=60,acdirmin=5,acdirmax=60,nomutejukebox,nonfc,sec=sys
The pcap shows once the movie is created a lockup call is responded from Isilon with Error: NFS3ERR_NOENT
478         V3 CREATE Call (Reply In 479), DH: 0xea5f731c/QBRSN-0-0-1.mov Mode: UNCHECKED
479         V3 CREATE Reply (Call In 478)
484         V3 LOOKUP Call (Reply In 485), DH: 0xea5f731c/._QBRSN-0-0-1.mov
485        V3 LOOKUP Reply (Call In 484) Error: NFS3ERR_NOENT
V3 LOOKUP Reply (Call In ....) Error: NFS3ERR_NOENT -   This is by design of OneFS, we coalesce files and then flush them out to disk which is why the commit time is accurate but the file is not immediately available. however when an async option is used within the mount options this should be avoided if writing asynchronously to the cluster. Has anyone else seen this behavior lately? (current workaround is to store locally and transfer to the cluster via Finder)

That error can happen for many reasons...one of the reasons that I occassionaly get it is because I try exporting a movie to an external drive that has been formated in the old FAT32 instead of the NTSF standard. FAT32 only allows for file sizes up to 2 gigs. And as soon as it reaches that...I would get that error. I don't know if that is why you are getting that error...but it would be easy to check. 1) are you generating a file that is over 2 gigs? 2) is your drive that you are exporting to FAT 32 (just right click the drive in My Computer and select "properties" then just look for what it says next to "file system".

Adobe Media Encoder won't start

Not OP, but I have the same problem. AME just won't run. Double click, it's loading, I can see the process in Windows Task Manager but it just goes away again. Tried deleting that watch folder .xml but not working. Here's my spec from the FAQ:
What version of Adobe Media Encoder? Include the minor version number (e.g., Adobe Media Encoder CS6 with the 6.0.1 update).AME CC from premiere cc 7.0.1
What other Adobe applications do you have installed, and what application are you using Adobe Media Encoder with?Premiere Pro. Premiere Pro
Have you installed the recent updates? (If not, you should. They fix a lot of problems.)Used creative cloud to update to latest version
What operating system? This should include specific minor version numbers, like "Mac OSX v10.6.8"---not just "Mac".Windows 7. All update patch installed.
Are you using Adobe Media Encoder through a Creative Cloud Membership subscription?Yeah
What kind(s) of source footage? When telling about your source footage, tell us about the codecs, not just the container types. For example, "H.264 in a .mov container", not just "QuickTime".N/A. App won't launch
If you are getting error message(s), what is the full text of the error message(s)?No error message
Is the problem only occurring with a specific output format or encoding preset? If so, which one? If this is a custom preset not included with AME, then upload the preset file to a file-sharing site and provide a link.No.
What were you doing when the problem occurred?Booted up the computer. Launch AME.
Has this ever worked before?Yes.
What other software are you running?Google Chrome
Do you have any third-party codecs installed?Avid DNxHD, Cineform Studio
Tell us about your computer hardware. Be especially certain to tell us about third-party I/O hardware (e.g., AJA, Matrox, Blackmagic, MOTU).Regular desktop
Are you using Mercury Playback Engine GPU Acceleration in Premiere Pro?Yes.

I have a problem like this:
Anybody HELP?
Process:         Adobe Media Encoder CC [16188]
Path:            /Applications/Adobe CC/*/Adobe Media Encoder CC.app/Contents/MacOS/Adobe Media Encoder CC
Identifier:      com.adobe.ame.application
Version:         7.2.0.43 (7.2.0)
Code Type:       X86-64 (Native)
Parent Process: launchd [253]
Responsible:     Adobe Media Encoder CC [16188]
User ID:         501
Date/Time:       2014-02-05 01:15:39.418 +0100
OS Version:      Mac OS X 10.9.1 (13B3116)
Report Version: 11
Anonymous UUID: 7E5DC048-8DD8-5DA9-CFD0-539F29161D59
Sleep/Wake UUID: D2BBCDCA-68C3-4C86-B34D-57E4C884FDD8
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Application Specific Information:
terminating with uncaught exception of type dvacore::filesupport::dir_create_exception: $$$/dvacore/filesupport/DirCreate=The directory '@0' could not be created. Please check the parent directory protection or permission rights.
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib                  0x00007fff8a1c2866 __pthread_kill + 10
1   libsystem_pthread.dylib                 0x00007fff8998835c pthread_kill + 92
2   libsystem_c.dylib                       0x00007fff8f10dbba abort + 125
3   libc++abi.dylib                         0x00007fff95124141 abort_message + 257
4   libc++abi.dylib                         0x00007fff95149aa4 default_terminate_handler() + 240
5   libobjc.A.dylib                         0x00007fff9413c322 _objc_terminate() + 124
6   libc++abi.dylib                         0x00007fff951473e1 std::__terminate(void (*)()) + 8
7   libc++abi.dylib                         0x00007fff95146e6b __cxa_throw + 124
8   com.adobe.dvacore.framework             0x000000010022814d dvacore::filesupport::DirHelper::Create() + 813
9   com.adobe.AMEAppFoundation.framework          0x0000000104f285e9 AME::foundation::AppUtils::GetUserPresetDir(bool) + 425
10 com.adobe.Batch.framework               0x0000000105c0a842 AMEBatch::Initialize() + 2194
11 com.adobe.ame.application               0x00000001000273cb AME::app::AMEAppInitializer::AMEAppInitializer(exo::app::AppInitArgs&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >&) + 811
12 com.adobe.ame.application               0x000000010000ad6a AME::app::AMEApp::InitApplication(exo::app::AppInitArgs&) + 2426
13 com.adobe.exo.framework                 0x000000010513e77a exo::app::AppBase::Initialize(exo::app::AppInitArgs&) + 1066
14 com.adobe.ame.application               0x00000001000141a8 AME::RunTheApp(exo::app::AppInitArgs&, std::vector<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> >, std::allocator<std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > > >&) + 1576
15 com.adobe.ame.application               0x0000000100056a38 main + 424
16 com.adobe.ame.application               0x0000000100003f74 start + 52
Model: MacBookPro11,3, BootROM MBP112.0138.B02, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.19f3
Graphics: Intel Iris Pro, Intel Iris Pro, Built-In, 1024 MB
Graphics: NVIDIA GeForce GT 750M, NVIDIA GeForce GT 750M, PCIe, 2048 MB
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D54343147533641465238412D50422020
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x134), Broadcom BCM43xx 1.0 (6.30.223.154.49)
Bluetooth: Version 4.2.1f2 12982, 3 services, 23 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
Serial ATA Device: APPLE SSD SM1024F, 1 TB
USB Device: Internal Memory Card Reader
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM20702 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 17.1

Apple ProRes 422 (HQ) in Adobe Media Encoder

Similar Messages

Maybe you are looking for