Abstract:
To provide consistent operation within an A/V handling system, a coordinated interface is provided to allow the transfer of data between an editing system, capable of editing video signals, and a data archive system, designed for archival purposes. The interface of the present invention takes into account the different data types native to the editing and archival applications, and provides accommodations for transcoding of data types as necessary. Further, the interface is uniquely configured to allow either system to initiate data transfers and the related transcoding operations.

Description:
BACKGROUND OF THE INVENTION 
       [0001]    This application claims the benefit of Provisional Application No. 60/787,892 filed Mar. 31, 2006. 
         [0002]    The present invention relates to a component interface within an audio/video processing system. More specifically, the invention is a method and process for providing an interface from an audio/video non-linear editing system to an external data archive system which allows the transfer of audio/video data between the two systems. The external data archive system is capable of actively transcoding the audio/video data from a plurality of editable formats native to the non-linear editing system to one of a plurality of video server or data archive formats. The inventive system interface allows a user on either the non-linear editing system or the data archive system to initiate a data transfer. 
         [0003]    Systems for the management and use of audio/visual signals typically involve many different subsystems and components, each necessary for carrying out a particular task. Unfortunately, each of the various systems are typically more efficient when a particular file format is utilized. Consequently, the coordination of various systems with one another is further complicated by these different file types. As an example, data archieve and data storage applications typically utilize a preferred format to accommodate the needs of those applications. Likewise, a second data format is often more effective for editing of audio/visual data, including various data types that may be unique to the editor itself. Further, a third data format may be more conducive for broadcast transmission purposes. Based upon these format differences, it is challenging for the various subsystems to deal with data provided in various formats. Thus interfacing between any of these subsystems is more complicated than simply providing straight forward data transfers. 
         [0004]    In addition to the different formats involved, audio/visual information typically includes tremendous amounts of data. Broadcast quality audio/visual signals are made up of very complex data structures, thus their processing and management is further complicated by the sheer size of data files involved. The tasks of processing the data typically requires considerable resources, and can become very involved. Thus, it is often desirable to encode data files whenever possible. 
       BRIEF SUMMARY OF THE INVENTION 
       [0005]    To accommodate the interaction between a various subsystems within a audio/visual data management system, the present invention provides an interface to effectively allow data transfer. More specifically, to allow interaction between a non-linear editing system, and a data archive system, the present invention provides interface accommodations which addresses the different data formats encountered. To achieve this interface, components within an audio-visual editing suite, and a data storage system are provided which recognize the differences in data formats typically utilized, and provides the ability and communication tools to efficiently provide an interface between those two components. 
         [0006]    Within the non-linear suite, utilized by the present invention, a transfer manager is included. Traditionally, this transfer manager is capable of managing transfers of audio/visual files to a video server, from internal storage. The transfer manager of the present invention, however, coordinates with a transfer server within a data archiving system. The data archiving system can then help to coordinate transfer of data to the video server as needed. 
         [0007]    To achieve the above coordination and management of data transfers, the data archiving system includes the transfer server, along with a transcoding engine. The transcoding engine provides the archive system with the capability to transcode audio/visual data between the various formats that may be most appropriate for archiving and/or editing. 
         [0008]    The present invention further includes processes for the transfer and manipulation of data which can be initiated by either a video editor, or a data archive system. Within these processes, the editor&#39;s transfer manager, and the data archive system&#39;s transfer server, both coordinate with one another to achieve the necessary transfers. Further, the transcoding engine of the data archive system is called upon to perform whatever conversions are necessary. Once the appropriate adjustments or conversions are made, signals can then be sent to the component making the request, in a most desirable format. 
     
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         [0009]    Further objects and advantages of the present invention can be seen from reading the following detailed description, in conjunction with the drawings in which; 
           [0010]      FIG. 1  is a block diagram illustrating a traditional non-linear editing suite; 
           [0011]      FIG. 2  is a block diagram illustrating the interface of the present invention between the non-linear editing suite and data archive system; 
           [0012]      FIG. 3  is a flow chart illustrating the steps taken when the editing system wishes to retrieve information; and 
           [0013]      FIG. 4  is a flow chart which illustrates the steps taken when the data archive system requests information from the editing system. 
       
    
    
     DETAILED DESCRIPTION OF THE INVENTION 
       [0014]    Referring now to  FIG. 1 , the major components of an audio/video Non-Linear Editing (NLE) suite  10  are illustrated schematically. The editing suite is composed of an audio/video editor  12 , a transfer manager  14  and system storage  16 . Transfer manager  14  controls the transfer of audio/video data from the editor to system storage and from system storage to external video servers(s)  16 . Transfer manager  14  is an existing component of an NLE system and includes software processes and protocols which govern the exporting and importing of audio/video data into and out of external storage locations such as video server(s)  20 . 
         [0015]      FIG. 2  is a block diagram illustrating the integration of the NLE suite with an external Data Archive System  30  (DAS) which allows the passing of audio/video data from the NLE suite to the DAS for storage and subsequent retrieval. DAS  30  contains a system core  32 , a transfer server  34 , a transcoding engine  36  and storage  38 . The NLE transfer manager  14  communicates with DAS transfer server  34  to initiate the data transfer process. Transfer server  34  in turn communicates with DAS system core  32  and obtains access to transcoding engine  36  for receiving and processing data received from NLE storage  14 . The audio/video data generated and stored within the NLE suite is typically stored in an editing format which may not be compatible with video server formats or data archive formats. Transcoding engine  36  transcodes editable format to playout format and vice-versa as needed. 
         [0016]    In a preferred embodiment the inventive method of integrating an NLE with a DAS is used to integrate an Avid editing suite sold by Avid Technology Inc. with a MassStore data archive system manufactured and sold by the applicant. The Avid editing suite includes a specification for importing and exporting data called Avid Dynamic Handle Module (DHM) which defines the specification for ingesting data into Avid (copy-out from the point of view of MassStore) and for playback (copy-in from the point of view of MassStore). Avid DHM specifies protocols and Dynamic Link Libraries (DLL) that must be implemented by third party applications to integrate their operation with the Avid editing suite. 
         [0017]      FIG. 3  is a flowchart which illustrates the sequence of steps that are followed by the inventive interface when a user of an Avid editing system wishes to playback audio/video content from Avid to a MassStore data archive. The process starts when at step  50  when an NLE user initiates a playback session. In the next step  52 , the request for playback is forwarded to NLE Transfer Manager  16  which then communicates with DAS Transfer Server  34  to get the DAS Playback DHM DLL in step  54 . The NLE Transfer Manager then initiates the playback process using the DAS Playback DHM DLL in step  56 . In the preferred embodiment, the first four steps  50 - 56  described above are native to the Avid system while the remaining steps described below are native to the MassStore system. Step  56  is followed by step  58  in which the DAS DLL connects to the DAS to initiate the copy-in process. In step  60  the DAS DLL obtains archive format parameters and gains access to a Transcode Streaming Service hosted by the Transcode Engine module  36  of the DAS. The Transcode Streaming Service converts the format of the data from an editing format to a playout format and vice versa as needed. In step  62  the DAS starts the copy-in process and in step  64  the DAS playback DLL creates a playback transcoding session thereby readying both systems for the flow of data from the NLE to the DAS (step  66 ). Finally when the data transfer is complete, signals are sent to the NLE Transfer Manager and the DAS Transfer Server to end the playback session in step  68 . 
         [0018]      FIG. 4  is a flowchart similar to  FIG. 3  which shows the sequence of steps that are followed when a user of the MassStore data archive initiates a playback of audio/video content from Avid to a MassStore storage device. The process starts with a DAS user initiating a playback session at step  70  followed by step  72  where the DAS starts the copy-in (Avid playback) process. In the next step  74  the DAS initiates a playback session in the NLE Transfer Manager by calling the Transfer Manager Automation (TMAuto) DLL which allows the DAS to remotely control the NLE Transfer Manager. Once the NLE Transfer Manager is activated, the DAS waits for a second copy-in request from the NLE Transfer Manager in step  76 , followed by a transfer of the DAS playback DHM DLL to NLE Transfer Manager in step  78 . Similarly to process described in  FIG. 3 , the initial steps  70 - 78  described above are native to the Avid system while the remaining steps described below are implemented on the MassStore system. In step  80  the DAS playback DLL connects to the DAS to initiate the copy-in process followed by the DAS playback DLL obtaining a transcode streaming service from Transcoding Engine  36  in step  82 . The DAS playback DLL creates a transcoding session in step  84  which leads to the flow of data in step  86  from the NLE to DAS storage. Finally in step  88  signals are sent ending the playback session when the data transfer is complete. 
         [0019]    The inventive interface allows users on both a non-linear editing system and a data archive system to initiate the transfer of data from one system to the other and the automatic transcoding of data provides seamless data transfer regardless of the format the data is stored in. A further advantage of the inventive interface is that it allows NLE users to store audio/video content indefinitely on data archive storage devices such as disk cache or tape libraries which are typically less expensive that NLE or video server storage. From data archive storage the NLE produced content can be converted or transcoded to a playback server or other environment on demand. Yet another advantage of the inventive interface is that it allows NLE users to easily playback and view content using data archive hardware which is less expensive than video servers.