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

Description

  The present invention relates to an information processing apparatus and method, and a program, and more particularly, for example, an information processing apparatus and method, and a program capable of more easily performing destructive editing of content data correctly according to the user's intention. About.

  Conventionally, when content data such as image data and audio data is recorded on a tape device as a recording medium in a VTR (Video Tape Recorder), usually only the content data is recorded on the tape device. For example, metadata such as a time code may be added to the content data, but this metadata is recorded linearly along the time axis with the content data in the tape device. Therefore, when editing such as rewriting a part of the content data is performed, only the portion of the metadata corresponding to (associated with) the editing portion of the content data is updated.

  On the other hand, in recent years, there is a method of recording content data such as image data and audio data in a non-linear manner using a recording medium that can be randomly accessed such as an optical disk or a hard disk (for example, see Patent Document 1). In this case, each recorded content data is managed as a file (clip) by the file system, and their recording position (recording order) is not necessarily on the time axis.

  For example, in the case of a television program composed of video and audio, the content data is managed as a set of a plurality of files such as an image file, an audio file, and a metadata file. At this time, metadata as information for managing and reproducing these files is also generated. That is, when content data is recorded non-linearly in this way, more metadata is added to the content data than in the case of VTR.

  For example, when image data to which time code information is added as metadata for each frame is recorded on a randomly accessible medium such as an optical disc, the time code of all frames of the image data can be easily managed. Table information indicating the relationship between the time code and the frame is generated as new metadata. The time code information added to each frame only directly indicates the value of the time code of each frame, and does not include information indicating the time code of another frame from each time code information. Therefore, for example, when a user reproduces an arbitrary frame using a time code, the user grasps the time code of all the frames in advance or the reproduction apparatus adds metadata (time code information) to each frame. ) One by one and it is necessary to search for the frame of the time code specified by the user.

  Therefore, when recording image data, the recording device extracts, for example, a frame in which the method of changing the value of the time code information changes, and generates table information composed of the frame number of the frame and the value of the time code. By doing so, the frame can be easily calculated from the time code. The recording apparatus adds such table information as new metadata to the image data and records it together with the image data.

  In the conventional case, in editing data recorded nonlinearly in this way, the editing device does not update the original data to be edited, but includes information indicating the editing content (information from which the editing result can be derived). A new file was created (non-destructive editing was done).

JP 2001-292421 A

  However, in such non-destructive editing, a new file is generated as the editing result while leaving the original data. For example, in the case of editing in which part of the content data is overwritten with other content data, There is a possibility that the recording area of the recording medium is unnecessarily consumed.

  Therefore, even in the case of a recording medium for recording content data in a non-linear manner such as an optical disk, it is required to perform “destructive editing” that actually updates the content data to be edited, as in the case of VTR. It is becoming.

  However, in this case, for example, as described above, when image data in which time code information is added to each frame as metadata is destructively edited, the time described above is obtained only by updating the image data and the time code information. There is a problem that inconsistency may occur in table information related to code information.

  In addition, the time code information may include not only a time address indicating a time to be a so-called time code but also a user bit that allows the user to input arbitrary information.

  In the user bit, for example, marking information including information such as characteristics and roles of the frame image is inserted as a mark of the frame. In other words, the playback device (user) refers to the user bits of the time code information added to the frame at the time of playback of the image data, and easily grasps what the frame is from the contents of the marking information. can do. In addition, information indicating a recording medium on which image data is recorded (for example, a reel number when the recording medium is a tape device) may be inserted into the user bit. In this case, the playback device (user) can easily determine on which recording medium the image data is recorded by referring to the user bits of the time code information added to the frame at the time of playback of the image data. Can grasp.

  As described above, when the time code information added to the image data includes information other than the time address, as described above, when all the time code information is updated together with the destructive editing of the image data, the user bit information is also changed. End up. However, the user merely performs destructive editing of the image data with the intention of editing the image data, and there are cases where the user bit is not intended to be changed. Therefore, there has been a problem that by performing destructive editing as described above, information that is not intended by the user is updated and inconvenience may occur.

  Conversely, when the user wants to update only the user bit, if the time code information is destructively edited, the time address information is also updated. Accordingly, it is necessary to update the table information. In such a case, there is a problem that the processing load increases.

  The present invention has been made in view of such a situation. For example, when content data is destructively edited, when the time code is also updated, only the data that needs to be updated is updated, and other data is updated. By protecting the content data, it is possible to more easily perform the destructive editing of the content data in accordance with the user's intention.

  An information processing apparatus according to the present invention includes a real-time metadata update unit for updating time code information included in real-time metadata including data whose content requires real-time in a reading process when reproducing content data, and content data Real-time metadata update means for changing point table which is non-real-time metadata composed of data whose contents are not required for read processing at the time of reproduction, and which is a list information of frames in which change of time code information is nonlinear And non-real-time metadata updating means for updating in accordance with the content of the update according to.

  The proxy data including low-resolution data of the image data further includes proxy data update means for updating time code information of each frame of the low-resolution image data in accordance with the contents of update by the real-time metadata update means. Can be.

  The non-real-time metadata update unit updates the content data with a section in which the time code information is updated by the real-time metadata update unit, a section before the section in which the time code information is updated, and time code information. The change point table can be updated by extracting the change points where the change of the time code information is nonlinear for each of the intervals.

  OVER occurrence confirmation means for confirming the occurrence of a change point of OVER status by update by the real-time metadata update means is further provided, and the non-real-time metadata update means generates a change point of status OVER by the OVER occurrence confirmation means. When it is confirmed, the update process can be terminated without extracting the changing points of the subsequent sections.

  In the background before the update by the real-time metadata update means, it further comprises a background OVER detection means for detecting a change point of the OVER status, and the non-real-time metadata update means is configured to detect the change point of the OVER status by the OVER occurrence confirmation means. Even if the occurrence is not confirmed, the update process can be terminated without extracting the change point in the section after the section in which the OVER is detected by the background OVER detection means.

  Insertion for selecting which of the time address configured by the time information included in the time code information and the user bit which is arbitrary information set by the user to be updated by the update by the real-time metadata update means An information selection means can be further provided.

  When a user bit is selected by the selection process by the insertion information selection means, in order to hold the time address included in the real-time metadata, the time address of the time code information is set using the time address included in the real-time metadata. A time address update means for updating is further provided, and the real time metadata update means can update the real time metadata using the time code information updated by the time address update means.

  When a user bit is selected by the selection process by the insertion information selection means, typical user bit holding means for holding typical user bit information that is metadata for all frames of image data included in the non-real-time metadata, and insertion When the user bit is selected by the selection process by the information selection unit, the typical user bit of the non-real-time metadata updated by the non-real-time metadata update unit using the typical user bit information held by the typical user bit holding unit A typical user bit update means for updating the information again can be provided.

  An information processing method according to the present invention includes a real-time metadata update step for updating time code information included in real-time metadata composed of data that requires real-time properties in reading processing at the time of reproduction of content data, and content data Real-time metadata update step including a change point table, which is non-real-time metadata composed of data that does not require real-time properties in reading processing at the time of playback, and is a list information of frames in which time code information changes nonlinearly And a non-real-time metadata update step for updating in accordance with the content of the update by the above process.

  The program according to the present invention includes a real-time metadata update step for updating time code information included in real-time metadata including data whose content requires real-time in a reading process during reproduction of content data, and reproduction of content data. Processing of the change point table, which is a list of frames that are non-linear in the change of time code information, included in non-real-time metadata consisting of data whose content is not required for real-time read processing at the time of the real-time metadata update step And a non-real-time metadata update step for updating in accordance with the content of the update.

  In the information processing apparatus and method, and the program of the present invention, the time code information included in the real-time metadata including the content data that requires real-time property in the reading process at the time of reproducing the content data is updated, and the content data The change point table, which is the list information of frames in which the change of the time code information is non-linear, is included in the non-real-time metadata consisting of data that does not require real-time properties in the reading process during playback of the real-time metadata It is updated according to the contents of.

  According to the present invention, for example, destructive editing of content data can be correctly performed more easily.

  Embodiments of the present invention will be described below. Correspondences between constituent elements described in the claims and specific examples in the embodiments of the present invention are exemplified as follows. This description is to confirm that specific examples supporting the invention described in the claims are described in the embodiments of the invention. Therefore, even if there are specific examples that are described in the embodiment of the invention but are not described here as corresponding to the configuration requirements, the specific examples are not included in the configuration. It does not mean that it does not correspond to a requirement. On the contrary, even if a specific example is described here as corresponding to a configuration requirement, this means that the specific example does not correspond to a configuration requirement other than the configuration requirement. not.

  Further, this description does not mean that all the inventions corresponding to the specific examples described in the embodiments of the invention are described in the claims. In other words, this description is an invention corresponding to the specific example described in the embodiment of the invention, and the existence of an invention not described in the claims of this application, that is, in the future, a divisional application will be made. Nor does it deny the existence of an invention added by amendment.

  In the present invention, an information processing apparatus (for example, FIG. 1) that processes content data (for example, the clip directory in FIG. 4) including image data in which time code information (for example, LTC in FIG. 12) is added to each frame. Editing device). The information processing apparatus updates real-time time code information included in real-time metadata (for example, real-time metadata in FIG. 6) composed of data that requires real-time properties in reading processing during content data reproduction. Non-real-time metadata (for example, non-real-time metadata in FIG. 12) composed of metadata update means (for example, the RTM update unit in FIG. 15) and data that does not require real-time properties in the reading process at the time of reproduction of content data Includes a change point table (for example, an LTC change point table in FIG. 7) that is a list of frames in which the change in time code information is nonlinear, and is updated in accordance with the content of the update by the real-time metadata update unit. Real-time metadata update And means (e.g., LTC updating unit in Fig. 15).

  In the proxy data including the low-resolution data of the image data (for example, the proxy data file in FIG. 4), the time code information of each frame of the low-resolution image data is changed according to the update contents by the real-time metadata update unit. Proxy data updating means for updating (for example, the PRX updating unit in FIG. 15) can be further provided.

  The non-real-time metadata update unit updates the content data in a section in which the time code information is updated by the real-time metadata update unit (for example, a section between the IN point and the OUT point in FIG. 17) and the time code information. A section before the section (for example, a section before the IN point in FIG. 17) and a section after the section with updated time code information (for example, a section after the OUT point in FIG. 17). Dividing into three sections, a change point where the change in the time code information is nonlinear is extracted for each section, and the change point table is updated (for example, step S31 in FIG. 26, step S35 in FIG. 26, and FIG. 27). Step S43).

  OVER occurrence confirmation means (for example, the OVER occurrence confirmation part in FIG. 16) for confirming the occurrence of a change point whose status is OVER by the update by the real-time metadata update means is further provided, and the non-real-time metadata update means confirms the occurrence of OVER. If the occurrence of a change point with a status of OVER is confirmed by the means, the update process can be terminated without extracting the change points in the subsequent sections.

  A background OVER detection unit (for example, a background OVER detection unit in FIG. 16) for detecting a change point of a status of OVER in the background before the update by the real-time metadata update unit is further provided. Even if the occurrence confirmation point is not confirmed by the occurrence confirmation means, the update process is terminated without extracting the change point in the section after the section where OVER is detected by the background OVER detection means. be able to.

  By updating by the real-time metadata updating means, a time address (for example, the time address in FIG. 212) configured by time information included in the time code information (for example, the SDTI-CP time code in FIG. 12), and the user Insertion information selection means (for example, an insertion information selection processing unit in FIG. 15) for selecting which of the user bits (for example, user bits in FIG. 12) that are set arbitrary information to be updated is further provided. Can be.

  When a user bit is selected by the selection process by the insertion information selection means, in order to hold the time address included in the real-time metadata, the time address of the time code information is set using the time address included in the real-time metadata. A time address updating unit (for example, a time address information updating unit in FIG. 15) for updating is further provided, and the real time metadata updating unit updates the real time metadata using the time code information updated by the time address updating unit. Can be.

  When a user bit is selected by the selection process by the insertion information selection unit, typical user bit information (for example, typical user bit information in FIG. 12) that is metadata for all frames of image data included in the non-real-time metadata. When the user bit is selected by the selection process by the insertion information selection unit and the typical user bit holding unit (for example, the TUB holding control unit in FIG. 15), the typical user bit information held by the typical user bit holding unit And a typical user bit update unit (for example, a TUB update unit in FIG. 15) that re-updates the typical user bit information of the non-real-time metadata updated by the non-real-time metadata update unit. Can do.

  In the present invention, an information processing apparatus (for example, FIG. 1) that processes content data (for example, the clip directory in FIG. 4) including image data in which time code information (for example, LTC in FIG. 12) is added to each frame. An information processing method is provided. This information processing method is a real-time method for updating time code information included in real-time metadata (for example, real-time metadata in FIG. 6) composed of data that requires real-time properties in reading processing at the time of reproduction of content data. The metadata update step (for example, step S8 in FIG. 24) and the non-real time metadata (for example, the non-real time metadata in FIG. 12) composed of data whose real-time property is not required in the reading process when reproducing the content data. The change point table (for example, the LTC change point table in FIG. 7), which is included in the frame list information in which the change in the time code information is nonlinear, is updated according to the content of the update by the processing of the real-time metadata update step. Non-real Im metadata update step (e.g., step S12 in FIG. 25) and a.

  In the present invention, processing relating to content data (for example, the clip directory in FIG. 4) including image data in which time code information (for example, LTC in FIG. 12) is added to each frame is processed by a computer (for example, the editing apparatus in FIG. 1). ) Is provided. This program is a real-time metadata for updating time code information included in real-time metadata (for example, the real-time metadata in FIG. 6) composed of data that requires real-time properties in reading processing at the time of reproduction of content data. Included in the update step (for example, step S8 in FIG. 24) and non-real-time metadata (for example, non-real-time metadata in FIG. 12) consisting of data that does not require real-time properties in the reading process when reproducing the content data. A non-real table that updates a change point table (for example, an LTC change point table in FIG. 7), which is a list of frames in which time code information changes non-linearly, according to the content of the update in the real-time metadata update step processing. Mumetadeta update step (e.g., step S12 in FIG. 25) and a.

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

  FIG. 1 shows a configuration example of an embodiment of a program production system to which the present invention is applied.

  In FIG. 1, a program production system 1 is a system for producing a program (content) broadcasted by, for example, television broadcasting. The program production system 1 includes a camcorder 11 and an editing device 13.

  The camcorder 11 is a device for photographing a subject and recording the obtained material data 21 such as image data and audio data, its metadata 22 and the like on an optical disc 12 as a recording medium, and is one of program production processes. Used for coverage work.

  The editing device 13 edits the material data 21 and the metadata 22 recorded on the optical disc 12, and connects, for example, a plurality of data, deletes unnecessary portions, inserts audio, subtitles, etc. It is a device that inserts character data and generates campaign data 23, which is data completed as content, and is used for editing work, which is one of the program production processes.

  The optical disc 12 is a large-capacity recording medium such as a CD (Compact Disc) or a DVD (Digital Versatile Disc), and records material data 21, metadata 22 and the like. The optical disc 12 is a randomly accessible recording medium and manages each data as a file non-time-series (non-linearly). Therefore, for example, the editing device 13 can access any file recorded in the metadata 12 regardless of the recording order.

  That is, in the program production system 1, the camcorder 11 and the editing device 13 exchange material data 21 and metadata 22 via the randomly accessible optical disk 12.

  FIG. 2 is a schematic diagram showing a configuration example of the recording area of the optical disc 12 in FIG.

  In FIG. 2, the recording area 30 of the optical disc 12 includes a replacement area 31, file systems 32 </ b> A and 32 </ b> B, a non-real time metadata area (NRT (Non Real Time) area) 33, and a clip area 34.

  The replacement area 31 is an area used as a substitute for the read / write defective area when a read / write defective area due to scratches, dirt, manufacturing defects, recording life, or the like occurs in other areas. In the file systems 32A and 32B, management information for managing data recorded in the NRT area 33 and the clip area 34 as files is recorded.

  The NRT area 33 is an area for recording non-real time metadata (NRT) which is metadata corresponding to the clip recorded in the clip area 34. A clip is a set of data that forms one content. For example, real-time metadata (RT: Real Time metadata) composed of metadata corresponding to each frame of image data, audio data, and image data, and The proxy data is low-resolution data such as image data and audio data.

  A clip is a unit indicating one imaging process until the photographer starts imaging and ends imaging. That is, the image signal of one clip is usually composed of image signals of a plurality of frames. Note that the clip is used not only to indicate one imaging process but also to indicate the time from the imaging start to the imaging end of the imaging process. Clips are also used to indicate the length and amount of image data obtained by one imaging process, or to indicate the image data itself, and are obtained by one imaging process ( It is also used to indicate the length and amount of various data (or related), or to indicate the collection of the various data itself. Specifically, as data included in a clip, for example, in addition to material data of image data and audio data, various metadata related to the material data, proxy data that is low-resolution data of the material data, or Also included is playlist data for controlling the reproduction method of the material data.

  For example, in the news gathering operation of FIG. 1, a data group obtained by one shooting (from recording start to recording end) performed by the camcorder 11 is one clip. Note that, for example, when a plurality of pieces of image data are connected by an editing operation in the editing apparatus 13, one piece of image data (and each piece of data corresponding to the piece of image data) that is the editing result is taken as one clip.

  The metadata added to the clip material data includes real-time metadata composed of data that requires real-time characteristics in the reading process and non-real-time metadata composed of data that does not require real-time characteristics in the reading process. Data exists.

  As the real-time metadata (RT), for example, LTC (Linear Time Code) that specifies the position of the frame of the image signal using predetermined time information such as hours, minutes, and seconds, the frame number of each frame, FTC (File Time Code), which is relative position information from the first frame of the file, user bit (UB: User Bit) indicating the signal characteristics of the image signal of that frame, UMID (ID for identifying the frame) (Unique Material Identifier), GPS (Global Positioning System) information indicating the position where the image was taken by the video camera, essence marks that are information about the contents of essence data such as image signals and audio signals, ARIB (Association of Radio Industries and Businesses) metadata, setting / control information of the video camera on which the image was taken. The ARIB metadata is metadata for a communication interface such as SDI (Serial Digital Interface) standardized by the standard organization ARIB. The video camera setting / control information is, for example, information such as an IRIS (iris) control value, a white balance / black balance mode, and lens information related to lens zoom and focus.

  Non-real time metadata is metadata for the entire clip. Non-real-time metadata (NRT) includes, for example, a conversion table in which an LTC corresponding to each frame is associated with a frame number (FTC), UMID, GPS information, or other information. A frame is a unit of an image signal and is image data corresponding to an image for one screen (or various data corresponding to the image data). A clip is a unit indicating one imaging process until the photographer starts imaging and ends imaging. That is, the image signal of one clip is usually composed of image signals of a plurality of frames.

  Such real-time metadata and non-real-time metadata may be added to any unit of image data. In the following, a case where real-time metadata is added to image data for each frame and non-real-time metadata is added to image data for each clip will be described. That is, in the following, it is assumed that the real-time metadata is frame metadata added to the image signal for each frame and includes data corresponding to the added frame. Further, the non-real-time metadata is clip metadata added for each clip to the image signal, and includes data corresponding to the entire added clip.

  Normally, image data is filed for each clip and managed by a file system. In such a case, the non-real-time metadata may be metadata for each file including image data.

  Note that the real-time metadata and the non-real-time metadata may include data other than those described above. In addition, the same content data may be included in the real-time metadata and the non-real-time metadata, or each data as the above-described real-time metadata may be the non-real-time metadata. Each data described above may be real-time metadata. For example, essence marks, ARIB metadata, or video camera setting / control information may be included as non-real-time metadata, or may be included in both real-time metadata and non-real-time metadata. In addition, UMID and GPS information may be included in real-time metadata, or may be included in both real-time metadata and non-real-time metadata.

  As shown in FIG. 2, in the clip area 34, data of each clip is recorded in order, such as a clip 34A, a clip 34B,. In FIG. 2, the area of the clip area 34 where the clip is not yet recorded is an unused area 34C. The clip 34A includes a body A including image data and audio data belonging to the clip 34A, footer information F_A, and header information H_A. Similarly, the clip 34B includes a body B including image data and audio data belonging to the clip 34B, footer information F_B, and header information H_B.

  In the optical disc 12, each data is managed as a file as shown in FIGS. 3 to 5 according to the management information of the file systems 32A and 32B.

  As a file system for managing data recorded on the optical disc 12, any system may be used, for example, UDF (Universal Disk Format), ISO9660 (International Organization for Standardization 9660), or the like. . When a magnetic disk such as a hard disk is used instead of the optical disk 12, the file system is FAT (File Allocation Tables), NTFS (New Technology File System), HFS (Hierarchical File System), or UFS (Unix (registered trademark)). ) File System) may be used. A dedicated file system may be used.

  In this file system, data recorded on the optical disk 12 is managed by a directory structure and files as shown in FIG.

  In FIG. 3, a root directory (ROOT) 51 includes a PROAV directory 52 in which information related to material data such as image data and audio data, an edit list indicating the editing result of the material data, and the like are arranged in a lower directory. Provided. In addition, although illustration is abbreviate | omitted in the root directory 51, structure table data etc. are also provided.

  The PROAV directory 52 includes a disc metafile (DISCMETA.XML) 53, an index file (INDEX.XML) 54 including management information for managing all clips and edit lists recorded on the optical disc 12, and copies thereof. Index file (INDEX.BUP) 55, disc information file (DISCINFO.XML) 56, duplicated disc information file (DISKINFO.BUP) 57, and clip root directory (CLPR) 58 in which clip data is provided in a lower directory , And an edit list root directory (EDTR) 59 in which edit list data is provided in a lower directory.

  In the clip root directory 58, clip data recorded on the optical disc 12 is managed by being divided into different directories for each clip. For example, in the case of FIG. 3, three clip data are stored in the clip directory (C0001). ) 61, a clip directory (C0002) 62, and a clip directory (C0003) 63. That is, each piece of data of the first clip recorded on the optical disc 12 is managed as a file in a directory under the clip directory 61, and each piece of clip data recorded on the optical disc 12 is subordinate to the clip directory 62. Each piece of clip data managed as a directory file and thirdly recorded on the optical disc 12 is managed as a directory file under the clip directory 63.

  In the edit list root directory 59, the edit list recorded on the optical disc 12 is managed separately for each editing process. For example, in the case of FIG. 3, four edit lists are edited. The list directory (E0001) 64, the edit list directory (E0002) 65, the edit list directory (E0003) 66, and the edit list directory (E0004) 67 are managed separately. That is, the edit list indicating the first editing result of the clip recorded on the optical disc 12 is managed as a file in a directory below the edit list directory 64, and the editing list indicating the second editing result is the edit list directory 65. The edit list showing the third editing result is managed as a file under the edit list directory 66, and the editing list showing the fourth editing result is the edit list directory 67. It is managed as a file in the lower directory.

  In the directory below the clip directory 61 provided in the above-described clip root directory 58, each piece of data of the clip first recorded on the optical disc 12 is provided and managed as a file as shown in FIG.

  In the case of FIG. 4, the clip directory 61 includes a clip information file (C0001C01.SMI) 71 that is a file for managing this clip, and an image data file (C0001V01.MXF) 72 that is a file including the image data of this clip. , Audio data files (C0001A01.MXF to C0001A08.MXF) 73 to 80 which are eight files including audio data of each channel of this clip, and a proxy which is a file including low resolution data corresponding to the image data of this clip Data file (C0001S01.MXF) 81, metadata corresponding to the entire clip, for example, non-real time metadata that does not require real-time properties, such as a conversion table that correlates LTC (Linear Time Code) and frame number Non-real tie, a file containing metadata Metadata file (C0001M01.XML) 82, which is metadata corresponding to each frame of the image data of this clip, and is a file including real-time metadata which is metadata requiring real-time properties, such as LTC. The real-time metadata file (C0001R01.BIM) 83 and the frame structure of the image data file 72 (for example, information on the compression format for each picture in the MPEG (Moving Picture Experts Group) etc., the offset address from the beginning of the file, etc. A file such as a picture pointer file (C0001I01.PPF) 84, which is a file in which (information) is described, is provided.

  In the case of FIG. 4, image data, proxy data, and real-time metadata, which are data required to be real-time during reproduction, are each managed as one file so that the reading time does not increase.

  The audio data is also required to be real-time during reproduction, but 8 channels are prepared and are managed as different files in order to cope with multi-channel audio such as 7.1 channels. That is, the audio data has been described as being managed as eight files. However, the present invention is not limited to this, and the number of files corresponding to the audio data may be seven or less, or nine or more.

  Similarly, image data, proxy data, and real-time metadata may be managed as two or more files, respectively, depending on circumstances.

  In FIG. 4, non-real-time metadata that does not require real-time property is managed as a file different from real-time metadata that requires real-time property. This is to prevent unnecessary metadata such as image data from being read out during normal playback. By doing so, the processing time of playback processing and the load required for processing can be reduced. Can do.

  Note that the non-real-time metadata file 82 is described in XML (eXtensible Markup Language) format in order to provide versatility, but the real-time metadata file 83 has a processing time and a load necessary for the processing of the reproduction process. This is a BIM format file that is a compilation of an XML format file for mitigation.

  The configuration example of the file of the clip directory 61 shown in FIG. 4 can be applied to all clip directories corresponding to each clip recorded on the optical disc 12. That is, the file configuration example shown in FIG. 4 can be applied to the other clip directories 62 and 63 shown in FIG.

  Next, an example of a file structure in a directory below the edit list root directory 59 of FIG. 3 will be described. In the directory below the edit list directory 65 provided in the above-described edit list root directory 59, edit list data, which is information relating to the second editing result of each piece of clip data recorded on the optical disc 17, is shown in FIG. It is provided and managed as a file as shown.

  In the case of FIG. 5, the edit list directory 65 includes an edit list file (E0002E01.SMI) 91, which is a file for managing the editing result (edit list), and the edited material data (all clip clips used for editing). Edit list that is a non-real-time metadata corresponding to the whole of the material data (the portion extracted as edited data) or a file containing non-real-time metadata newly generated based on the non-real-time metadata Non real-time metadata file (E0002M01.XML) 92, playlist file (E0002P01.SMI) 93, playlist picture pointer file (C0001I01.PPF) 94, playlist image data file (E0002V01.BMX) 95, play Audio data file for list (E0002A01.BMX to E000 2A04.BMX) 96 to 99, playlist proxy data file (E0002S01.BMX) 100, playlist real-time metadata file (E0002R01.BBM) 101, and the like are provided.

  In FIG. 5, non-real-time metadata that does not require real-time property is managed as a file different from real-time metadata that requires real-time property. This is to prevent unnecessary metadata from being read during reproduction of image data or the like using the reproduction procedure (playlist) (during reproduction of the editing result). The processing time of the reproduction process and the load necessary for the process can be reduced.

  The edit list non-real-time metadata file 92 is generated based on the non-real-time metadata of the clip used for editing (non-real-time metadata file existing in a directory below the clip root directory 58) based on the editing result. It is a file that contains new non-real-time metadata. For example, when editing is performed, a portion corresponding to the edited material data is extracted from the non-real time metadata included in the non-real time metadata file 82 in FIG. 4, and the edited material data is extracted using them. New non-real-time metadata for one clip is reconstructed and managed as a non-real-time metadata file for an edit list. In other words, new non-real time metadata in which the edited material data is one clip is added to the edited material data, and the non-real time metadata is managed as one edit list non-real time metadata file. . Therefore, the non-real time metadata file for edit list is generated for each editing.

  The edit list non-real-time metadata file 92 is described in the XML format in order to have versatility.

  Note that the image data, proxy data, and real-time metadata may be managed as a plurality of files, respectively, depending on circumstances. Similarly, the number of files corresponding to audio data may be 3 or less, or 5 or more.

  The configuration example of the files in the edit list directory 65 shown in FIG. 5 can be applied to all edit lists (edit results). That is, since the configuration example of the file shown in FIG. 5 can also be applied to the other edit list directories 64, 66, or 67 shown in FIG.

  The image data, audio data, proxy data, and real-time metadata are each divided at predetermined time intervals so that the real-time property during reproduction can be easily maintained when recorded on the optical disc 12. Then, the various divided data are collected and recorded as annual ring data.

  In other words, annual ring data composed of portions corresponding to each data is continuously recorded on the optical disc 12.

  FIG. 6 is a schematic diagram showing a configuration example of the real-time metadata file (C0001R01.BIM) 83 in FIG.

  As shown in FIG. 6, the real-time metadata file 120 includes decoding information (DecoderInit) 121 in which reference information for reproduction is stored and an initial description (Initial Description) 122 that is a metadata body.

  Real-time metadata is metadata added to each frame of image data. That is, the real metadata file 120 is configured as a set of metadata (frame unit (FUU (Fragment Update Unit))) for each frame. The initial description 122 has frame unit number information (Number of FUU) 123, which is information indicating the number of frame units. Following the frame unit number information 123, the FUU 124A, FUU 124B, and FUU 124C. , FUU124D,..., The frame unit for each frame is continuous. The head FUU 124A is a FUU indicating head information, and is configured as a real-time metadata target material filler. Following this FUU 124A, the FUU 124B for the frame with frame number 0, which is the first frame of the image data, is arranged. Subsequently, the FUU 124C corresponding to the frame with frame number 1, FUU 124D corresponding to the frame with frame number 2,.・ It is structured as follows. Note that the value of the frame unit number information 123 is “the number of frames of image data + 1” based on the above configuration.

  In the frame unit, for example, a KLV packet configured by information such as the LTC of the corresponding frame, the UMID of the corresponding frame, and the essence mark of the corresponding frame is described.

  Next, information included in the non-real time metadata file 82 of FIG. 4 will be described. The non-real-time metadata file 82 is additional information for the entire clip that does not require real-time properties regarding an image data file or an audio data file existing in the same clip directory as the non-real-time metadata file 82.

  In the non-real-time metadata file 82, an LTC change point table (LtcChangeTable) that is a list of frames in which the UMID and LTC changes of the clip (clip information file 71) to which the non-real-time metadata file 82 is added becomes nonlinear. Is included. Further, a typical user bit (TypicalUbit) configured by “reel number” or the like, which is information for identifying a recording medium (tape device) on which a clip is recorded, is also included. The “reel number” is information used for facilitating clip management, and is information frequently used in VTRs.

  Furthermore, the non-real-time metadata file 82 includes a basic UMID change point table (list information of frames in which the value of basic UMID (Basic) included in the UMID (BodyUmid) of each frame of image data changes). BodyUmidBasicChangeTable), time information change point table (BodyUmidWhenChangeTable) that is the list information of the frames where the value of time information (When) of UMID (BodyUmid) of each frame of image data changes, and UMID (BodyUmid) of each frame of image data The position information change point table (BodyUmidWhereChangeTable), which is a list of frames whose position information (Where) value changes, and the UMID (BodyUmid) person information (Who) value of each frame of image data A person information change point table (BodyUmidWhoChangeTable) which is list information is included.

  The non-real-time metadata file 82 also includes a KLV packet table (KlvPacketTable) that is list information of frames to which KLV packets are added. Furthermore, information on the video format of the image data, information on the audio format of the audio data, information on the hardware and software used for data recording and editing, user information, and title information of the clip to which the non-real-time metadata file 82 corresponds In addition, arbitrary memo information (description) and the like are also included.

  Next, the above-described LTC change point table will be described. FIG. 7 is a diagram for explaining an example of an LTC change point. In the graph shown in FIG. 7, the horizontal axis represents time T (the number of frames), and the vertical axis represents the LTC value.

  Since LTC is a time code, its value usually increases monotonically (changes linearly) by 1 frame in captured image data. However, for example, if a plurality of clips are connected by editing work, some frames are deleted, or the LTC value itself is edited, the LTC value does not necessarily change linearly. The method of changing the LTC value may change, such as changing from monotonic increase to monotonic decrease (may change non-linearly). A frame in which the way of changing the LTC value in this way is referred to as a change point.

  In FIG. 7, for example, frames 161 to 164 are changing points. For example, in the case of the frame 161, the LTC value increases by a predetermined amount (monotonically increases) every time one frame is advanced (every time the horizontal axis is moved in the right direction). On the other hand, in the frames after frame 161, the LTC value does not change even if the frame advances. Since the way of changing the LTC value changes in this way, the frame 161 is a change point.

  Similarly, the frame 162 to the frame 164 are also changed because the LTC change method changes before and after that. The change points such as the frames 161 to 164 are extracted, and the frame number and the LTC value are tabulated as an LTC change point table and registered in the non-real-time metadata 82.

  Such an LTC change point table is used, for example, when searching for a frame based on the LTC.

  Next, a basic UMID change point table, a time information change point table, a position information change point table, and a person information change point table will be described. FIG. 8 is a diagram illustrating an example of a basic UMID change point, a time information change point, a position information change point, and a person information change point. In the graph shown in FIG. 8, the horizontal axis indicates time T (the number of frames), and the vertical axis indicates the UMID configuration (Basic, When, Who, Where) of each frame of image data.

  The UMID is roughly divided into basic information (Basic), time information (When), position information (Where), and person information (Who). A frame in which such information changes in the UMID assigned to each frame is tabulated as a change point.

  For example, in FIG. 8, UMID is not added to the frames from frame 0 to frame 99, and basic information (Basic), time information (When), position information (Where), and person information (Who) None exist. However, basic UMID having only basic information is added to frames from 100 frames to 199 frames. Therefore, 100 frames are a change point of basic information (Basic).

  In addition, basic UMID having only basic information is added to frames from 100 frames to 199 frames, but basic information (Basic) and time information (frame information) are added to frames from 200 frames to 299 frames. An extended UMID having all of When, Position Information (Where), and Person Information (Who) is added. Therefore, the 200 frame is a change point of time information (When), position information (Where), and person information (Who).

  Such change points of information are extracted and registered in the non-real-time metadata 82 as change point tables.

  Next, the above KLV packet table will be described. FIG. 9 is a diagram illustrating an example of a KLV packet. The horizontal axis in FIG. 9 indicates time T (number of frames). That is, FIG. 9 is a diagram showing what kind of KLV packet is added to the frame of which frame number.

  For example, in FIG. 9, an essence mark indicating “Recording start (RecStart)” is added to the first frame of frame number “0” as a KLV packet, and frames “200” to “300” have “ The string “Japan” (keywords) is added as a KLV packet, and an essence mark indicating that “Flash” has been struck is added as a KLV packet to the frame with frame number “400”. An essence mark indicating “Japanese” is added as a KLV packet to the frame with the frame number “500”, and the character string “keyword” (keyword) is used for the frames with the frame numbers “600” to “700”. (KeyWords)) is added as a KLV packet, and the last frame with frame number "800" Essence mark indicating until recend) "is added as a KLV packet.

  Information about the frame to which such a KLV packet is added is tabulated and registered in the non-real-time metadata 82.

  The information related to the video format of the image data described above includes, for example, the format standard (port) of the image data, the codec standard (videoCodec) of the image data, the number of frames per second (recFps) during recording, It includes information such as the number of frames per second (playFps), the number of pixels of one screen image (pixel, numOfVerticalLine), and the scanning method (VideoScan).

  The audio format of the audio data described above includes, for example, information about the audio format for each channel, such as the channel number (cast) of the audio data, the signal system (port) of the signal, and the codec system.

  Next, information on the hardware and software used for data recording and editing described above includes, for example, hardware manufacturer name (manufacturer), model number (serialNO), model name (modelName), hardware It includes information such as name (hardware) and software version information (software).

  Next, editing of data having the above configuration will be described. For example, when the editing apparatus 13 of FIG. 1 edits the material data 21 and metadata 22 recorded on the optical disc 12, a method of updating the material data 21 and metadata 22 to be edited (destructive editing), and an editing target There is a method (non-destructive editing) in which the material data 21 and the metadata 22 are kept as they are, and data indicating the editing result is newly generated.

  FIG. 10 is a diagram for explaining a state of nondestructive editing. FIG. 10 shows a state of nondestructive editing in the storage area of the optical disc 12 described with reference to FIG. The upper row shows the configuration of the storage area of the optical disc 12 before editing, and the lower row shows the configuration of the storage area of the optical disc 12 after editing.

  When a part of the body A of the clip 34A is overwritten in the upper part of FIG. 10, in the case of nondestructive editing, as shown in the lower part, the original clip 34A is left as it is, and the result of overwriting the clip 34A in the unused area 34C. Clip 34A ′ (body A ′, footer F_A ′, and header H_A ′) is newly recorded. Therefore, when nondestructive editing is performed, the capacity of the unused area 34C is reduced by the amount that the editing result is newly recorded. However, since the clip 34A before editing remains, the user can easily obtain the clip 34A before editing even after editing.

  On the other hand, FIG. 11 is a diagram for explaining a state of destructive editing. FIG. 11 shows a state of destructive editing in the storage area of the optical disc 12 described with reference to FIG. The upper row shows the configuration of the storage area of the optical disc 12 before editing, and the lower row shows the configuration of the storage area of the optical disc 12 after editing.

  When a part of the body A of the clip 34A is overwritten in the upper part of FIG. 11, in the case of destructive editing, as shown in the lower part, the original clip 34A is updated and the clip 34A ′ (body A ′, footer) as the overwriting result is updated. F_A ′ and header H_A ′). Therefore, if the data amount does not change before and after editing, the capacity of the unused area 34C does not change even if destructive editing is performed. However, since the clip 34A before editing is not left, the user cannot easily obtain the clip 34A before editing after editing.

  An example of updating information related to the time code by such destructive editing will be described with reference to FIG.

  As shown in FIG. 12, the SDTI-CP time code 200 which is time code information of SDTI-CP (Serial Data Transport Interface Content Pakage) which is a general content data transmission format is a time constituted by time information. It has an address 201 and a user bit 202 that allows the user to set arbitrary information.

  SDTI-CP is a transmission method that transmits image data, audio data, their multiplexed data, metadata, etc. using the serial line of the VTR. Each frame of image data transmitted by this method is used for each frame. Usually a time code is added as metadata. The SDTI-CP time code 200 is time code information assigned to each frame. A configuration example of the SDTI-CP time code 200 will be described later.

  The time address 201 is time information included in the SDTI-CP time code 200, and indicates a time assigned to a frame to which the SDTI-CP time code 200 is added. That is, this time address 201 plays the same role as LTC. The user bit 202 is an area where arbitrary information can be input. For example, information such as the essence mark and reel number of the corresponding frame is input.

  As shown in FIG. 12, when performing the LTC update 203, which is a process of updating the LTC for the material data recorded on the optical disc 12, using such an SDTI-CP time code 200, the value of the time address 201 Is used. That is, the value of the time address 201 is inserted (overwritten) at the LTC update position. In the case of FIG. 12, the LTC between the values “12” to “14” of the frame sandwiched between the frame with the LTC value “11” and the frame with the LTC value “15” is overwritten and updated by the time address 203. The value is changed from “97” to “99”.

  With such LTC update 203, the LTC 205 of the real-time metadata 204 is updated, and the LTC change point table 207 included in the non-real-time metadata 206 is also updated according to the update.

  Also, as shown in FIG. 12, when performing KLV update 210, which is a process of updating information of KLV packets for material data recorded on the optical disk 12, using such an SDTI-CP time code 200, The value of user bit 202 is used. That is, the value of the user bit 202 is inserted (overwritten) at the update position of the KLV packet. In the case of FIG. 12, a “reel number” is assigned to the entire clip as a KLV, but an essence mark (EM) that is user bit (UB) information is inserted (overwritten) in a part of the frame of the KLV. Has been.

  By such KLV update 210, the KLV 212 of the real-time metadata 211 is updated, and the KLV packet table 214 included in the non-real-time metadata 213 is also updated according to the update. However, since the reel number itself is not updated, the typical user bit (Typcal Ubit) included in the non-real time metadata 213 is retained without being updated.

  FIG. 13 is a schematic diagram illustrating a configuration example of the SDTI-CP time code 200.

  As shown in FIG. 13, the SDTI-CP time code 200 includes an 8-bit (b0 to b7) frame number (Frame), an 8-bit second number (Seconds), an 8-bit minute number (Minutes), and 8 bits. Time number (Hour) and 32-bit (8 bits × 4 columns) binary group data (BG0 to BG7). A time address 201 is inserted into the frame number or time number in the left four columns in FIG. 13, and the binary group data in the right four columns in FIG. 13 is used as user bits.

  FIG. 14 is a block diagram showing a configuration example of the editing apparatus 13 of FIG. 1 to which the present invention is applied.

  14, the editing apparatus 13 includes a system control unit 221, an operation input unit 222, a control information input unit 223, a control information output unit 224, an input unit 231, a recording signal processing unit 232, an information processing unit 233, a network interface 234, A metadata processing unit 235, a drive control unit 236, a pickup unit 237, a spindle drive unit 238, a reproduction signal processing unit 239, and an output unit 240 are provided.

  The system control unit 221 is a control unit that controls the editing apparatus 13 as a whole. The system control unit 221 includes a calculation unit, a control unit, a storage unit, and the like (not shown). Processing related to control of The operation input unit 222 includes an input device such as a keyboard and buttons, for example, receives operation input from the user, and supplies the information to the system control unit 221.

  The control information input unit 223 receives information other than information related to content such as material data and metadata from the outside of the editing device 13 as control information, and supplies it to the system control unit 221. The control information output unit 224 outputs information other than information related to content such as material data and metadata supplied to the system control unit 221 to the outside of the editing apparatus 13.

  The input unit 231 is a processing unit that receives information related to content supplied from outside the editing device 13, and material data input that receives material data (for example, image data, audio data, etc.) supplied from the outside of the editing device 13. A unit 251 and a metadata input unit 252 that receives metadata (for example, real-time metadata or non-real-time metadata) supplied from the outside of the editing apparatus 13. The material data input unit 251 supplies the input material data to the recording signal processing unit 232, and the metadata input unit 252 supplies the input metadata to the recording signal processing unit 232. For example, the SDTI-CP time code described with reference to FIG. 24 is input to the editing device 13 via the metadata input unit 252.

  The recording signal processing unit 232 performs signal processing on the material data, metadata, and the like supplied from the input unit 231, and performs processing such as converting each data from a transmission format to a recording format. The recording signal processing unit 232 supplies the signal processed data to the information processing unit 233.

  The information processing unit 233 is controlled by the system control unit 221 and performs processing related to editing of material data. For example, the information processing unit 233 includes an information multiplexing unit 253 that multiplexes a plurality of data and an information decomposing unit 254 that decomposes one piece of information into a plurality of pieces of information, and performs processing such as composition and division. The material data and metadata to be edited are supplied from the recording signal processing unit 232, the network interface 234, the drive control unit 236, or the like. When the information processing unit 233 acquires the supplied material data and metadata, the information processing unit 233 controls the material data to be edited by the system control unit 221, and performs the editing on the network interface 234, the drive control unit 236, or the playback. The signal is supplied to the signal processing unit 239. Note that metadata editing is performed in the metadata processing unit 235. Therefore, when the metadata is supplied, the information processing unit 233 supplies the metadata to the metadata processing unit 235.

  The network interface 234 is an interface connected to a LAN (Local Area Network) such as Ethernet (registered trademark) or the Internet, for example, and by communicating with a communication device other than the editing device 13 connected to the same network, Material data, metadata, and the like are acquired from another device and supplied to the information processing unit 233, or material data, metadata, and the like supplied from the information processing unit 233 are supplied to another device. The metadata processing unit 235 edits the metadata supplied from the information processing unit 233 under the control of the system control unit 221, and returns the edited metadata to the information processing unit 233.

  The drive control unit 236 is a processing unit that controls each unit of a drive (not shown) of the editing apparatus 13 in which the optical disk 12 is mounted. For example, the drive control unit 236 is controlled by the system control unit 221 to read out information recorded on the optical disk 12 mounted on the drive or record information on the optical disk 12. The spindle drive unit 238 that controls the drive of the optical disk 12 mounted in the drive is controlled. Then, the drive control unit 236 controls the pickup unit 237 and the spindle drive unit 238 to supply the data read from the pickup unit 237 to the information processing unit 233. Further, the drive control unit 236 controls the pickup unit 237 and the spindle drive unit 238 to write (record) the data supplied from the information processing unit 233 to the optical disc 12 through the pickup unit 237.

  The pickup unit 237 is controlled by the drive control unit 236 to irradiate the optical disk 12 mounted on the drive with laser light, read data recorded on the optical disk 12, and supply it to the drive control unit 236. The data supplied from the drive control unit 236 is written on the optical disc 12. At this time, the pickup unit 237 is controlled by the drive control unit 236 and slides in the radial direction with respect to the optical disk 12 to control the access position in the radial direction of the optical disk 12. The spindle drive unit 238 mainly controls the rotational movement of the optical disk 12 mounted on the drive, and controls the access position with respect to the rotation direction of the optical disk 12 by the pickup unit 237.

  The reproduction signal processing unit 239 performs signal processing on the output signal (or reproduction signal) supplied from the information processing unit 233, for example, performs processing such as converting each data from a recording format to a transmission format. . The reproduction signal processing unit 239 supplies the signal processed data to the output unit 240.

  The output unit 240 is a processing unit that outputs information related to content to the outside of the editing device 13, and a material that outputs material data (image data, audio data, etc.) supplied from the reproduction signal processing unit 239 to the outside. A data output unit 255 and a metadata output unit 256 that outputs metadata (real-time metadata, non-real-time metadata, etc.) supplied from the reproduction signal processing unit 239 to the outside. Note that the output unit 240 may include an output device such as a display or a speaker, and the playback signal supplied from the playback signal processing unit 239 may be output from the output device.

  Each unit described above operates under the control of the system control unit 221, and performs processing related to editing and output (reproduction) of the material data 21 and metadata 22 recorded on the optical disc 12.

  FIG. 15 is a block diagram illustrating a detailed configuration example of the system control unit 221 of FIG.

  In FIG. 15, the system control unit 221 includes a control unit 261, an insertion information selection processing unit 271, a time code information receiving unit 272, a clip writing unit 273, a clip reading unit 274, a time address information updating unit 275, and a TUB holding control unit 276. RTM update unit 277, PRX update unit 278, LTC update unit 279, KLV update unit 280, TUB update unit 281, input control unit 291, communication control unit 292, write control unit 293, read control unit 294, edit update processing control 295 and an output control unit 296. These are divided into three layers. A control unit 261 that controls the entire system control unit 221 constitutes the highest layer, and includes an insertion information selection processing unit 271, a time code information receiving unit 272, a clip writing unit 273, Clip reading unit 274, time address information update unit 275, TUB holding control unit 276, RTM update unit 277, PRX update unit 278, LTC update unit 279, KLV update unit 280, and TUB update unit 281 execute the target processing. The input control unit 281, the communication control unit 282, the write control unit 283, the read control unit 284, the edit update processing control unit 285, and the output control unit 286 are included in the editing device 13 system. The lowest layer that controls the processing units other than the control unit 221 is configured.

  The control unit 261 includes an insertion information selection processing unit 271, a time code information receiving unit 272, a clip writing unit 273, a clip reading unit 274, a time address information updating unit 275, a TUB holding control unit 276, an RTM updating unit 277, and a PRX updating unit. 278, the LTC update unit 279, the KLV update unit 280, or the TUB update unit 281 starts and ends, and controls cooperation with other processes. The control unit 261 controls the above-described units based on operation input information supplied from the operation input unit 222 and control information supplied from the control information input unit 223. Further, the control unit 261 supplies the control information to the control information output unit 224 and outputs the control information to the outside of the editing apparatus 13 via the control information output unit 224. The output unit 261 also controls the output control unit 286 to control processing related to output of material data and metadata.

  The insertion information selection processing unit 271 controls the operation input unit 222 via the control unit 261, and selects information to be inserted into the clip from the time address 201 and user bit 202 of the input SDTI-CP time code 200. Accept.

  The time code information receiving unit 272 controls the input control unit 291 and the communication control unit 292 to receive the SDTI-CP time code 200 that is time code information input via the metadata input unit 252 and the network interface 234.

  The clip writing unit 273 controls the write control unit 293 to perform processing related to writing the destructively edited clip to the optical disk 12. The clip reading unit 274 controls the reading control unit 294 to perform processing related to reading of the designated clip from the optical disc 12.

  The time address information update unit 275 controls the edit update processing control unit 295 to update the time address information held in the metadata processing unit 235, which is the metadata of the material data held in the information processing unit 233. Process related to.

  The typical user bit (TUB) holding control unit 276 stores the information so that the typical user bit included in the non-real-time metadata is not updated when the non-real-time metadata is updated during the destructive editing of the clip. The data processing unit 235 holds the data.

  The real-time metadata (RTM) update unit 277 controls the edit update processing control unit 295 at the time of destructive editing of a clip, and performs processing related to updating of real-time metadata held in the metadata processing unit 235. The proxy data (PRX) updating unit 278 performs processing related to updating proxy data held in the information processing unit 233 at the time of destructive editing of a clip. The LTC update unit 279 performs processing related to updating the LTC change point table of the non-real-time metadata held in the metadata processing unit 235 at the time of destructive editing of a clip. The KLV update unit 280 performs processing related to the update of the KLV packet table of non-real-time metadata held in the metadata processing unit 235 at the time of destructive editing of a clip. The TUB update unit 281 performs processing related to the update of the KLV packet held in the metadata processing unit 235 at the time of destructive editing of a clip. The typical user bit (TUB) update unit 281 performs processing related to updating of typical user bits held in the metadata processing unit 235 at the time of destructive editing of a clip.

  The input control unit 291 controls the input unit 231 and the recording signal processing unit 232 to execute processing for receiving material data and metadata input to the input unit 231 from the outside of the editing apparatus 13. The communication control unit 292 controls the network interface 234 and performs processing related to communication with other devices. The write control unit 293 controls the drive control unit 236 to perform processing related to data writing to the optical disc 12. The read control unit 294 controls the drive control unit 236 to perform a process related to reading data recorded on the optical disc 12. The edit update processing control unit 295 controls the information processing unit 233 and the metadata processing unit 235, for example, performs processing related to destructive editing of the material data held by the information processing unit 233, or the metadata processing unit 235 Performs processing related to destructive editing of retained metadata. The output control unit 296 controls the reproduction signal processing unit 239 and the output unit 240, and executes processing related to output of the data output from the information processing unit 233 to the outside of the editing device 13.

  FIG. 16 is a block diagram illustrating a detailed configuration example of the LTC update unit 279 of FIG.

  In FIG. 216, the LTC update unit 279 includes an IN point pre-update processing unit 301, an IN point continuity confirmation update processing unit 302, an insertion part update processing unit 303, an OUT point continuity confirmation update processing unit 304, and an OUT point post-update process. A unit 305, an update end processing unit 306, a background OVER detection unit 311, an OVER occurrence confirmation unit 312, an OUT point confirmation unit 313, and an END occurrence confirmation unit 314.

  The pre-IN point update processing unit 301 controls the edit update processing control unit 295 to perform processing related to the update of the portion before the IN point, which is the LTC update start position, in the LTC change point table. The IN point continuity confirmation update processing unit 302 controls the edit update processing control unit 295 to confirm the continuity of the LTC corresponding to the frames before and after the IN point, and if necessary, changes in the LTC for the IN point. Performs processing related to point table update. The insertion part update processing unit 303 controls the edit update processing control unit 295 to perform processing related to the update of the insertion part that is the part (between the IN point and the OUT point) in which the LTC is updated in the LTC change point table. The OUT point continuity confirmation update processing unit 304 controls the edit update processing control unit 295 to confirm the continuity of the LTC corresponding to the frames before and after the OUT point that is the update end position of the LTC. Processing related to the update of the LTC change point table for the OUT point is performed. The post-OUT point update processing unit 305 controls the edit update processing control unit 295 to perform processing related to the update of the portion after the OUT point that is the LTC update end position in the LTC change point table. The update end processing unit 306 controls the edit update processing control unit 295 to perform update end processing such as embedding the updated LTC change point table in non-real time metadata.

  The background OVER detection unit 311 is controlled by the pre-IN point update processing unit 301 or the post-OUT point update processing unit 305, and performs processing to detect OVER existing in the unupdated LTC that is the base. OVER is one of the statuses of the change points in the LTC change point table, and is a status indicating that the number of change points detected so far has exceeded the upper limit due to device restrictions or the like. That is, when OVER occurs, the subsequent change points of the clip are not registered in the LTC change point table.

  The OVER occurrence confirmation unit 312 is controlled by the IN point continuity confirmation update processing unit 302, the insertion part update processing unit 303, the OUT point continuity confirmation update processing unit 304, and the post-OUT point update processing unit 305, and the occurrence of OVER occurs. Perform the confirmation process. The OUT point confirmation unit 313 is controlled by the insertion part update processing unit 303, and performs an OUT point confirmation process indicating the end of the insertion part. The END generation confirmation unit 314 is controlled by the post-OUT point update processing unit 305, and performs processing for confirming the generation of END points.

  In other words, the editing device 13 also updates the LTC change point table of non-real time metadata along with the update of the LTC of real time metadata. However, the number of change points of the LTC changes due to the update, and the occurrence of OVER occurs before and after the update. May be different. Accordingly, each unit of the LTC update unit 279 performs processing related to the update of the LTC change point table while detecting OVER.

  The occurrence pattern of this OVER will be described with reference to FIGS. FIG. 17 is a diagram illustrating a case where OVER does not occur before and after the update.

  As shown in the upper part of FIG. 17, information related to LTC is included in proxy data, real-time metadata, and non-real-time metadata. Proxy-data LTC (Proxy-LTC) is LTC corresponding to low-resolution material data included in proxy data. Real-time metadata LTC (RT-LTC) is LTC corresponding to material data (main line data). The non-real time metadata has a change point table (NRT-LTC) generated from the LTC (RT-LTC) of the real time metadata.

  As shown in the upper part of FIG. 17, an LTC is assigned to each frame from the start (BEGIN) to the end (END) of the clip (base Proxy-LTC, base RT-LTC). A corresponding LTC change point table (underlying NRT-LTC) is provided. In this case, OVER does not occur in the LTC change point table (underlying NRT-LTC).

  When such a clip is inserted (inserted) into a part (from the IN point to the OUT point) of LTC (material data with LTC added) as shown in the lower part of FIG. Inserted LTC is overwritten on the inserted part from to the OUT point. That is, in the case of FIG. 28, the proxy data LTC (Proxy-LTC) is composed of the base Proxy-LTC from the beginning of the clip (BEGIN) to the IN point and from the OUT point to the end of the clip (END). Consists of Proxy-LTC inserted from IN point to OUT point. Similarly, the real-time metadata LTC (RT-LTC) consists of the base RT-LTC from the beginning of the clip (BEGIN) to the IN point and from the OUT point to the end of the clip (END). Consists of RT-LTC inserted up to OUT point.

  The LTC change point table (NRT-LTC) is also updated based on this real-time metadata LTC (RT-LTC). In the case of FIG. 17, since OVER does not occur in the LTC change point table even after updating, the LTC change point table (NRT-LTC) is from the beginning of the clip (BEGIN) to the IN point as shown in the lower part of FIG. From the OUT point to the end of the clip (END) shows the LTC before update (underlying NRT-LTC), and from the IN point to OUT point shows the updated LTC (inserted NRT-LTC) It becomes composition.

  FIG. 18 is a diagram illustrating a case where OVER occurs in the insertion portion after updating.

  As shown in the upper part of FIG. 18, OVER does not occur in the LTC change point table (base NRT-LTC) before update. However, as shown in the lower part of FIG. 18, the number of change points increases due to the update of the LTC of the real-time metadata, and the OVER at the change point of the insertion part (between the IN point and the OUT point) of the updated LTC change point table. When this occurs, all subsequent change points are deleted, and the update process is terminated. That is, change points after the OVER point are ignored and are not registered in the updated LTC change point table.

  This is the same when OVER occurs after the OUT point as shown in FIG. FIG. 19 is a diagram illustrating a case where OVER occurs in the portion after the OUT point after the update. For example, when the number of LTC change points after the update in the insertion part is larger than before the update, and as a result, OVER occurs during the update of the LTC change point table in the part after the OUT point. Similarly to the above, all subsequent change points are deleted, and the update process is terminated. That is, also in this case, the change points after the OVER point are ignored and are not registered in the updated LTC change point table.

  Next, a case where OVER exists in the LTC change point table from before the update will be described. FIG. 20 is a diagram illustrating a case where OVER has not occurred after the update.

  As shown in the upper part of FIG. 20, in the change point table before update (base NRT-LTC), OVER occurs at a position before the OUT point after update. In this case, for example, when the number of change points is reduced by updating the LTC of the real-time metadata and no OVER occurs, as shown in the lower part of FIG. 20, the LTC change point table up to the insertion part (OUT point). Is generated. However, since it is located behind OVER in the LTC change point table before update, change points after the OUT point are not registered. Therefore, in the updated LTC change point table, it is assumed that OVER has occurred at the OUT point, and change points after the OUT point are ignored.

  That is, as shown in FIG. 20, when OVER exists before the OUT point in the LTC change point table before update, the updated LTC change point table is compulsory even if OVER does not occur up to the OUT point. In addition, it is determined that an OVER has occurred at the OUT point, and the change points after the OUT point are not registered.

  As shown in FIG. 21, when OVER occurs before the OUT point in the LTC change point table before update as in FIG. 20, when OVER occurs before the OUT point, after update, In the LTC change point table, no change point after the OVER is registered (the lower part of FIG. 32).

  In addition, as shown in FIG. 22, in the LTC change point table before update, when OVER occurs in a portion before the IN point that is the LTC insertion start position, the updated LTC change point table is updated. Regardless of the above, since OVER occurs at the same position as the LTC change point table before update, the subsequent change points are not registered (lower part of FIG. 22).

  On the other hand, as shown in FIG. 23, in the LTC change point table before update, when OVER occurs in the portion after the OUT point that is the LTC insertion end position, for example, the change point number of the insert portion is updated. Even if it decreases and OVER does not occur in the updated LTC change point table, the change point after OVER of the LTC change point table before update is not registered, so the LTC change point table after update is OVER is forcibly generated at the same position as before the update, and the subsequent change point is not registered (lower row in FIG. 23).

  In this way, by updating the LTC change point table of the non-real time metadata by a method in accordance with the change of the LTC of the real time metadata, the editing device 13 can more easily and accurately update the information regarding the time code. Can do.

  Next, the flow of processing relating to time code (TC) insertion by the editing device 13 will be described with reference to the flowcharts of FIGS.

  When the TC insertion process is started, the insertion information selection processing unit 271 of the system control unit 221 accepts selection of information to be inserted in step S1. The insertion information selection processing unit 271 controls the operation input unit 222 via the control unit 261 and inserts the time address 201 of the SDTI-CP time code 200 input via the metadata input unit 252 or the user bit An instruction to select whether to insert 202 is received. When the selection is accepted, in step S 2, the clip reading unit 274 reads the designated clip from the optical disk 12 and causes the information processing unit 233 and the metadata processing unit 235 to hold it. In step S3, the time code information receiving unit 272 controls the input control unit 291 or the communication control unit 292, and the insertion time supplied from the outside of the editing apparatus 13 via the input unit 231 or the network interface 234. Accept code information.

  In step S4, the control unit 261 determines whether or not to insert time address information based on the selection instruction received in step S1, and proceeds to step S8 if it is determined to insert time address information. .

  If it is determined in step S4 that the user bit 202 is to be inserted, the control unit 261 advances the process to step S5. In step S5, the time address information updating unit 275 extracts the LTC of the portion into which the time code information is inserted from the metadata, and in step S6, updates the time address information of the time code information with the extracted LTC. That is, the time address information update unit 275 updates the time address information of the time code information to be inserted with the LTC added to the clip before destructive editing. Thereby, even if the real-time metadata of the clip is updated by the time code information, the original LTC is overwritten and updated by the original LTC. Therefore, the time address information update unit 275 can store the original LTC. it can.

  When the process of step S6 ends, the time address information update unit 275 advances the process to step S7. In step S7, the TUB holding control unit 276 extracts and holds the typical user bit information of the non-real time metadata. Thereby, it can suppress that typical user bit information which is the information with respect to the whole clip will be updated by insertion of a user bit.

  The typical user bit information is information generated by using the value of the user bit of the time code information. As described above, the typical user bit information is intended to register information on the entire clip, such as a reel number, for example. . Therefore, it is not desirable that the typical user bit information is updated due to a small update such as adding one frame of essence mark. However, if the typical user bit information is not updated when the time code information is updated, the typical user bit information will not be updated even if the user bits of all frames of the clip are updated. Therefore, as described above, the editing device 13 permits the update of the typical user bit information only when the time address is also updated, and does not permit the update of the typical user bit information when only the user bit is updated. . By doing in this way, generation | occurrence | production of the malfunction mentioned above can be suppressed.

  When the process of step S7 ends, the TUB holding control unit 276 advances the process to step S8.

  In step S8, the RTM update unit 277 updates real-time metadata using the input time code information. In step S9, the PRX update unit 278 updates the proxy data using the input time code information. When the process of step S9 ends, the PRX update unit 278 advances the process to step S11 of FIG.

  In step S11, the control unit 261 determines whether or not the LTC has changed. If the control unit 261 determines that the LTC has changed, the process proceeds to step S12. In step S12, the LTC update unit 279 executes the LTC change point table update process of the non-real time metadata. Details of the LTC change point table update processing will be described later.

  When the process of step S12 ends, the LTC update unit 279 advances the process to step S13. If it is determined in step S11 that the LTC has not changed, the control unit 261 advances the process to step S13.

  In step S13, the control unit 261 determines whether or not the KLV packet data has changed. If it is determined that the KLV packet data has changed, the control unit 261 advances the process to step S14. In step S14, the KLV update unit 280 updates the changed portion of the KLV packet table of the non-real time metadata, and advances the processing to step S15. In step S15, the TUB update unit 281 updates the typical user bits of the non-real time metadata using the user bits of the input time code information, and advances the process to step S16.

  In step S16, the control unit 261 determines whether or not the TUB holding control unit 276 holds the typical user bit. If it is determined that the TUB holding control unit 276 holds, the process proceeds to step S17. In step S <b> 17, the TUB update unit 281 updates the typical user bits of the non-real-time metadata again to the data held by the TUB holding control unit 276. That is, the TUB update unit 281 returns the typical user bits of the non-real time metadata to the original values. When the process of step S17 ends, the TUB update unit 281 advances the process to step S18.

  If it is determined in step S13 that the KLV packet data has not changed, the control unit 261 advances the process to step S18. Furthermore, when it is determined in step S16 that the typical user bit is not held, the control unit 261 advances the process to step S18.

  In step S18, the clip writing unit 273 controls the writing control unit 293 to write the updated clip to the optical disc 12, and ends the TC insert process.

  Next, the detailed flow of the LTC change point table update process executed in step S12 of FIG. 25 will be described with reference to the flowcharts of FIGS.

  When the LTC change point table update process is started, the update processing unit 301 before the IN point of the LTC update unit 279 first updates the change point information for the portion before the IN point of the LTC change point table in step S31. Perform the update process before IN point. Since the part before the IN point is normally not updated, it is the same as the LTC change point before the update (underlying). In step S32, the background OVER detection unit 311 monitors the status of the LTC change point of the background, and determines whether or not OVER is detected. If it is determined that OVER is not detected, the background OVER detection unit 311 advances the process to step S33.

  In step S33, the IN point continuity confirmation update processing unit 302 confirms the LTC continuity before and after the IN point, updates the LTC change point table as necessary, and registers the IN point as a change point. Perform continuity check update processing. At this time, the IN point continuity confirmation update processing unit 302 controls the OVER occurrence confirmation unit 312 to monitor the status when the change point is registered in the LTC change point table. The OVER occurrence confirmation unit 312 monitors the status of the change point registered in the LTC change point table and determines whether or not an OVER has occurred in step S34. If it is determined that OVER has not occurred, the OVER occurrence confirmation unit 312 advances the process to step S35.

  In step S35, the insertion part update processing unit 303 performs insertion part update processing for updating the LTC change point table for the insertion part between the IN point and the OUT point. At this time, the insertion part update processing unit 303 controls the OVER occurrence confirmation unit 312 to monitor the status of the change point registered in the LTC change point table. The OVER occurrence confirmation unit 312 monitors the status of the change point registered in the LTC change point table and determines whether or not an OVER has occurred in step S36. If it is determined that OVER has not occurred, the OVER occurrence confirmation unit 312 advances the process to step S37.

  At this time, the insertion part update processing unit 303 controls the OUT point confirmation unit 313 to confirm the position of the end of the insertion part (OUT point). In step S37, the OUT point confirmation unit 313 determines whether or not the frame on which the LTC change point table update process has been performed has reached the OUT point. If it is determined that the frame has not reached, the process proceeds to step S35. It returns and repeats the process of subsequent step S35 thru | or step S37.

  If it is determined in step S37 that the LTC change point table update processing has reached the OUT point, the OUT point confirmation unit 313 advances the processing to step S41 in FIG. In step S41, the OUT point continuity confirmation update processing unit 304 confirms the LTC continuity before and after the OUT point, updates the LTC change point table as necessary, and registers the OUT point as a change point. Perform continuity check update processing. At this time, the OUT point continuity confirmation update processing unit 304 controls the OVER occurrence confirmation unit 312 to monitor the status when the change point is registered in the LTC change point table. The OVER occurrence confirmation unit 312 monitors the status of the change point registered in the LTC change point table, and determines whether or not an OVER has occurred in step S42. If it is determined that OVER has not occurred, the OVER occurrence confirmation unit 312 advances the process to step S43.

  In step S43, the post-OUT-point update processing unit 305 performs post-OUT-point update processing for updating the LTC change point table for the portion after the OUT point. At this time, the post-OUT point update processing unit 305 controls the background OVER detection unit 311 and monitors the status of the change point of the background LTC in step S44 to determine whether OVER is detected. If it is determined that OVER is not detected, the background OVER detection unit 311 advances the process to step S45. At this time, the post-OUT point update processing unit 305 controls the OVER occurrence confirmation unit 312 to monitor the status when the change point is registered in the LTC change point table. The OVER occurrence confirmation unit 312 monitors the status of the change point registered in the LTC change point table and determines whether or not an OVER has occurred in step S45. If it is determined that OVER has not occurred, the OVER occurrence confirmation unit 312 advances the process to step S46. Further, at this time, the post-OUT point update processing unit 305 controls the END occurrence confirmation unit 314 to monitor the status when the change point is registered in the LTC change point table. The END generation confirmation unit 314 monitors the status of the change point registered in the LTC change point table, and determines whether or not an END indicating the end of the clip has occurred in step S46. If it is determined that END has not occurred, the END generation confirmation unit 314 returns the process to step S43.

  If it is determined in step S46 that END has occurred, the END occurrence confirmation unit 314 advances the processing to step S47. If it is determined that OVER is detected in step S32 of FIG. 26 or step S44 of FIG. 27, the background OVER detection unit 311 advances the process to step S47. Furthermore, when it is determined that OVER has occurred in step S34 or S36 of FIG. 26, or step S42 or step S45 of FIG. 27, the OVER occurrence confirmation unit 312 advances the process to step S47.

  In step S47, the update end processing unit 306 performs an update end process such as inserting the updated LTC change point table into the non-real time metadata, ends the LTC change point table update process, and proceeds to step S12 of FIG. The process is returned and the subsequent processes are repeated.

  As described above, it is possible to correctly perform destructive editing of content data more easily by performing an update process of information relating to time codes.

  As described above, by maintaining the consistency between the LTC of the real-time metadata and the LTC change point table of the non-real-time metadata, the user can execute correct cue-up reproduction of the clip even after destructive editing. In addition, since the time code information of the proxy data is also matched, the user can perform normal offline editing using the proxy data even after destructive editing.

  In addition, by performing destructive editing processing as described above, when there is no need to update time address information (LTC), processing for maintaining consistency between real-time metadata and non-real-time metadata is omitted. Therefore, the editing device 13 can reduce the load of the destructive editing process.

  Further, typical user bit information of non-real-time metadata is usually handled as a substitute for a reel number in a conventional tape medium, and unnecessary updating may cause user confusion. By saving the value of typical user bit information (before destructive editing) of the base record when editing only the user bits, the user can also read the typical user bit information on the material after user bit editing as before editing. Can be operated as a number.

  The series of processes described above can be executed by hardware or can be executed by software. In this case, for example, the editing device 13 of FIG. 1 may be configured as a personal computer as shown in FIG.

  In FIG. 28, a CPU (Central Processing Unit) 401 of the personal computer 400 performs various processes according to a program stored in a ROM (Read Only Memory) 402 or a program loaded from a storage unit 413 to a RAM (Random Access Memory) 403. Execute the process. The RAM 403 also appropriately stores data necessary for the CPU 401 to execute various processes.

  The CPU 401, ROM 402, and RAM 403 are connected to each other via a bus 404. An input / output interface 410 is also connected to the bus 404.

  The input / output interface 410 includes an input unit 411 including a keyboard and a mouse, a display including a CRT and an LCD, an output unit 412 including a speaker, a storage unit 413 including a hard disk, a modem, and the like. A communication unit 414 is connected. The communication unit 414 performs communication processing via a network including the Internet.

  A drive 415 is connected to the input / output interface 410 as necessary, and a removable medium 421 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor memory is appropriately mounted, and a computer program read from them is It is installed in the storage unit 413 as necessary.

  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 FIG. 28, this recording medium is distributed to distribute a program to a user separately from the apparatus main body, and includes a magnetic disk (including a flexible disk) on which a program is recorded, an optical disk ( Removable media 421 composed of CD-ROM (compact disk-read only memory), DVD (digital versatile disk), magneto-optical disk (including MD (mini-disk) (registered trademark)), or semiconductor memory In addition to being configured, it is configured by a ROM 402 in which a program is recorded and a hard disk included in the storage unit 413, which is distributed to the user in a state of being pre-installed in the apparatus body.

  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 figure which shows the structural example of the program production system to which this invention is applied. FIG. 2 is a schematic diagram illustrating a configuration example of a recording area of the optical disc in FIG. 1. It is a schematic diagram which shows the example of the directory structure of the file recorded on the optical disk of FIG. It is a schematic diagram which shows the example of the directory structure of the file recorded on the optical disk of FIG. It is a schematic diagram which shows the example of the directory structure of the file recorded on the optical disk of FIG. It is a schematic diagram which shows the structural example of a real-time metadata file. It is a figure explaining the example of a LTC change point. It is a figure explaining the example of a basic UMID change point, a time information change point, a position information change point, and a person information change point. It is a figure explaining the example of a KLV packet. It is a figure explaining the mode of nondestructive editing. It is a figure explaining the mode of destructive editing. It is a figure explaining the example in the case of updating the information regarding a time code by destructive editing. It is a schematic diagram explaining the structural example of an SDTI-CP time code. It is a block diagram which shows the structural example of the editing apparatus of FIG. 1 to which this invention is applied. It is a block diagram which shows the detailed structural example of the system control part of FIG. FIG. 16 is a block diagram illustrating a detailed configuration example of an LTC update unit in FIG. 15. It is a figure explaining generation | occurrence | production of OVER. It is a figure explaining generation | occurrence | production of OVER. It is a figure explaining generation | occurrence | production of OVER. It is a figure explaining generation | occurrence | production of OVER. It is a figure explaining generation | occurrence | production of OVER. It is a figure explaining generation | occurrence | production of OVER. It is a figure explaining generation | occurrence | production of OVER. It is a flowchart explaining a time code insertion process. It is a flowchart following FIG. 24 explaining a time code insertion process. 6 is a flowchart for explaining an LTC change point table update process. 27 is a flowchart following FIG. 26 for explaining LTC change point table update processing. It is a block diagram which shows the structural example of the personal computer to which this invention is applied.

Explanation of symbols

  1 program production system, 11 camcorder, 12 optical disc, 13 editing device, 21 material data, 22 metadata, 23 package data, 200 SDTI-CP time code, 201 time address, 202 user bits, 221 system control unit, 222 operation input Unit, 223 control information input unit, 224 control information output unit, 231 input unit, 232 recording signal processing unit, 233 information processing unit, 234 network interface, 235 metadata processing unit, 236 drive control unit, 237 pickup unit, 238 spindle Drive unit, 239 reproduction signal processing unit, 240 output unit, 251 material data input unit, 252 metadata input unit, 253 information multiplexing unit, 254 information decomposition unit, 255 material data output Unit, 256 metadata output unit, 261 control unit, 271 insertion information selection processing unit, 272 time code information reception unit, 273 clip writing unit, 274 clip reading unit, 275 time address information update unit, 276 TUB holding control unit, 277 RTM update unit, 278 PRX update unit, 279 LTC update unit, 280 KLV update unit, 281 TUB update unit, 291 input control unit, 292 communication control unit, 293 write control unit, 294 read control unit, 295 edit update processing control unit , 296 Output control unit, 301 IN point pre-update processing unit, 302 IN point continuity confirmation processing unit, 303 Insertion partial update processing unit, 304 OUT point continuity confirmation update processing unit, 305 OUT point post-update processing unit, 306 Update Processing unit, 311, Ground OVER detection unit, 312 OVER occurrence probability Department, 313 OUT point checking unit, 314 END generating confirmation unit, 400 a personal computer

Claims (10)

An information processing apparatus for processing content data including image data in which time code information is added to each frame,
Real-time metadata updating means for updating the time code information included in real-time metadata composed of data that requires real-time properties in reading processing at the time of reproduction of the content data;
The change point table, which is a list information of frames in which the change of the time code information is nonlinear, is included in non-real time metadata including data whose contents are not required in the reading process at the time of reproduction of the content data, An information processing apparatus comprising: non-real-time metadata updating means for updating in accordance with the content of the update by the real-time metadata updating means. Proxy data updating means for updating time code information of each frame of the low-resolution image data according to the contents of the update by the real-time metadata updating means in proxy data including low-resolution data of the image data; The information processing apparatus according to claim 1, further comprising: The non-real-time metadata update unit includes the content data in a section in which the time code information is updated by the real-time metadata update unit, a section before a section in which the time code information is updated, and the time Dividing into three sections after the section in which the code information is updated, extracting a change point where the change in the time code information is nonlinear for each section, and updating the change point table The information processing apparatus according to claim 1. OVER occurrence confirmation means for confirming the occurrence of a change point of OVER status by update by the real-time metadata update means,
The non-real-time metadata updating means is characterized in that when the occurrence of a change point whose status is OVER is confirmed by the OVER occurrence confirmation means, the update process is terminated without extracting a change point in the subsequent section. The information processing apparatus according to claim 3. In the background before the update by the real-time metadata update means, further comprising a background OVER detection means for detecting a change point of the status OVER,
The non-real-time metadata updating means may detect change points in the section after the section in which the OVER is detected by the background OVER detection means, even if the occurrence of the change point of status OVER is not confirmed by the OVER occurrence confirmation means. The information processing apparatus according to claim 4, wherein the update process is terminated without extraction. By updating by the real-time metadata updating means, it is selected which of a time address configured by time information included in the time code information and a user bit which is arbitrary information set by the user is updated. The information processing apparatus according to claim 1, further comprising: an insertion information selection unit. When the user bit is selected by the selection process by the insertion information selection unit, the time code information is stored using the time address included in the real-time metadata in order to hold the time address included in the real-time metadata. A time address updating means for updating the time address of
The information processing apparatus according to claim 6, wherein the real-time metadata update unit updates the real-time metadata using the time code information updated by the time address update unit. Typical user bit holding means for holding typical user bit information that is metadata for all frames of the image data included in the non-real-time metadata when the user bit is selected by the selection processing by the insertion information selection means When,
When the user bit is selected by the selection process by the insertion information selection unit, the non-real-time metadata updating unit updates the non-real-time metadata update unit using the typical user bit information held by the typical user bit holding unit. The information processing apparatus according to claim 6, further comprising: typical user bit update means for updating the typical user bit information of the real-time metadata again. An information processing method of an information processing apparatus for processing content data including image data in which time code information is added to each frame,
A real-time metadata update step for updating the time code information included in real-time metadata composed of data that requires real-time properties in the reading process at the time of reproduction of the content data;
The change point table, which is a list information of frames in which the change of the time code information is non-linear, included in non-real time metadata including data whose contents are not required in the reading process at the time of reproduction of the content data, A non-real-time metadata update step for updating according to the content of the update by the processing of the real-time metadata update step. In a program for causing a computer to perform processing related to content data including image data in which time code information is added to each frame,
A real-time metadata update step for updating the time code information included in real-time metadata composed of data that requires real-time properties in the reading process at the time of reproduction of the content data;
The change point table, which is a list information of frames in which the change of the time code information is nonlinear, is included in non-real time metadata including data whose contents are not required in the reading process at the time of reproduction of the content data, A non-real-time metadata update step for updating according to the content of the update by the processing of the real-time metadata update step.

Images