JP2008219908A - Information processing apparatus and method, and program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide an information processing apparatus capable of enhancing the convenience of data by easily carrying out edit processing and confirmation processing of data or the like. <P>SOLUTION: A unique material identifier (UMID) of each of source data 452 is attached to a configuration table 451, and its own UMID is attached to each of the source data 452, and the UMID of the configuration table 451 and the UMID of each of the source data 452 are attached to an edit list 453; and an effect-attached editing list 454 is attached with the UMIDs of the source data 452 and the UMID of the original edit list 453, and each terminal traces the UMIDs to reference other data. Further, a metadata server generates and manages a reverse cross-reference table for the UMIDs and each terminal utilizes the table to reference the data. The information processing apparatus or the like is applicable to, for example, network systems. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to an information processing apparatus and method, and a program, and in particular, can improve the convenience of data, for example, by enabling easy data editing processing and confirmation processing. The present invention relates to an information processing apparatus and method, and a program.

  For example, in the production of television programs, a scenario (script) is first created in order to perform a series of operations in a planned, efficient and accurate manner, and interviews are conducted based on the scenario. Material data such as image data and audio data is created, and the material data is edited and joined, subtitles are synthesized, music is inserted, and the completed data (campaign) is created as a program .

  In such program production work, conventionally, various data such as scenarios, material data, and campaigns have been created as different data and managed individually.

  For example, a scenario is printed on paper and created as a book (script), and image data and audio data (material data) created by the coverage are created as independent data for each coverage and are different media ( For example, the campaign is newly created as data different from the material data, and recorded as a shipment on a medium (for example, video tape) different from the medium on which the material data is recorded.

  In such a program production work, it is necessary to share data among a plurality of people. For this reason, for example, when an operator edits material data, a still image (editing screen) of a scene that becomes a key for editing And the time code corresponding to the captured editing screen is registered in the server as a web page, and the server provides the web page to the terminal device as a so-called bulletin board, and the editing screen specified by the terminal device is There is a method of providing to a terminal device. The provided editing screen includes a time code corresponding to the editing screen, and the user of the terminal device can determine which part of the material data the still image is based on the time code. (For example, refer to Patent Document 1).

JP 2001-290731 A

  However, in the above method, the position of the previously registered editing screen can be grasped for one material data, but other related data cannot be referred to as described above. That is, in the method as described above, when the data to be referred to is specified by the user, the reference position can be searched based on the registered information. For example, the search for material data before editing (material data generated by the interview) and scenarios used to create the campaign is performed from the campaign. There was a problem that it was difficult to do.

  For example, when an editor is referring to a part of a package, when the editor refers to an image of material data before editing corresponding to that part, the editor plays back the material data before editing together with the package. In addition, complicated operations such as visually searching for the same portion based on the displayed image are required.

  Similarly, when referring to a scenario corresponding to a reference of a campaign, the editor must search the corresponding part of the scenario while comparing the image of the campaign and the scenario (script). I had to.

  The same applies when other data is referenced from data other than the campaign. In the production of a program, an operator often needs to refer to other data from one data. In some cases, the worker required complicated work as described above.

  In this way, searching for material data and scenarios before editing from a campaign requires complicated work, so the editor can check whether the campaign is created according to the scenario, Not only in the case of confirmation work such as confirming the points noticed in the campaign in the material data before editing, which is the data at the time of coverage, but for example, changing the edited contents of the campaign or diverting the campaign It is also difficult to perform editing work that requires material data and scenarios before editing based on the campaign, such as creating another campaign.

  The present invention has been made in view of such a situation, and facilitates the association between data and makes it possible to easily search the other data from one data. The convenience of the data can be improved by making it possible to easily perform the confirmation process.

  According to a first aspect of the present invention, material data including partial data of a desired time code in editing data including editing contents of material data constituting content data and completed data as content data corresponding to the editing information. Identification information and specifying means for specifying a time code of the partial data in the material data; and material data acquiring means for acquiring the material data using the identification information of the material data specified by the specifying means; And an output means for outputting the partial data of the material data acquired by the material data acquisition means corresponding to the time code in the material data specified by the specifying means.

  Corresponding to the completion data using the identification information acquisition means for acquiring the identification information of the editing information using the identification information of the completion data, and the identification information of the editing information acquired by the identification information acquisition means Edit information acquisition means for acquiring edit information, the specifying means from the edit information acquired by the edit information acquisition means, identification information of the material data and a time code of the partial data in the material data Can be specified.

  Further comprising a designation receiving means for accepting designation of a desired time code in the completion data, the identification information acquiring means uses the identification information of the completion data for which designation of the time code has been accepted by the designation accepting means, The identification information of the editing information is acquired, the editing information acquisition means acquires editing information corresponding to the completed data using the identification information of the editing information, and the specifying means is determined by the editing information acquisition means. From the acquired editing information, identification information of material data including partial data of the time code designated by the designation receiving means, and a time code of the partial data in the material data can be specified.

  According to a first aspect of the present invention, the specifying unit is a part of a desired time code in the completed data as the content data corresponding to the editing information from the editing information including the editing contents of the material data constituting the content data. Identification information of material data including data, and a time code of the partial data in the material data are specified, and the material data acquisition means uses the identification information of the material data specified by the specification means, An information processing method for acquiring data and for outputting the partial data of the material data acquired by the material data acquiring unit corresponding to a time code in the material data specified by the specifying unit. .

  According to the first aspect of the present invention, the computer further comprises partial data of a desired time code in the completed data as content data corresponding to the editing information from editing information including editing contents of the material data constituting the content data. Using the identification information of the material data, the specifying means for specifying the time code of the partial data in the material data, and the material data identification information specified by the specifying means A program for causing data acquisition means to function as output means for outputting the partial data of the material data acquired by the material data acquisition means corresponding to the time code in the material data specified by the specifying means. .

  The second aspect of the present invention is the editing information corresponding to the completion data using the identification information of the completion data as the content data, the editing information including the editing contents of the material data constituting the content data. Information processing comprising: identification information acquisition means for acquiring identification information; and edit information acquisition means for acquiring edit information corresponding to the completion data using the identification information of the edit information acquired by the identification information acquisition means Device.

  The apparatus may further include material data acquisition means for acquiring the material data using identification information of the material data included in the editing information acquired by the editing information acquisition means.

  The apparatus further comprises a configuration table acquisition unit that acquires the configuration table using the identification information of the configuration table that is information related to the content data production plan included in the editing information acquired by the editing information acquisition unit. Can do.

  The edit information acquired by the edit information acquisition means further comprises determination means for determining whether or not identification information of other edit information is included, and the configuration table acquisition means is configured to determine whether the edit table includes the edit information. When it is determined that the information does not include the identification information of the other editing information, the configuration table can be acquired.

  According to a second aspect of the present invention, the identification information acquisition means is editing information corresponding to the completion data using the identification information of the completion data as content data, and the material data constituting the content data In this information processing method, the identification information of the editing information including the editing content is acquired, and the editing information acquisition means acquires the editing information corresponding to the completed data using the acquired identification information of the editing information.

  According to a second aspect of the present invention, the computer further uses editing information corresponding to the completed data, using the identification information of the completed data as content data, and the editing contents of the material data constituting the content data As identification information acquisition means for acquiring identification information of editing information including the editing information acquisition means for acquiring editing information corresponding to the completed data using the identification information of the editing information acquired by the identification information acquisition means It is a program to make it function.

  According to a third aspect of the present invention, by using identification information of a configuration table, which is information related to a plan for producing the content data, included in editing information including editing contents of material data constituting the content data, the configuration table It is an information processing apparatus provided with the structure table | surface acquisition means to acquire.

  The editing information further includes a determination unit that determines whether the editing information includes identification information of other editing information, and the configuration table acquisition unit identifies the other editing information in the editing information by the determination unit. When it is determined that no information is included, the configuration table can be acquired.

  According to a third aspect of the present invention, the composition table acquisition means is an identification of a composition table, which is information relating to a plan for producing the content data, which is included in the editing information including the editing contents of the material data constituting the content data. The configuration table is obtained using information.

  In the third aspect of the present invention, the computer further uses the identification information of the configuration table, which is information related to the production plan of the content data, included in the editing information including the editing contents of the material data constituting the content data. And a program for functioning as a configuration table acquisition means for acquiring the configuration table.

  In the first aspect of the present invention, from the editing information including the editing content of the material data constituting the content data, the material data including the partial data of the desired time code in the completed data as the content data corresponding to the editing information. The identification information and the time code of the partial data in the material data are specified, the identification information of the specified material data is used, the material data is acquired, and the partial data corresponding to the time code in the specified material data is Is output.

  In the second aspect of the present invention, identification information of completed data as content data is used, editing information corresponding to the completed data, and editing information including editing contents of material data constituting the content data. The identification information is acquired, and the editing information corresponding to the completed data is acquired using the identification information of the editing information.

  In the third aspect of the present invention, the identification information of the configuration table, which is information related to the production plan of the content data, included in the editing information including the editing content of the material data constituting the content data is used. A configuration table is obtained.

  According to the present invention, information can be processed. In particular, the convenience of data can be improved, for example, by making it possible to easily perform data editing processing and confirmation processing.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 shows a configuration example of a network system to which the present invention is applied.

  The network system 1 in FIG. 1 is a program production support system used for production of content data (Content Data) such as a television program. The production process of content data is basically classified into planning / configuration, coverage, and editing / production. Planning (composition) is a process of supervising the entire production of the video program, and is a process of creating a video program scenario (scenario) by planning and planning the video program to be produced. For example, the coverage is a process of actually performing coverage at a production site in accordance with a production instruction and a scenario, and is a process of capturing video of each scene constituting the video program and covering the shooting situation. Editing (production) is the editing of image data and audio data obtained through coverage based on production instructions and scenarios, or image data and audio data obtained through coverage, or image data compiled through editing. And other data (CG / SI (Computer Graphics / SuperImpose), narration, document video / music, etc.) that is not obtained through interviews is added to the audio data and completed data (ie, content data) ).

  These steps are basically performed by different operators. Each process is advanced by a plurality of workers. Therefore, in the following description, the entire worker who performs the work of each process will be referred to as a group as needed. For example, an entire worker who performs a planning (configuration) process is referred to as a planning group, an entire worker who performs coverage is referred to as a news gathering group, and an entire worker that performs editing (production) work is referred to as an editing group.

  The network system 1 in FIG. 1 is a program production support system that supports the work in each of these processes. The plan configuration terminal device 11 of the planning group 10, the imaging device 31 and the field PC 32 of the news gathering group 30, and the editing group Forty editing terminal devices 41 and the like are provided as terminal devices. These terminal devices are connected to the network 21 and can access each other via the network 21.

  The imaging device 31 of the news gathering group 30 is a video camera, such as a camcorder (registered trademark), for example, and is used for news news coverage for broadcasting, shooting of sports games, video content such as movies (sound) Including the acquisition of the The imaging device 31 records image data, audio data, and the like obtained by imaging a subject on a recording medium such as an optical disc such as a DVD (Digital Versatile Disc), or another device (editing) via the network 21. Terminal device 41). The imaging device 31 can also perform processing in cooperation with the field PC 32. For example, information related to imaging (for example, information such as date setting and weather conditions) is obtained from the field PC 32 and obtained. It is recorded on a recording medium or transmitted as data including image data and audio data. Conversely, it is also possible to provide information from the imaging device 31 to the field PC 32.

  The field PC 32 is configured by a portable information processing device such as a notebook personal computer or PDA, a peripheral device, and the like, and in addition to image data and audio data, their metadata and the like are shared with the imaging device 31. For example, the field PC 32 generates, for example, information that is useful during subsequent editing processing, such as information related to coverage / shooting status, based on the input of the person in charge of the coverage group 30 that is the user, and the imaging device 31. Is associated as metadata with the image data or audio data obtained in the above.

  The planning terminal device 11 and the editing terminal device 41 are each composed of an information processing device such as a personal computer and peripheral devices, and are used by an operator in each process.

  In addition, the network system 1 is connected to the network 21 and includes, for example, a material data server 51, a campaign server 52, a planning terminal device 11, an imaging device 31, a field PC 32, an editing terminal device 41, and the like as terminal devices. And a metadata server 53 is provided.

  The material data server 51 has a material data database 61. For example, material data (image data and audio data) obtained by the imaging device 31 of the news gathering group 30 is accumulated in the material data database 61, and each terminal. The material data is provided to the device.

  The campaign server 52 has a campaign database 62. For example, the campaign server 52 accumulates campaigns, which are completed data as contents (programs) created in the editing terminal device 41 of the editing group 40, in the campaign database 62. The package is provided to each terminal device.

  The metadata server 53 includes an edit description database 63, a configuration table database 64, and a metadata database 65. For example, an edit description (contents of edit contents of material data) created in the edit terminal device 41 of the edit group 40 is provided. Description) is stored in the edit description data database 63, and the edit description is provided to each terminal device, or the configuration table (plan table relating to production of content data, etc.) created in the planning terminal device 11 of the planning group 10 is provided. Is stored in the configuration table data database 64, the configuration table is provided to each terminal device, or the metadata of the material data generated in the imaging device 31 or the field PC 32 of the news gathering group 30 is This metadata database 65 stores the metadata in each terminal device. The to or provide.

  Further, the metadata server 53 has a reference relationship table 66 for managing the reference relationship of each data using a UMID (Unique Material IDentifier) as will be described later. The reference relationship information using the UMID that is the identification information for identifying the data to be supplied is managed as this reference relationship table 66, and the UMID information of the data requested by each terminal device is managed as this reference relationship. The table 66 is used.

  UMID is a standard identifier by Society of Motion Picture and Television Engineers (SMPTE), and is an identifier for uniquely identifying AV (Audio Visual) material and the like. In other words, by using UMID, material data can be identified regardless of its management location (directory). Therefore, if the correspondence between the directory where the material data is managed and UMID is managed, the target material can be identified. Data can be specified regardless of the directory.

  That is, the network system 1 in FIG. 1 uses the material data server 51, the package server 52, and the metadata server 53 as servers, and the planning terminal device 11, the imaging device 31, the field PC 32, and the editing terminal device 41 as clients. Server client system.

  The configuration table (scenario) is like a design drawing in the production of a program, and is metadata of the produced program (content data). The operation of each process is basically performed based on this configuration table. This configuration table is created by the planning group 10 using the planning terminal device 11 in the planning (configuration) process, uploaded to the metadata server 53 via the network 21, and registered and stored in the configuration table database 64. The

  The material data includes image data, audio data, and the like obtained in the imaging device 31 of the news gathering group 30, is created in the news gathering process, is uploaded to the material data server 51 via the network 21, and is registered in the material data database 61. And accumulated. The material data includes, for example, image data such as time code in the material data and information directly added to the sound data.

  The metadata is information related to the material data and related to the material data. For example, the metadata is configured by information that is useful at the time of subsequent editing processing, such as information on the date, place, or situation of coverage / photographing. The This metadata is generated, for example, in the imaging device 31 or the field PC 32 of the news gathering group 30, and is associated with the material data using, for example, UMID. Then, the metadata is uploaded to the metadata server 53 via the network 21 and registered and accumulated in the metadata database 65.

  The edit description is a description of information that is generated when the material data is edited and includes the edited content. For example, the edit description is information described in a predetermined language such as XML (eXtensible Markup Language). That is, for example, when the material data is edited (nondestructive editing) by the editing terminal device 41 of the editing group 40 in the editing process, this editing description is generated as an editing result. In other words, the editing terminal device 41 normally does not directly process the material data to be edited when editing the material data (leaves the material data to be edited as it is), but uses the edit list as editing result data. Create an edit description that describes the edit contents, and include it in the edit list. For example, when the editing terminal device 41 performs editing to combine a plurality of material data into one data, how to combine the material data without changing the material data to be edited. The edit description shown is created as edit list information. The edit description (edit list) created in this way is uploaded to the metadata server 53 via the network 21 and registered and stored in the edit description database 63.

  The campaign is completed data (that is, content data) as a program, and is created by the editing terminal device 41 of the editing group 40 in the editing process, for example. For example, the campaign is created in the editing terminal device 41 based on the above-described editing description using the material data corresponding to the editing description. That is, the campaign is content data composed of image data, audio data, and the like, similar to the material data. This package is uploaded to the package data server 52 via the network 21 and registered and stored in the package database 62.

  These data are provided to each terminal device via the network 21 by each server based on the request of each terminal device. In addition, as described later, some of these data includes UMID information of other related data, and each terminal device uses data in which the UMID of the other data is described. And other data can be referred to.

  In addition, as described later, information that associates certain data with information including the UMID of the data, that is, to refer to other data including the own UMID from data including the own UMID in other data. (Information for reverse lookup) is managed by the metadata server 53 as a reference relationship table 66. The table information indicating the correspondence between the data is created when such data is created in each terminal device, uploaded to the metadata server 53 via the network 21, and managed as a reference relationship table 66. The

  In this way, each data created in the production of a program is associated with each other as necessary, and each terminal device can refer to other data from one data. Therefore, each terminal device facilitates the association between data, and the user of each terminal device can easily retrieve the other data from one data. That is, the network system 1 in FIG. 1 can improve the convenience of data, for example, by enabling easy data editing processing and confirmation processing.

  In FIG. 1, one terminal device is shown, but any number of terminal devices may be used. There may be a plurality of groups for each process. In such a case, one terminal device is assigned to each group or worker. For example, in the news gathering process, there are usually a plurality of news gathering groups 30, and there are many cases where a plurality of imaging devices 31 are used. The same applies to other terminal devices, and a plurality of terminal devices may exist.

  Of course, the above-described work process in the production of the program may be expressed in a way other than the above-described planning (configuration), coverage, and editing (production). In addition, the terminal device may be allocated in a manner other than the above, for example, the terminal device is shared for planning and editing.

  FIG. 2 is a diagram illustrating a detailed configuration example of the planning terminal device 11 of FIG.

  In FIG. 2, a CPU (Central Processing Unit) 71 of the planning terminal device 11 is loaded from a program stored in a ROM (Read Only Memory) 72, or from a storage unit 83 or a RAM (Random Access Memory) 73. Various processes are executed according to the program. The RAM 73 appropriately stores data and programs necessary for the CPU 71 to execute various processes.

  The CPU 71, ROM 72, and RAM 73 are connected to each other via a bus 74. An input / output interface 80 is also connected to the bus 74.

  The input / output interface 80 is connected to an input unit 81 including a keyboard and a mouse, and outputs a signal input to the input unit 81 to the CPU 71. The input / output interface 80 is also connected to an output unit 82 including a display, a speaker, and the like.

  In addition, the input / output interface 80 is connected to a storage unit 83 including a hard disk or the like. The storage unit 83 stores a configuration table creation / editing program 91 and a data acquisition / supply program 92. These programs are loaded into the RAM 73 and executed by the CPU 71. By executing these programs, the CPU 71 executes processing relating to creation and editing of a configuration table and processing relating to acquisition and supply of data to other devices as described later.

  The input / output interface 80 is connected to the network 21 and is connected to a communication unit 84 that communicates with other servers and terminal devices. A drive 85 is also connected as necessary. The drive 85 is used when reading data from or writing data to the removable medium 86 formed of a recording medium such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.

  FIG. 3 is a diagram illustrating a detailed configuration example of the imaging device 31 in FIG. 1.

  The imaging device 31 includes an imaging unit 101 that performs processing related to subject imaging and audio recording, a signal processing unit 102 that performs various types of signal processing on image data and audio data obtained by the imaging unit 101, and the signal processing unit 102. The recording unit 103 records the signal-processed image data and audio data on a recording medium and the like, and the imaging unit 101, the signal processing unit 102, and the control unit 104 that controls the recording unit 103.

  The CPU 111 of the control unit 104 executes various processes for controlling each unit of the imaging device 31 in accordance with a program stored in the ROM 112 or a program loaded into the RAM 113 from the storage unit 123. The RAM 113 appropriately stores data and programs necessary for the CPU 111 to execute various processes.

  The CPU 111, the ROM 112, and the RAM 113 are connected to each other via a bus 114, and supply and acquire information such as data and programs as appropriate. An imaging unit 101, a signal processing unit 102, and a storage unit 103 are also connected to the bus 114, and the CPU 111 controls operations of these units via the bus 104. An input / output interface 120 is also connected to the bus 114.

  The input / output interface 120 is connected to an input unit 121 including a keyboard and a mouse, and outputs a signal input to the input unit 121 to the CPU 111. The input / output interface 120 is also connected to an output unit 122 including a display and a speaker.

  Furthermore, a storage unit 123 composed of a hard disk or the like is connected to the input / output interface 120. The storage unit 123 stores an imaging recording control program 131, a metadata generation program 132, and a data acquisition / supply program 133. These programs are loaded into the RAM 113 and executed by the CPU 111. As will be described later, the CPU 111 controls the operation of the imaging unit 101, the signal processing unit 102, and the recording unit 103 by executing an imaging recording control program 131, and performs control processing for performing imaging recording processing. By executing the metadata generation program 132, processing for generating metadata of image data and audio data obtained by the imaging and recording processing, or by executing the data acquisition and supply program 133, various processing for other devices is performed. Process related to data acquisition and supply.

  The input / output interface 120 is connected to the network 21 and is connected to a communication unit 124 that communicates with other servers and terminal devices. A drive 125 is also connected as necessary. The drive 125 is used when data is read from or written to the removable medium 126 formed of a recording medium such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory.

  FIG. 4 is a diagram showing a detailed configuration example of the field PC 32 of FIG.

  As in the case of the planning terminal device 11 of FIG. 2, the field PC 32 is provided with a CPU 151, a ROM 152, and a RAM 153, which are connected to each other via a bus 154. That is, the CPU 151 corresponds to the CPU 71, the ROM 152 corresponds to the ROM 72, the RAM 153 corresponds to the RAM 73, and the bus 154 corresponds to the bus 74.

  Similarly to the planning terminal device 11 of FIG. 2, an input / output interface 160 is also connected to the bus 154 of the field PC 32. The input / output interface 160 includes an input unit 161, an output unit 162, A storage unit 163, a communication unit 164, and a drive 165 are connected. That is, the input / output interface 160 corresponds to the input / output interface 80, the input unit 161 corresponds to the input unit 81, the output unit 162 corresponds to the output unit 82, the storage unit 163 corresponds to the storage unit 83, and the communication The unit 164 corresponds to the communication unit 84, and the drive 165 corresponds to the drive 85. A removable medium 166 on which the drive 165 writes and reads data and programs corresponds to the removable medium 86.

  That is, the configuration of each part of the field PC 32 is basically the same as that of the planning terminal device 11 and performs the same processing.

  However, the storage unit 163 stores a configuration table linking program 171, a rough editing program 172, and a data acquisition and supply program 173. These programs are loaded into the RAM 153 and executed by the CPU 151. As will be described later, the CPU 151 executes processing for associating material data with the configuration table by executing the configuration table linking program 171 and performs rough editing processing on the material data by executing the rough editing program 172. In addition, by executing the data acquisition and supply program 173, processing related to acquisition and supply of various data to other devices is executed.

  FIG. 5 is a diagram illustrating a detailed configuration example of the editing terminal device 41 of FIG.

  The editing terminal device 41 is provided with a CPU 201, a ROM 202, and a RAM 203, as in the case of the planning terminal device 11 of FIG. 2, and these are connected to each other via a bus 204. That is, the CPU 201 corresponds to the CPU 71, the ROM 202 corresponds to the ROM 72, the RAM 203 corresponds to the RAM 73, and the bus 204 corresponds to the bus 74.

  Also, the input / output interface 210 is connected to the bus 204 of the editing terminal device 41 as in the case of the planning terminal device 11 of FIG. The unit 212, the storage unit 213, the communication unit 214, and the drive 215 are connected. That is, the input / output interface 210 corresponds to the input / output interface 80, the input unit 211 corresponds to the input unit 81, the output unit 212 corresponds to the output unit 82, the storage unit 213 corresponds to the storage unit 83, and the communication unit. 214 corresponds to the communication unit 84, and the drive 215 corresponds to the drive 85. A removable medium 216 on which the drive 215 writes and reads data and programs corresponds to the removable medium 86.

  That is, the configuration of each part of the editing terminal device 41 is basically the same as that of the planning terminal device 11 and performs the same processing.

  However, the storage unit 213 stores an edit list generation program 221, an effect editing program 222, a package generation program 223, a data acquisition and supply program 224, a material reference program 225, and a configuration table reference program 226. These programs are loaded into the RAM 203 and executed by the CPU 201. As will be described later, the CPU 201 executes an edit list generation program 221 to generate an edit list that is an edited result of editing material data, or executes an effect editing program 222 to execute an editing result. The editing list is further processed, or the campaign generation program 223 is executed to generate a campaign, or the data acquisition and supply program 224 is executed to execute another device. For example, processing related to acquisition and supply of various data is performed.

  Further, the CPU 201 can execute a process of referring to material data and a configuration table corresponding to a package from, for example, a package by executing the material reference program 225 and the configuration table reference program 226.

  FIG. 6 is a diagram showing a detailed configuration example of the material data server 51 of FIG.

  The material data server 51 is provided with a CPU 251, a ROM 252, and a RAM 253 as in the case of the planning terminal device 11 of FIG. 2, and these are connected to each other via a bus 254. That is, the CPU 251 corresponds to the CPU 71, the ROM 252 corresponds to the ROM 72, the RAM 253 corresponds to the RAM 73, and the bus 254 corresponds to the bus 74.

  Also, the input / output interface 260 is connected to the bus 254 of the material data server 51 as in the case of the planning terminal device 11 of FIG. 2. The input / output interface 260 includes an input unit 261 and an output unit. 262, a storage unit 263, a communication unit 264, and a drive 265 are connected. That is, the input / output interface 260 corresponds to the input / output interface 80, the input unit 261 corresponds to the input unit 81, the output unit 262 corresponds to the output unit 82, the storage unit 263 corresponds to the storage unit 83, and the communication unit. H.264 corresponds to the communication unit 84, and the drive 265 corresponds to the drive 85. The removable medium 266 on which the drive 265 writes and reads data and programs corresponds to the removable medium 86.

  That is, the configuration of each part of the material data server 51 is basically the same as that of the planning terminal device 11 and performs the same processing.

  However, the storage unit 263 stores a material data acquisition / supply program 271. The storage unit 263 has a material data database 61. The material data acquisition / supply program 271 is loaded into the RAM 253 and executed by the CPU 251. As will be described later, the CPU 251 executes the material data acquisition / supply program 271 to register the material data supplied from the terminal device in the material data database 61 or to store the material data registered in the material data database 61. Processing to be supplied to the terminal device is executed.

  FIG. 7 is a diagram showing a detailed configuration example of the package server 52 of FIG.

  The campaign server 52 is provided with a CPU 301, a ROM 302, and a RAM 303, as in the case of the planning terminal device 11 in FIG. 2, and these are connected to each other via a bus 304. That is, the CPU 301 corresponds to the CPU 71, the ROM 302 corresponds to the ROM 72, the RAM 303 corresponds to the RAM 73, and the bus 304 corresponds to the bus 74.

  Similarly to the planning terminal device 11 of FIG. 2, an input / output interface 310 is also connected to the bus 304 of the campaign server 52. The input / output interface 310 includes an input unit 311 and an output unit 312. A storage unit 313, a communication unit 314, and a drive 315 are connected. That is, the input / output interface 310 corresponds to the input / output interface 80, the input unit 311 corresponds to the input unit 81, the output unit 312 corresponds to the output unit 82, the storage unit 313 corresponds to the storage unit 83, and the communication unit. 314 corresponds to the communication unit 84, and the drive 315 corresponds to the drive 85. A removable medium 316 on which the drive 315 writes and reads data and programs corresponds to the removable medium 86.

  That is, the configuration of each part of the campaign server 52 is basically the same as that of the planning terminal device 11 and performs the same processing.

  However, the storage unit 313 stores a package acquisition and supply program 321. In addition, the storage unit 313 has a package database 62. The package acquisition / supply program 321 is loaded into the RAM 303 and executed by the CPU 301. As will be described later, the CPU 301 executes the campaign acquisition and supply program 321 to register the campaign supplied from the terminal device in the campaign database 62 or supply the campaign data registered in the campaign database 62 to the terminal device. Execute the process.

  FIG. 8 is a diagram illustrating a detailed configuration example of the metadata server 53 of FIG.

  As in the case of the planning terminal device 11 of FIG. 2, the metadata server 53 is provided with a CPU 351, a ROM 352, and a RAM 353, which are connected to each other via a bus 354. That is, the CPU 351 corresponds to the CPU 71, the ROM 352 corresponds to the ROM 72, the RAM 353 corresponds to the RAM 73, and the bus 354 corresponds to the bus 74.

  Also, the input / output interface 360 is connected to the bus 354 of the metadata server 53 as in the case of the planning terminal device 11 of FIG. 2, and the input / output interface 360 includes an input unit 361 and an output unit. 362, a storage unit 363, a communication unit 364, and a drive 365 are connected. That is, the input / output interface 360 corresponds to the input / output interface 80, the input unit 311 corresponds to the input unit 81, the output unit 312 corresponds to the output unit 82, the storage unit 313 corresponds to the storage unit 83, and the communication unit. 314 corresponds to the communication unit 84, and the drive 315 corresponds to the drive 85. A removable medium 316 on which the drive 315 writes and reads data and programs corresponds to the removable medium 86.

  That is, the configuration of each unit of the metadata server 53 is basically the same as that of the planning terminal device 11 and performs the same processing.

  However, the data acquisition and supply program 371, the reference relationship table management program 372, and the reference relationship table 66 are stored in the storage unit 363. The storage unit 363 includes an edit description database 63, a configuration table database 64, and a metadata database 65. The data acquisition / supply program 371 and the reference relationship table management program 372 are loaded into the RAM 353 and executed by the CPU 351. As will be described later, the CPU 351 executes a data acquisition and supply program 371 to perform processing for acquiring and supplying data supplied from the terminal device. Further, the CPU 351 executes the reference relationship table management program 372 to manage information in the reference relationship table 66, update the reference relationship table 66, and based on the reference relationship table 66 the UMID requested by the terminal device. Search, and supply it to the request source.

  Next, with reference to the flowchart of FIG. 9, the overall operation (step) of program production will be described. In FIG. 9, the program production workflow is shown in the leftmost column, the name of the group that executes each task is shown in the right column, and the right column is generated for each job. The processing content related to the UMID (self UMID) of the data to be processed is shown, and the rightmost column shows the processing content related to the UMID (reference UMID) of the data that is referenced (associated) by the data generated in each business ing.

  As a first step of program production, the planning terminal device 11 of the planning group 10 creates a configuration table to be a program production planning table based on user input or the like in step S1. At that time, the planning terminal apparatus 11 generates the UMID of the configuration table as a self-UMID and describes the UMID in the configuration table. In step S2, the imaging device 31 of the news gathering group 30 conducts news gathering and generates material data (image data and audio data). At this time, the imaging device 31 (or the field PC 32) generates the UMID of the material data as a self UMID and adds the UMID to the material data.

  When the material data is generated, the field PC 32 associates (associates) the configuration table with the material data obtained in the imaging device 31 in step S3. At this time, the field PC 32 (or the imaging device 31) describes the UMID of the material data in the configuration table.

  When the composition table and the material data are linked, in step S4, the field PC 41 performs rough editing processing on the data obtained in the imaging quality 31, and for example, determination of the IN point and OUT point is performed. The editing result at this time is described in the configuration table. When the material data is prepared as described above, the editing terminal device 41 of the editing group 40 performs an editing process on the material data based on the configuration table in step S5, and an edit list is created from the configuration table. Generate. At this time, the editing terminal device 41 generates a UMID of the generated edit list and describes it in the edit description of the edit list, and also describes the UMID of the configuration table in the generated edit list.

  Next, in step S6, the editing terminal device 41 performs an editing process for adding an effect, such as inserting a super, adding a sound effect or BGM, and adding the effect to the edit list. Generate the edited list. At this time, the editing terminal device 41 generates the generated UMID of the edit list to which the effect is added, and further describes the UMID of the original edit list in the edit list to which the effect is added. In step S7, the editing terminal apparatus 41 that has generated the edit list to which the effect has been added generates a campaign from the edit list to which the effect has been added. At this time, the editing terminal device 41 generates a UMID of the generated campaign and adds it to the generated campaign.

  As described above, each terminal device performs business and generates each data. At that time, each terminal device generates a UMID of each data as necessary, and adds it to other data, or adds the UMID of other data to the generated data. Generate related information. By doing so, the network system 1 can easily refer to target data from one data after each data is generated by each terminal device.

  Next, details of the flow of processing in each apparatus will be described.

  First, creation of a configuration table in the planning group 10 will be described. An operator (planner) of the planning group 10 creates a configuration table using the planning terminal device 11 in the first step of program production. When the operator operates the planning terminal device 11 to start creation of the configuration table, the CPU 71 of the planning terminal device 11 executes the configuration table creation / editing program 91 and starts a new configuration table creation process.

  An example of a new configuration table creation process will be described with reference to the flowchart of FIG.

  When the new configuration table creation process is started, the CPU 71 that executes the configuration table creation / editing program 91 supplies predetermined image data to the monitor of the output unit 82 in step S21. When the monitor of the output unit 82 acquires the image data, the monitor of the initial state corresponding to the image data is displayed.

  When the process of step S21 is completed, the CPU 71 proceeds to the process of step S22, controls the input unit 81, starts accepting user input, and determines whether information is input from the input unit 81 in step S23. To do. When the user operates the input unit 81 and determines that the information has been input, the CPU 71 advances the process to step S24 to supply the input information to, for example, the RAM 73 and hold it, and controls the output unit 82. The information is reflected in the configuration table displayed on the monitor. That is, the CPU 71 supplies the information acquired via the input unit 81 to the RAM 72 and holds it, generates image data of a configuration table reflecting the information, and supplies it to the monitor of the output unit 82. The monitor displays a configuration table reflecting the input information.

  When the process of step S24 ends, the CPU 71 advances the process to step S25. If it is determined in step S23 that no information is input from the input unit 81, the CPU 71 omits the process of step S24 and proceeds to step S25.

  In step S25, the CPU 71 controls the input unit 81 to determine whether or not the user has instructed saving. When it is determined that the instruction has been received, the CPU 71 proceeds to step S26 to generate a UMID and configure the UMID. It is added to the information held in the RAM 73 as the UMID of the table. Then, the CPU 71 advances the process to step S27, converts the information stored in the RAM 73 into a file as a configuration table, saves the file in, for example, the storage unit 83, etc., and performs the end process in step S28, The new creation process is terminated.

  On the other hand, if it is determined in step S25 that the storage is not instructed, the CPU 71 advances the process to step S29 to determine whether or not to end the configuration table new creation process. For example, if nothing is instructed by the user via the input unit 81 and it is determined that the new configuration table creation process is not to be terminated, the CPU 71 returns the process to step S23 and repeats the subsequent processes. If it is determined in step S29 that the new composition table creation process is to be terminated, for example, when the user inputs a halfway termination instruction, the CPU 71 performs the termination process in step S28 and then creates a new composition table. End the process.

  That is, the CPU 71 displays the initial configuration table on the monitor, starts accepting user input, and then completes the creation of the configuration table by the user while repeating the processes of steps S23 to S25 and step S29. Wait until. When the user completes the creation process of the configuration table and instructs to save the update of the configuration table, the CPU 71 performs the processing from step S26 to step S28, saves the created configuration table, and stores the configuration table. The new creation process is terminated. Further, when the user gives an instruction to end the creation process of the configuration table halfway, the CPU 71 performs an end process in step S28 and ends the new configuration table creation process.

  11 and 12 are diagrams showing examples of the configuration table created by the configuration table creation process as described above. In FIG. 11, the configuration table 381 includes information necessary for program production, such as a scenario of the program to be produced and various instructions. These pieces of information have a hierarchical structure in segment units at each level such as “program”, “episode”, “scene”, and “cut”. In the hierarchical structure, a plurality of subordinate concepts, in which a plurality of elements are classified into a plurality of levels and a lower level element is associated with an element of a higher level, are grouped into a single upper concept (grouped together). ), And the number of elements usually increases as the level goes down. Note that “program”, “episode”, “scene”, “cut”, and the like indicate “level” in this hierarchical structure, and a segment indicates “element” in this hierarchical structure (indicating a level). Not a thing). For example, the “cut” level (hierarchy) may include a plurality of segments (for example, cut numbers 1, 2, 3,...).

  “Take” is also configured to be positioned below “cut”, but “take” is not included in the element in the concept of the configuration table (scenario), as will be described later. Therefore, the segment is included in the “cut” level.

  For example, “program” is a level indicating the entire program, and represents a large theme common to the entire program. That is, normally, a segment of the “program” level is formed by one. “Episode” is one level below “Program”, and each segment of “Episode” represents a small theme that subdivides the entire program into several parts. “Scene” is a level that is one level lower than “episode” and is a level indicating “scene”. Usually, the “scene” indicates a part constituted by image data having the same location (coverage place) and coverage time. “Cut” is a level indicating a portion of the image data or audio data where the screen has not been switched due to editing, imaging stoppage, or the like. “Take” is a level indicating image data actually captured based on “cut” in the configuration table, and is image data from the start to the end of imaging.

  That is, in the program, each segment is structured hierarchically. That is, one or more “cut” segments make up a “scene” segment, one or more “scene” segments make up an “episode” segment, and one or more “episode” segments A “program” segment is formed. Of the one or more “takes”, those adopted as “cuts” are referred to as “OK takes”. Therefore, the segment of “take” hierarchically belongs to the lower level of “cut”, but the segment in the configuration table is included in “cut”.

  For example, a program title (program title) and an ID for identifying the program are assigned to the “program” segment. In addition, the UMID of the configuration table 381 (in the case of FIG. 11, “PPPPPPPP”) is also included. In addition, each segment below the “episode” is configured by a memo or the like that describes production instructions, special notes, and the like in each segment.

  Note that the UMID is actually 32 bytes (or 64 bytes) of information, but is shown here as an 8-character string for the sake of simplicity. The same applies to the following.

  As will be described later, take data, that is, a video file 383 and take metadata 382 that is metadata thereof are generated for such a configuration table 381 by coverage. As shown in FIG. 12, the take metadata 382 includes general metadata in which date, time, position information, device setting information, or special notes are described. Furthermore, the take metadata 382 includes the UMID of the video file and the information of the low resolution file including the low resolution data that is the low resolution image data of the video file, and the general metadata is associated with these files. . As will be described later, the video file 383 is material data composed of image data, audio data, and the like obtained by interviewing, and is added with its own UMID.

  Note that, at the stage of the configuration table creation process described above, only the configuration table 381 is created, and therefore the take metadata 382 and the video file 383 do not exist and are not associated with the configuration table 381.

  By executing the configuration table creation process as described above, the CPU 71 can not only create a new configuration table based on the user's instruction, but also add the self-UMID of the configuration table to the configuration table. it can. As a result, the network system 1 facilitates the association between the data and can easily retrieve the other data from one data, for example, the data editing process and the confirmation process can be easily performed. The convenience of data can be improved, such as enabling it.

  When the configuration table is created in the planning terminal device 11 as described above, the user of the planning terminal device 11 then operates the planning terminal device 11 to store the created configuration table in the metadata server 53. Upload and register in the configuration table database 64.

  With reference to the flowchart of FIG. 13, processing related to registration of the configuration table will be described.

  Based on the user's instruction, the CPU 71 that executes the data acquisition and supply program 92 of the planning terminal device 11 controls the communication unit 84 in step S41, and the created configuration table is sent to the metadata server 53 via the network 21. To supply.

  The CPU 351 of the metadata server 53 that executes the data acquisition / supply program 371 controls the communication unit 364, and when the supplied configuration table is acquired in step S51, the acquired configuration table is stored in the storage unit 363 in step S52. Are supplied to the configuration table database 64. When the configuration table database 64 acquires the configuration table in step S61, the configuration table database 64 registers the configuration table in step S62.

  When acquiring the configuration table registered as described above, the CPU 71 of the planning terminal apparatus 11 executes the data acquisition supply program 92 and controls the communication unit 84 in step S42 to control the metadata server 53. Request a configuration table. This request is made using UMID. The CPU 351 of the metadata server 53 that executes the data acquisition / supply program 371 controls the communication unit 364, and when the request is acquired in step S53, the requested configuration table is requested to the configuration table database 64 in step S54. To do. Upon acquiring the request in step S63, the configuration table database 64 searches the requested configuration table using the UMID and supplies it to the CPU 351 in step S64. In step S55, the CPU 351 that executes the data acquisition and supply program acquires the configuration table. In step S56, the CPU 351 controls the communication unit 364, and the acquired configuration table is sent to the request source via the network 21 for the planning. It supplies to the terminal device 11. The CPU 71 of the planning terminal apparatus 11 that executes the data acquisition and supply program 92 controls the communication unit 84 and acquires the configuration table supplied from the metadata server 53 in step S43.

  In this way, the configuration table registered in the configuration table database 64 can be requested and acquired from the planning terminal device 11 as necessary. The same applies to the other terminal devices, and the configuration table registered in the configuration table database 64 can be acquired as appropriate by communicating with the metadata server 53 as described above.

  Next, generation of material data (take data) will be described.

  An operator of the news gathering group 30 performs news gathering (imaging of a subject and recording of sound) using the imaging device 31. When the imaging device 31 is operated by an operator and instructed to perform imaging (sound recording), the imaging device 31 starts imaging processing (step S2 in FIG. 9).

  The imaging process will be described with reference to the flowchart of FIG.

  The CPU 111 of the imaging device 31 instructed to perform the imaging process executes the imaging recording control program 131, and controls the imaging unit 101 in step S81. The imaging unit 101 images a subject and generates take data based on the control of the CPU 111. The imaging unit 101 supplies the generated take data to the signal processing unit 102.

  In step S82, the CPU 111 that executes the imaging / recording control program 131 controls the signal processing unit 102 to perform signal processing on the generated take data. The signal processing unit 102 performs signal processing on the take data based on the control of the CPU 111 and supplies it to the recording unit 103.

  In step S 83, the CPU 111 generates a UMID of take data based on the imaging / recording control program 131 and supplies it to the recording unit 103. In step S84, the recording unit 103 is controlled by the CPU 111 to add a UMID to the take data and record it on a recording medium or the like.

  The CPU 111 further executes the metadata generation program 132, generates metadata (take metadata) corresponding to the generated take data in step S85, and stores it in the RAM 113 or the like. At this time, the CPU 111 adds the UMID of the take data corresponding to the take metadata to the take metadata. Then, the CPU 111 controls the input unit 121 based on the metadata generation program 132 and accepts the operator's input. In step S86, the take memo, which is information such as special remarks regarding take data input by the operator, is stored. It is determined whether or not it has been input. If it is determined that a take memo has been input, the CPU 111h adds the input take memo to the take metadata held in the RAM 113 or the like in step S87, and proceeds to step S88.

  If it is determined in step S86 that no take memo has been input, the CPU 111 skips step S87 and proceeds to step S88.

  In step S88, the CPU 111 that executes the metadata generation program 132 supplies the take metadata stored in the RAM 113 or the like to the recording unit 103 via the bus 114, controls the recording unit 103, and records it. Record on a medium.

  Based on the imaging recording control program 131, the CPU 111 advances the processing to step S89, determines whether or not to end imaging, and determines that it does not end, returns the processing to step S81 and repeats the subsequent processing. . If it is determined in step S89 that the imaging is to be ended, the CPU 111 performs an ending process in step S90 and ends the imaging process.

  By performing the imaging process as described above, take data 383 to which UMID is added and take metadata 382 to which UMID of take data is added are generated as shown in FIG. In FIG. 15, six take data 383 identified by UMID “AAAAAAAA” to “FFFFFFFF” and six take metadata 382 respectively corresponding to each take data are generated.

  As described above, the imaging device 31 generates the material data (take data) to which the self-UMID is added, so that the take data 383 can be associated with the configuration table 381 and other data as will be described later. . As a result, the network system 1 facilitates the association between the data and can easily retrieve the other data from one data, for example, the data editing process and the confirmation process can be easily performed. The convenience of data can be improved, such as enabling it.

  The material data generated in this way is supplied to the material data server 51 and registered in the material database 61 by the imaging device 31 and the like, as in the case of the configuration table. The processing at that time is basically the same as that of the configuration table described with reference to the flowchart of FIG. Specifically, for example, the CPU 111 of the imaging device 31 executes the data acquisition and supply program 133, controls the communication unit 124, and transmits the material data recorded on the recording medium in the recording unit 103 via the network 21. This is supplied to the material data server 51. When the CPU 251 of the material data server 51 that executes the material data acquisition / supply program 271 controls the communication unit 264 to acquire the material data, the CPU 251 supplies the material data to the material database 61. The material data database 61 registers the supplied material data.

  In this way, the material data registered in the material data database 61 can be acquired from each terminal device as needed, as in the case of the configuration table described above. For example, when acquiring the material data registered in the material data database 61, the CPU 111 of the imaging device 31 executes the data acquisition supply program 133, controls the communication unit 124, and controls the material data server 51. Request material data. At this time, the CPU 111 requests material data by supplying the UMID of the target material data. Upon receiving this request, the CPU 251 of the material data server 51 that executes the material data acquisition / supply program 271 accesses the material data database 61 based on the request, supplies the UMID of the material data, and requests the material data. To do. The material data database 61 searches for material data corresponding to the supplied UMID, and if it exists, supplies the material data to the imaging device 31 that is the request source via the material data acquisition / supply program 271. The CPU 111 of the imaging apparatus 31 that executes the data acquisition supply program 133 controls the communication unit 124 to acquire the material data.

  In this way, each terminal device can acquire the material data registered in the material data database 61 as necessary.

  The same applies to metadata, which is supplied to the metadata server 53 by the imaging device 31 and the like and registered in the metadata database 65. And each terminal device can acquire the metadata registered in the metadata database 65 as needed. Since these processes are the same as those in the case of the configuration table described with reference to the flowchart of FIG.

  Next, processing for associating (linking) take data with a configuration table will be described.

  As described with reference to the flowchart of FIG. 13, an operator of the news gathering group 30 conducts news gathering based on the acquired configuration table, and generates material data (take data), for example, using the field PC 32. Then, processing for associating the material data with the composition table is performed (step S3 in FIG. 9). The field PC 32 that is instructed to link take data executes a take data link process, and links the configuration table designated by the operator to the take data.

  The take data linking process will be described with reference to the flowchart of FIG.

  When the worker is instructed to link take data, the CPU 151 of the field PC 32 executes the configuration table linking program 171, and controls the input unit 161 in step S <b> 111, and the operator performs linking. It is determined whether or not a table cut is specified. The user operates the input unit 161 to select and specify a cut to be linked from the “Cut” column of the configuration table 381 shown in FIG. If it is determined that a cut has been designated, the CPU 151 advances the process to step S112 to set the designated cut in the configuration table as a processing target.

  Next, the CPU 151 that executes the configuration table linking program 171 advances the process to step S113 to control the input unit 161 to determine whether take data to be linked is specified. If it is determined that take data has been designated, the CPU 151 advances the processing to step S114, describes the UMID of the take data in the field (UMID field) relating to the take belonging to the designated cut in the composition table, and takes the take data. Associate with a cut in the bill. In the example of FIG. 17, UMIDs “AAAAAAAA” to “FFFFFFFF” of take data are respectively described in the “UMID” column of “take” in the configuration table 381, and the association is performed as indicated by the arrows in the figure. . When the take data is associated, the CPU 151 advances the process to step S115. If it is determined in step S113 that take data is not specified, the CPU 151 omits the process in step S114 and proceeds to step S115.

  In step S115, the CPU 151 controls the input unit 161 on the basis of the configuration table linking program 171 to be executed, and designates whether or not take data is adopted by the operator (OK take or NG take). It is determined whether or not an OK / NG setting (which is a setting for identifying whether there is) is input. If it is determined that the input has been input, the process proceeds to step S116, and the association is performed based on the input. The input setting is described in the OK / NG setting column provided in the column relating to the take belonging to the cut. In the case of the example in FIG. 17, of the two take data (take data of take number “1” and take data of take number “2”) associated with cut number “1” of configuration table 381, take number “ The take data associated as “1” is set to “OK”, and the take data associated as the take number “2” is set to “NG”. When the setting of OK / NG is completed, the CPU 151 advances the process to step S117. If it is determined in step S115 that the OK / NG setting has not been input, the CPU 151 omits the process of step S116 and advances the process to step S117.

  The CPU 151 that has proceeded to step S117 controls the input unit 161 based on the configuration table linking program 171 to be executed, and determines whether or not a memo related to the linked take data has been input by the operator. If it is determined that it has been input, the process proceeds to step S118, and the memo of the designated hierarchy in the configuration table is updated based on the input. CPU151 which completed update of a memo advances a process to step S119. If it is determined in step S117 that no memo has been input, the CPU 151 omits the process of step S118 and advances the process to step S119.

  In step S119, the CPU 151 determines whether or not the take data linking process is to be terminated. If it is determined that the take data linking process is not to be terminated, the CPU 151 returns the process to step S111 and repeats the subsequent processes. If it is determined in step S119 that the take data linking process is to be terminated, the CPU 151 advances the process to step S120, and a reference relationship with the UMID of the configuration table as a reference destination, such as the reference relationship table 391 shown in FIG. After creating a table and performing an end process in step S121, the take data linking process ends.

  In the case of the reference relationship table 391 shown in FIG. 18, the UMID “PPPPPPPP” in the configuration table is described as the reference destination UMID, and the UMIDs “AAAAAAAAA” to “FFFFFFFF” of the material data are described as the reference source UMID. This reference relationship table is a table for specifying a reference destination UMID based on a reference source UMID (or conversely, specifying a reference destination UMID based on a reference destination UMID), and a table indicating a relationship between UMIDs. .

  As described above, by performing the take data linking process, the field PC 32 can describe and associate the UMID of the take data 383 in the configuration table 381. The field PC 32 can also generate a reference relationship table used for making a reference in the reverse direction of the reference relationship of the UMID (that is, for example, searching the configuration table 381 from the take data 383). As a result, the network system 1 facilitates the association between the data and can easily retrieve the other data from one data, for example, the data editing process and the confirmation process can be easily performed. The convenience of data can be improved, such as enabling it.

  The field PC 32 that has generated the reference relationship table as described above uploads the generated reference relationship table to the metadata server 53 based on an instruction from the worker.

  With reference to the flowchart of FIG. 19, the flow of the process of uploading the reference relationship table will be described.

  The CPU 151 of the field PC 32 executes the data acquisition and supply program 173, controls the communication unit 164, and supplies the reference relationship table to the metadata server 53 via the network 21 in step S141.

  When the CPU 351 of the metadata server 53 executing the data acquisition / supply program 371 acquires the reference relationship table in step S151, the CPU 351 supplies the reference relationship table to the reference relationship table management program 372 in step S152. Specifically, the CPU 351 that executes the data acquisition / supply program 371 holds the acquired reference relationship table in the RAM 353 or the like, and moves the processing to the reference relationship table management program 372. When the CPU 351 executes the reference relationship table management program 372 and acquires the reference relationship table in step S161, the CPU 351 supplies the reference relationship table to the storage unit 363 and stores the reference relationship table in the storage unit 363 based on the reference relationship table. The reference relationship table 66 is updated.

  As described above, the field PC 32 uploads the generated reference relationship table to the metadata server 53, and the metadata server 53 updates the stored reference relationship table 66 using the table. By doing this, as described later, each terminal device can grasp the reference relationship of the UMID, and can refer to other data using data to which the UMID of other data is not added. become able to.

  The field PC 32 can perform a simple editing process (coarse editing) on the material data associated with each other as described above (step S4 in FIG. 9). For example, as described above, the operator of the news gathering group 30 can not only specify the OK take in the composition table, but also select the part to be adopted as the take from the material data adopted as the OK take in the composition table. It can also be specified.

  The part to be adopted from the material data is specified by specifying the so-called IN point and OUT point. That is, the operator designates a portion to be adopted by the material data by designating the time code of the first frame image as the IN point and designating the time code of the last frame image as the OUT point. In other words, the data between the IN point and the OUT point specified by the operator (data on the time code after the IN point and before the OUT point) is set as the adopted data. The timetable of the IN point and OUT point is described in the configuration table.

  The rough editing process by the field PC 32 will be described with reference to the flowchart of FIG.

  When the operator gives an instruction to start the coarse editing process, the CPU 151 of the field PC 32 executes the coarse editing program 172, and controls the input unit 161 in step S181 to determine whether the IN point is specified by the worker. Determine whether. If it is determined that the user has designated the IN point by operating the input unit 161, the CPU 151 proceeds to step S182 based on the coarse editing program 172 to be executed, and describes the IN point in the configuration table. In the case of the example of FIG. 21, in the configuration table 381, the time code of the IN point is described following the tag “[In]” in the “take data” column included in the take column belonging to the cut.

  When the process of step S182 ends, the CPU 151 advances the process to step S183. If it is determined in step S181 that the IN point has not been designated, the CPU 151 omits the process of step S182 and advances the process to step S183.

  In step S183, the CPU 151 executing the coarse editing program 172 controls the input unit 161 to determine whether or not the OUT point has been designated by the operator. If it is determined that the user has designated the OUT point by operating the input unit 161, the CPU 151 proceeds to step S184 based on the coarse editing program 172 to be executed, and describes the OUT point in the configuration table. In the example of FIG. 21, in the configuration table 381, the OUT point time code is described in the “take data” column included in the take column belonging to the cut, following the tag “[Out]”.

  When the process of step S184 is finished, the CPU 151h advances the process to step S185. On the other hand, if it is determined in step S183 that the OUT point is not designated, the CPU 151 omits the process in step S184 and proceeds to step S185.

  In step S185, the CPU 151 determines whether or not to end the rough editing process. If it is determined not to end the process, the CPU 151 returns the process to step S181 and repeats the subsequent processes. In step S185, for example, when it is determined that the rough editing process is to be ended, for example, by an operator instructing the end, the CPU 151 executes the end process in step S186 and ends the rough editing process.

  Next, creation of an edit list will be described.

  When material data and metadata are generated based on the composition table and linked to the composition table, the worker of the editing group 40 next performs the editing operation of the material data based on the composition table, An edit list as an editing result is generated (step S5 in FIG. 9).

  The editing terminal device 41 of the editing group 40 is operated by an operator before the editing process, and acquires data necessary for the editing process such as the configuration table, material data, and metadata in advance as described above. When the operator instructs the creation of an edit list, the CPU 201 of the editing terminal device 41 executes the edit list generation program 221 and starts the edit list creation process.

  The edit list creation process will be described with reference to the flowchart of FIG.

  First, in step S201, the CPU 201 of the editing terminal device 41 that executes the edit list generation program 221 generates a UMID for the edit list to be generated, and in step S202, creates an edit description based on the configuration table. In step S203, the UMID of the configuration table is described in the edit description. Then, the CPU 201 generates other data configured as an edit list in step S204 according to the edit list generation program 221, and records the data and edit description in the storage unit 213 or the like as an edit list in step S205. .

  In step S <b> 206, the CPU 201 creates a reference relationship table in which the UMID of the edit list is referred to based on the edit list generation program 221 to be executed.

  FIG. 23 is a diagram illustrating an example of a reference relationship table generated in the process of step S206 of FIG.

  In FIG. 23, the reference relationship table 393 sets the reference destination UMID as the UMID “MMMMMMMM” in the edit list, the reference source UMID as the UMID “AAAAAAAA” to “FFFFFFFF” in the material data, and the UMID “PPPPPPPP” in the configuration table. Table information. By using this reference relationship table 393, the operator can refer to the edit list from the material data and the configuration table.

  The CPU 201 that created the reference relationship table as described above ends the edit list creation process.

  FIG. 24 shows a description example of the edit description created by the above edit list creation processing. In FIG. 24, a description example 394 is a description indicating an editing result described in XML (eXtensible Markup Language). A line number is attached to the left end of each line for explanation. The first to seventh lines of the description example 394 are the header portion of the edit description, in which information such as settings related to the entire edit process is described. For example, in the third line, “umid =” MMMMMMMM ”” is described, indicating that the UMID of this edit list is “MMMMMMMM”. In line 7, for example, “<SourcePlanningMetadRef =“ PPPPPPPP ”/>” is described, and the UMID “PPPPPPPP” of the configuration table corresponding to this edit list is described.

  Lines 8 to 41 of the description example 394 are body parts indicating editing contents. Here, the editing contents as described in the cut layer of the configuration table are described in XML. In FIG. 24, since it is described based on the configuration table, it is described as information for each material data (clip) adopted as the adopted take of each cut. The information on the material data includes UMID information on the material data. For example, in the information of “Clip1” shown in the 10th to 14th lines, the UMID of the material data is described as “umid: EEEEEEEE” in the 11th line.

  The CPU 201 generates a reference relationship table as shown in FIG. 23 based on the editing description described in this way.

  The editing terminal device 41 supplies the edit list generated as described above to the metadata server 53 and registers it in the edit description database 63. Further, the editing terminal device 41 updates the reference relationship table 66 using the generated reference relationship table. The editing terminal device 41 and the metadata server 53 perform these processes in the same manner as in the case of the configuration table described with reference to the flowchart of FIG. The metadata server 53 provides these data to each terminal device. In this way, it becomes possible to refer to other data using data to which no other data UMID is added.

  As described above, by performing the edit list creation process, the editing terminal device 41 can generate an edit list based on the configuration table and the material data, and associate it with the configuration table and the edit list. The editing terminal device 41 can also generate a reference relationship table used for making a reference in the opposite direction of the UMID reference relationship (that is, for example, searching an edit list from material data). As a result, the network system 1 facilitates the association between the data and can easily retrieve the other data from one data, for example, the data editing process and the confirmation process can be easily performed. The convenience of data can be improved, such as enabling it.

  An operator of the editing group 40 may perform editing processing such as adding an effect to the edit list generated in this way (step S6 in FIG. 9). In this case, the editing terminal device 41 of the editing group 40 is operated by an operator before the editing process, and acquires an edit list or the like for performing the editing process as described above. When the operator gives an instruction to edit the edit list, the CPU 201 of the editing terminal device 41 executes the effect editing program 222 and starts the effect editing process.

  The effect editing process will be described with reference to the flowchart of FIG.

  In step S221, the CPU 201 that has executed the effect editing program 222 and started the effect editing process first reads the editing content of the original editing description in the edit list acquired in advance, creates a new editing description, and performs step S222. In step S223, a new edit description UMID is created, and in step S223, it is added to the new edit description.

  In step S224, the CPU 201 that executes the effect editing program 222 controls the input unit 211 to determine whether effect editing information has been input. If it is determined that the effect editing information has been input, the process proceeds to step S225 and is input. The effect is reflected in the editing content of the new editing description, and the process proceeds to step S226. If it is determined in step S224 that effect editing information has not been input, the CPU 201 omits the process of step S225 and advances the process to step S226.

  In step S226, the CPU 201 performs processing based on the effect editing program 222, and determines whether or not to save the created new editing description. If it is determined that the new edit description is to be saved, the CPU 201 proceeds to step S227 to record the created new edit description. In step S228, the new edit description is referred to as shown in FIG. Create a reference relationship table like this: In FIG. 26, the reference relationship table 395 includes the reference source UMID as the UMID of the original edit description and the UMID group of the material data edited in the original edit description, and the reference destination UMID is a newly created reference description UMID. It is a table with UMID. The reference relationship table 395 is uploaded to the metadata server 53 and used to update the reference relationship table 66 as described with reference to the flowchart of FIG.

  Returning to FIG. 25, if it is determined in step S226 that the created new edit description is not to be saved, the CPU 201 omits the processes in steps S227 and S228 and proceeds to step S229.

  In step S229, the CPU 201 determines whether or not effect editing is newly performed. When it is determined that effect editing is newly performed, the CPU 201 returns the process to step S221 and repeats the subsequent processes.

  If it is determined in step S229 that no new effect editing is to be performed, the CPU 201 proceeds to step S230 to determine whether to end the effect editing process. Returning to step S224, the subsequent processing is repeated. If it is determined in step S230 that the effect editing process is to be ended, the CPU 201 advances the process to step S231, performs the end process, and then ends the effect editing process.

  FIG. 27 is a diagram showing a description example of a new edit description generated as described above. In FIG. 27, a description example 396 is a description indicating the editing result of the editing process performed on the edit list described in XML. A line number is attached to the left end of each line for explanation. The configuration is basically the same as that of the description example 394 described with reference to FIG. In the case of the description example 397, for example, “LLLLLLLLLL”, which is the UMID of this edit list, is described as “umid =“ LLLLLLLL ”” on the third line. However, in the description example 397, unlike the description example 394, the information related to the UMID of the original edit list is “<SourceEditlist umidRef =“ MMMMMMMM ”/>”, not the information of the configuration table. It describes the UMID of the edit list before adding the effect.

  In the 8th and subsequent lines, information on data to be edited and information on effects added to the data are described.

  For example, "<transition id =" wipe "dur =" 00: 00: 06: 00 "type =" Wipe "subtype =" leftToRight "/>" is described in the 8th line, and the display screen left to right It is shown that the material data is combined using an effect that the new image wipes toward the screen and the image is switched over 6 seconds. That is, as shown in FIG. 28, the background image 403 that is an image of the original material data is displayed on the display screen 401, and the next material data (take data of the next cut) is displayed. An overwrite image 402 appears from the left side of the display screen 401 and gradually expands the image range in the right direction. Finally, the draft image 403 is deleted, and the overwrite image 402 is displayed on the entire display screen 401. It is shown in the above-mentioned eighth line that such an image switching effect (wipe) is used for the combined portion of the material data.

  For example, FIG. 29 shows a connection portion between “Clip 1” described in the 13th to 17th lines of description example 396 and “Clip 2” described in the 19th to 23rd lines. Thus, the wipe process is performed.

  29, the base image 403 is an image of “Clip1” in the description example 396 of FIG. 27, and the overwrite image 402 is an image of “Clip2” in the description example 396 of FIG. In the description line 396 of FIG. 27, “clipEnd =“ smpte-30 = 00: 01: 43: 20 ”” is described, and “Clip1” material data (material whose UMID is “EEEEEEEE”) (Data) is displayed with a frame image having a time code “00: 01: 43: 20”. 27, “clipBegin =“ smpte-30 = 00: 00: 12: 10 ”” is described in the 22nd line of the description example 396, and the material data of “Clip2” (UMID is “AAAAAAAA” Is displayed from the frame image of the time code “00: 00: 12: 10”.

  As described above, since the wipe time is 6 seconds, the time code “00: 00: 12: 10” of the material data of “Clip 2” (material data with the UMID “AAAAAAAA”) as the overwritten image 402 is set. The frame image is displayed 6 seconds before the frame image with the time code “00: 01: 43: 20” of the material data of “Clip 1” (the material data with the UMID “EEEEEEEE”) as the draft image 403. , The material data of “Clip 1” and the material data of “Clip 2” are combined. That is, the wipe is started from the position of “00: 01: 27: 20” in the time code of the entire variant description (time code in the edited result) (from the description of the description example 396, the start of the material data of “Clip 1” 10 Since the seconds are not displayed), the wipe is terminated at the position of the time code “00: 01: 33: 20” (the display image is completely switched to the material data image of Clip2).

  As described above, the edit list to which the effect is added is generated. The effects added to the edit list at this time include, for example, picture effects such as picture-in-picture, flash, fade-in, fade-out, pan, zoom, or telop insertion, BGM (Back Ground Music), and narration. Of course, any effect may be used, such as a sound effect such as insertion of a sound.

  The edit list to which such an effect is added is uploaded from the editing terminal device 41 to the metadata server 53 via the network 21 and registered in the edit description database 63, as in the case of the configuration table and edit list described above. Is done. The edit descriptions registered in the edit description database 63 are acquired and used as necessary by each terminal device, as in the case of the configuration table and the edit list described above.

  Even when an edit list is generated from an edit list as described above, the UMID of the edit list is added to the edit description of the newly generated edit list. Further, the UMID of the original edit list and the UMID of the material data corresponding to the edit list are added to the newly generated edit list. Further, information for referring to the newly generated edit list (information for reversely retrieving the UMID) from the original edit list and material data is managed by the metadata server 53 as a reference relationship table 66. .

  Therefore, each terminal device can easily acquire various data corresponding to the edit list using the UMID of the various data corresponding to the edit list described in the edit description of the edit list. Further, by using the reference relationship table 66, each terminal device can easily search and acquire an edit list using UMIDs of various data corresponding to the edit list.

  In other words, the network system 1 can easily perform data editing processing and confirmation processing, for example, by facilitating association between data and easily searching the other data from one data. For example, the convenience of data can be improved.

  As described above, the process of creating a new edit list from the edit list can be repeated any number of times. In addition, the operator can naturally create a plurality of edit lists from one edit list.

  As described above, the editing processing is performed on the material data, an edit list is generated from the material data, and when the editing work is completed, the operator of the editing group 40 operates the editing terminal device 41, and finally Using the edit description corresponding to the edit result, a package that is completed data as content data is generated (step S7 in FIG. 9). When the generation of the package is instructed, the editing terminal device 41 first acquires the edit description and material data for generating the package, executes the package generation program 223, and starts the package generation process.

  The campaign generation process will be described with reference to the flowchart of FIG.

  In FIG. 30, the CPU 201 that has started the package generation process reads the edit description in step S251, creates a package from the material data based on the edit contents of the edit description in step S252, and in step S253, generates the package description. A UMID is created and added to the package. In step S254, the package to which the UMID is added is supplied to and stored in the storage unit 213.

  Then, in step S255, the CPU 201 that executes the campaign generation program 223 creates a reference relationship table 411 as shown in FIG. 31 with the generated campaign as a reference destination. In the case of the reference relationship table 411 in FIG. 31, the UMID “ZZZZZZZZ” of the package is described as the reference destination UMID, and the UMID “LLLLLLLL” of the edit description is described as the reference source UMID.

  Returning to FIG. 30, the CPU 201 that has completed the process of step S256 ends the package generation process.

  FIG. 32 is a schematic diagram illustrating a configuration example of campaign data generated by the campaign generation process. As shown in FIG. 32, the campaign data is configured in a standard AV multiplex format. In the case of this standard AV multiplex format, data is configured by sequentially arranging a header (File Header) 421, a body (File Body), and a footer (File Footer).

  Here, in FIG. 32, as video data and audio data arranged in the body, video data encoded by MPEG (Moving Picture Experts Group) IMX system called D10 and non-standard of AES (Audio Engineering Society) 3 format are used. A standard AV multiplex format when compressed audio data is employed is shown.

  In addition, video data and audio data of various formats such as DV (Digital Video) can be arranged in the body.

  In the header 421, a header partition pack, header metadata 422, and an index table are sequentially arranged from the top. In the header partition pack, data for specifying the header 421, data format arranged in the body, information representing a file format, and the like are arranged. In the header metadata, in addition to the above-described package UMID 423 (self-UMID), for example, file unit metadata such as a file creation date and information on data arranged in the body is arranged. In the index table, a table representing the position of an edit unit, which will be described later, is arranged in the body.

  The index table is optional and may or may not be included in the header 421. In addition to the index table, various optional data can be arranged in the header 421.

  The footer is composed of a footer partition pack, and data for specifying the footer is arranged in the footer partition pack.

  The body is composed of one or more edit units. An edit unit is a unit of one frame, in which AV data and the like for one frame are arranged.

  That is, the edit unit is configured by arranging a system item (Sytem Item), a picture item (Picture Item), a sound item (Sound Item), and an auxiliary item (Auxiliary Item) from the top.

  In the system item, metadata (frame unit metadata) about a frame of video data arranged in a subsequent picture item is arranged. Here, examples of the metadata in units of frames include a time code.

  One frame of video data is arranged in the picture item. In FIG. 32, the above-described D10 format video data is arranged.

  Here, in the picture item, one frame of video data is KLV coded and arranged in a KLV (Key, Length, Value) structure.

  The KLV structure is a structure in which a key, length, and value are arranged sequentially from the beginning. What kind of data is the data arranged in the key? A 16-byte label that conforms to the SMPTE 298M standard is placed. In the length, the data length of data arranged in the value is arranged. In the value, actual data, that is, one frame of video data is arranged here.

  The picture item has a fixed data length based on KAG (KLV Alignment Grid). In order to make the picture item have a fixed length, a filler as data for stuffing is also made into a KLV structure and is arranged after the video data of the picture item.

  The fixed length based on KAG, which is the data length of the picture item, is, for example, an integral multiple of the sector length of the optical disc (for example, 512 bytes or 2 Kbytes). In this case, the so-called affinity between the optical disc and the picture item is increased, and the speed of the reading / writing process of the picture item with respect to the optical disc can be increased.

  In addition, the system item described above, and the sound item and auxiliary item described later, as well as the picture item, adopt the KLV structure and have a fixed data length based on KAG. .

  In the sound item, audio data for one frame in the video data frame arranged in the picture item is arranged in the KLV structure as in the case of the picture item described above.

  Also, a plurality of, for example, 8-channel audio data is multiplexed and arranged in the sound item.

  That is, in the sound item, the value of the KLV structure includes the element header EH (Element Header), the audio sample count ASC (Audio Sample Count), the stream valid flag SVF (Stream Valid Flags), and the multiplexed 8 from the beginning. Channel audio data is arranged sequentially.

  Here, in the sound item, 8-channel audio data is multiplexed by arranging the audio data samples in the order of the first sample, the second sample,. It has become. In the audio data shown at the bottom of FIG. 32, the numbers shown in parentheses indicate the number of samples of the audio data.

  The element header EH is arranged with data for specifying the element header. In the audio sample count ASC, the number of samples of audio data arranged in the sound item is arranged. The stream valid flag SVF is an 8-bit (1 byte) flag, and each bit represents whether the audio data of the channel corresponding to the bit is valid or invalid. That is, each bit of the stream valid flag SVF is set to, for example, 1 when the audio data of the channel corresponding to the bit is valid, and is set to 0, for example, when the audio data is invalid.

  Necessary user data is arranged in the auxiliary item. Therefore, the auxiliary item is an area where the user can arrange arbitrary data.

  As described above, in the standard AV multiplex format, a system item in which metadata in units of frames is arranged, a picture item in which video data is arranged, a sound item in which audio data is arranged, and an auxiliary in which user data is arranged. The items are multiplexed in units of one frame, and further, in the sound item, 8-channel audio data is multiplexed in units of one sample.

  It should be noted that the newly created package and reference relationship table 411 and the updated editing description by this package generation process are uploaded to the corresponding server, as in the case of the configuration table described above. They are registered in the database corresponding to each data or used for updating the table. Since these processes are the same as in the case of the configuration table described above, the description thereof is omitted. The campaign is uploaded to the campaign server 52 and registered in the campaign database 62.

  When a campaign is generated from the edit list in this way, the UMID of the campaign is added to the campaign. Also, information for referring to the campaign from the edit description is managed as a reference relationship table 66 by the metadata server 53. Since the UMID of this campaign and the UMID of the edit list (edit description) have a one-to-one relationship, in this case, the metadata server 53 refers to the reference UMID (the UMID of the campaign) as described later. It is also possible to search for the original UMID (UMID in the edit list).

  Therefore, each terminal device can easily acquire the UMID of the package corresponding to the edit list based on the UMID of the edit list by using the reference relation table 66 managed by the metadata server 54. Can do. Conversely, each terminal device can easily obtain the UMID of the edit list corresponding to the campaign using the UMID of the campaign. In other words, the metadata server 53 can easily search and provide the UMID of the package corresponding to the edit list from the UMID of the edit list by using the reference relationship table 66, and conversely, It is also possible to easily search for and provide the UMID of the edit list corresponding to the campaign from the UMID. In other words, the network system 1 can easily perform data editing processing and confirmation processing, for example, by facilitating association between data and easily searching the other data from one data. For example, the convenience of data can be improved.

  In the above description, as illustrated in FIG. 33, the editing terminal device 41 has been described so as to perform the work of adding an effect and the work of generating a campaign separately. That is, the editing terminal device 41 first executes the effect editing process of FIG. 25, and performs the operation 431 of adding an effect to the edit list using the material data (material data A to D) and the edit list 432. Next, it has been described that the campaign generation process of FIG. 30 is executed, and the operation 433 for generating a campaign is performed using the edit list generated in the operation 431 to generate the campaign 434.

  However, in addition, the editing terminal device 41 directly performs the main editing on the material data (material data A to D), for example, as shown in FIG. 34, and adds the effect to the edit list. However, as a matter of course, the processing 441 may be performed so as to generate a package using the material data. That is, the editing terminal device 41 may generate the campaign 443 by executing the effect editing process of FIG. 25 and the campaign generation process of FIG. 30 as one process.

  As described above, each device performs processing, and the reference relationship of each data becomes as shown in FIG.

  35, in the configuration table 451, the UMID (AAAAAAAA to FFFFFFFF) of the material data 452 is added in addition to its own UMID (PPPPPPPP), and each terminal device uses the configuration table 451 to add the configuration table 451. The material data 452 corresponding to 451 can be easily acquired. Each of the material data 452 is added with its own UMID (AAAAAAAA to FFFFFFFF). In addition to the self UMID (MMMMMMMM), the UMID (PPPPPPPP) of the configuration table 451 and the UMID of material data (AAAAAAAA to FFFFFFFF) are added to the edit list 453 created based on the configuration table 451. Each terminal device can easily obtain the configuration table 451 and the material data 452 corresponding to the edit list 453 using the edit list 453.

  In addition to the self UMID (LLLLLLLL), the UMID (AAAAAAAA to FFFFFFFF) of the material data 452 and the UMID (MMMMMMMMM) of the original edit list 453 are added to the edit list with effect 454 to which the effect is added to the edit list. Each terminal device can easily acquire the material data 452 and the edit list 453 corresponding to the effected edit list 454 using the effected edit list 454.

  Further, the metadata server 53 creates and manages a reference relationship table 66 as shown in FIG. 36 using the reference relationship table supplied from each terminal device. The metadata server 53 uses this reference relationship table 66 to search for a UMID corresponding to the UMID supplied by each terminal device, and supplies it to the requesting terminal device.

  Accordingly, each terminal device uses the reference relationship table 66 managed by the metadata server 53 to change the UMID of the material data 452 in FIG. 35 and the UMID and edit list 453 of the configuration table 451 corresponding to the material data 452. And the UMID of the edit list with effect 453 can be acquired. Similarly, each terminal device may acquire the UMID of the edit list 453 corresponding to the configuration table 451 from the UMID of the configuration table 451 using the reference relationship table 66 managed by the metadata server 53. From the UMID of the list 453, the UMID of the edit list with effect 454 corresponding to the edit list 453 can also be acquired.

  Furthermore, each terminal device acquires the UMID (ZZZZZZZZ) of the package 455 corresponding to the effected edit list 454 from the UMID of the effected edit list 454 using the reference relation table 66 managed by the metadata server 53. You can also Since the relationship between the edit list with effect 454 UMID and the UMID of the package 455 corresponding to the edit list 454 is one-to-one, each terminal device has a reference relationship table 66 managed by the metadata server 53. By using the UMID of the campaign 455, the UMID of the edit list with effect 454 corresponding to the campaign 455 can be acquired.

  As described above, the flow of processing in which each terminal device acquires a UMID using the reference relationship table 66 managed by the metadata server 53 will be described with reference to the flowchart of FIG.

  In FIG. 37, a case where the field PC 32 acquires a UMID will be described as an example of a terminal device.

  The CPU 151 of the field PC 32, in which the reference source UMID is designated by the operator's instruction or the like and the request for the reference destination UMID corresponding to the reference source UMID is instructed, executes the data acquisition and supply program 163. In step S271, the communication unit In step 164, the reference source UMID is supplied to the metadata server 53 via the network 21.

  When the CPU 351 of the metadata server 53 that executes the data acquisition / supply program 371 acquires the reference source UMID in step S281, the CPU 351 executes the reference relationship table management program 372 in step S282. To supply. In step S291, the CPU 351 that executes the reference relationship table management program 372 acquires the reference source UMID. More specifically, when the CPU 351 executes the processing of the data acquisition / supply program 371 and acquires the reference source UMID, the CPU 351 supplies the reference source UMID to the RAM 353 and holds it. Next, the CPU 351 executes the processing of the reference relationship table management program 372 and acquires the reference source UMID held in the RAM 353.

  Upon obtaining the reference source UMID, the CPU 351 that executes the reference relationship table management program 372 advances the processing to step S292, refers to the reference relationship table 66 stored in the storage unit 363, and in step S293, the reference relationship table In 66, a reference source UMID is searched, and a reference destination UMID corresponding to the reference source UMID is extracted and acquired.

  The CPU 351 that executes the reference relationship table management program 372 that has acquired the reference destination UMID supplies the reference destination UMID to the CPU 351 that executes the data acquisition and supply program 371 in step S294. The CPU 351 that executes the data acquisition / supply program 371 acquires the reference destination UMID in step S283. Specifically, in step S294, the CPU 351 executes the reference relationship table management program 372, supplies the reference destination UMID to the RAM 353, and holds it. Then, the CPU 351 executes the data acquisition / supply program 371 and acquires the reference destination UMID held in the RAM 353 in step S283.

  In step S284, the CPU 351 that executes the data acquisition and supply program 371 that has acquired the reference destination UMID controls the communication unit 364 and supplies it to the field PC 32 that is the request source. The CPU 151 of the field PC 32 that executes the data acquisition / supply program 173 controls the communication unit 164, and acquires the reference destination UMID in step S272.

  As described above, the field PC 32 supplies the reference source UMID to the metadata server 53 and acquires the reference destination UMID. It should be noted that other terminal devices such as the planning terminal device 11 also obtain the reference destination UMID from the metadata server 53 by performing the same processing as in the case of the field PC 32 described above.

  In addition, as described above, the UMID of the edit list to which the effect is added (the edit list for generating the campaign) and the UMID of the campaign are associated one-to-one in the reference relationship table 66. Therefore, when each terminal apparatus acquires the UMID of the edit list to which the effect is added from the UMID of the campaign, the terminal device supplies the UMID of the campaign that is the reference destination UMID to the metadata server 53, and the reference relation table of the metadata server 53 66, the UMID of the edit list which is the reference source UMID is acquired.

  In this case, the processing procedure of each device is described with reference to the flowchart of FIG. 37. In the processing for obtaining the reference destination UMID from the reference source UMID, the reference source UMID is replaced with the reference destination UMID, and the reference destination UMID is replaced with the reference source UMID. Since it is the same as the case where it replaces with, the description is omitted.

  As described above, in the production of a program (content data), a configuration table is created in the first step, and operations such as data generation and editing are performed based on the configuration table. Therefore, it may be possible to manage each piece of data generated at the time of production of a program and associate them with each other using a configuration table. There is a fear.

  More specifically, the configuration table is hierarchically structured as described above. As shown in FIG. 38, the hierarchy above the scene hierarchy (the upper hierarchy of the configuration table) is a description such as a memo or a plan. Since it is composed of only and is not directly linked to data, it is treated in the same manner in all processes. However, as shown in FIG. 38, in the cut hierarchy to which take data (material data) is linked, the method of using the material data changes depending on the progress of the process. For example, in the process of planning and recording (covering), as the main work, cut planning by time division is performed, so the operator specifies and refers to the material data with the UMID described in the configuration table, UMID ( Cut / take designation by reference to the material), but in the editing and browsing process, cut designation by time division is performed as the main work, so cut / take designation by the edit list (edit description) without using the configuration table I do.

  That is, the configuration table is only an initial plan table, and only a rough cut flow is designated. Therefore, for example, a state where the above-described effect is added, such as a campaign, is not considered. Therefore, if a fine cut is made later in the production of a program, it is more accurate for an operator to use an edit list (edit description) including the editing information than to refer to the composition table. Material data can be referred to.

  A specific example of referring to the material data is shown in FIG. In FIG. 39, for simplification of explanation, the UMID is represented by a 4-character string, but this UMID is the same as the UMID represented by, for example, the 8-character string shown in FIG. Information is actually 32 bytes (or 64 bytes) of information.

  As shown in FIG. 39, there are a campaign 471, an edit list 472, a configuration table 473, and material data 474 generated when a program is produced, and they are associated with each other by UMID as described above. And With respect to such data, a case will be described in which the operator of the editing terminal device 41 views the package 471 and refers to the frame of the material data corresponding to the frame by designating the frame of the package 471. .

  When the operator designates the frame “X” of “Cut C” at this time, the editing terminal device 41 obtains the time code of the frame “X”, refers to the edit list 472 based on the time code, The frame “Y” corresponding to the frame “X” of the campaign 471 is searched and specified. Then, the editing terminal device 41 identifies the UMID “CCCC” of the material data 474 in which the frame “Y” of the edit list 472 exists and the time code in the material data of the frame “Y”. The editing terminal device 41 that has identified the UMID refers to the target material data from the material data 474 using the UMID, and the frame “Z” of the material data (UMID = CCCC) corresponding to the identified time code. Is identified and the image is displayed.

  By using the edit list 472 in this way, the editing terminal device 41 can more easily and more accurately send the frame image of the material data 474 corresponding to the frame image specified in the campaign 471 to the operator. Can be provided.

  Further, when the operator designates a frame in the package 471 and refers to the configuration table corresponding to the frame, as described above, the frame “Y” in the edit list 472 corresponding to the frame “X” of the package is specified. Then, the editing terminal device 41 refers to the configuration table 473 and, based on the time code, the frame “W” of the configuration table corresponding to the frame “Y” is included in “Cut 1” of “Scene 2”. Specify that the frame is Then, the editing terminal device 41 presents the information of “Cut 1” of “Scene 2” in the identified configuration table 473 to the operator.

  By using the edit list 472 in this way, the editing terminal device 41 provides the operator with information on the configuration table 473 corresponding to the frame specified in the campaign 471 more easily and more accurately. be able to.

  Next, with reference to the flowchart of FIG. 40, the above-described processing for referring to material data from a package by the editing terminal device 41 will be described.

  For example, when an operator of the editing terminal device 41 operates the input unit 211 to instruct to display a campaign in a material data reference mode that can perform the above-described processing, the CPU 201 causes the material reference program 225 to be displayed. This is executed to start material data reference processing as shown in the flowchart of FIG. In order to simplify the description, it is assumed that the terminal device 41 has previously acquired a campaign to be processed from the campaign database 62 of the campaign server 52.

  The CPU 201 that has started the material data reference process first controls the output unit 212, and displays the campaign acquired in advance from the package server 52 on the monitor in step S311. Then, the CPU 201 controls the input unit 211 and starts accepting input from the worker.

  In step S312, the CPU 201 controls the input unit 211 to determine whether or not a frame to be referred to is designated by the worker. If it is determined that the frame is designated, the process proceeds to step S313, and the communication unit 214 is controlled. Then, the UMID of the package with the designated frame is supplied to the metadata server 53, and the UMID of the edit list is requested. In this case, the UMID of the supplied package is the reference destination UMID, and the UMID of the requested edit list is the reference source UMID. As described with reference to the flowchart of FIG. 37, the metadata server 53 uses the reference relationship table 66 to search the UMID of the edit list as the reference source UMID corresponding to the UMID of the campaign as the reference destination UMID. Then, it is supplied to the editing terminal device 41.

  In step S314, the CPU 201 of the editing terminal device 41 that executes the material reference program 225 controls the communication unit 214 to determine whether or not the requested UMID of the edit list has been acquired. If it is determined that the UMID of the edit list has been acquired, the CPU 201 advances the processing to step S315, controls the communication unit 214, and this time supplies the UMID of the edit list to the metadata server 53 so that the edit list is obtained. Request. As in the case of the configuration table described with reference to the flowchart of FIG. 13, the metadata server 53 searches the edit description database 63 for the requested edit list using the UMID, and uses it to edit the editing terminal device. 41.

  In step S316, the CPU 201 of the editing terminal device 41 that executes the material reference program 225 controls the communication unit 214 to determine whether or not the requested edit list has been acquired. If it is determined that the edit list has been acquired, the CPU 201 advances the process to step S317, refers to the acquired edit list, and based on the time code of the specified frame, the UMID of the material data corresponding to the specified frame And the time code in the material data is specified.

  When the UMID of the material data and the time code in the material data are specified, the CPU 201 controls the communication unit 214 in step S318, supplies the UMID of the material data to the material data server 51, and requests the material data. . The material data server 51 performs the same processing as the metadata server 53 that provides the configuration table described with reference to the flowchart of FIG. 13, and the material data requested from the material data database 61 using the UMID. And is supplied to the editing terminal device 41.

  In step S319, the CPU 201 of the editing terminal device 41 that executes the material reference program 225 controls the communication unit 214 to determine whether the requested material data has been acquired. When determining that the UMID of the material data has been acquired, the CPU 201 advances the processing to step S320, controls the output unit 212, and displays the frame of the specified time code of the acquired material data. Thus, the operator can refer to the frame image of the material data corresponding to the designated campaign frame. When the process of step S320 ends, the CPU 201 advances the process to step S322.

  If it is determined in step S <b> 312 that the worker has not designated a package frame referring to the material data, the CPU 201 advances the process to step S <b> 322. If it is determined in step S314 that the UMID of the edit list has not been acquired, the CPU 201 advances the process to step S321, performs an error process, displays an error message, etc., and then advances the process to step S322. . Similarly, when it is determined in step S316 that an edit list has not been acquired, or when it is determined in step S319 that material data has not been acquired, the CPU 201 proceeds to step S321 and performs error processing. After that, the process proceeds to step S322.

  In step S322, the CPU 201 determines whether or not to end the material data reference process. If it is determined not to end the process, the CPU 201 returns the process to step S312 and repeats the subsequent processes. If it is determined in step S322 that the material data reference process is to be ended, for example, by an instruction from the operator, the CPU 201 proceeds to step S323, performs the end process, and then performs the material data reference process. finish.

  As described above, when the editing terminal device 41 executes the material data reference process, the operator can easily refer to the frame image of the material data corresponding to the frame specified by the campaign. That is, even if the data at the reference destination is not directly related to the data at the reference source, the worker can easily refer to the data at the reference destination as long as it is indirectly related through other data. be able to.

  In the above description, it has been described that the edit list is acquired from the UMID of the campaign by two steps, such as requesting the edit list UMID in step S313 and requesting the edit list in step S315. For example, the edit list may be requested directly from the UMID of the campaign and acquired. In this case, the CPU 351 of the metadata server 51 specifies the UMID of the edit list from the UMID of the campaign using the reference relationship table, and uses the UMID of the edit list from the editing description database 63, as in the case described above. The edit list is searched, and the searched edit list is supplied to the editing terminal device 41.

  In the above, the case where the worker refers to the material data based on the campaign has been described. However, the present invention is not limited to this. For example, the material data can be referred to from the edit list, or the edit list can be referred to from the campaign. You can also In such a case, the CPU 201 of the editing terminal device 41 provides the target data to the worker by executing a part of the processing shown in the flowchart of FIG. In addition, by performing processing by changing the order and direction of processing, the CPU 201 of the editing terminal device 41 can also refer to the campaign and edit list from the material data.

  Further, as described above, the operator can refer to the configuration table based on the package. The processing flow in that case will be described with reference to the flowchart of FIG.

  For example, when the operator of the editing terminal device 41 operates the input unit 211 to instruct to display the campaign in the configuration table reference mode that can perform the above-described processing, the CPU 201 displays the configuration table reference program 226. To start the configuration table reference process as shown in the flowchart of FIG. In order to simplify the description, it is assumed that the terminal device 41 has previously acquired a campaign to be processed from the campaign database 62 of the campaign server 52.

  The CPU 201 that has started the configuration table reference process first controls the output unit 212, and displays the campaign acquired in advance from the campaign server 52 on the monitor in step S341. Then, the CPU 201 controls the input unit 211 and starts accepting input from the worker.

  In step S342, the CPU 201 controls the input unit 211 to determine whether or not the operator has instructed to refer to the configuration table. If it is determined that the instruction has been received, the process proceeds to step S343, and the communication unit 214 is set. The UMID of the campaign with the frame specified is supplied to the metadata server 53, and the UMID of the edit list is requested. In this case, the UMID of the supplied package is the reference destination UMID, and the UMID of the requested edit list is the reference source UMID. As described with reference to the flowchart of FIG. 37, the metadata server 53 uses the reference relationship table 66 to search the UMID of the edit list as the reference source UMID corresponding to the UMID of the campaign as the reference destination UMID. Then, it is supplied to the editing terminal device 41.

  In step S344, the CPU 201 of the editing terminal device 41 that executes the configuration table reference program 226 controls the communication unit 214 to determine whether the requested edit list UMID has been acquired. When it is determined that the UMID of the edit list has been acquired, the CPU 201 advances the process to step S345, controls the communication unit 214, and supplies the UMID of the edit list to the metadata server 53 this time. Request. As in the case of the configuration table described with reference to the flowchart of FIG. 13, the metadata server 53 searches the edit description database 63 for the requested edit list using the UMID, and uses it to edit the editing terminal device. 41.

  In step S346, the CPU 201 of the editing terminal device 41 that executes the configuration table reference program 226 controls the communication unit 214 to determine whether the requested edit list has been acquired. If it is determined that the edit list has been acquired, the CPU 201 advances the processing to step S347, and determines whether or not the UMID of another edit list is described in the acquired edit list edit description. If it is determined that the UMID of another edit list is described, the acquired edit list is an edit list generated by editing another edit list in which the UMID is described. Not directly associated. Therefore, in this case, the CPU 201 returns the process to step S345 and repeats the subsequent processes in order to acquire other edit lists.

  As described above, the processes from step S345 to step S347 are repeated to obtain the first edit list, that is, the edit list associated with the configuration table. The edit list associated with the composition table does not describe the UMIDs of the other edit lists, but describes the UMIDs of the composition table. Therefore, in step S347, the CPU 201 describes the other edit lists. If not, the process proceeds to step S348, the communication unit 214 is controlled, the UMID of the configuration table described in the edit description is supplied to the metadata server 53, and the configuration table is requested. As described with reference to the flowchart of FIG. 13, the metadata server 53 searches the configuration table database 64 for the requested configuration table using the UMID, and supplies it to the editing terminal device 41.

  In step S349, the CPU 201 of the editing terminal device 41 that executes the configuration table reference program 226 controls the communication unit 214 to determine whether or not the requested configuration table has been acquired. If it is determined that the configuration table has been acquired, the CPU 201 advances the processing to step S350, and displays the portion (or the entire configuration table) corresponding to the frame specified by the user in the acquired configuration table. Thus, the worker can refer to the configuration table corresponding to the designated campaign frame. When the process of step S350 ends, the CPU 201 advances the process to step S352.

  If it is determined in step S342 that the worker has not designated a package frame that refers to the configuration table, the CPU 201 advances the process to step S352. Also, when it is determined in step S344 that the UMID of the edit list has not been acquired, when it is determined that the edit list has not been acquired in step S346, or when it is determined that the configuration table has not been acquired in step S349 The CPU 201 advances the processing to step S351, performs error processing, displays an error message, etc., and then advances the processing to step S352.

  In step S352, the CPU 201 determines whether or not to end the configuration table reference process. If the CPU 201 determines not to end the process, the process returns to step S342, and the subsequent processes are repeated. If it is determined in step S352 that the configuration table reference process is to be terminated, for example, as instructed by an operator, the CPU 201 advances the process to step S353, performs the termination process, and then performs the configuration table reference process. finish.

  As described above, when the editing terminal device 41 executes the configuration table reference process, the operator can easily refer to the configuration table corresponding to the frame specified by the campaign. That is, even if the data at the reference destination is not directly related to the data at the reference source, the worker can easily refer to the data at the reference destination as long as it is indirectly related through other data. be able to.

  In this case as well, the CPU 201 may request and obtain the edit list directly from the UMID of the campaign. In addition, the configuration table can be referred to from the edit list, and the edit list can also be referred to from the campaign. In such a case, the CPU 201 of the editing terminal device 41 provides the target data to the worker by executing a part of the processing shown in the flowchart of FIG. In addition, by performing processing by changing the order and direction of processing, the CPU 201 of the editing terminal device 41 can also refer to the campaign and edit list from the configuration table.

  Further, the above-described material data reference processing and configuration table reference processing can be realized not only by the editing terminal device 41 but also by other terminal devices by performing the same processing.

  As described above, each device of the network system 1 facilitates the association between data, and can easily retrieve the other data from one data. For example, the data editing process and the confirmation process are performed. The convenience of data can be improved by making it easy to do so.

  In the network system 1 of FIG. 1, the material data and the package are described as being managed by the server such as the material data server 51 and the package server 52, but the present invention is not limited to this. For example, FIG. As described above, an operator may record the data on a recording medium such as an optical disk and move the recording medium between apparatuses.

  In the network system 501 of FIG. 42, the imaging device 531 records material data obtained by coverage on the optical disc 551. After the field PC 32 or the like has processed the material data, the operator mounts the optical disk 551 on which the material data is recorded on the drive 215 or the like of the editing terminal device 541 of the editing group 40, and loads the material data. This is provided to the editing terminal device 541.

  That is, since the data is associated using the UMID, the association of each data is maintained regardless of the data address. Therefore, like the network system 1 in FIG. 1 and the network system 501 in FIG. 42, the association method described above can be made to correspond to various data management methods. That is, in addition to the above, for example, the material data and the package may be exchanged between the terminal devices via the network 21 without passing through the server, and it is a function of the metadata server 53. The edit description database 63, the configuration table database 64, the metadata database 65, and the reference relationship table 66 may be managed in different servers, or a part or all of them may be managed in a predetermined terminal device. You may make it do.

  A part of the configuration of each device described above may be configured as a separate body, or the configuration described as different processing units may be formed integrally. In addition, the name and configuration of each segment in the configuration table may be other than those described above, and any type of hierarchical structure such as “program”, “episode”, “scene”, and “cut” may be used. It may be.

  In the above description, it has been explained that the mutual UMID is not added between the campaign and the edit list with effect for generating the campaign. That is, for example, as shown in FIG. 35, the UMID of the package 455 is not added to the effect edit list 454, and the UMID of the effect edit list 454 is not added to the package 455. When the effective edit list 454 is acquired from the campaign 455 or when the campaign 455 is acquired from the effective edit list 454, each terminal device has a reference relationship managed by the metadata server 53 as shown in FIG. It has been described that acquisition is performed using the table 66.

  However, other than this, for example, in FIG. 35, the UMID of the edit list with effect 454 may of course be added to the package 455. In that case, in step S253, the CPU 201 of the editing terminal device 41 creates a UMID of the generated campaign and adds it to the campaign, and also adds the UMID of the edit list with effect to the campaign. Note that the UMID of the edit list with effect is also added to the header metadata 422 in FIG. 32, as in the case of the UMID of the campaign. At this time, the UMID of the package that is the self-UMID may be the UMID of the material package indicating the package, and the UMID of the edit list with effect may be the UMID of the file package.

  Therefore, in this case, when acquiring the edit list with effect from the campaign, each terminal device acquires the edit list with effect using the UMID of the edit list with effect added to the campaign, and the campaign list from the edit list with effect. Is acquired using the reference relationship table 66 managed by the metadata server 53 as in the case described above. In this way, when acquiring an effected edit list from a package, each terminal device can reverse the reference relationship table 66 managed by the metadata server 53 as described above (from the UMID on the reference destination side). It is possible to obtain the edit list with effect without searching the UMID on the reference source side).

  At this time, it is also possible to add an effect edit list as “dark metadata” that can be identified only by a specific user in the header metadata of the campaign.

  The series of processes described above can be executed by hardware or can be executed by software. When the above-described series of processing is executed by software, a program constituting the software is installed from a network or a recording medium.

  For example, as shown in FIGS. 2 to 8, this recording medium is a magnetic disk (including a floppy disk) on which a program is recorded, which is distributed to distribute the program to the user separately from the apparatus main body. Removable media 86, removable media including optical disks (including CD-ROM (compact disk-read only memory), DVD (digital versatile disk)), magneto-optical disks (including MD (mini-disk)), or semiconductor memory A program is recorded that is not only configured by the media 126, the removable media 166, the removable media 216, the removable media 266, the removable media 316, or the removable media 366, but is delivered to the user in a state of being pre-installed in the apparatus main body. ROM72, ROM112, ROM152, ROM202, ROM 52, ROM 302 or ROM352, or, storage unit 83, a storage unit 123, a storage unit 163, a storage unit 213, a hard disk included in the storage unit 313 or the storage unit 363,.

  In the present specification, the step of describing the program recorded on the recording medium is not limited to the processing performed in chronological order according to the described order, but is not necessarily performed in chronological order. It also includes processes that are executed individually.

  Further, in this specification, the system represents the entire apparatus constituted by a plurality of apparatuses.

It is a block diagram which shows the structural example of the network system to which this invention is applied. It is a block diagram which shows the structural example of the terminal device for planning of FIG. It is a block diagram which shows the structural example of the imaging device of FIG. It is a block diagram which shows the structural example of the field PC of FIG. It is a block diagram which shows the structural example of the terminal device for editing of FIG. It is a block diagram which shows the structural example of the material data server of FIG. It is a block diagram which shows the structural example of the campaign server of FIG. It is a block diagram which shows the structural example of the metadata server of FIG. It is a flowchart explaining the example of the flow of a process of the whole program production. It is a flow chart explaining an example of composition table new creation processing. It is a schematic diagram which shows the structural example of a structure table. It is a schematic diagram which shows the structural example of the general metadata of metadata. It is a flowchart explaining the flow of the process regarding registration of a structure table. It is a flowchart explaining the example of an imaging process. It is a schematic diagram explaining the example of the produced | generated video file and take metadata. It is a flowchart explaining the example of a take data correlation process. It is a schematic diagram explaining the state of take data linking. It is a figure which shows the structural example of a reference relationship table. It is a flowchart explaining the example of the process regarding the update of a reference relationship table. It is a flowchart explaining the example of a rough edit process. It is a schematic diagram explaining the example of the structure table | surface in which the rough edit process was performed. It is a flowchart explaining the example of an edit list creation process. It is a figure which shows the other structural example of a reference relationship table. It is a figure which shows the example of a description of an edit description. It is a flowchart explaining the example of an effect edit process. It is a figure which shows the other structural example of a reference relationship table. It is a figure which shows the example of a description of an edit description. It is a figure explaining the mode of a wipe effect. It is a figure explaining the mode of a wipe effect. It is a flowchart explaining the example of a campaign production | generation process. It is a figure which shows the other structural example of a reference relationship table. It is a figure explaining the structural example of a campaign. It is a figure explaining the example of the flow of an effect edit process and a package generation process. It is a figure explaining the other example of the flow of an effect edit process and a package production | generation process. It is a figure explaining the relation of the association of each data. It is a figure explaining the structural example of the reference relationship table managed in a metadata server. It is a flowchart explaining the example of the flow of a process regarding acquisition of reference destination UMID. It is a figure explaining the mode of the reference method of the cut layer in a structure table. It is a figure explaining the specific example of the reference method between each data. It is a flowchart explaining the example of material data reference processing. It is a flowchart explaining the example of a structure table reference process. It is a block diagram which shows the other structural example of the network system to which this invention is applied.

Explanation of symbols

  DESCRIPTION OF SYMBOLS 1 Network system 11 Planning terminal device 31 Imaging device, 32 Field PC, 41 Editing terminal device, 51 Material data server, 52 Campaign server, 53 Metadata server, 61 Material data database, 62 Campaign database, 63 Editing description database, 64 composition table database, 65 metadata database, 66 reference relation table, 91 composition table creation and editing program, 92 data acquisition supply program, 131 imaging recording control program, 132 metadata generation program, 133 data acquisition supply program, 171 configuration table string Attaching program, 172 coarse editing program, 173 data acquisition and supply program, 221 edit list generation program, 222 effect editing program Gram, 223 Campaign generation program, 224 Data acquisition supply program, 225 Material reference program, 226 Composition table reference program, 271 Material data acquisition supply program, 321 Campaign acquisition supply program, 371 Data acquisition supply program, 372 Reference relationship table management program, 381 configuration table, 382 metadata, 383 material data, 391 and 393 reference relationship table, 394 description example, 395 reference relationship table, 396 description example, 411 reference relationship table, 423 UMID of CAMERA, 501 network system, 531 imaging device, 541 Terminal device for editing

Claims (15)

From the editing information including the editing content of the material data constituting the content data, the identification information of the material data including the partial data of the desired time code in the completed data as the content data corresponding to the editing information, and the material data A specifying means for specifying a time code of the partial data;
Material data acquisition means for acquiring the material data using identification information of the material data specified by the specifying means;
An information processing apparatus comprising: output means for outputting the partial data of the material data acquired by the material data acquisition means corresponding to a time code in the material data specified by the specifying means. Using the identification information of the completion data, identification information acquisition means for acquiring identification information of the editing information;
Edit information acquisition means for acquiring edit information corresponding to the completed data using the identification information of the edit information acquired by the identification information acquisition means, and
The information processing apparatus according to claim 1, wherein the specifying unit specifies identification information of the material data and a time code of the partial data in the material data from the editing information acquired by the editing information acquisition unit. Further comprising designation accepting means for accepting designation of a desired time code in the completed data;
The identification information acquisition means acquires identification information of the editing information using the identification information of the completion data for which the designation of the time code has been accepted by the designation acceptance means,
The editing information acquisition means uses the identification information of the editing information to acquire editing information corresponding to the completion data,
The specifying means includes, from the editing information acquired by the editing information acquiring means, identification information of material data including partial data of a time code designated by the designation receiving means, and the partial data in the material data The information processing apparatus according to claim 2, wherein a time code is specified. Identification means for identifying material data including partial data of a desired time code in completed data as content data corresponding to the editing information from editing information including editing contents of material data constituting the content data, and Specify the time code of the partial data in the material data,
Material data acquisition means acquires the material data using the identification information of the material data specified by the specifying means,
An information processing method, wherein the output means outputs the partial data of the material data acquired by the material data acquisition means corresponding to a time code in the material data specified by the specifying means. Computer
From the editing information including the editing content of the material data constituting the content data, the identification information of the material data including the partial data of the desired time code in the completed data as the content data corresponding to the editing information, and the material data A specifying means for specifying a time code of the partial data;
Material data acquisition means for acquiring the material data using identification information of the material data specified by the specification means;
A program for functioning as an output means for outputting the partial data of the material data acquired by the material data acquisition means corresponding to a time code in the material data specified by the specifying means. Identification information obtaining means for obtaining identification information of editing information corresponding to the completion data and including editing contents of material data constituting the content data, using identification information of the completion data as content data When,
An information processing apparatus comprising: edit information acquisition means for acquiring edit information corresponding to the completion data using the identification information of the edit information acquired by the identification information acquisition means. The information processing apparatus according to claim 6, further comprising a material data acquisition unit that acquires the material data using identification information of the material data included in the editing information acquired by the editing information acquisition unit. The apparatus further includes a configuration table acquisition unit that acquires the configuration table using identification information of the configuration table that is information related to the content data production plan included in the editing information acquired by the editing information acquisition unit. Item 7. The information processing device according to Item 6. A determination unit that determines whether the editing information acquired by the editing information acquisition unit includes identification information of other editing information;
The information processing apparatus according to claim 8, wherein the configuration table acquisition unit acquires the configuration table when the determination unit determines that the editing information does not include identification information of the other editing information. . The identification information acquisition means uses the identification information of the completed data as content data, and edit information corresponding to the completed data, the identification information of the editing information including the editing content of the material data constituting the content data. Acquired,
An information processing method in which editing information acquisition means acquires editing information corresponding to the completion data using identification information of the acquired editing information. Computer
Identification information obtaining means for obtaining identification information of editing information corresponding to the completion data and including editing contents of material data constituting the content data, using identification information of the completion data as content data ,
A program for functioning as edit information acquisition means for acquiring edit information corresponding to the completion data using the identification information of the edit information acquired by the identification information acquisition means. Composition table acquisition means for acquiring the composition table using identification information of the composition table, which is information related to the production plan of the content data, included in the editing information including the editing contents of the material data constituting the content data. Information processing device. A determination means for determining whether or not identification information of other editing information is included in the editing information;
The information processing apparatus according to claim 12, wherein the configuration table acquisition unit acquires the configuration table when the determination unit determines that the editing information does not include identification information of the other editing information. . The composition table obtaining means obtains the composition table using identification information of the composition table, which is information related to the production plan of the content data, included in the editing information including the edited contents of the material data constituting the content data. Information processing method. Computer
Functions as a configuration table acquisition means for acquiring the configuration table by using the identification information of the configuration table, which is information related to the production plan of the content data, included in the editing information including the editing content of the material data constituting the content data Program to let you.

Images