US20130129319A1 - Video data processing apparatus and file management method - Google Patents
Video data processing apparatus and file management method Download PDFInfo
- Publication number
- US20130129319A1 US20130129319A1 US13/741,264 US201313741264A US2013129319A1 US 20130129319 A1 US20130129319 A1 US 20130129319A1 US 201313741264 A US201313741264 A US 201313741264A US 2013129319 A1 US2013129319 A1 US 2013129319A1
- Authority
- US
- United States
- Prior art keywords
- header
- footer
- metadata information
- module
- data
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N9/00—Details of colour television systems
- H04N9/79—Processing of colour television signals in connection with recording
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L1/00—Arrangements for detecting or preventing errors in the information received
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
- H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
- H04N21/235—Processing of additional data, e.g. scrambling of additional data or processing content descriptors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/83—Generation or processing of protective or descriptive data associated with content; Content structuring
- H04N21/84—Generation or processing of descriptive data, e.g. content descriptors
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
- H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
- H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
- H04N21/85—Assembly of content; Generation of multimedia applications
- H04N21/854—Content authoring
- H04N21/85406—Content authoring involving a specific file format, e.g. MP4 format
Definitions
- Embodiments described herein relate generally to a video data processing apparatus and file management method.
- MXF Material exchange Format
- An MXF file is mainly formed by items such as a header, a body, and a footer.
- the item “Header” stores various metadata information items.
- the item “Body” stores frame data including video data and audio data.
- the metadata information includes information necessary for playing back video and audio stored in the item “Body”.
- the item “Header” is formed by repeated KLV structures, each of which is formed by the structure including a Key field, a Length field, and a Value field.
- the Key field indicates the data type of metadata information which is described as Value field.
- the Length field indicates the data length that the following Value field has.
- the Value field describes metadata information itself which is designated by the Key field.
- FIG. 1 is a block diagram of a functional structure of a video data processing apparatus according to a first embodiment.
- FIG. 2 is an example of a diagram illustrating a logical structure of an MXF file received by the video data processing apparatus shown in FIG. 1 .
- FIG. 3 is a diagram illustrating a structure of a Header of the MXF file illustrated in FIG. 2 .
- FIG. 4 is a diagram illustrating a specific example of a KLV structure of the Header illustrated in FIG. 3 .
- FIG. 5 is a flowchart illustrating processing of a control module shown in FIG. 1 , which is performed while recording metadata information and default data in a management module.
- FIG. 6 is a diagram illustrating processing performed when the data restoration module shown in FIG. 1 redetects “06h, 0Eh, 2Bh, 34h”.
- FIG. 7 is a block diagram illustrating a functional structure of a video data processing apparatus according to a second embodiment.
- FIG. 8 is a diagram illustrating structures of a Header and a Footer of an MXF file which is received by the video data processing apparatus shown in FIG. 7 .
- FIG. 9 is an example of a diagram illustrating a relation between header metadata information and footer metadata information in a comparison module shown in FIG. 7 .
- FIG. 10 is a flowchart illustrating processing of a control module shown in FIG. 7 , which is performed while outputting header metadata information and default data to the comparison module.
- FIG. 11 is a flowchart illustrating processing of the control module shown in FIG. 7 , which is performed while outputting footer metadata information and default data to the comparison module.
- FIG. 12 is a diagram illustrating a structure of the MXF file received by the video data processing apparatus shown in FIG. 7 .
- the data file includes a header, in which a header key field, a header length field, and a header value field are repeatedly arranged in this order.
- the header key field indicates a data type of header metadata information described in the following header value field.
- the header length field indicates a data length of the header value field.
- the header value field describes the header metadata information.
- the file receiving module connects to the network, and receives the data file through the network.
- the analyzer detects a character string which indicates a head of the header key field, thereby detects a header key field of the data file received by the file receiving module, and reads out header metadata information from a following header value field, based on a data type indicated by the header key field, and a data length indicated by the header length field following the header key field.
- the default data storage module stores in advance default data for a substitute header metadata information.
- the data restoration module discards header data from a position where the character string should be detected, when the character string is not detected at the position, and restores the default data from the default data storage module as header metadata information to be read out from the position to a next header key field.
- the management module stores the header metadata information read by the analyzer, and the default data restored by the data restoration module.
- FIG. 1 is a block diagram illustrating a functional structure of a video data processing apparatus 10 according to a first embodiment.
- the video data processing apparatus 10 illustrated in FIG. 1 is connected to a file server 20 , which stores program contents which are converted into MXF files, through an IP network such as Ethernet (Registered Trademark).
- the file server 20 transmits an MXF file to the video data processing apparatus 10 by, for example, File Transfer Protocol (FTP).
- FTP File Transfer Protocol
- FIG. 2 is an example of a schematic diagram illustrating a logical structure of an MXF file.
- the MXF file is mainly formed of a Header, a Body, and a Footer.
- the Body stores frame data which includes video data and audio data.
- the Body follows Header including metadata.
- the metadata includes metadata information which is necessary for playing back video and audio stored in the Body.
- the Footer follows the Body.
- FIG. 3 is a schematic diagram illustrating a structure of the Header.
- the Header adopts a KLV coding method which is formed by repeatedly disposing a Key field, a Length field, and a Value field.
- the Header is formed of a Header Partition Pack Key, Header Partition Pack Length, Header Partition Pack Value, Key field 1 , Length field 1 , Value field 1 , Key field 2 , Length field 2 , and Value field 2 . . . , in this order from the head.
- FIG. 4 is a diagram illustrating a specific example of the KLV structure in the Header.
- the total capacity of the Key field is determined as 16 bytes based on the SMPTE standard.
- the first 4 bytes of the Key field is defined as a character string “06h, 0Eh, 2Bh, 34h”.
- An identifying tag for identifying data is described in the Key field.
- the data length of the Length field is variable. Information relating to the data length of the following Value field is described in the Length field.
- Metadata information identified by the Key field is described in the Value field.
- the metadata information has a data length indicated by the Length field.
- the video processing apparatus 10 illustrated in FIG. 1 includes a file receiving module 11 , an analyzer 12 , a data restoration module 13 , a default data storage module 14 , a management module 15 , a storage module 16 , an external interface 17 , a control module 18 , and a playback module 19 .
- the control module 18 includes a Central Processing Unit (CPU) which is formed of a microprocessor or the like, and controls operations of the file receiving module 11 , the analyzer 12 , the data restoration module 13 , the management module 15 , the storage module 16 , and the playback module 19 .
- CPU Central Processing Unit
- the file receiving module 11 receives an MXF file transmitted from the file server 20 through an IP network.
- the analyzer 12 analyzes the MXF file from the file receiving module 11 . Specifically, the analyzer 12 reads out the Header Partition Pack Key, Header Partition Pack Length, and Header Partition Pack value, and then searches for “06h, 0Eh, 2Bh, 34h” which indicates the head of the Key field. When the analyzer 12 detects “06h, 0Eh, 2Bh, 34h”, the analyzer 12 reads 16 bytes of data, which is formed of the head part of 4 bytes and data of 12 bytes following the head part, as the Key field. After the Key field is read out, the analyzer 12 reads out the data length described in the Length field.
- the analyzer 12 reads out metadata information, which is identified by the Key field, has a data length designated by the Length field, and is described in the Value field, following the Length field. As described above, the analyzer 12 detects a KLV structure by detecting the Key field, and obtains metadata information included in each KLV structure. The analyzer 12 outputs the obtained metadata information to the management module 15 .
- the analyzer 12 When the analyzer 12 cannot detect “06h, 0Eh, 2Bh, 34h”, which indicates a position of the head of the next KLV structure, immediately following the Header Partition Pack Value field or immediately following another Value field, the analyzer 12 generates a redetection signal. The analyzer 12 outputs the redetection signal to the control module 18 . When the control module 18 receives the redetection signal, the control module 18 determines that a KLV structure is not detected, and the control module 18 outputs a first control signal to redetect “06h, 0Eh, 2Bh, 34h” to the data restoration module 13 .
- the control module 18 determines that the previous metadata information obtained is abnormal, and outputs an error signal indicating that the previous metadata information is abnormal to the data restoration module 13 . In receipt of the redetection signal, the control module 18 outputs a second control signal to discontinue analysis of the MXF file to the analyzer 12 . In receipt of the second control signal from the control module 18 , the analyzer 12 discontinues analysis of the MXF file.
- the analyzer 12 determines if a part including “06h, 0Eh, 2Bh, 34h” redetected by the data restoration module 13 and later fields of the MXF file have a KLV structure or not. When the part including “06h, 0Eh, 2Bh, 34h” and later fields have a KLV structure, the analyzer 12 restarts analysis of the MXF file.
- the default data storage module 14 stores in advance default data which is to be substituted for metadata information.
- the default data includes preset information relating to video resolution, video compression form, data size, and output form of audio data, and the like.
- the data restoration module 13 When the data restoration module 13 receives the first control signal from the control module 18 , the data restoration module 13 searches for “06h, 0Eh, 2Bh, 34h” by pattern matching, while shifting byte by byte from a position where “06h, 0Eh, 2Bh, 34h” was not detected. When the data restoration module 13 detects the next “06h, 0Eh, 2Bh, 34h”, the data restoration module 13 abandons data from the position where “06h, 0Eh, 2Bh, 34h” was not detected to a part before the next “06h, 0Eh, 2Bh, 34h”.
- the data restoration module 13 When the data restoration module detects “06h, 0Eh, 2Bh, 34h”, the data restoration module 13 outputs the detection and the detected position to the control module 18 .
- the control module 18 receives notification from the data restoration module 13 , the control module 18 outputs the third control signal to the analyzer 12 .
- the data restoration module 13 reads default data from the default data storage module 14 , and outputs the read default data to the management module 15 .
- the data restoration module 13 when the data restoration module 13 receives an error signal from the control module 18 , the data restoration module 13 reads default data for the detected previous metadata information from the default data storage module 14 , and outputs the read default data to the management module 15 .
- the management module 15 records normal metadata information output from the analyzer 12 , and the default data output from the data restoration module 13 .
- the storage module 16 records the MXF file which has been analyzed by the analyzer 12 .
- the external interface 17 connects to a user interface 30 , and receives user's instructions input from the user interface 30 .
- the user interface 30 is, for example, a mouse, a keyboard, and a display panel, through which user's instructions are input.
- the external interface 17 receives an instruction from the user interface 30
- the external interface 17 outputs the instruction to the control module 18 .
- the user interface 30 receives a playback instruction for playing back the designated MXF file from among MXF files recorded in the storage module 16 in the video data processing apparatus 10 .
- the control module 18 receives the playback instruction from the external interface 17
- the control module 18 reads out metadata information in the MXF file designated by the playback instruction from the management module 15 .
- the control module 18 generates a fourth control signal to read out the designated MXF file based on the read metadata information.
- control module 18 When default data for the designated MXF file is managed by the management module 15 , the control module 18 also reads out the default data from the management module 15 . The control module 18 generates a fourth control signal to read the designated MXF file based on the read metadata information and the default data. The control module 18 outputs the generated fourth control signal to the playback module 19 .
- the playback module 19 decodes the MXF file read from the storage module 16 , by using the metadata information and the default data, in accordance with the fourth control signal from the control module 18 .
- the playback module 19 outputs a video signal and an audio signal, which are generated by decoding, to the outside.
- FIG. 5 is a flowchart illustrating a processing of the control module 18 according to the first embodiment, which is performed when the analyzer 12 and the data restoration module 13 record metadata information and default data in the management module 15 .
- the control module 18 determines if a redetection signal is received from the analyzer 12 (Step S 51 ).
- the analyzer 12 cannot detect “06h, 0Eh, 2Bh, 34h” in position P 1 which is the head of the Key field as illustrated in FIG. 6
- the analyzer 12 outputs a redetection signal to the control module 18 .
- the control module 18 outputs a first control signal to redetect “06h, 0Eh, 2Bh, 34h” from the position P 1 to the data restoration module 13 , and outputs a second control signal to discontinue analysis of the MXF file to the analyzer 12 .
- control module 18 outputs an error signal indicating that the obtained previous metadata information is abnormal to the data restoration module 13 (Step S 52 ).
- the data restoration module 13 receives the error signal, the data restoration module 13 reads out default data for the previous metadata information from the default data storage module 14 , and outputs the read default data to the management module 15 .
- Step S 51 When no redetection data is received (No at Step S 51 ), the control module 18 repeats Step S 51 until a redetection signal is received. While Step S 51 is repeated, the analyzer 12 reads out metadata information from the MXF file based on the KLV structure, and outputs the read metadata information to the management module 15 .
- the control module 18 determines if notification is received from the data restoration module 13 that “06h, 0Eh, 2Bh, 34h” is received (Step S 53 ).
- the data restoration module 13 receives the first control signal from the control module 18
- the data restoration module 13 searches for “06h, 0Eh, 2Bh, 34h”, while shifting byte by byte from the position P 1 .
- the data restoration module 13 notifies the control module 18 that “06h, 0Eh, 2Bh, 34h” is detected at the position P 2 .
- the data restoration module 13 When the data restoration module 13 detects “06h, 0Eh, 2Bh, 34h”, the data restoration module 13 abandons data between the position P 1 and the position P 2 . Then, when analysis of metadata information in the Header is finished, the data restoration module 13 outputs the default data read from the default data storage module 14 to the management module 15 , instead of the abandoned metadata information.
- Step S 53 the control module 18 determines that notification is received from the data restoration module 13 (Yes at Step S 53 ).
- the control module 18 outputs a third control signal to restart analysis of the MXF file from the position P 2 to the analyzer 12 (Step S 54 ).
- Step S 54 the control module 18 determines that no notification is received from the data restoration module 13 (No at Step S 53 )
- the control module 18 repeats the processing of Step S 53 until notification is received from the data restoration module 13 .
- Step S 53 As described above, in the first embodiment, when no “06h, 0Eh, 2Bh, 34h” is detected in a head position of a Key field, “06h, 0Eh, 2Bh, 34h” is redetected from the head position.
- default data is obtained and recorded in the management module 15 , as metadata information which is located between the position where “06h, 0Eh, 2Bh, 34h” cannot be detected and “06h, 0Eh, 2Bh, 34h” which is detected by redetection.
- the video data processing apparatus 10 can obtain metadata information of and after the broken part, even when a Key field or a Length field in the Header is broken.
- the video data processing apparatus 10 can be realized by control using an all-purpose FTP protocol, it is unnecessary to design any special hardware as a file server. Specifically, it is possible to realize the video data processing apparatus and the file server at small cost.
- FIG. 7 is a block diagram illustrating a functional structure of a video data processing apparatus 40 according to a second embodiment.
- FIG. 8 is a schematic diagram illustrating a structure of a Header and a Footer of an MXF file used in the second embodiment.
- the KLV coding method is adopted for the MXF file illustrated in FIG. 8 , like the MXF file in the first embodiment.
- Metadata is registered in both the Header and the Footer.
- FIG. 8 among header metadata information described in a Header value field and footer metadata information described in a Footer value field, information items which have the same number are the same as a rule.
- the video recording time which is part of the Header metadata information, is not determined when preparation of the MXF file is started. Therefore, the Header metadata information is a provisional value, and the Footer metadata information is a fixed value.
- the video data processing apparatus 40 illustrated in FIG. 7 includes a file receiving module 11 , an analyzer 110 , a data restoration module 111 , a default data storage module 14 , a comparison module 112 , a management module 15 , a storage module 16 , an external interface 17 , a control module 18 , and a playback module 19 .
- the analyzer 110 analyzes a Header and a Footer in an MXF file from the file receiving module 11 . Specifically, the analyzer 110 reads out a Header Partition Pack Key, a Header Partition Pack Length, and a Header Partition Pack Value, and thereafter searches for “06h, 0Eh, 2Bh, 34h” which indicates the head of the Header Key Field. When “06h, 0Eh, 2Bh, 34h” is detected, the analyzer 110 reads out 16 bytes of data, which is formed of “06h, 0Eh, 2Bh, 34h” of 4 bytes and the following data of 12 bytes, as a Header Key Field.
- the analyzer 110 After the Header Key Field is read out, the analyzer 110 reads out a data length described in the Header Length field. Then, the analyzer 110 reads out header metadata information described in the Header Value field, which is identified by the Header Key field and has a data length designated by the Header Length field, following the Header Length field. As described above, the analyzer 110 detects a KLV structure by detecting a Header Key field, and obtains header metadata information included in each KLV structure. The analyzer 110 outputs the read header metadata information to the comparison module 112 .
- the analyzer 110 When “06h, 0Eh, 2Bh, 34h” which indicates a head position of the Header Key field cannot be detected immediately following the Header Partition Pack Value or immediately following another Header Value field by analyzing the Header, the analyzer 110 outputs a first redetection signal to the control module 18 .
- the control module 18 receives the first redetection signal, the control module 18 determines that a KLV structure cannot be detected, and outputs a first control signal to redetect “06h, 0Eh, 2Bh, 34h” to the data restoration module 111 .
- control module 18 determines that the previous header metadata information obtained is abnormal, and outputs a first error signal indicating that the previous header metadata information is abnormal to the data restoration module 111 . Further, when the control module 18 receives the first redetection signal, the control module 18 outputs a second control signal to discontinue analysis of the Header to the analyzer 110 . When the analyzer 110 receives the second control signal from the control module 18 , the analyzer 110 discontinues analysis of the Header.
- the analyzer 110 determines if the Header following “06h, 0Eh, 2Bh, 34h” redetected by the data restoration module 111 has a KLV structure. If the fields following “06h, 0Eh, 2Bh, 34h” have a KLV structure, the analyzer 110 restarts analysis of the Header.
- the analyzer 110 also performs the same analysis as the analysis of the Header, for the Footer, after analysis of the Header. Specifically, the analyzer 110 reads out a Footer Partition Pack Key, a Footer Partition Pack Length, and a Footer Partition Pack Value, and then searches for “06h, 0Eh, 2Bh, 34h” which indicates the head of the Footer Key field. When “06h, 0Eh, 2Bh, 34h” is detected, the analyzer 110 reads 16 bytes of data, which is formed of “06h, 0Eh, 2Bh, 34h” of 4 bytes and the following data of 12 bytes, as a Footer Key field.
- the analyzer 110 After the Footer Key field is read out, the analyzer 110 reads a data length described in a Footer Length field. Then, the analyzer 110 reads footer metadata information described in a Footer value field, which is identified by the Footer Key field and has a data length designated by the Footer Length field, following the Footer Length field. As described above, the analyzer 110 detects a KLV structure by detecting the Footer Key field, and obtains footer metadata information included in each KLV structure. The analyzer 110 outputs the read footer metadata information to the comparison module 112 .
- the analyzer 110 determines that a KLV structure cannot be detected, and outputs a second redetection signal to the control module 18 .
- the control module 18 receives the second redetection signal, the control module 18 outputs a fourth control signal to redetect “06h, 0Eh, 2Bh, 34h” to the data restoration module 111 .
- control module 18 determines that the previous footer metadata information obtained is abnormal, and outputs a second error signal indicating that the previous footer metadata information is abnormal to the data restoration module 111 . Further, when the control module 18 receives the second redetection signal, the control module 18 outputs a fifth control signal to discontinue analysis of the Footer to the analyzer 110 . When the analyzer 110 receives the fifth control signal from the control module 18 , the analyzer 110 discontinues analysis of the Footer.
- the analyzer 110 determines if the footer following “06h, 0Eh, 2Bh, 34h” redetected by the data restoration module 111 have a KLV structure. If the field following “06h, 0Eh, 2Bh, 34h” have a KLV structure, the analyzer 110 restarts analysis of the Footer.
- the data restoration module 111 includes a header obtaining module 1111 , and a footer obtaining module 1112 .
- the header obtaining module 1111 receives the first control signal from the control module 18 , the header obtaining module 1111 searches for “06h, 0Eh, 2Bh, 34h” by pattern matching, while shifting byte by byte from a position where “06h, 0Eh, 2Bh, 34h” cannot be detected.
- the header obtaining module 1111 abandons data from the position where “06h, 0Eh, 2Bh, 34h” cannot be detected to a part before the next “06h, 0Eh, 2Bh, 34h”.
- the header obtaining module 1111 When “06h, 0Eh, 2Bh, 34h” is detected, the header obtaining module 1111 outputs detection of “06h, 0Eh, 2Bh, 34h” and the detected position to the control module 18 .
- the control module 18 receives notification from the header obtaining module 1111 , the control module 18 outputs the third control signal to the analyzer 110 .
- the header obtaining module 1111 reads out default data for the header metadata information having an unfixed value from the default data storage module 14 , and outputs the read default data to the comparison module 112 .
- the header obtaining module 1111 when the header obtaining module 1111 receives the first error signal from the control module 18 , the header obtaining module 1111 reads out default data corresponding to the detected previous header metadata information from the default data storage module 14 , and outputs the read default data to the comparison module 112 .
- the footer obtaining module 1112 When the footer obtaining module 1112 receives the fourth control signal from the control module 18 , the footer obtaining module 1112 searches for “06h, 0Eh, 2Bh, 34h” by pattern matching, while shifting byte by byte from a position where “06h, 0Eh, 2Bh, 34h” cannot be detected. When the next “06h, 0Eh, 2Bh, 34h” is detected, the footer obtaining module 1112 abandons data from the position where “06h, 0Eh, 2Bh, 34h” cannot be detected to a part before the next “06h, 0Eh, 2Bh, 34h”.
- the footer obtaining module 1112 When “06h, 0Eh, 2Bh, 34h” is detected, the footer obtaining module 1112 outputs detection of “06h, 0Eh, 2Bh, 34h” and the detected position to the control module 18 .
- the control module 18 receives notification from the footer obtaining module 1112 , the control module 18 outputs the sixth control signal to the analyzer 110 .
- the footer obtaining module 1112 reads out default data for the footer metadata information having an unfixed value from the default data storage module 14 , and outputs the read default data to the comparison module 112 .
- the footer obtaining module 1112 when the footer obtaining module 1112 receives the second error signal from the control module 18 , the footer obtaining module 1112 reads out default data corresponding to the detected previous footer metadata information from the default data storage module 14 , and outputs the read default data to the comparison module 112 .
- the comparison module 112 receives the header metadata information and the footer metadata information from the analyzer 110 , and the default data from the header obtaining module 1111 and the footer obtaining module 1112 .
- the comparison module 112 compares the header metadata information with the footer metadata information, and outputs data with the relation illustrated in FIG. 9 , according to whether these information items are “normal”, “abnormal”, or “not described”.
- FIG. 9 gives footer metadata information priority over header metadata information, when normal footer metadata information is detected.
- the comparison module 112 compares header metadata information with corresponding footer metadata information, and outputs the footer metadata information to the management module 15 when both are normal.
- the comparison module 112 outputs the normal metadata information to the management module 15 .
- the comparison module 112 outputs the default data to the management module 15 .
- the management module 15 receives normal metadata information and default data from the comparison module 112 , and records them.
- control module 18 When the control module 18 receives a playback instruction from the external interface 17 , the control module 18 reads out metadata information of the MXF file designated by the playback instruction from the management module 15 . The control module 18 generates a seventh control signal to read out the designated MXF file based on the read metadata information.
- control module 18 When default data for the designated MXF file is managed in the management module 15 , the control module 18 also reads out the default data from the management module 15 . Then, the control module 18 generates a seventh control signal to read out the MXF file based on the read metadata information and the default data. The control module 18 outputs the generated seventh control signal to the playback module 19 .
- the playback module 19 decodes the MXF file read out from the storage module 16 by using the metadata information and the default data, in accordance with the seventh control signal from the control module 18 .
- the playback module 19 outputs a video signal and an audio signal prepared by decoding to the outside.
- FIG. 10 is a flowchart illustrating processing of the control module 18 , which is performed when the analyzer 110 and the header obtaining module 1111 according to the second embodiment output header metadata information and default data to the comparison module 112 .
- the control module 18 performs analysis of the Header.
- the control module 18 determines if a first redetection signal is received from the analyzer 110 (Step S 101 ).
- the control module 18 outputs a first control signal to redetect “06h, 0Eh, 2Bh, 34h” from the position P 1 of FIG. 6 to the header obtaining module 1111 , and outputs a second control signal to discontinue analysis of the Header to the analyzer 110 .
- the control module 18 outputs a first error signal indicating that the obtained previous header metadata information is abnormal to the header obtaining module 1111 (Step S 102 ).
- the header obtaining module 1111 receives the first error signal
- the header obtaining module 1111 reads out default data for the obtained previous header metadata information from the default data storage module 14 , and outputs the read default data to the comparison module 112 .
- Step S 101 When no first redetection signal is received (No at Step S 101 ), the control module 18 repeats Step S 101 until the control module 18 receives the first redetection signal. While Step S 101 is repeated, the analyzer 110 reads out metadata information from the Header based on the KLV structure, and outputs the read metadata information to the comparison module 112 .
- the control module 18 determines if notification is received from the header obtaining module 1111 that “06h, 0Eh, 2Bh, 34h” is received (Step S 103 ).
- the header obtaining module 1111 receives the first control signal from the control module 18
- the header obtaining module 1111 searches for “06h, 0Eh, 2Bh, 34h”, while shifting byte by byte from the position P 1 .
- the header obtaining module 1111 notifies the control module 18 that “06h, 0Eh, 2Bh, 34h” is detected at the position P 2 .
- the header obtaining module 1111 When the header obtaining module 1111 detects “06h, 0Eh, 2Bh, 34h”, the header obtaining module 1111 abandons data between the position P 1 and the position P 2 . Then, when analysis of header metadata information in the Header is finished, the header obtaining module 1111 outputs the default data read from the default data storage module 14 to the comparison module 112 , instead of the abandoned header metadata information.
- Step S 104 When notification is received from the header obtaining module 1111 (Yes at Step S 103 ), the control module 18 outputs a third control signal to restart analysis of the Header from the position P 2 to the analyzer 110 (Step S 104 ). When no notification is received from the header obtaining module 1111 (No at Step S 103 ), the control module 18 repeats the processing of Step S 103 until notification is received from the header obtaining module 1111 .
- FIG. 11 is a flowchart illustrating processing of the control module 18 , which is performed when the analyzer 110 and the footer obtaining module 1112 according to the second embodiment output footer metadata information and default data to the comparison module 112 .
- the control module 18 performs analysis of the Footer.
- the control module 18 determines if a second redetection signal is received from the analyzer 110 (Step S 111 ).
- the control module 18 outputs a fourth control signal to redetect “06h, 0Eh, 2Bh, 34h” from the position P 1 of FIG. 6 to the footer obtaining module 1112 , and outputs a fifth control signal to discontinue analysis of the Footer to the analyzer 110 .
- the control module 18 outputs a second error signal indicating that the obtained previous footer metadata information is abnormal to the footer obtaining module 1112 (Step S 112 ).
- the footer obtaining module 1112 receives the second error signal
- the footer obtaining module 1112 reads out default data for the obtained previous footer metadata information from the default data storage module 14 , and outputs the read default data to the comparison module 112 .
- Step S 111 When no second redetection signal is received (No at Step S 111 ), the control module 18 repeats Step S 111 until the control module 18 receives the second redetection signal. While Step S 111 is repeated, the analyzer 110 reads out metadata information from the Footer based on the KLV structure, and outputs the read footer metadata information to the comparison module 112 .
- the control module 18 determines if notification is received from the footer obtaining module 1112 that “06h, 0Eh, 2Bh, 34h” is received (Step S 113 ).
- the footer obtaining module 1112 receives the fourth control signal from the control module 18
- the footer obtaining module 1112 searches for “06h, 0Eh, 2Bh, 34h”, while shifting byte by byte from the position P 1 .
- the footer obtaining module 1112 notifies the control module 18 that “06h, 0Eh, 2Bh, 34h” is detected at the position P 2 .
- the footer obtaining module 1112 When the footer obtaining module 1112 detects “06h, 0Eh, 2Bh, 34h”, the footer obtaining module 1112 abandons data between the position P 1 and the position P 2 . Then, when analysis of footer metadata information in the Footer is finished, the footer obtaining module 1112 outputs the default data read from the default data storage module 14 to the comparison module 112 , instead of the abandoned footer metadata information.
- Step S 113 When the control module 18 determines that notification is received from the footer obtaining module 1112 (Yes at Step S 113 ), the control module 18 outputs a sixth control signal to restart analysis of the Footer from the position P 2 to the analyzer 110 (Step S 114 ). When the control module 18 determines that no notification is received from the footer obtaining module 1112 (No at Step S 113 ), the control module 18 repeats the processing of Step S 113 until notification is received from the footer obtaining module 1112 .
- header metadata information is written in the Header
- footer metadata information is written in the Footer.
- the analyzer 110 reads out header metadata information from the Header, and reads out footer metadata information from the Footer. Then, when both the header metadata information and the footer metadata information are normal, the comparison module 112 selects the footer metadata information, and records the footer metadata information in the management module 15 . Thereby, it is possible to record footer metadata information, which is a value more accurate than the header metadata information, in the management module 15 .
- the comparison module 112 selects metadata information which is normally obtained, and records the selected metadata information in the management module 15 . Thereby, even when the KLV structure of one of the Header and the Footer is not detected, it is possible to obtain normal metadata information.
- the second embodiment shows an example in which the Header and the Footer are successively analyzed from the head of the MXF file
- the second embodiment is not limited to this structure.
- the following is an explanation of operation performed by the video data processing apparatus 40 according to the second embodiment when metadata information is obtained from the MXF file by using the Random Index Pack Value.
- information which is called “Partition Pack” is inserted to the head part of the Header, the head and the middle parts of the Body, and the head part of the Footer.
- the Partition Pack includes a Partition Pack Key, a Partition Pack Length, and a Partition Pack Value.
- the Random Index Pack Value stores offset values from the head of the MXF file to the respective head positions of the Partition Pack Keys.
- the control module 18 controls the file receiving module 11 to obtain the Random Index Pack Value of the MXF file recorded in the file server 20 .
- the file receiving module 11 outputs an output request based on a FTP protocol or the like to output the Random Index Pack Value of the MXF file to the file server 20 .
- the file server 20 outputs the Random Index Pack Value of the MXF file to the file receiving module 11 .
- the file receiving module 11 receives the Random Index Pack Value from the file server 20 , and notifies the control module 18 of the received Random Index Pack Value.
- the control module 18 identifies the position of the Footer Partition Pack Key based on the Random Index Pack Value, and controls the file receiving module 11 to obtain the Footer of the MXF file recorded in the file server 20 .
- the file receiving module 11 outputs an output request to output the Footer of the MXF file to the file server 20 .
- the file server 20 outputs the Footer of the MXF file to the file receiving module 11 .
- the file receiving module 11 receives the Footer from the file server 20 , and outputs the received Footer to the analyzer 110 .
- the analyzer 110 analyzes the Footer, and obtains footer metadata information by using the KLV structure.
- the analyzer 110 outputs the obtained footer metadata information to the comparison module 112 .
- the footer obtaining module 1112 redetects “06h, 0Eh, 2Bh, 34h”, detects the next Footer Key field, and obtains default data.
- the control module 18 controls the file receiving module 11 to obtain the whole MXF file recorded in the file server 20 .
- the file receiving module 11 outputs an output request to output the whole MXF file to the file server 20 .
- the file server 20 outputs the MXF file to the file receiving module 11 .
- the file receiving module 11 receives the MXF file from the file server 20 , and outputs the received MXF file to the analyzer 110 .
- the analyzer 110 analyzes the MXF file from the head, and obtains header metadata information by using the KLV structure.
- the analyzer 110 outputs the obtained header metadata information to the comparison module 112 .
- the header obtaining module 1111 redetects “06h, 0Eh, 2Bh, 34h”, detects the next Header Key field, and obtains default data.
- the video data processing apparatus 40 may analyze the Footer of the MXF file before analyzing the Header, by using the Random Index Pack Value.
- the Footer is received after the Body of the MXF file is received. Therefore, it is required to wait until the transmission time of the Body is passed to start analysis of the Footer.
- analysis of the Footer is started first by using the Random Index Pack Value, and thereby it is possible to start playback processing of video and audio immediately following reception of the whole MXF file is started.
Abstract
According to one embodiment, a video data processing apparatus which receives a data file includes a file receiving module, an analyzer, a default data storage module, a data restoration module, and a management module. The data file includes a header, in which a header key field, a header length field, and a header value field are arranged. The analyzer detects a character string, thereby detects a header key field of the data file received by the file receiving module, and reads out header metadata information from a following header value field. The data restoration module discards header data from a first position, in absence of the character string at the first position, and restores default data in the default data storage module instead of the discarded header data. The management module stores the header metadata information and the default data.
Description
- This application is a divisional of U.S. patent application Ser. No. 13/192,308 filed on Jul. 27, 2011, which is based upon and claims the benefit of priority from Japanese Patent Application No. 2010-207631, filed Sep. 16, 2010, the entire contents of both of which are incorporated herein by reference.
- Embodiments described herein relate generally to a video data processing apparatus and file management method.
- In recent years, the Material exchange Format (MXF) has been used as a data exchange format for exchanging material data between servers. An MXF file is mainly formed by items such as a header, a body, and a footer. The item “Header” stores various metadata information items. The item “Body” stores frame data including video data and audio data. The metadata information includes information necessary for playing back video and audio stored in the item “Body”.
- The item “Header” is formed by repeated KLV structures, each of which is formed by the structure including a Key field, a Length field, and a Value field. The Key field indicates the data type of metadata information which is described as Value field. The Length field indicates the data length that the following Value field has. The Value field describes metadata information itself which is designated by the Key field.
- When the Key field in the Header is broken, no KLV structure is detected, and thus metadata information might not be read out. In addition, when the Key field is broken, metadata information corresponding to the broken key field might be read as metadata information which corresponds to another key field.
- Further, when the Length field in the Header is broken, metadata information which corresponds to a value field followed by the broken length field might not be accurately read out because the length of the Value field cannot be accurately known. In addition, when the Length field is broken, the KLV structure might not be detected because the head position of the next Key field is not detected.
- As described above, when a Key field or a Length field is broken, metadata information following the broken part might not be accurately obtained.
-
FIG. 1 is a block diagram of a functional structure of a video data processing apparatus according to a first embodiment. -
FIG. 2 is an example of a diagram illustrating a logical structure of an MXF file received by the video data processing apparatus shown inFIG. 1 . -
FIG. 3 is a diagram illustrating a structure of a Header of the MXF file illustrated inFIG. 2 . -
FIG. 4 is a diagram illustrating a specific example of a KLV structure of the Header illustrated inFIG. 3 . -
FIG. 5 is a flowchart illustrating processing of a control module shown inFIG. 1 , which is performed while recording metadata information and default data in a management module. -
FIG. 6 is a diagram illustrating processing performed when the data restoration module shown inFIG. 1 redetects “06h, 0Eh, 2Bh, 34h”. -
FIG. 7 is a block diagram illustrating a functional structure of a video data processing apparatus according to a second embodiment. -
FIG. 8 is a diagram illustrating structures of a Header and a Footer of an MXF file which is received by the video data processing apparatus shown inFIG. 7 . -
FIG. 9 is an example of a diagram illustrating a relation between header metadata information and footer metadata information in a comparison module shown inFIG. 7 . -
FIG. 10 is a flowchart illustrating processing of a control module shown inFIG. 7 , which is performed while outputting header metadata information and default data to the comparison module. -
FIG. 11 is a flowchart illustrating processing of the control module shown inFIG. 7 , which is performed while outputting footer metadata information and default data to the comparison module. -
FIG. 12 is a diagram illustrating a structure of the MXF file received by the video data processing apparatus shown inFIG. 7 . - In general, according to one embodiment, a video data processing apparatus which receives a data file through a network includes a file receiving module, an analyzer, a default data storage module, a data restoration module, and a management module. The data file includes a header, in which a header key field, a header length field, and a header value field are repeatedly arranged in this order. The header key field indicates a data type of header metadata information described in the following header value field. The header length field indicates a data length of the header value field. The header value field describes the header metadata information. The file receiving module connects to the network, and receives the data file through the network. The analyzer detects a character string which indicates a head of the header key field, thereby detects a header key field of the data file received by the file receiving module, and reads out header metadata information from a following header value field, based on a data type indicated by the header key field, and a data length indicated by the header length field following the header key field. The default data storage module stores in advance default data for a substitute header metadata information. The data restoration module discards header data from a position where the character string should be detected, when the character string is not detected at the position, and restores the default data from the default data storage module as header metadata information to be read out from the position to a next header key field. The management module stores the header metadata information read by the analyzer, and the default data restored by the data restoration module.
- An embodiment will be described below with reference to the drawings.
-
FIG. 1 is a block diagram illustrating a functional structure of a videodata processing apparatus 10 according to a first embodiment. The videodata processing apparatus 10 illustrated inFIG. 1 is connected to afile server 20, which stores program contents which are converted into MXF files, through an IP network such as Ethernet (Registered Trademark). Thefile server 20 transmits an MXF file to the videodata processing apparatus 10 by, for example, File Transfer Protocol (FTP). -
FIG. 2 is an example of a schematic diagram illustrating a logical structure of an MXF file. As illustrated inFIG. 2 , the MXF file is mainly formed of a Header, a Body, and a Footer. The Body stores frame data which includes video data and audio data. The Body follows Header including metadata. The metadata includes metadata information which is necessary for playing back video and audio stored in the Body. The Footer follows the Body. -
FIG. 3 is a schematic diagram illustrating a structure of the Header. The Header adopts a KLV coding method which is formed by repeatedly disposing a Key field, a Length field, and a Value field. According toFIG. 3 , the Header is formed of a Header Partition Pack Key, Header Partition Pack Length, Header Partition Pack Value,Key field 1,Length field 1,Value field 1,Key field 2,Length field 2, andValue field 2 . . . , in this order from the head. -
FIG. 4 is a diagram illustrating a specific example of the KLV structure in the Header. The total capacity of the Key field is determined as 16 bytes based on the SMPTE standard. The first 4 bytes of the Key field is defined as a character string “06h, 0Eh, 2Bh, 34h”. An identifying tag for identifying data is described in the Key field. - The data length of the Length field is variable. Information relating to the data length of the following Value field is described in the Length field.
- Metadata information identified by the Key field is described in the Value field. The metadata information has a data length indicated by the Length field.
- The
video processing apparatus 10 illustrated inFIG. 1 includes afile receiving module 11, ananalyzer 12, adata restoration module 13, a defaultdata storage module 14, amanagement module 15, astorage module 16, anexternal interface 17, acontrol module 18, and aplayback module 19. - The
control module 18 includes a Central Processing Unit (CPU) which is formed of a microprocessor or the like, and controls operations of thefile receiving module 11, theanalyzer 12, thedata restoration module 13, themanagement module 15, thestorage module 16, and theplayback module 19. - The
file receiving module 11 receives an MXF file transmitted from thefile server 20 through an IP network. - The
analyzer 12 analyzes the MXF file from thefile receiving module 11. Specifically, theanalyzer 12 reads out the Header Partition Pack Key, Header Partition Pack Length, and Header Partition Pack value, and then searches for “06h, 0Eh, 2Bh, 34h” which indicates the head of the Key field. When theanalyzer 12 detects “06h, 0Eh, 2Bh, 34h”, theanalyzer 12 reads 16 bytes of data, which is formed of the head part of 4 bytes and data of 12 bytes following the head part, as the Key field. After the Key field is read out, theanalyzer 12 reads out the data length described in the Length field. Then, theanalyzer 12 reads out metadata information, which is identified by the Key field, has a data length designated by the Length field, and is described in the Value field, following the Length field. As described above, theanalyzer 12 detects a KLV structure by detecting the Key field, and obtains metadata information included in each KLV structure. Theanalyzer 12 outputs the obtained metadata information to themanagement module 15. - When the
analyzer 12 cannot detect “06h, 0Eh, 2Bh, 34h”, which indicates a position of the head of the next KLV structure, immediately following the Header Partition Pack Value field or immediately following another Value field, theanalyzer 12 generates a redetection signal. Theanalyzer 12 outputs the redetection signal to thecontrol module 18. When thecontrol module 18 receives the redetection signal, thecontrol module 18 determines that a KLV structure is not detected, and thecontrol module 18 outputs a first control signal to redetect “06h, 0Eh, 2Bh, 34h” to thedata restoration module 13. In addition, in receipt of the redetection signal, thecontrol module 18 determines that the previous metadata information obtained is abnormal, and outputs an error signal indicating that the previous metadata information is abnormal to thedata restoration module 13. In receipt of the redetection signal, thecontrol module 18 outputs a second control signal to discontinue analysis of the MXF file to theanalyzer 12. In receipt of the second control signal from thecontrol module 18, theanalyzer 12 discontinues analysis of the MXF file. - When the
analyzer 12 receives a third control signal to restart analysis of the MXK file from thecontrol module 18, theanalyzer 12 determines if a part including “06h, 0Eh, 2Bh, 34h” redetected by thedata restoration module 13 and later fields of the MXF file have a KLV structure or not. When the part including “06h, 0Eh, 2Bh, 34h” and later fields have a KLV structure, theanalyzer 12 restarts analysis of the MXF file. - The default
data storage module 14 stores in advance default data which is to be substituted for metadata information. The default data includes preset information relating to video resolution, video compression form, data size, and output form of audio data, and the like. - When the
data restoration module 13 receives the first control signal from thecontrol module 18, thedata restoration module 13 searches for “06h, 0Eh, 2Bh, 34h” by pattern matching, while shifting byte by byte from a position where “06h, 0Eh, 2Bh, 34h” was not detected. When thedata restoration module 13 detects the next “06h, 0Eh, 2Bh, 34h”, thedata restoration module 13 abandons data from the position where “06h, 0Eh, 2Bh, 34h” was not detected to a part before the next “06h, 0Eh, 2Bh, 34h”. When the data restoration module detects “06h, 0Eh, 2Bh, 34h”, thedata restoration module 13 outputs the detection and the detected position to thecontrol module 18. When thecontrol module 18 receives notification from thedata restoration module 13, thecontrol module 18 outputs the third control signal to theanalyzer 12. - When a value of any metadata information is not determined when analysis of metadata information included in the header is finished, the
data restoration module 13 reads default data from the defaultdata storage module 14, and outputs the read default data to themanagement module 15. - In addition, when the
data restoration module 13 receives an error signal from thecontrol module 18, thedata restoration module 13 reads default data for the detected previous metadata information from the defaultdata storage module 14, and outputs the read default data to themanagement module 15. - The
management module 15 records normal metadata information output from theanalyzer 12, and the default data output from thedata restoration module 13. - The
storage module 16 records the MXF file which has been analyzed by theanalyzer 12. - The
external interface 17 connects to auser interface 30, and receives user's instructions input from theuser interface 30. Theuser interface 30 is, for example, a mouse, a keyboard, and a display panel, through which user's instructions are input. When theexternal interface 17 receives an instruction from theuser interface 30, theexternal interface 17 outputs the instruction to thecontrol module 18. - For example, the
user interface 30 receives a playback instruction for playing back the designated MXF file from among MXF files recorded in thestorage module 16 in the videodata processing apparatus 10. When thecontrol module 18 receives the playback instruction from theexternal interface 17, thecontrol module 18 reads out metadata information in the MXF file designated by the playback instruction from themanagement module 15. Thecontrol module 18 generates a fourth control signal to read out the designated MXF file based on the read metadata information. - When default data for the designated MXF file is managed by the
management module 15, thecontrol module 18 also reads out the default data from themanagement module 15. Thecontrol module 18 generates a fourth control signal to read the designated MXF file based on the read metadata information and the default data. Thecontrol module 18 outputs the generated fourth control signal to theplayback module 19. - The
playback module 19 decodes the MXF file read from thestorage module 16, by using the metadata information and the default data, in accordance with the fourth control signal from thecontrol module 18. Theplayback module 19 outputs a video signal and an audio signal, which are generated by decoding, to the outside. - The following is an explanation of the operation performed when the video
data processing apparatus 10 having the above structure obtains metadata information and default data, with reference to an operation process of thecontrol module 18. -
FIG. 5 is a flowchart illustrating a processing of thecontrol module 18 according to the first embodiment, which is performed when theanalyzer 12 and thedata restoration module 13 record metadata information and default data in themanagement module 15. - First, the
control module 18 determines if a redetection signal is received from the analyzer 12 (Step S51). When theanalyzer 12 cannot detect “06h, 0Eh, 2Bh, 34h” in position P1 which is the head of the Key field as illustrated inFIG. 6 , theanalyzer 12 outputs a redetection signal to thecontrol module 18. When a redetection signal is received (Yes at Step S51), thecontrol module 18 outputs a first control signal to redetect “06h, 0Eh, 2Bh, 34h” from the position P1 to thedata restoration module 13, and outputs a second control signal to discontinue analysis of the MXF file to theanalyzer 12. In addition, thecontrol module 18 outputs an error signal indicating that the obtained previous metadata information is abnormal to the data restoration module 13 (Step S52). When thedata restoration module 13 receives the error signal, thedata restoration module 13 reads out default data for the previous metadata information from the defaultdata storage module 14, and outputs the read default data to themanagement module 15. - When no redetection data is received (No at Step S51), the
control module 18 repeats Step S51 until a redetection signal is received. While Step S51 is repeated, theanalyzer 12 reads out metadata information from the MXF file based on the KLV structure, and outputs the read metadata information to themanagement module 15. - Then, the
control module 18 determines if notification is received from thedata restoration module 13 that “06h, 0Eh, 2Bh, 34h” is received (Step S53). When thedata restoration module 13 receives the first control signal from thecontrol module 18, thedata restoration module 13 searches for “06h, 0Eh, 2Bh, 34h”, while shifting byte by byte from the position P1. Then, when “06h, 0Eh, 2Bh, 34h” is detected at position P2 as shown inFIG. 6 , thedata restoration module 13 notifies thecontrol module 18 that “06h, 0Eh, 2Bh, 34h” is detected at the position P2. When thedata restoration module 13 detects “06h, 0Eh, 2Bh, 34h”, thedata restoration module 13 abandons data between the position P1 and the position P2. Then, when analysis of metadata information in the Header is finished, thedata restoration module 13 outputs the default data read from the defaultdata storage module 14 to themanagement module 15, instead of the abandoned metadata information. - When the
control module 18 determines that notification is received from the data restoration module 13 (Yes at Step S53), thecontrol module 18 outputs a third control signal to restart analysis of the MXF file from the position P2 to the analyzer 12 (Step S54). When thecontrol module 18 determines that no notification is received from the data restoration module 13 (No at Step S53), thecontrol module 18 repeats the processing of Step S53 until notification is received from thedata restoration module 13. As described above, in the first embodiment, when no “06h, 0Eh, 2Bh, 34h” is detected in a head position of a Key field, “06h, 0Eh, 2Bh, 34h” is redetected from the head position. Thereby, even when an error occurs in a Key field, it is possible to accurately detect the next Key field of the Key field. In addition, even when an error occurs in a Length field and the length of the Value field cannot be accurately known, it is possible to accurately detect the next Key field. Specifically, even when a Key field or a Length field is broken, a KLV structure following the broken part can be accurately detected. - In addition, in the above first embodiment, default data is obtained and recorded in the
management module 15, as metadata information which is located between the position where “06h, 0Eh, 2Bh, 34h” cannot be detected and “06h, 0Eh, 2Bh, 34h” which is detected by redetection. Thereby, even if it is an MXF file including the part where no KLV structure is detected, it is possible to obtain metadata information of the part. - Therefore, the video
data processing apparatus 10 according to the first embodiment can obtain metadata information of and after the broken part, even when a Key field or a Length field in the Header is broken. - In addition, in the first embodiment, when a playback instruction is input by the user, video data and audio data written in the MXF file are played back with reference to metadata information and default data. Thereby, even if it is an MXF file including the part where a KLV structure is not detected, it is possible to play back video and audio written in the MXF file without disorder.
- Further, as the video
data processing apparatus 10 according to the first embodiment can be realized by control using an all-purpose FTP protocol, it is unnecessary to design any special hardware as a file server. Specifically, it is possible to realize the video data processing apparatus and the file server at small cost. -
FIG. 7 is a block diagram illustrating a functional structure of a videodata processing apparatus 40 according to a second embodiment. -
FIG. 8 is a schematic diagram illustrating a structure of a Header and a Footer of an MXF file used in the second embodiment. The KLV coding method is adopted for the MXF file illustrated inFIG. 8 , like the MXF file in the first embodiment. Metadata is registered in both the Header and the Footer. InFIG. 8 , among header metadata information described in a Header value field and footer metadata information described in a Footer value field, information items which have the same number are the same as a rule. However, in the MXF file of this type, the video recording time, which is part of the Header metadata information, is not determined when preparation of the MXF file is started. Therefore, the Header metadata information is a provisional value, and the Footer metadata information is a fixed value. - The video
data processing apparatus 40 illustrated inFIG. 7 includes afile receiving module 11, ananalyzer 110, adata restoration module 111, a defaultdata storage module 14, acomparison module 112, amanagement module 15, astorage module 16, anexternal interface 17, acontrol module 18, and aplayback module 19. - The
analyzer 110 analyzes a Header and a Footer in an MXF file from thefile receiving module 11. Specifically, theanalyzer 110 reads out a Header Partition Pack Key, a Header Partition Pack Length, and a Header Partition Pack Value, and thereafter searches for “06h, 0Eh, 2Bh, 34h” which indicates the head of the Header Key Field. When “06h, 0Eh, 2Bh, 34h” is detected, theanalyzer 110 reads out 16 bytes of data, which is formed of “06h, 0Eh, 2Bh, 34h” of 4 bytes and the following data of 12 bytes, as a Header Key Field. After the Header Key Field is read out, theanalyzer 110 reads out a data length described in the Header Length field. Then, theanalyzer 110 reads out header metadata information described in the Header Value field, which is identified by the Header Key field and has a data length designated by the Header Length field, following the Header Length field. As described above, theanalyzer 110 detects a KLV structure by detecting a Header Key field, and obtains header metadata information included in each KLV structure. Theanalyzer 110 outputs the read header metadata information to thecomparison module 112. - When “06h, 0Eh, 2Bh, 34h” which indicates a head position of the Header Key field cannot be detected immediately following the Header Partition Pack Value or immediately following another Header Value field by analyzing the Header, the
analyzer 110 outputs a first redetection signal to thecontrol module 18. When thecontrol module 18 receives the first redetection signal, thecontrol module 18 determines that a KLV structure cannot be detected, and outputs a first control signal to redetect “06h, 0Eh, 2Bh, 34h” to thedata restoration module 111. In addition, when thecontrol module 18 receives the first redetection signal, thecontrol module 18 determines that the previous header metadata information obtained is abnormal, and outputs a first error signal indicating that the previous header metadata information is abnormal to thedata restoration module 111. Further, when thecontrol module 18 receives the first redetection signal, thecontrol module 18 outputs a second control signal to discontinue analysis of the Header to theanalyzer 110. When theanalyzer 110 receives the second control signal from thecontrol module 18, theanalyzer 110 discontinues analysis of the Header. - In addition, when the
analyzer 110 receives a third control signal to restart analysis of the Header from thecontrol module 18, theanalyzer 110 determines if the Header following “06h, 0Eh, 2Bh, 34h” redetected by thedata restoration module 111 has a KLV structure. If the fields following “06h, 0Eh, 2Bh, 34h” have a KLV structure, theanalyzer 110 restarts analysis of the Header. - The
analyzer 110 also performs the same analysis as the analysis of the Header, for the Footer, after analysis of the Header. Specifically, theanalyzer 110 reads out a Footer Partition Pack Key, a Footer Partition Pack Length, and a Footer Partition Pack Value, and then searches for “06h, 0Eh, 2Bh, 34h” which indicates the head of the Footer Key field. When “06h, 0Eh, 2Bh, 34h” is detected, theanalyzer 110 reads 16 bytes of data, which is formed of “06h, 0Eh, 2Bh, 34h” of 4 bytes and the following data of 12 bytes, as a Footer Key field. After the Footer Key field is read out, theanalyzer 110 reads a data length described in a Footer Length field. Then, theanalyzer 110 reads footer metadata information described in a Footer value field, which is identified by the Footer Key field and has a data length designated by the Footer Length field, following the Footer Length field. As described above, theanalyzer 110 detects a KLV structure by detecting the Footer Key field, and obtains footer metadata information included in each KLV structure. Theanalyzer 110 outputs the read footer metadata information to thecomparison module 112. - When “06h, 0Eh, 2Bh, 34h” which indicates a head position of the next Footer Key field cannot be detected immediately following the Footer Partition Pack Value or immediately following another Footer Value field by analysis of the Footer, the
analyzer 110 determines that a KLV structure cannot be detected, and outputs a second redetection signal to thecontrol module 18. When thecontrol module 18 receives the second redetection signal, thecontrol module 18 outputs a fourth control signal to redetect “06h, 0Eh, 2Bh, 34h” to thedata restoration module 111. In addition, when thecontrol module 18 receives the second redetection signal, thecontrol module 18 determines that the previous footer metadata information obtained is abnormal, and outputs a second error signal indicating that the previous footer metadata information is abnormal to thedata restoration module 111. Further, when thecontrol module 18 receives the second redetection signal, thecontrol module 18 outputs a fifth control signal to discontinue analysis of the Footer to theanalyzer 110. When theanalyzer 110 receives the fifth control signal from thecontrol module 18, theanalyzer 110 discontinues analysis of the Footer. - In addition, when the
analyzer 110 receives a sixth control signal to restart analysis of the Footer from thecontrol module 18, theanalyzer 110 determines if the footer following “06h, 0Eh, 2Bh, 34h” redetected by thedata restoration module 111 have a KLV structure. If the field following “06h, 0Eh, 2Bh, 34h” have a KLV structure, theanalyzer 110 restarts analysis of the Footer. - The
data restoration module 111 includes aheader obtaining module 1111, and afooter obtaining module 1112. When theheader obtaining module 1111 receives the first control signal from thecontrol module 18, theheader obtaining module 1111 searches for “06h, 0Eh, 2Bh, 34h” by pattern matching, while shifting byte by byte from a position where “06h, 0Eh, 2Bh, 34h” cannot be detected. When the next “06h, 0Eh, 2Bh, 34h” is detected, theheader obtaining module 1111 abandons data from the position where “06h, 0Eh, 2Bh, 34h” cannot be detected to a part before the next “06h, 0Eh, 2Bh, 34h”. When “06h, 0Eh, 2Bh, 34h” is detected, theheader obtaining module 1111 outputs detection of “06h, 0Eh, 2Bh, 34h” and the detected position to thecontrol module 18. When thecontrol module 18 receives notification from theheader obtaining module 1111, thecontrol module 18 outputs the third control signal to theanalyzer 110. - If a value of header metadata information is not fixed at the time when analysis of the header metadata information of the Header is finished, the
header obtaining module 1111 reads out default data for the header metadata information having an unfixed value from the defaultdata storage module 14, and outputs the read default data to thecomparison module 112. - In addition, when the
header obtaining module 1111 receives the first error signal from thecontrol module 18, theheader obtaining module 1111 reads out default data corresponding to the detected previous header metadata information from the defaultdata storage module 14, and outputs the read default data to thecomparison module 112. - When the
footer obtaining module 1112 receives the fourth control signal from thecontrol module 18, thefooter obtaining module 1112 searches for “06h, 0Eh, 2Bh, 34h” by pattern matching, while shifting byte by byte from a position where “06h, 0Eh, 2Bh, 34h” cannot be detected. When the next “06h, 0Eh, 2Bh, 34h” is detected, thefooter obtaining module 1112 abandons data from the position where “06h, 0Eh, 2Bh, 34h” cannot be detected to a part before the next “06h, 0Eh, 2Bh, 34h”. When “06h, 0Eh, 2Bh, 34h” is detected, thefooter obtaining module 1112 outputs detection of “06h, 0Eh, 2Bh, 34h” and the detected position to thecontrol module 18. When thecontrol module 18 receives notification from thefooter obtaining module 1112, thecontrol module 18 outputs the sixth control signal to theanalyzer 110. - If a value of footer metadata information is not fixed at the time when analysis of the footer metadata information of the Footer is finished, the
footer obtaining module 1112 reads out default data for the footer metadata information having an unfixed value from the defaultdata storage module 14, and outputs the read default data to thecomparison module 112. - In addition, when the
footer obtaining module 1112 receives the second error signal from thecontrol module 18, thefooter obtaining module 1112 reads out default data corresponding to the detected previous footer metadata information from the defaultdata storage module 14, and outputs the read default data to thecomparison module 112. - The
comparison module 112 receives the header metadata information and the footer metadata information from theanalyzer 110, and the default data from theheader obtaining module 1111 and thefooter obtaining module 1112. Thecomparison module 112 compares the header metadata information with the footer metadata information, and outputs data with the relation illustrated inFIG. 9 , according to whether these information items are “normal”, “abnormal”, or “not described”. - Since the header metadata information is a provisional value with high possibility,
FIG. 9 gives footer metadata information priority over header metadata information, when normal footer metadata information is detected. Specifically, thecomparison module 112 compares header metadata information with corresponding footer metadata information, and outputs the footer metadata information to themanagement module 15 when both are normal. When one metadata information is abnormal or one metadata information is not described among the header metadata information and the footer metadata information, thecomparison module 112 outputs the normal metadata information to themanagement module 15. When both the header metadata information and the footer metadata information are abnormal or are not described, thecomparison module 112 outputs the default data to themanagement module 15. - The
management module 15 receives normal metadata information and default data from thecomparison module 112, and records them. - When the
control module 18 receives a playback instruction from theexternal interface 17, thecontrol module 18 reads out metadata information of the MXF file designated by the playback instruction from themanagement module 15. Thecontrol module 18 generates a seventh control signal to read out the designated MXF file based on the read metadata information. - When default data for the designated MXF file is managed in the
management module 15, thecontrol module 18 also reads out the default data from themanagement module 15. Then, thecontrol module 18 generates a seventh control signal to read out the MXF file based on the read metadata information and the default data. Thecontrol module 18 outputs the generated seventh control signal to theplayback module 19. - The
playback module 19 decodes the MXF file read out from thestorage module 16 by using the metadata information and the default data, in accordance with the seventh control signal from thecontrol module 18. Theplayback module 19 outputs a video signal and an audio signal prepared by decoding to the outside. - The following is an explanation of the operation performed when the video
data processing apparatus 40 having the above structure obtains metadata information and default data, with reference to an operation process of thecontrol module 18. -
FIG. 10 is a flowchart illustrating processing of thecontrol module 18, which is performed when theanalyzer 110 and theheader obtaining module 1111 according to the second embodiment output header metadata information and default data to thecomparison module 112. - First, the
control module 18 performs analysis of the Header. Thecontrol module 18 determines if a first redetection signal is received from the analyzer 110 (Step S101). When the first redetection signal is received (Yes at Step S101), thecontrol module 18 outputs a first control signal to redetect “06h, 0Eh, 2Bh, 34h” from the position P1 ofFIG. 6 to theheader obtaining module 1111, and outputs a second control signal to discontinue analysis of the Header to theanalyzer 110. In addition, thecontrol module 18 outputs a first error signal indicating that the obtained previous header metadata information is abnormal to the header obtaining module 1111 (Step S102). When theheader obtaining module 1111 receives the first error signal, theheader obtaining module 1111 reads out default data for the obtained previous header metadata information from the defaultdata storage module 14, and outputs the read default data to thecomparison module 112. - When no first redetection signal is received (No at Step S101), the
control module 18 repeats Step S101 until thecontrol module 18 receives the first redetection signal. While Step S101 is repeated, theanalyzer 110 reads out metadata information from the Header based on the KLV structure, and outputs the read metadata information to thecomparison module 112. - Then, the
control module 18 determines if notification is received from theheader obtaining module 1111 that “06h, 0Eh, 2Bh, 34h” is received (Step S103). When theheader obtaining module 1111 receives the first control signal from thecontrol module 18, theheader obtaining module 1111 searches for “06h, 0Eh, 2Bh, 34h”, while shifting byte by byte from the position P1. Then, when “06h, 0Eh, 2Bh, 34h” is detected at position P2 shown inFIG. 6 , theheader obtaining module 1111 notifies thecontrol module 18 that “06h, 0Eh, 2Bh, 34h” is detected at the position P2. When theheader obtaining module 1111 detects “06h, 0Eh, 2Bh, 34h”, theheader obtaining module 1111 abandons data between the position P1 and the position P2. Then, when analysis of header metadata information in the Header is finished, theheader obtaining module 1111 outputs the default data read from the defaultdata storage module 14 to thecomparison module 112, instead of the abandoned header metadata information. - When notification is received from the header obtaining module 1111 (Yes at Step S103), the
control module 18 outputs a third control signal to restart analysis of the Header from the position P2 to the analyzer 110 (Step S104). When no notification is received from the header obtaining module 1111 (No at Step S103), thecontrol module 18 repeats the processing of Step S103 until notification is received from theheader obtaining module 1111. -
FIG. 11 is a flowchart illustrating processing of thecontrol module 18, which is performed when theanalyzer 110 and thefooter obtaining module 1112 according to the second embodiment output footer metadata information and default data to thecomparison module 112. - When analysis of the Header is finished, the
control module 18 performs analysis of the Footer. Thecontrol module 18 determines if a second redetection signal is received from the analyzer 110 (Step S111). When the second redetection signal is received (Yes at Step S111), thecontrol module 18 outputs a fourth control signal to redetect “06h, 0Eh, 2Bh, 34h” from the position P1 ofFIG. 6 to thefooter obtaining module 1112, and outputs a fifth control signal to discontinue analysis of the Footer to theanalyzer 110. In addition, thecontrol module 18 outputs a second error signal indicating that the obtained previous footer metadata information is abnormal to the footer obtaining module 1112 (Step S112). When thefooter obtaining module 1112 receives the second error signal, thefooter obtaining module 1112 reads out default data for the obtained previous footer metadata information from the defaultdata storage module 14, and outputs the read default data to thecomparison module 112. - When no second redetection signal is received (No at Step S111), the
control module 18 repeats Step S111 until thecontrol module 18 receives the second redetection signal. While Step S111 is repeated, theanalyzer 110 reads out metadata information from the Footer based on the KLV structure, and outputs the read footer metadata information to thecomparison module 112. - Then, the
control module 18 determines if notification is received from thefooter obtaining module 1112 that “06h, 0Eh, 2Bh, 34h” is received (Step S113). When thefooter obtaining module 1112 receives the fourth control signal from thecontrol module 18, thefooter obtaining module 1112 searches for “06h, 0Eh, 2Bh, 34h”, while shifting byte by byte from the position P1. Then, when “06h, 0Eh, 2Bh, 34h” is detected in position P2 shown inFIG. 6 , thefooter obtaining module 1112 notifies thecontrol module 18 that “06h, 0Eh, 2Bh, 34h” is detected at the position P2. When thefooter obtaining module 1112 detects “06h, 0Eh, 2Bh, 34h”, thefooter obtaining module 1112 abandons data between the position P1 and the position P2. Then, when analysis of footer metadata information in the Footer is finished, thefooter obtaining module 1112 outputs the default data read from the defaultdata storage module 14 to thecomparison module 112, instead of the abandoned footer metadata information. - When the
control module 18 determines that notification is received from the footer obtaining module 1112 (Yes at Step S113), thecontrol module 18 outputs a sixth control signal to restart analysis of the Footer from the position P2 to the analyzer 110 (Step S114). When thecontrol module 18 determines that no notification is received from the footer obtaining module 1112 (No at Step S113), thecontrol module 18 repeats the processing of Step S113 until notification is received from thefooter obtaining module 1112. - As described above, in the second embodiment described above, header metadata information is written in the Header, and footer metadata information is written in the Footer. In this case, the
analyzer 110 reads out header metadata information from the Header, and reads out footer metadata information from the Footer. Then, when both the header metadata information and the footer metadata information are normal, thecomparison module 112 selects the footer metadata information, and records the footer metadata information in themanagement module 15. Thereby, it is possible to record footer metadata information, which is a value more accurate than the header metadata information, in themanagement module 15. - In addition, in the second embodiment, when the KLV structure of one of the Header and the Footer is not detected and default data is obtained instead of one of the header metadata information and the footer metadata information, the
comparison module 112 selects metadata information which is normally obtained, and records the selected metadata information in themanagement module 15. Thereby, even when the KLV structure of one of the Header and the Footer is not detected, it is possible to obtain normal metadata information. - Although the second embodiment shows an example in which the Header and the Footer are successively analyzed from the head of the MXF file, the second embodiment is not limited to this structure. For example, it is possible to use a Random Index Pack Value which is located at the end of the MXF file illustrated in
FIG. 12 . - The following is an explanation of operation performed by the video
data processing apparatus 40 according to the second embodiment when metadata information is obtained from the MXF file by using the Random Index Pack Value. As illustrated inFIG. 12 , information which is called “Partition Pack” is inserted to the head part of the Header, the head and the middle parts of the Body, and the head part of the Footer. The Partition Pack includes a Partition Pack Key, a Partition Pack Length, and a Partition Pack Value. The Random Index Pack Value stores offset values from the head of the MXF file to the respective head positions of the Partition Pack Keys. - The
control module 18 controls thefile receiving module 11 to obtain the Random Index Pack Value of the MXF file recorded in thefile server 20. - In accordance with control by the
control module 18, thefile receiving module 11 outputs an output request based on a FTP protocol or the like to output the Random Index Pack Value of the MXF file to thefile server 20. In response to the output request, thefile server 20 outputs the Random Index Pack Value of the MXF file to thefile receiving module 11. Thefile receiving module 11 receives the Random Index Pack Value from thefile server 20, and notifies thecontrol module 18 of the received Random Index Pack Value. - The
control module 18 identifies the position of the Footer Partition Pack Key based on the Random Index Pack Value, and controls thefile receiving module 11 to obtain the Footer of the MXF file recorded in thefile server 20. In accordance with control by thecontrol module 18, thefile receiving module 11 outputs an output request to output the Footer of the MXF file to thefile server 20. In response to the output request, thefile server 20 outputs the Footer of the MXF file to thefile receiving module 11. Thefile receiving module 11 receives the Footer from thefile server 20, and outputs the received Footer to theanalyzer 110. - The
analyzer 110 analyzes the Footer, and obtains footer metadata information by using the KLV structure. Theanalyzer 110 outputs the obtained footer metadata information to thecomparison module 112. When the KLV structure cannot be detected during analysis of the Footer, thefooter obtaining module 1112 redetects “06h, 0Eh, 2Bh, 34h”, detects the next Footer Key field, and obtains default data. - When analysis of the Footer of the MXF file is finished, the
control module 18 controls thefile receiving module 11 to obtain the whole MXF file recorded in thefile server 20. In accordance with control by thecontrol module 18, thefile receiving module 11 outputs an output request to output the whole MXF file to thefile server 20. In response to the output request, thefile server 20 outputs the MXF file to thefile receiving module 11. Thefile receiving module 11 receives the MXF file from thefile server 20, and outputs the received MXF file to theanalyzer 110. - The
analyzer 110 analyzes the MXF file from the head, and obtains header metadata information by using the KLV structure. Theanalyzer 110 outputs the obtained header metadata information to thecomparison module 112. When the KLV structure cannot be detected during analysis of the Header, theheader obtaining module 1111 redetects “06h, 0Eh, 2Bh, 34h”, detects the next Header Key field, and obtains default data. - As described above, the video
data processing apparatus 40 may analyze the Footer of the MXF file before analyzing the Header, by using the Random Index Pack Value. When the whole MXF file is received from thefile server 20 and the received MXF file is successively analyzed from the head, the Footer is received after the Body of the MXF file is received. Therefore, it is required to wait until the transmission time of the Body is passed to start analysis of the Footer. However, analysis of the Footer is started first by using the Random Index Pack Value, and thereby it is possible to start playback processing of video and audio immediately following reception of the whole MXF file is started. - While certain embodiments have been described, these embodiments have been presented by way of example only, and are not intended to limit the scope of the inventions. Indeed, the novel embodiments described herein may be embodied in a variety of other forms; furthermore, various omissions, substitutions and changes in the form of the embodiments described herein may be made without departing from the spirit of the inventions. The accompanying claims and their equivalents are intended to cover such forms or modifications as would fall within the scope and spirit of the inventions.
Claims (6)
1. A video data processing apparatus which receives a data file that includes a header, in which a header key field, a header length field, and a header value field are repeatedly arranged in this order, and a footer, in which a footer key field, a footer length field, and a footer value field are repeated in this order, through a network, the header key field indicating a data type of header metadata information described in the following header value field, the header length field indicating a data length of the header value field, the header value field describing the header metadata information, the footer key field indicates a data type of footer metadata information described in the following footer value field, the footer length field indicates a data length of the footer value field, the footer value field describes the footer metadata information, the footer metadata information corresponds to the header metadata information, the video data processing apparatus comprising:
a file receiving module which is connected to the network, and receives the data file through the network;
an analyzing module which detects a character string which indicates a head of the header key field and a head of the footer key field, thereby detects a header key field and a footer key field of the data file received by the file receiving module, reads out header metadata information from a following header value field, based on a data type indicated by the header key field, and a data length indicated by the header length field following the header key field, and reads out footer metadata information from a following footer value field, based on a data type indicated by the footer key field, and a data length indicated by the footer length field following the footer key field;
a default data recording module which records in advance default data to be substituted for header metadata information and footer metadata information;
an obtaining module which retrieves the character string from a first position where the header key field should be detected, when the character string is not detected in the first position, obtains default data from the default data recording module as header metadata information to be read out from the first position to a next header key field, retrieves the character string from a second position where the footer key field should be detected, when the character string is not detected in the second position, and obtains the default data from the default data recording module as footer metadata information to be read out from the second position to a next footer key field;
a comparing module which determines if the header metadata information and the footer metadata information, which correspond to each other and are read by the analyzing module, are normal or not, selects the footer metadata information when both are normal, selects the other normal metadata information when one metadata information is not normal, and selects the default data obtained by the obtaining module when both are not normal, and
a management module which records the header metadata information, the footer metadata information, or the default data selected by the comparing module.
2. The video data processing apparatus of claim 1 , wherein
the comparing module outputs the other normal metadata information to the management module when one of the header metadata information and the footer metadata information which correspond to each other is abnormal or is not described, and outputs the default data to the management module when both the header metadata information and the footer metadata information are abnormal or is not described.
3. The video data processing apparatus of claim 1 , wherein
the analyzing module reads out footer metadata information from a following footer value field, based on a data type indicated by the next footer key field and a data length indicated by a footer length field following the next footer key field.
4. The video data processing apparatus of claim 1 , further comprising:
a recording module which records the data file, after analysis of the data file by the analyzing module is finished; and
a playback module which plays back the data file recorded in the recording module, in accordance with a playback instruction, based on the header metadata information, the footer metadata information, and the default data recorded in the management module.
5. The video data processing apparatus of claim 1 , wherein
the data file is an MXF file, the MXF file includes a header, a body, and a footer, to which a partition pack is inserted, and includes a random index pack value which describes offset values from a head of the MXF file to respective head positions of the partition packs at an end of the footer,
the file receiving module receives the footer of the MXF file earlier than the header of the MXF file, by referring to the offset values described in the random index pack value, and
the analyzing module performs analysis of the footer earlier than analysis of the header.
6. A file management method used in a video data processing apparatus which receives a data file that includes a header, in which a header key field, a header length field, and a header value field are repeatedly arranged in this order, and a footer, in which a footer key field, a footer length field, and a footer value field are repeated in this order, through a network, the header key field indicating a data type of header metadata information described in the following header value field, the header length field indicating a data length of the header value field, the header value field describing the header metadata information, the footer key field indicates a data type of footer metadata information described in the following footer value field, the footer length field indicates a data length of the footer value field, the footer value field describes the footer metadata information, the footer metadata information corresponds to the header metadata information, the file management method comprising:
connecting to the network, and receiving the data file through the network;
detecting a character string which indicates a head of the header key field and a head of the footer key field, thereby detecting a header key field and a footer key field of the received data file, reading out header metadata information from a following header value field, based on a data type indicated by the header key field, and a data length indicated by the header length field following the header key field, and reads out footer metadata information from a following footer value field, based on a data type indicated by the footer key field, and a data length indicated by the footer length field following the footer key field;
retrieving the character string from a first position where the header key field should be detected, when the character string is not detected in the first position, and obtaining default data which is to be substituted for the header metadata information, as header metadata information to be read out from the first position to a next header key field;
retrieving the character string from a second position where the footer key field should be detected, when the character string is not detected in the second position, and obtains the default data from the default data recording module as footer metadata information to be read out from the second position to a next footer key field;
determining if the header metadata information and the footer metadata information, which correspond to each other and are read by the analyzing module, are normal or not;
selecting the footer metadata information when both are normal;
selecting the other normal metadata information when one metadata information is not normal;
selecting the default data obtained by the obtaining module when both are not normal; and
recording the header metadata information, the footer metadata information, or the default data selected by the comparing module in a management module.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/741,264 US20130129319A1 (en) | 2010-09-16 | 2013-01-14 | Video data processing apparatus and file management method |
Applications Claiming Priority (4)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2010207631A JP5044687B2 (en) | 2010-09-16 | 2010-09-16 | Video processing apparatus and file management method |
JP2010-207631 | 2010-09-16 | ||
US13/192,308 US8761579B2 (en) | 2010-09-16 | 2011-07-27 | Video data processing apparatus and file management method |
US13/741,264 US20130129319A1 (en) | 2010-09-16 | 2013-01-14 | Video data processing apparatus and file management method |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/192,308 Division US8761579B2 (en) | 2010-09-16 | 2011-07-27 | Video data processing apparatus and file management method |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130129319A1 true US20130129319A1 (en) | 2013-05-23 |
Family
ID=45817840
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/192,308 Active US8761579B2 (en) | 2010-09-16 | 2011-07-27 | Video data processing apparatus and file management method |
US13/741,264 Abandoned US20130129319A1 (en) | 2010-09-16 | 2013-01-14 | Video data processing apparatus and file management method |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US13/192,308 Active US8761579B2 (en) | 2010-09-16 | 2011-07-27 | Video data processing apparatus and file management method |
Country Status (3)
Country | Link |
---|---|
US (2) | US8761579B2 (en) |
JP (1) | JP5044687B2 (en) |
KR (1) | KR20120030007A (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105468711A (en) * | 2015-11-19 | 2016-04-06 | 中央电视台 | Audio processing method and apparatus |
Families Citing this family (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN103379483B (en) | 2012-04-16 | 2017-06-06 | 中兴通讯股份有限公司 | A kind of method of information of mobile terminal safety management, device and mobile terminal |
CN102932677B (en) * | 2012-08-16 | 2014-05-07 | 中央电视台 | Device and method for detecting pack format of media file |
US10659520B1 (en) * | 2015-06-30 | 2020-05-19 | Amazon Technologies, Inc. | Virtual disk importation |
Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040218902A1 (en) * | 2000-02-07 | 2004-11-04 | Noboru Yanagita | Image processing apparatus, image processing method, and recording medium |
JP2008187371A (en) * | 2007-01-29 | 2008-08-14 | Oki Electric Ind Co Ltd | Content reception/reproduction/storage device |
US7831127B2 (en) * | 2000-09-06 | 2010-11-09 | Sony United Kingdom Limited | Combining video material and data |
US8189690B2 (en) * | 2009-10-19 | 2012-05-29 | Intergraph Technologies Company | Data search, parser, and synchronization of video and telemetry data |
Family Cites Families (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
JPH08214104A (en) | 1995-02-02 | 1996-08-20 | Olympus Optical Co Ltd | Information reproduction system |
JP3768008B2 (en) | 1998-07-21 | 2006-04-19 | 松下電器産業株式会社 | Image signal reproduction device |
JP4686587B2 (en) | 2008-10-16 | 2011-05-25 | 株式会社東芝 | Video recording / reproducing apparatus and file management method |
-
2010
- 2010-09-16 JP JP2010207631A patent/JP5044687B2/en not_active Expired - Fee Related
-
2011
- 2011-07-27 US US13/192,308 patent/US8761579B2/en active Active
- 2011-09-14 KR KR1020110092359A patent/KR20120030007A/en not_active Application Discontinuation
-
2013
- 2013-01-14 US US13/741,264 patent/US20130129319A1/en not_active Abandoned
Patent Citations (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20040218902A1 (en) * | 2000-02-07 | 2004-11-04 | Noboru Yanagita | Image processing apparatus, image processing method, and recording medium |
US7831127B2 (en) * | 2000-09-06 | 2010-11-09 | Sony United Kingdom Limited | Combining video material and data |
JP2008187371A (en) * | 2007-01-29 | 2008-08-14 | Oki Electric Ind Co Ltd | Content reception/reproduction/storage device |
US8189690B2 (en) * | 2009-10-19 | 2012-05-29 | Intergraph Technologies Company | Data search, parser, and synchronization of video and telemetry data |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
CN105468711A (en) * | 2015-11-19 | 2016-04-06 | 中央电视台 | Audio processing method and apparatus |
Also Published As
Publication number | Publication date |
---|---|
US20120070126A1 (en) | 2012-03-22 |
US8761579B2 (en) | 2014-06-24 |
JP2012065137A (en) | 2012-03-29 |
KR20120030007A (en) | 2012-03-27 |
JP5044687B2 (en) | 2012-10-10 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20230319229A1 (en) | System and method for modifying media streams using metadata | |
EP1329108B1 (en) | System and method of processing mpeg streams for file index insertion | |
US20030035648A1 (en) | Navigation for MPEG streams | |
JP5513400B2 (en) | Hierarchical and simple index structure for multimedia files | |
US8959202B2 (en) | Generating statistics of popular content | |
JP4686587B2 (en) | Video recording / reproducing apparatus and file management method | |
JP2007041722A (en) | Information processor, content reproduction device, information processing method, event log recording method and computer program | |
JP2009181216A (en) | Electronic apparatus and image processing method | |
US20130129319A1 (en) | Video data processing apparatus and file management method | |
KR20150004681A (en) | Server for providing media information, apparatus, method and computer readable recording medium for searching media information related to media contents | |
US7373439B2 (en) | System method using material exchange format (MXF) converting program for audio and video data files having routines that generates attribute data from audio and video data file | |
JP2006139682A (en) | Video search system, video search method, and program | |
EP2685456A1 (en) | Index with offset to closest I-picture entry for random access in a bitstream. | |
JP2006279147A (en) | Index file generating apparatus and moving picture edit apparatus | |
KR101251830B1 (en) | Video data processing apparatus and video data processing method | |
JP5857591B2 (en) | Video distribution device | |
RU2549102C2 (en) | Method of determining real-time broadcast media streams and system therefor | |
CN113672423A (en) | Method for restoring analysis file of album file and terminal equipment | |
CN117056287A (en) | Multichannel video data processing method and device, storage medium and electronic device | |
JP2011076353A (en) | Media player and content id determination method | |
JP2006113639A (en) | Contents storage device | |
JP2005033750A (en) | Video recording and regenerating method by user choosing content of text visibly | |
JP2010107767A (en) | Method for reproducing of compressed audio file | |
JP2011076668A (en) | Media player, method of acquiring information, database server and method of providing information |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: KABUSHIKI KAISHA TOSHIBA, JAPAN Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:NAKAO, AKIHIKO;REEL/FRAME:030181/0314 Effective date: 20110506 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |