EVS AVID TOOLS 4.06 Release Note

Transcription

1 EVS AVID TOOLS 4.06 Release Note April 2015 / 1.0 Corporate North & Latin America Asia & Pacific Other regional offices Headquarters Headquarters Headquarters Available at

2 EVS COMPLIANCE MATRIX... 3 MULTICAM... 3 INGEST WORKFLOWS (EVS TO AVID)... 3 AVID COMPLIANCE MATRIX... 4 VERSIONS BEFORE AVID INTERPLAY VERSIONS AFTER AVID INTERPLAY NEW FEATURES... 5 EVS AVID DHM INTEGRATION (SEND TO PLAY BACK)... 5 NEW EVS AVID FTP SERVER SOFTWARE INCLUDED IN THE EVS AVID TOOLS... 6 DOCUMENTS... 6 LICENSE... 7 PREREQUISITE INFRASTRUCTURE... 7 WHERE INSTALL EVS AVID FTP SERVER?... 7 LIMITATION... 7 BUGS CORRECTION SINCE EVS AVID TOOLS V KNOWN BUGS & LIMITATIONS... 8 ADDITIONAL NOTES & LIMITATIONS... 9 TMCLIENT.INI... 9 AVID INTERPLAY URI... 9 TRANSFER ENGINE ON WINDOWS 7 64 BITS ACFPLUGINHOST.DLL AVID MEDIA CHECKED AS RESERVED SEQUENCE NAME AS CLIP NAME File name EVS_Avid_ReleaseNote_v4.06.docx Page 2 of 10 2 of 10

3 EVS COMPLIANCE MATRIX MULTICAM Multicam 14 Multicam Multicam Multicam Xsquare and IPDirector are not linked to the EVS Avid Tools versions Please contact for more information. INGEST WORKFLOWS (EVS TO AVID) The ingest workflows through Avid Transfer Engine are no longer supported by the new EVS Avid tools 4.x. We strongly recommend using OPAtom file writing and the Avid Webservices API or the AAF generation for all ingest workflows (EVS to Avid). File name EVS_Avid_ReleaseNote_v4.06.docx Page 3 of 10 3 of 10

4 AVID COMPLIANCE MATRIX VERSIONS BEFORE AVID INTERPLAY 2.2 Old versions of Avid Interplay before the version 2.2 must be used with the EVS Avid Tools (November 2010) VERSIONS AFTER AVID INTERPLAY 2.2 Not tested anymore o Interplay v2.2 (TM v2.2/2.2.1/ ) o Interplay v2.3 (TM v or + only) o Interplay v2.4 (TM v2.4) o Interplay v2.5 (TM v2.5) o Interplay v2.6 (TM v2.6/2.7) o Interplay v2.7 (TM v2.7.0 but not the v ) Fully validated with the EVS Avid tools 4.6 o Interplay v2.7.5 (TM v2.7.5) o Interplay v3.0 (TM v3.0) o Interplay v3.1 (TM v3.1) o Interplay v3.2 (TM v3.2) File name EVS_Avid_ReleaseNote_v4.06.docx Page 4 of 10 4 of 10

5 NEW FEATURES EVS AVID DHM INTEGRATION (SEND TO PLAY BACK) Support of the Avid Interplay Transfer 3.2 (TM 3.2) ( The Avid Transfer Engine Client 64 bits must be installed with Only one setup (EVSAvidTools_Setup_4.x.x.exe) for all the Avid Transfer Engine version. File name EVS_Avid_ReleaseNote_v4.06.docx Page 5 of 10 5 of 10

6 NEW EVS AVID FTP SERVER SOFTWARE INCLUDED IN THE EVS AVID TOOLS The EVS Avid FTP Server allows XDCAM workflow from Avid to EVS with metadata. Thank to these exchange of metadata: it is possible to create IPD placeholder workflow DOCUMENTS File name EVS_Avid_ReleaseNote_v4.06.docx Page 6 of 10 6 of 10

7 LICENSE EVS_Avid_FTPServer_configman_1_0.pdf: user manual which explain who configure the EVS Avid FTP Server The EVS Avid FTP Server is protect by a new XSecure KEY: 240 EVS Avid Ftp Server PREREQUISITE INFRASTRUCTURE Windows 7 (32bits or 64bits) or Windows 2008 Server with.net 4.5 EVS Xsquare version 3.0 or upper EVS Multicam or upper Avid Interplay 3.0 or upper Avid Transfer Engine 3.0 or upper with FTP License Avid MediaComposer 7 or upper WHERE INSTALL EVS AVID FTP SERVER? To optimize the transfer: the EVS Avid FTP Server must be installed on the same computer that the temporary storage Avid TM XTAccess 3U Temporary storage XT3 Storage bandwidth depends on the number of transfer needed at the same time (at least 150Mbits per media transfer) Storage capacity depends on the sequence size We recommend using 3U EVS platform (ex: XTAccess 3U,IPD 3U,XF3 3U) with internal storage Raid 5. This storage can manage easily 6 XDCAM transfers at the same time LIMITATION The Avid XDcam Sequence must render completely localy or on the AVD STP Encode before the Avid TM FTP Transfert The Avid FTP Server is design for the XDCAM workflow but it can also work with Intra Codec BUGS CORRECTION SINCE EVS AVID TOOLS V4.01 File name EVS_Avid_ReleaseNote_v4.06.docx Page 7 of 10 7 of 10

8 There is no significant correction of bugs in this version KNOWN BUGS & LIMITATIONS The ingest workflows through Avid Transfer Engine are no longer supported by the new EVS Avid tools 4.x. We strongly recommend using OPAtom file writing and the Avid Webservices API or the AAF generation for all ingest workflows (EVS to Avid). The Avid Transfer Engine Client 32 bits must be installed with the EVS Avid Tools which are compatible with the Avid Interplay before the version 3.1 (2.2,2.3,2.3,2.5,2.6,2.7,3.0) The Avid Transfer Engine Client 64 bits must be installed with the EVS Avid Tools which are compatible with the Avid Interplay version 3.1 and after. The SendToPlayBack interface must also be installed on a Windows 64 bits. Windows XP is not supported anymore The STBP server creates the MXF OP1A files (in shared drive mode) slower than EVS MXF files The export of the Avid locators through the EVS Send To Play Back doesn t work with the version and of the Avid Transfer Engine Super Motion, 1080p dual EVS and 3D formats are not supported # 1384 : Invalid characters : Invalid characters for writing a Windows names are not supported in EVS Avid Playback server. This limitation concerns either the Avid sequence name or the TAPE ID following the option selected for clip name. # 1697 : XT server is full : no error message is generated by EVS Avid Playback Server. Missing frame : In Interplay versions, the transfer of fps files (IMX-D10 and Avid DNxHD codecs) is complete but Media Composer does not display the last frame (Push mode only). Workaround: add guard bands to the clip before transfer. File name EVS_Avid_ReleaseNote_v4.06.docx Page 8 of 10 8 of 10

9 ADDITIONAL NOTES & LIMITATIONS TMCLIENT.INI For the Transfer Engine before 2.2: the TMCLient.ini file must be in the EVS Application folder For the Transfer Engine 2.2: the TMClient.ini file for the EVS Application (XTAccess, XFile, EVS Avid Browser) must be located in these folders: Windows Vista and Windows 7: %ALLUSERSPROFILE%\Avid\tmclient.ini Windows XP and Windows Server 2003: Next to the EVS Application process For the Transfer Engine 2.3, 2.4,2.5,2.6,2.7, 3.0, 3.1 and 3.2: the TMClient.ini file for the EVS Application (XTAccess, XFile, EVS Avid Browser) must be located in these folders : Windows Vista and Windows 7: %ALLUSERSPROFILE%\Avid\MyApp\tmclient.ini ( MyApp is the EVS process name minus the.exe extension) Windows XP and Windows Server 2003: %ALLUSERSPROFILE%\Application Data\Avid\MyApp\tmclient.ini ( MyApp is the EVS process name minus the.exe extension) %ALLUSERSPROFILE%\ is actually: "C:\Users\All Users\" for Windows Vista et Windows 7 "C:\Documents and settings\all Users\" for Windows XP, Server Be careful the folder can be hidden by Windows depends on your Windows Explorer settings AVID INTERPLAY URI With interplay 2.7 or upper : The medias are referenced in the Catalogs and Incoming Media/[Workspace] interplay folders and not anymore directly in the Incoming Media interplay folder File name EVS_Avid_ReleaseNote_v4.06.docx Page 9 of 10 9 of 10

10 TRANSFER ENGINE ON WINDOWS 7 64 BITS If the transfer Engine is on Windows 7 64 bits: It is necessary to install XTAccess on one different computer than the Transfer Engine Itself The UAC on the Windows 7 64 bits must be deactivated. The EVS Avid tools are compiled with the 32 bits SDK of Avid but can be used on Windows 64 bits in 32 bits mode. ACFPLUGINHOST.DLL The ACFPluginHost.dll is a dll used by Avid but not necessary for the EVS Integration. If you have some trouble during the EVS Avid Tools installation with this dll you can unlock it by disable the PlayServer (PBS) service AVID MEDIA CHECKED AS RESERVED If the media imported by EVS are reserved in the Interplay Access: This is most likely caused by the Auto Reservation setting in the Avid Interplay Administrator settings. The auto reserve feature is controlled by a setting in the Avid Interplay Administrator application. 1. Launch the Avid Interplay Administrator Start->All Programs->Avid->Avid Interplay Access Utilities->Avid Interplay Administrator 2. Under Application Settings, select Application Database Settings 3. Under the Edit Settings tab, scroll down to the bottom of the window 4. Enter 0 for the Auto Reservation Duration SEQUENCE NAME AS CLIP NAME Since Interplay Transfer Engine version 2.1 : The MediaComposer adds transfer to the sequence name during the transfer: so if you have selected Clip Name Use Sequence Name option in the send to play back: the clip name on the EVS side will be also ended by transfer. File name EVS_Avid_ReleaseNote_v4.06.docx Page 10 of of 10