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

Description

  The present invention relates to an information processing apparatus and method, and a program. In particular, for example, when material data recorded on a disc is read, data ( The present invention relates to an information processing apparatus and method, and a program that can improve the convenience of material data.

  Conventionally, material data such as image data and audio data obtained by imaging or recording has been recorded on a tape device such as a video tape as a recording medium. As digitalization progresses, discs such as DVDs (Digital Versatile Discs) are being used as recording media.

  In particular, for example, in the case of production of a television program, not only generating and recording a large amount of material data, but also deleting unnecessary parts from the recorded material data, connecting multiple material data, Various edits such as adding special effects and inserting BGM (Back Ground Music) are repeated many times.

  Thus, in a large-scale image processing system such as production of a television program, it is necessary to process a large amount of data in a complicated manner. Therefore, there is a method of adding an ID that can be uniquely identified globally to each material data so that each material data can be easily managed.

  However, in recent years, in order to improve the convenience of material data in the editing work as described above, for example, various kinds of data such as low-resolution image data (low-resolution data (including audio data)) and metadata are used. Data has been added to material data. In addition, with the improvement of image processing technology, editing functions have become more multifunctional, and editing operations have become more complicated.

  For example, an image editing apparatus that facilitates multi-channel editing by simultaneously recording images of a plurality of channels having the same time information on one optical disk and supplying the optical disk to the editing apparatus has been proposed. (See Patent Document 1).

  In order to cope with this situation, not only global unique identification information is assigned to each material data, but also each data unit of the material data (for example, in the case of image data, a clip unit, a GOP unit, or a frame unit) Each device is assigned globally unique identification information, and various devices that handle material data are assigned to low resolution data and metadata added to material data by assigning globally unique identification information for each data unit. It has become possible to handle data more accurately and easily.

JP-A-11-136616

  However, when managing material data using a globally unique ID as described above, for example, in editing work, material data is read from an optical disk or the like as a recording medium and recorded on the optical disk. The material data is managed as data different from each other. That is, when material data is read from the optical disc, a new ID is always generated and replaced with the ID added to the read material data.

  Incidentally, as described above, a plurality of IDs are assigned to one piece of material data (and data added thereto) as described above. For example, as shown in FIG. 1, a plurality of globally unique IDs (ID A, ID B, ID C,...) Are assigned to a file A2 that is material data recorded on the optical disc 1. When such a file A2 is read from the optical disc 1 and a file B4 is generated, a new ID generation process 3 is performed, and a new ID is added, so that a plurality of files added to the file B4 are added. Since the globally unique IDs (ID P, ID Q, ID R,...) Are different from the ID added to the file A2, these files have the same contents as the material data. However, they are managed as different files and there are many IDs, so for the editor who is the user, which data in which file and which data in which file have the same contents There is a problem that it becomes difficult to manage whether it is over data.

  Moreover, as described above, such editing work is performed many times. That is, the same material data recorded on the optical disc is read out many times. In such a case, as shown in FIG. 2, when the file A5 (ID A) recorded on the optical disc 1 is read twice, the new ID generation processing 3 will read it from the same file A5. Instead, different IDs are assigned to the file B6 (ID B) read for the first time and the file C7 (ID C) read for the second time. In this way, even though the content is the same as the material data, a different ID is assigned each time it is read, so for the editor who is the user, which data in which file is the same as which data in which file There is a problem that it becomes more difficult to manage whether the data is content data.

  The present invention has been made in view of such circumstances, and is intended to improve the convenience of data.

An information processing apparatus according to the present invention includes a reading unit that reads data from a recording medium together with the recording data identification information, and a part of the value of the recording data identification information added to the data read from the recording medium by the reading unit. Output data identification information generating means for generating output data identification information for identifying data read from the recording medium by the reading means, and output data identification information generated by the output data identification information generating means Output data identification information adding means for adding to the data read from the recording medium by the reading means , and the output data identification information generating means includes a plurality of internal data included in one data recorded on the recording medium. Of the recorded data identification information added to each, the data was added to one predetermined internal data An extraction unit that extracts one piece of recording data identification information, a duplication unit that duplicates one piece of recording data identification information extracted by the extraction unit, and a plurality of recording data identification information that is duplicated by the duplication unit, by changing the number of digits of the random number, and wherein Rukoto a random value changing means for generating a plurality of output data identification information.

The output data identification information generating means further comprises a counting means for counting the number of output data identification information generated so far each time output data identification information is generated, and the random value changing means is a recording data identification By adding the count value by the counting means to the random value included in the information, a plurality of pieces of output data identification information having different random value values can be generated.

  The output data identification information generating means further includes a format conversion means for converting a file format of the data read from the recording medium by the reading means, and the output data identification information generating means adds the recording data identification added to the data before format conversion. It is possible to change the value of a part of the information to generate the required number of pieces of output data identification information in the data after the format conversion.

The information processing method of the present invention includes a read control step for controlling data to be read from the recording medium together with the recording data identification information, and is added to the data read from the recording medium controlled by the processing of the read control step. Output data identification information generation for generating output data identification information for identifying data read from the recording medium controlled by the process of the read control step by changing a part of the value of the recorded data identification information a step, viewed including the output data identification information adding step of adding the data read from the recording medium is controlled by the process control steps reads output data identification information generated by the processing of the output data identification information generation step The output data identification information generation step includes one data recorded on the recording medium. An extraction step of extracting one piece of recording data identification information added to one predetermined internal data from among the recording data identification information added to each of the plurality of internal data included in the data, and processing of the extraction step By duplicating one extracted record data identification information, and by changing a random number value of a predetermined number of digits included in each of the plurality of record data identification information duplicated by the process of the duplication step, And a random value changing step for generating the output data identification information .

The program according to the present invention provides a computer that reads from the recording medium the data to which recording data identification information for identifying data recorded on the recording medium is added, identifies the data from the recording medium, and identifies the recording data. A reading means for reading together with the information, and among the recording data identification information added to each of a plurality of internal data included in the data read by the reading means, is added to one predetermined internal data. An extraction unit that extracts one piece of the recording data identification information, a duplication unit that duplicates the one piece of recording data identification information that is extracted by the extraction unit, and a plurality of the recording data identification information that is duplicated by the duplication unit By changing the random number of a predetermined number of digits included in each, the reading means Random value changing means for generating a plurality of output data identification information for identifying the extracted data, and a plurality of the output data identification information generated by the random value changing means are read by the reading means It functions as output data identification information adding means to be added to the data .

In the information processing apparatus and method and the program of the present invention, data is read from the recording medium together with the recording data identification information, and the value of the recording data identification information added to the data read from the recording medium By changing a part, output data identification information for identifying the data read from the recording medium is generated, and the generated output data identification information is added to the data read from the recording medium. Among the recorded data identification information added to each of a plurality of internal data included in one data recorded on the recording medium, one recorded data identification information added to one predetermined internal data is The extracted one record data identification information is duplicated and included in each of the plurality of duplicated record data identification information. By changing the random number of digits, a plurality of output data identification information is generated.

  According to the present invention, data can be processed. In particular, for example, when the material data recorded on the disc is read, the management of the identification number information of the material data is facilitated, whereby the convenience of the material data can be improved.

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

  FIG. 3 shows an AV network system 10 to which the present invention is applied (a system is a logical collection of a plurality of devices, regardless of whether or not each component device is in the same casing). 2 shows an example of the configuration of an embodiment.

  The disk device 11 includes a disk drive unit 21, a format conversion unit 22, and a communication I / F 23. The disk device 11 receives an AV data file transmitted via the network 14, records it on the optical disk 17, and records the optical disk. The AV data file recorded in 17 is read out and transmitted via the network 14.

  That is, the optical disk 17 can be attached to and detached from the disk drive unit 21. The disk drive unit 21 records (writes) an AV independent format file, which will be described later, supplied from the format conversion unit 22 to the optical disk 17 by driving the optical disk 17 mounted thereon. The AV independent format file is read and supplied to the format conversion unit 22.

  The format conversion unit 22 converts the AV independent format file supplied from the disk drive unit 21 into a standard AV multiplex format file, which will be described later, and supplies the file to the communication I / F 23. The format conversion unit 22 converts the standard AV multiplex format file supplied from the communication I / F 23 into an AV independent format file and supplies the converted file to the disk drive unit 21.

  The communication I / F 23 includes, for example, an IEEE (Institute of Electrical and Electronics Engineers) 1394 port, a USB (Universal Serial Bus) port, a LAN (Local Area Network) connection NIC (Network Interface Card), an analog modem, , A TA (Terminal Adapter), a DSU (Digital Service Unit), an ADSL (Asymmetric Digital Subscriber Line) modem, and the like. In other words, the communication I / F 23 transmits the standard AV multiplex format file supplied from the format conversion unit 22 via the network 14, and the standard AV multiplex format file transmitted via the network 14. It is received and supplied to the format conversion unit 22.

  In the disk device 11 configured as described above, the communication I / F 23 receives a standard AV multiplex format file transmitted via the network 14 and supplies the file to the format conversion unit 22. The format conversion unit 22 converts the standard AV multiplex format file from the communication I / F 23 into an AV independent format file and supplies it to the disk drive unit 21. Then, the disk drive unit 21 records the AV independent format file from the format conversion unit 22 on the optical disk 17 mounted thereon.

  Further, in the disk device 11, the disk drive unit 21 reads an AV independent format file from the optical disk 17 loaded therein and supplies it to the format conversion unit 22. The format conversion unit 22 converts the AV independent format file from the disk drive unit 21 into a standard AV multiplex format file and supplies it to the communication I / F 23. The communication I / F 23 transmits the standard AV multiplex format file from the format conversion unit 22 via the network 14.

  Here, the standard AV multiplex format file is, for example, a file conforming to the MXF standard, and includes a header, a body, and a footer. Since the standard AV multiplex format file conforms to the MXF standard, video data and audio data, which are AV data, are multiplexed and arranged, for example, in units of one frame. ing.

  In FIG. 1, AV devices 15 and 16 connected to the network 14 are devices compliant with the MXF standard capable of handling files compliant with the MXF standard. Therefore, the AV devices 15 and 16 are standard. An AV multiplex format file can be transmitted to the disk device 11 via the network 14. Further, the AV devices 15 and 16 can receive a standard AV multiplex format file transmitted from the disk device 11 via the network 14. That is, file exchange of standard AV multiplex format files can be performed between the disk device 11 and the AV devices 15 and 16 via the network 14. Furthermore, the AV devices 15 and 16 can perform various processes such as streaming playback on the received standard AV multiplex format file.

  Here, an apparatus that conforms to the current MXF standard, such as the AV apparatus 15 or 16, is hereinafter referred to as a standard apparatus as appropriate.

  On the other hand, an AV independent format file is composed of a header, a body, and a footer in the same manner as a standard AV multiplex format file, but only the format of the body is different from the standard AV multiplex format. That is, in the AV independent format file, video data and audio data are separate files. A video file that is a video data file has a header and a footer that have the same format as a standard AV multiplex format file, but video data is collectively arranged in the body. An audio file, which is an audio data file, also has a header and footer in the same format as a standard AV multiplex format file, but the audio data is collectively arranged in the body.

  Therefore, if a video file or audio file in an AV independent format is transmitted from the disk device 11 to the AV device 15 or 16, the AV device 15 or 16 that is a standard device does not support the AV independent format. As long as video data and audio data arranged in the body of the AV independent format video file and audio file cannot be handled, the AV independent format video file and audio file itself can be handled. That is, a video file or audio file in an AV independent format is composed of a header, a body, and a footer in the same way as a standard AV multiplex format file, and the header and footer have the same format as a standard AV multiplex format file. Since it is adopted, unless it refers to the “contents” of the body (data placed in the body), video files and audio files in the AV independent format are equivalent to files in the standard AV format (standard AV format) Compliant file). Therefore, even when the AV devices 15 and 16 that are standard devices do not support the AV independent format, the video files and audio files themselves of the AV independent format can be handled.

  In other words, it is possible to perform only file exchange of AV independent format files between the disk device 11 and the AV devices 15 and 16 which are standard devices.

  As described above, an AV independent format file is equivalent to a standard AV multiplexed format file unless the contents of the body are referred to. From this viewpoint, an AV independent format file is a standard AV multiplexed format file. It can be said that it is compatible with other files.

  Next, in FIG. 3, the optical disk 17 can be attached to and detached from the disk device 12. The disk device 12 is, for example, a standard device, like the AV devices 15 and 16, and reads AV independent format video files and audio files from the optical disk 17 mounted on the disk device 12 and supplies them to the editing device 13.

  That is, as described above, since the video file and audio file in the AV independent format are equivalent to the file in the standard AV multiplex format unless the “content” of the body is referred to, the disk device 12 as the standard device is An AV independent format video file or audio file can be read from the optical disc 17.

  The editing device 13 is a device compatible with the AV independent format that can handle files of the AV independent format. For example, the AV independent editing is performed on the AV independent format video file or audio file supplied from the disk device 12. The AV independent format video file or audio file as the editing result is supplied to the disk device 12.

  Then, the disk device 12 records the AV independent format video file and audio file supplied from the editing device 13 on the optical disk 17 loaded therein.

  That is, as described above, since the video file and audio file in the AV independent format are equivalent to the file in the standard AV multiplex format unless the “content” of the body is referred to, the disk device 12 as the standard device is An AV independent format video file or audio file can be recorded on the optical disc 17.

  As described above, in a standard AV multiplex format file, video data and audio data are multiplexed and arranged, for example, on a frame-by-frame basis in the body. In files and audio files, video data and audio data are collectively arranged in the body, so that editing such as AV independent editing can be easily performed. And since the AV independent format file has the same header and footer as the standard AV multiplex format file, it is compatible with the standard AV multiplex format file unless you refer to the “contents” of the body. Can be handled with standard equipment.

  Next, FIG. 4 shows an example of a standard AV multiplex format.

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

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

  A standard AV multiplex format file is composed of a header (File Header), a body (File Body), and a footer (File Footer) sequentially arranged from the top.

  In the header, a header partition pack, header metadata, and an index table are sequentially arranged from the top. In the header partition pack, data for specifying the header, data format arranged in the body, information indicating a file format, and the like are arranged. In the header metadata, for example, metadata in units of files such as a file creation date and information related to data arranged in the body is arranged. In the index table, a table representing the position of an edit unit, which will be described later, is arranged in the body.

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

  In addition, as information indicating the file format arranged in the header partition pack, information indicating the standard AV multiplex format is adopted in the standard AV multiplex format file, but in the AV independent format file, the information indicating the AV independent format is used. Information is adopted. However, the format of the header partition pack itself is the same in the standard AV multiplex format and the AV independent format.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

  For this reason, in a file in which video data and audio data are arranged separately, the video data and audio data must be played back after all the video data files and audio data files are received. However, in the standard AV multiplex format, video data and audio data are multiplexed in units of frames, so if one frame of video data and audio data is received, the video data of that frame And audio data can be played immediately. Therefore, it can be said that the standard AV multiplex format is suitable for streaming.

  As described above, the standard AV format is suitable for streaming because video data and audio data are multiplexed in units of frames. On the other hand, however, it is difficult to perform AV independent editing in which video data and audio data are separately edited.

  Furthermore, file-unit metadata is also scattered in the edit unit system items, and is difficult to handle during editing.

  In addition, the AES3 format that can be adopted in the standard AV format has a specification in which at least 4 bytes are assigned to one sample of audio data, and the overall size of the file becomes large.

  FIG. 5 shows an example of the AV independent format.

  In the AV independent format, the video data, the audio data, the file-unit metadata, and the user data multiplexed in the standard AV multiplex format are each arranged as a file.

  That is, in the AV independent format, picture items in which video data is arranged in the standard AV multiplex format are collectively arranged in the body, and further, a header and footer of the same format as the standard AV multiplex format are added to the body, A video file is composed.

  Since the video file body in the AV independent format is arranged with picture items that are integral multiples of the sector length of the optical disc 7, the size of the entire body is also integral multiples of the sector length of the optical disc 7. ing. That is, the body of the video file in the AV independent format has a size with sector alignment.

  In FIG. 4, an index table is shown in the header of the standard AV multiplex format file. In MXF, as described above, the index table is optional, and in the video file of FIG. The same applies to files), and does not employ an index table.

  In the AV independent format, the multiplexed 8-channel audio data arranged in the sound item in the standard AV multiplex format is separated into audio data for each channel, and converted from AES3 format to WAVE format. These are arranged in the body of the file for each channel in the KLV structure, and further, the header and footer of the same format as the standard AV multiplex format are added to the body to constitute an audio file.

  That is, in the AV independent format, the audio file of each channel is configured independently for the audio data of 8 channels. Each channel's audio file is the WAVE format of the channel's audio data, and the entire KLV structure is placed in the body, and the body has headers and footers in the same format as the standard AV multiplex format. Added and configured.

  In addition, as described above, the audio file in the AV independent format has a KLV structure in which WAVE audio data of a certain channel is arranged, and the size of the entire audio data is the optical disc. It is not always an integral multiple of the sector length of 7. Therefore, in order to achieve sector alignment, the body of an AV independent format audio file is provided with KLV-structured fillers necessary for sector alignment after the KLV-structured audio data.

  In the AV independent format, in addition to the video file as described above and the audio file for each of the eight channels, the file unit metadata in which the file unit metadata arranged in the header metadata in the standard AV multiplex format is arranged together. A frame-unit metadata file is configured in which files and system items in which frame-unit metadata is arranged in the standard AV multiplex format are arranged together. Furthermore, in the AV independent format, an auxiliary file in which auxiliary items in which user data is arranged in the standard AV multiplex format is arranged together is configured.

  In the AV independent format, a master file in which pointers are described for a video file, an audio file for each of 8 channels, a metadata file for each file, a metadata file for each frame, and an auxiliary file. Is configured.

  That is, the master file is described in, for example, XML (Extensible Markup Language), and includes a video file, an audio file for each of 8 channels, a metadata file for each file, a metadata file for each frame, and an auxiliary file. For example, the file name of each file is described as a pointer to each file.

  Accordingly, a video file, an audio file for each of eight channels, a metadata file in units of files, a metadata file in units of frames, and an auxiliary file can be referred to from the master file.

  For example, the auxiliary file can be an optional file.

  In FIG. 5, the file-unit metadata file, the frame-unit metadata file, and the auxiliary file do not have the same format header and footer as the standard AV multiplex format. Data files, frame-by-frame metadata files, and auxiliary files can also be configured by adding headers and footers in the same format as the standard AV multiplex format.

  Furthermore, a minimum set of file-unit metadata is arranged in the header metadata constituting the header of the AV independent format video file and audio file.

  That is, in the AV independent format, there is a file unit metadata file in which the file unit metadata arranged in the header metadata in the standard AV multiplex format is arranged together, so the file arranged in the metadata file It is redundant to place the unit metadata redundantly in the header metadata that constitutes the header of the video file and the audio file, and the size of the entire AV independent format file will be increased. .

  However, in MXF, the header metadata is an indispensable item for the header. If the header is configured without any header metadata, the header is not the same format as the standard AV multiplex format. It becomes.

  On the other hand, in MXF, there are various items of metadata in file units to be arranged in the header metadata. Among these items, there are essential items and optional items.

  Therefore, in order to suppress the increase in the size of the file and maintain compatibility with the standard AV multiplex format, the header metadata constituting the header of the video file and the audio file in the AV independent format is In the minimum set of file-unit metadata, that is, only metadata of items that are required to be arranged in header metadata in MXF.

  As described above, in the AV independent format, the video data is collectively arranged in the video file, and the audio data of each channel is collectively arranged in the audio file of the channel. Editing such as AV independent editing, which is edited separately, can be easily performed.

  Furthermore, in the AV independent format, since the audio data is in the WAVE format, the data amount can be reduced as compared with the case where the AES3 format audio data is adopted as in the standard AV independent format. As a result, when an AV independent format file is recorded in a storage such as the optical disc 7, the storage capacity required for the recording can be suppressed as compared to recording a standard AV multiplex format file. it can.

  In addition, AV independent format video files and audio files are composed of a header, a body, and a footer from the top in the same manner as standard AV multiplex format files. Since they are of the same format, when the video device or audio file in the AV independent format is recorded on the removable optical disc 7 in the disc device 1 and the optical disc 7 is mounted on the disc device 2, the disc device 2 If it is a standard apparatus (an apparatus capable of handling MXF files), it is possible to read AV independent format video files and audio files from the optical disc 7.

  Furthermore, in the AV independent format, the metadata in units of files and the metadata in units of frames are collected separately, and both are made into one file, so that search processing using metadata becomes easy. .

  Each of the items shown in FIGS. 6 to 11 is included in the header metadata of the file header in the standard AV multiplex format and in the header metadata included in the header portion of the video file in the AV independent format. In addition, a UUID (Universally Unique IDentifier) that is a globally unique ID is assigned. In FIGS. 6 to 11, only items related to UUID are shown. That is, the actual header metadata includes data other than the set names shown in FIGS. 6 to 11, and each set includes information other than the UUID.

  6 and 7 are diagrams showing the UUID distribution of the header metadata included in the header part of the AV independent format video file recorded on the optical disc 17, and FIGS. It is a figure which shows distribution of UUID of the header metadata contained in the file header of a standard AV multiplex format.

  That is, the UUID shown in FIGS. 6 and 7 is identification information (recording data identification information) for identifying data (recording data) recorded on the recording medium, and the UUID shown in FIGS. This is identification information (output data identification information) for identifying data (output data) read from the recording medium. As shown in FIGS. 6 to 11, these UUIDs are identification information for identifying data (internal data) included in recording data or output data. Specifically, these UUIDs are information for identifying, for example, information included in each set, and indicating their context and subordinate relationships.

  Note that the same UUID is assigned to each UUID assigned the same number in the link column. That is, in the AV independent format, 18 types of UUIDs are assigned to each set, and in the standard AV multiplex format, 26 types of UUIDs are assigned to each set. The UUID of the AV independent format file is identified by a random value included in the UUID in the file. In other words, 18 different values exist as random numbers of UUIDs in one AV independent format file.

  For example, when the disk device 11 reads a file from the optical disk 17, the disk device 11 converts the file of the AV independent format into the standard AV multiplex format, and assigns 26 types of UUIDs as shown in FIGS. There is a need.

  Therefore, the format conversion unit 22 of the disk device 11 does not newly create all these UUIDs, but, as will be described later, the header of the video file recorded on the optical disk 17 shown in FIGS. 6 and 7. Generate by using UUID stored in metadata. Specifically, the format conversion unit 22 indicates the address “0x000740” of the header metadata preface set (Preface Set) shown in the top row of FIG. 0x000744 "), the 26 types of UUIDs described above are generated using the UUID configured as the item name" UUID ".

  By doing so, not only can a large number of UUIDs be generated easily, but the UUID is related to the file recorded on the optical disc 17 and the file after being read, so that the user is a user. The editor can easily grasp the relationship between these files and various data included in these files. As will be described in detail later, UUIDs are generated in the same manner every time a file is read out. Therefore, UUIDs are similarly assigned to all files read from the same file recorded on the optical disc 17. Therefore, the editor can easily grasp that a plurality of files (and various data included in the files) generated by being read a plurality of times have the same contents.

  Next, FIG. 12 shows a configuration example of the format conversion unit 22 included in the disk device 11 of FIG.

  The format conversion unit 22 includes a standard / independent conversion unit 31 and an independent / standard conversion unit 32.

  The standard / independent conversion unit 31 converts the standard AV multiplex format file of FIG. 4 supplied from the communication I / F 23 into the AV independent format file of FIG. The independent / standard conversion unit 32 converts the AV independent format file of FIG. 5 supplied from the disk drive unit 21 into a standard AV multiplex format file of FIG. 4 and supplies it to the communication I / F 23.

  Next, FIG. 13 shows a configuration example of the independent / standard conversion unit 32 of FIG.

  The buffer 41 is an AV independent format file (master file, metadata file in units of files, metadata file in units of frames, auxiliary files, video files, 8 channels supplied from the disk drive unit 21 (FIG. 3). Audio files).

  The file acquisition unit 42 refers to the master file stored in the buffer 41, so that a file unit metadata file, a frame unit metadata file, an auxiliary file, a video file, and an audio file for each of the eight channels. Recognize the name, and based on the file name, the disk drive unit 21 converts the metadata file for each file, the metadata file for each frame, the auxiliary file, the video file, and the audio file for each of the eight channels via the buffer 41. To be read from the optical disc 17. Further, the file acquisition unit 42 converts the acquired file unit metadata file and frame unit metadata file into the metadata file processing unit 43, the auxiliary file into the auxiliary file processing unit 44, and the video file into the video file. The file processing unit 45 is supplied with audio files of eight channels to the audio file processing unit 46, respectively. Further, the file acquisition unit 42 supplies the video file to the instance UID generation unit 51.

  The metadata file processing unit 43 extracts the file unit metadata from the file unit metadata file supplied from the file acquisition unit 42, and the frame unit metadata is arranged from the frame unit metadata file. The item is extracted and supplied to the data synthesis unit 47.

  The auxiliary file processing unit 44 extracts the auxiliary items from the auxiliary file supplied from the file acquisition unit 42 and supplies the extracted items to the data synthesis unit 47.

  The video file processing unit 45 extracts a picture item from the video file supplied from the file acquisition unit 42 and supplies it to the data synthesis unit 47.

  The audio file processing unit 46 extracts the audio data of each channel from the audio file of each of the eight channels supplied from the file acquisition unit 42, and further configures a sound item in which the audio data of each channel is multiplexed and arranged. Then, the data is supplied to the data synthesis unit 47.

  The instance UID generation unit 51 extracts header metadata from the video file supplied from the file acquisition unit 42, and further extracts the UUID (of the address “0x000744”) of the above-described pre-face set from the header metadata. Then, based on the UUID, 26 UUIDs (instance UIDs) are generated and supplied to the data synthesis unit 47.

  The data synthesis unit 47 is supplied from the file unit metadata and system items supplied from the metadata file processing unit 43, the auxiliary items supplied from the auxiliary file processing unit 44, and the video file processing unit 105. Using the picture item, the sound item supplied from the audio file processing unit 46, and the instance UID supplied from the instance UID generation unit 51, a standard AV multiplex format file is constructed and supplied to the buffer 48.

  The buffer 48 temporarily stores the standard AV multiplex format file supplied from the data synthesis unit 47 and supplies the file to the communication I / F 23 (FIG. 3).

  Next, FIG. 14 shows a configuration example of the instance UID generation unit 51 of FIG.

  The video file supplied from the file acquisition unit 42 is supplied to the header / footer extraction unit 61. The header / footer extraction unit 61 extracts a header and a footer from the video file supplied thereto, further extracts header metadata from the header, and supplies the header metadata to the UUID extraction unit 62. The UUID extraction unit 62 extracts the UUID from the sequence by separating the UUID arranged in the header metadata pre-face set supplied from the header / footer extraction unit 61, and converts it into the time information change unit 63. To supply. The time information change unit 63 increments the value of the time information (Time Snap) included in the UUID supplied from the UUID extraction unit 62 by +1 and supplies the incremented value to the UUID holding unit 64. The UUID holding unit 64 temporarily holds the UUID supplied from the time information changing unit 63 and, based on a request from the addition processing unit 71, adds a copy (duplication) of the held UUID to the random number value changing unit 65. To the unit 71.

  When the addition processing unit 71 requests the UUID holding unit 64 to supply the UUID and acquires the UUID supplied from the UUID holding unit 64, the addition processing unit 71 acquires the count value of the counter 72, and uses the acquired count value as the UUID. The value is added to the value of the random number part (RandomNumber) of the UUID supplied from the holding unit 64 and supplied to the data synthesis unit 47 (FIG. 13). Then, the addition processing unit 71 controls the counter 72 to execute the count process, and increments the count value by +1. In this way, the addition processing unit 71 acquires the UUID from the UUID holding unit 64, adds the count value to the value of the random number part (random number value) of the UUID, and supplies the value to the data synthesis unit 47 as the instance UID. It repeats 26 times, 26 instance UIDs are generated and supplied to the data synthesis unit 47. That is, the 26 instance UIDs output from the addition processing unit 71 (random number change unit 65) are IDs having different random number values.

  Next, FIG. 15 shows a configuration example of the video file processing unit 45 of FIG.

  The video file supplied from the file acquisition unit 42 is supplied to the header / footer removal unit 81. The header / footer removing unit 81 removes the header and footer from the video file supplied thereto, and supplies the remaining body to the disassembling unit 82. The disassembling unit 82 separates the sequence of picture items arranged in the body supplied from the header / footer removing unit 81, so that other items (system items, sound items, auxiliary items) are separated from the sequence. A unit to be multiplexed, that is, here, individual picture items in which video data in units of frames is arranged is extracted and supplied to the data synthesis unit 47 (FIG. 13).

  Next, FIG. 16 shows a configuration example of the audio file processing unit 46 of FIG.

  The 8-channel audio files supplied from the file acquisition unit 42 are supplied to the header / footer removal unit 91. The header / footer removing unit 91 removes the header and footer from the audio file of each of the 8 channels supplied thereto, and supplies the remaining body of each channel to the KLV decoder 92.

  The KLV decoder 92 decomposes the KLV structure of the body of each channel supplied from the header / footer removing unit 91 and supplies the WAVE audio data of each channel obtained thereby to the data converting unit 93.

  The data converter 93 converts the audio data of each channel in the WAVE format supplied from the KLV decoder 92 into the audio data of each channel in the AES3 format, and supplies the audio data to the channel multiplexer 94.

  The channel multiplexing unit 94 multiplexes the audio data of each channel supplied from the data conversion unit 93 in units of samples, and supplies the multiplexed audio data obtained as a result to the KLV encoder 95.

  The KLV encoder 95 divides the multiplexed audio data supplied from the channel multiplexing unit 94 into units corresponding to each frame of video data, and KLV codes the multiplexed audio data corresponding to each frame into a KLV structure. Furthermore, the KLV encoder 95 adds a filler KLV structure that is insufficient for the data length of the fixed-length sound item to the KLV structure of the multiplexed audio data corresponding to each frame. The data is configured and supplied to the data synthesis unit 97 (FIG. 13).

  Next, FIG. 17 shows a configuration example of the data synthesis unit 47 of FIG.

  The header / footer generating unit 101 is supplied with metadata in units of files output from the metadata file processing unit 43. The header / footer generating unit 101 generates a header and footer of a standard AV multiplex format file, and further arranges the file unit metadata from the metadata file processing unit 43 in the header metadata of the header, The header and footer are supplied to the instance UID insertion unit 104.

  In addition to the header and footer supplied from the header / footer generation unit 101, the instance UID insertion unit 104 is supplied with 26 instance UIDs output from the instance UID generation unit 51. The instance UID insertion unit 104 has the same information as the list shown in FIGS. 8 to 11, and grasps in advance which instance UID should be inserted into which part. Based on this information, the instance UID insertion unit 104 appropriately inserts the instance UID output by the instance UID generation unit 51 into each set of header metadata included in the header supplied from the header / footer generation unit 101. Then, the instance UID insertion unit 104 supplies the header and footer including the header metadata into which the instance UID is inserted to the header / footer adding unit 103.

  The multiplexing unit 102 includes a system item output from the metadata file processing unit 43, an auxiliary item output from the auxiliary file processing unit 44, a picture item output from the video file processing unit 45, and an audio file processing unit 46. Sound items output by are supplied. The multiplexing unit 102 composes a sequence of edit units by sequentially multiplexing the system eyelem, picture item, sound item, and auxiliary item supplied thereto in that order, and the sequence of the edit unit. Is supplied to the header / footer adding unit 103 as a body.

  The header / footer adding unit 103 includes a header (File Header) and a footer (File Footer) including header metadata supplied from the instance UID insertion unit 104 and inserted with the instance UID in the body supplied from the multiplexing unit 102. ) Is added to form a standard AV multiplex format file for output.

  Next, in the independent / standard conversion unit 32 of FIG. 13, an instance UID generation process for generating an instance UID, a metadata file process for processing a metadata file, an auxiliary file process for processing an auxiliary file, and a video file A video file process for processing the audio file, an audio file process for processing the audio file, and a synthesis process for synthesizing (generating) a standard AV multiplex format file using these processing results.

  18 and FIG. 20 to FIG. 24, the instance UID generation processing, metadata file processing, auxiliary file processing, video file processing, audio file processing performed by the independent / standard conversion unit 32, The synthesis process will be described. Further, description will be made with reference to FIG. 19 as necessary.

  First, the instance UID generation process will be described with reference to the flowchart of FIG. Further, description will be made with reference to FIG. 19 as necessary.

  The instance UID generation process is started when, for example, a master file is read from the optical disk 17 by the disk drive unit 21 and stored in the buffer 41.

  That is, first, in step S1, the file acquisition unit 42 recognizes the file name of the video file by referring to the master file stored in the buffer 41. Further, in step S 1, the file acquisition unit 42 acquires the video file based on the file name by causing the disk drive unit 21 to read from the optical disk 17 through the buffer 41 and supplies the video file to the instance UID generation unit 51. Then, the process proceeds to step S2. In step S2, the header / footer extraction unit 61 of the instance UID generation unit 51 extracts the header and footer from the video file supplied from the file acquisition unit 42, and supplies the extracted header and footer to the UUID extraction unit 62. The process proceeds to step S3.

  In step S3, the UUID extraction unit 62 uses the header metadata included in the header of the video file supplied from the header / footer extraction unit 61, and the UUID configured as shown in FIGS. Among them, the UUID arranged at the address “0x000744” of the pre-face set shown in the top row in the list of UUIDs in FIG. 6 is extracted, and the UUID is supplied to the time information changing unit 63, and the process goes to step S4. Proceed with the process. In step S4, the time information changing unit 63 changes the time information (time snap) included in the UUID supplied from the UUID extracting unit 62 by incrementing a predetermined constant (for example, +1).

  FIG. 19 is a diagram illustrating a configuration example of the UUID. In FIG. 19, for example, the configuration of the UUID 120 in a transmission file format for data transmission via a network compliant with the IEEE 1394 standard (hereinafter referred to as IEEE 1394 network) is shown. The UUID 120 is shown as a bit string divided every 8 bits (1 byte), and a bit indicated by “X” indicates a bit whose value is “0” or “1”. Note that the values of the fourth to sixth bytes from the right are indicated by hexadecimal numbers.

  From the left, the UUID 120 is composed of a 7-bit time snap 121, a 2-bit fixed value 122, a 6-bit random value 123, and a 64-bit (8 bytes) IEEE 1394 node unique ID 124.

  The time snap 121 is an area for storing information about time or time. Time information is stored in 3 bytes (24 bits) from the left, and time information (Julian date information) based on Julian date is stored in the remaining 4 bytes (32 bits). Is stored.

  The fixed value 122 is a 2-bit area in which a predetermined value “11” is stored. This value is a value for distinguishing from other IDs such as a material number such as UMID (Unique Material IDentifier). The random value 123 is an area for storing a random value, that is, an arbitrary value, and is composed of 6 bits. In addition to the random value calculated by a predetermined method, for example, a value obtained using a time snap, an arbitrary value, or the like can be stored in the random value 123. This random number value 123 avoids, for example, when a plurality of IDs (identical IDs) having the same creation time are generated and assigned to different formats when the time setting of the device is incorrect, for example. Used for.

  The IEEE 1394 node unique ID 124 is an area in which a unique 64-bit identifier pre-assigned to an IEEE 1394 interface (hardware) that becomes a node in the IEEE 1394 network is stored, and the 3 bytes from the 3rd byte to the 5th byte from the left. Stores the address unique to the interface manufacturer or distributor (manufacturer or vendor). In the original configuration of the IEEE 1394 node unique ID, the unique address assigned to the manufacturer or sales company (manufacturer or vendor) of this interface is configured in the most significant 3 bytes of the IEEE 1394 node unique ID. In the IEEE 1394 node unique ID 124 area, the position of the least significant 2 bytes (16 bits) is unique to the IEEE 1394 node so that the UUID 120 has the same structure as the material number in the UMID added to other data. The ID is adjusted to be the most significant 2 bytes (9th byte and 10th byte from the left in the entire UUID 120). Accordingly, in the IEEE 1394 node unique ID 124 of FIG. 19, the 4th to 6th bytes from the right (24 bits indicated by hexadecimal values “08”, “00”, and “46” in the figure) are the original. The upper 24 bits of the IEEE 1394 node unique ID.

  Returning to FIG. 18, in step S4, the time information changing unit 63 increments the value of the time snap 121 of the UUID 120 configured as shown in FIG. 19 by a predetermined constant (for example, +1), and increments the value. The UUID 120 is supplied to the UUID holding unit 64, and the process proceeds to step S5. In step S5, the UUID holding unit 64 holds the UUID supplied from the time information changing unit 63, and notifies the random value changing unit 61 that the UUID has been held. Then, the process proceeds to step S6.

  Upon receiving the notification from the UUID holding unit 64, the addition processing unit 71 of the random value changing unit 65 accesses the UUID holding unit 64 at a predetermined timing, and requests the UUID held by the UUID holding unit 64. Based on the request, the UUID holding unit 64 supplies the held UUID (more precisely, a copy of the held UUID) to the addition processing unit 71. Upon obtaining the supplied UUID in step S6, the addition processing unit 71 obtains the current count value from the counter 72, and adds the count value to the random number value of the UUID in step S7. The addition processing unit 71 to which the count value has been added advances the processing to step S8 and outputs the UUID to the data synthesis unit 47 as the instance UID.

  The addition processing unit 71 that has output the instance UID further proceeds to step S9, controls the counter 72 to count once, and increments the count value by +1. The addition processing unit 71 that increments the count value determines whether all UUIDs have been processed based on the count value, that is, for example, whether 26 instance UIDs have been generated. If it is determined that the UUID has not been processed (26 instance UIDs have not been generated), the process returns to step S6, and the subsequent processes are repeated. That is, the addition processing unit 71 accesses the UUID holding unit 64 again, acquires the UUID whose time information is incremented, and performs processing for changing the random value. At this time, since the count value changes every time by the process of step S9, the values of the 26 instance UIDs output from the addition processing unit 71 are all different values (26 types of values).

  As described above, the processing from step S6 to step S10 is repeated to output 26 instance UIDs. When it is determined in step S10 that all UUIDs have been processed, the addition processing unit 71 ends the instance UID generation processing. To do.

  Next, metadata file processing will be described with reference to the flowchart of FIG.

  The metadata file processing is started when, for example, a master file is read from the optical disc 17 by the disc drive unit 21 and stored in the buffer 41.

  That is, first, in step S21, the file acquisition unit 42 refers to the master file stored in the buffer 41, thereby recognizing the file names of the metadata files in file units and frame units. Further, in step S21, the file acquisition unit 42 acquires the metadata file for each file unit and each frame unit by causing the disk drive unit 21 to read from the optical disc 17 via the buffer 41 based on the file name. The metadata file processing unit 43 supplies the process to step S22. In step S22, the metadata file processing unit 43 extracts file unit metadata from the file unit metadata file supplied from the file acquisition unit 42, and frame unit metadata from the frame unit metadata file is extracted. The arranged system items are extracted and supplied to the data composition unit 47, and the metadata file processing is terminated.

  Next, the auxiliary file processing will be described with reference to the flowchart of FIG.

  The auxiliary file processing is started when, for example, a master file is read from the optical disc 17 by the disc drive unit 21 and stored in the buffer 41.

  That is, first, in step S41, the file acquisition unit 42 recognizes the file name of the auxiliary file by referring to the master file stored in the buffer 41. Further, in step S41, the file acquisition unit 42 acquires the auxiliary file based on the file name by causing the disk drive unit 21 to read from the optical disc 17 via the buffer 41, thereby performing the auxiliary file processing. Then, the process proceeds to step S42.

  In step S42, the auxiliary file processing unit 44 extracts (acquires) an auxiliary item from the auxiliary file by disassembling the auxiliary file supplied from the file acquisition unit 42 into auxiliary item units. To the data composition unit 47, and the auxiliary file processing is terminated.

  Next, video file processing will be described with reference to the flowchart of FIG.

  The video file processing is started when, for example, a master file is read from the optical disc 17 by the disc drive unit 21 and stored in the buffer 41.

  That is, first, in step S61, the file acquisition unit 42 recognizes the file name of the video file by referring to the master file stored in the buffer 41. Further, in step S 61, the file acquisition unit 42 acquires a video file based on the file name by causing the disk drive unit 21 to read from the optical disk 17 via the buffer 41 and supplies the video file to the video file processing unit 45. Then, the process proceeds to step S62.

  In step S62, the header / footer removal unit 81 of the video file processing unit 45 (FIG. 15) removes the header and footer from the video file supplied from the file acquisition unit 42, and the resulting body is converted into the decomposition unit 82. To proceed to step S63. In step S63, the decomposing unit 82 decomposes the sequence of picture items arranged in the body supplied from the header / footer removing unit 81 into individual picture items and supplies them to the data synthesizing unit 47 for video file processing. Exit.

  Next, audio file processing will be described with reference to the flowchart of FIG.

  The audio file processing is started when, for example, a master file is read from the optical disc 17 by the disc drive unit 21 and stored in the buffer 41.

  That is, first, in step S81, the file acquisition unit 42 refers to the master file stored in the buffer 41 to recognize the file names of the audio files of the eight channels. Further, in step S81, the file acquisition unit 42 acquires the audio files of the eight channels based on the file names by causing the disk drive unit 21 to read out from the optical disk 17 via the buffer 41, and perform audio file processing. The process proceeds to step S82.

  In step S82, the header / footer removing unit 91 of the audio file processing unit 46 (FIG. 16) removes the header and footer from each of the 8 channels of audio files supplied from the file acquisition unit 42, and as a result, the remaining channels. Are supplied to the KLV decoder 92, and the process proceeds to step S83. In step S83, the KLV decoder 92 disassembles the KLV structure of the body of each channel supplied from the header / footer removing unit 91 and supplies the WAVE audio data of each channel obtained thereby to the data converting unit 93. Then, the process proceeds to step S84.

  In step S84, the data conversion unit 93 converts the audio data of each channel in the WAVE format supplied from the KLV decoder 92 into the audio data of each channel in the AES3 format, and supplies the audio data to the channel multiplexing unit 94. Proceed to S85. In step S85, the channel multiplexer 94 multiplexes the audio data of each channel supplied from the data converter 93, supplies the multiplexed audio data obtained as a result to the KLV encoder 95, and proceeds to step S86. .

In step S86, the KLV encoder 95 divides the multiplexed audio data supplied from the channel multiplexing unit 94 into units corresponding to each frame of video data, and the multiplexed audio data corresponding to the frame is converted into a KLV structure. Code step S
Proceed to 7. Further, in step S87, the KLV encoder 95 adds a KLV structure of a necessary filler to the KLV structure of the multiplexed audio data corresponding to each frame, thereby configuring a sound item, and a data synthesis unit. 47 to finish the audio file processing.

  Next, the synthesis process will be described with reference to the flowchart of FIG.

  For example, for the data synthesis unit 47, the file unit metadata and system items from the metadata file processing unit 43, the auxiliary items from the auxiliary file processing unit 44, and the video file processing unit 45 are combined. To the picture item, the sound item from the audio file processing unit 46, and the instance UID from the instance UID generation unit 51, respectively.

  That is, first, in step S101, the header / footer generating unit 101 of the data synthesizing unit 47 (FIG. 17) generates a header and footer of a standard AV multiplex format file, and further, in the header metadata of the header, The metadata in units of files from the metadata file processing unit 43 is arranged. Further, in step S101, the header / footer generation unit 101 supplies the header and footer obtained as described above to the instance UID insertion unit 104, and the process proceeds to step S102.

  In step S102, the instance UID insertion unit 104 adds the 26 instance UIDs supplied from the instance UID generation unit 51 to the header metadata included in the header supplied from the header / footer generation unit 101 at predetermined positions. That is, it is inserted so as to have a configuration as shown in FIGS. Then, the instance UID insertion unit 104 supplies the header and footer into which the instance UID has been inserted to the header / footer adding unit 103, and the process proceeds to step S103.

  In step S103, the multiplexing unit 102 outputs a system item output from the metadata file processing unit 43, an auxiliary item output from the auxiliary file processing unit 44, a picture item output from the video file processing unit 45, and an audio file. The sound items output from the processing unit 46 are multiplexed, and the sequence of edit units obtained as a result of the multiplexing is supplied as a body to the header / footer adding unit 103, and the process proceeds to step S104.

  In step S104, the header / footer adding unit 103 adds the header and footer supplied from the instance UID inserting unit 104 to the body supplied from the multiplexing unit 102, thereby forming a file in the standard AV multiplex format. And output, and the synthesis process is terminated.

  As described above, when the material data is read from the optical disk 17 that is a recording medium, the format conversion unit 22 of the disk device 11 performs the format conversion process and is included in the header metadata of the video file recorded on the optical disk. The UUID stored in the header metadata in the standard AV multiplex format, which is the transmission format after format conversion, is generated using the UUID and the original file recorded on the optical disc 17 is extracted. And a file after reading have a certain relationship (relevance) to the UUID (instance UID), so the AV device 15 or 16 that uses the read file (or the editor who is the user) ) Is the relationship between the file after reading and the file before reading, for example, which Can be any data and over data to easily understand, such as whether it is the same content, it is possible to easily carry out the management of data in the editing work and the like.

  In addition, as described above, when files recorded on the optical disc 17 are repeatedly read, the header metadata included in the read files includes the same UUID (instance UID). ) Is inserted, the AV device 15 or 16 (or an editor who is the user) using the read file easily grasps that each file has the same content. Therefore, it is possible to easily manage data in editing work or the like.

  In other words, the disk device 11 can improve the convenience of data (material data) by performing the processing as described above.

  Note that, as described above, in FIG. 14, the addition processing unit 71 adds the count value of the counter 72 to the random number value 123 of the UUID so that the values are different from each other so as to be different from each other. An instance UID can be generated. As a result, the disk device 11 adds 26 types of UUIDs (instance UIDs) to the header metadata of the file (standard AV multiplex format file) read from the optical disk 17, as shown in FIGS. Can be inserted.

  As described above, in FIG. 14, the time information 63 increments the value of the UUID time snap 121 supplied from the UUID extraction unit 62 by a predetermined value (for example, +1). Insert a UUID (instance UID) with a value different from that of the original file (AV independent format file) of the optical disk 17 into the header metadata of the file read from the optical disk 17 (standard AV multiplex format file). Can do. This ensures that the UUID (instance UID) included in the read file is a globally unique ID (the global uniqueness of the UUID can be maintained). In other words, when it is sufficient that each data can be identified in this file (when it is not necessary to maintain global uniqueness), the time information changing unit 63 in FIG. 14 (or the processing in step S4 in FIG. 18) It can be omitted.

  In the above description, the number of instance UIDs generated by the instance UID generation unit 51 has been described as 26 (26 types of UUIDs are generated). However, the number of instance UIDs generated by the instance UID generation unit 51 is not limited to this. The number of can be any number. However, in the example described above, the value of the random number 123 of the UUID 120 is incremented so that the values are not the same among the instance UIDs in the file (uniqueness is maintained). Therefore, in this case, the maximum value of the number of UUIDs that can be generated by the instance UID generation unit 51 is determined by the number of digits of the random value 123. In the case of the example in FIG. 19, since the random number value is 6 bits, the instance UID generation unit 51 can generate 64 (64 types) instance UIDs.

  In the above, each UUID of the AV independent format file recorded on the optical disc 17 and each UUID of the standard AV multiplex format file read from the optical disc 17 are represented by the random value 123 in each file. The UUID of the AV independent format file that is mutually identified and recorded on the optical disc 17 and the UUID of the standard AV multiplex format file read from the optical disc 17 are determined by time information (when the time information is read when the file is read). It has been described that the values are distinguished from each other (by incrementing the value). However, as a method for identifying each UUID (a method for maintaining uniqueness), other than this, for example, each UUID of an AV independent format file recorded on the optical disc 17 and a standard read from the optical disc 17 are used. Each UUID of an AV multiplex format file is distinguished from each other by time information (time snap) in each file, and the UUID of the AV independent format file recorded on the optical disc 17 and the optical disc 17 The read UUID of the standard AV multiplex format file may be distinguished from each other by a random value (by incrementing the random value when reading the file).

  In this case, the time information changing unit 63 in FIG. 14 (or the process in step S4 in FIG. 18) can be omitted. Further, in this case, if a predetermined constant is added to the random number value in the instance UID generation process at the time of reading the file, the UUID of the AV independent format file recorded on the optical disc 17 and the optical disc 17 are read out. Thus, the counter 72 of FIG. 14 can be omitted. In that case, in step S7 in FIG. 18, the addition processing unit 71 adds a predetermined constant, not a count value, to the random value.

  In the following, each UUID of the AV independent format file recorded on the optical disc 17 and each UUID of the standard AV multiplex format file read from the optical disc 17 in each file will be described as follows. The UUID of the AV independent format file recorded on the optical disc 17 and the UUID of the standard AV multiplex format file read from the optical disc 17 are identified by a random number value so as to be distinguished from each other by information (time snap). A process related to recording of a file on the optical disc 17 by the disc device 11 in the case where the disc devices 11 are distinguished from each other (by incrementing a random value when reading the file) will be described.

  As described with reference to FIG. 12, the format conversion unit 22 of the disk device 11 converts the standard AV multiplex format file supplied from the communication I / F 23 into the AV independent format file by the standard / independent conversion unit 31. And supplied to the disk drive unit 21.

  FIG. 25 shows a configuration example of the standard / independent conversion unit 31 of FIG.

  The buffer 131 is supplied with a standard AV multiplex format file from the communication I / F 23. The buffer 131 temporarily stores a standard AV multiplex format file supplied thereto.

  When the standard AV multiplex format file is stored in the buffer 131, the master file generation unit 132 generates an AV independent format master file for the standard AV multiplex format file and supplies it to the buffer 144.

  The header acquisition unit 133 acquires the header by extracting the header from the standard AV multiplex format file stored in the buffer 131, and supplies the header to the header metadata extraction unit 135.

  The body obtaining unit 134 obtains the body by extracting the body from the standard AV multiplex format file stored in the buffer 131, and the body is extracted from the system item extracting unit 136, the auxiliary item extracting unit 138, and the picture item extracting unit. 140 and the sound item extraction unit 142.

  The header metadata extraction unit 135 extracts header metadata from the header supplied from the header acquisition unit 133, and supplies metadata in units of files arranged in the header metadata to the metadata file generation unit 137. . The system item extraction unit 136 extracts a system item in which metadata in units of frames is arranged from each body edit unit supplied from the body acquisition unit 134 and supplies the system item to the metadata file generation unit 137. The metadata file generation unit 137 generates a file unit metadata file in which the file unit metadata supplied from the header metadata extraction unit 135 is arranged, and each of the edit units supplied from the system item extraction unit 136. A frame-unit metadata file in which system items are arranged together (sequentially) is generated, and the file unit and frame-unit metadata file are supplied to the buffer 144.

  The auxiliary item extraction unit 138 extracts the auxiliary item in which the user data of the frame unit is arranged from each edit unit of the body supplied from the body acquisition unit 134, and supplies it to the auxiliary file generation unit 139. To do. The auxiliary file generation unit 139 generates an auxiliary file in which the auxiliary items of each edit unit supplied from the auxiliary item extraction unit 138 are arranged together, and supplies the auxiliary file to the buffer 144.

  The picture item extraction unit 140 extracts a picture item in which video data in units of frames is arranged from each body editing unit supplied from the body acquisition unit 134 and supplies the extracted picture item to the video file generation unit 141. The video file generation unit 141 collectively arranges the picture items of each edit unit supplied from the picture item extraction unit 140 in the body, and further, in the body, a header and a footer having the same format as the standard AV multiplex format file. Generate an attached video file. Further, the video file generation unit 141 stores the UUID (18 types of UUIDs) supplied from the UUID generation unit 151 in each part of the header metadata included in the header of the video file, and supplies the video file to the buffer 144. .

  The sound item extraction unit 142 extracts a sound item in which audio data in units of frames is arranged from each body edit unit supplied from the body acquisition unit 134 and supplies the sound item to the audio file generation unit 143. The audio file generation unit 143 arranges the audio data of each channel arranged in the sound item of each editing unit supplied from the sound item extraction unit 142 in the body for each channel, and further, in the body, An audio file for each channel to which a header and footer having the same format as the standard AV multiplex format file are added is generated and supplied to the buffer 144.

  As described above, the UUID generation unit 151 generates 18 types of UUIDs so that the time information is different from each other, and supplies them to the video file generation unit 141.

  The buffer 144 is a master file supplied from the master file generation unit 132, a metadata file for each file unit and frame unit supplied from the metadata file generation unit 137, and an auxiliary file supplied from the auxiliary file generation unit 139. Ali files, video files supplied from the video file generation unit 141, and audio files of each channel supplied from the audio file generation unit 143 are temporarily stored, and these files are converted into AV independent format files as a disk drive unit. 21.

  FIG. 26 is a block diagram illustrating a configuration example of the UUID generation unit 151 in FIG.

  26, the UUID generation unit 151 includes an IEEE 1394 node unique ID holding unit 161, a constant addition unit 162, a constant holding unit 163, a time information addition unit 164, a time information generation unit 165, and a UUID output control unit 166. .

  The IEEE 1394 node unique ID holding unit 161 holds an IEEE 1394 node unique ID that is an ID of the disk device 11 as an IEEE 1394 network node, and supplies it to the constant adding unit 162 based on a request from the constant adding unit 162. To do.

  The constant adding unit 162 obtains the IEEE 1394 node unique ID from the IEEE 1394 node unique ID holding unit 161, obtains a predetermined constant held by the constant holding unit 163, and transmits the information on the constant to the IEEE 1394 node unique ID. This is added (combined) to the upper bits of the ID and supplied to the time information adding unit 164.

  The time information adding unit 164 adds the count value acquired from the counter 172 of the time information generating unit 165 to the higher-order bits to the constant adding unit 162 added with (combined) the constant information to the IEEE 1394 node unique ID. (Combined) generates a UUID and supplies it to the UUID output control unit 166.

  The UUID output control unit 166 supplies the UUID supplied from the time information addition unit 164 to the video file generation unit 141 at a predetermined timing.

  The time information generation unit 165 includes a clock generation unit 171 that generates a clock having a predetermined frequency and a counter 72 that counts the number of clocks generated in the clock generation unit 171. The clock generation unit 171 includes, for example, a crystal resonator, a PLL (Phase Locked Loop) circuit, and the like, generates a clock having a predetermined frequency (for example, a frame frequency of image data), and outputs the clock to the counter 172. To supply. The counter 172 counts the number of clocks supplied from the clock generation unit 171 and supplies the count value based on a request from the time information addition unit 164.

  Next, FIG. 27 illustrates a configuration example of the video file generation unit 141 of FIG.

  The picture item of each edit unit supplied from the picture item extraction unit 140 is supplied to the combining unit 181. The combining unit 181 sequentially combines (concatenates) the picture items of the edit units supplied thereto and supplies them to the header / footer adding unit 182. The header / footer adding unit 182 adds the header and footer of the same format as the standard AV multiplex format file to the body, which is a combination of the picture items of the editing units supplied from the combining unit 181. To do. Further, the header / footer adding unit 182 stores the UUID supplied from the UUID generating unit 151 at a predetermined address of the header metadata included in the header, thereby forming and outputting a video file in an AV independent format. .

  Next, FIG. 28 shows a configuration example of the audio file generation unit 143 of FIG.

  The sound item of each edit unit supplied from the sound item extraction unit 142 is supplied to the KLV decoder 191. The KLV decoder 191 decomposes the KLV structure of the audio data arranged in the sound item of each edit unit, and obtains the audio data obtained by multiplexing the 8 channels (hereinafter referred to as multiplexed audio data as appropriate). To the channel separation unit 192.

  The channel separation unit 192 separates the audio data of each channel from the multiplexed audio data of each sound item supplied from the KLV decoder 191, collects the audio data of each channel for each channel, and converts the data into a data conversion unit 193.

  The data converter 193 converts the audio data encoding method of each channel supplied from the channel separator 192. That is, in the standard AV multiplex format, the audio data is encoded in the AES3 format, but in the AV independent format, the audio data is encoded in the WAVE system. Therefore, the data conversion unit 193 supplies the audio data (AES3 format audio data) encoded by the AES3 format supplied from the channel separation unit 62 to the audio data (WAVE format audio data) encoded by the WAVE format. Data).

  Here, the data converter 193 converts the AES3 audio data into WAVE audio data, but the data converter 63 converts the audio data into audio data other than the WAVE audio data. It is possible. That is, the conversion of the audio data in the data conversion unit 193 is performed for the purpose of suppressing the data amount of the audio data of the AES3 system, and if the encoding system can achieve the purpose, the data The conversion unit 193 may employ any encoding method.

  If the amount of audio data does not matter, the audio file generation unit 143 can be configured without the data conversion unit 193.

  The audio data for each WAVE channel obtained by the data converter 193 is supplied to the KLV encoder 194. The KLV encoder 194 performs KLV coding on the audio data gathered for each channel supplied from the data conversion unit 193 into the KLV structure, and further performs sector alignment on the audio data of each channel having the KLV structure. A necessary filler (FIG. 3) is added to the header / footer adding unit 195.

  The header / footer adding unit 195 uses the audio data of each channel supplied from the KLV encoder 194 as a body, and adds a header and footer of the same format as the standard AV multiplex format file to the body of each channel. Configure and output audio files for each channel in AV independent format.

  Next, the standard / independent conversion unit 31 in FIG. 25 performs UUID generation processing for generating a UUID, master file generation processing for generating a master file as an AV independent format file, and metadata files in units of files and frames. A metadata file generation process to be generated, an auxiliary file generation process to generate an auxiliary file, a video file generation process to generate a video file, and an audio file generation process to generate an audio file are performed.

  29 to 35, the UUID generation process, master file generation process, metadata file generation process, auxiliary file generation process, video file generation process performed by the standard / independent conversion unit 31, and The audio file generation process will be described.

  First, UUID generation processing will be described with reference to the flowchart of FIG.

  For example, when the UUID generation process is started by instructing the video file generation unit 141 or the like, the constant addition unit 162 of the UUID generation unit 151 accesses and holds the IEEE 1394 node unique ID holding unit 161 in step S121. Read (obtain) the IEEE 1394 node unique ID. Further, in step S122, the constant adding unit 162 accesses the constant holding unit 163 and reads (acquires) the held constant. The constant adding unit 162 that has read the IEEE 1394 node unique ID and constant proceeds to step S123, adds (combines) the constant to the IEEE 1394 node unique ID, and converts the bit string composed of the IEEE 1394 node unique ID and the constant into time information. The data is supplied to the adding unit 164, and the process proceeds to step S124.

  In step S124, the counter 172 of the time information generation unit 165 counts the clock supplied from the clock generation unit 171. In practice, the clock generator 171 always generates a clock and supplies it to the counter 172, and the counter 172 counts all the supplied clocks. That is, in step S124, the counter 172 supplies the count value to the time information adding unit 164, and the process proceeds to step S125.

  In step S125, the time information adding unit 164 acquires the count value supplied from the counter 172. In step S126, the time information adding unit 164 supplies the count value acquired from the counter 172 as time information (time snap) and is supplied from the constant adding unit 162. Is added to the bit string composed of the IEEE 1394 node unique ID and the constant, and the bit string composed of the IEEE 1394 node unique ID, constant, and time information (time snap) is supplied to the UUID output control unit 166.

  In step S127, the UUID output control unit 166 outputs a bit string composed of the IEEE 1394 node unique ID, constant, and time information (time snap) as a UUID to the video file generation unit 141 at a predetermined timing. Advances to step S128.

  In step S128, the time information adding unit 164 determines whether or not to end the UUID generation process. If it is determined not to end, the process returns to step S124, and the subsequent processes are repeated. For example, the time information adding unit 164 controls to repeat the processing from step S124 to step S128 until 18 UUIDs are generated.

  If it is determined in step S128 that, for example, 18 UUIDs need not be generated anymore and it is determined that the UUID generation process is to be terminated, the time information adding unit 164 terminates the UUID generation process. To do.

  Next, master file generation processing will be described with reference to the flowchart of FIG.

  For example, when a standard AV format file is supplied and stored in the buffer 131 (FIG. 25), a master file generation process is started. First, in step S141, the master file generation unit 132 (FIG. 25) File names of metadata files, auxiliary files, video files, and audio files of each channel are generated for each file and frame, and the process proceeds to step S142. In step S142, the master file generation unit 132 generates a master file described in XML with the link to the file having each file name generated in step S141, supplies the link to the buffer 144, stores the master file, and performs master file generation processing. finish.

  Next, a file unit metadata file generation process for generating a file unit metadata file will be described with reference to the flowchart of FIG.

  For example, when a standard AV format file is supplied to and stored in the buffer 131 (FIG. 25), a metadata file generation process in units of files is started. First, in step S161, the header acquisition unit 133 sets the buffer 131. The header is acquired from the file of the standard AV format stored in, and supplied to the header metadata extraction unit 135, and the process proceeds to step S162. In step S162, the header metadata extraction unit 135 extracts header metadata from the header supplied from the header acquisition unit 133, and converts the metadata in units of files arranged in the header metadata into a metadata file generation unit. 137 and proceeds to step S163. In step S163, the metadata file generation unit 137 generates a file unit metadata file in which the file unit metadata supplied from the header metadata extraction unit 135 is arranged, supplies the file to the buffer 144, stores the file, and stores the file. The unit metadata file generation process is terminated.

  Next, a frame unit metadata file generation process for generating a frame unit metadata file will be described with reference to the flowchart of FIG.

  For example, when a standard AV format file is supplied and stored in the buffer 131 (FIG. 25), a frame-based metadata file generation process starts. First, in step S181, the body acquisition unit 134 The body is acquired from the standard AV multiplex format file stored in 131, supplied to the system item extraction unit 136, and the process proceeds to step S182. In step S <b> 182, the system item extraction unit 136 extracts a system item in which metadata in units of frames is arranged from each body editing unit supplied from the body acquisition unit 134 and supplies the system item to the metadata file generation unit 137. Then, the process proceeds to step S183. In step S183, the metadata file generation unit 137 combines the system items of the respective edit units supplied from the system item extraction unit 136, so that the system unit metadata files arranged in units of the respective edit units are arranged together. Is supplied to and stored in the buffer 144, and the metadata file generation processing for each frame is completed.

  Next, an auxiliary file generation process for generating an auxiliary file will be described with reference to the flowchart of FIG.

  For example, when a standard AV format file is supplied and stored in the buffer 131 (FIG. 25), an auxiliary file generation process is started. First, in step S201, the body acquisition unit 134 stores the file in the buffer 131. The body is acquired from the stored standard AV multiplex format file, supplied to the auxiliary item extraction unit 138, and the process proceeds to step S202. In step S202, the auxiliary item extraction unit 138 extracts an auxiliary item from each edit unit of the body supplied from the body acquisition unit 134, supplies the extracted item to the auxiliary file generation unit 139, and the process proceeds to step S203. move on. In step S203, the auxiliary file generation unit 139 combines the auxiliary items of the edit units supplied from the auxiliary item extraction unit 138, thereby arranging the auxiliary items of the edit units together. The auxiliary file is generated, supplied to the buffer 144 and stored therein, and the auxiliary file generation process is terminated.

  Next, a video file generation process for generating a video file will be described with reference to the flowchart of FIG.

  For example, when a standard AV format file is supplied and stored in the buffer 131 (FIG. 25), a video file generation process is started. First, in step S221, the body acquisition unit 134 is stored in the buffer 131. The body is acquired from the standard AV multiplex format file, supplied to the picture item extraction unit 140, and the process proceeds to step S222. In step S222, the picture item extraction unit 140 extracts a picture item from each edit unit of the body supplied from the body acquisition unit 134, supplies it to the video file generation unit 141, and proceeds to step S223. In step S223, in the video file generating unit 141 (FIG. 27), the combining unit 181 combines the picture items of the respective edit units supplied from the picture item extracting unit 140 to collect the picture items of the respective edit units. The arranged body is generated and supplied to the header / footer adding unit 182, and the process proceeds to step S224.

  In step S224, the header / footer adding unit 182 adds a header and footer in the same format as the standard AV multiplex format file to the body supplied from the combining unit 181, thereby forming an AV independent format video file. Then, the data is supplied to and stored in the buffer 144, and the video file generation process is terminated.

  Next, an audio file generation process for generating an audio file will be described with reference to the flowchart of FIG.

  For example, when a standard AV format file is supplied and stored in the buffer 131 (FIG. 25), an audio file generation process is started. First, in step S241, the body acquisition unit 134 is stored in the buffer 131. The body is acquired from the standard AV multiplex format file, supplied to the sound item extraction unit 142, and the process proceeds to step S242. In step S242, the sound item extraction unit 142 extracts a sound item from each edit unit of the body supplied from the body acquisition unit 134, supplies the sound item to the audio file generation unit 143, and proceeds to step S243. In step S243, in the audio file generation unit 143 (FIG. 28), the KLV decoder 191 decomposes the KLV structure of the audio data arranged in the sound item of each edit unit, and 8 channels obtained as a result are multiplexed. The audio data (multiplexed audio data) is supplied to the channel separation unit 192, and the process proceeds to step S244.

  In step S244, the channel separation unit 192 separates the AES3 format audio data of each channel from the multiplexed audio data of each sound item supplied from the KLV decoder 191, and the AES3 format audio data of each channel is separated. These are arranged together for each channel and supplied to the data conversion unit 193.

  In step S245, the data conversion unit 193 converts the AES3-format audio data of each channel supplied from the channel separation unit 192 into WAVE audio data, and supplies the audio data to the KLV encoder 194, and then in step S246. Proceed to In step S246, the KLV encoder 194 performs KLV coding on the WAVE format audio data collected for each channel supplied from the data conversion unit 193 into the KLV structure, and further, the audio of each channel having the KLV structure. A filler (FIG. 3) necessary for sector alignment is added to the data. Accordingly, the KLV encoder 194 collectively arranges the WAVE format audio data of each channel, generates a body of each channel in which necessary fillers are arranged, and supplies the body to the header / footer adding unit 195, so that step S247 is performed. Proceed to

  In step S247, the header / footer adding unit 195 generates a header and footer having the same format as the standard AV multiplex format file, and further uses the UUID supplied from the UUID generating unit 151 (FIG. 27) as header header metadata. Is added to the body of each channel supplied from the KLV encoder 194, so that each channel of the AV independent format is inserted. Are supplied to and stored in the buffer 144, and the audio file generation process is terminated.

  As described above, the disk device 11 has the UUID of the AV independent format file recorded on the optical disc 17 and the UUID of the standard AV multiplex format file read from the optical disc 17, respectively. In each file, the UUID of the AV independent format file recorded on the optical disc 17 and the UUID of the standard AV multiplex format file read from the optical disc 17 are distinguished from each other by time information (time snap). Can be distinguished from each other by a random value (by incrementing the random value when reading the file). Thereby, the AV device 15 and the AV device 16 (or an editor who is a user thereof) using the file read from the optical disc 17 can identify each data and easily relate the relationship between the files. Since it can be grasped, the convenience of the file is improved, and for example, an editor can easily perform an editing operation or the like.

  Next, the series of processes described above can be performed by hardware or software. When a series of processing is performed by software, a program constituting the software is installed in a general-purpose computer or the like.

  Therefore, FIG. 36 illustrates a configuration example of an embodiment of a computer in which a program for executing the series of processes described above is installed.

  The program can be recorded in advance on a hard disk 215 or a ROM 213 as a recording medium built in the computer 200.

  Alternatively, the program is stored temporarily on a removable recording medium 221 such as a flexible disk, a CD-ROM (Compact Disc Read Only Memory), an MO (Magneto Optical) disk, a DVD (Digital Versatile Disc), a magnetic disk, or a semiconductor memory. It can be stored permanently (recorded). Such a removable recording medium 221 can be provided as so-called package software.

  The program is installed in the computer 200 from the removable recording medium 221 as described above, and is transferred from the download site to the computer 200 via a digital satellite broadcasting artificial satellite or by a LAN (Local Area Network). ), And transferred to the computer 200 via a network such as the Internet. The computer 200 can receive the program transferred in this way by the communication unit 218 and install it in the built-in hard disk 215.

  The computer 200 includes a CPU (Central Processing Unit) 202. An input / output interface 211 is connected to the CPU 212 via a bus 211, and the CPU 212 operates an input unit 217 including a keyboard, a mouse, a microphone, and the like by the user via the input / output interface 220. When a command is input by the equalization, a program stored in a ROM (Read Only Memory) 213 is executed accordingly. Alternatively, the CPU 212 may be a program stored in the hard disk 215, a program transferred from a satellite or a network, received by the communication unit 218 and installed in the hard disk 215, or a removable recording medium 221 attached to the drive 219. The program read and installed in the hard disk 215 is loaded into a RAM (Random Access Memory) 214 and executed. Thereby, the CPU 212 performs processing according to the flowchart described above or processing performed by the configuration of the block diagram described above. Then, the CPU 212 outputs the processing result from the output unit 216 configured with an LCD (Liquid Crystal Display), a speaker, or the like, for example, via the input / output interface 220, or from the communication unit 218 as necessary. Transmission and further recording on the hard disk 215 are performed.

  Here, in the present specification, the processing steps for describing a program for causing the computer to perform various processes do not necessarily have to be processed in time series in the order described in the flowcharts, but in parallel or individually. This includes processing to be executed (for example, parallel processing or processing by an object).

  Further, the program may be processed by one computer or may be distributedly processed by a plurality of computers. Furthermore, the program may be transferred to a remote computer and executed.

  In the present embodiment, the disk device 11 reads / writes an AV independent format file from / to the optical disc 17, but the AV independent format file is limited to a disc-shaped recording medium such as the optical disc 17. It is possible to read / write data from / to a tape-like recording medium such as a magnetic tape, a semiconductor memory, or the like.

  In the embodiment of FIG. 3, the disk drive unit 21, the format conversion unit 22, and the communication I / F 23 constitute the disk device 11 as one device. 22. The communication I / F 23 can be an independent device.

  Furthermore, in this embodiment, the file conforming to MXF is adopted as the standard AV multiplex format file, but as the standard AV multiplex format file, in addition to the MXF compliant file, a header, a body, It is possible to employ a file that is composed of a footer, includes a UUID in the header, and is arranged by multiplexing two arbitrary data (or more) in the body.

  In the present embodiment, the video data and audio data multiplexed are arranged in the body of the standard AV multiplex format file. For example, it is possible to arrange a multiplexed version of two or more video data (streams) or a multiplexed version of two or more audio data (streams).

  Furthermore, in the above description, the UUID arranged in the header metadata has been described. However, the UUID may be arranged in any position of various files. Of course, identification information other than the UUID may be used.

  In this specification, the system represents the entire apparatus constituted by a plurality of devices (apparatuses).

It is a figure explaining the example of the conventional method which reads a file from a disk. It is a figure explaining the other example of the conventional method which reads a file from a disk. It is a block diagram which shows the structural example of one Embodiment of the AV network system to which this invention is applied. It is a figure which shows a standard AV multiplex format. It is a figure which shows AV independent format. It is a figure which shows the example of the list of UUID arrange | positioned at the header metadata of the video file in AV independent format. FIG. 7 is a diagram subsequent to FIG. 6, illustrating an example of a list of UUIDs arranged in header metadata of a video file in an AV independent format. It is a figure which shows the example of the list of UUID arrange | positioned at the header metadata in a standard AV multiplex format. FIG. 9 is a diagram illustrating an example of a list of UUIDs arranged in header metadata in the standard AV multiplex format, following FIG. 8. FIG. 10 is a diagram subsequent to FIG. 9 showing an example of a list of UUIDs arranged in header metadata in the standard AV multiplex format. FIG. 11 is a diagram subsequent to FIG. 10 showing an example of a list of UUIDs arranged in header metadata in the standard AV multiplex format. It is a block diagram which shows the structural example of the format conversion part of FIG. It is a block diagram which shows the structural example of the independent / standard conversion part of FIG. It is a block diagram which shows the structural example of the instance UID production | generation part of FIG. It is a block diagram which shows the structural example of the video file process part of FIG. It is a block diagram which shows the structural example of the audio file processing part of FIG. It is a block diagram which shows the structural example of the data synthetic | combination part of FIG. It is a flowchart explaining the example of an instance UUID production | generation process. It is a figure which shows the structural example of UUID. It is a flowchart explaining a metadata file process. It is a flowchart explaining an auxiliary file process. It is a flowchart explaining a video file process. It is a flowchart explaining an audio file process. It is a flowchart explaining a synthetic | combination process. FIG. 5 is a block diagram illustrating a configuration example of a standard / independent conversion unit in FIG. 4. FIG. 26 is a block diagram illustrating a configuration example of a UUID generation unit in FIG. 25. FIG. 26 is a block diagram illustrating a configuration example of a video file generation unit in FIG. 25. FIG. 26 is a block diagram illustrating a configuration example of an audio file generation unit in FIG. 25. It is a flowchart explaining a UUID generation process. It is a flowchart explaining a master file generation process. It is a flowchart explaining the metadata file production | generation process of a file unit. It is a flowchart explaining the metadata file production | generation process of a frame unit. It is a flowchart explaining an auxiliary file production | generation process. It is a flowchart explaining a video file generation process. It is a flowchart explaining an audio file production | generation process. It is a block diagram which shows the structural example of one Embodiment of the computer to which this invention is applied.

Explanation of symbols

  11, 12 disk device, 13 editing device, 14 network, 15, 16 AV device, 17 optical disk, 21 disk drive unit, 22 format conversion unit, 23 communication I / F, 31 standard / independent conversion unit, 32 independent / standard conversion Unit, 41 buffer, 42 file acquisition unit, 43 metadata file processing unit, 44 auxiliary file processing unit, 45 video file processing unit, 46 audio file processing unit, 47 data synthesis unit, 48 buffer, 51 instance UID generation unit 61 header / footer extracting unit 61, 62 UUID extracting unit, 63 time information changing unit, 64 UUID holding unit, 65 random number changing unit, 71 addition processing unit, 72 counter, 81 header / footer removing unit, 82 decomposing unit, 91 Header / footer removal unit, 92 KLV decoder, 93 data conversion unit, 94 channel multiplexing unit, 95 KLV encoder, 101 header / footer generation unit, 102 multiplexing unit, 103 header / footer addition unit, 120 UUID, 121 time snap, 122 fixed value, 123 Random value, 124 IEEE 1394 node unique ID, 131 buffer, 132 master file generation unit, 133 header acquisition unit, 134 body acquisition unit, 135 header metadata extraction unit, 136 system item extraction unit, 137 metadata file generation unit, 138 o Auxiliary item extraction unit, 139 Auxiliary file generation unit, 140 Picture item extraction unit, 141 Video file generation unit, 142 Sound item extraction unit, 143 Audio file generation , 144 buffer, 151 UUID generation unit, 161 IEEE1394 node unique ID holding unit, 162 constant addition unit, 163 constant holding unit, 164 time information addition unit, 165 time information generation unit, 166 UUID output control unit, 171 clock generation unit, 172 counter, 181 coupling unit, 182 header / footer addition unit, 191 KLV decoder, 192 channel separation unit, 193 data conversion unit, 194 KLV encoder, 195 header / footer addition unit, 200 computer, 211 bus, 212 CPU, 213 ROM , 214 RAM, 215 hard disk, 216 output unit, 217 input unit, 218 communication unit, 219 drive, 220 input / output interface, 221 removable recording medium

Claims (5)

In the information processing apparatus for reading the data to which the recording data identification information for identifying the data recorded on the recording medium is added from the recording medium,
Reading means for reading the data from the recording medium together with the recording data identification information;
The data read from the recording medium by the reading means is changed by changing a part of the value of the recording data identification information added to the data read from the recording medium by the reading means. Output data identification information generating means for generating output data identification information for identification;
Output data identification information adding means for adding the output data identification information generated by the output data identification information generating means to the data read from the recording medium by the reading means;
The output data identification information generating means
One record data added to one predetermined internal data among the record data identification information added to each of a plurality of internal data included in one data recorded on the recording medium Extraction means for extracting identification information;
Duplication means for duplicating one of the recorded data identification information extracted by the extraction means;
Random number value changing means for generating a plurality of output data identification information by changing a random number value of a predetermined number of digits included in each of the plurality of recording data identification information duplicated by the duplication means. Information processing device. The output data identification information generating means further comprises a counting means for counting the number of output data identification information generated so far each time the output data identification information is generated,
The random number change means generates a plurality of the output data identification information having different random value values by adding the count value by the counting means to the random value included in the recording data identification information. The information processing apparatus according to claim 1. Format conversion means for converting the file format of the data read from the recording medium by the reading means;
The output data identification information generating means changes a part of the value of the recording data identification information added to the data before format conversion, and the required number of output data identification information in the data after format conversion. The information processing apparatus according to claim 1. An information processing method of an information processing apparatus for reading from the recording medium the data to which recording data identification information for identifying data recorded on the recording medium is added,
A read control step for controlling the data to be read from the recording medium together with the recording data identification information;
Controlled by the process of the read control step by changing a part of the value of the recording data identification information added to the data read from the recording medium under the control of the process of the read control step. Output data identification information generating step for generating output data identification information for identifying the data read from the recording medium;
An output data identification information addition step for adding the output data identification information generated by the processing of the output data identification information generation step to the data read from the recording medium controlled by the processing of the read control step; Including
The output data identification information generation step includes
One record data added to one predetermined internal data among the record data identification information added to each of a plurality of internal data included in one data recorded on the recording medium An extraction step for extracting identification information;
A duplication step of duplicating one of the recording data identification information extracted by the extraction step;
A random value changing step for generating a plurality of the output data identification information by changing a random number value of a predetermined number of digits included in each of the plurality of the recording data identification information duplicated by the process of the duplication step; An information processing method including: A computer for reading from the recording medium the data to which recording data identification information for identifying data recorded on the recording medium is added ;
Reading means for reading the data from the recording medium together with the recording data identification information;
One recording data identification information added to one predetermined internal data among the recording data identification information added to each of a plurality of internal data included in the data read by the reading means Extracting means for extracting
Duplication means for duplicating one of the recorded data identification information extracted by the extraction means;
Output data for identifying the data read by the reading unit by changing a random number value of a predetermined number of digits included in each of the plurality of recording data identification information copied by the copying unit Random number changing means for generating a plurality of identification information;
Output data identification information adding means for adding a plurality of the output data identification information generated by the random value changing means to the data read by the reading means
Program to function as .

Images