Friday, September 3, 2010

Premiere Pro CS5 (5.0.2) update: bug fixes and CUDA support

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

An After Effects update is coming very soon and will be announced here.


new and changed features

  • We made several improvements to RED (R3D) import and workflow. See the last section of this post for details.
  • 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.
  • 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.

Thursday, April 2, 2009

Sunday, March 29, 2009

The Adobe Day @ Fine Arts CAIRO



Adobe User Group - Fine Arts CAIRO hosting a new Adobe Day event Tuesday 24 March 2009 . The group is managed by Ahmed Waheib .


The Adobe Day event will introduce Adobe creative products to the group members and faculity students and how they can extend their creative ability by learning more about Adobe products. Start your new life at the home of Creative Minded Users and Feel your Succes with us.

Rafiq Elmansy (Adobe Community Expert, Adobe User Group Manager, Adobe Certified Expert and Adobe contributor author) and Ahmed Waheib (Adobe User Group Manager) will dig deep into the resources of creativity inside Adobe products.

Mr.Hany Sabry (general Manager of GES Egypt) & Mr. Mohamed abd Elfattah ( traning Manager of GES Egypt ) will illlustrate about the Adobe products what we are use in Print .

The Agenda :

01:00 Welcome Note & About AUG - Fine Arts CAIRO

01:30 Adobe Illustrator CS4 & Indesign CS4

02:15 Break

02:30 Adobe Flash & Cartoons

03:00 Adobe Photoshop & ART

Thnaks for All .

Ahmed Waheib

AUG - Fine Arts CAIRO Manager

Monday, March 16, 2009

Calling All Artists .:: YOU Are WELCOME ::.


We are currently in the process of lining up Artists from Fine arts cairo  for our fall meetings. If you are in the field of Graphic design, can talk for at least an hour, and care about helping the Adobe user group design community grow, we want to hear you! 

Topics can vary, all we ask is that you focus on  Designs in some fashion,print ads,web & outdoor print. While we prefer that your in the EGYPTIAN  ART area. If you are listener then a talker, want to know something about graphics, feel free and come with us YOU Are WELCOME.

Ahmed waheib - AUGM 


Canon or Nikon?



Nothing riles up photo pros on forums more than a newbie "Canon or Nikon?" question. And yet, the fact that this question is asked by so many people is an indication of a large communications inefficiency that has spawned a thriving camera review industry.

Remember how marketing textbooks always said that people don't really buy drills, they buy holes? Well, you'd imagine that when shopping for cameras, people are really buying pictures and not the expensive black boxes, but you can't really tell by the way cameras are sold today.

There are a lot -- a huge unmanageable lot -- of resources that let you compare the boxes down to their smallest and, to many, meaningless details. About the only way to compare pictures these different boxes produce is to shovel through the Camerassection on Flickr.

This doesn't make sense. I'm trying to think of another consumer electronics product that you buy for its output where you want but are unable to compare the output of different models. You can compare TV sets by walking up to the wall in Best Buy. For shredder shoppers, confetti samples are readily available on display. It might be tough to compare irons, but then I guess most people don't expect deviations in the quality of heat and steam.

I wish there were an easier way to make up my mind about a camera than trying to understand complicated reviews when all I need to know is what body+lens combinations produces nice baby pictures for under $700.