September, 2011 Archives
Today, the Adobe Media Encoder CS5.5 (5.5.1) update was released.
If Adobe Application Manager hasn’t already told you about this, go ahead and check for new updates by choosing Help > Updates.
Ideally, you should install the updates automatically by choosing Help > Updates, but you can also directly download the update packages from the download page for Mac OS or Windows by choosing the “Adobe Media Encoder CS 5.5.1” update.
If you have difficulty with this update, please bring questions and issues to the Adobe Media Encoder forum. Don’t ask questions in the comments on this blog post, which fewer people will see.
This is also a good time to install updates for other applications, including Adobe Premiere Pro and After Effects. See this page for details. (Important: Some of these updates must be manually downloaded; they are not installed automatically by choosing choosing Help > Updates.)
bugs fixed in this update
- Adobe Media Encoder wasn’t noticing files dropped into watch folders by other computers, making use of AME across a network fail in some cases.
- The current-time indicator wasn’t updating when encoding audio files.
- Adobe Media Encoder CS5.5 wouldn’t start if Adobe Media Encoder CS5 was running.
- Media from QuickTime reference files from Avid Unity systems wasn’t imported.
- Encoding would fail if an item was added to a watch folder when encoding of another watch folder was paused.
- Incorrect timecode and codec metadata was written for AVC-Intra exports.
- Import of ProRes files with four tracks of audio from ATOMOS devices failed.
Adobe Premiere Pro CS5.5 (5.5.1) update: bug fixes, including some for Mac OSX v10.7 (Lion) compatibility
Today, the Adobe Premiere Pro CS5.5 (5.5.1) update was released.
Ideally, you should install this update by choosing Help > Updates.
However, if you need to download the update packages manually, you can do so from the download pages for Windows or Mac OS, using the “Adobe Premiere Pro CS5.5 5.5.1 update” link. You must choose the correct patcher based on your original installation type—electronic download or DVD.
If you have difficulty with this update, please bring questions and issues to the Adobe Premiere Pro forum. Don’t ask questions in the comments on this blog post, which fewer people will see.
You should also install updates for your other applications while you’re at it.
Note: If you have installed the RED Epic importer plug-in from Adobe Labs, the Premiere Pro CS5.5 (5.5.1) update will overwrite it with the built-in RED importer plug-in. To restore the functionality of the RED Epic importer, just re-install the RED Epic importer plug-in after installing the Premiere Pro CS5.5 (5.5.1) update.
There are a lot of bug fixes in this update.
Note that we were able to find and fix a lot of these problems because of the great feedback that we get through bug reports and crash reports.
Here’s list of the significant bugs fixed in this update:
- Improved playback/scrubbing performance of footage from DSLR cameras.
- Media from Avid Unity QuickTime reference files was not imported.
- XML project files created by Premiere Pro did not work with DaVinci Resolve.
- On Mac OSX v10.7 (Lion), the Universal Counting Leader was missing countdown numbers.
- On Mac OSX v10.7 (Lion), Premiere Pro would crash when quitting.
- Preview in the Capture panel was not functioning properly for HDV footage.
- Image sequences lost their frame rates.
- Edges of a clip were highlighted during transitions/dissolves when using CUDA processing.
- Projects created by importing Final Cut Pro XML projects that contain multiple mono clips would lose some audio when the project was closed and reopened.
- Exporting to a QuickTime movie using DVCPRO HD settings would not complete under some circumstances, including if an image, graphic, or synthetic element was in the sequence.
- Using CUDA-accelerated Invert effect would reposition the clip.
- Premiere Pro could not find files after changing the location of the project.
- If an After Effects composition with a background color other than black was included in a sequence and Mercury Playback GPU Acceleration was enabled, the alpha channel transparency of the composition was ignored.
- MXF files created by Premiere Pro were not readable by Sony XDCAM HD decks, Final Cut Pro, or Avid Media Composer.
- ProRes files created by an ATOMOS device with four tracks of audio were not imported correctly.
- MCC closed caption files exported from MacCaption failed to appear in the Premiere Pro Program Monitor under some conditions.
- Incorrect data was being written to XML files for AVC Intra exports.
- Opacity effects were being ignored after a second transition when CUDA processing (Mercury Playback Engine GPU Acceleration) was enabled.
- Premiere Pro would hang or crash when loading a merged clip with disabled audio channels.
- various other crashes
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, AJA, Nvidia, 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.
- On Mac OSX v10.7 (Lion), eyedroppers do not behave correctly in Premiere Pro CS5.5 with the 5.5.1 update installed.
- On Mac OSX v10.6 (Snow Leopard) and v10.7 (Lion), in Premiere Pro CS5.5 with the 5.5.1 update installed, closed captions are not shown in the correct position in the Program Monitor—and are often not visible because they are drawn offscreen. Output of closed captions is not affected; this bug only applies to preview in the Program Monitor.
- 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.)
As you may already have seen in the official press release, Adobe has just acquired technology from IRIDAS, the makers of the SpeedGrade line of color applications, as well as several other tools for the professional film and video market.
One of the major reasons that we’re excited is that we know that the Adobe team will be enriched by the addition of the IRIDAS team—with their deep knowledge of color science, light, and image processing. They’ve done a great job developing world-class products.
With the addition of this set of high-end technologies, we’re even better able to deliver on our commitment to provide video professionals with the tools that you need. Not only have we listened to your requests for better, faster, and more powerful color grading and finishing tools—but we’ve also looked ahead to the future needs of professional video, including HDR (high dynamic range) and raw video workflows.
Though we can’t comment on the details of future product versions, we can point to our history of ever-increasing integration between our applications as an indication of why we acquired these technologies. We look forward to the new workflows that may be enabled by future integration work.
How would you like to see these applications integrated? Feel free to give us feedback, either through the usual feature-request form or in comments on this blog post.
You should also come and talk with us on the new Adobe SpeedGrade forum.
Be sure to check out the official press release, which has lots of additional information, as well as some insight from Jim Guerard and Lin Sebastian Kayser. Jim has also shared some thoughts on this matter in a blog post here.