Adobe Premiere Pro CS5 5.5.2 update now available

Question

The Adobe Premiere Pro CS5 5.5.2 update brings Mercury Playback Engine support for NVIDIA ‘Maximus’ configurations, where a Tesla card can work alongside a Quadro card for increased GPU processing power. The update also fixes issues which prevent the proper display of Closed Captions and the Timecode Effect, and fixes the Color Picker on Mac OS X 10.7 (Lion). In addition:
• Mac: Fixed an issue where the Timecode Effect was not displayed properly when rendering/exporting to a new file (2977326)
• Mac/Win: Fixed an issue which could cause Closed Captioning data to be displayed in the wrong location, and sometimes offscreen (2927519)
• Mac: Fixed an issue which could cause Assert errors when enabling the display of Closed Captioning data (2977314)
• Mac: Fixed an issue where the Color Picker did not pick the correct color (2977304, OS X 10.7 only)
• Mac/Win: Fixed an issue which could cause the application to crash when trimming with third-party I/O hardware installed (2984420)
The update is available on Adobe.com at:
http://www.adobe.com/support/downloads/detail.jsp?ftpID=5285
http://www.adobe.com/support/downloads/detail.jsp?ftpID=5286
http://www.adobe.com/support/downloads/detail.jsp?ftpID=5287
http://www.adobe.com/support/downloads/detail.jsp?ftpID=5288
And it will be available via AAM within the next day or so. Enjoy!
Sheri

Answer 1

Todd_Kopriva wrote:
> There was a FIX promised for this issue almost 6 months ago.
Please point me to where you saw this.
What I do recall is us saying that we were likely able to fix some DSLR scrubbing/playback issues in an update. We did. There was a major improvement in scrubbing/playback for DSLR files. The issue that we weren't able to fix in the update was the issue in which the decoding of some Nikon .mov files was done using QuickTime instead of the native decoders. But all that you need to do to get around that is change a file-name extension.
Ok, so maybe a fix wasnt promised for this. Maybe 3 months ago when a fix was being worked on and should be released soon, that isnt a promise. 
This is like using a spare tire on a car.  Would you pay for a car and then use a small spare tire for three months on it, cuz its a workaround thats kinda simple?  Maybe thats not a relative comparison. Maybe this is extremely difficult. It was working fine in cs5 premiere tho. So I guess im just gonna have to drive around with this piece of .... spare tire until you guys decide to actually fix this problem.  I will however not be upgrading future releases if this is the way you handle bugs. 
Ive had this issue since day 1 of upgrading. That was May 2nd I believe, cant remember the exact release date. Thats 6 months of waiting for a fix for this problem. Workarounds are dumb, I didnt pay for software for workarounds.