Avid has released upgrades to its Media Composer, Symphony and News Cutter software products. Media Composer 3.1, Symphony 3.1 and News Cutter 7.1 fix a variety of issues and are available as a free download for existing 3.x and 7.x customers and customers with Avid Assurance.

Below is a complete summary of changes and fixes in this new release. You can download the original PDF here

Changed in Avid Media Composer v3.1

This release includes compatibility with Pro Tools v8.0 which includes the Video Satellite feature. For information, see the Video Satellite Guide provided by Digidesign®.

Fixed in Avid Media Composer v3.1

The following have been fixed in this release.

You might have had problems checking out sequences that contained Boris effects from
Avid Interplay. The effects might have appeared unrendered. This has been fixed.

With the previous editing application releases (Media Composer v3.0, Symphony v3.0 and
NewsCutter v7.0), render times might have been slower than earlier releases. Render times
have now been improved.

The Avid Interplay Administrator limits custom metadata fields to 31 characters. Previous
releases did not limit the custom metadata fields. Therefore, you might have received
“Exception, ATTR_INVALID_NAME” errors when trying to restore archived media that
did contain custom metadata fields longer than 31 characters. The restore process now
allows you to access the archived media and the metadata is truncated to 31 characters.

Previously, advanced keyframes might not have been deleted from the Record window even
if they had been deleted from the Advanced Keyframe editor. This may have occurred
intermittently. This has been fixed.

(Macintosh) Previously, you might have received assertion or bus errors when consolidating
MXF media or performing an AAF export. This has been fixed.

Previously, the memory usage would climb when opening the Advanced Keyframe
parameter graph and switching from one clip to another. This has been fixed.

Reverse play was not working properly when in MultiCamera mode. This has been fixed.

When in Effects Mode, if you dragged a wire frame, you might have experienced low
memory conditions. This has been fixed.

Previously, memory reporting was incorrect on the Macintosh. This has been fixed.

EDL Manager might have crashed when trying to create events from clips containing motion
effects. This has been fixed.

FilmScribe XML data stored in master clips was not appearing in lists following an
Autosync. This has been fixed.

You might have received an overrun error when creating an Assemble Weblist while Pullin
Source was enabled in FilmScribe. This has been fixed.

(Macintosh) You might have received a DISK_FILE_NOT_FOUND error when attempting
to create a WebList with FilmScribe. This occurs if you have an illegal character in the
sequence name. You will now receive an error message indicating you have an illegal
character in the sequence name and advising you to rename the sequence title in the CutList
or ChangeList tool.

You might have received a “MainThread” error when attempting to open a bin containing
23.976 footage in FilmScribe. This has been fixed.

FilmScribe was creating lists with missing data. This has been fixed.

You might have experienced a memory leak when using MultiCamera mode with editing
applications using Nitris DX. You might have also experienced memory leaks with Software
only editors or editing applications using Adrenaline.

(Macintosh) You might have received “Segmentation fault” errors while using JKL. This has
been fixed.

QuickTime 7.4.5 and 7.5 causes washed out video if you use Motion JPEG-B, Avid
recommends that you use the Avid codecs when using these versions of QuickTime.

You can capture or import indexed media from an external drive, that was attached to a
Macintosh Power PC, without causing it to rescan and index again when you reconnect the drive to a Macintosh or Windows Intel machine or vice versa.

In 1080p24 projects running Adrenaline hardware, audio and video might have been out of
sync by 2 frames. This has been fixed.

You might have received “Rational Overflow” errors when trimming advanced keyframe
effects. This has been fixed.

Previously, deleting Matte Keys from bins left the LRELE8-A files on the Avid Unity ISIS
workspace. This has been fixed.

(Nitris and Adrenaline) Previously, you might have seen a slight vertical line down the right
side of the image from HD component output. This has been fixed.

You might have experienced audio crackle on output after toggling between 4 and 8
channels. This has been fixed.

During playback, you might have received “Overrun on transmitting Midi data” errors if a
Command 8 was turned On. This has been fixed.

You might have received “Bus Error on Main Thread” errors when performing a Dual rolling
trim. This has been fixed.

Batch Imported clips (media created from Meridien systems) might have stuttered during
playback. This has been fixed.

Exporting AAF caused errors when all tracks were selected. This has been fixed.

Performing Send To QuickTime on the Macintosh was not working properly. This has been
fixed.

Occasionally, when working with Matte key layers, parts of the motion path display would
not appear if the path was writing over itself. This has been fixed.

When using EDL Mgr: v24.05 motion effects did not conform properly. This has been fixed.

An exported QuickTime from AfterEffects may have looked aliased within the Avid editing
application. This has been fixed.

(Macintosh Power PC) You might have had distorted sound on 24-bit XDCAM audio
imports. This has been fixed.

Previously, if you double-clicked an item in the Interplay Window, the item was checked out
from Interplay. If it was a master clip that had local changes, the checked out clip was
discarded and the local clip was loaded into the monitor. If it was a sequence with local
modifications, the incoming sequence replaced the local sequence and was loaded into the
monitor. The local modifications to the sequence were lost. Now, when you select a master
clip or a sequence that has local modifications a dialog is posted that lets you choose
whether to update. If update is chosen, then the check-out will occur and the local changes
will be lost, and the updated item will be loaded into the monitor. Otherwise the local copy
of the item will be loaded into the monitor.