Premiere Pro CC and CS6 freeze on export

I have a problem with Premiere freezing when exporting a video sequence.
The sequence consists of about 5 min of video from 10 different clips, so it not very big.
I want to export to H.264 format, but a few percent into the export everything freezes and I have to turn off my PC. The same thing happens with export to MPEG2 and MPEG4 formats, but not if I export to AVI format.
At first I suspected on of the clips was causing the problem, but I'm able to take all the clips one at a time, and export each one to H.264 format without any problems. Even If I take the new exported H.264 clips and put them together, and export them again as one file, it will freeze again.
The problem is the same in Premiere Pro CC and in Premiere Pro CS6.
Any ideas on what might be causing this?
/Mark

More information needed for someone to help... please click below and provide the requested information
-Premiere Pro Video Editing Information FAQ http://forums.adobe.com/message/4200840

Similar Messages

  • Only Premiere Pro CC and CS6 won't launch on startup after installing CC 2014

    Ever since I downloaded CC, I cannot open Premiere Pro on CC or CS6 -- which CS6 worked fine before. However, all other installed apps on CC work fine, including After Effects. My specs are all up to date, (2012 Macbook Pro, 8GB RAM, 64-bit, etc) and figure there's some kind of bug within Premiere. My Adobe preference folder is set to Read&Write and don't know what to do. I have read that people downloaded and ran CC Cleaner but to no avail to fix the underlying issues. Need help ASAP. Thanks in advance.

    Hi,
    Launch Premiere while holding the Option key on the keyboard. If that doesn't help, 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.
    Thanks,
    Rameez

  • How would you edit 4k in Premiere Pro CC and export in 2.5k and 1080p (all within premiere pro, is it possible?), how would you edit 4k in Premiere Pro CC and export in 2.5k and 1080p (all within premiere pro, is it possible?)

    how would you edit 4k in Premiere Pro CC and export in 2.5k and 1080p (all within premiere pro, is it possible?), how would you edit 4k in Premiere Pro CC and export in 2.5k and 1080p (all within premiere pro, is it possible?)

    Edit 4K and export what ever you want from AME

  • Adobe Premiere Pro.exe and Dynamiclinkmanager.exe *32  not stopping after closing PP CS6.03

    PP 6.03 will not restart after closing program.  When I try to re-start nothing happens when clicking on the PP6 icon. Looked in task manager and found that Adobe Premiere Pro.exe and Dynamiclinkmanager.exe *32  are not stopping after closing program. Once I manually stop the processes PP will restart as normal. This is on Win 7 Sp1, HP Elitebook 8760W Matrox MXO2 LE. Also Audio meters are not active during capture, can't change clip name during capture.

    Hello Elcuad, and Canino video,
    Please verify the following steps and report back  your findings:
    - uninstall the currently installed MXO2 effects and drivers
    - go to control panel - user accounts - and locate the account you are using, then drop down the UAC level all the way, ok and reboot
    - download our 7.02 driver with Internet Explorer, followed by our effects
    - after the files are downloaded, right click each file, go to properties, and confirm they are not blocked, if they are click the unblock button
    - reinstall the Matrox driver, again, the one we just downloaded, followed by the effects, reboot
    - go to start, all programs and locate the premiere icon, hold shift and ctrl keys down, and launch this particular icon, keeping the keys down until the application opens up
    - please build a new project and try it out

  • Premiere Pro CC 2014 keeps freezing when loading projects from Premiere Pro CC

    Hi everyone,
    I'm reporting this issue in case someone else would have the same problem.
    I just downloaded the 2014 version of Premiere Pro CC, and when I'm loading a project from Premiere Pro CC into CC2014 I have the software freezing and being unable to even play the loaded sequences. It seems that dynamic link is having trouble linking the CC and the CC2014 version of Premiere Pro.
    Until now the only solution I found was to kill the process of the software and start it again, after 8 times I got my sequence loaded alright, then sometimes it is freezing again, killing process, starting software again, and so on. Does anyone has the same problem ?
    I'm running a Windows 7 Ultimate PC with 12Go RAM dedicated only to Premiere Pro.
    Cheers,
    Vincent

    Hi Vincent,
    I feel your pain, you are not alone. Here are my machine specs and my very frustrating situation, if anyone has any idea as to how I should move forward, I would really appreciate the input/advice...
    iMac - 27" Late 2013
    Processor  3.4 GHz Intel Core i5
    Memory  12 GB 1067 MHz DDR3
    Graphics  NVIDIA GeForce GTX 780M 4096 MB
    Software  OS X 10.9.4 (13E28)
    I'm having similar issues that began when I installed Premiere Pro CC 2014, and actually got worse with the latest update/release. The majority of my projects worked fine at first, but the update last week ended that quickly. I did what I know I never should do and updated Adobe CC while completing a project on a deadline. I thought some of the fixes would help me complete the project sooner. Needless to say, the deadline has passed, my client is pissed enough to not pay me or hire me again and I'm stuck with an almost-there version that I can't export correctly because of this software. This is my problem, not Adobe's, but I didn't expect such a detrimental update to halt my operation.
    After doing some research, I found that some plugins could be the cause of some specific editing issues, mainly due to incorrect or inaccessible folders - who knows if its Dynamic Link, CC apps or 2014 apps. I concluded that my issue at the time was a plugin permissions issue on the Adobe "Preference" Folder, so I reset the permissions on the folder so that CC and 2014 apps would be able to access its contents without any problems. This was the wrong decision. For some reason, resetting this folders permissions also effected the main HDD, it's Kernel Text files and their respective permission. I could not boot my machine, just got the Apple and spinning wheel until I had to power down. I ended up on the phone with 3 different AppleCare reps who helped me at least be able to turn the machine back on and access my desktop/files, apps, etc. Outside of this, no one could offer anything other than "Uninstall the problematic application, reboot, reinstall, etc..." or "Backup your files and reimage the HDD." When I mentioned the recent CUDA driver update for my graphics card (NVIDIA GeForce GTX 780M 4096 MB now running CUDA Driver Version: 6.0.51), it was like they had never heard of graphics cards being used in their machines.
    Resetting permissions on Adobe Preference Folder...
    This is what I read would get the CC and 2014 apps communicating correctly so that they could utilize my plugins. There is a problem, I believe, in that their are TOO MANY locations where Adobe folders/components live. There are 3 "Preferences" folders that I found, and I don't know which effects what process, but the folder I changed permissions on clearly effects the operation of all of the CC & 2014 apps I had installed, as well as my HDD. Kernel Extensions and the entire system.
    Based on my perceived effects of the Preference folder, I needed to uninstall everything, run the Adobe CC Cleaner Tool, download/install just the 2014 releases and see if that resolved the issue. I'm not downloading CC apps, the 2014 releases should run fine on their own. I've yet to confirm this with Adobe, as what I've read has simply said to install the new release next to the CC apps, rather than on top of, as traditional update releases work. Anyway, one by one, I reinstalled the 14 apps that I use on a regular basis on a "clean" machine with no trace of previous Adobe apps.
    After reinstalling (without any plugins), I was at least able to open Premiere Pro from the Application folder and work for a few minutes before both Program and Source monitors froze and had to force quit the app. If I try to open the Project File by double clicking it in the Finder, SpeedGrade opens up instead of Premiere Pro - never seen that before. I also had to force quit to end that process and reopen in Premiere instead of SpeedGrade.
    So back to Premiere, if I do have success in opening a project in the right application, Premiere freezes - if not immediately, eventually it will just stop responding. The video clips, sequence segments and UI freeze, but the audio will keep playing until I force quit. When I force quit, Premiere Pro doesn't close entirely. The UI closes, but the process still runs. I've even force quit from Finder, force quit again from the Dock, Shut Down the machine, restarted and Premiere Pro will still be open, but "Not Responding", so I force quit again and open the project. Just now, I opened PP, made minor edits to a sequence, sent it to Media Encoder, exported, but the video I tested exported without audio. I force quite PP twice just before that and it is still running now, but again, it is "not responding".
    Ultimately, none of this works, nor have my attempts at resolving these many issues. One thing I know is that there is something VERY WRONG with either the latest release/update to 2014 apps, the Preference folder or the permissions that were changed.
    As I mentioned previously, and what I think is a major oversight by someone at Adobe, is that for some reason the permission changes to ONE Adobe folder also effected my entire system and Macintosh HD. Some Kernel Extension files went missing, which is never good and should not happen when resetting folder permissions, so I believe my issues are far greater than the faulty Adobe CC 2014 applications, and is the cause of many of my problems right now. If I can't get things sorted soon, I'm going to reimage my HDD and start from scratch. As much as I would like to avoid this, I really have no choice if I want to get back to work and not lose clients over inexplicable technology issues.
    If I find a solution, I will repost, but I think Adobe has to make some serious fixes on this release before anything is resolved entirely. I pay them monthly and rely on their software and platform to work without issue, which is foolish - I know, but I've used CC since it was introduced and it has work well enough until now.
    Is there anyone at Adobe that can offer some advice??

  • Problems with Dinamic Link between Premiere pro CC and After Effects CC

    I'm having serious problems with dinamic link between premiere pro and after effects, really serious problems that have 2 big projects in trouble (a documentary and a video clip) and I had to redo all the work pipeline to the consumer.
    The documentary for a spanish TV was made on CC 2014 and a video clip was made on CC. Both of them with a lot of after effects composition in the premiere pro timeline. Render freeze, a lot of playback issues, and many more problems... Until I decided to remove these links between premiere and after effects and render out all the after effects compositions one by one and insert as clips in premiere pro. 1 week working away with back and fourth.
    I've got a huge workstation:
    i7 4990
    32Gb ram
    GTX780 3gb
    256 gb system ssd
    2 Tb project storage
    *All my hardware and software are update.
    I know that a lot of folks are on the same huge problem and I want to ask everyone:
    How do you save this?
    What is your pipeline?
    Are there any solution?
    Best practice to use dinamic link in a huge project?
    Thanks,
    Ruben Gimenez.
    R&D iceblink.es
    www.rambot.es

    Thank You, Jim -
    Unfortunately that specifically did not work.
    Based on another comment sent to me, here is what did.
    In PProCC
    File > Adobe Dynamic Link > New After Effects Composition
    In AECC
    From that composition created from PPro, I imported the project (aep) initially created in AECC from another team member. Saved the file.
    Back in PProCC
    File > Adobe Dynamic Link > Import After Effects Composition
    Magic.

  • Premiere Pro CS5 - Media Encoder Crash when Exporting to MPEG-2

    System:
    Core i7 920 @ 3.8 Ghz
    Gigabyte X58A-UD3R
    12GB DDR3 1600
    External Sound Card - M-Audio ProFire 610
    OS Drive - 2x300GB WD Raptors - Raid 0
    Project Drives - 3x300 WD Raptor - Raid 0
    Video Card - Geforce GTX 285 1GB
    Adobe Premiere Pro CS5 and Media Encoder CS5 continually crashes or hangs every time I try to export to MPEG-2.  I can successfully render to every other codec without any issue, but need the MPEG-2 for an Adobe Encore Project.
    The project is approximately 38 minutes long and contains AVI and MP4 files, all of which were ripped from DVDs as I'm producing a reel for a producer who provided his DVDs for me to rip and use as content.
    Possible issues:
    1.   Currently have Magic DVD Ripper and DVD Fab installed (codec conflicts?)
    2.   Originally ripped the DVDs at 630x360 (my mistake - hadn't really worked with a DVD ripper before and was the largest avi pre-set) and I'm exporting to MPEG-2 standard 720x480 Widescreen)  (I know I should've just ripped them as the original lossless MPEG-2 files - I'm a tool)
    2.   Blank space in the timline (there are a number of these)
    I would like to get some input before I try to export to MPEG-2 again as I blew a capacitor on my old mother board (Gigabyte x58-ud3r) after I had gotten my computer to start rendering a MPEG-2 after about 50 tries to export/launch media encoder set on MPEG-2.  I just installed my new motherboard to replace it.  Clearly MPEG-2 taxes the system more so than any other codec (from what I can tell).  However, I thought the issue with the blank space/no media in the timeline was fixed with CS5.  I saw in a previous post that someone thought that ffdshow was conflicting with AME.  I don't have ffdshow, but I believe that's a ripper program like Magic and DVDFab.

    I experienced this at one point.  Searching the WEB I saw suggestions that there was a problem with a recent version of Quicktime.  (I have no idea why the quicktime player would have an impact.)  However, reverting to an earlier version of Quicktime fixed the problem.  Search this board using quicktime as a search phase.  The quicktime web site allows you to download the earlier versions.  I'm not at my editing machine, but I believe that I am at version 7.5.2.

  • XDCAM HD workflow with Adobe Premiere Pro CC and Macbook Pro

    Hi folks,
    I have an assignment for a TV production to secure and convert the data (mxf files XDCAM HD 422 1080i 50 / 50 Mbit/sec with 8 audio channels) from Sony XDCAM camcorders (PDW-700) for postproduction.
    The producer wants me to convert the mxf files during production to Apple ProRes 422 (HQ) for faster and smooth editing during postproduction.
    I'm not sure about the final output yet, but I guess it will be either 720p50 or 1080i 25, since the production will be broadcast and as far as I know this is the standard for HD on German television. It is also not clear which NLE will be used for editing (usually one of the producers edits their projects with FCP, but this time they've got their hands full and are still looking for someone to outsource postproduction.
    Unfortunately, my Macbook is getting fixed as we speak, so I can't try things out.
    Since this is the first time I'm doing this workflow, could someone please check if I got everything right?
    1. Can someone please confirm that I can actually convert the mxf files using AME CC to Apple ProRes 422?
    Or do I need to install any other tools/converters for this task? Does MPEG streamclip do the job? Any other freeware?
    2. When converting to Apple ProRes422, the producer suggested to deinterlace the footage (1080i 50) to 25p, if 720p or 1080p I have to find out tomorrow since our conversation got interrupted this afternoon.
    In my opinion this doesn't make sense, though. First, if output to 1080i 25 it has to stay interlaced anyway. Second, in case the output will be 720p 50 I would edit the footage either natively or in Apple ProRes 422, but leave deinterlacing until the very end when outputting to the final format. This way I could use an advanced deinterlacer, e.g. the one from Magic Bullet Suite, rather than just checking some deinterlace box in the export settings for Apple ProRes 422.
    The reason the producer suggested to deinterlace right away when using  an intermediate like ProRes was that she and the client got irritated by the jagged lines from the interlaced footage when editing the last project with the same requirements on a progressive display.
    3. What would be the best solution to tackle this issue (jagged lines) during editing?
    As I said my Mac is getting fixed, so I have no way of trying things out,and I usually edit DSLR footage which is progressive anyway.
    But if I remember correctly I can switch my monitor between 1080p and 1080i. This should do the trick, shouldn't it?
    4. Can I keep all of the 8 audio tracks when converting to ProRes using AME CC ?
    5. Is ProRes422 (HQ) really necessary, or is the regular quality sufficient for this kind of job?
    6. Let's assume the whole project would be edited within Adobe Premiere Pro CC and  system specs as stated below:
    Since Adobe Premiere Pro CC has native support for  XDCAM HD is there any advantage of using an intermediate like ProRes at all?
    How smooth is native editing with XDCAM HD in Premiere Pro CC? I don't think there will be more than 3-4 video tracks in use...
    Thanks for your help!
    working with
    Adobe Premiere Pro CC and Adobe Media Encoder CC
    Apple MacBook Pro
    Intel Core  i7 Quad Core Prozessor
    2.3 GHz and 6MB L3 Cache
    16 GB RAM 1600MHz DDR3,
    256 GB SSD
    Intel HD Graphics 4000 512MB + nVidia GeForce GT 650M with 1 GB GDDR5 RAM

    Thanks Jim! I knew there must be a reason xdcam is widely uses for eng aquistion :) I think they used FCP 6 or 7 on their last project... So what about monitoring interlaced footage on a progressive screen? Any advice on that? Is there a converter built in to APP CC that deinterlaces in realtime when monitoring interlaced sources on a progressive screen? And would you agree that deinterlacing source material is best left right before outputting?

  • Premiere Pro CS5 and After Effects CS5

    Hi I'm fairly inexperienced when it comes to Adobe products. I was wondering whether Premiere Pro CS5 and After Effects CS5 can be used together, for instance Premiere Pro to do the basic editing and After Effects to do some more advanced stuff before importing the clip back into Premiere Pro for exporting the film.

    Yeah.

  • Premiere Pro CC and the New Mac Pro (2014)

    I'm expecting delivery soon of a new Mac Pro, nicely loaded, which I purchased mainly because of all the work I do with video. Yet, I read in a review that Adobe Premiere Pro isn't optimized to take advantage of the new Mac Pro, won't run faster, and I'm better off using Apple's Final Cut.
    1. Is this true?; and
    2. If so, will Premiere Pro be updated any time soon to run best on a 2014 Mac Pro?
    My new Mac Pro will have the following configuration:
    3.5GHz 6-core with 12MB of L3 cache
    32GB (4x8GB) of 1866MHz DDR3 ECC
    1TB PCIe-based flash storage
    Dual AMD FirePro D700 GPUs with 6GB of GDDR5 VRAM each

    My main problem is that when i export using gpu open gl it crashes hard boot the mac pro. A 3 min timeline with 4k footage n a bunch of color grading.  I get lucky if the timeline is shorter. But i think it is a gpu issue n my mac must be fixed. Currently under apple tech support. N my case is unique. No one has had the same issue and that makes it harder for me to figure the isse and to apple figure the issue.
    If i export using software only mercury then the export goes smoothe no mattrr how long. But that defeata the point of owning a mac pro with 2 GPUs
    Enviado desde mi iPhone
    El 29/03/2014, a las 01:51 p.m., BanksMeador <[email protected]> escribió:
    Re: Premiere Pro CC and the New Mac Pro (2014)
    created by BanksMeador in Premiere Pro - View the full discussion
    I have had my 12 core 2014 Mac Pro for a couple of weeks now, and I'm not very impressed with Premiere CC performance with 4K R3D on a 1920 x 1080 timeline.
    I understand that there may be an update soon that will take adantage of the CPU's and GPU's when it comes to the complex task of de-bayering the R3D footage, but it's just not there now.
    I get similar playback performance to what I experienced on my 09 Mac Pro tower.
    Any insights on getting better playback performance in this scenario would be greatly appreciated.
    Thanks!
    Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/6253414#6253414
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/6253414#6253414
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/6253414#6253414. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Premiere Pro at Adobe Community
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/thread/416458?tstart=0.

  • PREMIERE PRO CS5.5 Gamma problem while exporting project to mjpeg A or B

    Dear Sir,
    I'm in a big ****. I've directed and edited 1h documentary for Finnish television, also, the technical specs requested by the TV Channel is all production Broadcast masters must be encoded with Apple ProRES codec or MJPEG A or B.
    As i'm working on PC (win7), the ProRES codec doesn't exist on PC system, so i've done the export to MJPEG. The problem is i have a different gamma level when i watch the final export with Quicktime or VLC. Of course i can adjust the level in those players, but it doesnt effect the file. When i import the Qt file into a Premiere sequence, the gamma level is still **** and different from my original level i have from my timeline and preview window. If i export the project to H264 1920x1080p25, then the gamma is perfect with Qt, VLC and WinMedia player. But the TV station don't wanna work with H264. Deadline is on next monday, and i can't send a Qt MJPEG file with wrong gamma !!!Any chance to find a solution to fix it ??? After reading different forum, i can see this problem exist since many years and never been solved.
    What can i do ??
    Denis.

    Things is my prpject includ few effect plugins i bought, so what ever i could find a mac, not your i could export xml project to finalcut with plugins it dont have
    Denis
    Sent from my iPad.
    Le 31 mai 2013 à 15:20, Fuzzy Barsik <[email protected]> a écrit :
    Re: PREMIERE PRO CS5.5 Gamma problem while exporting project to mjpeg A or B
    created by Fuzzy Barsik in Premiere Pro - View the full discussion
    If it were me, I wouldn't encode to MJPEG.
    So as to encode to ProRes on Windows you can utilise any solution based on ffmpeg/ffmbc or better yet find a Mac with Final Cut or Compressor installed for delivering critical work.
    Please note that the Adobe Forums do not accept email attachments. If you want to embed a screen image in your message please visit the thread in the forum to embed the image at http://forums.adobe.com/message/5368019#5368019
    Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/5368019#5368019
    To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/5368019#5368019. In the Actions box on the right, click the Stop Email Notifications link.
    Start a new discussion in Premiere Pro by email or at Adobe Community
    For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • I have premiere pro cc and i can't put the speech analysis models spanish for adobe premiere pro cc

    I have Premiere Pro CC and I can't put the Speech Analysis Models Spanish for Adobe Premiere Pro CC, they're installing on the folder CS6 and when I try to analyze it only appears on english... If anybody can help me

    the messsage is for forum housekeeping and is not a message directed to you.

  • Premiere Pro CC and Encore CC are ignoring the Target and Maximum Bitrates

    Adobe Premiere Pro CC and Adobe Encore CC are ignoring the Target and Maximum Bitrates settings in the export window, The files that are exported are much smaller than what the estimated size of the file should be shown in the export window and are highly compressed. What can cause such an issue?
    I haven't drastically changed my presets.

    There is a very definite bug in the Adobe Media Encoder engine which is used in both Premiere Pro and After Effects.  H.264 exports seem to randomly choose their own export quality, using 2-pass VBR.  I have found with some DV-size exports on 'match quality' in Premiere Pro, that setting the export above 10Mbps pushes the quality down to well under 1Mbps, e.g. 167kbps.  I've found that using the default min 6, max 8 seems to work the best.  I've worked with this on two different machines and fiddled with it extensively and this is definitely NOT an intended 'feature'.  In fact, I have found that exporting from the same sequence, if I select the first 20 seconds, I get very low bitrate, but if I select 30 seconds or more, I get the higher bitrate that I want!  And I tend to get different results when I enable and disable 'use previews'.
    I am also having some trouble with missing frames when exporting progressive animation files to h.264 mp4 files that never occured before.  Not sure yet if this is related to the same issue, but interestingly, I don't get the 'blinking' missing frames issue when the bitrate drops itself down to a very low 150-200kbps.  When I do get the export rate up higher, then the missing frames on just this animation clip return.
    So, after my tests, here is a screen capture of sample export settings (yes, 15Mbps is a very high bitrate for DV, but the same happens at 6Mbps or 7 or whatever I try in some cases):
    This gave me a 1.5MB file with a reported 167kbps bitrate and a quality level as shown below:
    A currently working 'workaround' is to use 1-pass VBR which gives me a crisp, clean 5.5MB file.  Would a few others please try to reproduce this so we can get it escalated to bug status?  I'll report it if you can confirm it there, this is happening on two computers here.
    Thanks,
    Sean

  • Hello, i use premiere pro cc and i would like to uplaod my sequence in speedgrade with direct link but it's not available. I can see the option but it's not clickable, somebody knows why ?

    Hello, i use premiere pro cc and i would like to upload my sequence in speedgrade with direct link but it's not available. I can see the option but it's not clickable, somebody knows why ?

    Oh i'm not sure they are on same, i downloaded speedgrade this morning and i didn't upgraded premiere so it's maybe this ! thanks i will try it and let you know

  • We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason. Anyone else got that too with Premiere Pro CC and the new Media encoder? Thanks! bedrijfsfilm Companyfilms

    We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason. Anyone else got that too with Premiere Pro CC and the new Media encoder?

    We have an issue when we send a film to the media encoder it crashes about half of the time for no particular reason
    Anyone else got that too with Premiere Pro CC and the new Media encoder?
    Lack of detailed info makes your question impossible for anyone to answer you!
    eg. ...."Doctor it hurts...anyone else got something that hurts?" 

Maybe you are looking for