Skip navigation

Premiere Pro

Currently Being Moderated

Adobe Premiere Pro CS5 5.5.2 update now available

Nov 1, 2011 3:36 PM

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

5473 Views 25 Replies Latest reply: jefbak, Nov 18, 2011 7:24 AM

Replies

Currently Being Moderated

1. Bill Hunt,

Nov 1, 2011 3:47 PM in reply to Sheri Codiana

Report

Sheri,

Great news, and thanks for the H/U.

Appreciated,

Hunt

|
Mark as:
Currently Being Moderated

2. Todd_Kopriva,

Nov 1, 2011 3:52 PM in reply to Bill Hunt

Report

more details here, including information about the new Maximus capability for CUDA processing:
"Adobe Premiere Pro CS5.5 (5.5.2) update: Maximus functionality and bug fixes"

|
Mark as:
Currently Being Moderated

3. lasvideo,

Nov 1, 2011 3:58 PM in reply to Todd_Kopriva

Report

Todd - "We have also been working with several providers of plug-ins, codecs, and hardware devices (such as Matrox, Nvidia, and BlackMagic) to assist them in updating their software to fix some errors and crashes."

I notice that AJA is conspicuously absent from your list of third party hardware vendors. This is of great concern since th AJA timelines still have lots of issues (noted here on this forum) that the Adobe timelines dont exhibit. Whats the story?

|
Mark as:
Currently Being Moderated

4. Todd_Kopriva,

Nov 1, 2011 4:25 PM in reply to lasvideo

Report

Tom,

The Nvidia part is about the new Maximus features and some Lion-specific issues; the Matrox part is about the instability when trimming; and theBlackmagic part is actually a little stale, being about a fix in 5.5.1. The omission of AJA there isn't because we're not working with them; it's just because there's nothing in this relatively small update that touches on them specifically.

|
Mark as:
Currently Being Moderated

5. lasvideo,

Nov 1, 2011 4:15 PM in reply to Todd_Kopriva

Report

Gotcha! Thanks Todd.

|
Mark as:
Currently Being Moderated

6. Zac Lam,

Nov 1, 2011 4:31 PM in reply to Todd_Kopriva

Report

The instability when trimming with CUDA enabled was first noticed by a Matrox customer, and made it's way to our bug database. However, the same issue in 5.5.1 affected third-party hardware in general, and we have verified that 5.5.2 does fix the same issues for AJA as well. Sorry Todd that wasn't clear from my comments in the bug record.

Zac

|
Mark as:
Currently Being Moderated

7. Todd_Kopriva,

Nov 1, 2011 4:34 PM in reply to Zac Lam

Report

Thanks for the clarification, Zac.

|
Mark as:
Currently Being Moderated

8. Ray Tragesser,

Nov 1, 2011 5:52 PM in reply to Todd_Kopriva

Report

Hi Todd,

Is there a reference guide that talks about Maximus configurations and benefits for Premiere Pro users?

Thanks
Ray

|
Mark as:
Currently Being Moderated

9. Todd_Kopriva,

Nov 1, 2011 9:51 PM in reply to Ray Tragesser

Report

> Is there a reference guide that talks about Maximus configurations and benefits for Premiere Pro users?

It's relatively simple. The Maximus configuration allows the Tesla card to be used for CUDA processing, while the Quadro card is used for driving the display and OpenGL processing.

Because the Tesla cards have lots of computation ability without the overhead of needing to also serve as a display card, you get a lot of processing power for the dollar. (Not that the Tesla cards are cheap, but they're less than an card with the same CUDA cores and VRAM would be if it also had the other components of a display card.)

|
Mark as:
Currently Being Moderated

10. pmasters8941,

Nov 1, 2011 10:24 PM in reply to Sheri Codiana

Report

Any idea what this error code means? Adobe Premiere Pro CS5.5 5.5.2 Installation cancelled. Error Code: U44M2P24

OSX Lion 10.7.2
MBP 2011 15"

|
Mark as:
Currently Being Moderated

11. Todd_Kopriva,

Nov 1, 2011 10:27 PM in reply to pmasters8941

Report

Pat,

The first thing to check is to make sure that you downloaded the correct patcher---the one for the DVD version or the one for the download version.

|
Mark as:
Currently Being Moderated

12. pmasters8941,

Nov 1, 2011 10:30 PM in reply to Todd_Kopriva

Report

Yep, made sure of that and downloaded the other as a fail safe. Installed the retail DVD patch when I got this error. The other patch doesnt even try to install and gives a warning that it cannot be installed. It's perplexing to say the least.

|
Mark as:
Currently Being Moderated

13. Todd_Kopriva,

Nov 1, 2011 10:40 PM in reply to pmasters8941

Report

The update will be available through Adobe Application Manager (Help > Updates) soon. I suggest trying that method when it's available. If that doesn't work, then uninstalling the application, reinstalling, and then updating would be the next thing to try.

|
Mark as:
Currently Being Moderated

14. Ray Tragesser,

Nov 2, 2011 6:07 AM in reply to Todd_Kopriva

Report

Hi Todd,

Can you give a little more performance detail - "real world" observations with the Tesla C2075 card installed into a system? If I already am running a Quadro 4000 what areas of improvement could I expect to see in Premiere Pro CS-5.5 or CS-X going forward?

|
Mark as:
Currently Being Moderated

15. Sheri Codiana,

Nov 2, 2011 10:07 AM in reply to Sheri Codiana

Report

The update is now available via AAM (Adobe Application Manager, Help > Updates).

Sheri

|
Mark as:
Currently Being Moderated

16. 50 Hungry Lions,

Nov 2, 2011 9:22 PM in reply to Sheri Codiana

Report

Hello,

I was wondering if this fixes the issue with D7000 cameras as well, or that was fixed in a previous patch. I know it doesn't list it as one of the fixes, but I thought maybe it wasn't mentioned.

Thank you

|
Mark as:
Currently Being Moderated

17. Todd_Kopriva,

Nov 2, 2011 10:16 PM in reply to 50 Hungry Lions

Report

> I was wondering if this fixes the issue with D7000 cameras as well, or that was fixed in a previous patch. I know it doesn't list it as one of the fixes, but I thought maybe it wasn't mentioned.

All of the fixes in this update are listed here.

The workaround for Nikon D7000 footage playback is here.

|
Mark as:
Currently Being Moderated

18. 50 Hungry Lions,

Nov 6, 2011 11:58 AM in reply to Todd_Kopriva

Report

Todd,

I know the workaround. There was a FIX promised for this issue almost 6 months ago. I paid alot for this software, and alot for my camera. I was kinda hoping that the investment would be supported by Adobe. I dont understand how it is not a simple fix for your company? Just because theres a workaround, doesnt make it FIXED.

Its disappointing as I feel like upgrading to .5 versions are pointless if you guys arent going to support them. Are we supposed to wait til we get the cs6 or whatever it is to be called before we get fixes for issues?

Please FIX this problem.

|
Mark as:
Currently Being Moderated

19. Todd_Kopriva,

Nov 6, 2011 2:45 PM in reply to 50 Hungry Lions

Report

> 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.

> I dont understand how it is not a simple fix for your company?

If we were to change the code for determining which decoding path is used for various file types, the testing required would take a long time. This would delay the release of all of the other fixes in the updates. We considered it far more beneficial to far more users to get all of the other fixes out in the update rather than delay the release of the update for this one issue---for which there is a very simple workaround.

|
Mark as:
Currently Being Moderated

20. 50 Hungry Lions,

Nov 7, 2011 7:25 AM in reply to Todd_Kopriva

Report

This would delay the release of all of the other fixes in the updates. We considered it far more beneficial to far more users to get all of the other fixes out in the update rather than delay the release of the update for this one issue---for which there is a very simple workaround.
I hate to argue with you man, but this is what you said on 5.5.1 release also.

|
Mark as:
Currently Being Moderated

21. 50 Hungry Lions,

Nov 8, 2011 6:10 PM in reply to Todd_Kopriva

Report

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.

|
Mark as:
Currently Being Moderated

22. jefbak,

Nov 15, 2011 9:04 AM in reply to Todd_Kopriva

Report

Hi Todd, this update is causing a lot of playback and scrubbing problems for me using a Mac. How can I go back to 5.5.1?
Timeline lag and freeze and program monitor problems are the issue with projects that previously worked just fine.

|
Mark as:
Currently Being Moderated

23. Todd_Kopriva,

Nov 15, 2011 9:08 AM in reply to jefbak

Report

> How can I go back to 5.5.1?

Uninstall the application. Re-install the application. Install the 5.5.1 update.

> this update is causing a lot of playback and scrubbing problems for me using a Mac
Please submit a bug report.

|
Mark as:
Currently Being Moderated

24. jefbak,

Nov 15, 2011 9:30 AM in reply to Todd_Kopriva

Report

Ugh, that will be a pain since this is a volume license install so I would have to request the discs again. Ugh.

Sent from my iPhone

|
Mark as:
Currently Being Moderated

25. jefbak,

Nov 18, 2011 7:24 AM in reply to Todd_Kopriva

Report

Is it possible that any rendering done in projects created in 5.5.1 or earlier need to be removed and re-rendered after updating to 5.5.2?

This appears to be helping with the performance problems for me, but I have never had to do that before with any update. All my projects are displaying performance problems now until I remove the rendering files and re-render.

|
Mark as:

Forum guidelines

Answers + Points = Status

10 points awarded for Correct Answers
5 points awarded for Helpful Answers
10,000+ points
1,001-10,000 points
501-1,000 points
5-500 points