JP4135109B2 - Recording apparatus, recording method, and recording medium - Google Patents

Description

The present invention relates to a recording apparatus, a recording method, and a recording medium , and more particularly to a recording apparatus, a recording method, and a recording medium that prevent a user from misidentifying a failure in relation to continuous reproduction of data. About.

  In addition to continuous recording of video data, audio data, and the like, the disc may be recorded intermittently with time. In addition, once recorded data may be erased and other data may be overwritten.

  When such erasure or overwrite processing is repeatedly executed, data to be reproduced continuously may not be recorded at continuous positions on the disk, but may be recorded at spaced positions on the disk. In such a case, if the capacity of the buffer at the time of playback of the device is not sufficient, depending on the recording position, the data cannot be played back continuously, and playback data may be temporarily lost. is there.

  However, whether or not the discontinuity occurs is affected by the buffer capacity of the device, so compatibility between devices cannot be ensured, and in the worst case, the user misidentifies that the device has failed. There was a risk.

  The present invention has been made in view of such a situation, and ensures compatibility of devices and suppresses a user from misidentifying that the device has failed.

The recording medium according to the first aspect of the present invention is a recording medium on which at least video data is recorded divided into a plurality of playback sections, and when the read channel buffer of the playback device becomes empty during playback, In addition, when the video data cannot be recorded by being changed to a continuously reproducible position, information indicating whether or not the replay of the video data during the plurality of replay sections is reproducible , Information indicating at least that continuous playback is not possible is recorded.

  The recording medium according to the second aspect of the present invention is a recording medium on which at least video data is recorded divided into a plurality of playback sections, and when the read channel buffer of the playback device becomes empty during playback. In addition, when the user approves the occurrence of discontinuity, the information indicating whether or not the video data can be continuously played back during the plurality of playback sections includes at least information indicating that continuous playback is not possible. It is recorded.
  The information indicating whether or not the video data can be continuously played back can be a flag indicating whether or not the video data can be played back continuously.
  A recording apparatus according to a third aspect of the present invention is a recording apparatus for recording at least video data in a plurality of playback sections on a recording medium, and when the read channel buffer of the playback apparatus becomes empty during playback. And when the video data cannot be recorded at a position where it can be continuously played back, information indicating whether playback of the video data during the plurality of playback sections can be played back continuously And a recording means for recording at least information indicating that continuous reproduction is not possible.
  The information indicating whether or not the video data can be continuously played back can be a flag indicating whether or not the video data can be played back continuously.
  A recording method according to a third aspect of the present invention is a recording method for a recording device that records at least video data in a plurality of playback sections on a recording medium, and a read channel buffer of the playback device is empty during playback. Whether or not the video data can be continuously played back during the plurality of playback sections when the video data cannot be recorded after being changed to a continuously playable position. As the information indicating, at least a recording step for recording information indicating that continuous reproduction is impossible is included.
  A recording apparatus according to a fourth aspect of the present invention is a recording apparatus in which at least video data is recorded in a plurality of playback sections on a recording medium, and a read channel buffer of the playback apparatus becomes empty during playback. When the user approves the occurrence of discontinuity, the information indicating whether or not the playback of the video data during the plurality of playback sections can be continuously played back is at least continuous playback disabled. It is characterized by comprising recording means for recording the indicated information.
  The information indicating whether or not the video data can be continuously played back can be a flag indicating whether or not the video data can be played back continuously.
  A recording method according to a fourth aspect of the present invention is a recording method for a recording apparatus in which at least video data is recorded on a recording medium divided into a plurality of reproduction sections, and a read channel buffer of the reproduction apparatus is used during reproduction. When it becomes empty and when the user accepts the occurrence of discontinuity, the information indicating whether or not the video data can be continuously played back during the plurality of playback sections is at least continuous. Recording means for recording information indicating that reproduction is impossible is provided.

In the first aspect and the third aspect of the present invention , at the time of reproduction, when the read channel buffer of the reproduction apparatus becomes empty, the video data is changed to a position where it can be reproduced continuously. When recording is not possible , at least information indicating that continuous playback is not possible is recorded as information indicating whether playback of the video data during the plurality of playback sections is continuously possible.
In the second aspect and the fourth aspect of the present invention, when the read channel buffer of the playback device is emptied during playback and the user acknowledges the occurrence of discontinuity, the plurality of playbacks are performed. At least information indicating that continuous playback is not possible is recorded as information indicating whether or not the video data can be continuously played back during the section.

  According to the present invention, a recording medium that can ensure compatibility can be realized.

  Embodiments of the present invention will be described below, but in order to clarify the correspondence between each means of the invention described in the claims and the following embodiments, in parentheses after each means, The features of the present invention will be described with the corresponding embodiment (however, an example) added. However, of course, this description does not mean that each means is limited to the description.

  The recording / reproducing apparatus according to claim 1 is a recording means for recording data on a recording medium (for example, the optical head 2 in FIG. 25), and when the data is recorded on the recording medium, the data is already recorded. A determination unit (for example, step S2 in FIG. 48) for determining whether or not the data being continuously reproducible is executed, and processing related to continuous data reproduction is executed in accordance with the determination result of the determination unit. Executing means (for example, step S5 in FIG. 48).

  The recording / reproducing apparatus according to claim 6 is configured to reproduce data recorded on a recording medium by reproducing means (for example, the optical head 2 in FIG. 25) and data reproduced by the reproducing means. An extraction unit (for example, step S41 in FIG. 50) for extracting continuous reproduction information indicating whether or not it is possible, and a gap with respect to the data reproduced by the reproduction unit corresponding to the continuous reproduction information extracted by the extraction unit Adding means (for example, step S46 in FIG. 50).

First, a file arrangement on a recording medium (media) on which information is recorded or reproduced in the present invention will be described. As shown in FIG. 1, the following seven types of files are recorded on the medium.
VOLUME.TOC
ALBUM.STR
PROGRAM _ $$$. PGI
TITLE _ ###. VDR
CHUNKGROUP _ @@@. CGIT
CHUNK _ %%%%. ABST
CHUNK _ %%%%. MPEG2

  VOLUME.TOC and ALBUM.STR are placed in the root directory. Also, “PROGRAM _ $$$. PGI” (where “$$$” represents the program number) is placed in the directory “PROGRAM” immediately below the root directory. Similarly, “TITLE _ ###. VDR” (where “###” represents the title number) is included in the directory “TITLE” directly under the root directory, and “CHUNKGROUP _ @@@” is included in the directory “CHUNKGROUP”. .CGIT ”(where“ @@@ ”represents the chunk group number), but in the directory“ CHUNK ”,“ CHUNK _ %%%%. ABST ”(where“ %%%% ”represents the chunk number) ) Are placed respectively.

  In the MPEGAV directory immediately below the root directory, one or more subdirectories are created, and “CHUNK _ %%%%. MPEG2” (where %%%% represents a chunk number) is placed under the subdirectory.

  There is usually one VOLUME.TOC file on the media. However, there may be a plurality of media having a special structure such as a medium having a hybrid structure of ROM and RAM. This file is used to indicate the overall nature of the media.

  The structure of VOLUME.TOC is as shown in FIG. File_type_id is placed at the beginning, and this indicates that the corresponding file is VOLUME.TOC. Next is volume_information (), followed by text_block ().

  FIG. 3 shows the configuration of volume_information (). This includes volume_attribute (), resume (), volume_rating (), write_protect (), play_protect (), and recording_timer ().

  The volume_attribute () is an area for recording the attribute of the logical volume, and its detailed structure is shown in FIG. As shown in the figure, this area includes title_playback_mode_flag, program_playback_mode_flag, and the like.

  resume () is an area for recording information for restoring the state immediately before eject when the medium is reinserted, and its detailed structure is shown in FIG.

  Volume_rating () in FIG. 3 is an area for recording information for realizing the viewing age restriction on the entire volume according to age and category, and its detailed structure is shown in FIG.

  The write_protect () in FIG. 3 is an area for recording information for restricting changes to the title and program recorded in the volume and erasing operations, and its detailed structure is shown in FIG.

  The play_protect () in FIG. 3 is an area for recording information that restricts the reproduction permission / non-permission of the title and program recorded in the volume, or restricts the number of reproductions, and its detailed structure is shown in FIG. Is shown in

  The recording_timer () in FIG. 3 is an area for recording information for controlling the recording time, and its detailed structure is shown in FIG.

  The detailed structure of text_block () of VOLUME.TOC in FIG. 2 is shown in FIG. This text_block () includes language_set () and text_item, and their detailed structures are shown in FIGS. 11 and 12, respectively.

  There is usually one ALBUM.STR file in FIG. 1 on the medium. However, there may be a plurality of media having a special structure such as a medium having a hybrid structure of ROM and RAM. This file is used to combine a plurality of media so that it is as if it is one medium.

  The structure of this ALBUM.STR is as shown in FIG. File_type_id is placed at the beginning, indicating that the file is ALBUM.STR. This is followed by album (), followed by text_block ().

  album () is an area for recording information for handling a plurality of volumes (a plurality of media) as one unit, and its detailed structure is shown in FIG.

  There are as many TITLE _ ###. VDR files as the number of titles in FIG. The title refers to, for example, one song on a compact disc or one program on television broadcasting. The structure of this information is as shown in FIG. File_type_id is placed at the beginning, and this indicates that the corresponding file is TITLE _ ###. VDR. Next is title_info (), followed by text_block (). ### is a character string indicating the title number.

  title_info () is an area for recording the title start point, end point, and other attributes related to the title on the chunkgroup, and its detailed structure is shown in FIG.

  There are as many files of PROGRAM _ $$$. PGI in FIG. 1 as there are programs. The program is composed of a plurality of cuts that specify part (or all) of the title, and each cut is reproduced in the specified order. The structure of this information is shown in FIG. File_type_id is placed at the beginning, indicating that the file is PROGRAM _ $$$. PGI. Then program () follows, and finally text_block () follows. $$$ is a character string indicating the title number.

  The program () is an area for recording information necessary to collect and play the necessary parts of the title without performing irreversible editing on the material. The detailed structure is shown in FIG. Has been.

  Program () in FIG. 18 has one play_list. Details of the play_list () are shown in FIG.

  The play_list has a plurality of play_item (). The details of play_item () are shown in FIG.

  There are as many CHUNKGROUP _ @@@. CGIT files as the number of chunk groups in FIG. A chunk group is a data structure for arranging bit streams. This file is not recognized by the user because the user normally operates a device for recording and reproducing media such as a VDR (video disc recorder).

  The structure of this information is as shown in FIG. File_type_id is placed at the beginning, indicating that the file is CHUNKGROUP _ @@@. CGIT. Next is chunkgroup_time_base_flags and chunkgroup_time_base_offset, followed by chunk_connection_info (), and finally text_block ().

  chunkgroup_time_base_flags indicates a flag relating to a chunkgroup reference counter, and chunkgroup_time_base_offset indicates a start time of a reference time axis in the chunkgroup. This is a value set in a counter that counts up at 90 kHz, and has a size of 32 bits. The chunk_connection_info () is an area for storing information on specific points such as video switching points and video and audio synchronization, and the detailed structure thereof is shown in FIG.

  In this chunk_connection_info (), there are as many chunk_arrangement_info () loops as the number of chunks belonging to the chunk group. FIG. 23 shows details of the chunk_arrangement_info ().

  There are as many CHUNK _ %%%%. ABST files in FIG. 1 as there are chunks. A chunk is an information file corresponding to one stream file. The structure of this information is as shown in FIG. File_type_id is placed at the head, and this indicates that the corresponding file is CHUNK _ %%%%. ABST.

  The CHUNK _ %%%%. MPEG2 file in FIG. 1 is a stream file. This file stores an MPEG bitstream, and is different from other files that record only information.

  FIG. 25 shows a configuration example of an optical disc apparatus that records or reproduces information with respect to an optical disc as a medium having the above files. In this optical disk apparatus, one optical head 2 is provided for one rewritable optical disk 1, and the optical head 2 is shared for both reading and writing of data.

  The bit stream read from the optical disk 1 by the optical head 2 is demodulated by the RF and demodulation / modulation circuit 3, and then subjected to error correction by the ECC circuit 4. The read rate and the decoding processing rate are passed through the switch 5. To the read channel buffer 6 for absorbing the difference. The output of the read channel buffer 6 is supplied to the decode 7. The read channel buffer 6 is configured to be readable and writable from the system controller 13.

  The bit stream output from the read channel buffer 6 is decoded by the decoder 7 from which a video signal and an audio signal are output. The video signal output from the decoder 7 is input to the combining circuit 8 and is combined with the video signal output from the 0SD (On Screen Display) control circuit 9, and then output from the output terminal P1 to a display (not shown) for display. Is done. The audio signal output from the decoder 7 is sent from the output terminal P2 to a speaker (not shown) and reproduced.

  On the other hand, the video signal input from the input terminal P3 and the audio signal input from the input terminal P4 are encoded by the encoder 10, and then a write channel buffer for absorbing the difference between the encoding processing rate and the write rate. 11 is sent. The write channel buffer 11 is also configured to be readable and writable from the system controller 13.

  The data stored in the write channel buffer 11 is read from the write channel buffer 11, input to the ECC circuit 4 via the switch 5 and added with an error correction code, and then the RF and demodulation / modulation circuit 3. Modulated with. A signal (RF signal) output from the RF and demodulation / modulation circuit 3 is written on the optical disk 1 by the optical head 2.

  The address detection circuit 12 detects address information of a track to be recorded or reproduced on the optical disc 1. The system controller 13 controls the operation of each part of the optical disk device, and temporarily stores a CPU 21 that performs various controls, a ROM 22 that stores processing programs to be executed by the CPU 21, data generated during the processing, and the like. And a RAM 24 for storing various information files to be recorded on or reproduced from the optical disc 1. The CPU 21 finely adjusts the position of the optical head 2 based on the detection result of the address detection circuit 12. The CPU 21 also performs switching control of the switch 5. The input unit 14 including various switches and buttons is operated by the user when inputting various commands.

  Next, a basic information file reading operation will be described. For example, when reading the “VOLUME.TOC” information file, the CPU 21 of the stem controller 13 uses a file system operation instruction incorporated in the processing program in advance, and the optical disk 1 on which “VOLUME.TOC” is recorded. Determine the upper physical address and its length. Subsequently, the CPU 21 moves the optical head 2 to the reading position based on the address information of “VOLUME.TOC”. The CPU 21 sets the optical head 2, the RF and demodulation / modulation circuit 3, and the ECC circuit 4 to the read mode, switches the switch 5 to the read channel buffer 6 side, and finely adjusts the position of the optical head 2. Thereafter, reading by the optical head 2 is started. As a result, the contents of “VOLUME.TOC” are read out by the optical head 2, demodulated by the RF and demodulation / modulation circuit 3, further corrected by the ECC circuit 4, and then stored in the read channel buffer 6. The

  When the amount of data stored in the read channel buffer 6 is equal to or larger than the size of “VOLUME.TOC”, the CPU 21 stops reading. Thereafter, the CPU 21 reads the corresponding data from the read channel buffer 6 and stores it in the RAM 24.

  Next, the basic information file writing operation will be described by taking the case of writing the “VOLUME.TOC” information file as an example. The CPU 21 uses a file system operation instruction incorporated in the processing program in advance, and a free area having a size equal to or larger than “VOLUME.TOC” to be written in the file system (optical disc 1). And confirm the address.

  Next, the CPU 21 transfers “VOLUME.TOC” to be newly written, which is prepared in the RAM 24, to the write channel buffer 11. Subsequently, the CPU 21 moves the optical head 2 to the writing position based on the address information of the free area. The CPU 21 sets the optical head 2, the RF and demodulation / modulation circuit 3, and the ECC circuit 4 to the write mode, switches the switch 5 to the write channel buffer 11 side, and finely adjusts the position of the optical head 2. Then, writing by the optical head 2 is started.

  As a result, the contents of the newly prepared “VOLUME.TOC” are read from the write channel buffer 11, input to the ECC circuit 4 via the switch 5, and after the error correction code is added, RF and demodulation / demodulation / Modulation is performed by the modulation circuit 3. The signal output from the RF and demodulation / modulation circuit 3 is recorded on the optical disk 1 by the optical head 2. When the amount of data read from the write channel buffer 11 and recorded on the optical disk 1 becomes equal to the size of “VOLUME.TOC”, the CPU 21 stops the write operation.

  Finally, the CPU 21 rewrites the pointer indicating “VOLUME.TOC” in the file system (optical disc 1) so as to indicate the newly written position by using a file system operation instruction incorporated in the processing program in advance. .

  Next, a basic stream reproduction operation will be described by taking as an example the case of reproducing a stream called CHUNK_0001.MPEG2 in FIG. The CPU 21 uses a file system operation instruction incorporated in advance in the processing program to determine the physical address on the optical disc 1 on which “CHUNK — 0001.MPEG2” is recorded and its length. Subsequently, the CPU 21 moves the optical head 2 to the reading position based on the address information of “CHUNK — 0001.MPEG2”. Then, the optical head 2, the RF and demodulation / modulation circuit 3, and the ECC circuit 4 are set to the read mode, the switch 5 is switched to the read channel buffer 6 side, and the position of the optical head 2 is finely adjusted. 2 starts reading.

  The contents of “CHUNK — 0001.MPEG2” read by the optical head 2 are accumulated in the read channel buffer 6 via the RF and demodulation / modulation circuit 3, the ECC circuit 4, and the switch 5. The data stored in the read channel buffer 6 is output to the decoder 7, subjected to decoding processing, and a video signal and an audio signal are output. The audio signal is output from the output terminal P2, and the video signal is output from the output terminal P1 via the synthesis circuit 8.

  When the amount of data read, decoded and displayed from the optical disc 1 becomes equal to the size of “CHUNK — 0001.MPEG2”, or when stop of the reading operation is designated from the input unit 14, the CPU 21 Stop reading and decoding.

  Next, a basic stream recording operation will be described by taking as an example the case of writing the “CHUNK — 0001.MPEG2” information file. The CPU 21 uses a file system operation instruction incorporated in advance in the processing program, and a free area having a size equal to or larger than “CHUNK_0001.MPEG2” to be written in the file system (optical disc 1). And confirm the address.

  The video signal input from the input terminal P3 and the audio signal input from the input terminal P4 are encoded by the encoder 10 and then stored in the write channel buffer 11. Subsequently, the CPU 21 moves the optical head 2 to the writing position based on the address information of the free area. The CPU 21 sets the optical head 2, the RF and demodulation / modulation circuit 3, and the ECC circuit 4 to the write mode, switches the switch 5 to the write channel buffer 11 side, and finely adjusts the position of the optical head 2. Then, writing by the optical head 2 is started. As a result, the contents of the newly prepared “CHUNK — 0001.MPEG2” are read from the write channel buffer 11 and input to the optical head 2 via the switch 5, ECC circuit 4, RF and demodulation / modulation circuit 3. 1 is recorded.

  When the amount of data read from the write channel buffer 11 and recorded on the optical disc 1 becomes equal to a preset value, or when the stop of the write operation is designated from the input unit 14, the CPU 21 performs the write operation. Stop. Finally, the CPU 21 rewrites the pointer indicating “CHUNK — 0001.MPEG2” in the file system (optical disc 1) so as to indicate the newly written position by using a file system operation instruction incorporated in the processing program in advance. .

  Assume that an information file and a stream file as shown in FIG. 26 are recorded on the optical disc 1. In this example, one program file named “PROGRAM — 001.PGI” is included. The optical disc 1 also includes three title files named “TITLE_001.VDR”, “TITLE_002.VDR”, and “TITLE_003.VDR”.

  Further, the optical disc 1 includes two chunk group files “CHUNKGROUP_001.CGIT” and “CHUNKGROUP_002.CGIT”. The optical disc 1 includes three stream files named “CHUNK — 0001.MPEG2”, “CHUNK — 0011.MPEG2”, and “CHUNK — 0012.MPEG2”, and the corresponding information includes “CHUNK — 0001. Three information files “.ABST”, “CHUNK — 0011.ABST”, and “CHUNK — 0012.ABST” are placed.

The logical structure of the optical disc 1 having the information file and the stream file shown in FIG. 26 is as shown in FIG. In this example, the chunk information file “CHUNK_0001.ABST” is the stream file “CHUNK_0001.MPEG2”, the chunk information file “CHUNK_0011.ABST” is the stream file “CHUNK_0011.MPEG2”, and the chunk information file “CHUNK_0012”. “.ABST” designates the stream file “CHUNK — 0012.MPEG2”, respectively. Specifically, the file ID of the stream is specified in the field called chunk_file_id in CHUNK _ %%%%. ABST in FIG.

  Furthermore, in this example, the chunk group information file “CHUNKGROUP_001.CGIT” is the chunk information file “CHUNK_0001.ABST”, and the chunk group information file “CHUNKGROUP_002.CGIT” is the chunk information files “CHUNK_0011.ABST” and “CHUNK_0012”. .ABST ”is specified respectively. Specifically, the file ID of chunk information is specified in a field called chunk_info_file_id in chunk_arrangement_info () in FIG. This chunk_arrangement_info () is in the chunk group information file and has a data structure that exists as many as the number of chunks belonging to the chunk group (chunk_arrangement_info () in FIG. 23 is described in chunk_connection_info () in FIG. 22). This chunk_connection_info () is described in CHUNKGROUP _ ###. CGIT in FIG. 21).

  CHUNKGROUP_001 has only one chunk_arrangement_info (), and chunk_info_file_id in it specifies CHUNK_0001. CHUNKGROUP_002 has two chunk_arrangement_info (), in which CHUNK_0011 and CHUNK_0012 are specified, respectively. For such a case, the chunk group can specify the reproduction order of a plurality of chunks.

  Specifically, first, the initial value of the clock in the chunk group is determined by chunkgroup_time_base_offset in CHUNKGROUP _ ###. CGIT in FIG. Next, when registering each chunk, presentation_start_cg_count and presentation_end_cg_time_count of chunk_arrangement_info () in FIG. 23 are designated.

  For example, as shown in FIG. 28, the length (time) of CHUNK_0011 is A, and the length (time) of CHUNK_0012 is B. The presentation_start_cg_count of CHUNK_0011 is equal to chunkgroup_time_base_offset, and the presentation_end_cg_count is equal to “chunk_group_time_base_offset + A”. In addition, presentation_start_cg_count of CHUNK_0012 is equal to chunkgroup_time_base_offset + A, and presentation_end_cg_count is equal to “chunk_group_time_base_offset + A + B”. With this setting, CHUNKGROUP_002 is defined as a continuous reproduction of CHUNK_0011 and CHUNK_0012.

  In addition, when there is an overlap in the reproduction time of CHUNK_0011 and CHUNK_0012, it can be specified by shifting the time as such. Also, by describing in transition_info () in chunk_arrangement_info () of FIG. 23, special effects (fade in, fade out, wipe, etc.) can be specified in transition between two streams.

In the example of FIG. 26 (FIG. 27), the title information files “TITLE_001.VDR” and “TITLE_002.VDR” are the chunk group information file “CHUNKGROUP_001.CGIT”, and the title information file “TITLE_003.VDR” is the chunk group information. Each file “CHUNKGROUP_002.CGIT” is specified. Specifically, in title_info () of FIG. 16, the file ID of the chunk group is specified in the field called cgit_file_id, and the time range in which the corresponding title is defined in the chunk group in the fields title_start_chunk_group_time_stamp and title_end_chunk_group_time_stamp Is specified.

  For example, in the example of FIG. 27, TITLE_001 indicates the first half of CHUNKGROUP_001 and TITLE_002 indicates the second half. This division is performed according to a request from the user, and its position is arbitrary for the user and cannot be determined in advance. Here, it is assumed that the position of division by TITLE_001 and TITLE_002 is set to a position separated by A from the head of CHUNKGROUP_001.

  TITLE_001 specifies CHUNKGROUP_001 as the chunk group, specifies the start time of CHUNKGROUP_001 as the start time of the title, and specifies the time of the point specified by the user as the end time of the title.

  That is, CHUNKGROUP_001 chunkgroup_time_base_offset (start position) is set as TITLE_001 title_start_chunk_group_time_stamp, and TITLE_001 title_end_chunk_group_time_stamp is set to CHUNKGROUP_001 chunkgroup_time_base_offset plus the length of A.

  TITLE_002 designates CHUNKGROUP_001 as the chunk group, designates the time at the point designated by the user as the title start time, and designates the end time of CHUNKGROUP_001 as the title end time.

  That is, the title_start_chunk_group_time_stamp of TITLE_002 is set to CHUNKGROUP_001's chunkgroup_time_base_offset (start position) plus the length of A, the title_end_chunk_group_time_stamp of TITLE_002 is set to CHUNKgroup_time_base_off_ of CHUNKGROUP_001 and CH001 is set to the length of CH_K

  Further, TITLE_003 designates CHUNKGROUP_002 as the chunk group, designates the start time of CHUNKGROUP_002 as the start time of the title, and designates the end time of CHUNKGROUP_002 as the end time of the title.

  That is, CHUNKGROUP_002 chunkgroup_time_base_offset is set as TITLE_003 title_start_chunk_group_time_stamp, and TUNLE_003 title_end_chunk_group_time_stamp is set to CHUNKGROUP_002 chunkgroup_time_base_offset plus the length of CHUNKGROUP_002.

  Further, in this example, the program information file “PROGRAM_001.PGI” specifies that a part of TITLE_001 and a part of TITLE_003 are reproduced in this order. Specifically, a title is specified by title_number in play_item () in FIG. 20, and a start point and an end point are defined at the time defined by each title, so that one cut is extracted. A program is constructed by collecting a plurality of such cuts.

  Next, an operation when additional information is additionally recorded (appended recording) on the optical disc 1 will be described. Specifically, this recording is performed, for example, by timer recording or by the user operating the input unit 14 to instruct the optical disc apparatus to record in real time. In the latter case, when the recording button is pressed, the recording end time cannot be predicted, but when the button of the one-touch recording function (the function that performs recording for a certain time after the operation) is pressed The end time can be predicted.

  Here, a timer recording is described as an example. In this case, it is assumed that the user of the optical disc apparatus has designated in advance the recording start time, recording end time, bit stream bit rate, recording channel, and the like. In addition, it is assumed that it is confirmed in advance that the free space corresponding to the bit rate and the recording time is left on the optical disc 1 at the time when the recording is reserved.

  In the case where further recording is performed on the optical disc 1 between the time of recording reservation and the time of execution of the reserved recording, the capacity for recording the reserved program at the designated bit rate. May not be able to be secured. In such a case, the CPU 21 lowers the bit rate below a specified value and records information for the reserved time, or records the recorded time only while keeping the bit rate as it is. To do. At this time, it goes without saying that the CPU 21 issues a message informing the user when further recording is performed and a problem occurs in the reserved recording.

  When the reserved recording start time approaches, the CPU 21 automatically returns the mode from the sleep mode to the operation mode using a built-in timer and clock. Then, the CPU 21 secures an area on the optical disc 1 where a reserved program can be recorded by using a file system operation instruction incorporated in the processing program in advance. That is, the numerical value obtained by subtracting the start time from the end time of the reserved recording (recording time) and the bit rate is the size of the area necessary for recording the reserved program, and the CPU 21 has this size. First, secure the area. In addition, when it is necessary to record an information file other than the stream file at the time of recording, for example, when a title information file is necessary for registration as a new title, the capacity of the information file can be recorded. Must be secured on the optical disk 1. When the necessary area cannot be secured, the above-described method (method of changing the bit rate, recording only within the recordable time, etc.) is taken.

  At this time, since a new title is recorded, the user assigns a file name of a new stream file as a new stream file in a new stream directory. Here, this is assumed to be \ MPEGAV \ STREMS_003 \ CHUNK_0031. That is, as shown in FIG. 29, the file is named CHUNK_0031.MPEG2 under the STREAM_003 directory under the MPEGAV directory under the root directory.

  The CPU 21 instructs each unit to execute the recording mode. For example, a video signal input to the input terminal P 3 from a tuner (not shown) and an audio signal input to the input terminal P 4 are encoded by the encoder 10 and then stored in the write channel buffer 11. Subsequently, the CPU 21 moves the optical head 2 to the writing position based on the address information of the area secured previously. The CPU 21 sets the optical head 2, the RF and demodulation / modulation circuit 3, and the ECC circuit 4 to the write mode, switches the switch 5 to the write channel buffer 11 side, and finely adjusts the position of the optical head 2. Then, writing by the optical head 2 is started. As a result, the contents of the newly prepared “CHUNK — 0031.MPEG2” are read from the write channel buffer 11 and passed through the switch 5, the ECC circuit 4, the RF and demodulation / modulation circuit 3, and the optical head 2. To be recorded.

The CPU 21 stops the write operation when any of the following conditions occurs by continuing the above write operation.
1) When the scheduled recording end time is reached 2) When recording is not possible on the optical disc 1 due to lack of capacity or other reasons 3) When the recording operation is instructed to stop

  Next, the CPU 21 rewrites a pointer indicating “CHUNK — 0031.MPEG2” in the file system to a value indicating the newly written position by using a file system operation instruction incorporated in the processing program in advance. In addition, the CPU 21 prepares each file of chunk information, chunk group information, and title information, and records them with appropriate names. It should be noted that it is necessary to secure enough free space on the optical disc 1 to record these files during recording or reservation.

  In this way, a new information file is created as shown in FIG. 30, for example. In the figure, the file name newly added is the one with an asterisk (*) on the right shoulder of the file name.

  FIG. 31 shows the relationship of the newly created information file. TITLE_004 specifies CHUNKGROUP_003, CHUNKGROUP_003 specifies CHUNK_0031, and CHUNK_0031 specifies STREAM_0031.

  That is, the new stream is registered in the information file as TITLE_004. The user can know the attribute of TITLE_004 by the function of confirming the title of the optical disc apparatus, and can reproduce TITLE_004.

  Next, the operation in the case of overwriting recording on the optical disc 1 illustrated in FIG. 26 (FIG. 27) will be described. Overwrite recording refers to an operation of recording a new program on a previously recorded program (erasing the program) as in the case of recording a signal on a video tape.

  In the overwrite recording, the position where the overwrite recording is started is important. For example, it is assumed that the user specifies to start overwriting from the beginning of TITLE_001. At this time, overwriting is performed while rewriting TITLE_001, TITLE_002, and TITLE_003 in order. If the recording operation is not completed even after rewriting to the end of TITLE_003, a new area is secured in the free area on the optical disc 1 and recording is continued. For example, when TITLE_002 is set as the recording start position, TITLE_001 is positioned before the recording start position and is not rewritten by the current recording operation.

  Now, it is assumed that the timer recording is overwritten from the beginning of TITLE_003. In this case, it is assumed that the user of the optical disc apparatus designates a recording start time, an end time, a bit stream bit rate, a recording channel, and the like in advance. In addition, in the overwrite recording, it is assumed that an important recording start position is designated as the head of TITLE_003. Further, in this case, it is assumed that it is confirmed in advance that the capacity corresponding to the bit rate and the recording time exists on the optical disc 1 at the time when the recording is reserved. In the case of overwrite recording, the sum of the total capacity of a plurality of titles that can be overwritten from a designated position and the free capacity of the optical disc 1 is the recordable capacity. That is, in this case, the total capacity of the streams STREAM_0011 and STREAM_0012 managed by TITLE_003 and the sum of the free capacity on the optical disc 1 is a recordable capacity.

  In overwrite recording, there are several options for the actual recording in the order of recording capacity. First of all, a method of recording in the order of the streams specified by the title is conceivable. In other words, in this case, the recording starts from the beginning of STREAM_0011, records until the end of STREAM_0011, continues recording from the beginning of STREAM_0012, and then records until the end of STREAM_0012. It is. The other method is a method in which recording is first performed in an empty area, and recording is performed on an existing stream when the empty area is exhausted.

  The former method is superior in terms of video tape emulation. That is, in the sense that the operation is the same as that of a video tape, it is easy to understand from the user. The latter method is characterized in that it is superior in terms of protecting recorded ones since the already recorded stream is deleted later.

  In addition, when further recording is performed on the optical disc 1 between the recording reservation time and the reserved recording execution time, the program reserved this time is recorded at a specified bit rate. In some cases, the capacity cannot be secured. In such a case, as in the case described above, when the reservation is executed, the bit rate is automatically lowered, and all of the reserved time is recorded, or the recordable time with the bit rate left unchanged. Only recording is done.

  When the reserved recording start time approaches, the optical disc apparatus returns from the sleep mode to the operation mode. The CPU 21 ensures all free space on the optical disc 1. Of course, there is a method in which the free capacity is not secured at this time, but is secured when it is needed, but here, for explanation, it is assumed that a necessary area is secured before the start of recording.

  Note that the start time, end time, and bit rate are specified in timer recording, etc., so if the size of the required area is known in advance, only the necessary amount (or some margin is added). You may make it secure capacity. When it is necessary to record an information file at the time of recording, for example, when a title information file or the like is necessary for registration as a new title, it is necessary to leave a capacity sufficient to record these information files. is there.

  Here, a file name of a new stream file is given as a new stream file in a new stream directory. That is, here, the file name is \ MPEGAV \ STREMS_002 \ CHUNK_0031. That is, as shown in FIG. 32, a file named CHUNK_0031.MPEG2 under the STREAM_002 directory under the MPEGAV directory under the root directory is created.

  The video signal input to the input terminal P3 and the audio signal input to the input terminal P4 are encoded by the encoder 10 and then stored in the write channel buffer 11. Subsequently, the CPU 21 moves the optical head 2 to the writing position based on the address information of the area secured previously. The CPU 21 sets the optical head 2, the RF and demodulation / modulation circuit 3, and the ECC circuit 4 to the write mode, switches the switch 5 to the write channel buffer 11 side, and finely adjusts the position of the optical head 2. Then, writing by the optical head 2 is started. As a result, the contents of the newly prepared “CHUNK — 0031.MPEG2” are read from the write channel buffer 11 and passed through the switch 5, the ECC circuit 4, the RF and demodulation / modulation circuit 3, and the optical head 2. To be recorded.

  At this time, first, the stream file “CHUNK — 0011.MPEG2” is rewritten. When the recording to the end of “CHUNK — 0011.MPEG2” is performed, the recording is then proceeded to “CHUNK — 0012.MPEG2”, and further to “CHUNK — 0031.MPEG2”.

  Continuing the above operation, as in the case described above, the CPU 21 stops the write operation when any of the three conditions occurs.

  Next, the CPU 21 updates the stream file, chunk information, chunk group information, and title information by using a file system operation instruction previously incorporated in the processing program.

  By the way, the configuration of the file changes depending on the timing when writing is completed. For example, when overwriting of two streams CHUNK_0011.MPEG2 and CHUNK_0012.MPEG2 is completed and further recording is performed on CHUNK_0031.MPEG2, the file structure of the optical disc 1 is as shown in FIG. The newly created file has an asterisk (*) on the right shoulder of the file name.

  FIG. 34 shows the relationship of the newly created file (file shown in FIG. 33). As is clear from FIG. 31, CHUNK_0031 is increased as CHUNK included in CHUNKGROUP_002 specified by TITLE_003, and CHUNK_0031 specifies STREAM_0031.

  On the other hand, when overwriting is completed in the middle of overwriting of an existing stream, for example, when overwriting is completed in the middle of recording of CHUNK_0011, the stream of CHUNK_0031 reserved for overwriting is not overwritten and is released. In this case, special title processing is performed. That is, overwriting is started from the beginning of TITLE_003, and when recording ends in the middle, the title is divided there. That is, as shown in FIG. 35, a new TITLE_003 is set from the overwrite recording start position to the end position, and the rest (the remaining portion of the original TITLE_003) is set as TITLE_004.

  Next, the title playback operation will be described. Now, assume that an optical disc 1 having a file as shown in FIG. 26 is inserted into an optical disc apparatus and a title is reproduced. First, when the optical disc 1 is inserted, the CPU 21 reads an information file from the optical disc 1 and stores it in the RAM 24. This operation is performed by repeating the basic information file reading operation described above.

  The CPU 21 first reads VOLUME.TOC and ALBUM.STR. Next, the CPU 21 checks how many files with the extension “.VDR” exist under the directory “TITLE”. A file having this extension is a file having title information, and the number of files is the number of titles. In the example of FIG. 26, the number of titles is 3. Next, the CPU 21 reads three title information files and stores them in the RAM 24.

  The CPU 21 controls the OSD control circuit 9 to generate character information indicating the information of the title recorded on the optical disc 1, and to synthesize it with the video signal by the synthesizing circuit 8, and to output it to the display from the output terminal P1, Display. In this case, there are three titles, and the length and attributes (name, date and time of recording, etc.) of each of the three titles are displayed.

  Here, it is assumed that the user has designated reproduction of TITLE_002, for example. In the information file of TITLE_002 (cgit_file_id in title_info () of FIG. 16), a file ID that specifies CHUNKGROUP_001 is recorded. The CPU 21 stores this and stores CHUNKGROUP_001 in the RAM 24.

  Next, the CPU 21 checks which CHUNK corresponds to the start time and end time of TITLE_002 (title_start_chunk_group_time_stamp and title_end_chunk_group_time_stamp in title_info () in FIG. 16). This is performed by comparing information in which each CHUNK is registered (presentation_start_cg_time_count and presentation_end_cg_time_count in chunk_arrangement_info () in FIG. 23) from the information of CHUNKGROUP. In this case, as shown in FIG. 27, it can be seen that the start time of TITLE_002 is in the middle of CHUNK_0001. That is, it can be seen that in order to reproduce TITLE_002 from the beginning, it is only necessary to start reproduction from the middle of the stream file “CHUNK_0001.MPEG2”.

  Next, the CPU 21 checks where the head of TITLE_002 is in the stream. That is, how many times the start time of TITLE_002 corresponds to the offset time (time stamp) in the stream is calculated, and then the playback start point immediately before the start time is specified using the feature point information in the CHUNK file. . As a result, the offset distance from the beginning of the file at the playback start point can be determined.

  Next, the CPU 21 determines a physical address on the optical disc 1 in which “CHUNK — 0001.MPEG2” is recorded and its length by using a file system operation instruction that is incorporated in the processing program in advance. Further, the reproduction start point offset address obtained previously is added to this address, and the reproduction start point address of TITLE_002 is finally determined.

  Subsequently, the CPU 21 moves the optical head 2 to the reading position based on the address information of “CHUNK — 0001.MPEG2”. Then, the CPU 21 sets the optical head 2, the RF and demodulation / modulation circuit 3, and the ECC circuit 4 to the read mode, switches the switch 5 to the read channel buffer 6 side, and finely adjusts the position of the optical head 2. Then, reading by the optical head 2 is started. As a result, the contents of “CHUNK — 0001.MPEG2” are accumulated in the read channel buffer 6.

  The data stored in the read channel buffer 6 is output to the decoder 7 and subjected to decoding processing to output a video signal and an audio signal. When the amount of data read, decoded and displayed from the optical disc 1 becomes equal to the size of “CHUNK — 0001.MPEG2”, the CPU 21 proceeds to playback of TITLE — 003. The playback operation of TITLE_003 is the same as the playback operation of TITLE_002.

  When the reproduction of the registered title is completed or when an instruction to stop the reading operation is given, the reading and decoding processes are stopped.

  When a new disk is inserted as the optical disk 1 in the optical disk apparatus or when a disk with a different format is inserted, the CPU 21 reads VOLUME.TOC and ALBUM.STR when the disk is inserted. That said, no such file exists on these disks. In such a case, that is, when VOLUME.TOC and ALBUM.STR cannot be read, the CPU 21 outputs a message and asks the user for an instruction. The user instructs the CPU 21 to eject the optical disc 1 (for example, if it is a disc with a different format), initialize it (for example, if it is a new disc of the same format), or restore the data by some method (For example, when the disks are of the same format but the data is destroyed).

  Next, the title will be further described. As shown in FIG. 15, TITLE _ ###. VDR is a file for storing title information. Information about one title is recorded in one title_info (). The number of title_info () existing in TITLE _ ###. VDR is one. Therefore, there are as many TITLE _ ###. VDRs as there are titles in volume.

  The title number is not defined in title_info () in FIG. 16, but is determined by the file name or file id. Therefore, a positive integer ### in TITLE _ ###. VDR represents the title number. The title is a part of the range from the title index representing the start point to the title index representing the beginning of the next title, or the end point of the chunkgroup, rather than the structure.

  As shown in FIG. 36, file_type_id of TITLE _ ###. VDR in FIG. 15 is an id indicating that title_info () is recorded, and is represented by a character string of length 16. text_block () is an area for storing various texts, and only text items permitted to be used in the text_block () are described.

  As shown in FIG. 16, title_info () is an area in which title start and end points and other attributes related to the title are written on the chunkgroup. Also, title_info () can have a flag indicating whether seamless playback can be guaranteed between titles when playback is performed in the order of title numbers. With this flag, it is possible to know in advance whether or not the titles can be seamlessly reproduced by the optical disc apparatus, and whether or not the arrangement needs to be changed at the time of merging.

  Since the title boundary can also be a file boundary, seamless playback may not be guaranteed. However, as a function of the optical disk apparatus, it is possible to make a state in which seamless reproduction is generally performed by performing rearrangement or the like.

  Title_info_length in title_info () in FIG. 16 represents the length of title_info () in bytes. In flags_for_title, the write attribute of the corresponding title, write (change permission), playback count limit, rating level, and the like are recorded. In cgit_file_id, file_id of chunkgroup information file (CHUNKGROUP _ ###. CGIT) which is the base of the corresponding title is recorded.

  In title_start_chunk_group_time_stamp, the playback start time of the title on the local time axis defined by chunkgroup is recorded. The display time of the picture indicated by the title index of the title is this value. The title_end_chunk_group_stamp records the playback end time of the title on the local time axis defined by chunkgroup. This value is the same as the value indicated by titleindex indicating the chunkgroup playback end point or the start point of the title located immediately after on the time axis.

  In title_playback_time (), the playback time (time code value or number of frames or fields) of the title is recorded. In number_of_marks, the total number of all marks set in the title (excluding titleindex) is recorded. In mark_type, as shown in FIG. 37, the type of mark attached at an arbitrary position in the title is recorded. mark is also used as a random access point in the title. In mark_chunk_group_time_stamp, time stamps at locations where the mark is set are recorded in order from the smallest value on the time axis of the chunkgroup. There must not be more than one mark with the same time stamp value. An index having the same time stamp as the start point and end point of title may exist. In stuffing_bytes, bytes to be stuffed are recorded, and the length is 8 × n bits (n> = 0).

  Next, the chunkgroup and chunk shown in FIGS. 21 to 24 will be further described. CHUNKGROUP _ ###. CGIT is a file that describes the definition of the time axis of the title, the configuration of the chunk, and the processing of the discontinuous points included in the title.

  The title is composed of various bitstreams, and may be a stream without video or a DV (digital video) bitstream. In the DV format, the time axis is defined in units of frames, and when the STC (System Time Clock) of MPEG2 video is used as a standard, the format is different, and thus this DV bitstream cannot be managed.

  Therefore, a local time axis is set in the title. This time axis does not depend on the streams that make up the title. The title boundary is set independently of the chunk boundary. Therefore, the local time axis is set for chunks containing multiple (arbitrary numbers) titles rather than for each chunk (corresponding to bitstream one to one) or for each title. It is appropriate to set. A collection of chunks is a chunkgroup.

  In chunkgroup, a single time axis is defined, and the chunk display time is determined by pasting the chunk on top of it. That is, chunks are arranged in the chunkgroup in a state where the contents (byte string) of the bitstream file are expanded on the time axis. A path in which all chunks included in one bitstream file are arranged on the time axis is called a path. Multiple paths can be arranged in chunkgroup. Of the paths, a path that defines the playback start time and end time of the chunkgroup is referred to as a main path, and the other paths are referred to as sub paths. The sub path mainly represents an audio chunk or the like additionally recorded later.

  The connection point of chunk does not necessarily match the title boundary, so it is not a title attribute. However, if the relationship between chunks is included in the attributes of each chunk, there may be hierarchical conflicts. Such discontinuous point information is located between the chunk and the title, and is considered to be appropriate to be placed in the chunkgroup hierarchy.

  Summarizing the above, the information that chunkgroup has is information about the arrangement of chunks on the time axis, the playback order of chunks, the discontinuity that occurs at the connection point between the end of the chunk and the start of the next chunk to be played back, etc. is there.

  As shown in FIG. 38, file_type_id of CHUNKGROUP _ ###. CGIT in FIG. 21 is an identifier indicating that the file is CHUNKGROUP _ ###. CGIT, and is represented by a 16-character string according to ISO 646. Is done. In the chunkgroup_time_base_flags, a flag related to the chunkgroup base counter is recorded. In chunkgroup_time_base_offset, the start time of the reference time axis in the chunkgroup is recorded. This value is a value set in a counter that counts up a 90 kHz clock, and is represented by 32 bits. text_block () is an area for storing various texts, and only text items permitted to be used in the text_block () are described.

  As shown in FIG. 22, chunk_connection_info () is a file for recording information on singular points (video switching points, video and audio synchronization, etc.), and specifies the connection status between chunks. Yes. In the singularity between the chunk and the chunk created by editing, it is necessary to change the chunk in the middle of the GOP. Information about such edit points is described here. A chunk cannot belong to more than one chunkgroup.

  In chunk_connection_info_length, the length of chunk_connection_info () is recorded in bytes. In number_of_chunks, the total number of chunks used in the chunkgroup is recorded. As shown in FIG. 39, chunk_sync_play_flag is a flag indicating whether or not two or more chunks need to be played back at the same time, and the value 0 means that one chunk is played back. 1 means simultaneous playback of a plurality of chunks.

  In chunk_arrangement_info () of FIG. 23, the chunk_arrangement_info_length records the information length of each chunk in bytes (length including the first byte of chunk_arrangement_info_length to the last byte of transition_info ()). . In chunk_info_file_id, file_id of the target chunk_info_file is recorded.

In chunk_switch_stream_id, stream_id of a stream that is continuously played back when connected is recorded. As this id, for example, an id for identifying video or audio recorded in the MPEG2 packet header is used. In presentation_start_cg_time_count, a time count value indicating the display start time of the chunk in terms of the time in the chunkgroup is recorded. The display start time of chunk is expressed by a global time stamp defined in the chunkgroup. The corresponding chunk starts to be displayed at this time in the chunkgroup. In presentation_end_cg_count, a time count value indicating the display end time of the chunk in terms of the time in the chunkgroup is recorded. The display end time of chunk is expressed by a global time stamp defined in the chunkgroup.

  As shown in FIG. 40, the original_time_count_type records the time count type used in the stream. For example, in the case of an MPEG2 video stream, the original_time_count_type is “0000”. In number_of_start_original_time_count_extension, when a plurality of time counts are required, the number of time counts indicating newly required start times is recorded. In number_of_end_original_time_count_extension, when a plurality of time counts are required, the number of time counts indicating the newly required end time is recorded. In presentation_start_original_time_count, the time or counter value in the stream corresponding to presentation_start_tg_time_count is recorded. In presentation_end_original_time_count, the time or counter value in the stream corresponding to presentation_end_tg_time_count is recorded.

  An attribute for time_count_extension is recorded in tc_ext_attributes. In this time_count_extension, for example, information such as which stream to apply can be entered. In start_original_time_count_extension, the start time or start counter value necessary for switching the chunk is recorded. This is optional and is used when multiple times or counter values need to be recorded. In end_original_time_count_extension, an end time or an end counter value necessary for switching the chunk is recorded. This is also an option and is used when multiple times or counter values need to be recorded. In transition_info (), information necessary for applying special effects by switching chunks is recorded. For example, chunk designation, switching time, special effect type, and the like are described here.

  As shown in FIG. 24, CHUNK _ %%%%. ABST is a file in which feature points extracted from a bitstream that constitutes a chunk of sub_file number %%%%. In this file, the start byte position, length, attribute, and the like are described for each unit constituting a bitstream such as GOP or Audio frame. GOP information and Audio frame information are collected as one CHUNK _ %%%%. ABST for each chunk (sub-file).

  As shown in FIG. 41, in CHUNK _ %%%%. ABST file_type_id, an identifier indicating that the stream_info () is recorded is recorded as a 16-character string according to ISO 646. .

  As shown in FIG. 42, the info_type records the type of the next stream_info in FIG. Here, the type of stream is specified. In number_of_programs, the number of programs included in an MPEG2 TS (Transport Stream) is recorded. To know this number, it is necessary to read PSI (Program Specific Information). This value is 1 except for TS. In number_of_streams, the number of streams used in the program is recorded. This value is equal to the number of different PIDs (packet identification) in the case of TS. In the case of MPEG streams other than TS, the number of streams having different stream ids is recorded here.

  In stream_identifier, stream id is recorded. In the case of TS, PID is used as stream id.

  As shown in FIG. 43, the slot_unit_type records how to divide the stream when the stream is divided at certain intervals. When the delimiter index such as each frame or field is time, a time stamp value is used. In slot_time_length, a time corresponding to 1 slot is recorded. This value is represented by a time stamp value using a counter that counts a 90 kHz clock. In number_of_slots, the number of slot_info () written in CHUNK _ %%%%. ABST is recorded. In number_of_I_pictures_in_a_slot, the number of I-pictures included in the slot is recorded. This value is an integer of 1 or more and a value of 15 or less. However, the number of I-pictures included in the slot located immediately before the slot starting from the GOPheader may be smaller than this value. This value is used when setting a slot starting with a picture header of an I-picture that is not immediately after the GOPheader.

  Next, the program shown in FIGS. 17 and 18 will be further described. There is only one program () in PROGRAM _ $$$. PGI. There are as many PROGRAM _ $$$. PGI programs in the volume as there are programs. The program number is not defined in program () but is specified by the file name or file id.

  As shown in FIG. 44, in the file_type_id of PROGRAM _ $$$. PGI in FIG. 17, an id indicating that the program () is recorded is recorded as a 16-character string. In text_block (), areas for storing various texts are formed. Only text items that are allowed to be used in the text_block () are described here.

  Various flags related to program are recorded in flags_for_program of program () in FIG. For example, the write attribute, write (change permission), playback frequency limit, rating level, etc. of this program are recorded.

  As shown in FIG. 45, program_status records the attribute of program. The setting of this field is option, but it must be set to “none” if not set.

  In program_playback_time (), the playback time of the program is recorded. In number_of_play_sequences, the number of play_sequences used in the program is recorded. However, in this format example, the value is fixed to 1. That is, in this format example, 1 program = 1ch (channel) playback is performed, so that simultaneous playback of 2 programs can be specified in order to realize 2ch simultaneous playback. If there is no restriction of 1 program = 1ch playback, 2ch simultaneous playback is possible with 1 program. When two play sequences are reproduced simultaneously using multichannel I / O, the optical disc apparatus determines which play sequence is assigned to which output channel.

  In number_of_play_lists, the number of play_lists used in this play sequence is recorded. In this example, the value is 1. In play_list_start_time_stamp_offset, the time in the play sequence counted by the timer starting from the start time of the play sequence is recorded. This value is the start time of the play list. In program, there must be only one play list in the play sequence. The time unit system is 90 kHz (1/90000 seconds is the minimum unit of time). In stuffing_bytes, bytes of stuffing are recorded. The length is 8 × n bits (n> = 0).

  Next, the discontinuous point flag will be further described. Here, the discontinuity point flag means a mark recorded as seamless_connection_flag of play_list () in FIG. 19 or index type 8 shown in FIG. 37.

  A seamless_connection_flag value of 0 means that continuous playback (seamless playback) with the previous play item is not guaranteed or unknown, as shown in FIG. 46, and a value of 1 means seamless playback. Is guaranteed.

  That is, as shown in FIG. 47, when this flag is 0, it is guaranteed that a predetermined play item is reproduced continuously (without interrupting the image or sound) from the immediately preceding play item. . On the other hand, when this flag is 1, a discontinuous portion may occur between the end of the immediately preceding play item and the playback of the next play item.

  Next, a process for recording the title discontinuity flag will be described with reference to the flowchart of FIG. First, in step S1, the user operates the input unit 14 to specify a title to be recorded. At this time, in step S2, when the CPU 21 records the title designated in step S1 on the optical disc 1, the CPU 21 can continuously reproduce the title with respect to the immediately preceding title already recorded. It is determined whether or not. This determination is made in accordance with the capacity of the read channel buffer 6 (the time required for the decoder 7 to decode the capacity data) and the playback time between titles. That is, when the read channel buffer 6 becomes empty before the next title is played back, it is determined that continuous playback is impossible, and when it is not empty, it is determined that continuous playback is possible. .

  If continuous playback is not possible, the process proceeds to step S3, where the CPU 21 controls the OSD control circuit 9, and the title for which recording has been commanded cannot be played back continuously with respect to the title that has already been recorded. That is, a message indicating that a discontinuity occurs between the two is generated. This message is displayed on the display from the synthesis circuit 8 via the output terminal P1.

  The user views this message and operates the input unit 14 to input whether or not to approve the occurrence of the discontinuity. When the user approves the occurrence of the discontinuous point, the CPU 21 sets the index type 8 as an index indicating the discontinuous point among the marks shown in FIG. 37 to the mark_type in the title_info () of FIG. 16 in step S5. Is set, and the position at which the discontinuity is generated is set to relative_time_stamp_in_title in FIG. Note that the position recorded in the relative_time_stamp_in_title (the position at which the discontinuous point is generated) can be an arbitrary position. Therefore, normally, a point that has little influence even when a discontinuity occurs (for example, the beginning of the next title or the end of the previous title) is recorded here.

  Then, the title_info () having such settings is supplied from the RAM 24 to the write channel buffer 11 and stored, and then read out at a predetermined timing to be read from the switch 5, the ECC circuit 4, and the RF Then, the signal is supplied to and recorded on the optical disc 1 via the demodulation / modulation circuit 3 and the optical head 2.

  Next, proceeding to step S6, the CPU 21 determines whether there are other points that cannot be continuously played back in the title. If there are other playback discontinuities, Returning to step S3, the subsequent processing is repeatedly executed. If it is determined that there are no other playback discontinuities in the title, the process ends.

  On the other hand, if it is determined in step S4 that the user has not accepted the occurrence of the discontinuity, the process proceeds to step S7, and the CPU 21 sets the recording position of the already recorded title to a position that can be continuously played back with the title to be recorded. It is determined whether or not it can be changed. If it is determined that the title recording position can be changed, the CPU 21 proceeds to step S8, and changes the recording position of the already recorded title to a position that can be continuously played back with the title to be recorded. Then, it progresses to step S6.

  If it is determined in step S7 that the title recording position cannot be changed, the process proceeds to step S5, and as described above, a discontinuous point is recorded as the mark_type, and the discontinuous point occurrence position is set to relative_time_stamp_in_title. To be recorded.

  After such processing, the recording processing of the title designated in step S1 is executed.

  Next, with reference to the flowchart of FIG. 49, processing when a discontinuous point flag is recorded when a program is created will be described. First, in step S21, the user operates the input unit 14 to specify a title to be included in the program. When this designation is performed, in step S22, the CPU 21 designates a necessary part in the title designated in step S21 by a reproduction start point and a reproduction end point. In response to this designation, the CPU 21 creates a play item (FIG. 20).

  Next, in step S23, the CPU 21 determines whether or not continuous playback is possible with the immediately preceding play item (this determination is also made for the playback time generated between the play item and the play item, and for the read channel). If the continuous reproduction is not possible, the process proceeds to step S24, and the OSD control circuit 9 is controlled to generate a discontinuous point. Is displayed as a message. In response to this message, the user operates the input unit 14 to input whether or not to approve the occurrence of discontinuous points. Therefore, in step S25, the CPU 21 determines whether or not the user has approved the occurrence of the discontinuous point, and if it is determined that the user has approved the occurrence of the discontinuous point, the process proceeds to step S26 and the play is performed. Set seamless_connection_flag of item to 0. As described with reference to FIG. 46, when this flag is 0, it means that continuous reproduction is not guaranteed.

  Next, proceeding to step S27, the CPU 21 determines whether or not the program creation process has been completed. If it is determined that the program has not been completed yet, the CPU 21 returns to step S23 and repeats the subsequent processes. . If it is determined in step S27 that the program creation process has ended, the process ends.

  On the other hand, if it is determined in step S25 that the user does not accept the occurrence of the discontinuity, the process proceeds to step S28, where the CPU 21 changes the recording position (arrangement position) of the target stream on the optical disc 1. Alternatively, it is determined whether or not partial re-recording is possible. If the stream rearrangement process or the partial re-recording is possible, the process proceeds to step S29, and the CPU 21 executes a process of changing the recording position to a position where continuous recording is possible. In this case, the CPU 21 sets a seamless_connection_flag of the play item to 1 in step S30. As described with reference to FIG. 46, 1 of this flag means that continuous reproduction is guaranteed. Then, it progresses to step S27 and the process after it is performed.

  If it is determined in step S28 that the stream rearrangement process or the partial re-recording is impossible, the process proceeds to step S26, and the same process as when the user acknowledges the occurrence of the discontinuous point is executed. The

  If it is determined in step S23 that continuous playback is possible with the immediately preceding play item, the process proceeds to step S30, where 1 is set immediately in the seamless_connection_flag of the play item.

  Next, as described with reference to FIG. 48, processing when playback is instructed when a discontinuity flag is recorded in the title will be described with reference to the flowchart of FIG. First, in step S41, the CPU 21 reads the discontinuous point flag of the designated title. In step S42, the CPU 21 starts the title reproduction process. In step S43, the CPU 21 determines whether or not the title that has started reproduction has ended. If the reproduction of the title has not ended, the process proceeds to step S44, and the CPU 21 determines whether or not the position represented by the discontinuity point flag (relative_time_stamp_in_title) has been reproduced, and determines that it has not been reproduced yet. If yes, the process returns to step S43.

  If it is determined in step S44 that the position represented by the discontinuity flag has been reproduced, the process proceeds to step S45, and the CPU 21 causes the player (in this case, the optical disc apparatus) to continuously reproduce the subsequent portion, so that there is a gap. Determine whether it is necessary. This determination is made based on the amount of data stored in the read channel buffer 6 at that time (the time required for the decoder 7 to decode the amount of data). If the amount of data is sufficient, it is determined that a gap is not necessary, and if the amount of data is insufficient, it is determined that a gap is necessary. When this optical disk apparatus does not require a gap for continuous reproduction of subsequent portions (when data is sufficiently stored in the read channel buffer 6), the process returns to step S43, and the subsequent processing is repeatedly executed. .

  On the other hand, if it is determined in step S45 that the optical disc apparatus needs a gap for reproduction of the subsequent portion (when data is not sufficiently stored in the read channel buffer 6), the process proceeds to step S46. The CPU 21 generates a gap. That is, the CPU 21 continues to write data to the read channel buffer 6 as it is, but interrupts the reading to the decoder 7 and increases the data amount of the read channel buffer 6. Then, the process proceeds to step S47, where it is determined whether or not the subsequent portion can be continuously reproduced. If not, the process returns to step S46 to continue the gap generation process.

  As described above, when a predetermined amount of data is written to the read channel buffer 6 and it is determined in step S47 that the subsequent portion can be continuously reproduced, the process proceeds to step S48, and the CPU 21 The reproduction is continued (decoding by the decoder 7 is resumed). Thereafter, the process returns to step S43, and the subsequent processing is repeatedly executed.

  On the other hand, if it is determined in step S43 that the title has ended, the process proceeds to step S49, and the CPU 21 determines whether or not there is a title to be reproduced next. If there is no next title to be played back, the process ends. On the other hand, if it is determined that there is a title to be reproduced next, the process proceeds to step S50, and the CPU 21 determines whether or not a discontinuity flag exists at the end of the previous title. If it is determined that a discontinuity flag exists at the end of the previously played title, the process proceeds to step S51, and the CPU 21 determines whether the player (optical disc apparatus) needs a gap for playing the next title. judge. When it is determined that a gap is necessary, the process proceeds to step S52, and the CPU 21 executes a gap generation process, and determines whether or not the next title can be reproduced in step S53. If not, the process returns to step S52, and the gap generation process is repeatedly executed.

  If it is determined in step S53 that the next title can be reproduced, the process returns to step S41, and the subsequent processing is repeatedly executed.

  If it is determined in step S50 that there is no discontinuity flag at the end of the previous title, the process returns to step S41, and the subsequent processing is executed. Even if a discontinuity flag exists at the end of the previous title, if it is determined in step S51 that the optical disc apparatus does not require a gap for reproduction of the next title (for the read channel of the optical disc apparatus) If the capacity of the buffer 6 is sufficiently large), the process returns to step S41, and the subsequent processing is executed.

  Next, as shown in FIG. 49, when a program is created, a process when the reproduction of the program is instructed will be described with reference to the flowchart of FIG.

  First, in step S61, the CPU 21 reproduces the first play item constituting the designated program. In step S <b> 62, the CPU 21 determines whether or not the play item has been played back. If the play item has not been finished, the CPU 21 waits until the play item is finished.

If it is determined in step S62 that the play item has been reproduced, the CPU 21 proceeds to step S63 and determines whether or not the next play item exists. If it is determined that the next play item exists, the process proceeds to step S64, and the CPU 21 determines whether or not the seamless_connection_flag of the next play item is 0. When it is determined that this flag is 0 (when seamless playback is not guaranteed), the process proceeds to step S65, and the CPU 21 determines whether or not the optical disc apparatus needs a gap for the next play item playback. If it is determined that a gap is required, the process proceeds to step S66 to execute a gap generation process. In step S67, it is determined whether or not the next play item can be played back.
If it is not yet possible, the process returns to step S66 to repeatedly execute the gap generation process.

  If it is determined in step S67 that the next play item can be played back (when a sufficient amount of data has been written to the read channel buffer 6), the process proceeds to step S68, and the CPU 21 Start the playback process for the next play item. Thereafter, the process returns to step S62, and the subsequent processing is repeatedly executed.

  In step S64, when it is determined that the seamless_connection_flag of the next play item is not 0 (when it is determined to be 1), or in step S65, the optical disc apparatus sets a gap for playback of the next play item. If it is determined that it is not necessary, the processing of step S66 and step S67 is skipped, and the process proceeds to step S68. Then, the reproduction of the next play item is started, and then the process returns to step S62.

  In the above, the case where the present invention is applied to an optical disc apparatus has been described as an example. However, the present invention can also be applied to a case where information is recorded or reproduced on other recording media.

  As a providing medium for providing a user with a computer program for performing the processing as described above, a communication medium such as a network or satellite can be used in addition to a recording medium such as a magnetic disk, a CD-ROM, or a solid memory. .

  According to the present invention, it is determined whether or not data can be continuously reproduced with respect to already recorded data, and processing related to continuous reproduction is executed in accordance with the determination result. Therefore, a recording medium that can ensure compatibility can be realized.

  In addition, since a gap is added corresponding to the continuous reproduction information extracted from the recording medium, compatibility can be ensured regardless of the difference in the buffer capacity of the recording / reproducing apparatus. Therefore, it can suppress that a user misidentifies with a failure of an apparatus.

  The series of processes described above can be executed by hardware, but can also be executed by software. When a series of processes is executed by software, a program constituting the software may execute various functions by installing a computer incorporated in dedicated hardware or various programs. For example, it is installed from a recording medium in a general-purpose personal computer or the like.

  FIG. 16 shows a configuration of an embodiment of a personal computer when the electrical internal configuration of the client PC 14 of FIG. 4 is realized by software. The CPU 101 of the personal computer controls the overall operation of the personal computer. Further, when an instruction is input from the input unit 106 such as a keyboard or a mouse from the user via the bus 104 and the input / output interface 105, the CPU 101 is stored in a ROM (Read Only Memory) 102 correspondingly. Run the program. Alternatively, the CPU 101 reads a program read from the magnetic disk 121, the optical disk 122, the magneto-optical disk 123, or the semiconductor memory 124 connected to the drive 110 and installed in the storage unit 108 into a RAM (Random Access Memory) 103. To load and execute. Thereby, the function of the client PC 14 of FIG. 4 described above is realized by software. Further, the CPU 101 controls the communication unit 109 to communicate with the outside and exchange data.

  As shown in FIG. 16, the recording medium on which the program is recorded is distributed to provide the program to the user separately from the computer, and a magnetic disk 121 (including a flexible disk) on which the program is recorded, By a package medium composed of an optical disk 122 (including compact disc-read only memory (CD-ROM), DVD (digital versatile disk)), a magneto-optical disk 123 (including MD (mini-disc)), or a semiconductor memory 124 In addition to being configured, it is configured by a ROM 102 on which a program is recorded and a hard disk included in the storage unit 108 provided to the user in a state of being preinstalled in a computer.

  In this specification, the step of describing the program recorded on the recording medium is not limited to the processing performed in time series in the order described, but of course, it is not necessarily performed in time series. Or the process performed separately is included.

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

It is a figure explaining the structure of a directory. It is a figure explaining VOLUME.TOC. It is a figure explaining volume_information (). It is a figure explaining volume_attribute (). It is a figure explaining resume (). It is a figure explaining volume_rating (). It is a figure explaining write_protect (). It is a figure explaining play_protect (). It is a figure explaining recording_timer (). It is a figure explaining text_block (). It is a figure explaining language_set (). It is a figure explaining text_item (). It is a figure explaining ALBUM.STR. It is a figure explaining album (). It is a figure explaining TITLE _ ###. VDR. It is a figure explaining title_info (). It is a figure explaining PROGRAM _ $$$. PGI. It is a figure explaining program (). It is a figure explaining play_list (). It is a figure explaining play_item (). It is a figure explaining CHUNKGROUP _ ###. CGIT. It is a figure explaining chunk_connection_info (). It is a figure explaining chunk_arrangement_info (). It is a figure explaining CHUNK _ %%%%. ABST. 1 is a block diagram illustrating a configuration example of an optical disc device to which the present invention is applied. It is a figure explaining the structure of a directory. It is a figure explaining the logical structure of a directory. It is a figure explaining offset. It is a figure explaining the structure of a directory. It is a figure explaining the structure of a directory. It is a figure explaining the logical structure of a directory. It is a figure explaining the structure of a directory. It is a figure explaining the structure of a directory. It is a figure explaining the logical structure of a directory. It is a figure explaining the logical structure of a directory. It is a figure explaining file_type_id. It is a figure explaining mark_type. It is a figure explaining file_type_id. It is a figure explaining chunk_sync_play_flag. It is a figure explaining original_time_count_type. It is a figure explaining file_type_id. It is a figure explaining info_type. It is a figure explaining slot_unit_type. It is a figure explaining file_type_id. It is a figure explaining program_status. It is a figure explaining seamless_connection_flag. It is a figure explaining the meaning of seamless_connection_flag. It is a flowchart explaining the discontinuous point flag recording process of title. It is a flowchart explaining the recording process of the discontinuous point flag at the time of program creation. It is a flowchart explaining the process of the discontinuous point flag at the time of title reproduction. It is a flowchart explaining the process of the discontinuous point flag at the time of program reproduction | regeneration.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Optical disk, 2 Optical head, 3 RF and demodulation / modulation circuit, 4 ECC circuit, 6 Read channel buffer, 7 Decoder, 8 Compositing circuit, 9 OSD control circuit, 10 Encoder, 11 Write channel buffer, 12 Address detection circuit , 13 System controller, 14 Input section, 21 CPU, 22 ROM, 23, 24 RAM

Claims (10)

In a recording medium in which at least video data is recorded divided into a plurality of playback sections,
During playback, when the read channel buffer of the playback device is emptied and the video data cannot be recorded after being changed to a continuously playable position, the video data between the plurality of playback sections A recording medium in which at least information indicating that continuous playback is not possible is recorded as information indicating whether or not playback is continuously possible. 2. The recording according to claim 1, wherein the information indicating whether or not the video data can be continuously played back is a flag indicating whether or not the video data can be played back continuously. Medium.   In a recording medium in which at least video data is recorded divided into a plurality of playback sections,
  During playback, when the read channel buffer of the playback device is empty and the user acknowledges the occurrence of discontinuity, the video data can be played back continuously between the playback sections. As at least information indicating that continuous playback is not possible.
  A recording medium characterized by the above.   The information indicating whether or not the video data can be continuously played back is a flag indicating whether or not the video data can be played back continuously.
  The recording medium according to claim 3.   In a recording device that records at least video data on a recording medium in a plurality of playback sections,
  During playback, when the read channel buffer of the playback device is emptied and the video data cannot be recorded after being changed to a continuously playable position, the video data between the plurality of playback sections Recording means for recording at least information indicating that continuous playback is not possible as information indicating whether or not playback is continuously possible
  A recording apparatus.   The information indicating whether or not the video data can be continuously played back is a flag indicating whether or not the video data can be played back continuously.
  The recording apparatus according to claim 5.   In a recording method of a recording apparatus for recording at least video data on a recording medium divided into a plurality of playback sections,
  During playback, when the read channel buffer of the playback device is emptied and the video data cannot be recorded after being changed to a continuously playable position, the video data between the plurality of playback sections Including a recording step of recording at least information indicating that continuous playback is not possible as information indicating whether or not playback of the video is continuously reproducible
  And a recording method.   In a recording apparatus in which at least video data is recorded in a plurality of playback sections on a recording medium,
  During playback, when the read channel buffer of the playback device is empty and the user acknowledges the occurrence of discontinuity, the video data can be played back continuously between the playback sections. Recording means for recording at least information indicating that continuous reproduction is not possible as information indicating whether or not
  A recording apparatus.   The information indicating whether or not the video data can be continuously played back is a flag indicating whether or not the video data can be played back continuously.
  The recording apparatus according to claim 8.   In a recording method for a recording apparatus in which at least video data is recorded on a recording medium divided into a plurality of playback sections,
  During playback, when the read channel buffer of the playback device is empty and the user acknowledges the occurrence of discontinuity, the video data can be played back continuously between the playback sections. Recording means for recording at least information indicating that continuous reproduction is not possible as information indicating whether or not
  And a recording method.

Images