Does Premiere CC 2014 use OpenCL acceleration in H.264 encoding or just for rendering?

It doesn't seem to matter what renderer I select, transcoding to H.264 isn't any faster with OpenCL. MainConcept has an H.264 codec that uses OpenCL hardware acceleration - does Premiere CC 2014 for Windows use that codec or not? Does any hardware acceleration apply to transcoding?

Kenneth Badertscher wrote:
It doesn't seem to matter what renderer I select, transcoding to H.264 isn't any faster with OpenCL. MainConcept has an H.264 codec that uses OpenCL hardware acceleration - does Premiere CC 2014 for Windows use that codec or not? Does any hardware acceleration apply to transcoding?
Transcoding is entirely CPU-bound.  It's not something that can easily be parallelized, so there's no win in trying to send it to the GPU.  The GPU can be used in exporting if you've added accelerated effects, or if you scale the video to a different resolution.  Things that can be parallized fairly easily.  Changing from one video format to another isn't one of those things, unfortunately.

Similar Messages

  • Does Premiere Pro 2 use graphics card for playback?

    Does Premiere Pro 2 use graphics card for playback? I am using a 350W PSU, so my nVidia 6600GT runs in low-power mode, and my video playback in Premiere is choppy. The same .avi files play fine in a media player, so it can't be a disc issue I guess... Please advise, thank you!

    Only the latest CS5 uses SELECTED card's GPU for video acceleration
    >same .avi files play fine in a media player
    Playback is not at all the same as editing
    Use the FREE http://www.headbands.com/gspot/ to find out what codec is inside that AVI wrapper
    Anything other than DV AVI type 2 with 48khz sound is not going to do well in Premiere

  • Why does Premiere CC 2014.2 freeze while loading at Loading ExporterQuickTimeHost.prm?

    I can not get Premiere to load.  Is there a solution available?

    I posted this question because Adobe support had control of my computer for the past three days trying to solve this issue, without success.  The last support helper Rameez, had me delete QuickTime and re install which solved the problem.  Maybe this post can help someone else as well.

  • Premiere CC 2014 hangs when sending sequences to Media Encoder CC 2014

      Whenever I try to send a sequence from Premiere Pro CC 2014 to Media Encoder CC 2014, Premiere immediately freezes and becomes unresponsive. AME seems to still be running just fine.
    I've tried the following troubleshooting steps:
    – Clearing the media cache.
    – Clearing and moving the scratch disks.
    – Deleting all render previews and re-building them.
    – Completely re-installing all of Adobe's Creative Cloud suite.
    – Importing the at-question PPCC14 project file into a fresh PPCC14 project and importing only the sequence I need to export.
    – Dragging and dropping the at-question Premiere sequence into AME.
    – Opening only AME and trying to drag the entire Premiere project file from Finder.app into AME's render queue. (This happens to work, as a matter of fact, however something strange happens once the sequence is in the AME queue. It pops up just fine, I can change the render settings and file export location, but when I click the green play button at the top right, nothing happens. AME doesn't hang or freeze up or anything, it's just that nothing happens. No prep, no nothing – very strange.)
    – Uninstalling CUDA completely and tried using only OpenCL and software-only rendering engines.
    – Opening the same at-question project on an entirely different computer.
    – Trying to export from PPCC14 itself.
    – Tried opening up an entirely different PPCC14 project and exporting – worked perfectly. So it must be something with this specific project file.
    I eventually got it working (honestly, I'm not even sure what I did – at that point it felt like I was in a zombie state after four hours of troubleshooting and was just repeating troubleshooting steps because I was trying to hit a deadline with this export.) I was able to export it directly from PPCC14 – I was never able to get it to work with AMECC14, however.
    Other miscellaneous noteworthy things: This project I'm trying to export is massive – it's a feature documentary that's about 2 hours in length. It's very complex in its edits, has a mixture of ProRes 422 files and .MTS files, and the entire project is reading media from three separate USB 3.0 hard drives. I know that's not the ideal workflow, but it's been doing just fine until this last time I tried to render out the latest export for our client.
    Thanks in advance for anyone's help.

    I've tried importing into a new blank project, but that did not seem to work. I then tried selecting the sequence in the bin and exporting that as a "Simplified Project" via the File menu. That still does not work when sending the sequence to AMECC14, but it does work when I render straight from PPCC14.
    I have also found that as long as I give it enough time to load up and all that, I seem to be able to export just fine from PPCC14 itself – I'm still getting the freezing/hanging when trying to send to AMECC14 however.
    Thanks for the help so far Cgunningham – I really appreciate it. I'll keep following up here if I find anything else new out.

  • Does Premiere need to stay open after exporting into media encoder

    After using the Export Media option to get my sequence into the Media Encoder, Premiere was closed accidently. This happened after 9 hrs of rendering and according to the encoder estimate I have 20 more hours to go. Is there a reason to restart if it is still running?

    No. You can close PR while AME is running, no problem, no interference.

  • A signed-in email in a newly unboxed iPhone 5?! Does it mean someone used it?

    I bought a brand new iPhone 5 yesterday and when I unboxed it and opened the App Store it already contained someones email signed in to it! So I had to sign out and type in mine.. Does it mean someone used it before me?! Thanks in advance for any help and feedback!

    Return it and check your new one before you leave the store.

  • Video card GeForce 820m is compatible with CUDA in Premiere CC 2014?

    Hello, I bought an Asus notebook and I wonder if the GeForce 820m graphics card is compatible with CUDA in Premiere CC 2014? Tks.

    Export
    Format: H.264
    Preset: YouTube (make sure this matches the dimensions of your sequence)
    You could further adjust the Target Bitrate but the preset is already setup for a good quality file for upload.
    You can also do further reading on Video Bitrates.

  • Lenovo S8-50LC Wlan(WiFi) Does not work when use Sim Cart(3G)

    Hi
    Tablet Lenovo S8-50LC
    Wlan(WiFi) Does not work when use Sim Cart(3G).
    What is the solution for this problem?
    Build Number : TABS8-50LC_S000200_150121_ROW
    SoftWarw Version : TABS8-50LC_150121

    Right, but if you have the SIM in the tablet and you put the tablet in airplane mode, does wifi work then? If so, it may be a bad SIM. Do you have another SIM you can try?

  • Does turn by turn use your data

    does turn by turn use your data

    Then why do I get dual notifications for Facebook messenger and emails on my phone and iPad Air when I haven't been using them for a while?
    I rarely ever have to reconnect to the Wi-Fi via the lease time thing on my LG G3 or iPad Air.
    My laptop and desktop happens whenever I turn them on. Then I have to renew my lease but as long as they are on and the Wi-Fi isn't freaking out, I can keep it going forever.

  • Premiere CC 2014 does not use CUDA or Processor

    Premiere CC 2014 does not use CUDA or Processor

    In Premiere CC this all ok!
    the CC2014 he does not use or CUDA or the processor.

  • Why does my Premiere CC 2014 crash every time I use "Adobe Dynamic Link" and have After Effects CC 2014 open in the background?

    Here are my MacBook Specs:
    MacBook Pro (15-inch, Mid 2012)
    2.6 GHz Intel Core i7
    16 GB 1600 MHz DDR3
    NVIDIA GeForce GT 650M 1024 MB
    480 GB Solid State SATA Drive
    750 GB SATA Disk
    I use "Adobe Dynamic Link" mainly for typography and some animation, but not to the point where it would stress out Premiere CC 2014.

    Chris,
    It doesn't crash for everyone.  A person could be forgiven for saying, in return, "Please sort out your **** system problems". 
    Trust me when I say many, many problems are caused by the computer system setup not being up to the needs of this cutting-edge graphics software.  Photoshop is heavily dependent on the GPU, and GPU drivers are notorious for having bugs (they're primarily written to run games).
    However, that being said, recent driver releases from both ATI and nVidia do actually work pretty well with Photoshop CC 2014.
    What video card do you have?
    What display driver version are you running?
    If you're unsure how to tell these things, go into Photoshop, choose Help - System Info, copy the data, and post it here.
    -Noel

  • AME takes a long time to start encoding when using GPU Acceleration (OpenCL)

    Have had this issue for a while not (current update as well as at least the previous one).
    I switched to using GPU Hardware Acceleration over Software Only rendering. The speed for the actual encoding on my Mac is much faster that software only rendering. However, more often than not, the encoding process seems to stick at 0% waiting to start for a long time, say anywhere from 1 minute to several minutes. Then it will eventually start.
    Can't seem to find what is causing this. Doesn't seem related to any particular project, codec, output format or anything else I can see. I'd like to keep using GPU Acceleration but it's pointless if it takes 5 times as long to even start as rendering by software-only would. It doesn't even pass any elapsed time while it's hanging or waiting. Says at 0 until it starts. Like I said, once it starts, it's a much faster render than what the software would take. Any suggestions? Thanks.
    using an iMac, 3.4Ghz, 24GB RAM, AMD Radeon HD 6970M 2048 MB

    Actually, I just discovered it doesn't seem to have anything to do with OpenCL. I just put the rendering back to software only and it is doing the same thing. hangs for a long time before it starts to run. Activity monitor shows it running 85-95% CPU, 17 threads and about 615 MB of memory. Activity Monitor doesn't say its not responding, it just seems kind of idle. It took almost 7 minutes for it to start rendering.
    1- Running version 7.2.2.29 of Media Encoder,
    version 7.2.2 (33) of Premiere.
    2- Yes, a premiere project of HD 1080 source shot with Canon 60D, output to H.264 YouTube 720, fps 23.976
    not sure what you are referring to by native rendering. The rendering setting i tried now is Mercury Playback Engine Software Only if that is what you are referring to. But OpenCL gives me the same issue now.
    3- H.264 YouTube 720, 23,976 - seems to happen on multiple output types
    4- In Premiere, I have my project timeline window selected. Command-M, selected the output location I wanted and what output codec, selected submit to Queue. Media Encoder comes up, the project loads and I select the run icon. It preps and shows the encoding process setup in the "Encoding" window, then just sits there with no "Elapsed" time occurring until almost 5-6 minutes later, then it kicks in.

  • Opencl acceleration makes premiere crash

    I was really excited about premiere pro since I installed the evaluation version a few days ago, but today I'm just disappointed in Adobe and here is why.
    This week-end, I switched to mercury openCL accelerated rendering, only to find out that premiere would crash without any error message as soon as some video or picture is to be displayed. After hours of searching websites and forums for a solution, uninstalling and reinstalling my amd graphics driver, I finally tried to contact a adobe premiere expert by chat. The guy answered me right away: no chat or phone support for evaluation versions.
    I can understand the decision not to spend work effort on non-paying maybe customers, but the more I think about it, the more it makes me wonder if Adobe really understands what an evaluation software is all about... namely convincing people to buy their stuff:
    I, the customer, find a neat piece of software, start evaluating it in order to decide whether or not it is worth my money. Starting to understand how it works, I try to get the most performance out of it, switch a setting and find out that the product actually is quite unstable on my setup (which is far from being exotic). My positive feeling about the product starts to wobble, but since I am quite convinced I don't put it away without searching for a solution. Used to get my hands dirty when computer issues arise, I put a few hours of effort into finding a workaround. Without success. Taking a closer look at Adobes support service, my positive impression is back: I can contact a premiere expert by chat.
    And here it comes, counterproductive and just so... let's say it, stupid: Unfortunately, we don't provide chat or phone support to evaluation version users.
    Come on, that can't be serious? I'm evaluating this software, and they make me understand: oh, it does not work? well, buy it, and then maybe we will make it work for you!
    I love software business... It tries to make people accept the unacceptable. Imagine looking for a sports car. You find a very nice one which has a city mode which limits the engine to 50HP, and a much more exciting sports mode which unleashes all the 450HP it packs. They let you take a ride, you fall in love with the car, think about buying it for real. You want of course to know exactly what you're buying. Unfortunately, when switching from city mode to sports mode, the engine stops. Ok, bad impression... but you like the car and give them a second chance: you ask the dealer to check it out, so that you can try the other mode. How would you react to the dealer answering you: No, if you want to see what it's like, you must buy it first.
    What the hell?! Who would not just walk away?
    And here, I am supposed to pay for a piece of software that does not run properly on my PC?
    How ... disappointing!

    Hello Vinay,
    Thank you for your answer.
    I updated my version of permiere to 7.2.2 (33) today, unfortunately it still crashes as soon as opencl acceleration is activated.
    My operating system is windows 8.1
    I have 2 amd graphic cards in my rig:
    R9 280x
    HD5870
    When I select mercury opencl, premiere crashes as soon as anything has to be displayed. It is independent of the type of material (pictures or videos) I browse in the media explorer and display in the source window. It crashes also as soon as I play the timeline, whether there are effects or not.
    The videos and pictures I'm processing are all taken with a gopro hero3 and a galaxy note 3.
    Regards,
    Severin

  • After I purchased the creative cloud, I receive an error message when trying to use premier pro cc 2014.  It states "Adobe Premiere Pro 2014.2 has stopped working.  A problem has caused it to stop working.  Windows will close the program and notify you of

    After I purchased the creative cloud, I receive an error message when trying to use premier pro cc 2014.  It states "Adobe Premiere Pro 2014.2 has stopped working.  A problem has caused it to stop working.  Windows will close the program and notify you of a solution."  When I used the trial I never received this message.  Now after purchasing it I receive this error each time I open PP and am unable to use. it.  Any ideas or support to fix this issue?

    What does the detailed crash report say?
    And have you updated your video card drivers from the GPU maker's website? (most crashes on launch are due to bugs in out of date video card drivers)

  • Updated to Premiere CC 2014 and AE CC 2014 and now have blue lines/blue imprints of windows and crashes after 5 minutes of use or on start up

    iMac - 27 ", late 2012
    Processor  3.4 GHz Intel Core i7
    Memory  32 GB 1600 MHz DDR3
    Graphics  NVIDIA GeForce GTX 680MX 2048 MB
    Software  OS X 10.9.4 (13E28)
    After I updated from CS6 to CC 2014, my screen started to display blue lines and/or a blue imprint of a previously closed window, and Premiere CC 2014 and AE CC 2014 began crashing after about five minutes of use. Also, an error message popped up telling me to update my CUDA driver. I took the iMac into Apple and after updating the CUDA driver in store with an Apple associate, the error message went away. They were concerned about the blue lines, and after 3 days of hardware testing, they determined that the screen was not failing, the hardware was in great shape and the lines and crashing must be a software related issue. I took the computer home, uninstalled and reinstalled AE using the appropriate installer, and rebooted. Then I uninstalled and reinstalled Premiere using the Premiere installer and rebooted again. During the second restart a blue imprint of the Google Chrome window I had had open before the reboot was imprinted over the welcome/password screen. I typed in my password, opened up the Premiere project I'd been working on and immediately, the always dramatic message "A serious issue as occurred..." popped up. I tried opening it again, saved a new recovery copy and started to work on the project. Five minute later it froze up and I had to force quit. This happened two more times, both roughly after five minutes of use....back to square one.
    Obviously, this is seriously hurting my workflow. Any advice you could give would be greatly appreciated!

    ... a blue imprint of the Google Chrome window I had had open before the reboot was imprinted over the welcome/password screen.
    The apple guys said this wasn't a hardware error? I don't know software errors to save imprints throughout a restart. If I were to live dangerously and assume anything it would be that you got a failing graphics processor.
    Ever tried cloning your boot drive and then doing a complete wipe and re-install of OS and CC?

Maybe you are looking for