September, 2012 Archives
Today, we released new updates for several of our CS6 applications on Windows, including Adobe Media Encoder, Premiere Pro, and Prelude.
These updates are cumulative Windows-only updates that contain an important change to the code signing to address the issue described on the following pages:
- Security certificate updates
- Certificate revocation FAQ
- Adobe to revoke code signing certificate
- Guidance for IT administrators | Adobe certificate revocation
We strongly recommend that you install these updates.
You can install the updates automatically by choosing Help > Updates, or you can follow the links below for manual download and installation:
- Premiere Pro CS6 (6.0.3) for Windows, which contains all changes in Premiere Pro CS6 (6.0.2) and the code-signing change
- Adobe Media Encoder CS6 (6.0.3) for Windows (64-bit or 32-bit), which contains all changes in Adobe Media Encoder CS6 (6.0.2) and the code-signing change
- Prelude CS6 (1.0.3) for Windows, which contains all changes in Prelude CS6 (1.0.2) and the code-signing change
If Adobe Application Manager hasn’t already told you about this, go ahead and check for new updates by choosing Help > Updates. The best way to check for updates is by closing all Adobe applications other than Adobe Bridge, and choosing Help > Updates in Adobe Bridge; this ensures that all processes related to Adobe video applications have been quit and can be updated safely.
Note that the Premiere Pro CS6 (6.0.3) update is only available for Windows. It contains all of the changes in the Premiere Pro CS6 (6.0.2) update, plus one more change to address an issue described here.
For information about updates for other Adobe professional video applications, see this page.
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.
We have also been working with several providers of plug-ins, codecs, and hardware devices 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. For more information about plug-ins and third-party hardware for Premiere Pro CS6, see this page.
We strongly recommend that users of Premiere Pro on Mac OS update to Mac OSX v10.8 for performance and stability improvements in that operating system update.
Updates are cumulative, so installing the Premiere Pro CS6 (6.0.2/6.0.3) update will also provide the fixes and features in the Premiere Pro CS6 (6.0.1) update.
features added or changed in this update
- Windows 8 certification
- updates for HiDPI display, which improves appearance on computers that use Retina Display, such as MacBook Pro computers
added GPUs to the list of those that Premiere Pro CS6 will use for GPU processing: GT 650M with 1GB of VRAM and GTX 680
Note: Premiere Pro can use either OpenCL or CUDA for GPU processing on the GT 650M. The default is to use OpenCL. You can change this in the General project settings.
notable bugs fixed in this update
- tearing in image when using XDCAM EX footage
- numeric keypad keys couldn’t be assigned to keyboard shortcuts
- audio deleted when enabling Audio Follows Video without enabling multicam for audio track
- color shift introduced by Three-Way Color Corrector at default settings when GPU acceleration turned off
- color shifts in some imported M2TS assets
- Premiere Pro ignored Command+Option+H command to hide applications on Mac OSX
- Auto-save window appearing over other applications when Premiere Pro was in the background
- crash during auto-save if a third-party effect’s modal dialog box was open on Mac OSX (affects CoreMelt, etc.)
- rendering preview files using OpenCL caused dropped frames in some cases
- rendered preview files not used when restarting Premiere Pro in some cases, including when using certain third-party effects
- when using CUDA on Mac OSX to export a sequence consisting of a very large number of still images (e.g., timelapse), GPU memory could become depleted and output frames corrupted
- audio recorded through Audio Mixer (e.g., voice-over recording) appearing incorrectly as duplicated audio
- channel output mapping for adaptive tracks was reset to default settings for duplicated sequences
- audio waveform displayed incorrectly for clips with speed adjustments
- audio playback for multichannel files too quiet in some circumstances
- markers added during peak file generation not saved if Premiere Pro quit before peak file generation completed
- fixes for QuickTime groiwng files
- some 4:2:2 footage appeared jagged or pixelated in Program Monitor or Source Monitor when no effects applied
- some MXF files going offline, requiring relinking
- relinking to AVCHD media on Mountain Lion (Mac OSX v10.8) not possible for projects created on other operating systems
- automatic relinking of footage occurring incorrectly in some cases
- frames imported out of order for some MPEG assets
- changes to timeline clip channel mapping performed using the context menu for the clip in the Timeline panel Audio were not saved with the project
- Audition opened when choosing Reveal Project In Explorer from context menu for a clip in Premiere Pro Project panel
- multicam source sequences in Source Monitor lost A/V synch when an In point was created
- setting an In point in the Source Monitor created an In point for all clips in the Media Browser directory
- thumbnails not appearing for some XDCAM HD items in Project panel and Timeline panel
- deleting a nested sequence not providing a warning
- layers not correctly counted in PSD file (Photoshop document) if layers contained in groups
- importing a QuickTime file created by the FORK media system also imported the disabled proxy track
- QT32Server failing in some circumstances, disabling ability to use some QuickTime features
- some exported AVC-I files didn’t include appropriate drop-frame timecode information, so appeared with non-drop-frame timecode
- closed captioning metadata was being set incorrectly
- many other fixes in Mercury Transmit and in plug-in SDK, fixing issues with AJA, BlackMagic, Matrox, and other third-party I/O systems for video monitoring, tape capture, and exporting to tape
- various fixes to FCP XML import and export
- crash when removing some effects using Remove Effects command
- crash during OMF export in some circumstances
- crash on Mac OSX when computer wakes from sleep
- various fixes for other crashes
- various performance and stability improvements for CUDA and OpenCL processing