Known Participant

Answered

Premiere Pro CS5.5 stopped recognizing my CUDA-enabled card

Forum|Forum|14 years ago
June 24, 2011
11 replies
35955 views

I just fired up the project I've been editing on a 3-year 2 x 3 GHz QUad-Core Intel Xeon old MacPro, which I upgraded with a Quadro 4000 a few weeks ago to get the benefits of the Mercury Playback Engine, and got a message saying that the last time I opened this project I was on a Mercury enabled machine, but now I'm not so it's opening my project up in "software only" mode. Weird because of course it's the same machine both times. The Mercury box in the "project settings" menu is grayed out set to "software only" so there's no manually changing it.

The only two things that I have changed on my system since yesterday are

1. I installed FCP X (which won't open, just crashes)

2 I installed the OS X 10.6.8 system update

Anyone else having this trouble?

Thanks.

R

This topic has been closed for replies.

Correct answer Todd_Kopriva

Here are the full details and instructions from the Nvidia folks:

"Quadro 4000 driver and CUDA driver update for Mac OSX v10.6.8"

A

Anonymous

Note that there are newer NVidia drivers out if your didnt upgrade the yet.

C

churchillstudios

Participating Frequently

Hey folks I was caught editing all day long and had to do several workarounds to finish due to my continuing problem with dissolves in a Mercury GPU accelerated project. This repeatable has occurred - or at least I started noticing it - only after I updated to the latest Nvidia drivers for OSX. I was able to create a small project that duplicates the problem… Could anyone load this up and tell me if this is repeatable on their machine?

You can download my test project (53MB) from my FTP, here:

ftp://0320579.netsolhost.com

User: newguest1

PW: churchill1!

filename: "Dissolve Problem.zip"

In this test project, the problem occurs twice. Once at 7:20 and again at 8:13. Look close and you'll see the dissolve is mistakenly fading to the previous clip, then hard-cutting to the next. It's easy to spot, unless my system is the only one creating this error. My email is churchillstudios@aol.com and studio line is 901-754-6675 if you have any direct questions. Please advise … and thanks!!

Brian Churchill

Churchill Studios, Inc.

www.churchillstudios.com

M

marcusmoonen

Participant

I didn't run into the dissolve problem, but I tried the new drivers and soon the troubles started with my Magic Bullet plugins.

I applied Looks to some HDSLR footage, no problems, then I added Denoiser and the whole thing went pear-shaped. I started getting errors that wouldn't go away and eventually it crashed Premiere. It seems there are still lots of problems with these new drivers.

Adobe, I've sent you the crash report.

C

churchillstudios

Participating Frequently

Thanks Brian, I can confirm your bug and will work on a fix, but obviously cannot commit to any timeframe. The workaround you mention of placing an accelerated effect on one end will work fine, and any accelerated effect that by default doesn't render such as fast color corrector should do. Note that your comment about Noise not being YUV or 32 bit isn't quite correct. The badges are for the software capabilities and all CUDA effects, such as noise, are always 32-bit float even when the software effect isn't.

Thanks Steve. Good news is it looks like we've got a viable workaround for this strange dissolve problem. So I take it this was not a result of the CUDA update? (If so, sorry for the threadjack; I hadn't noticed the problem until now.) Can you share more information as to what causes the bug by e-mail or perhaps on a separate thread? Also, I'd love to read more info on how accelerated effects are always 32 bit, even if they aren't marked that way.

- BC

C

churchillstudios

Participating Frequently

Okay guys will someone check this out for me? I upgraded to the newest drivers this morning, however now I'm seeing a MAJOR bug with a simple dissolve transition in Mercury GPU acceleration... Test this out please:

1. Add footage to the timeline (In my case HDV) and edit a cut between two clips.

2. Apply a dissolve transition between them with Mercury GPU on... on my system it's just a cut.

3. Disable Mercury GPU playback ... the dissolve works fine.

Please confirm this as a bug and let the powers that be know. Thanks!

- BC

C

churchillstudios

Participating Frequently

This is still on on a Mac Pro, by the way, OSX 10.6.8, Cuda driver 4.0.19, GPU driver 1.6.37.0 (256.02.25f01)

L

lightprism

Known Participant

http://www.nvidia.com/object/macosx-cuda-4.0.19-driver.html

The fix is located here.

Restores CUDA GPU acceleration within Premiere using 10.6.8 and the new nVidia graphics driver for their cards.

Thanks to everyone for the quick work and effort to make this happen so fast.

HAPPY< HAPPY HAPPY !!!

Todd_KoprivaCorrect answer

Inspiring

Here are the full details and instructions from the Nvidia folks:

"Quadro 4000 driver and CUDA driver update for Mac OSX v10.6.8"

A

Anonymous

It worked! Goodbye FCPX, hello adobe Premiere Pro ...Oh happy days. Good response time. Respect.

trancepriest

Participant

I'm having the same issues on 10.6.8 breaking the CUDA support on both Premiere Pro and Davinci Resolve. Even with the new Quadro 4000 driver. Hopefully this fix is just Adobe coming out with a new CUDA support driver.

C

churchillstudios

Participating Frequently

Update from the same link on Nvidia's site: http://forums.nvidia.com/index.php?showtopic=203839

Someone posted a workaround where you roll back the Nvidia driver to the March release, and Mercury GPU acceleration comes back online for 10.6.8. HOWEVER I have noted a performance hit from my last edits, as noted on that thread. Here's a copy/paste of my observations:

Successfully rolled back to the March drivers ... Thank you! Premiere shows Mercury GPU acceleration back online, HOWEVER I see a performance hit from where we were. I just loaded several projects that used to play at full frame rate (or close to), now getting more dropped frames. Not so obvious on straight DSLR footage, but there's definitely some frame sticking that wasn't there before, particularly obvious on cuts. Another project I have features multiple flying titles on layers and nested sequences utilizing Premiere's Move/Scale, Basic 3D and Proc Amp effects. Playback is definitely faster than CPU-only (I have a Mac Pro w/ dual 2.93 Xeons) but seems less "smooth" than it was. Hard to compare... Anyone else experiencing GPU performance differences?

Just want to make sure Nvidia knows this workaround is not 100% fixing the problem.

It DOES help though. Here's a direct link to the March driver: http://www.nvidia.com/object/quadro-macosx-256.01.00f03v7-driver.html

If you need to roll back, you have to manually install each package as the installer will say "No Driver Update Needed" ... Here's how:

1. Open the package in Finder (right click and "Show Package Contents")

2. There will be 3 packages inside, Display, Driver and Opengl, install each of them reboot.

Visit the Nvidia thread http://forums.nvidia.com/index.php?showtopic=203839 for more info. I'd also like to encourage anyone who sees a similar performance hit to post their findings both here at Adobe and on Nvidia's site. I'd test more, got to get back to real work for now. Hope this helps everyone out so we can all get back up and running.

- BC

M

marcusmoonen

Participant

Thanks for the info on a workaround, but as stated that by no means is a solution.

I hope that Adobe and nVidia will find a way to sort this out very soon and hopefully figure out how to prevent this with future updates from Apple. I don't want to go through this every time Apple decides to update OSX. That would be just plain ridiculous and unprofessional.

C

churchillstudios

Participating Frequently

Same here... Adobe / Everyone If a workaround is discovered please make sure to post it here. If no solution is found, I'm dead in the water start of next week!

- BC

Todd_Kopriva

Inspiring

We're looking into this. Anyone who is interested in this issue should follow this thread on the Nvidia site:

http://forums.nvidia.com/index.php?showtopic=203839

Nvidia is tracking the issue there.

A

Anonymous

Thank you for the link, Todd.

A

Anonymous

And to be honest, Adobe was not very helpful in trouble shooting this issue with me. I sat on hold for over an hour with Adobe customer service just to be told that no one else is having this problem but me...lol. If I can't resolve this in a timely manner then Final Cut Pro X here I come. Peace out Adobe Premiere Pro.

A

Anonymous

The Same thing happened to me. I upgraded to Mac OS X Version 10.6.8 from 10.6.7, earlier today. I was in the middle of working on a project for a client in Adobe Premiere Pro CS5. I have a Nvida Quadro 4000 graphics card. After I updated my system Mac OS X 10.6.8, Premiere pro stopped recognizing my graphics card. I called Adobe and they said that no one else is having this problem. Obvisoly this is an issue for many other Premiere Pro CS 5 and CS 5.5 users. I have the updated Nvida Quadro drivers for my graphics card but still the problem persists.

When I open a project in Premiere Pro I get the following message:

"This project was last used with Mercury Playback Engine GPU Acceleration, which is not available on this system. Mercury Playback Engine Software Only will be used".

This is a huge problem for me. I work in high definition AVCHD format. I can't even preview my work, let alone edit it without my graphics card functioning properly with Premiere Pro. Everything was working fine until I updated to Mac OS X 10.6.8. Like I said, I have the latest drivers installed from Nvidia. If anyone out there knows how to fix this, I would be so appreciative.

L

lightprism

Known Participant

Well folks, I hate to say it looks like the Apple 10.6.8 broke

the nVidia 4000 for the Mac card support of GPU acceleration in Premiere. Here's why:

My Intel Mac 3,1 was running Premiere beautifully - I did NOT get sucked into installing FCPX.
When I booted up my machine this morning, "Software Update" told me I need to install the update of operating system 10.6.8 for many security reasons and bug fixes which is why I did so - appeared very urgent, especially to protect against a new named virus attacking Apple machines.
I immediately had all kinds of funkiness - sluggish operation, Firefox and Safarie freezing requiring force quits, Premiere lost it's GPU acceleration ability (all greyed out and not an option any longer - old projects or new projects - no longer a selectable choice)
For kicks, I tried to open good old FCP7, and whalah - error message pops up stating that my "graphics card did not meet the requirements for running FCP7" and it also wrongly showed I had a graphics card with "0 Vram installed"
After searching around the web, I started finding all the horror stories about 10.6.8. Found the info that nVidia had sometime today (6-24-11) posted a new driver for this specific card to fix issues with 10.6.8 which just came out. After installing the new nVidia driver needed for 10.6.8 and this graphics card, all funkieness went away... Firefox and Safari worked fine, sluggishness went away, and FCP7 worked fine as before. B U T Premiere GPU accleration was STILL broken.

Apple has broken their competitor - surely they would have tested one of the few major graphics cards that work in the Mac version of Adobe Premiere.

Apple made sure that nVidia had a new driver for THEIR combinations of nVidia Quadro 4000 for the Mac and FCP7 and X ... but not for Adobe Premiere.

Hopefully Adobe will jump on this quickly. I think it is clear something foul is afoot!

M

Maciej_ca

Participant

I seem to be in the same boat as you.

I installed 10.6.8 yesterday, and had soem sluggish perfomance on the system.

Updated to the new Nvidia Driver for 10.6.8 (Quadro 4000), also tried reinstaling Cuda.

Mercury playback is no longer available now. I did install FCPX as well yesterday.

Show more replies

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded