Premiere Pro CC 2014 update and Media Encoder update fail to install

Hi -
I've been updating my CC applications. But PP CC 2014 and media Encoder say: "UPDATE FAILED". Naturally I cannot get through to Abobe. Does anyone have a suggestion?
Harry

Hi Harry,
Sorry, chat and phone support are closed on weekends for the video queue. We only have general support open on weekends. It's been this way for years. Sorry if that caused some inconvenience.
I hope you have solved your issue. If on Mac, you can update NVIDIA drivers in the NVIDIA control panel in System Preferences. AMD GPUs are merely updated when you update OS X.
Also, please check out the doc that was recommended: Installation failed. Error U44M1P7 | Updates
If you are still having trouble, contact us Monday through Friday 7AM-7PM PST here: Contact Customer Care
If you can't get your issue solved, send me a PM and I'll try and help.
BTW, I am not sure why your post is marked as correct. I do have that ability but did not do that. Sorry for that.
Thanks,
Kevin

Similar Messages

  • Why remove .flv export from Premiere Pro CC 2014? And what's a good workaround?

    Why remove .flv export from Premiere Pro CC 2014? And what's a good workaround?

    OK, so you want to put it on your own web page. That's fine as long as you know how to create a web page.
    The next thing you have to decide is how big do you want the video to appear on the web page. Many people just post on YouTube and then embed the video into their web page. That way, the video can take advantage of all of the various sizes that YouTube provides.
    In any case, I suggest that you use H.264. But the data rate depends on the size of the file. If you are going to display it in HD, then you probably want to start at about 20Mb/s and go up or down from there. The required data rate depends on what you find acceptable, and that depends on the amount of movement in the video. For example, a talking head next to a white board explaining something requires a lot less bits to represent the image because less changes are taking place from frame to frame. If you use 10Mb/s for that, you might find 20Mb/s or more is required to make you happy if you shot a football game from the sidelines.
    I generally use settings that look like this image. If you have any questions as to why I choose these settings, feel free to ask.

  • Latest Premiere Pro CC 2014 Freezing and crashing. Why?

    While editing a project everything runs smooth for a while, but then PPCC will freeze, become sluggish and or will crash from time to time. I have a new MacPro (Late 2013) 3.5 GHz 6-Core Intel Xeon E5, 64 GB ram, with duel AMD FirePro D700 graphics cards. I purchased my machine a few months ago. in Addition I'm editing off of a Thunderbolt 2 raid SSD drive. SO I don't know why my projects are freezing and crashing. This happens weather I'm editing DSLR 1080 footage Or RED 6K Footage. My system has more than enough power to handle my project, but premiere works for awhile then doesn't play nice. Why? PPCC 2014 by far has the best tools for editors in my opinion but if its not as stable a FCPX then why should we continue to use it. in addition, yes I have done a complete clean install so there should not be any conflicts.Running OS X 10.10.1

    My Premiere Pro CC 2014 also freezes when I try to export. I do not get any error messages, it just freezes and I have to restart my computer. The only way I can render is to Queue to Media Encoder CC 2014.
    I have tried posting my problem many times but this Community Forums will not accept my post and keeps telling me to 'try again later .m4'.

  • Premiere Pro CC 2014 Crashing and Bogging Down on Documentary Film Project

    We have been working in Premiere on this documentary film for months.
    As we reach completion it is beginning to really bog down and crash a lot.
    Equipment is
    iMac 27 inch 3.5 GHz Intel Core i7 Late 2013 Model
    Apple Cinema HD Display
    32 GB 1600 Mhz DDR3 RAM
    NVIDIA GeForce GTX 780M 4096 MB Graphics Card
    1TB internal SSD Drive
    We are running Premiere Pro CC 2014.0.1 and have remained there because we don't want to upgrade the software in the middle of the project.
    The media is all on the external drive. It's a USB 3.0 connection. There is quite a lot of footage that we are working with.
    We do have some After Effects comps that are linked in the project and we have exported the ones that are complete as QuickTimes to try to stop that from bogging us down.
    Any advice on how we can manage this crashing and freezing problem would be much appreciated.
    We don't have the cash to upgrade the computer and it has been working pretty well for us so far.
    Here are things we have done:
    Made a smaller timeline because we were working on one that was the entire movie.
    Turned off the secondary monitor and unplugged it.
    We are looking at moving the render cache off the external drive to a thunderbolt drive, but I'm concerned that this may take a long time.
    Any recommendations would be greatly appreciated.

    Splitting up the read/write items is rather a key to getting smoother operation out of PrPro. Either that or putting things on a large RAID-0/5, this sort of thing is covered over on the
    Tweaker's Page ...
    http://ppbm7.com/index.php/tweakers-page
    And I highly recommend you take a look. Their info isn't just "we think ... " ... but the results of many many carefully crafted test sequences run on many machines with all sorts of hardware bits & pieces. You can also register, download the PBM test and run it on your own machine. It takes only a little while to do so, and with the logger app that's included and posting the results back to them, you can get a very good breakdown on where your machine is doing ok ... and where any choke points are occurring.
    I think this would be good for you right now ... you need to get stuff done, not guess & try things.
    Neil

  • Premiere Pro CC 2014 crash and crash, and crash....

    Kevin and all you other Premiere Pro CC people out there.
    How long before Adobe will solve the problem of Premiere Pro crashing over and over again.
    I guess there is no one reading this that could tell me "it works for me".
    So Kevin (staff),
    Here is the 36-line-report you requested from me.
    For your information. Premiere Pro CC 2014_2 and back paddling to 8.0, they all crash.
    Most crashes are freeze on timeline. Thats is, nothing moves, sometime the music track
    just keep going and you can't stop it, so you have to hard quit.
    My power: Mac Pro 2014, 6 core, dubble graphic card, 64 GB memory, 1 TB SS storage
    This is my latest report:
    Process:               Adobe Premiere Pro CC 2014 [717]
    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.0.0 (8.0.0)
    Code Type:             X86-64 (Native)
    Parent Process:        ??? [1]
    Responsible:           Adobe Premiere Pro CC 2014 [717]
    User ID:               501
    Date/Time:             2015-04-03 14:55:56.729 +0900
    OS Version:            Mac OS X 10.10.2 (14C1514)
    Report Version:        11
    Anonymous UUID:        3C4BE865-15A1-83C0-2A8F-247384EECB0D
    Time Awake Since Boot: 19000 seconds
    Crashed Thread:        0  Dispatch queue: com.apple.main-thread
    Exception Type:        EXC_BAD_ACCESS (SIGSEGV)
    Exception Codes:       KERN_INVALID_ADDRESS at 0x00000000000000c0
    VM Regions Near 0xc0:
    -->
        __TEXT                 0000000100000000-0000000100003000 [   12K] r-x/rwx SM=COW  /Applications/Adobe Premiere Pro CC 2014/Adobe Premiere Pro CC 2014.app/Contents/MacOS/Adobe Premiere Pro CC 2014
    Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
    0   com.apple.CoreText             0x00007fff8c98db95 TLine::~TLine() + 243
    1   com.apple.CoreFoundation       0x00007fff9105ca9e CFRelease + 526
    2   com.apple.HIToolbox           0x00007fff8d5a0944 TCoreTextLineInfo::~TCoreTextLineInfo() + 34
    3   com.apple.HIToolbox           0x00007fff8d5a0913 TLayoutInfo::Clear() + 51
    4   com.apple.HIToolbox           0x00007fff8d5a078f TCoreTextEngine::Invalidate() + 49
    5   com.apple.HIToolbox           0x00007fff8d59d0a8 TCoreTextEngine::Init(void const*, THIThemeTextInfo const*) + 92
    6   com.apple.HIToolbox           0x00007fff8d59cf00 TThemeTextCache::Create(void const*, THIThemeTextInfo const*) + 460
    7   com.apple.HIToolbox           0x00007fff8d59c8bf DataEngine::GetTextDimensions(void const*, double, HIThemeTextInfo*, double*, double*, double*) + 259
    8   com.apple.HIToolbox           0x00007fff8d59c785 HIThemeGetTextDimensions + 185
    9   com.apple.HIToolbox           0x00007fff8d5e124e HIStandardMenuView::MeasureItemTextWidth(__CFString const*, TextLayout*, __CTFont const*) + 122
    10  com.apple.HIToolbox           0x00007fff8d5e0a3f HIStandardMenuView::GetItemWidth(float, TextLayout*, unsigned char*) + 719
    11  com.apple.HIToolbox           0x00007fff8d5dde02 HIStandardMenuView::GetOptimalSizeSelf(CGSize*, float*) + 878
    12  com.apple.HIToolbox           0x00007fff8d5dda1c HIView::SendGetOptimalBounds(CGRect*, float*, CGSize*) + 416
    13  com.apple.HIToolbox           0x00007fff8d5dd84f HIView::GetOptimalSize(CGSize*, float*, CGSize*) + 45
    14  com.apple.HIToolbox           0x00007fff8d5dd755 HandleCalculateMenuSize(OpaqueEventRef*) + 154
    15  com.apple.HIToolbox           0x00007fff8d58213a MenuData::EventHandler(OpaqueEventHandlerCallRef*, OpaqueEventRef*, void*) + 358
    16  com.apple.HIToolbox           0x00007fff8d58098c DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1260
    17  com.apple.HIToolbox           0x00007fff8d57fdce SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 386
    18  com.apple.HIToolbox           0x00007fff8d57fc42 SendEventToEventTargetWithOptions + 43
    19  com.apple.HIToolbox           0x00007fff8d5dd4e4 _CalcMenuSizeOnDevice(MenuData*, unsigned short, unsigned int, CGRect const*, unsigned int) + 763
    20  com.apple.HIToolbox           0x00007fff8d5e1bad GetInitialMenuRect(MenuSelectData*, MenuData*, unsigned char, Point, unsigned short, Rect*, unsigned int*, CGPoint*) + 261
    21  com.apple.HIToolbox           0x00007fff8d5f6f32 GetCurrentMenuRect(MenuSelectData*, unsigned int*, CGPoint*) + 110
    22  com.apple.HIToolbox           0x00007fff8d605890 DrawTheMenu(MenuSelectData*, __CFArray**, unsigned char, unsigned char*) + 582
    23  com.apple.HIToolbox           0x00007fff8d60548c MenuChanged(MenuSelectData*, unsigned char, unsigned char) + 356
    24  com.apple.HIToolbox           0x00007fff8d5f1e36 TrackMenuCommon(MenuSelectData&, unsigned char*) + 1211
    25  com.apple.HIToolbox           0x00007fff8d604fb1 MenuSelectCore(MenuData*, Point, double, unsigned int, OpaqueMenuRef**, unsigned short*) + 510
    26  com.apple.HIToolbox           0x00007fff8d604c5e _HandleMenuSelection2 + 446
    27  com.apple.AppKit               0x00007fff9191b8be _NSHandleCarbonMenuEvent + 277
    28  com.apple.AppKit               0x00007fff917b72f0 _DPSNextEvent + 1843
    29  com.apple.AppKit               0x00007fff917b6730 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 194
    30  com.apple.AppKit               0x00007fff917aa593 -[NSApplication run] + 594
    31  com.adobe.Frontend.framework   0x00000001000c948d FE::MacApplication::RunSelf() + 45
    32  com.adobe.Frontend.framework   0x0000000100047cca FE::Application::Run(std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&) + 4058
    33  com.adobe.Frontend.framework   0x00000001000cad44 FE::AppMain(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int, void*) + 276
    34  com.adobe.Frontend.framework   0x00000001000d1f25 FE::Run(ASL::ObjectPtr<ASL::Module, ASL::AtomicValue> const&, std::basic_string<unsigned short, std::char_traits<unsigned short>, dvacore::utility::SmallBlockAllocator::STLAllocator<unsigned short> > const&, int) + 581
    35  com.adobe.AdobePremierePro     0x00000001000018ac main + 508
    36  com.adobe.AdobePremierePro     0x00000001000016a4 start + 52

    Hi,
    Sorry to hear about the experience. Can you please try this:
    Go to the following locations:
    Location 1: When in Finder, click on Go > Go to Folder > ~/Library/Application Support/Adobe
    Location 2: Go > Go to Folder > ~/Library/Preferences/Adobe
    Location 3: Documents > Adobe
    In all the locations, rename the 'Adobe' folders to 'OldAdobe'
    Launch Premiere, accept the License Agreement and see if it works.
    Note: You will lose your customized workspaces and keyboard shortcuts. Wait for Premiere to generate the media cache the first time you launch the project.
    Also i would suggest you to make this change if the playback issue continues and see if it works better:
    Under File > Project settings > General, change the Video renderer to Mercury Playback Engine software only. Click OK and select "Delete Previews"
    Thanks,
    Rameez

  • Premiere Pro CC 2014 Crashes During Media Export

    Hi, I have diligently applied several of the fixes listed here:
    Re: Premiere Pro CC 2014 freezes frequently and crashes
    However, Premiere Pro CC crashes at about 10% of the video export -- it gets through the audio stuff as far as i can see.

    yeah, checked out the article.
    my computer is not shutting down. premiere is crashing. the media exporter is crashing.
    it gets through the audio then it crashes during the video processing.
    i even tried to hit pause every 2 seconds.
    a test exports fine from premiere 6.0, but i am concerned that 6.0 might crash if i rebuild the whole project.
    hmm i have an idea.
    obviously i would much rather the software worked.

  • Premiere Pro freezes after exporting with Media Encoder

    So I'm running the latest version of CC.
    Mac Pro, OSX 10.9.2, 8-Core Xeon, 24GB RAM, ATI Radeon HD 5870 1GB
    I've got a very simple and straight forward timeline. After sending "Exporting Media" via queue to Media Encoder, everything exports fine. But after returning to Premiere, it has become impossibly slow--practically frozen. No crash, no error message, just takes about 60 seconds for any clicks to register. I click save project, and the saving progress bar does not visibly progress, yet it seems to actually successfully save the project, because closing and launching premiere, the file is saved up-to-date just fine.
    So for the past few days, I've been saving --> export/queue timeline --> quit premiere --> allow queue to complete --> then relaunch premiere... Of course, this is only a temporary work around.
    Now, if I "Export" the media only without queueing in Encoder, it does fine and premiere remains stable and normal.
    Ideas?

    Exact same problem here, plus exports are slow
    Specs
    latest CC
    OSX 10.9.2
    3.4GHz Core i7
    32Gb 1600MHz DDR3
    GTX 680MX GPU
    4TB Thunderbolt GRAID, footage/project files
    3TB USB3 Seagate for cache
    1TB Apple for system

  • Premiere Pro not Exporting to Adobe Media Encoder

    Never had this problem before on a Mac. Now using a Windows 7 Machine.
    Intel Xeon CPU E5-2630 v3 @2.40 (2 processors)
    64 GB Ram
    Nividia Quadro K4200 v. 2.1.2
    Trying to export a Premiere Pro sequence to Media Encoder for encoding. Nothing pops up in AME. And if I try to add the sequence from within AME, doesn't work either. Exporting directly from Premiere DOES work though. Any ideas?

    This was my first video in Premiere Pro CS4.
    Information Hard Disk #1 :
    Manufacturer :
    Seagate
    Model :
    ST3500418AS
    Serial Number :
    5VMFTSYR
    Revision (Firmware) :
    CC38
    Family :
    Seagate Barracuda 7200.12 family
    Serial ATA :
    Yes
    Serial ATA Version :
    2.0  -  (SATA-300)
    Support :
    ATA8-ACS
    Size :
    500GB
    Solid State Disk (SSD) :
    No
    Speed :
    7200 rpm
    Cache :
    16 384KB
    Information Hard Disk #2 :
    Model :
    MAXTOR STM3320620AS
    Serial Number :
    6QF4Z8WZ
    Revision (Firmware) :
    3.AAE
    Family :
    Seagate Maxtor DiamondMax 21
    Serial ATA :
    Yes
    Serial ATA Version :
    1.0  -  (SATA-150)
    Support :
    ATA/ATAPI-7
    Size :
    320GB
    Cache :
    16 384KB
    ECC Size :
    4
    Multiple Sector :
    16
    Thanks for your reply

  • Premiere Pro Unresponsive after queuing to Media Encoder

    In the current version of Premiere Pro (8.1.0), every time a send a sequence to the Media Encoder, Premiere becomes unresponsive. But not in a spinning beach ball of death fashion. It's like the UI is non responsive, with some very strange behavior. For example, when I try to quit and save, the save dialogue just sits there until I have to force quit the application.
    Any thoughts? This is extremely annoying!

    Exact same problem here, plus exports are slow
    Specs
    latest CC
    OSX 10.9.2
    3.4GHz Core i7
    32Gb 1600MHz DDR3
    GTX 680MX GPU
    4TB Thunderbolt GRAID, footage/project files
    3TB USB3 Seagate for cache
    1TB Apple for system

  • Exporting from Premiere Pro.  Takes forever for Media Encoder to start.

    When I exported a timeline out of PrePro to the Media Encoder and press "Start Queue" it took it over 19 minutes before it began rendering.  Is this normal?

    Morning all
    Fair point John.
    Webshark2000, the orignal poster of this topic, has got Vista 64bit, so he can make use of the more memory.
    I understand that memory use for  CS4 is:
    Premiere -  2gigs
    Encore - 2gigs
    Media Encoder - 1 gig
    + Windows and other apps you may have running!
    So if you don't have around 5 - 6 gigs ram, Windows will be doing ALOT of paging! Thus slowing the system and render times down.
    64Bit and tons of ram -  is the way forward. It rocks with it!
    Hope that helps - Shaun

  • Premiere Pro CC 2014.2 and AVCHD audio bug

    The AVCHD audio is mangled by Premiere. Details below.
    I recorded a 2 act play and I'm editing it in Premiere. Each act is about 1 hour so the camera recorded spanning MTS files.
    Act 1 imported perfectly. No problem.
    When importing act 2, I noticed some audio glitches and the audio quickly lost sync. After further investigation, I found that:
    - The AVCHD file plays perfectly fine in Quicktime player
    - The audio track in Premiere is exactly half the length of the video
    - When listening closely, it sounds like it plays 1 second, skips 1 second, plays 1 second, etc. Which is consistent with losing sync gradually and finishing the audio twice as fast as the video.
    It seems related to the problem in this thread. I'm at a loss as to what to try next.

    After posting the initial thread, I reinstalled Premiere Pro CC (7.0), created a new project, imported the AVCHD files and the audio was synched.
    I then opened the file in CC 2014 and the audio was still synched.
    So it appears to be a bug in AVCHD conforming in 2014 only. While not a fix, I hope this workaround will help others.

  • Questions on Premiere CS4 4.2.1 and Media Encoder 4.2.0.006

    What I am trying to do is take a single long captured file and break it into individual clip files.   I know I could have used timecode based scene selection when importing to break up the clips into individual files, but the timecode was messed up and capturing to one long file was the only option.
    Question 1) How, if possible, can I export mutiple clips on the timeline to ME at one time.  It just seems silly to have to move the work area start/end points for each clip, export it, and then move the work area start/end points to the next clip and export and so on for, say, 50 clips on the timeline.  With clips the start/end points are obvious; the start of the clip and the end of the clip.  And a simple Clip 1, Clip 2, Clip 3, Clip 4... naming convention would be fine.   Is there a way to do this?  Or even just draging and dropping a clip into ME would at least save me the time of moving the work area around (which, again, seems repetative since the whole clip is being exported).
    Also, once I have manually exported, say, 20 clips into ME, it is taking about 5 minutes (after it indicates it is encoding) to actually start encoding.  Once the progress bar begins to show the clip is encoding is goes quickly and I get the green check mark.  But then the next clip says encoding and it again takes about 5 minutes for the progress bar start to show encoding is occuring.  So to encode 20 clips (ranging from 10 seconds to maybe a minute long each) it takes up to 2 hours.  These are simple DV captures being exported to .AVI clip just to break them into individual clip files, so no transcoding or scaling or effects are involved.
    Question 2)  Are there any settings that I may have/have not set that can speed up the process?  Is this normal encoding speed?
    PC Info:
    Home Build
    Intel Q6600 2.4GHz QuadCore CPU
    Nvidia GeForce 8800 GTX graphics (latest driver from Nvidia)
    2GB DDR2 PC-800 RAM
    ASUS Maximus Formula (SE) (latest BIOS from ASUS)
    SATA 3gb/s drives

    Oh, and I am using Windows 7 32-bit

  • Why does Premiere pro locks out effect and media render when I have an active creative cloud account?

    PP was operating correctly with full effects.  Relaunched today with active cc acct confirmed and effects got locked out just like I have a trial version.  Any suggestions.  We relaunched PP several times with the same result.

    If Premiere is acting weird restart computer. Hold down shift+alt while opening Premiere until welcome screen.
    See if that will help.

  • Premiere Pro CC 2014 and Medie Encoder CC 2014 problem

    Hello there,
    Every time that I am willing to export my project my Premiere Pro CC 2014 stop responding all together. I tried the short cut (Commend+M) or going through the Manu bar. the result is the same, Premiere Pro CC 2014 just freezes and does not respond to anything till I force quit it and restart it allover again. I tried exporting from Premiere Pro it self, without using Media Encoder, but the problem remains the same.
    I am using the new Mac Pro. I heard Adobe Premiere Pro is experiencing  problems with the New Mac Pro. Is that true? Or is there other issue?
    Thank you and looking forward to hear back,
    Maruf

    I am having a similar problem.
    Premiere Pro CC 2014 suddenly decided to crash every time I export to either Adobe Media Encoder or within Premiere itself.
    The encode will usually go for 5-10 minutes before the programs either spits out a "serious error has occurred" window, or it just sits there frozen until I force quit.
    I did find a work-around for the moment. If I open AME and FILE > OPEN, select my project and then the sequence I want, AND put it in Software render mode, it will work.
    My timeline is 2K, 58 minutes in 23.976
    Only effects applied are Lumetri LUTs - no third party.
    I've exported as recently as a week ago without issue.
    Running OSX 9.5 on an X99 board
    3.75 GHz 8-core
    64GB 2400 MHz RAM
    EVGA Titan Black 6GB
    Because I can get my renders out, I am not too concerned. Either there is something wonky with my timeline that screws with any graphics enabled rendering, or there is a bug that is have the same effect. I will try rendering on another of my edit bays that utilizes a GTX 580 that I KNOW works. The Titan is pretty new to my workflow.
    Thanks Adobe, for checking this out.

  • H.264 encoding issues with Premiere Pro CC 2014

    After updating to Premiere Pro CC 2014 yesterday, I see encoding artifacts on my H.264 exports.
    Same source video imported into CC v2014 and v7, and exported using the YouTube 1080p 29.97 fps settings. The artifacts manifests itself as softness/blurriness in parts of the image every few seconds, especially notice the area with a red circle below.
    Here are the source file (GoPro HERO3 Black Edition), the v2014 render and the v7 render.
    Original: https://drive.google.com/file/d/0B2rJe0xgMTxFYXJiMjZpZ0stUzQ/edit?usp=sharing
    CC v2014 render: https://drive.google.com/file/d/0B2rJe0xgMTxFQ1B0Z09GS3I0a1E/edit?usp=sharing
    CC v7 render: Premiere Pro CC.mp4 - Google Drive
    [Version numbers corrected.]
    Message was edited by: Jim Simon

    Mark Mapes wrote:
    This is a known issue introduced in CC2014.0. Some h.264 encodes have blurriness or noise periodically in some areas of the frame. The problem is most pronounced in regions of the frame with very little detail, like grass or pavement--or the T-shirt in the sample frame. We are working on a fix. Before you ask when the patch will be forthcoming, I'm not authorized to even hint at the timeframe.
    Unfortunately, the only real workaround is to export to a format other than h.264. If that's not an option for you, then your best bet is probably to keep working in CC7.2.2 until the patch is released.
    Sorry, but thats not completely true and by far not the correct answer:
    The problems with random artifacts occurred with the introduction of a new version of H264 in CS6 but there you still had the option to export with the previous H264 Version via Media Encoder. 
    Since the previous H264 version is not available in CC, using CC7.2.2 is not a solution either.
    BTW
    Updating to CC and using the new Mac Pros with Mavericks is currently a total mess - no open cl rendering, random crashes, no usable h264 ... thanks adobe!!
    ... but we can track masks in premiere now ... wow!

Maybe you are looking for