Comments UPDATE: The Premiere Pro CS5 (5.0.3) update is now available and contains all of the fixes in the 5.0.2 update, plus many more.
Today, the Premiere Pro CS5 (5.0.2) update was released.
If Adobe Application Manager hasn’t already told you about this, go ahead and check for new updates for Premiere Pro CS5. Ideally, you should check for updates by choosing Help > Updates. But you can also directly download the update packages from the download pages for Windows or Mac OS, using the “Adobe Premiere Pro CS5 5.0.2 update” link. (If you download from the web page, you must choose the correct patcher based on your original installation type.)
If you have difficulty with this update, please bring questions and issues to the Premiere Pro forum. Don’t ask questions in the comments on this blog post, which fewer people will see.
There are a lot of fixes and tweaks in this update. You can read the complete list in the Premiere Pro 5.0.2 release notes. I’ll mention a few changes and fixes here, since some of these are important enough that I really want to make sure that people see them.
You should also install the Adobe Media Encoder CS5 (5.0.1) update (Windows or Mac OS), which got some bug fixes and additional formats and export settings presets, including several for F4V and FLV formats. (The download pages might not be updated yet at the time that you’re reading this.)
The After Effects CS5 (10.0.1) update is also available.
new and changed features
- We made several improvements to RED (R3D) import and workflow. See the last section of this post for details.
- Premiere Pro CS5 now integrates with CS Review.
- QuickTime (.mov) files from JVC solid-state cameras can be imported.
- Added sequence presets: Canon XF MPEG2 720p30 and Canon XF MPEG2 720p25.
- Premiere Pro CS5 (5.0.2) can export MXF files containing MPEG-2 essence items that comply with the XDCAM HD format used by such systems as Avid Unity. The standalone Adobe Media Encoder can also export files in this format.
- Added support for source timecode in XDCAM HD422 files.
- Added 10-bit DisplayPort support for NVIDIA Quadro cards on Windows.
- Audio files in Broadcast Wave (.wav) format can be imported, and timecode in these files is read and preserved. Audio in exported OMF files can be in Broadcast Wave format.
- Premiere Pro CS5 (5.0.2) for Windows adds support for the following graphics cards to accelerate processing using CUDA technology on the GPU: GTX 470, Quadro 4000, and Quadro 5000. For a complete list of supported graphics cards, see the Premiere Pro system requirements. For more information about CUDA acceleration of processing and the Mercury playback engine in general, see Premiere Pro Help.
bug fixes
There are a lot of fixes in this update. For details and a very long list of fixes, see the Premiere Pro 5.0.2 release notes.
Note that we were able to find and fix a lot of these problems because of the great feedback that we got when we asked people to use the crash reporter. Please keep doing so. And don’t hesitate to file bugs and send feature requests.
Here’s a partial list of bug fixes in this update:
- Various crashing issues fixed.
- When using AIFF source audio, previews and rendered and exported audio were scrambled or jumped around. (See this Technical Support document.)
- Adobe Premiere Pro projects files were growing very large (“bloating”), causing projects to take a long time to load, and sometimes causing projects to fail to load.
- The time to start Premiere Pro, load workspaces, and load a project have been decreased (improved).
- Title Designer panel showed no background video.
- XDCAM HD422 files generated by Convergent Design Nano Flash were imported with garbled audio.
- XDCAM EX media in a project was reconformed every time the project was opened.
- Four-channel audio recorded by Sony XDCAM EX camera was not being imported correctly.
- GPU-accelerated export through Adobe Media Encoder didn’t work correctly on Windows.
- Audio-only capture on Mac OS failed.
- Time required to render a preview increased each time the sequence was rendered.
- BMP and GIF files were not importing on Mac OS.
- Preview files were missing when a project was reopened.
- Various fixes for color shifts, gamma shifts, and incorrect color rendering for many formats and codecs.
- Various fixes for Final Cut Pro XML export. (See this page for details.)
- Various timecode fixes.
- Various fixes for performance and stability when using still-image files.
- Various fixes for performance, stability, and fidelity of CUDA-accelerated rendering using the GPU rendering pipeline in the Mercury playback engine (MPE).
- Various fixes for Firewire (IEEE 1394) output.
- Various fixes for Panasonic P2 media.
- Various fixes for audio and video being out of synch and audio playing at the wrong time.
One of the fixes for audio and video synchronization problems involves the MPEG index (.mpgindex) files created when Premiere Pro indexes imported MPEG-based media. If you re-index these files after installing the update, some problems with audio playing at the wrong time may be fixed. You can cause a file to be re-indexed by deleting the associated MPEG index files from the media cache.
other software updates known to address problems with Premiere Pro
We have also been working with several providers of plug-ins, codecs, and hardware devices (such as Cineform and BlackMagic) to assist them in updating their software to fix some errors and crashes. Please take this opportunity to download and install updated codecs, plug-ins, and drivers from these providers, as relevant to your work.
known issues
See the Premiere Pro 5.0.2 release notes for other known issues.
- Possible hang on start if firewall or other software (such as ZoneAlarm or FileMaker) blocks communication between Premiere Pro and related components. (See this Technical Support document for more information and solutions.)
updates for RED (R3D) footage and new REDCODE plug-ins
- Updated support for build 30 (Mysterium-X sensor, new color science) support: This is the same support that’s available as the RED3 Importer prerelease available on the Adobe Labs website. The difference is that the new RED importer software is installed with the Premiere Pro 5.0.2 update, so you don’t need to install the importer plug-in from the Labs website. For more information about changes and bug fixes in this importer, and how to make it work, see this blog post about the updated RED importer.
Note: If you save a project using R3D files from Premiere Pro CS5 5.0.2 and then open the same project in Premiere Pro CS5 5.0.0 or 5.0.1, R3D footage items in that project will be reset to default source settings. Premiere Pro CS5 5.0.0 and 5.0.1 use an older version of the RED importer plug-in. Also, Premiere Pro CS4 and Premiere Pro CS5 (5.0.0 and 5.0.1) projects that use color science version 1 will use the new color science (version 2) when opened using Premiere Pro CS5 (5.0.2). If you are using R3D footage in a multiple-machine environment, make sure all machines are using the same version of Premiere Pro.
- Initial support for RMD metadata sidecar files: RED (R3D) video files can store settings in RMD (RED metadata) sidecar files. Premiere Pro 5.0.2 introduces a Save RMD button in the lower right of the RED R3D Source Settings dialog box, with which you can save the current settings in the dialog box to an RMD sidecar file. You can also load or reload a sidecar file and set the settings in the dialog box to those in the sidecar file by clicking the Reload From RMD button. If there is no RMD sidecar file associated with the video file, the Reload From RMD button resets the settings to the defaults.
- Support for RED Rocket cards: RED Rocket cards are optional cards that can accelerate decoding and debayering of RED (R3D) files. To tell Premiere Pro to make use of an installed RED Rocket card, use the Enable RED Rocket (Global Setting) menu in the RED (R3D) Source Settings dialog box. The options are None, One, and All. The One and All settings refer to the maximum number that will be used by Premiere Pro; if fewer are available, then only the available number will be used. If another application acquires the ROCKET card before Premiere Pro does, Premiere Pro does not display a message at launch that it will fall back to software (non-ROCKET) rendering.
Is this new patch support Nvidia Geforce GTX 460 in Mercury Engine? I read the page and system support still listed the old GPU support. Thank you.
[reply from TMGK: This post tells what has changed; the list of additional cards doesn't include the GTX 460. This post then points to the original systems requirements page; that page doesn't mention the GTX 460. So, that indicates that the answer to your question is "no".]
The full release notes haven’t benn posted yet : has the problem of banding over large uniform areas (sky for example) during fadings to black been fixed ?
[reply from TMGK: Try it. Install the update and, if the problem persists for you, file a bug report here: http://www.adobe.com/go/wish ]
Why no support for GTX 480?
Does this break the “other” GPU’s work around?
[reply from TMGK: I won't comment on the functioning of any hack.]
I am confused that there is support for the GTX 470 and not the GTX 480.
SO any support then for the 465?
[reply from TMGK: This post gives a list and points to another list. Neither mentions the GTX 465. So, no.]
I don’t understand why adobe is so tight on supporting cards when the work around pretty much works with any Nvidia GPU flawlessly. And is TMGK a moderator or something, can we have a real adobe rep here?
[reply from TMGK (Todd Kopriva, the person who wrote this article):
We support the cards that we have been able to test thoroughly. It's better to have a small number of supported cards that everyone can be confident have been tested, rather than a large number with potentially thin testing coverage.
Regarding having a real Adobe rep: It doesn't get any more real than me. This is the official blog of the Premiere Pro team, and I'm a member of that team.
If you want to request support for additional cards, please submit a feature request: http://www.adobe.com/go/wish
If you want to talk about this more, let's do it on the forum, not in a comment thread here. This isn't the best interface for a conversation. Here's a link to the forum: http://forums.adobe.com/community/premiere ]
When will the AME update be posted for download? The page you link to only has older updates – not the new one.
Thanks!
[reply from TMGK:
If you choose Help > Updates, you should get the update through Adobe Application Manager. The web pages that host the updates tend to lag behind the Adobe Application Manager.]
I’m a little confused about the 470 vs. the 480 on the GPU list, but regardless, it’s hard to argue with 4 pages full of fixes and improvements. I’m pleased with what I’ve seen from the Premiere Pro development in the last two versions (CS4 and CS5) when it comes to fixing bugs and adding improvements in the months following the major release.
Really good work to you and the team, in both handling the actual update and managing the demands and expectations – wild and untamed as they are – from my fellow Premiere Pro users.
Ok for the great job on cs5, but till I made the last update, I have a message informing me that “there is a new update available for Adobe media Encoder for Premiere Pro, go to the website…” And I have some Compilation error. Before this, I had no troubles… I precise that I have the french version. A little bit desappointed…
What about firewire output (preview) while hardware MPE is on (Mac system)? I have two Mac Pro with FX4800/CUDA and no firewire output + hard MPE…
I would also like to see an answer for this as we have customers who still use tape based workflows
the auto-update seems to have knocked out all my presents, specifically my hdslr/dslr (canon 5d/7d)–can’t open my earlier project either. any advice?
[reply from TMGK:
At the top of this post, it says to not ask questions on this blog post but to take them to the Premiere Pro forum.
Here's a link to a thread on the forum that is relevant to your issue:
http://forums.adobe.com/message/3105993 ]
Does PPro also support monitoring via the RED Rocket card?
I updated today and now cannot render previous projects. I just get perpetual rendering that never ends. HELP
[reply from TMGK:
If you bring questions and issues to the Premiere Pro forum, we can help: http://bit.ly/4LhNPW
]
i think this is usefull
SONY has a new laptop, Model: VPCF136FM/B with a NVIDIA GetForce GT425M graphics card. Is this graphics card powerful enough to run the ADOBE PREMIUM PRO Mercury Engine so that I can playback RED ONE CAMERA video files? Thanks!
[reply from TMGK:
See the bottom of the system requirements page here for a list of cards that Adobe supports for the CUDA acceleration portion of the Mercury playback engine:
http://www.adobe.com/products/premiere/systemreqs/
The card that you mention is not ...on the list.
If you have questions about hardware for Premiere Pro, bring them to the Premiere Pro hardwar forum, and we'll help you there:
http://forums.adobe.com/community/premiere/hardware_forum
]
Well after this update with Cineform Neo Scene v5 installed. Priemire CS5 can not accept .mov files with Animation codec. I don’t know what is conflicting, Premiere, Cineform or Quicktime. All I know is that it does not work anymore, editing .mov files that is.
[reply from TMGK:
Be sure to install the newest Cineform software. They released an update right around the same time that we did to fix some issues. As this post of mine says, the Cineform updates and the 5.0.2 update are meant to go together.
If you continue to have a problem, bring the issue to the Premiere Pro forum, and we can help: http://bit.ly/4LhNPW
]
Hi question about cards.
All not listed card sill work, just no gpu acc correct?
would it also be true to say that a gpu acc might happen even if the card is not on the ‘approved’ list?
Thanks
Just wanted to say AWESOME JOB PREMIERE TEAM! I just tested out my first R3D workflow tonight, and it’s heavenly. Great work, thank you so much! Don’t let the naysayers get you down about video card supprt. Tight integration is what made Macs great, and it’s awesome to see that coming to PCs. If they want their application to function like a pro app, they should get a pro card.
LOVE all of the Mercury stuff, really really great stuff, integration with FCP and OMF is brilliant (and nessecary). Thanks so much! You guys have worked hard and come a long way from Pro v1.
i just wondered if anyone can tell me if the mercury gpu render acceleration will work for the boris final effect complete plug in?
왜 480을 지원하지 않는것입니까?
혹시 480을 지원하면
Fermi Series와 크게 성능차이가 나지 않는
Quadro급에 타격을 입히는건가요?
그리고 왜 SLI를 지원하지 않는것이죠?
기술적 문제인가요?
영어를 못해 이렇게라도 남깁니다.
[reply from TMGK: Premiere Pro에 대한 기능 요청 또는 버그 리포트를 제출하려면: http://www.adobe.com/go/wish ]
So QuickTime (.mov) files from JVC solid-state cameras can be imported But what about importing the XDCAM EX files into Premier that have been previously wrapped in Quicktime after importing to Final Cut Pro? I want to use CS5 but I have a ton of .mov XDCAM EX clips.
looks an impressive upgrade, is it included on the curent Cd for CS5 Installation ?
[reply from TMGK:
No.]
Does the Mercury Playback engine and the Red Rocket work in unison (do they compliment each other) ?
For instance, if you could get 3 video layers playing R3D files simultaneously with the MPE/Nvidia card and then you added the Red Rocket could you expect to be able to play additional R3D video tracks ?
Or if one is working does the other in a sense just sit idle ? (or am I thinking about it in the wrong way all together)?
I’ve currently got a Mac Pro with a Red Rocket installed and am seeing decent playback of R3D files in Adobe CS5 (5.0.2)… I am however using an ATI Radeon 4870 which apparently does NOT take advantage of the MPE (I need an Nvidia card for that).
I’ve been thinking of installing an Nvidia GTX285 which is listed on the Adobe site a card that works with CS5… but before I do this I want to make sure I’m going to see a significant performance boost.
Also, I haven’t been able to find a clear answer as to how the Red Rocket is being harnessed and used in CS5 (Premiere Specifically)… just how much of the work is it doing? Is it being fully utilized ?
Thanks in Advance !
[reply from TMGK:
If you ask these questions on the Premiere Pro forum, we'll answer there: http://bit.ly/4LhNPW
]
I guess the GTX 480 card is not supported because it has features that are not compatible with Adobe Premiere and the Media Encoder. I use the card and trying the work around only causes more problems than it fixes. I have found problems when rendering MP4 files using the Mercury Playback engine via the Media Encoder. So the long and short of it…. Only buy and use a graphics card that Adobe approves of.
BEWARE!
Adobe has awesome applications…but getting them installed…and then overcoming obscure bugs that totally ruin any attempt at enjoyment of these apps…makes me wish that I had NEVER gone done the Adobe route.