Mercury Engine GPU bug/error/problem

Hi there
Im experiencing a very strange phenomenon with the Mercury Engine in hardware mode. I recently upgraded my computer so I am running on new hardware. I ran Production Premium on my laptop and my older desktop, both working without problems.
My new configuration is a 2600k i7, 16gig Ram, GTX 570. The problem will be best described with screenshots:
The top image was taken in software mode. This is the correct result, displaying like it does on my laptop and old pc. The bottom pic shows the same frame in GPU acceleration mode.
1. It looks like the Title texts' edge is shrunk by a pixel or so.
2. The layer below the text, the strap, is an animated AE composition. It contains a drop shadow at 50%. In hardware mode it looks like its about 20%
3. I have a 2 pixel 40% opacity black stroke applied to the strap. In hardware mode its almost completely invisible. I think the outline is shrunk as well.
To make it even wierder, if I click on the Title layer in the preview window in Premiere, ie, if I select it, it suddenly displays correctly. When I deselect it, its wrong. If I open the title editor, the text displays correctly. When I close the title editor, its wrong again in the playback window. The straps all display correctly when I work on them in AE.
This is forcing me to switch to software mode before I render, otherwise the rendered result is faulty. I'm 99% sure its a CUDA thing.
Im running the latest nvidia drivers. Any ideas?

Actually this is how hardware mode works. I know it's wierd but its due to what is called "Linear color/ light processing" Basically it will cause the issue your seeing. Hardware mode handles video this way. Currently you can't do anything about it, sadly. I always just have to make things darker to compensate. The reason it looks correct in titler is because the titler displays the still in software mode, or at least this is what I have noticed so I assumed this a long time ago.
Basically though if you export your video in software mode then check max render quality when you export it cause the same issue that having MPE+GPU enabled does.  That's because enabling max render quality causes even software mode to use 32-bit linear color processing. So most likely I think this is what is causing the issue you're seeing. You can verify it, by setting your sequence to software mode. Then exporting and checking max render quality when you export, then looking at the end result and you'll see the opacity differences.
You can check out this thread for more in depth info.
http://forums.adobe.com/thread/773441

Similar Messages

  • 59.94iシーケンスで.Mercury EngineがGPUモードだと.SDI出力が29.97Pになってしまう.

    現在、Decklink SDIとPremiere CS6の組み合わせのテストをしているのですが、
    Mercury EngineがGPUモードの場合、
    SDIから出力される信号は1080iなのですが、どうも偶数フィールドが表示されていないようなのです。
    テストのため、四角が素早くスライドする検証用の動画(1080i 29.97(奇数優先)のProresHQ)を作って再生させたところ、
    明らかにガクついて30Pっぽい動きをします。
    FinalCut7やFinalCutXでDecklink SDI経由で出した場合は、滑らかな動画が表示されます。
    そこで、MercuryEngineをSoftwareモードにすると、FCP7やFCPXのように滑らかに再生されます。（レンダリング後ですが。。。）
    これでモニタリングすれば良いのですが、これではGPUの意味がなくFCP7程度レンダリングに時間がかかってしまいます。。。
    これは、環境による問題なのでしょうか？
    それとも、Mercury EngineがGPUモードの場合、59.94iでの外部モニター出力はPremireCS6ではできないのでしょうか？
    環境は以下のようになっています。
    よろしくお願いします。
    macpro 10.8.1
    premiere cs6.0.2
    blackmagic driver 9.6.4
    GTX285
    premiereでのシーケンス設定
    シーケンスプリセット/blackmagic/8bit YUV/interlace/59.94i

  • Issues with Mercury Engine GPU acceleration and stills

    Hi folks, recently made the switch to CS6 Creative Cloud and for the most part I am loving Premiere Pro CS6 except I am having one major issue. I've got a early 2011 Macbook Pro with the 1GB AMD Radeon HD 6750M video card and 16GB of RAM and I am using Lion 10.7.4. Mercury Engine GPU mode works great on this machine (fast timeline renders, accelerated effects, quick exports) except whenever I try to use a still image on the timeline. It doesn't matter if it's a JPG, TIFF, PSD, or anything else. It also doens't matter what the size of the image is either. As soon as I drop a still on the timeline the responsiveness of the entire program starts to grind to a halt. Parts of the timeline that were playing back soomthly (in GPU or software mode) now can barely play at 10-15 fps.
    I don't have this issue in Software Mercury Playback mode (I just loose all the benefits of the GPU acceleration).
    If I switch back to Software Mode, delete the previews and restart Premiere things go back to working well in software mode.
    I'm working on projects with Canon DSLR footage (1080P 30fps) and I am working off of a fast RAID 0 hard drive set-up.
    If anyone has any advice on how I can actually use the amazing GPU mode I would be most grateful.
    thanks
    Daniel

    >doens't matter what the size of the image is either
    Well... exactly what pixel sizes have you tried?
    Photo Scaling for Video http://forums.adobe.com/thread/450798
    -Too Large May = Crash http://forums.adobe.com/thread/879967
    -And another crash report http://forums.adobe.com/thread/973935

  • SOAP adapter engine with system error, problem with fault message.

    HI,
    I have IDOC -> PI -> SOAP scenario.
    Idoc to PI is async. I have no problem in receiving the idoc in PI. The message mapping is carried out and sent to the adapter engine. I can also see the technical routing payload. It is sucessful at XML monitoring in SXMB_MONI.
    The error is at PI -> SOAP.
    I have wsdl provided by the receiver webservice. Which I have imported.
    And created a service interface against this wsdl. I tried changing it to both sync and async.
    I have also provided fault message.
    I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap
    action = processDocument. Also provided user id and password.
    I have a
    Sender Agreement
    Receiver determination
    Interface determination
    Receiver Agreement
    I check in RWB adapter engine, this message goes to system error. The error log is as shown at the bottom.
    When I see the message content, the SOap document shows me the details about IDOC, Instead I feel it should match
    with the wsdl, where they have specified the corresponding interface name and address location etc.Please correct me.
    How does the receiver know which service interface is it? The Service Interface which I created in the ER is
    different from the WSDL, Does this have to be same? I see that the soap document in the adapter engine has the
    Service interface name which I created in the  ER. Where in the document the Reciever interface name is sent?
    Where can I see the generated soap document for the receiver?
    Is there some setting/configuration required in PI for this to work?
    I tried using the tcpgw to see the error. If I dont provide the service interface name in the communication channel
    then I get the following error in the TCPGW. "The service cannot be found for the endpoint reference"
    When I provide the service interface name in the communication channel I get a valid fault message.
    Similarly
    When I use SOAPUI, I can see the fault exception being return. The adapter engine doesnot show an equivalent message
    instead it goes into system error as shown at the bottom. I guess this is expected, if so what is the work around? (I found this weblog /people/alessandro.guarneri/blog/2011/01/10/soap-fault-in-sap-pi-hijack-it, do I need to implement this? Or use ALEAUD?
    The fault message what I see in SOAPUI has the below format.
    <soapenv:Fault xmlns:axis2ns1="http://schemas.xmlsoap.org/soap/envelope/">
             <faultcode>axis2ns1:Server</faultcode>
             <faultstring>nested exception is: psdi.util.MXApplicationException: BMXAA7136E - Validation failed when the
                                database default values were set. See the associated message for more information.
               BMXAA4190E - Country NZ is not in the value list.</faultstring>
             <detail>
                <Exception>org.apache.axis2.AxisFault: nested exception is: psdi.util.MXApplicationException: BMXAA7136E
                          - Validation failed when the database default values were set. See the associated message for more information.
         BMXAA4190E - Country NZ is not in the value list.
                /Exception>
             </detail>
      </soapenv:Fault>
    And the fault message in my ER service interface is stanadard datatype ExchangeFaultData, which is different from
    the above. Is this the problem? Can I change the data type here to be the same as above?
    Audit log in the RWB adapter engine.
    Time Stamp Type Description
    30.09.2011 15:10:57 Information MP: processing local module Localejbs/sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
    30.09.2011 15:10:57 Information SOAP: request message entering the adapter with user J2EE_GUEST
    30.09.2011 15:10:57 Information SOAP: completed the processing
    30.09.2011 15:10:57 Information SOAP: sending a delivery error ack ...
    30.09.2011 15:10:57 Information SOAP: sent a delivery error ack
    30.09.2011 15:10:57 Error MP: exception caught with cause
    com.sap.engine.interfaces.messaging.api.exception.MessagingException
    30.09.2011 15:10:57 Error Adapter Framework caught exception: null
    30.09.2011 15:10:57 Error Delivering the message to the application using connection
    SOAP_http://sap.com/xi/XI/System failed, due to:
    com.sap.engine.interfaces.messaging.api.exception.MessagingException.
    30.09.2011 15:10:57 Information The message status was set to WAIT.
    30.09.2011 15:10:57 Information The asynchronous message was successfully scheduled to be delivered at Fri Sep 30
    15:15:57 NZDT 2011.

    I tried changing it to both sync and async.
    I have also provided fault message.
    dont feel that you need to do above steps.
    I have a
    Sender Agreement
    ideally you dont need a sender agreement (and a channel) for IDOC --> PI flow.
    When I see the message content, the SOap document shows me the details about IDOC
    this is fine...you may see fields as seen in EDI_DC40 of the IDOC...
    How does the receiver know which service interface is it?
    receiver need not know about the SI created in PI.
    The Service Interface which I created in the ER is
    different from the WSDL, Does this have to be same?
    you should the WSDL (external definition) as the Request Message in your service interface.
    Is there some setting/configuration required in PI for this to work?
    nothing specific...AFAIK
    I have set a receiver soap communication channel and provided the target URL like "http://xxx/services" and soap action
    can you open the URL from Internet explorer...from your machine or from the machine which is in the same network as your PI server?
    Things to check:
    WSDL structure in PI and in target system is exactly the same.
    does the target system require mesage in SOAP format (SOAP envelope - SOAP Header + SOAP body)?
    target system is up and running?

  • One solution to AME stops encoding using Mercury Engine with an "Unknown Error" - Mac only

    I recently switched from FCS to CS5.5 - it's been a somewhat rough ride - and I kept getting an "Unknown Error" if I tried to export a sequence while having the mercury engine gpu-enabled.
    After finishing my latest project just three days ago I found a solution, go figure. Well, here it is: the offender were imported dissolves from FCP. They play perfectly in PPro, they render perfectly in software mode, but never once while using the GPU. The solution to that is equally simple: deleting the offending dissolves and create a new dissolve, same length, same effect name, nothing's changed. But now, they render just beautifully using Mercury Engine in GPU mode.
    If somebody likes to look into that, I created a small project for re-checking.

    Sure, no problem. Where would you like me to put it? Including the sources, its about 50MB (I replaced to original footage with low-res, low-datarate stuff). Or do you only need the project file?

  • Error compiling movie: unknown error & Mercury Playback GPU acceleration

    Hardware
    2014 Mac Pro, 12GB RAM, 3.7 GHz Quad-Core Intel Xenon ES Processor, duel AMD FirePro D300 2048 MB graphics cards
    Software
    Mavericks (10.9.4)
    Premiere Pro CC2014 (8.0.1)
    I'm attempting to render out a moderately complex sequence. Raw footage was dslr h.264 MOV files. 30fps 1920x1080 from canon. It has some clips that are pulled from multi-cam sequences and a few that have warp stabilizer applied. 4 total audio tracks with some linked comps from audition. Whole thing is about 14 minutes. It should be noted that I render out similar sequences regularly without issue. However on this occasion whenever I tried to render out using media encoder ( for web h.264 MOV 720 30fps) I was getting an error at the same clip every time. Error Compiling Movie: Unknown Error. So I checked out the clip. It was one of the ones with warp stabilize. I turned that off and sent it out again. Render got further this time but hit a different clip with warp stabilize (after getting through like 2 other clips with warp stabilize enabled) and gave me the same error. I tried getting rid of cache files, saving to a local drive instead of a network drive, uninstalling and re-installing premiere even. (which btw if you check remove preferences then reinstall it def still has preferences so that's a total load.) Anyway I was doing some forum surfing and found several people going all the way back to PP 5.5 saying that the only solution they found was to turn off the Mercury Playback GPU acceleration. Tried that and it's currently rendering just fine but taking roughly 4X longer than with acceleration. The GPU acceleration is a big deal for me since our company relies on putting out a lot of volume quickly. Has anyone else experienced this problem and is it something you were able to fix without turning off GPU acceleration. Grateful for your input.

    sorry I actually wrote that wrong. I am using the H.264 setting 720 30fps to create a web friendly .mp4. Alternately though I decided to watch and see if it was the same clip failing every time. It is. I went into the project and did a match frame for the offending clip. Dragged the a new version of the same content onto the timeline and copied the warp stabilize effect onto the new version. Well this time the encode got past the clip with the issue, however the next clip it hit with warp stabilize caused another error compiling movie: unknown error. I guess at this point my options are to turn off the GPU acceleration and wait for a render that takes more than 3x as long to render with software only, or to go through the whole timeline and replace the clips with warp stabilize (there are a bunch, the shooter wasn't having a great day on glidecam). Not a great solution on either end. Please let me know if I should file this as a bug report. Though it seems people have been having the same issues since version CS5.5

  • About Mercury Engine in a Dell Notebook (ATI HD 7730M GPU)

    Hey, guys!
    (sorry anticipately about any language errors, I'm from Brazil and try my best to say things correctly in english)
    I was about to buy a new Dell notebook, the Inspiron 15r SE, that has a really great config (for my use) and comes with this ATI Radeon HD 7730M GPU.
    One friend advised me to don't do this, because it lacks the GPU Mercury Engine ability.
    With some research, I found that the OpenCL (ATI's equivalent to GeForce's CUDA) isn't really ready to work with CS6 GPU Mercury Engine on any PC.
    So, what you guys think? Is it really the best choice, to don't buy this Inspiron because of the lack of GPU MPE or it won't change performance that much?
    Additional info:
    1. This Inspiron 15r SE config is the following:
    - i7-3612QM
    - 8GB RAM (1600 Mhz)
    - ATI Radeon HD 7730M (2GB)
    - 1TB HDD + 32GB mSATA SSD Cache
    - 15,6" screen (1920x1080)
    2. I will use only CS6, not CS5.X
    So, hope you guys could help me.
    If this problem isn't that bad, I'm gonna buy this Inspiron, 'cause the price is really good (to brazilian standards :/).
    Thanks!

    Hey, Dave, thanks for the reply!
    First: About lap/desktops, I know these things. I do have one desktop too, but as I travel every weekend I like to keep one laptop with me, you know?
    Second: I did check the cards list, but they're all too expensive, or desktop, or so.
    Now: My use is balanced with Photoshop, Illustrator and After Effects. I don't use Premiere that much, although sometimes I edit some stuff. Anyways, nothing intense like multiple RED footage or so. So, about the occasional use of Premiere: The CUDAs would make it insanely better to work in comparison to this ATI card?
    Let's take, for comparison, my actual laptop: LG a520 (i7-2630QM, 6GB RAM, 640HDD, GeForce GT 540M 2GB- wich has CUDA but is not on the officially supported list, or is to weak, I Don't know).
    My use won't get worse, right? In fact, with PS, AI and AE it will be better, I think.
    In the end: I just wanna know if I'm gonna do a bad deal buying this Dell, because, specifically, of its GPU.
    (Last thing: About the RAM, this Dell is expeansible up to 16GB. So, if it's the case, in the future, I get some more RAM. Thanks, anyway)

  • Mercury Playback Engine GPU not available

    I've been reading through forum postings and have not found a solution, so I apologize if there is a solution posted elsewhere.
    I have a 27" iMac (late 2012) with NVIDIA GeForce GTX 680MX graphics card running Mac OS 10.8.5.
    I'm using Adobe Premiere Pro CS6.0.3, and when I updated my OS to 10.9 Maverick, I began to experience several problems, including:
    The dreaded spinning beachball and "Premiere not responding."
    "This project was last used with Mercury Playback Engine GPU Acceleration (CUDA) which is not available on your system. Mercury Playback Engine Software Only will be used.
    Video files - I think they were all .MOV - became "squished" to the top of the Program Monitor (movie only took up about 1/3 of program monitor window).
    After a long chat with Adobe Support, he indicated that the update to 10.9 Maverick was the problem, so I:
    Updated to Premiere 6.0.5, but that did not fix any of the issues.
    Logged in as "Root," which worked for a while but I also received 3 "Premiere encountered problem and must shut down."
    Deleted preferences, repaired permissions, basic troubleshooting practices, etc, but problems persisted.
    No help.
    Eventually I restored my computer from a Time Machine backup to a day prior to the OS 10.9 update, and this seemed to fix all the issues. So I was back to Mac 10.8.5 and Premiere 6.0.3.
    But the .MOV-compressed-in-the-program-monitor problem began to surface again (see  photo below).
    So I updated to Premiere to 6.0.5 (but not my OS - it's still 10.8.5), and the "Mercury Playback Engine" error is back.
    And the .MOV files are still compressed in the Program Monitor. I have a project that I completed in 6.0.3, but is now messed up in 6.0.5.
    Help please. Is the only solution downgrading to Premiere 6.0.3, and if so, must I do a clean install of the program from the DVD?
    Thanks,
    RW Harris, Director of Training
    Express Oil Change & Tire Engineers
    Birmingham, AL

    harris1966 wrote:
    Thanks so much for your quick responses.
    @Kevin, the strange thing is this: Express purchased this iMac and the Adobe Creative Suite back in January of this year, and the computer and software have worked flawlessly since that time.
    It was only after upgrading, first to Mac OS 10.9 Mavericks (which I later downgraded back to 10.8.5), and then to Premiere 6.0.5, that I began experiencing problems.
    Prior to these upgrades, I never received the "Missing Renderer" message, nor did I experience any lagging problems or problems relating to .MOVs in the Program Viewer.
    Hi Randy,
    I'm sorry. I really don't know the answer to your question, or how that happened. All I know is that the card is not supported for CS6. I guess we have a mystery on our hands.
    harris1966 wrote:
    Any insight on why I never experienced problems until upgrading software?
    Sorry, it is behaving as if your text file was hacked prior to you receiving the computer. After you updated the OS, a new text file without your card was created. Your card would not be listed in that file because it is not supported.
    harris1966 wrote:
    Are you saying that PP doesn't support NVIDIA 680 MX cards "now that the software is at 6.05"? Or PP doesn't support that card at all, under any software version?
    The card is supported for Premiere Pro CC, but not prior to that.
    harris1966 wrote:
    Again, thanks so much for your help.
    You're welcome!
    Thanks,
    Kevin

  • How can I open a project that has been created with Mercury Playback Engine GPU Acceleration software, on my trial version of Premier Pro CC?

    Hi,
    I'm working with a colleague who is using Mercury Playback Engine GPU Acceleration software on his PC version of Premier Pro CC. I am using a mac and have a trial version of Premier Pro CC. When I try to open a project file that he has sent me I get an error message-
    "Missing renderer: This project was last used with Mercury Playback Engine GPU Acceleration (CUDA), which is either not available or not certified on this system. Mercury Playback Engine Software Only will be used."
    When I click OK and locate the files I get a message saying "File format not supported".
    Can anyone tell me what to do so that we can share project files?
    Many thanks,
    Jessie

    Shouldn't really be the MPE at fault here ... what is the codec of the footage/sequence/project?
    Second, can you create a new project in PrPro, then in the media browser, import that sequence from the other project?

  • IMAC's Top graphics card frustration - Cheap and no support for Adobe Mercury Playpack Engine GPU Acceleration?

    If anyone has a solution for getting the Mecury Playpack Engine GPU acceleration to work with Premiere Pro CS6 on an iMAC 2011, please let me know. Like I wonder if you could Thunderbolt an External graphics card somehow? Or is an upgrade possible? Ahh...not worth the risk.
    Please, if you have a solution for me, let me know. Otherwise I find it pretty frustrating that I purchased a top-end iMAC, fully maxed-out in every way possible, and that the iMac doesn't support Adobe Premiere's Mercury Playback Engine GPU acceleration. Also, an old USB 2.0 Hub and thus the built-in SD card reader is slow. If you have SD cards with 95MB/s Transfer, Read and Write speeds, the iMAC will only transfer at around 30MB/s if you're lucky. Technically 480Mbs which is around 50MB/s but I haven't seen those speeds.
    I figured this could at least be circumvented with a Thunderbolt SD card reader or a Thunderbolt to USB 3.0 adapter but of course no such thing exists.
    Well, nothing with a reasonable price tag. This all might seem trivial to some but when you're uploading 24 hours of HD video footage from a 128GB SDXC card, the speed makes a big difference.
    And come on, no BluRay support? Ridiculous. I get the politics of why but still, just ridiculous. It would be nice to be able to burn a BluRay to watch in my home theater system. There are other methods but BluRay is convenient and great for backing up large Video Files. Unfortunately BluRay looks like it's not going to make it.  Maybe cable distribution companies will increase their Internet upload speeds one day and I can just store everything in the cloud and watch full length movies(that I've created) on Vimeo.
    Anyways, I went and took a look at the hardware Apple stuffed inside my fancy (3.4 Ghz i7, 16GB 1333 DDR3, 2GB AMD 6970M, 256 GB SSD Internal and 2TB 7200 Internal) machine and it appears to be pretty middle of the range stuff. It's an iMAC, not a Mac Pro so why am I griping? Because my 2009 PC(which I tricked out over the last two years) is faster and does support the Mercury Playback Engine. I spent $2100 total on this PC which includes all my upgrades. I spent around $3300 on the iMAC. I feel ripped off.
    Yes, I do love my iMAC on multiple levels but had I known my dated 2009 PC would render video projects faster, I would have gone with a MAC Pro or just a new PC. It seems that Mac is moving completely away from making high-end computers for niche markets(video editing) and focusing on their tiny laptops, IPADS and IPhones for the masses. Obviously smart from a capitalistic perspective(at present at least) but very frustrating for some.
    I was actually told to purchase a MAC for video editing. I've been a PC guy for 15 years. I went with the iMAC because I had read many good things about it(probably just Apple propaganda)  and also the MAC PRO was to be discontinued. Also the MAC Pro would have been triple the cost for what didn't seem like a whole lot more.
    It's one's thing to prepackage a computer with inferior hardware(the iMAC I have is fast for most things and more than enough for 99% of the population) but to not allow us to pop open the computer and make a quit upgrade to the machine is what really makes me feel like I'm using a computer built for Grannies. I mean there is a reason my mother loves iMacs and Iphones. Amazing that I was able to upgrade my memory from 4 to 16GB  but I've heard Apple has even done away with that. I get why they do it. Apple Warranty, Apple Care issues, Profit and World Domination: Apple wants a monopoly on everything.
    Was great to see Adobe bounce back after the whole Flash/HTML5 thing and knock Final Cut Pro off the face of the Earth for good. People are still buying it b/c of the brand name but Final Cut is done. David Fincher used Adobe's Workflow for everything when he made The Girl with The Dragon Tattoo. Hollywood is making the shift and the world will follow. The Adobe Workflow has finally come together and there is just no way Apple can compete with Adobe Creative Cloud and an Engine that can just swap from Premiere to After Effects to Prelude to SpeedGrade to Photoshop to Story with speed for $29 bucks a month(or $49 for some). Apple better start supporting Adobe's Mercury Engine or they may have a problem. And if you're using Final Cut X, you're severely handicapping yourself. Problem is that people don't want to take the time to learn Adobe's products(steep learning curve for sure) which is where Apple's Granny software, and perhaps computers, comes in to play. Arnold Schwarzenegger once said "Milk is for babies, Real Men Drink Beer".  I'm beginning to think that "Mac's are for Grannies, Real Men Use Adobe and PCs".
    The major problem with Apple is you're forced to use Apple. Not sure but history has proven that people don't like to be forced into anything. Autocracies don't work. These systems eventually topple, even in the corporate world.
    Amazon.com, now that's the company to emulate. What an amazing machine!
    I've read that Apple may even discontinue the iMAC after 2013. Who knows?
    If anyone has a solution for getting the Mecury Playpack Engine GPU acceleration to work with Premiere Pro CS6 on an iMAC 2011, please let me know. Like I wonder if you could Thunderbolt an External graphics card somehow? Or is an upgrade possible? Ahh...not worth the risk.
    1) Graphcis Card  - AMD Radeon HD 6970M 2048 MB (6990 would have been better or something from NVIDIA.
    2) USB 2.0 Hub with only 480 Mb/sec
    3) Seagate Baracude SATA I 7200 RPM drive with 3GB/s transfer rate and only a 32 GB Cach. It's ok. I would have expected at least a Western Digital Caviar Black 2 TB SATA III 7200 RPM 64 MB  or the Velociraptor at 10,000RPM.
    4)APPLE SSD TS256C  Flash Drive. As you can see, it doesn't stack up so well against other SSD Drive.
    Just average. http://www.harddrivebenchmark.net/hdd_lookup.phphdd=APPLE+SSD+TS256C

    Whining and ranting about how iMacs can't do this or iMacs/orMacs can't do that is not going to get you a lot of help here.
    Your "I love my MAC" is typical of the ever ubiquitous PC whiner.
    If your video work needs were that computer intensive and critical , you should've done some online research and you should have budgeted for a Mac Pro.
    Mac Pros are completely expandable and upgradeable unlike the iMac.
    Mac Pros have much more faster and more CPU cores than the iMac line.
    iMac line is limited to CPUs with 8 cores. The Mac Pros, I believe, are up to 16 core CPUs, now.
    The Mac Pros can have their GPU upgraded and you even add/expand to use specialty audio/video cards.
    Mac Pros are the defacto standard for real video work.
    iMacs, even the high end model, is not really designed to do really heavy and intensive video work.
    iMacs do do video creation and editing. Just not on the level that is needed from a more "Pro" computer.
    It seems to me you are asking your iMac to do more than it was originally designed for, in terms of professional video editing.
    You get a lot more out of a Mac Pro than an iMac for any real serious video, CGI or animation work.
    You just didn't want to spend that much cash on one.
    iMacs are not user upgradeable or friendly to user upgrades at all!!!
    If you purchased a Mac Pro, you could've had that better, faster HD, better faster SSDs.
    That said, I can offer no real help to but because of the nature of your post and the fact you just simply annoyed me, I feel some advice and explanations are in order
    First off, you picked Adobe video editing software suite as your video creation software on the Mac.  It's no secret to long-time video content creators on the Mac that Adobe products, especially those for video creation and editing are very user unfriendly on the Mac. Even though Macs are supported from Adobe, Adobe for a long time has treated the Mac and Mac users as second class citizens.
    Before purchasing and installing Adobe Premiere, did you even check Adobe's site for the preferred system hardware and software requirements? Hmmm?
    This is why you should KNOW what software you are going to be running on a computer first then research what computer make and model will run said software.
    That's why Apple has its own apps like Aoerture, Logic and Final Cut.
    Despite your ignorance in this matter, Final Cut Pro X is alive and doing well, thank you, and using this software on your iMac would kick Adobe Premier in the you know whats.
    Final Cut Pro X is a complete video solution for and completely designed around the Mac.
    Why are you using USB 2.0 connections for video work when you have a perfectly good FireWire 800 connection.
    In case you are not aware, FireWire 800 is called so because it has a max throughput of 800 Mbps.
    Your 2011 iMac can take up to 32 GBs of RAM. Not just 16 GBs.
    This changed when the 2010 model iMacs came out.
    Blu-ray? I believe you can buy external Blu-ray writers that work with Mac using said FW800 connection.
    So you cite one movie and one videographer using Adobe Premier for your premise that Final Cut is dead in Hollywood?
    Your argument that Apple locks you into everything in their world can be countered by saying Windows and Windows PCs lock you into the Windows world. What's your point?
    Apple is not discontinuing their computers platforms any time soon.
    All you are regurgitating is rumor. Probably from all of the PC crowd.
    iMacs and professional desktop Macs are not going anywhere.
    Currently, Apple is the only desktop/laptop computer maker that is still making a profit on their Macs and increasing their market share percentages for the last 5 years during which the PC market has continually slumped/dropped in its market share.

  • Premiere CC 2014: Message on loading project from older version: This project was last used with Mercury Playback Engine GPU acceleration (CUDA)...

    After installing Adobe CC 2014 I have each time a message when loading an old Adobe pro project. Message:This project was last used with Mercury Playback Engine GPU acceleration (CUDA), which is either not available or not certified on this system. Mercury Playback software will be used. I have very recent HP Zbook 15 with a NVIDIA Quadro K2100M. At webinar today it was explained how to solve this, but sound was not understandable at my machine at that moment. Help? What need I to do.

    Problem is solved since yesterday via Adobe helpdesk. It appeared that the newest driver for the NVIDIA were note present. So after downloading the new drivers it work. But I think Adobe should mention those issues when they launch new versions of Adobe CC like in June.

  • Adobe Premiere Pro CC crush - no Mercury Playback Engine GPU acceleration (OPEN CL)

    I was an happy customer of Adobe CC till few days ago.
    It were a few weeks I did not update the software in CC due to a problem with connection.
    Needed to use Premiere Pro CC. It always crushes my MacBook Pro retina 2012 (16 giga ram) during export of the video. The monitor became black and there was no way to restart.
    The Macbook worked smoothly with all the other softwares. Deleted CC and reinstalled everything, which was quit painful. However, at the end of the day, Premiere Pro CC works but I cannot use Mercury Playback Engine GPU Acceleration (open CL) which I used all the times before with huge advantage (exporting a 1 minute video in good quality needed 2 minutes with GPU accelerator, 20 minutes without).
    When I open old project of Premiere Pro cc I read this message "this project was last used with Mercury Playback Engine GPU acceleration (OPEN CL), which is either not available or not certified on this system. Mercury Playback Engine software only will be used". There is no way to change the rendered from Project setting - Mercury Playback Engine software is the only option.  
    My question: is it a problem with Adobe Premiere Pro CC or with my graphic?

    Ask in the Premiere forum.
    Mylenium

  • Mercury Playback Engine GPU Acceleration

    I was an happy customer of Adobe CC till few days ago.
    It were a few weeks I did not update the software in CC due to a problem with connection.
    Needed to use Premiere Pro CC. It always crushes my MacBook Pro retina 2012 (16 giga ram) during export of the video. The monitor became black and there was no way to restart.
    The Macbook worked smoothly with all the other softwares. Deleted CC and reinstalled everything, which was quit painful. However, at the end of the day, Premiere Pro CC works but I cannot use Mercury Playback Engine GPU Acceleration (open CL) which I used all the times before with huge advantage (exporting a 1 minute video in good quality needed 2 minutes with GPU accelerator, 20 minutes without).
    When I open old projects of Premiere Pro cc I read this message "this project was last used with Mercury Playback Engine GPU acceleration (OPEN CL), which is either not available or not certified on this system. Mercury Playback Engine software only will be used". There is no way to change the rendered from Project setting - Mercury Playback Engine software is the only option. 
    My question: is it a problem with Adobe Premiere Pro CC or with my graphic? How to fix if is due to the software.
    thanks

    giacomonovara wrote:
    --- GPU Computation Info ---
    Did not find any devices that support GPU computation.
    Any idea of the meaning?
    It means your nVidia GPU isn't active.  Either it's toast, or OS X has turned it off for some reason.  My laptop is nearly identical to yours, and this is what my output is:
    # /Applications/Adobe\ Premiere\ Pro\ CC/Adobe\ Premiere\ Pro\ CC.app/Contents/GPUSniffer.app/Contents/MacOS/GPUSniffer
    --- OpenGL Info ---
    Vendor: Intel Inc.
    Renderer: Intel HD Graphics 4000 OpenGL Engine
    OpenGL Version: 2.1 INTEL-8.26.34
    GLSL Version: 1.20
    Monitors: 1
    Monitor 0 properties -
       Size: (0, 0, 2880, 1800)
       Max texture size: 16384
       Supports non-power of two: 1
       Shaders 444: 1
       Shaders 422: 1
       Shaders 420: 1
    --- GPU Computation Info ---
    Found 1 devices supporting GPU computation.
    OpenCL Device 0 -
       Name: GeForce GT 650M
       Vendor: NVIDIA (Apple platform)
       Capability: 1.2
       Driver: 1.2
       Total Video Memory: 1024MB
    See the difference?  The nVidia GPU is listed.

  • Inactive Mercury Engine Playback GPU Acceleration

    Hello. I have problems with activating Mercury Engine Playback GPU Support in Premier Pro, Media Encoder, Prelude. It is dimmed and a can't choose it. Only Mercury Engine Playback Software Only.
    Workstation configuration: iMac 21'5 (mid 2013), Windows 8.1, Adobe Creative Cloud 2014 with last updates, Nvidia drivers 344.75 for Geforce GT650M
    I tried method with cuda_supported_cards.txt but it does not help.
    How I can enable CUDA Support?

    I've 512MB of VRAM GDDR5
    --- OpenGL Info ---
    Vendor: NVIDIA Corporation
    Renderer: GeForce GT 650M/PCIe/SSE2
    OpenGL Version: 2.1.2 NVIDIA 344.11 344.11
    GLSL Version: 1.20 NVIDIA via Cg compiler
    Monitors: 1
    Monitor 0 properties -
       Size: (0, 0, 1920, 1080)
       Max texture size: 16384
       Supports non-power of two: 1
       Shaders 444: 1
       Shaders 422: 1
       Shaders 420: 1
    --- GPU Computation Info ---
    Found 1 devices supporting GPU computation.
    CUDA Device 0 -
       Name: GeForce GT 650M
       Vendor: NVIDIA
       Capability: 3
       Driver: 6.5
       Total Video Memory: 512MB
       * Not chosen because of insufficient video memory.

  • I cannot enable Mercury Playback Engine GPU.. I have a FirePro W9100..

    As the title states, I cannot seem to enable Mercury Playback Engine GPU..
    I have a FirePro W9100, and the option to shift from software only to GPU is disabled.  Any ideas?
    I purchased the W9100 solely for use with Premiere, and help assist with GreenScreen rendering..
    I have the latest driver pack from AMD, and I'm running Premiere Pro CC 2014 (all updated).
    I'm banging my head against the desk with this one, and any help greatly appreciated!

    PROBLEM SOLVED.
    I reinstalled CS5 on the bookdisk and it worked fine. Spent 9 hours trying everything else its really was the only thing left and the last thing I wanted to do.
    Results:
    Rendering a 32min clip with Gaussian Blur effect
    Before CUDA it took 4 hours and hence my move to purchase a CUDA card.
    After CUDA 23mins! using Encoder
    Question:
    I noticed that the GPU is not stressing that much still. Only running at 30% activity???

Maybe you are looking for