Log InCreate An Account
  1. News
  2. »
  3. Audio Software & Plugin Hosts
  4. »
  5. Adobe

Adobe updates Premiere Pro CS6 to v6.0.1


Adobe has updated Premiere Pro CS6 to version 6.0.1.

Features added or changed:

  • Improved performance using OpenCL, especially when used on Mac OS X v10.7.4 or later. For details of GPU acceleration in Premiere Pro, see this page. For details of OpenCL features in Premiere Pro CS6, see this page.
  • Added encoding presets with additional bit-rate settings for XDCAM HD.
  • Added Automatic Peak File Generation preference in the Audio category for turning off automatic peak file generation for imported audio. By default, this preference is enabled and matches the behavior of Premiere Pro CS6 (6.0.0). When this preference is disabled, importing audio or opening projects will not cause peak files to be generated. If peak files were already generated, then waveforms will be visible. Files imported before the preference was disabled will continue to generate peak files.
  • Enabled "smart rendering" and added Enable Smart Rendering Codec setting to the Video tab of the MXF OP1a exporters for XDCAM HD and XDCAM EX to enable or disable smart rendering for these formats. This option defaults to the off/disabled state.

Bugs fixed:

  • Start timecode was not imported or exported correctly when working with AAF files.
  • Some files from the Canon 5D Mark III camera were imported with the wrong timecode.
  • Playing/viewing waveforms in the Source Monitor caused audio dropouts with some XDCAM HD clips.
  • NTSC MXF OP1a files that were exported with drop-frame timecode had video data that was tagged as non-drop-frame.
  • Switching the Renderer project setting from Mercury Playback Engine Software Only to Mercury Playback Acceleration GPU Acceleration on a computer using OpenCL caused Premiere Pro to crash under some circumstances. Switching between the two settings on a computer using CUDA would in some cases cause problems with video and/or audio playback.
  • Crash when using full-screen, cinema mode on some computer systems.
  • Tape capture was not working correctly with some third-party systems.
  • Crash when capturing from tape using some BlackMagic hardware.
  • An extra, black frame was included at the end of the output when exporting to P2 MXF in some circumstances.
  • First two frames were being played twice on external monitor using Matrox MXO2.
  • Crash when using "hover scrub" with Matrox MXO2.
  • Audio/video synchronization was off by a few frames when playing video on external monitor.
  • The Export Frame button was not exporting the correct frame, instead exporting a frame one or two frames away from the current frame.
  • Some audio files and some MXF files would go offline or have their audio reconformed when the project was re-opened or when Premiere Pro was minimized or lost focus.
  • Crash when modifying an effect property while playback was occurring.
  • Hang/freeze when using a dissolve transition on an adjustment layer.
  • Dropped frames and audio/video synchronization issues when exporting to tape using some third-party hardware.
  • Information about dropped frames on output to tape was not accessible to third-party systems.
  • Some QuickTime files were imported with the wrong field order.
  • When audio was sent through a Mercury Transmit plug-in, any number of channels that was not 2 or 6 was treated as mono.
  • In HDV editing mode, File > Export > Tape could not be used with third-party hardware.
  • The current-time indicator (playhead) was not returning to the current time after using the Play Around command.
  • Last several frames of output when exporting to tape were black.
  • When encoding a 23.976 fps video to H.264, the duration of the video in the output .m4v file was too short, and audio drifted out of synchronization with the video.
  • Transparency (alpha channel) information from a dynamically linked After Effects composition was rendered incorrectly in Premiere Pro.
  • Importing some QuickTime OP1a files caused Premiere Pro to hang.
  • The duration of the audio track sent to SpeedGrade using the Send To SpeedGrade command was the length of the entire Premiere Pro sequence, not the length of the work area.
  • Timecode written to trimmed clips using the Project Manager did not match the source timecode for some QuickTime files.
  • Various other crashes.


Discussion: Active

Please log in to join the discussion

News & Deals Related To This Item

Show more...