JP2006140992A - Data processing apparatus - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To generate management information of an appropriate format without analyzing a data stream and to transfer the data stream and the management information at high speed to various recording media with different formats of the management information. <P>SOLUTION: A data processing apparatus includes an encoder and a management information generating unit. The encoder generates a plurality of reproduction units each including I/B/P picture data, and information indicating reproduction time to reproduce each of the pictures to generate a data stream. The management information generating section generates, in accordance with the type of the recording medium, one of picture information defining a correspondence between a reproduction time of an I picture to be recorded first in respective reproduction units and its recording position, and reproduction unit information defining a correspondence between a reproduction time length of a reproduction unit and the recording position of the I picture, and information relating to a reproduction time length of a picture within a reproduction unit. Such information is stored in one or more tables for each of reproduction units as management information. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a technique for writing encoded video / audio data on a recording medium such as an optical disk, a hard disk, or a memory card, and reproducing the written video / audio data.

  In order to compress video data at a low bit rate, the MPEG2 standard (ISO / IEC 13818-1) defines a system stream. Three types of system streams are defined: a program stream, a transport stream, and a PES (Packetized Elementary Stream) stream.

  Such a system stream is written and stored on an optical disc, for example. An optical disk is a recording medium for video data instead of a magnetic tape, and a phase change optical disk represented by a DVD-RAM and a Blu-ray Disc, and a magneto-optical disk represented by an MO are known.

  For example, as a standard for recording video data on a DVD-RAM, the VIDEO RECORDING standard (DVD Specifics for Rewriteable / Re-recordable Discs Part 3 VIDEO RECORDING Version 1.0 September 1999) has been formulated. According to this standard, a data file of video data is recorded on a DVD-RAM disc in the MPEG2 program stream format.

  As another example, a standard for recording video data on a Blu-ray Disc has been developed. In the standard, a data file of video data is recorded in an MPEG2 transport stream format defined by ISO / IEC 13818-1. In the transport stream, video data is compressed by the MPEG2 system defined by ISO / IEC 13818-2, and audio data is compressed by, for example, MPEG2-AAC (Advanced Audio Cording) defined by ISO / IEC 13818-7. The

  FIG. 1 shows a data structure when video is recorded on the phase change optical disk 131 in real time. In FIG. 1, the phase change optical disk is composed of 2 Kbyte sectors, and 16 sectors are handled as one logical block, and an error correction code is assigned to each logical block and recorded on the phase change disk. ing. For example, Patent Document 1 discloses the above-described data structure.

  Furthermore, a physically continuous logical block having a data size of at least a predetermined time (for example, data of 11 seconds in terms of maximum recording / reproducing rate) is secured as one continuous data area, and 0.4 to 1 is allocated to this area. Unit video packets (Video Object UNIT: hereinafter referred to as “VOBU”) composed of MPEG transport streams for seconds are recorded in order.

  One VOBU is composed of transport packets which are lower layers of an MPEG transport stream of 188 bytes. The transport packet stores a video transport packet (V_TSP) in which video compressed data is stored, an audio transport packet (A_TSP) in which audio compressed data is stored, and a program association table packet (PAT). The transport packet (PAT_TSP) and the transport packet (PMT_TSP) in which the program map table (PMT) is stored are configured.

  One VOBU includes V_TSP related to pictures for a predetermined playback time. Furthermore, one VOBU includes all A_TSPs including audio frames necessary for video reproduction. That is, the audio frame is completed within the VOBU. In addition, the data size of one VOBU varies within a range equal to or less than the maximum recording / reproducing rate if the video is a variable bit rate. If the video is a fixed bit rate, the data size of VOBU is almost constant.

  2A to 2E show details of V_TSP, A_TSP, PAT_TSP, PMT_TSP, and V_TSP having no PCR, respectively. V_TSP is composed of a transport packet header and video data. A_TSP is composed of a transport packet header and audio data. PAT_TSP mainly includes a transport packet header and a program association table. PMT_TSP mainly includes a transport packet header and a program map table. When PCR (program clock reference) is added to V_TSP, the PCR value is recorded in the adaptation field adjacent to the transport packet header as shown in FIG.

  V_TSP, A_TSP, PAT_TSP, and PMT_TSP are each identified by a PID (Packet ID) in the transport packet header. For example, as shown in FIGS. 2A to 2D, the PID of V_TSP is “0x0020”, the PID of A_TSP is “0x0021”, the PID of PAT_TSP is “0x0000”, and the PID of PMT_TSP is “0x0030”. When the PID value is detected, the type of the packet is identified.

  Here, the assignment status of PIDs for V_TSP and A_TSP is described in a program map table in PMT_TSP. The PID for PMT_TSP is described in the program association table in PAT_TSP. The PID for PAT_TSP takes a fixed value of “0x0000”.

  The PCR is a sample value of a 27 MHz clock indicating the time when the transport packet arrives at the virtual MPEG decoder. The MPEG2 standard (ISO / IEC 13818-1) stipulates that a PCR is inserted at an arbitrary timing within at least 100 msec in a transport packet having a specific PID.

  In the PCR_PID field in the PMT, which PID is selected for describing the PCR is recorded. The apparatus that has received the stream inputs this PCR value to the 27 MHz clock and applies PLL (Phase Lock Loop). Further, the apparatus uses the PCR value to obtain a reference value for the display timing value and the decoding timing value. That is, the apparatus sets a PCR value as an initial value of a 27 MHz clock, and thereafter uses the PCR value as a clock on the transmission side by inputting the PCR value to the PLL. The apparatus then decodes the video data at a timing at which the clock value matches the decoding timing value (decoding time stamp, DTS) or display timing value (presentation time stamp, PTS) included in the video data. The video based on the video data is displayed. Note that audio data is different from video data in that only PTS is included. It is the same as video data in that decoding and output are performed at the same timing as PTS.

  The apparatus redetects the next continuous data area when the remaining one continuous data area becomes small. When one continuous data area is full, data is written to the next continuous data area.

  FIG. 3 shows an example of data on an optical disc managed on a UDF (Universal Disk Format) file system. In FIG. 3, one MPEG transport stream is converted into a file MOVIE. By one operation of turning on and off the recording start button. The case where it records as MPG is shown.

  As shown in FIG. 3, the file name and the position of the file entry are managed by an FID (File Identifier Descriptor). In addition, one file and three continuous data areas a, b, and c constituting the file are managed by using the allocation descriptor in the file entry.

  The process of dividing the continuous data area into three will be described. First, when the apparatus detects a defective logical block during recording in the continuous data area a, the defective logical block is skipped and writing is continued from the beginning of the continuous data area b.

  If the apparatus detects the recording area of the PC file during recording in the continuous data area b, the apparatus skips the recording area of the PC file and continues writing from the beginning of the continuous data area c. As a result, the file MOVIE. The MPG is composed of three areas, continuous data areas a, b, and c.

  FIG. 4 shows the relationship between VOBUs and transport packets, and video elementary streams and audio elementary streams. Here, it is assumed that one VOBU is composed of M GOPs (Group of Pictures).

  Each video frame and each audio frame includes a PES header. One VOBU includes a sequence header at the head. Each GOP includes a GOP header.

  The PES header of the leading video or audio in each VOBU is adjusted to start from the beginning of the payload of each transport packet. Specifically, padding data is inserted into the immediately preceding transport packet to adjust the data size of the transport stream.

  PAT_TSP and PMT_TSP store the PID of a packet in which video data is stored and the PID of a packet in which audio data is stored. Therefore, it can be said that video and audio cannot be reproduced unless at least these two PIDs can be recognized.

  In order to control decoding timing and output timing based on PTS and DTS at the time of decoding, it is necessary to quickly initialize the 27 MHz clock value to an appropriate value. For this purpose, it is necessary that the MPEG decoder receives the PCR value as soon as possible and starts using the value as a clock value.

  For a specific configuration of an apparatus for writing the above-described video data and audio data on a phase change optical disk, see, for example, Patent Document 2.

  In the MPEG2 standard (ISO / IEC 13818-1), the insertion timing of PAT_TSP, PMT_TSP and PCR is not defined. Moreover, although the insertion frequency of PCR is prescribed | regulated, the insertion frequency of PAT_TSP and PMT_TSP is not prescribed | regulated.

On the other hand, many playback devices that play back video recorded on a disc have a function of playing back specific scenes of the video in the user's preferred order. When playing back video from a specific scene, playback of video data is generally started from the beginning of the sequence header.
JP 11-155130 A International Publication No. WO02 / 080541

  However, in general, the insertion timing of PAT_TSP, PMT_TSP, and PCR with respect to V_TSP including the beginning of a sequence header serving as a playback start point is not defined in the standard. Even if the device reads data from the head of the sequence header, V_TSP and A_TSP cannot be recognized by referring to the PID unless PAT_TSP and PMT_TSP are detected. Therefore, the decoding process cannot be executed until PAT_TSP and PMT_TSP are detected.

  Thus, since PAT_TSP and PMT_TSP are not detected, for example, when an I picture immediately after the sequence header cannot be recognized, video cannot be displayed until the next sequence header. As a result, typically, video and audio of about 0.5 to 1.0 seconds are not output.

  Further, when playing back while sequentially switching a specific scene, the PID registered in PAT_TSP and PMT_TSP may be different for each scene. In addition, descriptor information included in PAT_TSP and PMT_TSP may be different for each scene. For this reason, it is necessary to pass PAT_TSP and PMT_TSP to the MPEG decoder as early as possible with appropriate contents at least for each scene.

  In particular, when transmitting to STB (set top box) or DTV (digital television) connected by IEEE1394 interface using the transport protocol of ISO-61883 transport stream, transmission of PAT_TSP, PMT_TSP, and PCR is important. become. This is because there is no means for transmitting the used PID, PCR value, etc. separately from the transport stream.

  When playing back using the MPEG decoder of the device, the used PID, PCR value, etc. are different using a different path from the MPEG stream (for example, via a CPU connected to the MPEG decoder). It is conceivable to convert the data structure before transmission.

  However, in order to transmit information necessary for each scene from another route, information on the PID and information on the top PCR value are recorded at the time of recording for each VOBU, and those information is recorded in the MPEG before the scene is switched. It is necessary to transmit to the decoder. In this method, it is necessary to record PID and PCR values as management data in units of VOBU, which increases the data capacity. Further, since a processing delay occurs, this method is used to reproduce the video using the MPEG decoder of the device and simultaneously output the video signal to the 1394 interface and display the same video at both output destinations. Is not enough.

  In addition, there is a problem when a stream stored on the hard disk of the PC is played back using an MPEG playback application running on the PC. Specifically, even if playback is started from a specific scene, if PAT_TSP, PMT_TSP, and PCR are recorded from the middle of the scene, the video from the position after the first sequence header is detected after that scene. It was displayed. Alternatively, after detecting PAT_TSP, PMT_TSP, and PCR inserted after the data corresponding to the playback start point, it is necessary to return to the playback start point and start playback. This causes a delay in starting reproduction and a delay in switching scenes.

  Furthermore, problems have arisen when copying or dubbing an MPEG stream to another recording medium. That is, when it is necessary to convert the data structure of the management information of the MPEG stream, for example, it is necessary to analyze the MPEG stream for each VOBU and generate management information that can be recorded on the copy destination recording medium. This may require a great deal of processing time. This problem may also occur when the MPEG stream on the copy source recording medium is copied to another device as it is and copied.

  An object of the present invention is to easily reproduce all frames within a specified range within a device even when the middle of a file is set as a reproduction start point, and the same frame is connected to a device via a 1394 interface. It is providing the apparatus and method which can be reproduced | regenerated by this.

  Another object of the present invention is to generate management information in an appropriate format for various recording media having different formats of management information without analyzing the data stream, and to speed up the data stream and the management information. Is to be able to transfer.

  A data processing apparatus according to the present invention includes an encoder that performs an encoding process on a video signal to generate a data stream, a management information generation unit that generates management information for reproducing video from the data stream, the data stream, A drive for writing the management information to a recording medium. The encoder generates a plurality of reproduction units including data of a reference picture that can be decoded independently, data of one or more reference pictures that need to be decoded from the reference picture, and time information indicating a reproduction time of each picture. , Arrange and generate the data stream. The management information generation unit, according to the type and recording format of the recording medium, reference picture information in which a reproduction time of a reference picture recorded first in each reproduction unit is associated with a recording position of the reference picture; And generating one piece of reproduction unit information for associating the reproduction time length of the reproduction unit with the recording position of the reference picture, and further generating and managing time length information related to the reproduction time length of the picture in the reproduction unit Information is stored in one or more tables for each reproduction unit.

  Due to the encoding process, the order in which the data of each picture is arranged is different from the order in which each picture is displayed. The encoder includes one or more reference pictures arranged after the first reference picture with respect to an arrangement of data in the reproduction unit, wherein the one or more reference pictures are displayed before the first reference picture. The management information generation unit generates time length information related to the playback time length of the specified one or more reference pictures, and further stores the information in one or more tables for each playback unit. Good.

  The management information generation unit generates a first flag for specifying one of the generated reference picture information and the reproduction unit information, and a second flag indicating that the time length information is included, You may further store in one or more tables for every reproduction | regeneration unit.

  The data processing apparatus may further include a conversion unit that converts the format of the management information. When the management information generation unit generates the reference picture information, the conversion unit may further generate the reproduction unit information based on the reference picture information and the time length information.

  The conversion unit may generate new management information by replacing the generated reproduction unit information with the reference picture information.

  The data processing apparatus may further include an interface unit for performing data communication with an external device. The interface unit may output the new management information and the data stream to the external device.

  The data processing apparatus may further include a conversion unit that converts the format of the management information. When the management information generation unit generates the reproduction unit information, the conversion unit may further generate the reference picture information based on the reproduction unit information and the time length information.

  The conversion unit may generate new management information by replacing the generated reference picture information with the reproduction unit information.

  The data processing apparatus may further include an interface unit for performing data communication with an external device. The interface unit may output the new management information and the data stream to the external device.

  The data processing method according to the present invention is used to write a video data stream and management information for reproducing the video from the data stream to a recording medium. In the data processing method, reference picture data that can be decoded independently by performing an encoding process on a video signal, data of one or more reference pictures that require decoding from the reference picture, and reproduction time of each picture Generating a plurality of playback units including time information indicating the time information, generating a data stream by arranging the plurality of playback units, and depending on the type and recording format of the recording medium, One of reference picture information that associates the reproduction time of the reference picture recorded in the recording position with the recording position of the reference picture, and reproduction unit information that associates the reproduction time length of the reproduction unit with the recording position of the reference picture. Generating a time length information related to a playback time length of a picture in the playback unit; One of the reference picture information and the reproduction unit information, and the time length information are stored as management information in one or more tables for each reproduction unit, and the data stream and the management information are written to the recording medium. Including.

  A circuit chip according to the present invention includes an encoder that performs an encoding process on a video signal to generate a data stream, and a management information generation unit that generates management information for reproducing a video from the data stream. The circuit chip can write the data stream and the management information to a recording medium via a drive. The encoder generates a plurality of reproduction units including data of a reference picture that can be decoded independently, data of one or more reference pictures that need to be decoded from the reference picture, and time information indicating a reproduction time of each picture. Arrange to generate the data stream. The management information generation unit, according to the type and recording format of the recording medium, reference picture information in which a reproduction time of a reference picture recorded first in each reproduction unit is associated with a recording position of the reference picture; And generating one piece of reproduction unit information for associating the reproduction time length of the reproduction unit with the recording position of the reference picture, and further generating and managing time length information related to the reproduction time length of the picture in the reproduction unit Information is stored as a table for each reproduction unit.

  The computer program according to the present invention can be executed in a computer, and is used to generate a video data stream and management information for reproducing the video from the data stream. The computer program causes the computer to perform encoding processing on a video signal and to decode standard picture data that can be decoded independently, data of one or more reference pictures that require decoding from the standard picture, and each picture Generating a plurality of playback units including time information indicating the playback time, generating a data stream by arranging the plurality of playback units, and each playback unit according to the type and recording format of the recording medium Reference picture information in which the reproduction time of the reference picture recorded first and the recording position of the reference picture are associated with each other, and reproduction unit information in which the reproduction time length of the reproduction unit is associated with the recording position of the reference picture And generating time length information related to the playback time length of the picture in the playback unit. Storing one of the generated reference picture information and the reproduction unit information and the time length information as management information in one or more tables for each reproduction unit, and the data stream and the management information Are written on the recording medium.

  The data processing apparatus of the present invention holds the time length information related to the playback time length of the reference picture played back before the first reference picture in the stream playback unit in the management information table. By using this information, when exporting a stream file and management file with its management information recorded to another recording medium, management data can be converted without analyzing the stream for each object. Processing can be realized.

  Hereinafter, first to seventh embodiments of a data processing apparatus according to the present invention will be described with reference to the accompanying drawings. It should be noted that particularly main processes, data structures and the like relating to the present invention will be described in Embodiments 6 and 7.

(Embodiment 1)
FIG. 5 shows a configuration of an optical disc recorder 200 (hereinafter referred to as “recorder 200”) according to the present embodiment. The recorder 200 processes an MPEG2 transport stream (hereinafter referred to as “transport stream”). When recording a video signal and an audio signal, the signals input from the video signal input unit 100 and the audio signal input unit 102 are compressed by the video compression unit 101 and the audio compression unit 103, respectively, and then the PAT / PMT in the system encoding unit 104 A packet including PAT and a packet including PMT generated by the generation unit 105 is mixed with the compressed video signal and audio signal to create a transport stream, and written to the phase change optical disc 131 via the recording unit 120 and the pickup 130. . This process is performed while receiving a video signal and an audio signal. That is, since recording is performed in parallel with signal reception, it is also called real-time recording. The above-described video compression unit 101, audio compression unit 103, system encoding unit 104, and PAT / PMT generation unit 105 constitute an MPEG encoder 170.

  At the time of reproduction of the video signal and the audio signal, the transport stream taken out via the pickup 130 and the reproduction unit 121 is separated into the video signal and the audio signal by the system decoding unit 114, and the video expansion unit 111 and the audio expansion unit are respectively separated. The video data is output to the video display unit 110 and the audio output unit 112 via 113. The video decompression unit 111, the audio decompression unit 113, and the system decoding unit 114 constitute an MPEG decoder 171.

  At the time of recording the video signal and the audio signal, the recording control unit 161 controls the recording unit 120, the continuous data area detection unit 160, and the logical block management unit 163 to perform recording. At this time, the continuous data area detection unit 160 checks the usage status of the sectors managed by the logical block management unit 163 according to an instruction from the recording control unit 161 and detects physically continuous free areas.

  At the time of reproduction of the video signal and the audio signal, the reproduction control unit 162 controls the reproduction unit 121 to perform reproduction.

  When the recorded video file is output to the outside in the isochronous transfer mode via the IEEE 1394 interface unit 140, the output timing of the transport stream read out via the playback unit 121 is obtained by the output timing generation unit 141, and the calculated transmission is performed. The transport stream is transferred to the 1394 interface unit 140 according to the timing.

  The device according to the present embodiment has a main feature in the timing at which the system encoding unit 104 inserts PAT_TSP, PMT_TSP, and PCR.

  FIG. 6 shows the data structure of a recording file recorded by the recorder 200. The recording file is assumed to be composed of a well-known VOBU except for the recording positions of PAT_TSP and PMT_TSP.

  In FIG. 6, PAT_TSP and PMT_TSP are always arranged at the head of each VOBU. Further, V_TSP having PCR is arranged in the next transport packet. In the VOBU, PAT_TSP and PMT_TSP are inserted so as to record at a frequency within 100 msec according to the Japanese BS digital broadcasting standard and the European digital broadcasting (DVB) standard. Specifically, for example, PAT_TSP and PMT_TSP are recorded once every two to three frames. Furthermore, in the VOBU, PCR is also recorded at time intervals within 100 msec in accordance with the provisions of the MPEG2 standard (ISO / IEC 13818-1).

  With the above configuration, when the playback start point that can be set by the user is the head of the VOBU, the head of any VOBU is always specified, so that the head always includes PAT_TSP and PMT_TSP. Therefore, the system decoding unit 114 can easily identify video data and audio data for all subsequent transport packets, and can be easily distributed to the video expansion unit 111 and the audio expansion unit 113 for reproduction display. It becomes possible. As a result, all the designated frames can be displayed at the start of reproduction and without missing the designated frames at the time of scene switching. Furthermore, since the PCR arrives before the DTS and PTS added to the video, the MPEG decoder can perform reproduction display utilizing (referring to) the DTS or PTS.

  In addition, when a transport stream is output to an external device via the 1394 interface unit 140, a transport stream having PAT_TSP and PMT_TSP as the top packet is easy regardless of which VOBU head is designated as the playback start point. Can be output.

  Furthermore, in the present embodiment, the file is described as being managed by the UDF file system. However, the same effect can be expected even when the file is managed by the FAT or other unique file system.

  In this embodiment, the recording frequency of PAT_TSP and PMT_TSP in VOBU is assumed to be at least once every 100 msec. However, according to other standards, PAT_TSP and PMT_TSP are inserted at different frequencies. May be.

  In this embodiment, the PCR is included in the first V_TSP in the VOBU. However, a transport packet consisting only of the PCR may be recorded between the first V_TSP and the PMT_TSP in the VOBU. The PID of this transport packet may be the same as or different from the PID of V_TSP.

(Embodiment 2)
In the first embodiment, as shown in FIG. 5, a transport stream is generated and recorded in the recorder, and is reproduced in the recording / reproducing apparatus, and at the same time, the transport stream is output to the outside.

  The present embodiment is different from the first embodiment in that a transport stream input from the outside is recorded and then the transport stream is output to the outside.

  FIG. 7 shows a block configuration of an optical disc recorder 300 (hereinafter referred to as “recorder 300”) according to the present embodiment. In FIG. 7, at the time of recording, a transport stream is input from the 1394 interface unit 301, and writing is performed on the phase change optical disk 311 via the recording unit 303 and the pickup 312. At this time, the recording control unit 307 activates the continuous data area detection unit 306 at the same time, and detects an empty continuous data area necessary for recording. The logical block management unit 310 receives the notification of the logical block number used at the time of recording from the recording control unit 307 and manages the usage status.

  In addition, the management information generation unit 302 detects a V_TSP including a sequence header and a PES header immediately before the sequence header, a transport packet PAT_TSP including a PAT, and a transport packet PMT_TSP including a PMT from the input transport stream. . Then, the management information generation unit 302 generates, as management information, the data size between the V_TSP and the PES header including adjacent sequence headers, and the time length during reproduction. The playback time length is generated in units of video frames. Further, the data size of the I picture immediately after the sequence header is also generated as management information.

  Further, a transport packet including a PMT inputted in the past in the past from a V_TSP including a sequence header and a PES header, and including a PAT inputted in the past in the past. The data size between the transport packet including the sequence header and the PES header is also generated as management information in units of the number of transport packets.

  The recording control unit 307 activates the recording unit 303 for the input transport packet, writes management information on the phase change optical disc, and generates a management file.

  On the other hand, at the time of reproduction, the reproduction control unit 308 first reads out the management file stored in the phase change optical disk 311 via the pickup 312 and the reproduction unit 305. Then, by referring to the management file based on the designated playback start time, the recording position of the corresponding MPEG Sequence Object Unit (hereinafter referred to as “SOBU”) and the position of the corresponding PAT_TSP are determined, and the PAT_TSP Data, the first PMT_TSP data included after that position, and the data after the corresponding SOBU are read out via the pickup 312 and the playback unit 305. That is, transport packets other than PAT_TSP and PMT_TSP among the transport packets recorded between the PAT_TSP and the corresponding SOBU head are not output. The SOBU will be described later.

  Further, the read data is output via the output timing generation unit 304 and the 1394 interface unit 301. The output timing generation unit 304 performs an appropriate output timing by performing buffer simulation of the transport stream target decoder (T_STD) defined by the MPEG2 system standard (ISO / IEC 13818-1) on the read data. And the read data is passed to the 1394 interface unit 301 in accordance with the calculated output timing. The 1394 interface unit 301 outputs a transport packet while maintaining the timing.

  FIG. 8 is a data structure diagram of a recording file recorded by the recorder 300. As shown in FIG. 8, the recording file is composed of SOBU.

  In the present specification, SOBU and VOBU (FIG. 6) are properly used as follows. That is, “VOBU” refers to a reproduction unit of a data stream when a recorder mainly generates and encodes an analog signal. On the other hand, “SOBU” refers to a data stream reproduction unit when the data structure of a transport stream received from outside by a recorder is substantially maintained and written to a recording medium. Also, when there is no particular need to be aware of which playback unit is VOBU or SOBU, it is called SOBU. These usages are for convenience. The invention is not limited by the above definition.

  In principle, the SOBU includes from the V_TSP including the sequence header of the video and the PES header immediately before it to the previous V_TSP including the next sequence header and the immediately preceding PES header. However, the head SOBU exceptionally includes PAT_TSP at the head. This is because in the second embodiment, recording starts from PAT_TSP. Further, with such a configuration, odd data is included between V_TSP and PAT_TSP including the first sequence header. Each SOBU may include a plurality of GOPs.

  In FIG. 8, the position of PAT_TSP immediately before the last PMT_TSP in the first SOBU is assumed to be Mth from the end of the SOBU. The second SOBU includes a V_TSP including a sequence header and a PES header immediately before the first SOBU, and the position of the PAT_TSP immediately before the last PMT_TSP in the SOBU is the Nth from the end of the SOBU. Shall.

  However, the V_TSP including the sequence header and the immediately preceding PES header does not need to include the PES header and the sequence header from the top of the data area (hereinafter referred to as “payload”). This is because the start position of the sequence header of the transport stream input from the outside cannot be specified.

  In an extreme case, for example, a sequence header may be arranged across two V_TSPs. In this case, it is assumed that the V_TSP including the first byte (0x00) in the 4-byte sequence header code (0x000001B3) arranged at the head of the sequence header is the first V_TSP in the SOBU.

  FIG. 9 is a data structure diagram of the management file recorded by the recorder 300. As shown in FIG. 9, the management file includes a TMAP_GI table, a plurality of TM_ENT tables (TM_ENTs), and a plurality of SOBU_ENT tables (SOBU_ENTs). These three tables set the beginning of the file as time 0 (zero), and hold the relationship between the time elapsed from that time and the recording position of the transport packet corresponding to that time.

  First, in the TMAP_GI table, the type number is stored as the identifier of the data structure of the management file in the TMAP type. The number of TM_ENT tables is stored as the number of time entries, and the number of SOBU_ENT tables is stored as the number of SOBU entries. In addition, the head time offset stores how much time has elapsed from the first video frame in the file as the value referred to by the first TM_ENT table as a value represented by the number of fields.

  Next, in the SOBU_ENT table, the data size of the I picture at the head of the SOBU is set in the I-picture data size field. This data size is described using the number of transport packets. Also, the time length required to display SOBU is set in the field number SOBU time length field. The SOBU data size is set in the SOBU data size field in units of the number of transport packets. The above-described configuration approximates conventionally known time map information.

  Further, the position of the PAT_TSP input in the past closest to the last PMT_TSP in the previous SOBU is set in the PAT / PMT pointer field as the number of packets from the end of the previous SOBU. Furthermore, the difference in arrival time of the leading packets of each SOBU among the transport packets constituting two consecutive SOBUs is set in the TSP arrival time field using a counter value by a 27 MHz clock.

  Furthermore, when the time length information in the TSP arrival time field and the time length information in the SOBU time length field are compared after aligning the units, if the time length information differs by 1.5 times or more (or more than 1.5 times), the time The long valid flag field is set to “0”, and when it is less than 1.5 times (or 1.5 times or less), the time length valid flag field is set to “1”. When the time length valid flag is “1”, the value of the SOBU time length field is valid, and when it is “0”, the TSP arrival time field is valid.

  Also, the TM_ENT table stores the position on the recording file with respect to the reference time at intervals of 10 seconds. In other words, the SOBU Entry Index stores the serial number of the SOBU_ENT table corresponding to the SOBU corresponding to the reference time at intervals of 10 seconds. In the time difference, a value representing the time difference between the video frame corresponding to the reference time at intervals of 10 seconds and the head frame of the SOBU referred to by the SOBU Entry Index in units of the number of fields is stored.

  Further, regarding the PAT / PMT pointer, in the case of the recording file shown in FIG. 8, the PAT / PMT pointer of the SOBU_ENT table corresponding to the first, second, and third SOBUs is' 0. (Zero) ',' M ', and' N 'are stored.

  At the time of recording, a transport file input via the 1394 interface unit 301 is recorded to create a recording file, and at the same time, a management file is also created. However, TM_ENT and TMAP_GI are created with reference to SOBU_ENT after the creation of the recording file and SOBU_ENT is completed. At this time, if the time length valid flag is “0”, TM_ENT is generated by referring to the TSP arrival time field and regarding the time length of the corresponding SOBU.

  At the time of reproduction, the management file is read in advance, and the SOBU_ENT table of the SOBU corresponding to the designated reproduction start time is detected with reference to the TM_ENT table. Further, referring to the PAT / PMT pointer in the SOBU_ENT, the transport packet on the disk is read from the position, and the necessary transport packet is output to the outside.

  With the above configuration, data after SOBU corresponding to the designated playback start time can be output in a form including an appropriate PAT and PMT. More specifically, even when the head of a specific SOBU is designated as the playback start time, all data necessary for playback after SOBU can be output without being lost. This makes it possible to output to an external device such as a DTV or STB connected to the 1394 interface unit 301 in a reproducible form at any timing as long as the time is specified in SOBU units. .

  Further, when detecting the head of SOBU, V_TSP including the fourth byte of the sequence header code may be detected, and management data may be created with the V_TSP as the head of SOBU. This method can detect the V_TSP including the first byte of the PES header immediately before the sequence header code, and can simplify the detection process as compared with the case where management data is created using the V_TSP as the head of SOBU. This is because if the sequence header or the immediately preceding PES header spans two V_TSPs, the SOBU head position needs to be calculated retroactively to the previous V_TSP after detecting the fourth byte of the sequence header. Because there is. At this time, since the number of transport packets sandwiched between the two V_TSPs is not constant, it is necessary to calculate the number of sandwiched packets every time. Compared to this, the number of sandwiched in the method of the present embodiment is 0 (zero), and there is no need to calculate every time.

  When V_TSP including the fourth byte is the first V_TSP in SOBU, V_TSP including the first byte of the sequence header existing between PAT_TSP pointed to by the PAT / PMT pointer and the SOBU head is also transmitted during playback. There is a need to. Alternatively, it is necessary to newly generate and insert V_TSP including the first byte of the sequence header. Or, if the beginning of the payload is 0xB3 in the MPEG decoder on the receiving side, it is necessary to perform reproduction by regarding it as a sequence start code.

  In addition, by providing the TSP arrival time and time length valid flag, even when the input transport stream is for special playback, the time management in units of less than 1 second by SOBU and the interval of 10 seconds by TM_ENT Time management can also hold an appropriate time interval. As a transport stream for special playback, for example, a transport stream for slow playback having a display speed of about 5 frames per second may be recorded. At this time, each picture is input in order as a transport stream such as IBBPBB. In this case, the number of frames in the SOBU is '5', that is, about 1/3 second, but the TSP arrival time is 1 second. Even for such an input, it can be managed as an SOBU of one second equal to the display time length.

  On the other hand, there may be a transport stream for high-speed playback having a display speed of about 5 frames per second. In this case, the I-pictures are sequentially input as the transport stream IIII. Even for such an input, it can be managed as an SOBU of one second equal to the display time.

  In this embodiment, the pointer to the PAT / PMT input in the past in the past from the beginning of the SOBU at the time of recording is registered in SOBU_ENT. However, the pointer to the PAT and PMT immediately after the SOBU is registered. It may be stored. However, in this case, at the time of playback, a transport packet obtained by subtracting the counter value of the continuity counter (Continuity Counter) of the PAT and PMT referred to by the PAT / PMT pointer by “1” is output prior to SOBU. There is a need to. Furthermore, when a program clock reference (PCR) field is included in a transport packet including PAT or PMT, it is necessary to correct this value so that the PCR value is reduced by the time to be output in advance. When PCR is included, it is desirable to send a transport packet including PCR separately.

  In the present embodiment, the PAT / PMT pointer in the SOBU_ENT table is referred to at the time of reproduction. At that time, the data immediately before the SOBU is read by a predetermined amount, searched in the direction of the transport packet input in the past from the head of the SOBU, and the first detected PMT_TSP and subsequently detected PAT_TSP are output before the SOBU output do it. In particular, in the case of a transport stream compliant with the digital broadcasting standard, it is possible that the insertion frequency of PAT_TSP and PMT_TSP is defined. Therefore, if a predetermined amount corresponding to this insertion frequency is read, PAT_TSP and PMT_TSP must be read. Will be included. For example, in the case where the frequency of 100 msec or less exists in a 15 Mbps stream, the predetermined amount is 187.5 kilobytes. In this case, however, it goes without saying that an extra packet search processing time is required.

  Furthermore, in this embodiment, the PAT / PMT pointer in the SOBU_ENT table is referred to during playback. However, a predetermined amount of data after the beginning of the SOBU is read without reference, and the necessary transport is read from the data. By searching for packets, the PAT_TSP closest to the beginning of the SOBU, the PMT_TSP closest to the beginning of the SOBU, and the transport packet including the PCR closest to the beginning of the SOBU are extracted, and the internal data is changed to change the SOBU It may be output before. In particular, in the case of a transport stream compliant with the digital broadcasting standard, it is possible that the insertion frequency of PAT_TSP and PMT_TSP is defined. Will be included. For example, in the case where there is a frequency of 100 msec in a 15 Mbps stream, the predetermined amount is 187.5 kilobytes. In this case, however, it goes without saying that extra packet search processing time is required.

  In this case as well, the transport packet obtained by subtracting the continuity counter (Continuity Counter) of the transport packet including PAT_TSP, PMT_TSP, and PCR by “1” needs to be output prior to SOBU. Furthermore, when a program clock reference (PCR) field is included in a transport packet including PAT or PMT, it is necessary to correct this value so that the PCR value is reduced by the time to be output in advance. In addition, it is necessary to update the transport packet including the PCR so that the adaptation field is expanded to eliminate the payload portion.

  A management file similar to the management file of this embodiment may be recorded by the method shown in the first embodiment. In the present embodiment, the management file is recorded separately. However, the management file is recorded in a transport packet, for example, in the form of a private PES stream divided into transport packets at the end of the recording file. It may be.

  Further, in the present embodiment, the PAT / PMT pointer is determined between the PAT_TSP input in the past closest to the past and the PUT_TSP input in the past closest to the past from the SOBU and the head of the SOBU. Although it is assumed that the data size, the transport packet including the PCR inputted in the past in the past from the SOBU is further traced back in the past in the past in the past in the PMT_TSP entered in the nearest past. It is even better if the data size is between the closest PAT_TSP input in the past and the SOBU.

  In this case, only the transport packet including PAT_TSP, PMT_TSP, and PCR sandwiched between the SOBU head and the PAT / PMT pointer is output before the SOBU is transmitted during reproduction. As a result, the MPEG decoder on the receiving side of the transport stream obtains the PCR value before referring to the PTS or DTS described in the PES header in the first V_TSP of SOBU. The referenced operation can be performed.

  On the other hand, in the present embodiment, the operation referring to the PTS or DTS cannot be performed, and the elapsed time from the input time of the first V_TSP of SOBU is referred to the value of the vbv_delay field with reference to the vbv_delay field in the video data. Timing control such as starting decoding of video when they match is required.

  Furthermore, in this embodiment, the PAT / PMT pointer has a data size between the SOBU head and the PAT_TSP input in the past closest to the past to the PMT_TSP input in the past closest to the past from the SOBU. It is supposed to be. However, it may indicate a position separated by a predetermined number before the SOBU head (for example, 100 transport packets before, etc.). In this case, from the insertion frequency of PAT / PMT / PCR, it is desirable that the number is always included.

  In this embodiment, the PAT / PMT pointer has a data size between the SOBU head and the PAT_TSP input in the past closest to the past with respect to the PMT_TSP input in the past closest to the past from the SOBU. However, the position of the transport packet (for example, 300 msec before) input in the past by a predetermined time from the head of SOBU may be indicated.

  For example, before 300 msec, in the case of Japanese digital broadcasting and European digital broadcasting (DVB), there is a high possibility that PAT_TSP, subsequent PMT_TSP, and subsequent PCR are included in this order. This is because there is an operation rule that the transmission frequency of PAT_TSP and PMT_TSP is 100 msec or more.

  Further, the position of the transport packet input in the past for a predetermined time may be searched for at the time of reproduction without pointing to the position with the PAT / PMT pointer. However, in this case, it is assumed that the arrival timing is separately recorded for each transport packet.

  If the SOBU has a trick mode flag used in special playback in the PES header, the time length valid flag may be set to '0'.

  In this embodiment, the PAT / PMT pointer is recorded as management information. However, the transport packet including the actual PAT and the transport packet including the PMT are grouped into SOBU groups that ensure the continuity of the MPEG standard. Each unit may be recorded separately from the management information for each SOBU group. Moreover, you may record for every recording file. However, when recording is performed for each recording file, when a transport packet including DIT is detected, it is necessary to divide the recording file before and after detection. Further, only the PAT and PMT tables may be included without including the transport packet header.

  Further, when recording is performed for each recording file, the transport packet including PAT and the transport packet including PMT are not recorded as they are, and the correspondence between the types of elementary streams included therein and the PIDs as shown in FIG. The PID of the PMT, the PID storing the PCR, etc. may be summarized and recorded.

  Further, the continuity counter value of the transport packet including the first PAT and PMT in SOBU may be detected and included. FIG. 11 shows an example of such management information for each SOBU.

  In addition, since PAT and PMT usually do not change over a plurality of SOBUs, an identifier for identifying PAT_TSP and PMT_TSP separately recorded as management information for each SOBU group may be recorded for each SOBU group. Good.

  When a specific SOBU designated by the user is used as a playback start point, it is necessary to configure and send separately recorded PAT and PMT as transport packets prior to the SOBU. Furthermore, transport packets including PCR must also be transmitted at a timing between PMT and SOBU.

  At this time, the continuity counter value of the transport packet including the PAT and the transport packet including the PMT is only “1” from the continuity counter value of the first PAT and PMT in the SOBU recorded as the management information. The subtracted value may be used. In this way, the PAT and PMT can be easily created by holding the values of the continuity counters of the first PAT and PMT in the SOBU as management information.

  In this embodiment, V_TSP including the first byte of the sequence start code is arranged at the head of the second and subsequent SOBUs. However, even if another transport packet is recorded at the head of the SOBU. Good. This is because the first V_TSP in the SOBU only needs to include the first byte of the sequence start code. As an example of recording another transport packet, a predetermined number of pieces of arrival timing information for each transport packet are stored together.

  The recorder of this embodiment does not have an MPEG decoder, but an MPEG decoder may be provided. As a result, playback and display can be performed by processing inside the recorder.

  Furthermore, in this embodiment, V_TSP including a sequence header is assumed to include a PES header, but it is not always necessary to include a PES header. This is because, according to the MPEG standard, the PES header of video is allowed only once at the beginning of the stream.

  In this embodiment, the transmission timing of the transport packet including PAT_TSP, PMT_TSP, and PCR transmitted before the SOBU head V_TSP is not mentioned, but the time interval is considered in consideration of the processing speed on the receiving side. You may make it send out with a gap.

  Furthermore, in the present embodiment, the first SOBU is recorded from the PAT_TSP, but recording may be started from other types of transport packets. For example, all transport packets until the first PAT_TSP arrives may be recorded.

  In this embodiment, the SOBU time length and the TSP arrival time are recorded for each SOBU. However, only the TSP arrival time may be recorded. In this case, the process of detecting the sequence header and the process of counting the number of fields are not required, so that the management information generating unit can be simplified.

(Embodiment 3)
Hereinafter, an apparatus according to Embodiment 3 of the present invention will be described with reference to the drawings. While the first and second embodiments described above relate to recording / playback of a video file, the present embodiment relates to recording / playback of an audio file.

  First, the configuration of a recorder that records and reproduces an audio file according to the present embodiment is the same as that of the recorder 200 shown in FIG. Since the configuration of the recorder 200 has been described in the first embodiment, a detailed description thereof will be omitted below.

  FIG. 12 is a data structure diagram of an audio file. As shown in FIG. 12, the audio file is composed of a header having a fixed data size (for example, about 2 kilobytes) and an audio object (hereinafter referred to as “AOB”), and the AOB includes a plurality of audio object units (hereinafter referred to as “AOB”). , “AOBU”).

  The header stores management information related to the audio file. Each AOBU includes a predetermined number (for example, four) of audio frames, and includes PAT_TSP and PMT_TSP at the head. One audio frame is composed of a predetermined number (for example, three) of transport packets A_TSP. In FIG. 12, it is assumed that each audio frame has a fixed bit rate.

  By adopting the data structure of the audio file shown in FIG. 12, PAT_TSP and PMT_TSP are surely included when reproduction is started from an intermediate AOBU. Therefore, regardless of the AOBU of the audio file, it is possible to reliably reproduce from the first audio frame.

  Further, as shown in the present embodiment, if the number of audio frames included in the AOBU is 4, the PAT / PMT insertion timing can be set within 100 msec. By doing so, it can be kept within 100 msec determined by the 1394 transmission standard corresponding to Japanese BS digital broadcasting. Specifically, this is the case where ISO / IEC 13818-7 Advanced Audio Coding compression is used with 48 KHz sampling and 1024 samples.

  In addition, as shown in FIG. 12, by fixing the PAT_TSP and PMT_TSP insertion timing, the number of audio frames constituting the AOBU, and the number of transport packets constituting the audio frame, playback is started from an AOBU in the middle by specifying the time. In this case, since the position of the AOBU corresponding to the time can be obtained only by simple calculation, it is not necessary to record a table corresponding to the TM_ENT table or the SOBU_ENT table as in the second embodiment. As necessary information, the frame time of one voice frame, the number of transport packets constituting one voice frame, and the number of voice frames constituting one AOBU are sufficient. Such information may be recorded, for example, in the header portion of the audio file.

  In this embodiment, it is described that the insertion timing of PAT_TSP and PMT_TSP, the number of audio frames constituting the AOBU, and the number of transport packets constituting the audio frame are fixed, but the audio frames constituting the AOBU The number and the number of transport packets constituting the audio frame may be a predetermined number or less. However, in this case, it is better to record a table corresponding to the TM_ENT table or SOBU_ENT table as in the second embodiment as a file footer or another management file.

  In the first and third embodiments, PAT_TSP and PMT_TSP are arranged at the head of VOBU or AOBU. However, another transport packet is recorded immediately before PAT_TSP and PMT_TSP, and then PAT_TSP and PMT_TSP are recorded. Also good. This is because PAT_TSP and PMT_TSP need only be recorded before the first V_TSP or A_TSP in VOBU or AOBU. As an example of recording another transport packet, a predetermined number of pieces of arrival timing information for each transport packet are stored together.

  In the first A_TSP in the AOBU, it is desirable that the PCR is included in the transport packet header. This is because PAT_TSP, PMT_TSP, and PCR can be sent before audio data in A_TSP.

(Embodiment 4)
FIG. 13 shows a configuration of the player 400 according to the present embodiment. The player 400 is connected to, for example, a 1394 interface unit of the recorder 200 (FIG. 5) via a 1394 cable.

  A PAT / PMT / PCR analysis unit 402 extracts PAT, PMT, and PCR fields from the transport stream input from the 1394 interface unit 401. After the analysis, the analysis unit 402 sends the video and audio PID and PCR necessary for decoding to the reproduction unit 403. As soon as the playback unit 403 receives the video PID, the audio PID, and the PCR, the playback unit 403 starts storing the input transport stream. Then, the transport stream decoding process is started using the received information. The playback unit 403 passes the decoded video signal and audio signal to the display unit 404.

  At the start of the decoding process, if a transport packet including a PCR is a trigger (trigger) for accumulation and decoding, it is assumed that the transport packet after the transport packet itself is to be accumulated and decoded. Thereafter, each time the PAT / PMT / PCR analysis unit 402 detects PAT / PMT / PCR, it passes the PID and PCR to the reproduction unit 403.

  With the above configuration, the transport stream output from the 1394 interface unit of the recorder according to the first to third embodiments is received by the 1394 interface unit 401 of the player shown in FIG. can do.

  The processing time required for the PAT / PMT / PCR analysis process varies depending on each device. For example, there are models with a processing time of 0.5 seconds and models with a processing time of 1.0 seconds. However, if the sending side device according to the first, second, and third embodiments outputs a unified transport stream without depending on these processing times, the receiving side player according to the fourth embodiment can perform the PAT / PMT / PCR. As soon as the analysis process is completed, playback of the video or the like can be started.

  According to this method, the transmission side apparatus estimates the maximum value of the analysis processing time, sends only the transport packet including PAT / PMT / PCR, and outputs the transport stream only during the maximum value of the analysis processing time. The delay time until video and audio output can be shortened compared to the method of stopping the transmission. Furthermore, even when a specific scene is selected and a plurality of selected scenes are continuously reproduced, the scene switching time can be shortened.

  Further, when such scene switching occurs, the timing of scene switching may be notified to the device in advance. For example, the notification content may be expressed as an STC (system time clock) value used in the previous scene to notify the timing at which the first frame of the next scene is reproduced. As a notification method, for example, an AVC command in 1394 may be used. Moreover, you may notify by a special transport packet.

  Further, information regarding the PAT / PMT of the next scene may be notified to the device slightly before the switching point of the transport stream. The PAT and PMT version number (version_number) field and the current_next_identifier (current_next_indicator) field may be used for notification.

  Further, at the scene switching point, the transmission side may check the switching timing in the transport stream by inserting the transport packet including the DIT (Discontinuity Information Table) by monitoring the input stream.

  In the present embodiment, it is assumed that the PAT / PMT / PCR analysis unit 402 inputs in the order of PAT, PMT, and PCR. However, even if input in a different order, the PAT, PMT, and Information such as video and audio PID and PCR included in the PCR may be passed to the reproduction unit 403.

  By assuming such processing, in the third embodiment, transport packets including PAT_TSP, PMT_TSP, and PCR among transport packets input in the past within 100 msec from the transport packet including the sequence header are used. It may be extracted and sent out in the same order. At this time, whatever the order of transmission of transport packets including PAT_TSP, PMT_TSP, and PCR is, the receiving side interprets the transport packets including PAT_TSP, PMT_TSP, and PCR in the same order. This eliminates the need to extract these transport packets from the transport stream input before 300 msec.

  If such processing is assumed, in the first and second embodiments, the order of sending and recording of transport packets including PAT_TSP, PMT_TSP, and PCR may not be maintained. In addition, the PAT / PMT pointer in the third embodiment may refer to the position information of the transport packet that has been input most recently among transport packets including PAT_TSP, PMT_TSP, or PCR. This is because these three types of transport packets exist from that position to the beginning of the SOBU.

(Embodiment 5)
FIG. 14 shows a data structure of management information of a transport stream used for multi-view broadcasting of ARIB (Association of Radio Industries Businesses) standard. In multi-view broadcasting, a maximum of three programs are multiplexed in one transport stream. In the case of such a transport stream, an SOBU_ENT table and a TM_ENT table are created for each program.

  Then, the SOBU_ENT tables of program 1, program 2, and program 3 whose display times are close to each other are repeatedly recorded in order as 1, 2, 3, 1, 2, 3,. The TM_ENT table is recorded in the same manner. It is assumed that each SOBU_ENT table and TM_ENT table have the same data structure as in the second embodiment. Also, it is assumed that the number of multiplexed programs is recorded in TMAP_GI. Other configurations are the same as those of the second embodiment.

  With the above configuration, even in multi-view broadcasting, it is possible to transmit a transport stream including PAT, PMT, and PCR from an arbitrary sequence header in an arbitrary program.

  Note that the SOBU_ENT table corresponding to the program 2 and the program 3 may be recorded in series after the SOBU_ENT table of the program 1. Similarly, TM_ENT tables corresponding to program 2 and program 3 may be recorded in series after the TM_ENT table of program 1.

(Embodiment 6)
Hereinafter, two types of management files of the data stream will be described. Thereafter, the management file according to the present embodiment, which can be easily converted into any management file, will be described. In addition, the apparatus according to the present embodiment for generating such a management file will be described.

  In the embodiment described below, a playback unit of a video stream is referred to as SOBU even if the recording apparatus encodes itself to generate a video stream. Note that for convenience of explanation, SOBU and VOBU are not distinguished.

  FIG. 15 shows the data structure of the first management file 1.

  A recording device such as an optical disk recorder generates one or more SOBUs and records them as a stream file. Thereafter, a management file storing management information regarding the stream file is recorded. The stream file and the management file are arranged in the same directory on the phase change optical disk 131. Also, the file names are different only in the file extension, and the same name is assigned except for the file extension. For example, MOVIE001. MPG (stream file) and MOVIE001. Like a CTL (management file), a 1: 1 correspondence is maintained and recorded. The management information of the management file is used, for example, for reproducing video and audio from an arbitrary location in the stream file. At the time of playback, the device derives the storage destination address of the SOBU to be played back from the management file based on the elapsed time from the beginning of the playback start point designated by the user, and the stream file stored at that address. Play video etc. using data.

  The management file 1 shown in FIG. 15 includes a TMAP_GI table 2 and a plurality of SOBU_ENT tables (SOBU_ENTs) 3.

  First, in the TMAP_GI table 2, the type number is stored as the identifier of the data structure of the management file in the TMAP type. The number of SOBU_ENT tables is stored in the number of SOBU entries.

  Next, the SOBU_ENT table 3 will be described. First, the data size of the I picture recorded at the head of the SOBU is set in the “I-picture data size” field 4. The set value is the number from the transport packet storing the head of the I picture data to the transport packet storing the end of the data. Note that, for example, transport packet packets storing audio data may be interleaved between the transport packets. At this time, a value including the number of transport packets that do not store I picture data is set.

  The total playback time of pictures included in each SOBU is set in the SOBU time length field 5. The set value is the number of video fields when the SOBU is played back. The data size of each SOBU is set in the SOBU data size field 6. The set value is the number of transport packets included in the SOBU. Since the data length of the transport packet is fixed at 188 bytes, the data length of the SOBU can be easily specified by describing the number of packets.

  In addition, when a transport stream input via the 1394 interface unit 640 is recorded, a stream file is generated and a management file is generated at the same time.

  FIG. 16 shows the data structure of the second management file 11. The management file 11 is employed in, for example, a Blu-ray disc.

  The management file 11 includes a TMAP_GI table 12 and a plurality of SOBU_ENT tables (SOBU_ENTs) 13.

  First, in the TMAP_GI table 12, a type number is stored as an identifier of the data structure of the management file in the TMAP type. The number of SOBU_ENT tables is stored in the number of SOBU entries.

  Next, in the SOBU_ENT table 13, an “I-picture data size” field 14, a PTS difference field 15, and an SOBU data size field 16 are provided. In the fields 14 and 16, information equivalent to the fields 4 and 6 having the same name in the management file 1 is described, respectively.

  On the other hand, the PTS difference field 15 is set with the PTS difference between the I pictures recorded at the head of two adjacent SOBUs in the data stream.

  Hereinafter, the above-described PTS difference will be described in more detail with reference to FIGS. 17 (a) and 17 (b). FIG. 17A shows the relationship between the SOBU, the definition of the PTS difference of the SOBU leading I picture, and the SOBU time length. Symbols “B”, “I”, and “P” indicate a B picture, an I picture, and a P picture in the MPEG standard, respectively. Each picture is illustrated in the order in which it is played.

  The display order of each picture in each SOBU shown in FIG. 17A is BBIBBP, IBBP, and BBI. The SOBU time length in the figure indicates the playback time length of the video frame included in each SOBU, and is defined with the number of video fields as a unit. Also, the PTS difference between I pictures is defined by the time difference between the display timing (PTS) of the I frame that is the first frame of a certain SOBU and the display timing (PTS) of the I frame that is the first frame of the immediately following SOBU. However, in the present embodiment, it is assumed that the number of video fields is set instead of the actually added PTS value.

  On the other hand, FIG. 17B shows the order in which the data of each picture is arranged in the transport stream. The data of each picture is written on the recording medium in this order. IBBPBB, IPBB, IBB... Shown in FIG. 17 (b) are the IBBPBB, IPBB, and IBB compressed video frames in SOBU # i, SOBU # (i + 1), SOBU # (i + 2). Indicates that a picture is included. In FIGS. 17A and 17B, the number of video frames constituting one SOBU is an example. More pictures may be included.

  In this specification, it is assumed that a management file having the data structure shown in FIG. 15 is recorded on the HDD and the phase change optical disk, and a management file having the data structure shown in FIG. 16 is recorded on the memory card. On the other hand, the data structure of the stream file is the same regardless of the type of recording medium. That is, it is assumed that the stream file stores the transport stream in both the HDD and the phase change optical disk. The data structure of the stream file and the management file may be defined by the recording medium standard or may be arbitrarily determined.

  In the present embodiment, a new management file that can be easily converted into either the management file 1 shown in FIG. 15 or the management file 11 shown in FIG. 16 is defined. Such a management file is generated together with the generation of the stream file. By using the management file according to the present embodiment, when the data stream is transferred from the recorder to another device, the management file may be converted into a management file suitable for the transfer destination device. Since it is not necessary to generate the management file by analyzing the entire data stream, the transfer of the data stream and the management file is completed at high speed.

  The configuration and operation of the recorder that generates the management file according to the present embodiment and the data structure of the management file will be described below.

  FIG. 18 shows a configuration of main functional blocks of the HDD built-in optical disc recorder 500 according to the present embodiment. The HDD built-in optical disc recorder 500 (hereinafter referred to as “recorder 500”) encodes a video signal and an audio signal by the recording / reproducing unit 540 to generate a transport stream and its management information. The transport stream and management information are recorded as stream files and management files on each recording medium via the HDD (hard disk drive) unit 520 and / or the optical disc drive unit 530. This management file includes an SOBU time length field as shown in FIG. 15, but is different from the data structure shown in FIG. A detailed data structure will be described later with reference to FIG.

  FIG. 19 shows a detailed configuration of the recording / playback unit 540 of the recorder 500. When the video signal and the audio signal are received and encoded (that is, self-encoded), the recording process of the stream of the recorder 200 shown in FIG. 5 and the recording of the management information including the SOBU time length shown in FIG. Basically the same processing as the processing is performed.

  The format conversion unit 510 of the recording / playback unit 540 can read the stream file recorded on the HDD or the phase change optical disk and write it to the memory card via the memory card drive unit 550. Further, the format conversion unit 510 can read a management file recorded on the HDD or the phase change optical disc, convert the format, and write it to the memory card of the memory card drive unit 550.

  Further, the recording / reproducing unit 540 can receive and record (that is, import) a transport stream from another device via the 1394 interface. The recording / playback unit 540 can send a transport stream to another device via the 1394 interface and record (i.e., export) the transport stream to that device. These import / export processes are the same as the stream import / export processes in the second embodiment. Further, the process of recording the management information as a management file is performed in the same manner as the management information recording process shown in FIG.

  FIG. 20 shows the data structure of the management file 21 according to this embodiment. The management file 21 includes a TMAP_GI table 22 and a plurality of SOBU_ENT tables (SOBU_ENTs) 23.

  The management file 21 is different from the management file 1 shown in FIG. 15 in that the SOBU_ENT table 23 of the management file 21 newly has a preceding display number field 27. In the preceding display number field 27, information on a video frame to be displayed before the first I frame in the SOBU is described. In other fields, information equivalent to the corresponding fields of the management file 1 shown in FIG. 15 is described.

  A corresponding SOBU time length field 25 and SOBU data size (or SOBU recording position) field 26 are stored in each SOBU_ENT table 23. These are positioned as information unique to each SOBU.

  Hereinafter, the meaning indicated by the information described in the preceding display number field will be described with reference to FIGS. 21 (a) and 21 (b).

  FIGS. 21A and 21B schematically show the definition of the preceding display number recorded in the management file.

  FIG. 21B shows the order in which the data of each frame is recorded. SOBU # i, SOBU # (i + 1), SOBU # (i + 2) in the transport stream are recorded with picture data in the order of IBBPB... B, IPBBPB... B, IBI. Yes.

  On the other hand, FIG. 21A shows the order in which the frames are displayed. In this example, the display order is BBIBB ... P, IBBPBB ... P, BIB ... for each SOBU. In SOBU # i, according to FIG. 21A, the two B frames before the I frame are displayed before the I frame. Therefore, the preceding display number is 2 frames (4 fields).

  In the subsequent SOBU # (i + 1), there is no frame displayed before the first I frame. Therefore, the preceding display number is 0 frame (0 field).

  In SOBU # (i + 2), only one B frame is displayed before the first I frame. Therefore, the preceding display number is 1 frame (2 fields).

  After receiving the video signal, the recorder 500 performs an encoding process by itself to generate a transport stream. Therefore, the time length of the frame displayed before the first I frame in each SOBU can be specified each time each SOBU is generated.

  The time length of the frame displayed before the first I frame in each SOBU specified as described above is described in the preceding display number field of the SOBU_ENT table in units of video fields. In a video system in which 30 frame images are displayed per second, one field image corresponds to a time length of 1/60 seconds. Therefore, when two frame images are displayed before the I frame, “4” is described in the preceding display number field.

  The reason why the preceding display number is described using the number of video fields is as follows. For example, when a film material of substantially 24 frames is recorded with 3: 2 pull-down conversion to 60 fields per second, one recorded video frame may have a playback time length of 2 fields or 3 fields. Therefore, it is preferable to use the field as a unit. Needless to say, if such a case is not assumed, the unit may be the number of video frames.

  FIG. 22 shows a processing procedure for the recorder 500 to generate the management file 21. In order to simplify the description, the following description will focus on processing related to video signals.

  In step S211, the MPEG encoder 670 performs an encoding process for each video frame based on the video signal. In step S212, the MPEG encoder 670 specifies a video frame to be displayed before the first SOBU I picture (I frame). Specifically, the MPEG encoder 670 may specify which video frame is encoded as the first I frame from the video frames input after the last video frame of the previous SOBU. Thereby, a video frame input before the video frame (that is, a B frame displayed before the I frame) can be specified. The MPEG encoder 670 outputs information regarding the number of video frames displayed before the I frame. Note that instead of the information regarding the number of video frames, it may be notified individually that video frames have been generated.

  At this time, the MPEG encoder 670 also outputs information on the data size of the I picture, the SOBU time length, and the SOBU data size. Since the MPEG encoder 670 performs encoding processing and packet arrangement processing, all these pieces of information are specified for each SOBU generated.

  In step S213, the management information generation unit 642 calculates the display time corresponding to the specified number of video frames as the number of fields. In step S214, the management information generation unit 642 describes the calculated field number value in the preceding display number field 27 in the SOBU_ENT table 23. The management information generating unit 642 also writes information on the data size of the I picture, the SOBU time length, and the SOBU data size in the table every time an SOBU is generated.

  As a result of the above processing, each SOBU_ENT table (SOBU_ENTs) 23 is generated. When all SOBUs are acquired, the contents of the TMAP_GI table 22 are also determined.

  Thereafter, the recording control unit 661 receives the management information and transmits the management information to the HDD unit 520 and / or the optical disc drive unit 530 so as to be written on the HDD and / or the phase change optical disc. As a result, the management file 21 is obtained.

  Since the HDD is built in the recorder 500, the data structure of the data to be written does not need to be considered for matching with the external device. Therefore, no problem occurs even if the data structure of the management file 21 according to the present embodiment is written. When outputting to an external device that does not support the data structure of the management file 21, it is converted into the management file 1 shown in FIG. 15 or the management file 11 shown in FIG. 16 by the conversion process described with reference to FIG. That's fine.

  On the other hand, since the phase change optical disk is removable, if it is loaded in a device that does not support the management file 21, it may not be processed and an error may occur. However, there is no problem in recording the management file 21 on the phase change optical disk depending on circumstances such as the standardization of each data structure of the management file 21.

  The recorder 500 according to the present embodiment can reproduce video and audio using the management file 21. For example, referring to the management file 21, it is possible to easily realize the process of reproducing the 10th and subsequent seconds from the head of the designated stream.

  Specifically, it is as follows. First, the management information generation unit 642 adds the value of the SOBU time length field 25 until it exceeds 10 seconds. When it exceeds 10 seconds, it can be said that the 10th second video frame data is stored in the SOBU corresponding to the last added SOBU time length. When the management information generation unit 642 identifies the SOBU, the playback unit 621 reads the SOBU based on an instruction from the playback control unit 662 and sends the SOBU to the MPEG decoder 671. The MPEG decoder 671 decodes the SOBU, and outputs the video frame after the 10th second from the beginning of the stream. As a result, playback starts from the video at the designated time. Note that the above-described processing is performed not only at the time of reproduction but also when outputting video via the 1394 interface.

  Next, a process in which the recorder 500 converts the management file 21 into the management file 1 shown in FIG. 15 or the management file 11 shown in FIG. Hereinafter, the conversion process will be described on the assumption that the stream file and the management file recorded on the HDD of the recorder 500 are transferred to another recording medium.

  FIG. 23 shows the procedure of management file conversion processing.

  First, in step S221, the recorder 500 receives a transfer instruction from the user via a remote controller or a button (both not shown) of the recorder 500 main body. At this time, the transfer destination recording medium and its recording device are specified together with the transfer instruction. In step S222, the playback control unit 662 of the recorder 500 first instructs the stream file to be read from the HDD. Then, the stream file read by the playback unit 621 is transferred to, for example, the optical disc drive unit 530 or the memory card drive unit 550, and written to the specified recording medium. As described above, the transport stream is transferred as it is regardless of the type of the recording medium.

  In the next step S223 and thereafter, management information conversion processing is performed. First, in step S223, the format conversion unit 510 determines whether or not the transfer destination is a memory card. The reason is that if it is a memory card, it is necessary to convert it to the management file 11 of FIG. 16, and if it is a recording medium (for example, an optical disk) other than the memory card, it is necessary to convert it to the management file 1 of FIG. is there. If the transfer destination is a memory card, the process proceeds to step S224, and if the transfer destination is a recording medium other than the memory card, the process proceeds to step S226.

  The “memory card” includes not only a memory card loaded in the recorder 500 but also a memory card of an external device connected to the recorder 500. Further, the “recording medium other than the memory card” includes the optical disk of the recorder 500 and the optical disk or HDD of an external device connected to the recorder 500.

  In step S224, the playback unit 621 reads the management file 21 based on an instruction from the playback control unit 662. The format conversion unit 510 receives the management file 21 and calculates the PTS difference of the I picture with reference to the preceding display number field 27 of each table.

  This PTS difference can be calculated by the following equation 1 using the relationship between the SOBU time length and the preceding display number in the SOBU_ENT table shown in FIG.

(Formula 1)
PTS difference of I picture of SOBU_ENT table #j (FIG. 16) = SOBU time length of SOBU_ENT table #j (FIG. 20) -Previous display number of SOBU_ENT table #j (FIG. 20) + SOBU_ENT table # (j + 1) (FIG. 20) Preceding display number of

  In the next step S225, the management information generation unit 642 replaces the value of the SOBU time length field 25 of each table 23 with each calculated PTS difference value. Thereby, the PTS difference field 15 of FIG. 16 is generated.

  In step S226, the format conversion unit 510 deletes the preceding display number field 27 of each table 23. By the above processing, the management file 11 shown in FIG. 16 can be obtained from the management file 21 shown in FIG.

  If it is determined in step S223 that the transfer destination is other than a memory card, the management file 1 is obtained simply by deleting the preceding display number field 27 of the management file 21. This is apparent from the relationship between the management file 21 in FIG. 20 and the management file 1 in FIG.

  Fields other than those mentioned in the above process need not be converted. The obtained management file is transferred to the specified recording medium and recorded.

  In the above-described processing, the conversion processing is executed when a stream transfer instruction is received. However, the recorder 500 may execute the above-described conversion process at an arbitrary timing. For example, the management file 1 and / or the management file 11 may be stored in advance when the transfer instruction is not received, so that the transfer can be started immediately after the transfer instruction is received. In the above conversion process, the stream file is transferred before the management file is converted. However, the stream file may be transferred after the management file is converted, that is, after step S226.

  With the above configuration, when the video stream recorded by the recorder 500 according to the present embodiment and the management information of the stream are exported to another recording medium such as a memory card, all the SOBUs of the recorded video stream are read. Since there is no need to analyze and convert management information, conversion processing can be performed at high speed.

  Note that the management file 21 of this embodiment includes the SOBU time length field 25 in the SOBU_ENT table. However, instead of this field, a PTS difference field between I pictures corresponding to the field 15 in FIG. 15 may be included. When the PTS difference field is provided, the corresponding I picture data size and the PTS difference field are stored in each SOBU_ENT table 23. Each of these is information regarding the I picture of each SOBU.

  Even if the PTS difference field is provided, it is easy to obtain the SOBU time length. In other words, the SOBU time length can be obtained by shifting the first term on the right side of Equation 1 to the left side and the term on the left side to the right side.

  Further, the preceding display number may not be recorded, and the data size of the I picture, the SOBU time length, the SOBU data size, and the PTS difference between the I pictures may be included. Even if these fields are used, the converted management file can be easily obtained.

  When import / export is performed with a device having a 1394 interface, not only the stream but also the management file 21 is transferred, and the management file is further converted into a predetermined format (for example, the management file 1 or the management file 21). Data format). However, it should be noted that the management file needs to be transmitted in the asynchronous communication mode of the 1394 standard.

(Embodiment 7)
In the sixth embodiment, the process of exporting the stream file and management file on the HDD or phase change optical disk to another HDD, phase change optical disk or memory card has been described.

  In the present embodiment, a process for importing a stream file and a management file into an HDD, a phase change optical disk, or a memory card will be described. The data structure of management information used in this processing is different from the data structure in the sixth embodiment. Hereinafter, such processing and data structure will be described along with the operation of the device. Note that the recorder 500 according to the present embodiment can also perform the export process according to the sixth embodiment. Since the processing is the same as the processing described in the sixth embodiment, description thereof is omitted.

  The hardware configuration of the device according to the present embodiment is the same as that of the recorder 500 (FIGS. 18 and 19). Therefore, the description is omitted. Hereinafter, the recorder 500 will be described as a device according to the present embodiment.

  The format conversion unit 510 reads the recorded stream file from the memory card drive unit 550 and writes it to the HDD or the optical disc. Furthermore, the format conversion unit 510 reads the management file written in the memory card, converts the format, and writes it in the HDD or the optical disc. The imported stream file and management information correspond 1: 1.

  FIG. 24 shows the data structure of the management file 31 according to this embodiment.

  The data structure of the management file 31 is different from the data structure of the management file 21 of the sixth embodiment in that, instead of the SOBU time length field 25 in the SOBU_ENT table 23 in FIG. ”Field 37.

  A further difference is that the TMAP_GI table 32 is provided with two flag fields 34 and 35. In the flag field 34, a switching flag indicating which one of the numerical value of the SOBU time length and the numerical value of the PTS difference is written in the field 37 in the SOBU_ENT table 33 is written. The flag field 35 is a point where an validity flag indicating whether or not the preceding display number is recorded in the SOBU_ENT table 33 is recorded. Details of each flag will be described later. Other fields (fields 36, 38, etc.) excluding the above-described differences are the same as the fields having the same names shown in FIG.

  At the time of self-encoding, the management information generating unit 642 of the recording / reproducing unit 540 describes the numerical value of the SOBU time length in the field 37. Then, the preceding display number is specified based on the output of the MPEG encoder 670, and the value is set in the field 39. At this time, the value of the switching flag in the field 34 of TMAP_GI 32 is set to 0. In addition, the validity flag value in the field 35 is set to 1. As a result, a numerical value of the SOBU time length is described in the field 37, and a preceding display number value is described in the field 39.

  FIG. 25 shows the correspondence between the fields of the SOBU_ENT table of the management file when exporting to the memory card and importing from the memory card in the recorder 500 of this embodiment. Among these, at the time of export, the format conversion unit 510 converts the SOBU_ENT table 33 in the management file at the time of self-encoding into the SOBU_ENT table 13. The value of the PTS difference field 15 between I pictures of the management file on the memory card is generated by using the values of both the SOBU time length field 37 and the preceding display number field 39 of the SOBU_ENT table 33.

  At the time of import, the format conversion unit 510 converts the SOBU_ENT table 13 in the management file on the memory card into the SOBU_ENT table 43. The value of the PTS difference field 15 on the memory card is copied to the PTS difference field 44 between the SOBU time length or I picture. However, at this time, the SOBU time length / PTS difference switching flag 34 (FIG. 24) is described by selecting the value 1 indicating that the PTS difference value is described. As the value of the validity flag 35 of the preceding display number, the value 0 indicating invalid is selected and described.

  When the recorder 500 according to the present embodiment reproduces a stream file recorded on the HDD unit or the optical disc unit, it can determine the reproduction start point with reference to the management file for the stream. For example, when starting playback from the start point of the 10th second from the beginning of the stream, it is necessary to specify the playback start point in the stream. The management file stores the SOBU time length or the PTS difference between the leading I pictures of two adjacent SOBUs. The playback control unit 662 can specify the transport packet that is the playback start point regardless of which value is described between the SOBU time length and the PTS difference. Details are as described in connection with the sixth embodiment.

  With the above configuration, the recorder of this embodiment can generate a management file without analyzing a stream when importing a transport stream file and its management file from the outside. Furthermore, when exporting a transport stream file and its management file to the outside, a management file can be generated without analyzing the stream.

  Thus, import / export can be easily realized with another type of recording medium such as a memory card.

  In this embodiment, it is assumed that the SOBU time length and the preceding display number are recorded during self-encoding. However, the PTS difference and the preceding display number may be selected and recorded. At this time, for example, even if the management file corresponding to the export destination device has a data structure that adopts the SOBU time length, the SOBU time length can be easily calculated by the following equation 2.

(Formula 2)
SOBU time length of SOBU_ENT table #j of other management file =
PTS difference of SOBU_ENT table #j at the time of self-encoding + Number of preceding display of SOBU_ENT table #j at the time of self-encoding-Number of preceding display of SOBU_ENT table # (j + 1) at the time of self-encoding

  In the present embodiment, the management information is set by selecting either the SOBU time length or the PTS difference. However, both fields may be provided for each SOBU_ENT table.

  In this embodiment, it is assumed that management information including a PTS difference between I pictures is recorded in the memory card. However, different data structures may be employed depending on the type of memory card. For example, FIG. 26 shows the second correspondence of each field of the SOBU_ENT table of the management file according to this embodiment. Similar to the example of FIG. 25, the management file table 13 of the memory card # 1 is provided with a PTS difference field between I pictures. On the other hand, the SOBU time length field 54 is provided in the table 53 of the memory card # 2.

  The recorder 500 can also import the stream file and management file exported to the memory card # 1 in FIG. 26 into the recorder 500 again, and then export them to the memory card # 2. Since the information on the preceding display number included in the management file before the first export is lost, the management file table 53 does not include the information on the preceding display number after the export to the memory card # 2.

  If the information of the preceding display number is described also in the memory card # 2, the format conversion unit 510 needs to analyze the transport stream and detect the SOBU time length of the management file. Alternatively, after the stream file of the memory card # 1 is once recorded on the hard disk, the transport stream on the hard disk may be decoded and compressed and encoded again. Since this process is equivalent to the self-encoding process, the recorder 500 can generate management information to be described in the management file. Thereafter, the transport stream and management information may be stored in the memory card # 2. In this way, simultaneously with compression and encoding again, each field of the management file is newly generated and stored as management data of the memory card # 2.

  Also, when the stream file and the management file are dubbed from the memory card # 2 to the memory card # 1 via the hard disk 520 of the recorder 500, analysis processing similar to the above processing or compression coding is required again. . When imported from the memory card # 2 to the recorder 500, the memory card # 2 has no preceding display number field. Therefore, in the management file after the import, the value 0 of the validity flag 35 is selected and described so that the preceding display number field 65 is invalidated.

  In the sixth and seventh embodiments, the MPEG encoder generates data in the SOBU data format during self-encoding. However, the VOBU data format mentioned in the first embodiment may be used. That is, like VOBU, the leading packet may start from PAT_TSP and PMT_TSP.

  In the sixth and seventh embodiments, the MPEG system stream is a transport stream, but may be a program stream. At this time, the data size field of the I picture and the data size of the SOBU need to be read as the number of packs, not the number of transport packets.

  In Embodiments 6 and 7, the MPEG system stream is a transport stream, but it may be a QuickTime stream, an ISO Base Media file stream, or an MP4 file stream. Alternatively, it may be a stream portion of an AVC file stream. However, in the latter case, each field of the management file is mapped and stored in each data field in the file header.

  In the sixth and seventh embodiments, the SOBU data size may be an address value with the stream head of each SOBU set to zero.

  In the sixth and seventh embodiments, the format conversion unit converts only the management information file and does not convert the stream file. However, the stream file may be converted as necessary.

  In the sixth and seventh embodiments of the present invention, the stream and the stream management file are first recorded on the phase change optical disk or HDD. However, it may be recorded in the semiconductor memory first. At this time, the recorder further performs data conversion of the management file after copying the stream to the phase change optical disk or the memory.

  In the sixth and seventh embodiments, the audio data is included in the stream, but may not be present. The stream management information does not include the PAT / PMT pointer, the TSP arrival time, and the time length valid flag fields described in the second embodiment, but may include them as necessary.

  In the sixth and seventh embodiments, the PTS absolute value of the I frame of the first SOBU may be recorded in TMAP_GI. Thereby, the absolute value of PTS can be derived together with the PTS difference. By using this PTS absolute value, the display start location of the MPEG decoder can be finely controlled.

  In the sixth and seventh embodiments, each data field in SOBU_ENT may be provided as an independent table. Each independent table exists, for example, as an independent management file, and constitutes management information.

  Further, for example, only the field of the preceding display number may be provided as a separate table. According to this example, since the data structure configuration of the management file according to the sixth and seventh embodiments approximates the data structure of the management file 11, the affinity with the management file 11 is improved.

  In the above-described embodiment, the stream and its management information are recorded on the recording medium via the built-in drive of the recorder. However, it may be recorded on a recording medium by a drive device connected to the recorder via a network.

  In the above-described embodiment, the optical disk file system is UDF, but may be NTFS, FAT, UFS (Unix (registered trademark) File System), or the like. The digital interface is exemplified by a 1394 interface. However, other digital interfaces such as USB 2.0 and HDMI may be used.

  In the above-described embodiment, a picture refers to one progressive video frame, a set of two interlaced videos of top field and bottom field, or one interlaced video according to the MPEG-2 video standard. This picture corresponds to a video object plane (VOP) of the MPEG-4 video standard, for example.

  Further, although the storage medium is described as being a phase change optical disk, the present invention is not particularly limited to this. In addition, for example, a recording medium having a disk shape such as an optical disk such as DVD-RAM, MO, DVD-R, DVD-RW, DVD + RW, CD-R, CD-RW, or hard disk, or a disk shape such as a memory card. The recording medium which does not have may be sufficient. Further, it may be a semiconductor memory such as flash memory, MRAM, or FeRAM. The read / write head is a pickup, but if the recording medium is an MO, it becomes a pickup and a magnetic head, and if it is a hard disk, it becomes a magnetic head.

  Each functional block in FIG. 19 and the like is typically realized as a plurality of one or more integrated circuit (Large Integrated Circuits; LSI) chips. These may be individually made into one chip, or may be made into one chip so as to include a part or all of them. For example, the encoder 670 and the management information generating unit 642 may be integrated into one chip and mounted on the recording / reproducing unit 540. This chip can write data stream and management information files to a recording medium via the HDD drive unit 520, the optical disk drive unit 530, and / or the memory card drive unit 550.

  The encoder 670 and the decoder 671 may be integrated into one chip, and the management information generation unit 642 may be realized as another chip. At this time, the management information generation unit 642 is mounted as a dedicated processor or a general-purpose processor that executes a computer program that implements the functions of the management information generation unit described above.

  In this embodiment, the logical block is 32 Kbytes and the sector is 2 Kbytes, but there is no particular limitation as long as the logical block size is an integral multiple of the sector size. For example, the logical block may be 16K bytes and the sector may be 2K bytes. Further, both the logical block and the sector may be 2K bytes.

  In the present embodiment, the video compression code and the audio compression code have been described as the MPEG2 video compression code and the AAC compression code, respectively. However, MPEG4 AVC code (H.264 code) such as MPEG1 video compression code, MPEG4 video compression code, MPEG-Audio compression code, Dolby AC3 compression code, or Twin-VQ compression code may be used.

  In the example of FIGS. 25 and 26, the management information generation unit generates information of each item of the SOBU_ENT table according to the type of the recording medium. However, the management information generation unit may generate each information according to only the recording format of the recording medium. Alternatively, each piece of information may be generated according to the type of recording medium and the recording format.

  In the above-described embodiment, the transmission timing of the transport stream is determined by the output timing generation unit. However, the transmission timing of the transport packet output from the system encoding unit 104 at the time of recording may be recorded at the same time as the transport packet, and this transmission timing information may be used at the time of 1394 output. In this case, for example, it can be realized by recording transmission timing information of 4 bytes immediately before the transport packet and recording it in a packet format of a total of 192 bytes. However, in this case, it is necessary to count the number of packets of 192 bytes as the SOBU data length. Further, a plurality of transmission timing information may be stored in a dedicated transport packet for storing transmission timing information, and the corresponding transport packet may be recorded immediately after the transport packet. In this case, the data size of the packet remains 188 bytes.

  In the above-described embodiment, the management information of the stream has been described on the assumption that the stream is a continuous stream. However, even if the time stamp such as PCR, PTS, or transmission timing information becomes discontinuous with a predetermined packet as a boundary, Good. However, in this case, management information may be managed and recorded separately for each continuous range of streams.

  The recorder (data processing apparatus) according to the present invention operates based on a computer program that defines the processing procedure shown in FIGS. A computer (for example, CPU) of the data processing apparatus can execute the above-described processing by operating each component in the apparatus by executing such a computer program. The computer program is recorded on a recording medium such as a CD-ROM and distributed as a product to the market or transmitted through an electric communication line such as the Internet. As a result, the computer system can be operated as a device having a function equivalent to that of the above-described data processing apparatus.

  As described above, according to the present invention, processing for importing a video stream and management information recorded on an external recording medium and processing for high-speed export of the stream and management information to an external recording medium are performed. A feasible data processing apparatus can be obtained.

It is a figure which shows the data structure of a recording file. (A)-(e) is a figure which shows the data structure of various transport packets. It is a figure which shows the example of the data on the optical disk managed on the UDF file system. It is a figure which shows the relationship between VOBU and a transport packet, and a video elementary stream and an audio elementary stream. 1 is a block configuration diagram of an optical disc recorder 200 according to Embodiment 1. FIG. It is a figure which shows the data structure of the recording file recorded by the recorder. 6 is a block configuration diagram of an optical disc recorder 300 according to Embodiment 2. FIG. 3 is a data structure diagram of a recording file recorded by a recorder 300. FIG. 4 is a data structure diagram of a management file recorded by a recorder 300. FIG. It is a data structure figure of the management data provided for every continuous SOBU group. It is a data structure figure by the other example of a management file. It is a data structure figure of the audio | voice file by Embodiment 3. FIG. 6 is a block configuration diagram of a player 400 according to a fourth embodiment. FIG. 10 is a data structure diagram of a management file according to a fifth embodiment. It is a figure which shows the 1st example of the data structure of a management file. It is a figure which shows the 2nd example of the data structure of a management file. It is a figure which shows the relationship between PTS difference of SOBU, SOBU head I picture, and SOBU time length. FIG. 10 is a main block configuration diagram of an HDD built-in optical disc recorder 500 according to Embodiment 6. FIG. 10 is a diagram illustrating a configuration of a recording / reproducing unit 540 according to a sixth embodiment. It is a figure which shows the data structure of the management file by Embodiment 6. It is a figure which shows the definition of the prior | preceding display number recorded on the management file by Embodiment 6. FIG. 5 is a flowchart showing a procedure of processing for generating a management file 21 by a recorder 500. It is a flowchart which shows the procedure of the conversion process of a management file. It is a figure which shows the data structure of the management file by Embodiment 7. It is a figure which shows the correspondence of each field in the SOBU_ENT table of a management file at the time of the export to a memory card, and the import from a memory card. It is a figure which shows the correspondence of each field regarding the SOBU_ENT table of various recording media.

Explanation of symbols

500 HDD built-in optical disk recorder 510 format conversion unit 520 HDD unit 530 optical disk drive unit 540 recording / playback unit 550 memory card drive unit 642 management information generation unit 661 recording control unit 670 MPEG encoder 671 MPEG decoder

Claims (12)

An encoder that encodes a video signal to generate a data stream;
A management information generating unit for generating management information for reproducing video from the data stream;
A data processing apparatus comprising: a drive for writing the data stream and the management information to a recording medium;
The encoder generates a plurality of reproduction units including data of a reference picture that can be decoded independently, data of one or more reference pictures that need to be decoded from the reference picture, and time information indicating a reproduction time of each picture. Sequence to generate the data stream;
The management information generation unit, according to the type and recording format of the recording medium, reference picture information in which a reproduction time of a reference picture recorded first in each reproduction unit is associated with a recording position of the reference picture; Generating one piece of reproduction unit information for associating the reproduction time length of the reproduction unit with the recording position of the reference picture, and further generating and generating time length information related to the reproduction time length of the picture in the reproduction unit A data processing apparatus for storing each piece of information as management information in one or more tables for each reproduction unit. Due to the encoding process, the order in which the data of each picture is arranged is different from the order in which each picture is displayed,
The encoder includes one or more reference pictures arranged after the first reference picture with respect to the arrangement of data in the reproduction unit, wherein the one or more reference pictures displayed before the first reference picture are displayed. Output information to identify,
2. The data processing according to claim 1, wherein the management information generation unit generates time length information related to the playback time length of the identified one or more reference pictures, and further stores the time length information in one or more tables for each playback unit. apparatus.   The management information generation unit generates a first flag for specifying one of the generated reference picture information and the reproduction unit information, and a second flag indicating that the time length information is included, The data processing apparatus according to claim 1, further storing in one or more tables for each reproduction unit. A conversion unit for converting the format of the management information;
The data processing according to claim 1, wherein when the management information generation unit generates the reference picture information, the conversion unit further generates the reproduction unit information based on the reference picture information and the time length information. apparatus.   The data processing apparatus according to claim 4, wherein the conversion unit generates new management information by replacing the generated reproduction unit information with the reference picture information. It further includes an interface unit for performing data communication with an external device,
The data processing apparatus according to claim 5, wherein the interface unit outputs the new management information and the data stream to the external device. A conversion unit for converting the format of the management information;
The data processing according to claim 1, wherein when the management information generation unit generates the reproduction unit information, the conversion unit further generates the reference picture information based on the reproduction unit information and the time length information. apparatus.   The data processing apparatus according to claim 7, wherein the conversion unit generates new management information by replacing the generated reference picture information with the reproduction unit information. It further includes an interface unit for performing data communication with an external device,
The data processing apparatus according to claim 8, wherein the interface unit outputs the new management information and the data stream to the external device. A data processing method for writing a video data stream, and management information for reproducing the video from the data stream to a recording medium,
Data of a reference picture that can be decoded independently by performing an encoding process on a video signal, data of one or more reference pictures that need to be decoded from the reference picture, and time information that indicates the reproduction time of each picture Generating multiple playback units;
Arranging a plurality of playback units to generate a data stream;
In accordance with the type and recording format of the recording medium, reference picture information in which the reproduction time of the reference picture that is first recorded in each reproduction unit is associated with the recording position of the reference picture, and reproduction of the reproduction unit Generating one piece of reproduction unit information for associating a time length with a recording position of the reference picture;
Generating time length information relating to a playback time length of a picture in the playback unit;
Storing one of the generated reference picture information and the reproduction unit information, and the time length information as management information in one or more tables for each reproduction unit;
A data processing method comprising: writing the data stream and the management information to the recording medium. An encoder that encodes a video signal to generate a data stream;
A management information generating unit that generates management information for reproducing video from the data stream, and instructing a drive to write the data stream and the management information to a recording medium,
The encoder generates a plurality of reproduction units including data of a reference picture that can be decoded independently, data of one or more reference pictures that need to be decoded from the reference picture, and time information indicating a reproduction time of each picture. Sequence to generate the data stream;
The management information generation unit, according to the type and recording format of the recording medium, reference picture information in which a reproduction time of a reference picture recorded first in each reproduction unit is associated with a recording position of the reference picture; And generating one piece of reproduction unit information for associating the reproduction time length of the reproduction unit with the recording position of the reference picture, and further generating and managing time length information related to the reproduction time length of the picture in the reproduction unit A circuit chip that stores information in one or more tables for each reproduction unit. A computer-executable computer program used to generate a video data stream and management information for reproducing the video from the data stream,
The computer program is stored in the computer.
Data of a reference picture that can be decoded independently by performing an encoding process on a video signal, data of one or more reference pictures that need to be decoded from the reference picture, and time information that indicates the reproduction time of each picture Generating multiple playback units;
Arranging a plurality of playback units to generate a data stream;
In accordance with the type and recording format of the recording medium, reference picture information in which the reproduction time of the reference picture that is first recorded in each reproduction unit is associated with the recording position of the reference picture, and reproduction of the reproduction unit Generating one piece of reproduction unit information for associating a time length with a recording position of the reference picture;
Generating time length information relating to a playback time length of a picture in the playback unit;
Storing one of the generated reference picture information and the reproduction unit information, and the time length information as management information in one or more tables for each reproduction unit;
A computer program causing the data stream and the management information to be written to the recording medium.

Images