Premiere Pro 5.5.1 not working with CUDA in Lion 10.7.1: FIXED

So I hadn’t tried the updated Premiere Pro, 5.5.1, which I was hoping had fixed my CUDA issues, but instead it has made them worse. I had to update my CUDA driver to 4.0.50 with Lion GPU Driver 7.4.10 2.70.05.05f01, and that allowed Premiere Pro to boot, and the program runs, but unfortunately without CUDA support. My Geforce GTX 285 is supported, but does not work with CUDA Support.

I have reported this to Adobe and to NVIDIA, but have not heard anything back as of yet.

PremiereNewProject

I did a complete Adobe uninstall and re-installed and I have CUDA support back. So something just wasn’t happy. Have to check on my plug ins now, but at least it is working correctly.

Premiere Pro 5.5.1 Released

Adobe Premiere Pro CS5.5.1 has been released.

Here are the bug fixes:

  • Improved playback/scrubbing performance of footage from DSLR cameras.
  • Media from Avid Unity QuickTime reference files was not imported.
  • XML project files created by Premiere Pro did not work with DaVinci Resolve.
  • On Mac OSX v10.7 (Lion), the Universal Counting Leader was missing countdown numbers.
  • On Mac OSX v10.7 (Lion), Premiere Pro would crash when quitting.
  • On Mac OSX v10.7 (Lion), closed caption overlays did not appear in Program Monitor.
  • Preview in the Capture panel was not functioning properly for HDV footage.
  • Image sequences lost their frame rates.
  • Edges of a clip were highlighted during transitions/dissolves when using CUDA processing.
  • Projects created by importing Final Cut Pro XML projects that contain multiple mono clips would lose some audio when the project was closed and reopened.
  • Exporting to a QuickTime movie using DVCPRO HD settings would not complete under some circumstances, including if an image, graphic, or synthetic element was in the sequence.
  • Using CUDA-accelerated Invert effect would reposition the clip.
  • Premiere Pro could not find files after changing the location of the project.
  • If an After Effects composition with a background color other than black was included in a sequence and Mercury Playback GPU Acceleration was enabled, the alpha channel transparency of the composition was ignored.
  • MXF files created by Premiere Pro were not readable by Sony XDCAM HD decks, Final Cut Pro, or Avid Media Composer.
  • ProRes files created by an ATOMOS device with four tracks of audio were not imported correctly.
  • MCC closed caption files exported from MacCaption failed to appear in the Premiere Pro Program Monitor under some conditions.
  • Incorrect data was being written to XML files for AVC Intra exports.
  • Opacity effects were being ignored after a second transition when CUDA processing (Mercury Playback Engine GPU Acceleration) was enabled.
  • Premiere Pro would hang or crash when loading a merged clip with disabled audio channels.
  • various other crashes

No word on the 64 Bit Kernel Issue.

You can download the Mac Version here, or the Windows Version Here.

Adobe has a 45% gain after Apple releases FCPX!

Hardmac has an article on an official statement from Adobe about them having a 45% growth in OS X after the release of FCP X. Good job Apple! You could not have done more for Adobe, or in all likelihood AVID than crippling FCP X as you did!

And if you cared, you would have released an update to FCP X by now, but obviously you have not, so your claims to caring are shown to be hollow!

Digital Rebelion on 18 Features Premiere needs to borrow from FCP 7

Digital Rebellion has an excellent article on 18 features that Premiere Pro must lift from Final Cut Pro, some of which I have covered extensively (like showing clip duplication in the timeline) and others I had not even realized, but all I agree with are necessary for Premiere Pro to really replace Final Cut Pro.
Though I doubt you will ever be able to open multiple projects as you can’t in After Effects either (only import projects into each other). Still it would be nice!

FilmRiot is Premiere better than FCP

Film Riot has a a good video podcast on is Premiere Pro better than Final Cut Pro, and basically it comes down to that yes it is. It can open Final Cut Pro projects, and is really damn fast. And one of my favorites, is the After Effects integration, which really is incredible. Check out this video below.

Biscardi Creative on Premiere and AVID with Davinci Resolve

Biscardi Creative has an interesting article on workarounds to use Adobe Premiere Pro and AVID Media Composer with Davinci Resolve which is currently made to work with Final Cut Pro 7.

It looks like there is no easy solution right now, as Resolve reads Premiere’s XML, but not all of it’s media is compatible, and you need a $500 plug in to make it work with AVID. Otherwise you basically need to export a quicktime and use scene detection to make a grade (so no dissolves).
Not an ideal solution for sure.

Scroll Wheel in Premier Pro

Adobe has a good tech article on scrolling in Premier Pro. This is functionality that seems strange to me, so I thought I would post it.

I am sure anyone who has tried premiere pro sees that scrolling with a mouse in Premiere Pro moves you down the timeline and doesn’t reveal tracks, but you can still scroll by hovering over the scroll bars and using the wheel, and it can also zoom the timeline if you hold down the option key (though I would like to see a setting to change the scrolling behavior from right to left to up and down).

Biscardi Creative switches to Premiere Pro

Biscardi Creative has an excellent article on why they are not waiting for Final Cut Pro X to become this amazing Paradigm of editing in the future, when they can do everything they need in Premiere Pro right now. The article really mirrors what I am feeling about Premiere Pro right now. I love not having to re-compress to Pro Res, and edit in realtime in my timeline.

There’s been so much talk about a “new paradigm” and “a new beginning” lately courtesy of Apple.  Defenders of the “new paradigm” are quick to point out that this is an entirely new application, nothing like it has ever been done, therefore, Apple had to break with all convention to create Final Cut Pro X.   It’s stripped down now, like Final Cut Pro 1, but give it time and the things we “need” will be added back over time.  It has so much “potential for the future.”


The more I work with Adobe Premiere Pro the more I just don’t understand that mentality.   Why wait?  Premiere Pro already includes the “missing elements” of FCP X and so much more it can’t do.



He goes on to say that despite all the protesting in forums he transferred over a large project to Premiere Pro final Cut Pro 7 and it all worked perfectly, he loves all the realtime effects, and also how Adobe Media Encoder can look into Premiere Pro and After Effects projects and render individual sequences without having to open the host apps, which for him, and for me is huge! You don’t have to export a quicktime movie and you don’t have to give up the host app to to the compression. THAT IS SO COOL, AND SO USEFUL! TALK ABOUT A TIME SAVER!