Quelles sont les nouveautés de la version 2.7.5 ?
Puis-je dès aujourd'hui updater mon Media Composer Adrenaline en version 2.7.5 ?
Puis-je updater mon adrenaline 1.x en 2.7.5 en court de production ?
Qui bénéficie de cet upgrade ?
Je ne suis pas sous contrat, comment faire pour bénéficier de cette upgrade ?
Où puis-je télécharger la dernière version logicielle ?
Le service technique de CTM m’a communiqué un lien pour télécharger la dernière version logicielle, mais je souhaiterai obtenir les CDs de cette version, est ce possible?
J’ai téléchargé la dernière version logicielle, mais je souhaiterai une intervention de l’équipe technique de CTM pour l’installation et la configuration de ma station Avid, est ce gratuit ?

Extraits des nouvelles fonctionnalités de la version 2.7.0 (voir release 2.7.5) :

Nouveautés de la 2.7.5 :

Fixed in v2.7.5
A compatibility issue was fixed in this release. No user functionality was affected. This editing application has been qualified in an Avid Interplay™ 1.1.5 environment.

Changed in v2.7.4
The following additions or changes have been incorporated into this release of the editing application.
Avid Interplay Support
Avid has qualified the editing applications in an Avid Interplay™ 1.1.4 environment.
QuickTime Support
Avid has qualified QuickTime® 7.2 with the editing applications.
Mac OS 10.4.10 Support
Avid has qualified the Macintosh OS v10.4.10 with the editing applications.

Fixed in v2.7.4
The following have been fixed: Audio
* Consolidating audio-only sequences might not have generated any new media, and consolidating any sequence might have skipped all audio. This has been fixed.
* If you had two MXF audio clips adjacent in the Timeline and you exported the sequence as a QuickTime reference file, the first MXF audio file might have been silent when you played the sequence in QuickTime. This has been fixed.
* Previously, audio may have been out of phase on playback and digital cut. This has been fixed.
* HD ancillary timecode was causing HD embedded audio to disappear during playback. This has been fixed.

If you were using desktop play delay with monitored audio or audio-only clips or sequences, the blue position bar might have jumped forward at the start of play. This has been fixed by having the system ignore the play delay for monitored audio or audio-only clips or sequences.
* Audio Project settings changes might not have carried over to a new editing session. For this release, you can decide if you want to be able to save all audio-related settings as Site
settings. Audio-related settings include Audio Settings, Audio Project settings, and Passthrough Mix Tool settings. To save audio-related settings as Site settings:
1. Press A+S as you start your editing application.
A message box opens asking if you want to be able to save audio-related settings as Site settings.
2. Click Yes.
3. Save the audio-related settings as Site settings. For more information about saving Site settings, see the Help for your application.
The ability to save persists for subsequent editing sessions. To remove this ability, press A+S when you start the application and then click No.
Bins
* You might have seen an error message when you tried to open the Bin Fast menu. This has been fixed.
* You might have seen errors when you attempted to open bins containing master clips or sequences with alpha clips. This has been fixed.
Capture
* Capturing any footage in using the 10:1m resolution on a G5 PPC might have resulted in random white flash frames. This has been fixed.
* Advanced pulldown JFIF compressed resolution media captured through Firewire in SD progressive projects might have been shifted down. This has been fixed.
* You might have experienced a system error when you tried to enter key numbers for 1080p24 clips in a 24p NTSC project. This has been fixed.
* You might have received a BuildComposition error when trying to perform a Varicam capture. This has been fixed.

A standalone TransferManager might not have ingested media to the correct LANshare folder. This has been fixed. Compatibility
* You might have experienced your dongle expiring prematurely. This has been fixed. EDL Manager
* If you scrolled through an off line sequence created from an EDL you might have experienced system errors. This has been fixed.
* You can now open EDL Manager from within an Avid editor and select Get Current Sequence from EDL Manager without getting a DISK_FILE_NOT_FOUND error.
Effects
* Sequences that contain certain AVX 2.0 effects (Sapphire, Boris BCC) which were created and saved on one type of platform (Power Mac) can now be opened on other types of platforms (Mac Intel or Windows PC) without causing errors.
* You might have seen system errors relating to memory usage after using the application for several hours while rendering many effects and opening and closing many bins. This has been fixed.
* The memory leaks that were occurring during rendering have been fixed.
* Importing moving Alpha Mattes that were non-native size to the project, displayed as black. This has been fixed.
Import
* Your system might have hung when you tried to batch import a sequence. This has been fixed.
* (Windows only) You might have experienced a system error if you tried to set the file location in a batch import for clips that weren’t found, particularly for clips that were created on a Macintosh system. This has been fixed.
Interplay
* Previously, if a transcode failed with an STD Exception, audio files from the clip that was transcoding were deleted by the Transcode provider. This has been fixed.
* Previously, you might have received a “Cannot Import composition” error while transcoding an MPEG sequence. This has been fixed.

Previously, the headframe of a clip might not have appeared in the Interplay window. This has been fixed.
* After performing an audio punch-in on a channel other than channel 1, the voice-over clip might have appeared offline in the bin or Timeline. This has been fixed.
* OMF media drives might have taken a very long time to be scanned by your Media Indexer. This has been fixed.
* Previously, the editing application might crash if you tried to search in the Interplay Window without being logged in to Interplay. This has been fixed.
* A sequence with filler and a video mixdown that played back successfully in the editing application might have received a “Play frame error” when the sequence was loaded in Assist. This has been fixed.
* If you created two sequences with identical tape ID names that differed only by upper and lower case letters (for example, footballAug07 and FOOTBALLAug07) and then sent one after another to the Media Stream Server, the server might have replaced the first clip with the second one. Clip names on the Media Stream server are not case sensitive and the server does not notify the transfer manager that the tape ID is already in use for another clip. When sending to the Media Stream Server, the transfer manager now forces all tape IDs to lower case. If the tape ID already exists on the server, the transfer fails and you see an error message that the tape ID already exists.
* Clips that you checked into Interplay might have had missing associations and it might not have been possible to delete them. This has been fixed.
* Improvements were made to the validation process of the Media Indexer, this should improve some slowdown issues that might have occurred working on your editor workstation and Avid Interplay.
* We have fixed the issue where the Interplay database intermittently locks when logged into an editing application.
* You might have seen inconsistent online-offline status of EDL-based clips in Interplay Access. This has been fixed.
* Previously, master clips with audio gain were checking into Interplay with no sequence relatives. This has been fixed.
* In the Interplay Login dialog box, you could enter or change the Interplay user name and you should not have been able to. This has been fixed.

Exported P2 DV 25 PAL clips might have appeared with media offline when you tried to import them into an Avid editing application with Dynamic Relink set to Specific Resolution. This has been fixed.
* You might not have been able to delete certain assets from your Interplay database. This has been fixed.
* You might not have been able to restore rendered effects or titles from within the Avid editing application or from the online database (AvidWG) in Interplay Access. This has been
fixed.
* Interplay Names of folders that were opened in the Interplay window and then renamed in another Interplay application were not reflected in the Interplay window even if you refreshed the window; they sometimes caused system failures. This has been fixed. After you refresh the window, references to the directory in the tree browser as well as opened bins in the Research panel should change to the new name.
* In Interplay Access, rendered effects might have added incorrect names in the Tape Name text box. This has been fixed.
* If you tried to check an audio-only sequence from a 23.976/1080p or a 23.976/720p 23 project into Interplay, the checkin might not have been successful. This has been fixed.
* If you tried to use Media Services to transcode a master clip that contained offline media, the error message might not have clearly indicated the problem. This has been fixed.
* Sending a long sequence or several short sequences to a MediaStream server might have caused Interplay Transfer to fail. This has been fixed.
* Previously, you might have received an “Error loading workspaces” error when selecting folders. This has been fixed.
* In Interplay Assist, if you changed a shotlist and clicked the red X to close the shotlist, the changes might not have been saved. This has been fixed.
* In Interplay Assist, the Audio/Video Monitoring Window might have displayed tracks as disabled when in fact they were not. This has been fixed.
* Previously, the Interplay Transfer Engine was ignoring the catalog specified by an ingest device in the configuration. It would not create the catalog or check clips into it, if manually created. Clips were ingested and checked in, but could not be easily located via the specified catalog. This has been fixed.
* (Interplay Transcode Service) You might have received intermittent DecompStream Errors after transcoding for several hours. Transcoding reliability has been improved.

etc…. voir la release 2.7.5

Rappel Nouveautés dans la version 2.7.x (voir aussi la release)

The following additions have been made to this release:

• Disconnected Client Mode. See “Disconnecting an Avid Editing Application from the Interplay Environment” on page 50.
• Added the following procedure to the Documentation. See “Adding Locators On-the-Fly while Playing” on page 54.
• Added the following note to the documentation in the “Selecting Output and Timecode Formats for 23.976p, 24p, and 25p Projects.”
Depending on the type of project you are working with, NTSC or PAL, the system will only display output options for one format. You cannot switch from NTSC to PAL or PAL to NTSC. You can only switch from one PAL format to another PAL format or from one NTSC format to another NTSC format.
• The following note has been added to the documentation: If you mount your P2 cards as virtual drives on your Avid editing application, import clips from them, and then exit the editing application, you won't see the P2 drives the next time you open the editing application. You need to reimport the clips. For more information about mounting P2 drives, see “Mounting P2 Cards as Drives” in the Help for your editing application.
• NVIDIA® Driver Update to v91.85. See “Checking the NVIDIA Display Driver Version” on page 17.
• Avid Unity™ MediaNetwork v5.0 compatibility. See “Shared Storage Support” on page 15.
• Macintosh® OS 10.4.9 Support. Avid has qualified the Macintosh OS v10.4.9 with the editing applications.

Fixed in 2.7.5

• (Mac Only) Unmounting a drive may have resulted in an “Exception: Need to implement QualityManager on MAC” error message. This has been fixed.
• (Mac Only) You may have received an error when selecting the default file name in the General Settings dialog box. This has been fixed.
• Previously, MPEG2 transcoded resolutions may not have played back successfully. This has been fixed.
• A Firmware update for the Panasonic AG-HVX200 causes clips written to the P2 cards via “Export to Device->P2” to not be properly recognized by the P2 camera. The 4.05-00-0.00 firmware update for the Panasonic AG-HVX200/HVX202, which was released to support 16GB P2 cards, introduces a regression in the “Export to Device->P2” capability. Clips exported to P2 cards from the editing application will not be correctly recognized by the P2 camera with that firmware. A red X appears on the camera’s display in place of a thumbnail. Do not load the 4.05-00-0.00 firmware update if you use “Export to Device->P2.”
• If you made your Media Creation settings a site setting, opened a new project, and then closed it, you might have experienced Access Violation errors followed by a
“DOMAIN_COPYIN_FAILED” message. This has been fixed.
• If you attempted a digital cut of HD material that originated in SD or the reverse, you might have been prompted to transcode even though it was not necessary. This has been fixed.
• You might not have been able to use the DV 25 QuickTime® codec to export a 720×480-sized composition from Adobe® After Effects®. This has been fixed.
• At the end of a transcoded clip, you might have seen a corrupt frame. This has been fixed.
• You might have been forced to quit the editing application if you tried to unmount a workspace while on the timeline. This has been fixed.
• A “MainThreadBus” error might have occurred when lifting a clip from a complex sequence after adjusting Automation Gain. This has been fixed.
• An Assertion error might have occurred when exporting a master clip with audio as OMF_1. This has been fixed.
• If you saved a bin while a Locator comment field was active, a “MainThread Bus” or “Runtime” error might have occurred. This has been fixed.
• Stepping into HD progressive titles or Matte Keys might have caused Assertion failures. This has been fixed.
• Group clips did not ScriptSync™ if a clip had black at the head. This has been fixed.
• An ”Exception: MSM: No OFFLINE Media found” error might have occurred when attempting to link to XDCAM™ media. This has been fixed.
• (Mac Pro) Saved Marquee® .mqp titles would lose edge properties on objects or text when reopened in Marquee. This has been fixed.
• Previously, if a P2 drive was connected after launching the editor, the P2 drives did not appear when selecting Import P2 > Clip to Bin > Browse For Folder. This has been fixed. LTC output was not adjusting properly for Audio Punchin preroll. This has been fixed.
• (FilmScribe) TabbedLists or WebLists were not initially generated if you chose an audio channel. This has been fixed.
• Previously, playback of multi-layered, high definition, progressive sequences sometimes resulted in an "Exception" error, which has been fixed.
• Output as RGB did not appear properly in Adobe After Effects. This has been fixed.
• Previously, if you deleted some of the media for a clip (either video or audio) and then later tried to come back to delete the remaining media, you only had the choice to delete the master clip. This has been fixed.
• If you tried to send media from a local drive (such as your C drive) to playback, you might have seen a fatal error message. This has been fixed.
• You might have seen a white video line with Plasma Wipe effects in HD interlaced projects because the effects were being created in SD and then resized. This has been fixed.
• Effects templates saved in bins might not have seemed to have a logical sort method when they displayed in the Effects Palette. Effect templates in bins now display as alphabetically sorted in the Effect Palette and in the Quick Transitions menu.
• If you played (in Full Quality mode) progressive HD media after an SD clip in an SD project, you might have seen a green bar and strobing in the image. This has been fixed.
• Previously, you might have received Exception errors when arming the video track in the Capture tool while attempting to capture in a 16mm PAL 24p Film Rate project. This has been fixed.
• (Macintosh only) Installing certain AVX plug-ins on your system might have caused the Avid Marquee title tool to crash on startup. Avid continues to work on finding a fix for this issue. In the meantime, use the following workaround that allows you to open the Marquee title tool. This workaround turns off the scripting functionality inside Marquee.
1. Close the Avid editing application.
2. Create a text file and name it NoScripting.txt. (It does not matter what is in the text file.)
3. Ctrl + click the Avid editing application icon to access the context menu.
4. Select Show Package Contents.
5. Double-click the Contents folder
6. Double-click the PlugIns folder
7. Place the text file that you created in step 1 in the Plugins folder.

Now Marquee should launch from the editor, but you will not have the scripting functionality.
• The editing application might not have rendered AudioSuite™ effects to a workspace. This has been fixed.
• You might have seen a “Runtime” error when lifting a clip containing an Advanced Keyframe effect while the Effect Editor was open. This has been fixed.
• You might have seen an “Assertion” error when performing an XDCAM SD high-resolution batch import. This has been fixed.
• Previously, you might not have been able to capture audio in a 16mm PAL 24P video project. This has been fixed.
• (Macintosh PowerPC®) XDCAM HD long clips did not import into HD projects. This has been fixed.
• Importing XDCAM is available on the Windows® and Macintosh platforms. Please disregard any mention in our documentation that states importing XDCAM media is
available on (Windows only). The documentation text will be updated in a future release.
• If you tried to do an audio mixdown of a single audio track, you might have seen an Access Violation error and the system might have frozen. This has been fixed.
• With some of the previous NVIDIA drivers, if you created a Marquee title and tried to save it, you might have seen a “Serious Error” message. This has been fixed with the latest NVIDIA drivers, which you must install manually. See “Checking the NVIDIA Display Driver Version” on page 17.
• If you used uncompressed SD material in an HD project, you might have seen corruption on line 21. This has been fixed.
• With an Avid Mojo® attached, connecting a blackburst after you have opened a PAL project could cause jittery playback. Workaround: Connect the PAL blackburst before you open the project, reopen the project with the blackburst attached, or change the resolution (Draft to Full quality or the reverse).
• The Video Input tool and Video Output tool are now available from the Tools Menu.
• You can now mount a new tape in an Ikegami® NLTEK drive and have the Media Indexer recognize it, and the Manual Storage Scan command in the Avid editing application now points to the correct folder on the drive.
• Occasionally, access violations occurred when trying to Post to Web. This has been fixed. (Interplay) Choosing Undo (Ctrl + Z) after performing an “Update Bin from Interplay” operation caused the application to crash. This has been fixed.
• (Interplay™) Previously, transcoded media did not show up online unless you restarted the editing application. This has been fixed.
• (Interplay) Previously, imported M2T files did not check into the Unchecked In Avid Assets folder. This has been fixed.
• (Interplay) If you selected Bin > Update Bin from Interplay and then closed the dialog box by clicking the close button (the red X) without selecting any options, the bin might have updated anyway and any changes you made were lost. This has been fixed.
• (Interplay) In the Service Configuration window of the Avid Interplay Administrator, you can now log in without a password if a password was not set.
• (Interplay) Previously, you might not have been able to delete media in a bin when working with 720p 23.976 35mm media. This has been fixed.
• (Interplay) When you captured a master clip at 24 NTSC or 23.976 NTSC and checked in the clip and then checked the clip out onto another system, the clip would be 30 fps and would not load into the source monitor. This has been fixed.

New for Version Adrenaline 2.7.0 PC Mac:

Support Mac Intel OS X 10.4.8
Mac Pro 2 x Dual Core 2.66GHz Intel Xeon
MacBook Pro, Core 2 Duo notebooks, 2.16 & 2.33 GHz
iMac Core 2 Duo (standalone, pas sur Unity)
Continuité du support pour Continued support for Power Macs
Stations de travail Dual 2.0 GHz G5 et plus
1.67 GHz G4 notebooks (SD seulement)

Nouvelles fonctionnalités logicielles :
Workflow complet avec les supports XDCAM SD et HD et Panasonic P2
Avid DNxHD 36 (enfin une résolutions HD de type "off-line" peu gourmande en espace disque, avec des performances en compression/qualité bluffantes)
Support du 720p50
Scrolling Timeline
Amelioration de la stabilité.
Intégration avec Avid Interplay v1.1
A noter aussi la sortie officielle de la nouvelle version 5.7 d’Avid Xpress Studio Complete
Avid Xpress Pro v5.7
Pro Tools LE v7.3.1
Avid DVD by Sonic v5.7
Avid FX v5.7
Avid 3D v5.7

Pour l'instant, nous testons cette nouvelle version dans les locaux de CTM, nous n'avons encore que peu de retour sur l'exploitation de cette dernière. Néanmoins les premiers tests s'avèrent trsè concluant avec des grosse amélioration sur MAc OS X Intel (version fortement améliorée par rapport aux versions Mac beta Intel en test chez nous depuis quelques mois)

Pour tout complément d’information sur Avid Media Composer Adrenaline HD v2.7.5 PC ou Mac , vous pouvez vous reporter au PDF « ReadMe PC ou Mac » qui accompagne cette release (disponibles sur simple demande auprès de notre service technique 33 (0)140854500 (préciser à l'opératrice la référence UPDATE-2.7.5 pour être mis en relation avec le service technique concerné).

Rappel des ajouts de la 2.5.x & 2.6.x

Un grands nombre de fontionnalitées disponible sur PC se retrouvent désormais sur le MAC; Ces fonctionnalitées incluent:
Le Support de la HD, incluant le HDV, le DVCProHD et l'Avid DNxHD / Le Support 10-bit uncompressed SD video / Le Real-time multicam /Le Support des cartes P2 et de L'XDCAM / Le suppoort des AVX2 (plug-in AVX en qualité 16-bit). Media Composer supporte la lecture et le montage de toute les résolutions offline et online,SD et HD disponible sur MediaComposer Adrenaline HD, Les possiblitées de capture et de sortie de ces résolutions dépendent du type de DNA associé (Mojo,Mojo SDI,Adrenaline).

Lecture Plein écran sans Hardware supplémentaire
La sortie SD ou HD du moniteur source ou du moniteur composer peut etre joué en plein-écran sans hardware supplémentaires de deux manieres:
– directement depuis le moniteur de l'interface (switch l'ecran de l'interface en ecran video -Toogle screen comme autrefois…)
– sur un moniteur externe en connectant sur la 2eme sortie DVI de l'ecran informatique (en remplacment de l'ecran client)

L'intégralité des fonctions de montage ainsi que les effets disponibles sur Media Composer Adrenaline sont disponibles dans la version logiciel seul de Media Composer (inclue Paint, Blur, Pan Scan, Motion Tracking, etc.).

Possiblité de relire et de monter des medias acquis en HD non-compressé 8-bits ou 10-bits capturé par le biais d'un Avid Symphony Nitris.

Veuillez noter que cette version supporte les Macintoshs sur base PowerPC uniquement
Le support pour les Macintoshs sur base Intel Mac’s est prevues pour une future release

Import et montage des proxy MPEG 4 et des medias HD Sony XDCAM-HD, à 25 MB/s CBR, 35 MB/s CBR et 18 MB/s CBR.

-Audio Punch in 4-Cannaux / -Embedded audio en HD-SDI (nécessitte l' Adrenaline DNA la carte DNxcel) / -Tracker et stabilisation incluant SteadyGlide
Voir aussi les nouveautés intégrées dans la version précédente 2.2.6 et 2.2.7 reprises sur la 2.5, la 2.5.x et 2.5.3 2.6.1 (Fuid Morph, user profiles, Access Violation errors etc…),
INFORMATION CTM SERVICES

Puis-je dès aujourd'hui updater mon Media Composer Adrenaline en version 2.7.5 ?
La mise à jour en version Adrenaline 2.7.5 impose parfois des compléments à votre configuration de base (ex. augmentation de la RAM (3Go Minimum en 2.7.5 pour des projets en HD ou HDV), upgarde de votre carte graphique pour une carte plus puissante, etc…), mise à jour de services pack os, UN CPU puissant Minimum Mac ou PC…vérification des configurations si vous êtes sur un reseau Avid, etc… Pour savoir si votre machine peut être updatée absolument contactez notre service technique avant tout update au 33 (0)140854500 (préciser à l'opératrice la référence UPDATE-2.7.5 pour être mis en relation avec le service technique concerné). Attention, même si les machine équipées de 2go de RAM sont validées depuis Adrenaline 2.2.x, nous remarquons qu'un système équipé de 3go est réelement plus véloce.

Attention, si vous êtes équipé d'un CPU PC XW8000, veillez vous reporter à la news suivante.

Attention cependant gardez en tête que certains settings des adrenalines 2.x et 1.x ne sont pas compatibles. Il très fortement préférable d'éviter de commencer une production en 1.x et de la continuer en 2.x sans effectuer une procédure de récupération du projet bien spécifique (pour éviter tout problème de