Avid Mediacomposer / Symphony upgrade: V 3.5.4

Bugfixing

AMA

• If you are connected to an Avid Unity, AMA clips will no longer highlight yellow when the clips are taken offline.

• P2 AMA import: On some projects such as 1080i59, the editor was not able to consolidate or transcode from spanned P2 cards. This has been fixed.

• If you applied an AudioSuite Plug-in to an XDCAM EXclip linked through AMA, the system froze when you rendered. This has been fixed.

• You can successfully eject an XDCAM disc when you have clips loaded in a bin. However, when linking XDCAM clips from an optical disk, Avid recommends you do not display the bin in Frame view or Script view due to performance problems. If you have problems ejecting a disk, clear any clips loaded in a monitor.

• You should now be able to view P2 locators through AMA that have no text associated with them.

• Switching cards among slots in the P2 card reader should not cause errors when linking clips through AMA.

• If you change the User Clip Name in the P2 Viewer or from a Panasonic camera, the Avid editor updates the Name column and User Clip Name column with the new name through the AMA method. Note: If you change the User Clip Name in the P2's Metadata Upload dialog box, make sure to save the change to the MXF file as well.

• If you use an XDCAM EX SxS card, and you render an effect through the Effect Source Drive dialog box, the rendered clip is saved to the hard drive (system), not to the SxS card.

• The amount of space needed when you consolidate an AMA clip and attempt to change the audio sample rate, should display the correct amount.

• You should be able to export to XDCAM when AMA is enabled.

• You should be able to hear the audio for tracks A3 and A4 (and beyond) when you play XDCAM or XDCAM EX clips linked through AMA.

• When Enabling Dynamic Relink, the system should not remove the yellow highlight of the linked AMA clips.

• You should not receive an exception error when you play an AMA XDCAM IMX clip.

Audio

• Audio was silent when scrubbing over a locator or IN point using the Keyboard arrow keys. This has been fixed.

• When Audio Punch In was stopped using the space bar, the application froze for about 30 seconds. This has been fixed.

• The Audio Punch In workflow was different between Adrenaline and Nitris DX. For example, when attached to Adrenaline, if you had the Audio Tool open and set to the incoming signal, and then scrubbed through the audio you could hear the audio tracks in the Timeline. When performing the same with a Nitris DX, you could not hear the Timeline audio tracks. With Nitris DX, you can now hear the Timeline audio tracks.

• The editing application might have crashed after applying Automation Gain to an MP2 clip. This has been fixed.

• Previously, you might have received an “Invalid Path” error if you enabled the audio waveform Sample Plot. This has been fixed.

• You might have heard audio pops, clicks or artifacts with rendered and unrendered dissolves on MP2 audio clips. This has been fixed.

• Audio digitized in a 23p film project would not relink occasionally. This has been fixed.

Capture

• You might have received an “Assertion Failed Could not initialize Player” error after capturing or importing clips. This has been fixed.

Compatibility

• Previously, the Arabic language text justification was not retained if a clip was opened and modified (for example, a locator added) by another user. This has been fixed.

• Previously, the editing applications did not install correctly on Windows Vista 64-bit operating systems unless you edited the Common Files folder path. This has been fixed.

Digital cut

• (Macintosh) You might have received an “Assertion Failed RealConsumer” error when performing a Digital Cut preview. This has been fixed

EDL

• When trying to export an edl, EDL Manager displayed an “assertion failed” error. This occurred if there were more than 255 sources. This has been fixed.

• Locator timecode was not displayed accurately in EDL. This has been fixed.

Effects

• Previously, when editing a sequence with a Sapphire effect, you might have received an “Assertion failed” or “spring buffer timeout” error. This has been fixed.

• You might have received Bus Errors when applying an AudioSuite effect to a group clip. This has been fixed.

• Dragging a Color Correction template from a bin to a bucket did not apply the template to the bucket. This has been fixed.

• AAF could not conform Pan and Scan correctly. This has been fixed.

• Previously, you might have experienced noticeable delays when editing a clip from the Source monitor into a sequence and adding effects or an Add Edit. This has been fixed.

• Applying a Timecode effect on multiple tracks did not show on V1 when parked on a frame in a film project. This has been fixed.

Film

• (FilmScribe) Previously, a “Film Type” option did not appear as a display choice in lists. This has been fixed.

• When working with a 16mm film project, the feet and frames displayed in the Center Duration was inaccurate. This has been fixed.

Import

• You might have received a memory leak error on checkout or when performing an AAF import. This has been fixed.

Interplay

• Previously, clips in sequences would lose Pan data after being checked in and checked out of Interplay. This has been fixed.

• When opening a sequence in the Interplay Window, you might have received the message “The item you are loading into a monitor has been modified locally” even if the item was not modified. This has been fixed.

• Previously, you might have experienced intermittent “Access Violation” errors while setting the Interplay Folder settings in the editor for a new project. This has been fixed.

• Occasionally, using the Interplay Window would cause a“freed object” error or an “access violation” error. This has been fixed.

• Previously, you might have receive an “error writing properties to Asset Manager” error when trying to check-in material to Avid Interplay. This has been fixed.

• Previously, site settings for Dynamic Relink were not sticking. This has been fixed.

Play

• (Adrenaline and Mojo SDI) Previously, when scrubbing in the Timeline, the blue bar would move, pause, move, pause, etc. This has been fixed.

• In an 1080p/25 XDCAM project, if you trimmed a clip in the timeline, you might have received an Access violation. This has been fixed.

• Previously, you might have experienced noticeable delays when editing a clip from the Source monitor into a sequence and adding effects or an Add Edit. This has been fixed.

• Previously, if you added a Source Tape color correction to a shot in the timeline, not all shots in the timeline that come from the same source tape reflected the changes. This has been fixed.

• Send to Playback failed if the sequence name contained an illegal character. This has been fixed.

• Previously, for an HD long GOP sequence, if the sequence name or tape id contained a non-English character, Send to Playback would result in a “Server not responding” error. This has been fixed.

• When sending a sequence that contained IN and OUT points to playout to AirSpeed, only partial audio played. This has been fixed.

• Previously, you might have received “Segmentation Fault” errors when playing MP2 clips. This has been fixed.

• Sequences with IN and OUT points contained partial audio when sent to playout from AirSpeed Multi Stream. This has been fixed.

• Previously, Send To Playback failed if the sequence ontained a MetaSync track. This has been fixed.

• Occasionally edits of MPEG50 material would not play properly. For example, in Trim mode, outgoing material would play in place of incoming material. This has been fixed.

Settings

• Previously, if you made a change to the project type or the raster type, the Genlock setting in the Video Output tool would change to the application default settings. Now if you make a change to the project type or the raster type, the Genlock setting is retained.

ScriptSync

• Performance of the ScriptSync feature was slower in the previous editor release. This has been fixed.

• Performing ScriptSync on a subclip resulted in a “PMS_RESTART_OUT_OF_RANGE” error. This has been fixed.

Titles

• Previously, if you added a crop to a title, the opacity would darken. This has been fixed.

Avid Unity

• You might have experienced extreme slowness when opening and closing bins or projects when working in an Avid Unity Media Network environment. Performance has been improved.