Digital video recording/playback system with entry point processing function

[0002] This application is a division of application Ser. No. 09/632,937, U.S. Pat. No. 6,360,057, filed on Aug. 4, 2000, which is a division of application Ser. No. 09/564,538, U.S. Pat. No. 6,480,669, filed on May 4, 2000, both of which are incorporated by reference.

[0003] This application is based upon and claims the benefit of priority from the prior Japanese Patent Application No. 11-131475, filed May 12, 1999, the entire contents of which are incorporated herein by reference.

[0004] The present invention relates to an apparatus/method capable of real-time digital recording of a video picture and the like, and a digital information medium (real-time digital video recording/playback system) used in the apparatus/method.

[0005] More particularly, the present invention relates to an apparatus/method which assures a special information storage area on a recordable/reproducible DVD disc (DVD-RAM disc or the like), and uses information stored in that area as needed upon playback, erasure, or the like of a recorded video program.

[0006] Nowadays, DVD video specification that uses MPEG2 (Moving Picture Expert Group 2) in video (moving picture) digital recording/playback, and AC-3 (Digital Audio Compression or Audio Coding 3) in audio digital recording/playback has been settled, and various playback apparatuses (DVD video players) which use that specification are commercially available.

[0007] The DVD video specification supports MPEG2 as a moving picture compression scheme, and AC-3 audio and MPEG audio in addition to linear PCM as an audio recording scheme. Also, the DVD video specification supports sub-picture data for superimposed dialogs, navigation data for playback control such as fastforwarding, rewinding, data search, and the like, and ISO9660 and UDF bridge format for computers.

[0008] Furthermore, recordable DVD discs (recordable/reproducible DVD-RAM/DVD-RW or write-once DVD-R) have been developed, and an environment that allows the development of digital video information recording/playback apparatuses (alternatives to a conventional video cassette tape recorder) using recordable DVD discs is in order.

[0009] Under such circumstances, the DVD-RTR (DVD real-time recording) specification for digitally recording a video picture or the like in real time and playing it back has been proposed, and is settled as a standard.

[0010] However, the number and kinds of program contents recorded tends to increase with increasing recording size of a disc, and it becomes harder for the user to grasp the recorded contents. For this reason, a problem is posed in terms of management of recorded discs.

[0011] It is an object of the present invention to provide an apparatus/method and medium, which allow the user to write or erase a mark (entry point) at an arbitrary recording position of video data, audio data, and the like as if he or she placed a bookmark between pages or at an important position while reading a book.

[0012] In order to achieve the above object, a digital video information medium according to the present invention has a volume space including a management area and data area.

[0013] The data area stores data segmented into one or more objects (RTR_MOV.VRO/VR_MOVIE.VRO, RTR_STO.VRO/VR_STILL.VRO, RTR_STA.VRO/VR_AUDIO.VRO). Each object is comprised of one or more data units (one or more VOBUs form a cell, and one or more cells form video object). Each data unit (VOBU) stores one or more packs (video or audio packs) of video or audio data to be played back within a predetermined time (0.4 to 1.2 sec).

[0014] The management area stores management information (RTR_VMG) used to manage the objects. The management information (RTR_VMG) has program chain information (ORG_PGCI or UD_PGCIT) for designating the playback order of objects. The program chain information (PGCI) includes one or more pieces of program information (PGI) and one or more pieces of cell information (CI). The cell information (CI) contains designation information (M_CI) for designating an object to be played back.

[0015] The designation information (M_CI) records entry point information (M_C_EPI) for designating the playback position in an object.

[0016] The entry point information (M_C_EPI) includes information (PRM_TXTI) that pertains to an entry point.

[0017] In order to achieve the above object, a digital video information recording/playback apparatus according to the present invention records or plays back the contents of the objects (RTR_MOV.VRO/VR_MOVIE.VRO) using a recordable/reproducible medium which has movie cell information (M_CI) in management information (RTR_VMG) for managing objects (RTR_MOV.VRO/VR_MOVIE.VRO) as recorded information.

[0018] The digital video information recording/playback apparatus comprises an entry point setting unit (MPU) for setting a required entry point (M_C_EPI#1 to M_C_EPI#n) in the movie cell information (M_CI); an additional information input unit (MPU) for inputting additional information (information type, information date, text information, and the like in PRM_TXTI) with respect to the entry point (M_C_EPI); and an additional information setting unit (MPU) for setting the additional information in the entry point (M_C_EPI).

[0019] In order to achieve the above object, a digital video information processing method according to the present invention records or plays back the contents of the objects (RTR_MOV.VRO/VR_MOVIE.VRO) using a recordable/reproducible medium which has movie cell information (M_CI) in management information (RTR_VMG) for managing objects (RTR_MOV.VRO/VR_MOVIE.VRO) as recorded information.

[0020] In this digital video information processing method, a required entry point (M_C_EPI#1 to M_C_EPI#n) is set in the movie cell information (M_CI); additional information (information type, information date, text information, and the like in PRM_TXTI) is input with respect to the entry point (M_C_EPI); and the additional information is set in the entry point (M_C_EPI).

[0021] Using the entry point as needed, the user can easily recognize the recorded contents of a disc. Also, using the entry point information, the user can record/play back from a desired position.

[0022] Additional objects and advantages of the invention will be set forth in the description which follows, and in part will be obvious from the description, or may be learned by practice of the invention. The objects and advantages of the invention may be realized and obtained by means of the instrumentalities and combinations particularly pointed out hereinafter.

[0023] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate presently preferred embodiments of the invention, and together with the general description given above and the detailed description of the preferred embodiments given below, serve to explain the principles of the invention.

[0024] FIG. 1 is a view for explaining the structure of a recordable/reproducible optical disc according to an embodiment of the present invention;

[0025] FIG. 2 is a view for explaining the format of digital information recorded on the optical disc shown in FIG. 1;

[0026] FIG. 3 is a view for explaining the data structure of a video object shown in FIG. 2;

[0027] FIG. 4 is a view for explaining the data structure of a dummy pack shown in FIG. 3;

[0028] FIG. 5 is a view for explaining the file structure of digital information recorded on the optical disc shown in FIG. 1;

[0029] FIG. 6 is a view for explaining the data structure of a navigation data file (RTR_VMG) shown in FIG. 5;

[0030] FIG. 7 is a view for explaining the contents of a video manager information table (VMGI_MAT) shown in FIG. 6;

[0031] FIG. 8 is a view for explaining the data structure of a play list search pointer table (PL_SRPT) shown in FIG. 6;

[0032] FIG. 9 is a view for explaining the contents of play list search pointer table information (PL_SRPTI) shown in FIG. 8;

[0033] FIG. 10 is a view for explaining the contents of a play list search pointer (PL_SRP) shown in FIG. 8;

[0034] FIG. 11 is a view for explaining the contents of thumbnail pointer information (THM_PTRI) shown in FIG. 10;

[0035] FIG. 12 is a view for explaining the data structure of a movie AV file information table (M_AVFIT) shown in FIG. 6;

[0036] FIG. 13 is a view for explaining the data structure of movie VOB information (M_VOBI) shown in FIG. 12;

[0037] FIG. 14 is a view for explaining the data structure of time map information (TMAPI) shown in FIG. 13;

[0038] FIG. 15 is a view for explaining the contents of time map general information (TMAP_GI) shown in FIG. 14;

[0039] FIG. 16 is a view for explaining the contents of a time entry (TM_ENT) shown in FIG. 14;

[0040] FIG. 17 is a view for explaining the data structure of a user defined PGC information table (UD_PGCIT) shown in FIG. 6;

[0041] FIG. 18 is a view for explaining the data structure of a text data manager (TXTDT_MG) shown in FIG. 6;

[0042] FIG. 19 is a view for explaining the data structure of PGC information (PGCI; original PGC or user defined PGC information);

[0043] FIG. 20 is a view for explaining the contents of PGC general information (PGC_GI) shown in FIG. 19;

[0044] FIG. 21 is a view for explaining the contents of program information (PGI) shown in FIG. 19;

[0045] FIG. 22 is a view for explaining the data structure of cell information (CI) shown in FIG. 19;

[0046] FIG. 23 is a view for explaining the data structure of movie cell information (M_CI) shown in FIG. 22;

[0047] FIG. 24 is a view for explaining the contents of movie cell general information (M_C_GI) shown in FIG. 23;

[0048] FIG. 25 is a view for explaining the contents of movie cell entry point information (M_C_EPI) shown in FIG. 23;

[0049] FIG. 26 is a view for explaining a use example of primary text information (PRM_TXTI);

[0050] FIG. 27 is a view for explaining a correspondence among programs that form a program set, and program parts that form a play list;

[0051] FIG. 28 is a view for explaining a correspondence between the presentation start times/presentation end times of cells that form a user defined PGC (or original PGC), and the offset addresses for VOBUs of VOBs that form a movie video object (RTR_MOV.VRO/VR_MOVIE.VRO) shown in FIG. 5;

[0052] FIG. 29 is a block diagram for explaining an example of the arrangement of an apparatus (RTR video recorder) for recording a video program or the like in real time and playing it back using the recordable/reproducible optical disc shown in FIG. 1;

[0053] FIG. 30 is a flow chart for explaining an example of recording in the apparatus shown in FIG. 29;

[0054] FIG. 31 is a flow chart for explaining an example of playback in the apparatus shown in FIG. 29;

[0055] FIG. 32 is a flow chart for explaining an example of an entry point enter process in the apparatus shown in FIG. 29;

[0056] FIG. 33 is a flow chart for explaining an example of an automatic entry point enter process (for entering entry points at given time intervals) in the apparatus shown in FIG. 29;

[0057] FIG. 34 is a flow chart for explaining an example of a text information input process in the apparatus shown in FIG. 29;

[0058] FIG. 35 shows an example of a text information input window in the text information input process shown in FIG. 34;

[0059] FIG. 36 is a view for explaining an example of the relationship among recorded video data, entry points, and information (attribute, recording date, and the like) of the recorded video data in an optical disc recorded by the apparatus shown in FIG. 29;

[0060] FIG. 37 is a view for explaining another example of the relationship among recorded video data, entry points, and information (attribute, recording date, and the like) of the recorded video data in an optical disc recorded by the apparatus shown in FIG. 29;

[0061] FIG. 38 is a flow chart showing an example of a playback menu display process in the apparatus shown in FIG. 29;

[0062] FIG. 39 shows an example of a playback menu display window in the playback menu display process shown in FIG. 38;

[0063] FIG. 40 is a flow chart for explaining an example of a text information search process in the apparatus shown in FIG. 29;

[0064] FIG. 41 shows an example of a search keyword input window in the text information search process shown in FIG. 40;

[0065] FIG. 42 shows an example of a search result display window in the text information search process shown in FIG. 40;

[0066] FIG. 43 is a flow chart for explaining an example of a defect enter process in the apparatus shown in FIG. 29;

[0067] FIG. 44 is a view for explaining an example of the relationship between defective portions of recorded video data detected by the process shown in FIG. 43, and entry points;

[0068] FIG. 45 shows a display example of defective portions of recorded video data detected by the process shown in FIG. 43, and their reproduction manners;

[0069] FIG. 46 is a flow chart for explaining an example of a process for entering the priority order of erasure in the apparatus shown in FIG. 29;

[0070] FIG. 47 is a view for explaining an example of the relationship among recorded video data, entry points, and information (attribute, recording date, and the like) of the recorded video data detected by the process shown in FIG. 46;

[0071] FIG. 48 shows a display example of information (recording time, title, thumbnail, last playback date, and the like) of recorded video data detected by the process shown in FIG. 46, and its order of erasure;

[0072] FIG. 49 explains a structure of one stream pack used when a streamer is used for a DVD-RTR recorder;

[0073] FIG. 50 shows details of the inner structure of the stream pack shown in FIG. 49;

[0074] FIG. 51 briefly illustrates entry point relating information with respect to movie cell information (M_CI) used for an RTR recorder;

[0075] FIG. 52 briefly illustrates entry point relating information with respect to still picture cell information (S_CI) used for an RTR recorder; and

[0076] FIG. 53 briefly illustrates entry point relating information with respect to stream cell information (SCI) used for a streamer.

[0077] The arrangement of a medium (DVD recordable/reproducible disc) according to an embodiment of the present invention, the arrangement of a DVD-RTR (DVD real-time recording) recording/playback apparatus (RTR video recorder), and various operations of this apparatus will be explained below with reference to the accompanying drawings.

[0078] FIG. 1 is a view for explaining the structure of optical disc 10 used in the DVD-RTR recording/playback apparatus. As shown in FIG. 1, optical disc 10 has a structure obtained by adhering a pair of transparent substrates 14 respectively having layers 17A and 17B using adhesive layer 20.

[0079] If this disc 10 is a single-layered DVD-RAM (or DVD-RW) disc, first information recording layer 17A is formed of a phase change recording layer, and second information recording layer 17B is formed of a dummy layer (which may also serve as a label of that disc).

[0080] If this disc 10 is a single-sided, two-layered DVD-ROM/RAM disc, first information recording layer 17A is formed of a semi-transparent film (thin metal film or the like) formed with pits, and second information recording layer 17B is formed of a phase change recording layer.

[0081] If this disc 10 is a double-sided, two-layered DVD-RAM (or DVD-RW) disc, both first and second information recording layers 17A and 17B are formed of phase change recording layers.

[0082] Each substrate 14 can be formed of a 0.6-mm thick polycarbonate film, and adhesive layer 20 can consist of a very thin ultraviolet setting resin (around 40 m to 70 m thick). When this pair of 0.6-mm thick substrates 14 are adhered so that layers 17A and 17B contact each other on the surfaces of adhesive layer 20, 1.2-mm thick large-capacity optical disc 10 is obtained.

[0083] Optical disc 10 has center hole 22, and clamp areas 24 used for clamping optical disc 10 upon its rotation are formed around center hole 22 on the two surfaces of the disc. Center hole 22 receives the spindle of a disc motor when disc 10 is loaded into a disc drive (not shown). Optical disc 10 is clamped at its clamp areas 24 by a disc clamper (not shown).

[0084] Optical disc 10 has information areas 25 that can record information such as video data, audio data, and the like around clamp areas 24.

[0085] Each information area 25 has lead-out area 26 on its outer periphery side, and lead-in area 27 on its inner periphery side that contacts clamp area 24. The area between lead-out and lead-in areas 26 and 27 is defined as data recording area 28.

[0086] FIG. 1 also exemplifies the correspondence between each data recording area 28 of optical disc 10 and a data recording track recorded there.

[0087] On each of recording layers 17A and 17B of information areas 25, a recording track is continuously formed in, e.g., a spiral pattern. The continuous track is segmented into a plurality of sectors, which have serial numbers. Various data are recorded on optical disc 10 using these sectors as recording units.

[0088] Data recording area 28 serves as an actual data recording area, and records video data (main picture data) such as a movie or the like, sub-picture data such as superimposed dialogs, menus, and the like, and audio data such as words, effect sounds, and the like as recording/playback information in the form of similar pit trains (physical shapes or phase states that bring about change in optical conditions).

[0089] When optical disc 10 is a double-sided recording RAM disc in which each surface has one recording layer, each of recording layers 17A and 17B can be formed by three layers, i.e., by sandwiching a phase-change recording material layer (e.g., Ge2Sb2Te5) between two zinc sulfide.silicon oxide (ZnS.SiO2) mixture layers.

[0090] When optical disc 10 is a single-sided recording RAM disc in which each surface has one recording layer, recording layer 17A on the side of read-out face 19 can be formed by three layers including the aforementioned phase-change recording material layer. In this case, layer 17B on the side opposite to read-out face 19 need not be an information recording layer but may merely be a dummy layer.

[0091] When optical disc 10 is a one-side read type two-layered RAM/ROM disc, two recording layers 17A and 17B can comprise single phase-change recording layer 17B (on the side farther from read-out face 19; read/write), and single semi-transparent metal reflection layer 17A (on the side closer to read-out face 19; read-only).

[0092] When optical disc 10 is a write-once DVD-R, a polycarbonate substrate is used, gold can be used as a reflection layer (not shown), and an ultraviolet setting resin can be used as a protection layer (not shown). In this case, an organic dye is used in recording layer 17A or 17B. As the organic dyes, cyanine, squarilium, chroconic, and triphenylmenthane dyes, xanthene and quinone dyes (naphthoquinone, anthraquinone, and the like), metal complex dyes (phthalocyanine, porphyrin, dithiol complex, and the like), and so forth can be used.

[0093] Data can be written on such DVD-R disc using a semiconductor laser having a wavelength of 650 nm and an output of around 6 to 12 mW.

[0094] In various types of optical discs 10 described above, read-only ROM information is recorded on the recording layer as an embossed pattern signal. By contrast, no such embossed pattern signal is formed on substrate 14 having a read/write (or write-once) recording layer, and a continuous groove is formed instead. A phase-change recording layer is formed on such groove. In case of a read/write DVD-RAM disc, the phase-change recording layer in land portions is also used for information recording in addition to the groove.

[0095] When optical disc 10 is of one-side read type (independently of one or two recording layers), substrate 14 on the rear side viewed from read-out face 19 need not always be transparent to the read/write laser beam used. In this case, a label may be printed on the entire surface of substrate 14 on the rear side.

[0096] A DVD-RTR recorder/player (to be describe later) can be designed to attain repetitive recording/repetitive playback (read/write) for a DVD-RAM disc (or DVD-RW disc), single recording/repetitive playback for a DVD-R disc, and repetitive playback for a DVD-ROM disc.

[0097] When disc 10 is a DVD-RAM (or DVD-RW), disc 10 itself is stored in cartridge 11 to protect its delicate disc surface.

[0098] When DVD-RAM disc 10 in cartridge 11 is inserted into the disc drive of a DVD-RTR recorder/player (to be described later), disc 10 is pulled out from cartridge 11, is clamped by the turntable of a spindle motor (not shown), and is rotated to face an optical head (not shown).

[0099] On the other hand, when disc 10 is a DVD-R or DVD-ROM, disc 10 itself is not stored in cartridge 11, and bare disc 10 is directly set on the disc tray of a disc drive.

[0100] Recording layer 17 of information area 25 shown in FIG. 1 is formed with a continuous data recording track in a spiral pattern. The continuous track is segmented into a plurality of logical sectors (minimum recording units) each having a given storage size, as shown in FIG. 1, and data are recorded with reference to these logical sectors. The recording size per logical sector is determined to be 2,048 bytes (or 2 kbytes) which are equal to one pack data length (to be described later).

[0101] Data recording area 28 is an actual data recording area, which similarly records management data, main picture (video) data, sub-picture data, and audio data.

[0102] Note that data recording area 28 of disc 10 can be segmented into a plurality of ring-shaped (annular) recording areas (a plurality of recording zones), although not shown. The disc rotational velocity varies in units of recording zones. However, within each zone, a constant linear or angular velocity can be set. In this case, an auxiliary recording area (free space) can be provided for each zone. These free spaces in units of zones may collectively form a reserve area for that disc 10.

[0103] FIG. 2 is a view for explaining the hierarchical structure of information recorded on optical disc 10 shown in FIG. 1.

[0104] In this structure, lead-in area 27 includes an embossed data zone whose light reflection surface has an embossed pattern, a mirror zone whose surface is flat (mirror surface), and a rewritable data zone capable of information rewrites. Lead-out area 26 is also made up of a rewritable data zone capable of information rewrites.

[0105] Data recording area (volume space) 28 is comprised of volume/file management information 70 and data area DA, which can be rewritten by the user.

[0106] Volume/file management information 70 records file information of audio/video data recorded on data area DA, and information that pertains to the entire volume.

[0107] Data area DA can have both areas DA1 and DA3 that record computer data, and audio/video data area DA2 that records video data/audio data and the like. Note that the recording order, recording information size, and the like of computer data and audio/video data are arbitrary. Data area DA can record computer data or audio/video data alone.

[0108] Audio/video data area DA2 includes control information DA21, video object DA22, picture object DA23, and audio object DA24.

[0109] Control information DA21 can include control information required upon executing various processes such as recording (image recording and/or audio recording), playback, edit, search, and the like.

[0110] Video object DA22 can include information of the contents of recorded video data.

[0111] Picture object DA23 can include still image information such as still images, slide images, and the like.

[0112] Audio object DA24 can include information of the contents of recorded audio data.

[0113] Note that video object DA22 is formed by video object set VOBS. This VOBS has contents corresponding to one or more program chains PGC#1 to PGC#k which respectively designate cell playback orders by different methods.

[0114] The embossed data zone of lead-in area 27 records in advance:

[0115] (1) information which pertains to the entire information storage medium: the disc type (a DVD-ROM, DVD-RAM (or DVD-RW), DVD-R, or the like); disc size (12 cm, 8 cm, or the like); recording density; physical sector numbers indicating the recording start/end positions, and the like;

[0116] (2) information which pertains to the recording/playback/erasure characteristics: the recording power and recording pulse width; erase power; playback power; linear velocity upon recording and erasure, and the like; and

[0117] (3) information which pertains to the manufacture of each information storage medium: the manufacturing number and the like.

[0118] The rewritable zone of each of lead-in area 27 and lead-out area 26 includes:

[0119] (4) a field for recording a unique disc name of each information recording medium;

[0120] (5) a test recording field (for confirming recording/erasure conditions); and

[0121] (6) a field for recording management information that pertains to defective fields in data area DA.

[0122] On fields (4) to (6), a DVD-RTR recorder/player (a RTR video recorder or a personal computer with a DVD-RAM drive) can record information.

[0123] When disc 10 is set in the DVD-RTR recorder/player (RTR video recorder), information on lead-in area 27 is read first. Lead-in area 27 records a predetermined reference code and control data in ascending order of sector numbers.

[0124] The reference code in lead-in area 27 is made up of two error correction code blocks (ECC blocks). Each ECC block consists of 16 sectors. These two ECC blocks (32 sectors) are generated by appending scramble data. Upon playing back the reference code appended with the scramble data, filter operation or the like on the playback side is done to play back a specific data symbol (e.g., 172), thus assuring data read precision after that.

[0125] The control data in lead-in area 27 is made up of 192 ECC blocks. This control data field repetitively records the contents for 16 sectors in each block 192 times.

[0126] This control data made up of 16 sectors contains physical format information in the first sector (2,048 bytes), and disc manufacturing information and contents provider information in the subsequent sectors.

[0127] The physical format information contained in the control data includes the following contents.

[0128] That is, the first position describes the version of the DVD format that the recorded information complies with.

[0129] The second position describes the size (12 cm, 8 cm, or the like) of a recording medium (optical disc 10) and minimum read-out rate. In case of a read-only DVD video, 2.52 Mbps, 5.04 Mbps, and 10.08 Mbps are prescribed minimum read-out rates, but other minimum read-out rates are reserved. For example, when an RTR video recorder capable of variable bit rate recording records at an average bit rate of 2 Mbps, the minimum read-out rate can be set to fall within the range from 1.5 to 1.8 Mbps using the reserve field.

[0130] The third position describes the disc structure (the number of recording layers, track pitch, recording layer type, and the like) of the recording medium (optical disc 10). Based on this recording layer type, disc 10 can be identified to be a DVD-ROM, DVD-R, or DVD-RAM (or DVD-RW).

[0131] The fourth position describes the recording density (linear density and track density) of the recording medium (optical disc 10). The linear density indicates the recording length per bit (0.267 μm/bit, 0.293 μm/bit, or the like). On the other hand, the track density indicates the neighboring track spacing (0.74 μm/track, 0.80 μm/track, or the like). The fourth position also includes a reserve field to designate other numerical values as the linear density and track density of a DVD-RAM or DVD-R.

[0132] The fifth position describes the start and end sector numbers and the like of data area (volume space) 28 of the recording medium (optical disc 10).

[0133] The sixth position describes a burst cutting area (BCA) descriptor. This BCA is applied as an option to a DVD-ROM disc alone, and is an area for storing recorded information upon completion of the disc manufacturing process.

[0134] The seventh position describes a free space size of the recording medium (optical disc 10). For example, when disc 10 is a single-sided single-layered recording DVD-RAM disc, information indicating 2.6 GB (or the number of sectors corresponding to this number of bytes) is stored at that position of disc 10. On the other hand, when disc 10 is a double-sided recording DVD-RAM disc, information indicating 5.2 GB (or the number of sectors corresponding to this number of bytes) is stored at that position.

[0135] Other positions are reserved for future use.

[0136] FIG. 3 is a view for explaining the data structure of the video object shown in FIG. 2.

[0137] As shown in FIG. 3, each cell (for example, cell #m) consists of one or more video object units (VOBUs). Each VOBU is constituted as a set (pack sequence) of video packs, sub-picture packs, audio packs, dummy packs, and the like.

[0138] Each of these packs has a predetermined size (2,048 bytes) and serves as a minimum unit for data transfer. The minimum unit for logical processing is a cell, and logical processing is done is units of cells.

[0139] The playback or presentation time of the VOBU corresponds to that of video data made up of one or more picture groups (groups of pictures; to be abbreviated as GOPs) included in the VOBU, and is set to fall within the range from 0.4 sec to 1.2 sec. One GOP is screen data which normally has a presentation time of about 0.5 sec in the MPEG format, and is compressed to play back approximately 15 frame images during this interval. (The VOBU includes an integer number of GOPs except for a special case wherein a gap is produced in the video data flow. That is, the VOBU is normally a video information compression unit synchronous with GOPs.)

[0140] When the VOBU includes video data, a video datastream is formed by arranging GOPs (complying with MPEG) each consisting of video packs, sub-picture packs, audio packs, and the like. However, independently of the number of GOPs, the VOBU is defined with reference to the presentation time of GOPs.

[0141] Note that even playback data consisting of audio data and/or sub-picture data alone is formed using the VOBU as one unit. For example, when the VOBU is formed by audio packs alone, audio packs to be played back in the presentation time of the VOBU to which the audio data belong are stored in that VOBU as in the video object of video data.

[0142] The packs that form each VOBU have similar data structures except for a dummy pack. An audio pack will be taken as an example. As shown in FIG. 3, a pack header is allocated at the beginning of the pack, a packet header and sub-stream ID follow, and audio data is allocated at the end of the pack. In such pack format, the packet header is written with information of presentation time stamp PTS indicating the start time of the first frame in the packet.

[0143] Likewise, a pack that stores real-time recording data can be made up of a pack header, a packet header that can contain PTS information and stuffing bytes as needed, and a data area that stores video, audio, sub-picture, or real-time recording data. At the end of this data area, padding bytes can be appended as needed.

[0144] The pack header can contain data such as a pack start code, system clock reference (SCR), program multiplex rate, pack stuffing length, and the like.

[0145] In a DVD-RTR recorder/player that can record a video program that contains video object DA22 with the structure shown in FIG. 3 on optical disc 10, the user often wants to edit the recording contents after recording. In order to meet such requirement, dummy packs can be appropriately inserted in each VOBU. Each dummy pack can be used to record edit data later.

[0146] The dummy pack shown in FIG. 3 has a data structure shown in FIG. 4. More specifically, one dummy pack 89 is comprised of pack header 891, packet header 892 having a predetermined stream ID, and padding data 893 padded with a predetermined code (insignificant data). Note that packet header 892 and padding data 893 form padding packet 890. The contents of padding data 893 in a non-used dummy pack are not especially significant.

[0147] This dummy pack 89 can be used as needed when the recording contents are to be edited after predetermined image recording is done on disc 10 shown in FIG. 1, and in other cases.

[0148] More specifically, the dummy pack is inserted into each VOBU for the purposes of:

[0149] addition of information to be additionally recorded after image recording (for example, memo information indicating that after-recording information is inserted into an audio pack and replaced by a dummy pack is inserted as sub-picture information into a sub-picture pack and is replaced by a dummy pack);

[0150] compensation of a short size from an integer multiple of 32 kbytes to match the VOBU size with an integer multiple of the ECC block size (32 kbytes); and so forth.

[0151] Also, the dummy pack can be used to store reduced-scale image (thumbnail picture) data which is displayed on a user menu, as needed.

[0152] FIG. 5 is a view for explaining an example of the directory structure of information (data files) recorded on the optical disc shown in FIG. 1 to have the data structure shown in FIG. 2.

[0153] According to the DVD-RTR specification capable of digital real-time recording/playback of a video picture, the contents of a DVD disc are managed using the directory structure shown in FIG. 5, and are saved in accordance with a file system such as ISO9660, UDF, or the like.

[0154] Even when the data structure shown in FIG. 2 is used on the disc/apparatus side, this data structure is invisible to the user. The data structure that the user can actually see is a hierarchical file structure shown in FIG. 5.

[0155] More specifically, directories such as a DVD_RTR directory, VIDEO_TS directory, AUDIO_TS directory, computer data file directory, and the like are displayed on the display screen (not shown) of the root directory by means of menu windows, icons, or the like in correspondence with the types of data recorded on data area DA shown in FIG. 2.

[0156] The DVD_RTR directory shown in FIG. 5 stores file RTR.IFO of navigation data RTR_VMG, file RTR_MOV.VRO/VR_MOVIE.VRO of movie video object RTR_MOV.VOB, file RTR_STO.VRO/VR_STILL.VRO of still picture video object RTR_STO.VOB, file RTR_STA.VRO/VR_AUDIO.VRO of still picture additional audio object RTR_STA.VOB for still pictures, and the like.

[0157] Note that file RTR.IFO stores management information such as a program set, program, entry point, play list, and the like for managing moving picture information.

[0158] File RTR_MOV.VRO/VR_MOVIE.VRO stores recorded moving picture information and its audio information, file RTR_STO.VRO/VR_STILL.VRO stores recorded still picture information and its audio information, and file RTR_STA.VRO/VR_AUDIO.VRO stores after-recording data for a still picture, and the like.

[0159] When a DVD-RTR recorder/player (RTR video recorder) has a function of displaying the directories shown in FIG. 5 and also has a playback function of a DVD video disc (ROM disc), and the DVD video disc is set in its disc drive, the VIDEO_TS directory shown in FIG. 5 is activated. In this case, when the VIDEO_TS directory is opened, the recorded contents of the set disc are further displayed.

[0160] When the DVD-RTR recorder/player has a DVD audio playback function and a DVD audio disc is set in its disc drive, the AUDIO_TS directory shown in FIG. 5 is activated. In this case, when the AUDIO_TS directory is opened, the recorded contents of the set disc are further displayed.

[0161] Furthermore, when the DVD-RTR recorder/player comprises a personal computer with a DVD-RAM drive and has a computer data processing function, and a DVD-RAM (or DVD-ROM) disc that has recorded computer data is set in that disc drive, the computer data directory shown in FIG. 5 is activated. In this case, when the computer data directory is opened, the recorded contents of the set disc are further displayed.

[0162] The user can access the recorded sources of DVD video, DVD video ROM, DVD audio, and computer data (including computer programs) as if he or she were operating a personal computer, while observing a menu screen or window display screen displayed with the directory structure shown in FIG. 5.

[0163] FIG. 6 is a view for explaining the data structure of the navigation data file (RTR_VMG) shown in FIG. 5. RTR video manager RTR_VMG as navigation data is comprised of various kinds of information, as shown in FIG. 6.

[0164] Referring to FIG. 6, RTR video manager information RTR_VMGI describes basic information of recordable/reproducible optical disc (RTR disc) 10 shown in FIG. 1. This RTR_VMGI contains video manager information management table VMGI_MAT and play list search pointer table PL_SRPT.

[0165] RTR_VMGI further contains movie AV file information table M_AVFIT, still picture AV file information table S_AVFIT, original PGC information ORG_PGCI, user defined PGC information table UD_PGCIT, text data manager TXTDT_MG, and manufacturer's information table MNFIT.

[0166] FIG. 7 shows the contents of the video manager information management table (VMGI_MAT) shown in FIG. 6.

[0167] Referring to FIG. 7, VMG identifier VMG_ID describes “DVD_RTR_VMG0” that specifies an RTR_VMG file using an ISO646 character set code.

[0168] RTR_VMG_EA describes the end address of RTR_VMG by a relative byte number from the first byte of RTR_VMG.

[0169] VMGI_EA describes the end address of RTR_VMGI by a relative byte number from the first byte of RTR_VMG.

[0170] VERN describes the version number of the DVD specification for video recording (real-time video recording).

[0171] TM_ZONE describes the time zone of the RTR disc. In the DVD_RTR specification, five different data fields (PL_CREATE_TM, VOB_REC_TM, FIRST_VOB_REC_TM, LAST_VOB_REC_TM, and VOBU_REC_TM) are specified. These five different data fields are generally called REC_TM. REC_TM contains data TZ_TY and TZ_OFFSET. TZ_TY describes a common universal time or local time, and TZ_OFFSET describes a date offset from the common universal time in units of minutes.

[0172] STILL_TM describes the still time of a still picture in units of seconds.

[0173] CHRS describes a character set code used in primary text information. With this CHRS, for example, an ISO8859-1 character set code or shift JIS kanji code can be designated.

[0174] RSM_MRKI describes program chain number PGCN, program number PGN, cell number CN, marker point MRK_PT, and marker creation time MRK_TM. PGCN in this information indicates the number of the program chain where a marker point is present. When a marker is present in an original PGC, PGCN is set at “0”. PGN indicates the number of the program where the marker point is present. When a resume marker is present in a user defined PGC, PGN is set at “0”. indicates the number of a cell where the marker point is present. MRK_PT indicates a marker point in a target cell. When the resume marker is present in a movie cell, MRK_PT describes a presentation time (PTM) using an RTR presentation time description format. MRK_TM describes the time of creation of the marker using an RTR date description format.

[0175] REP_PICTI describes program chain number PGCN, program number PGN, cell number CN, picture point PICT_PT, and representative picture creation time CREAT_TM of the disc.

[0176] PGCN in this information indicates the number of the program chain where a representative picture of the disc is present. The representative picture of the disc is designated by only the pointer in an original PGC. Hence, when this representative picture pointer is present, PGCN is set at “0”. PGN indicates the number of the program where the representative picture of the disc is present. When a resume marker is present in a user defined PGC, PGN is set at “0”. CN indicates the number of a cell where the representative picture of the disc is present. PICT_PT indicates the representative picture of the disc in the target cell. When the representative picture is present in a movie cell, PICT_PT describes the presentation time (PTM) using the RTR presentation time description format. When this representative picture is present in a still picture cell, PICT_PT describes a still picture VOB entry number (S_VOB_ENTN) in a corresponding still picture VOB group (S_VOG). CREAT_TM describes the time of creation of the representative picture of the disc using the RTR date description format.

[0177] M_AVFIT_SA describes the start address of movie AV file information table M_AVFIT shown in FIG. 6 by a relative byte number from the first byte of RTR_VMG.

[0178] S_AVFIT_SA describes the start address of still picture AV file information table S_AVFIT shown in FIG. 6 by a relative byte number from the first byte of RTR_VMG.

[0179] ORG_PGCI_SA describes the start address of original PGC information ORG_PGCI shown in FIG. 6 by a relative byte number from the first byte of RTR_VMG.

[0180] UD_PGCIT_SA describes the start address of user defined PGC information table UD_PGCIT shown in FIG. 6 by a relative byte number from the first byte of RTR_VMG. If UD_PGCIT is not available, UD_PGCIT_SA is set at “0000 0000h”.

[0181] TXTDT_MG_SA describes the start address of text data manager TXTDT_MG shown in FIG. 6 by a relative byte number from the first byte of RTR_VMG. If TXTDT_MG is not available, TXTDT_MG_SA is set at “0000 0000h”.

[0182] MNFIT_SA describes the start address of manufacturer's information table MNFIT shown in FIG. 6 by a relative byte number from the first byte of RTR_VMG. If MNFIT is not available, MNFIT_SA is set at “0000 0000h”.

[0183] FIG. 8 shows the data structure of play list search pointer table PL_SRPT shown in FIG. 6.

[0184] PL_SRPT describes information required for searching and accessing play lists in an RTR disc, and contains play list search pointer table information PL_SRPTI and one or more play list search pointers PL_SRP#1 to PL_SRP#n.

[0185] Each play list is made up of a user defined PGC, and each PL_SRP has a PGC number corresponding to that play list.

[0186] Each play list is specified by play list number PLN assigned thereto. PLNs are assigned to all pointers PL_SRP, and have serial numbers from 1 to 99 (maximum) in the order of one or more pointers PL_SRP described in PL_SRPT.

[0187] The user can identify a specific play list from other ones using PLN. Or the user can identify a specific play list from other ones using text information appended to the play list.

[0188] FIG. 9 shows the contents of play list search pointer table information PL_SRPTI shown in FIG. 8.

[0189] PL_SRP_Ns indicates the number of play list search pointers PL_SRP in PL_SRPT.

[0190] PL_SRPT_EA indicates the end address of play list search pointer table PL_SRPT, which is described by a relative byte number from the first byte of PL_SRPT.

[0191] FIG. 10 shows the contents of play list search pointer PL_SRP shown in FIG. 8.

[0192] Referring to FIG. 10, PL_TY describes the play list type. That is, one of movie, still picture, or hybrid (both movie and still picture) play lists can be specified by the contents (4-byte PL_TYL) of PL_TY.

[0193] PGCN describes the number of corresponding user defined program chain UD_PGC. The maximum value of this PGCN is 99.

[0194] PL_CREATE_TM describes the time of creation of the play list using the RTR date description format. This PL_CREATE_TM can describe year, month, day, hour, minute, and second.

[0195] PRM_TXTI describes primary text information of the play list. This PRM_TXTI consists of 128 bytes, the first 64 bytes of which are used to describe primary text information using ASCII character sets, and the remaining 64 bytes of which are used to describe primary text information using other character sets (shift JIS, ISO8859-15, and the like). Other character set codes are described in VMGI_MAT, and can be used by all pieces of primary text information in the disc. Note that a terminal control code is not described in PRM_TXTI.

[0196] IT_TXT_SRPN describes the number of IT_TXT_SRP of the play list. (Item text IT_TXT will be described later with reference to FIG. 18.)

[0197] THM_PTRI describes information of thumbnail pointer THM_PTR. Thumbnail pointer information THM_PTRI may be optionally set or used in either an RTR recorder and player. If the RTR recorder does not have performance capable of processing THM_PTRI, all pieces of 8-byte THM_PTRI can be set at “FFh”. If the RTR player does not have performance capable of processing THM_PTRI, it may simply ignore THM_PTRI.

[0198] Note that a “thumbnail” means a picture as small as the nail of the thumb, and normally indicates a picture which is obtained by reducing a still picture in a recorded video picture to the thumbnail size.

[0199] FIG. 11 shows the contents of thumbnail pointer information THM_PTRI shown in FIG. 10. Referring to FIG. 11, CN describes the number of a cell where the thumbnail point is present. Also, THM_PT describes the thumbnail point in a target cell.

[0200] When the resume marker is present in a movie cell, THM_PT describes the presentation time (PTM) using the RTR presentation time description format.

[0201] When a thumbnail is present in a still picture cell, THM_PT describes a still picture VOB entry number (S_VOB_ENTN) in a corresponding still picture VOB group (S_VOG).

[0202] FIG. 12 shows the data structure of the movie AV file information table (M_AVFIT) shown in FIG. 6.

[0203] M_AVFIT describes information of a movie AV file (file RTR_MOV.VRO/VR_MOVIE.VRO shown in FIG. 5), and contains movie AV file information table information M_AVFITI, one or more pieces of movie VOB stream information M_VOB_STI#1 to M_VOB_STI#n, and movie AV file information M_AVFI.

[0204] M_AVFI is information of a movie AV file having a predetermined file name (RTR_MOV.VRO/VR_MOVIE.VRO), and contains movie AV file information general information M_AVFI_GI, one or more movie VOB information search pointers M_VOBI-SRP#1 to M_VOBI_SRP#n, and one or more pieces of movie VOB information M_VOBI#1 to M_VOBI#n.

[0205] One movie AV file can contain one or more VOBs, and each VOB has movie VOB information M_VOBI for VOB in M_AVFI. One or more pieces of information M_VOBI in M_AVFI are described in the same order as that of VOB data stored in the movie AV file.

[0206] FIG. 13 shows the data structure of the movie VOB information M_VOBI shown in FIG. 12. As shown in FIG. 13, M_VOBI contains movie VOB general information M_VOBI_GI, seamless information SMLI, audio gap information AGAPI, and time map information TMAPI.

[0207] M_VOBI_GI shown in FIG. 13 contains VOB_TY which describes the type of VOB, VOB_REC_TM which describes the recording time of the start field in VOB using the RTR date description format, VOB_REC_TM_SUB which describes the recording time (sub-second information) of the start field in VOB by the number of video fields, M_VOB_STIN which describes the number of movie VOB stream information, VOB_V_S_PTM which describes the presentation start time of the first video field in VOB using the RTR presentation time description format, and VOB_V_E_PTM which describes the presentation end time of the last video field in the VOB using the RTR presentation time description format.

[0208] VOB_TY includes TE which indicates if that VOB has been temporarily erased, A0_STATUS which indicates the status of audio stream #0, A1_STATUS which indicates the status of audio stream #1, analog protection system APS which indicates the format of analog copy protection or the ON/OFF state of this copy protection, SML_FLG which indicates if VOB is to be played back seamlessly, A0_GAP_LOC which indicates if an audio gap is present in audio stream #0 and the location of the audio gap if it is present, and A1_GAP_LOC which indicates if an audio gap is present in audio stream #1 and the location of the audio gap if it is present.

[0209] VOB_REC_TM is updated to indicate the recording time of the start field of the remaining VOB if the start field of a given VOB is deleted (erased).

[0210] More specifically, “new VOB_REC_TM=old VOB_REC_TM+presentation duration of deleted field”.

[0211] On the other hand, if the presentation duration of the deleted field cannot be displayed in units of seconds (for example, when the presentation duration of the deleted field is 60.5 sec),

[0212] “new VOB_REC_TM+new VOB_REC_TM_SUB=old VOB_REC_TM+old VOB_REC_TM_SUB +presentation duration of deleted field”.

[0213] Since VOB_REC_TM describes the date of video recording, even when audio data has been modified, such modification has no influence on VOB_REC_TM.

[0214] The aforementioned RTR date description format will be briefly explained below. In this format, presentation time PTM is expressed by a PTM base and PTM extension. The PTM base is a value measured using 90 kHz as a unit, and the PTM extension is a value measured using 27 MHz as a unit.

[0215] SMLI shown in FIG. 13 contains VOB_FIRST_SCR which describes SCR (system clock reference) of the first pack of current VOB using the RTR presentation time description format, and PREV_VOB_LAST_SCR which describes SCR of the last pack in previous VOB using the RTR presentation time description format.

[0216] FIG. 14 shows the data structure of the time map information TMAPI shown in FIG. 13. Time map information TMAPI is used upon executing special playback (e.g., cell playback in an order unique to each user using a user defined PGC) and time search.

[0217] Time map information TMAPI includes time map general information TMAP_GI, one or more time entries TM_ENT#1 to TM_ENT#r, and one or more VOBU entries VOBU_ENT#1 to VOBU_ENT#q.

[0218] Each VOBU entry contains information of the size and presentation time of VOBU. The VOBU size is presented in units of sectors (2 kbytes), and the presentation time is presented in units of video fields (one field={fraction (1/60)} sec in NTSC; one field={fraction (1/50)} sec in PAL).

[0219] Since the VOBU size is presented in units of sectors, as described above, VOBU can be accessed using addresses in units of sectors.

[0220] Each VOBU entry includes reference picture size information 1STREF_SZ, VOBU playback time information VOBU_PB_TM, and VOBU size information VOBU_SZ.

[0221] Note that VOBU_PB_TM represents the playback time of VOBU of interest in units of video fields. On the other hand, reference picture size information 1STREF_SZ represents the size of the first reference picture (corresponding to I-picture in MPEG) of VOBU of interest in units of sectors.

[0222] On the other hand, each time entry contains address information (VOBU_ADR) of the corresponding VOBU, and time difference information (TM_DIFF). This time difference information indicates the difference between the playback time designated by the time entry and the VOBU presentation start time.

[0223] Assuming that the time interval (time unit TMU) between two successive time entries is 10 sec, this time entry interval corresponds to 600 fields in, e.g., NTSC video.

[0224] Normally, the “time interval between neighboring VOBUS” is expressed by the number of fields in the VOBU entry. As another method, a “count value from a given VOBU to the next VOBU by a clock counter” may be used to express the “time interval between neighboring VOBUs”.

[0225] For example, the “time interval between neighboring VOBUS” can be expressed by the “difference value between the value of presentation time stamp at the start position of one VOBU and the value of PTS at the start position of the immediately succeeding VOBU”.

[0226] In other words, “the time interval in a specific unit can be expressed by the difference value of the clock counter in that unit”.

[0227] FIG. 15 shows the contents of time map general information TMAP_GI shown in FIG. 14.

[0228] This time map general information TMAP_GI includes TM_ENT_Ns indicating the number of time entries in that time map information, VOBU_ENT_Ns indicating the number of VOBU entries in that time map information, time offset TM_OSF for that time map information, and address offset ADR_OFS of that time map information.

[0229] When a value (10 sec or equivalent) corresponding to 600 fields in NTSC video (or 500 fields in PAL video) is used as time unit TMU, time offset TM_OSF is used to represent the time offset within TMU.

[0230] When the VOBU size is expressed by the number of sectors, address offset ADR_OFS is used to indicate a file pointer from the beginning of an AV file.

[0231] FIG. 16 shows the contents of time entry TM_ENT shown in FIG. 14.

[0232] This time entry TM_ENT includes VOBU_ENTN indicating the number of the corresponding VOBU entry, TM_DIFF indicating the time difference between the presentation start time of VOBU designated by the time entry, and the calculated presentation time, and VOBU_ADR indicating the target VOBU address.

[0233] When time unit TMU is expressed by 600 fields in NTSC (or when time unit TMU is expressed by 500 fields in PAL), the “calculated presentation time” with respect to time entry #j is given by TMU (j−1)+TM_OSF.

[0234] On the other hand, VOBU_ADR indicates the target VOBU address by the total size of VOBUs preceding VOBU of interest when the VOBU size is expressed in units of sectors.

[0235] In the aforementioned data structure, in order to start presentation from the middle of a certain VOBU, that access point must be determined. This access point is assumed to be a time entry point.

[0236] This time entry point is located at a position separated from the position indicated by movie address information of VOBU by the time difference indicated by time difference information TM_DIFF in time entry TM_ENT. This time entry point serves as a special presentation start point (or time search point) indicated by time map information TMAPI.

[0237] FIG. 17 shows the data structure of user defined PGC information table UD_PGCIT shown in FIG. 6.

[0238] UD_PGCIT includes user defined PGC information table information UD_PGCITI, one or more user defined PGCI search pointers UD_PGCI_SRP#1 to UD_PGCI_SRP#n, and one or more pieces of user defined PGC information UD_PGCI#1 to UD_PGCI#n.

[0239] All UD_PGCs are assigned program chain numbers PGCN ranging from 1 to 99 in the description order of UD_PGCI_SRP in UD_PGCIT. This PGCN can specify each PGC.

[0240] UD_PGCITI contains UD_PGCI_SRP_Ns indicating the number of UD_PGCI_SRPS, and UD_PGCIT_EA indicating the end address of UD_PGCIT.

[0241] Note that the maximum value of UD_PGCI_SRP_Ns is set at, e.g., “99”. UD_PGCIT_EA represents the end address of UD_PGCIT by a relative byte number from the first byte of UD_PGCIT.

[0242] UD_PGCI_SRP includes start address UD_PGCI_SA of UD_PGCI. This UD_PGCI_SA represents the start address of UD_PGCI by a relative byte number from the first byte of UD_PGCIT.

[0243] FIG. 18 shows the data structure of text data manager TXTDT_MG shown in FIG. 6.

[0244] TXTDT_MG contains text data information TXTDTI, one or more item text search pointers IT_TXT_SRP#1 to IT_TXT_SRP#n, and one or more item texts IT_TXT.

[0245] TXTDTI includes CHRS that describes a character set code (ISO8859-1 or shift JIS kanji), used in TXTDT_MG, IT_TXT_SRP_Ns that describes the number of pointers IT_TXT_SRP, and TXTDT_MG_EA that describes the end address of TXTDT_MG by a relative byte number from the first byte of TXTDT_MG.

[0246] Each IT_TXT_SRP includes IT_TXT_SA that describes the start address of IT_TXT by a relative byte number from the first byte of TXTDT_MG.

[0247] IT_TXT describes item text by a character code designated by CHRS. The data length (the number of bytes) of IT_TXT changes depending on the text contents.

[0248] FIG. 19 shows the data structure of the PGC information PGCI (information of an original PGC or user defined PGC).

[0249] PGCI contains navigation information for program chain PGC.

[0250] Two different types of program chains, i.e., an original PGC and user defined PGC, are available (see the contents of RTR_VMG shown in FIG. 6). The original PGC has VOB and PGCI. However, the user defined PGC does not have its own VOB, and refers to VOB in the original PGC.

[0251] As shown in FIG. 19, PGC information (PGCI#i) includes PGC general information PGC_GI, one or more pieces of program information PGI#1 to PGI#m, one or more cell information search pointers CI_SRP#1 to CI_SRP#n, and one or more pieces of cell information CI#1 to CI#n.

[0252] Note that the start address of cell information CI can be indicated by CI_SA described by a relative byte number from the first byte of PGCI.

[0253] FIG. 20 shows the contents of PGC general information PGC_GI shown in FIG. 19.

[0254] This PGC_GI contains PG_Ns that describes the number of programs in PGC, and CI_SRP_Ns that describes the number of CI_SRPs in PGC.

[0255] In case of the user defined PGC, PG_Ns is set at “0”. On the other hand, the maximum number of programs PG in the original PGC is “99”, and the maximum number of cells in the PGC is “999”.

[0256] FIG. 21 shows the contents of program information PGI shown in FIG. 19.

[0257] This PGI includes PG_TY which describes the type of program, C_Ns which describes the number of cells in PG, primary text information PRM_TXTI used in PG, search pointer number IT_TXT_SRPTN of IT_TXT where text data corresponds to PG, and thumbnail pointer information THM_PTRI.

[0258] Note that PRM_TXTI is constructed by a 128-byte field, and the first 64 bytes of that field are described by an ASCII character set. When ASCII text is less than 64 bytes, “00h” is written in blank bytes.

[0259] The second 64 bytes of the 128-byte field are used to describe primary text of another character set (e.g., shift JIS or ISO8859-15). Note that the code of “another character set” is described in VMGI_MAT, and is shared by all the pieces of primary text information in the disc.

[0260] Note that a terminal control code that assumes a value ranging from “01h” to “1Fh” is never described in PRM_TXTI.

[0261] THM_PTRI describes information of a thumbnail pointer. That is, THM_PTRI includes CN that describes the number of the cell where the thumbnail pointer is present, and THM_PT that describes the thumbnail point in the target cell.

[0262] When the resume marker is present in a movie cell, THM_PT describes the presentation time (PTM) using the RTR presentation time description format.

[0263] On the other hand, when a thumbnail is present in a still picture cell, THM_PT describes a still picture VOB entry number (S_VOB_ENTN) in a corresponding still picture VOB group (S_VOG).

[0264] THM_PTRI may be optionally set or used in either an RTR recorder or player. When the RTR recorder does not have performance capable of processing THM_PTRI, all the pieces of 8-byte THM_PTRI may be set at “FFh”. On the other hand, when the RTR player does not have performance capable of processing THM_PTRI, it may simply ignore THM_PTRI.

[0265] FIG. 22 shows the data structure of cell information CI shown in FIG. 19. As shown in FIG. 22, there are two kinds of cell information, i.e., movie cell information M_CI and still picture cell information S_CI.

[0266] Information (M_C_EPI) that pertains to the entry point is written in movie cell information M_CI in navigation data file RTR.IFO shown in FIG. 5.

[0267] FIG. 23 shows the data structure of movie cell information M_CI shown in FIG. 22. As shown in FIG. 23, M_CI contains movie cell general information M_C_GI, and one or more pieces of movie cell entry point information M_C_EPI#1 to M_C_EPI#n.

[0268] FIG. 24 shows the contents of movie cell general information M_C_GI shown in FIG. 23.

[0269] That is, M_C_GI contains C_TY which describes the type of cell, M_VOBI_SRPN which describes the number of the movie VOBI search pointer corresponding to VOB of this cell, C_EPI_Ns which describes the number of pieces of cell entry point information, C_V_S_PTM which describes the presentation start time of this cell using the RTR presentation time description format, and C_V_E_PTM which describes the presentation end time of this cell using the RTR presentation time description format.

[0270] Note that C_V_S_PTM and C_V_E_PTM satisfy the following conditions.

[0271] (1) In Case of Cell in Original PGC

[0272] C_V_S_PTM must be set in the first four VOBUs of the corresponding VOB; and

[0273] C_V_S_PTM must be set in the last four VOBUs of the corresponding VOB.

[0274] (2) In Case of Cell in User Defined PGC

[0275] O_C_V_S_PTM≦C_V_S_PTM≦C_V_E_PTM≦O_C_V_E_PTM must hold,

[0276] where O_C_V_S_PTM indicates the presentation start time of an original cell corresponding to VOB referred to by this cell, and O_C_V_E_PTM indicates the presentation end time of an original cell corresponding to VOB referred to by this cell.

[0277] FIG. 25 shows the contents of movie cell entry point information M_C_EPI shown in FIG. 23.

[0278] This M_C_EPI has two types (type 1 and type 2). M_C_EPI of type 1 without any text information is composed of EP_TY and EP_PTM, and M_C_EPI of type 2 with text information is composed of EP_TY, EP_PTM, and PRM_TXTI. FIG. 25 shows M_C_EPI of type 2.

[0279] As shown in FIG. 25, M_C_EPI includes EP_TY that describes the type of entry point, EP_PTM that describes the presentation time of the entry point using the RTR presentation time format, and PRM_TXTI that describes primary text information and the like of the entry point.

[0280] Upon playback, the value EP_PTM and cell playback time are converted into file pointers that point to VOBU by the time map TMAP information (see FIGS. 14 to 16), and are also converted into physical addresses by the file system.

[0281] PRM_TXTI in M_C_EPI is constructed by a 128-byte field. The first 64 bytes of that field are used to describe primary text using an ASCII character set. When ASCII text is less than 64 bytes, “00h” fills blank bytes. The latter 64 bytes of the 128-byte field are used to describe primary text of another character set (e.g., shift JIS, ISO8859-15, or the like). Note that “another character set” is described in VMGI_MAT, and is shared by all the pieces of primary text information in the disc.

[0282] Note that a terminal control code that assumes a value ranging from “01h” to “1Fh” is never described in PRM_TXTI.

[0283] EP_TY in M_C_EPI is comprised of 1-byte data including a 2-bit type identification code. If this identification code is “00b”, it indicates that M_C_EPI is of type 1 (empty primary text data or no data); if the code is “01b”, it indicates that M_C_EPI is of type 2 (primary text data).

[0284] This EP_TY has a 6-bit reserved field in addition to the 2-bit type identification code that identifies type 1 or 2. Using some or all the bits of this reserved field, the contents of PRM_TXTI in M_C_EPI can be further specified. (If all the six bits are used, a maximum of 64 different specifications may be made. More than 6 bits may be assigned to this designation code to specify more types.)

[0285] The bits using this reserved field will be referred to as a designation code for designating the contents of the primary text information hereinafter.

[0286] Specific bits in the designation code can designate whether PRM_TXTI in M_C_EPI shown in FIG. 25 is “text information” with “information type” and/or “information date” or “text information” without “information type” and/or “information date”.

[0287] Furthermore, specific bits in the designation code can designate whether PRM_TXTI in M_C_EPI shown in FIG. 25 is “text information” with corresponding “thumbnail information” in addition to “information type” and/or “information date”, or “text information” without “thumbnail information”. (The “thumbnail information” corresponds to, e.g., thumbnail pointer information THM_PTRI shown in FIG. 21.)

[0288] Moreover, specific bits in the designation code can designate whether PRM_TXTI in M_C_EPI shown in FIG. 25 consists of “thumbnail information” alone without any “text information” or “thumbnail information” with “text information”.

[0289] When the designation code (not shown) in EP_TY designates “information type”, “information date”, and “text information” shown in FIG. 25, these pieces of information can be used to express the following contents.

[0290] More specifically, “information type” describes an attribute of the entry point, “information date” describes the date the entry point was entered (recorded on the disc), and “text information” describes additional information (a brief comment of a picture at the entry point) that pertains to the entry point.

[0291] The attributes of the entry point described in “information type” include:

[0292] information type [1]=0, user mark (the user enters an entry point)

[0293] information type [1]=1; set mark (the recorder/player enters an entry point)

[0294] information type [1]=2; defect start mark

[0295] information type [1]=3; defect end mark

[0296] information type [1]=4; presentation start mark

[0297] information type [1]=5; presentation end mark

[0298] information type [1]=6; erasure prohibition mark

[0299] information type [1]=7; another mark (e.g., an instruction from other than the user or recorder/player).

[0300] Note that [1] in information type [1] means the first data field of the information type. If this data field has a 3-bit configuration, information type [1] can express eight different marks.

[0301] Note that information similar to “information type”, and “information date” and/or “text information” in FIG. 25 may be assured in play list search pointer PL_SRP shown in FIG. 10.

[0302] The DVD-RTR system can process text information other than the text managed by text data manager TXTDT_MG shown in FIG. 18. The text information includes primary text information (FIG. 21) described in a program, primary text information (FIG. 10) described in a play list, and primary text information (FIG. 25) described in the selected entry point.

[0303] The user uses such primary text information PRM_TXTI to identify the corresponding recorded contents using a character set such as ASCII, shift JIS, or the like.

[0304] FIG. 26 shows that example. That is, the player (RTR recorder/player) reads out primary text information PRM_TXTI shown in FIG. 21 from disc 10, and displays recording date information of recorded programs (PG1, PG2, PG3, . . . ) on the display panel of the player (this example indicates that recording of program #1 was started from PM 12:30:15).

[0305] When the corresponding primary text information PRM_TXTI is read out from the disc, the player outputs the result on a monitor (television). Before the beginning of playback of the recorded programs (PG1, PG2, PG3, . . . ), brief comments (e.g., “barbecue with family” of PG1, “7th birthday of daughter” of PG2, and the like) of the programs recorded on that disc 10 are displayed on the monitor screen.

[0306] The user can easily select a desired program (e.g., “barbecue with family) from this display. When the user has selected a desired program by operating the cursors of a remote controller (not shown) and has pressed a playback button, playback of program #1 is started.

[0307] Also, the user can similarly make display/user selection/playback operation using primary text information PRM_TXTI (FIG. 10) of a play list, and those using primary text information PRM_TXTI (FIG. 25) of an entry point.

[0308] More specifically, as exemplified in FIG. 27, an entry point (corresponding to a “bookmark” compared to a book) can be set at an arbitrary position of each program, and text such as “barbecue with family” can be stored in primary text information PRM_TXTI (FIG. 25) of that entry point.

[0309] The same applies to a case wherein the user decomposes recorded programs #1 to #4 into arbitrary parts, enters the playback order of decomposed parts in play lists #1 and #2, and sets entry points in the individual parts.

[0310] Furthermore, a short title such as “barbecue with grandma” may be written in primary text information PRM_TXTI (FIG. 10) of each play list.

[0311] FIG. 28 is a view for explaining a correspondence between the presentation start times/presentation end times of cells that form a user defined PGC (or original PGC), and the offset addresses for VOBUs of VOBs that form movie video object RTR_MOV.VRO/VR_MOVIE.VRO shown in FIG. 5.

[0312] Referring to FIG. 28, information PGCI and information M_VOBI are stored in the RTR.IFO file shown in FIG. 5. A VOB as a set of VOBUs corresponding to a PGC as a set of cells is stored in the RTR_MOV.VRO/VR_MOVIE.VRO file shown in FIG. 5.

[0313] Program chain information PGCI of the original PGC shown in FIG. 28 manages the playback method of a program as a set of one or more cells, and each user defined PGC manages the playback method of a set of one or more cells determined by the user.

[0314] The presentation start time and presentation end time of each cell in the original PGC or user defined PGC are converted by time map information TMAPI contained in each M_VOBI#i shown in FIG. 13 into file pointers from the beginning of the VRO file, which point to a given VOBU that stores the corresponding video data or the like, and are further converted into physical addresses by the file system.

[0315] In order to play back each cell, the corresponding VOB number, presentation start time, and presentation end time are described as cell information. Upon playing back each cell, the presentation start and end times are passed on to the corresponding VOBI, are converted into file pointers that point to a VOBU corresponding to the cell playback time using a time map (TMAP) included in the VOBI, and are further converted into physical addresses by the file system, thus accessing a VOB.

[0316] For example, video data (VOBS) recorded in audio/video data area DA2 in FIG. 2 is made up of a set of one or more program chains PGC. Each PGC is a set of programs as sets of one or more cells, and cells to be played back and their order upon forming programs can be determined by the original PGC information or user defined PGC information.

[0317] The playback times of cells and their playback order designated by the original PGC information or user defined PGC information are converted into VOBU addresses that form each of cells to be played back on the basis of the contents (time map TMAP shown in FIG. 28) of time map information TMAPI shown in FIG. 14.

[0318] That is, upon playback based on the original PGC (the cell playback order of the initially recorded state), the addresses of VOBUs within the time band to be played back are obtained via time map information (TMAP) in accordance with the contents of ORG_PGCI shown in FIG. 6, and playback is made in that order.

[0319] On the other hand, upon playback based on a PGC uniquely defined by the user (e.g., when the user has edited the playback order after recording), the addresses of VOBUs within the time band to be played back are obtained via time map information (TMAP) in accordance with the contents of UD_PGCI shown in FIG. 17, and playback is made in that order.

[0320] The cell playback order based on user defined PGC information UD_PGCI can be quite different from that based on original PGC information ORG_PGCI.

[0321] The playback times and the addresses of VOBUs to be played back can correspond to each other with reference to the contents of time entries and VOBU entries in time map information TMAPI shown in FIG. 14.

[0322] FIG. 29 is a block diagram for explaining an example of the arrangement of an apparatus (RTR video recorder) for recording a video program in real time and playing it back using recordable/reproducible optical disc 10 shown in FIG. 1.

[0323] The apparatus main body of the RTR video recorder shown in FIG. 29 is roughly constructed by a disc drive unit (32, 34, and the like) for rotating DVD-RAM or DVD-R disc 10 and reading/writing information on disc 10, encoder unit 50 which constructs the recording side, decoder unit 60 which constructs the playback side, and microcomputer block 30 for controlling the operations of the overall apparatus.

[0324] Encoder unit 50 comprises ADC (analog-to-digital converter) 52, video encoder (V encoder) 53, audio encoder (A encoder) 54, sub-picture encoder (SP encoder) 55, formatter 56, and buffer memory 57.

[0325] ADC 52 receives an external analog video signal+external analog audio signal from AV input section 42, or analog TV signal+analog audio signal from TV tuner 44, or the like. This ADC 52 converts the input analog video signal into digital data at, e.g., a sampling frequency=13.5 MHz and the number of quantization bits=8.

[0326] Likewise, ADC 52 converts the input analog audio signal into digital data at, e.g., a sampling frequency=48 kHz and the number of quantization bits=16.

[0327] When an analog video signal and digital audio signal are input to ADC 52, the digital audio signal passes through ADC 52.

[0328] On the other hand, when a digital video signal and digital audio signal are input to ADC 52, these signals pass through ADC 52.

[0329] A digital video signal component from ADC 52 is supplied to formatter 56 via video encoder (V encoder) 53. Also, a digital audio signal component from ADC 52 is supplied to formatter 56 via audio encoder (A encoder) 54.

[0330] V encoder 53 has a function of converting the input digital video signal into a digital signal compressed at variable bit rate on the basis of the MPEG2 or MPEG1 specifications.

[0331] A encoder 54 has a function of converting the input digital audio signal into a digital signal (or linear PCM digital signal) compressed at fixed bit rate on the basis of the MPEG or AC-3 specifications.

[0332] When a DVD video signal is input from AV input section 42, or when a DVD video signal is broadcasted and is received by TV tuner 44, a teletext signal component in the DVD video signal is input to SP encoder 55. Sub-picture data input to SP encoder 55 is arranged into a predetermined signal format, and is then sent to formatter 56.

[0333] Formatter 56 executes predetermined signal processing of the input video signal, audio signal, sub-picture signal, and the like using buffer memory 57 as a work area, and outputs recording data that matches a predetermined format (file structure) to data processor 36.

[0334] Standard encode process contents for generating the recording data will be briefly explained below. More specifically, when encoder unit 50 shown in FIG. 29 starts an encode process, parameters required for encoding video data and the like are set. Main picture data is pre-encoded using the set parameters to compute optimal code amount distribution for the selected average transfer rate (recording rate). Then, the main picture data is encoded based on the code amount distribution obtained by pre-encoding. At this time, audio data is encoded simultaneously.

[0335] As a result of pre-encoding, if it is determined that the data compression amount is insufficient (a desired video program cannot fall within a DVD-RAM disc or DVD-R disc to be used in recording), and pre-encoding can be re-done (if the source to be recorded is a source that can be repetitively played back such as a video tape, video disc, or the like), main picture data is partially re-encoded, and the previously pre-encoded main picture data portion is replaced by the re-encoded main picture data portion. With a series of processes described above, the main picture and audio data are encoded, and the average bit rate value required for recording can be greatly reduced.

[0336] Analogously, parameters required for encoding sub-picture data are set, and encoded sub-picture data is generated.

[0337] The encoded main picture, audio, and sub-picture data are combined, and are converted into the DVD_RTR video structure.

[0338] The encoded main picture data, audio data, and sub-picture data are segmented into packs each having a predetermined size (2,048 bytes), as shown in FIG. 3. Dummy packs are inserted into these packs, as needed. Note that time stamps such as PTS (presentation time stamp), DTS (decode time stamp), and the like are described in packs other than dummy packs, as needed. As for PTS of sub-picture data, a time arbitrarily delayed from PTS of main picture data or audio data in the identical playback time band can be described.

[0339] Data cells are arranged in units of VOBUs to allow playback in the time code order of data, thus forming a VOB consisting of a plurality of cells. An RTR_MOV.VRO/VR_MOVIE.VRO file that combines one or more VOBs is formatted into the structure shown in FIG. 5.

[0340] Upon digitally copying a DVD playback signal from the DVD video player, since the contents of the cells, program chains, management tables, time stamps, and the like are determined in advance, they need not be created again. (However, upon designing the RTR video recorder to be able to digitally copy a DVD playback signal, the recorder must have copyright protection means such as digital watermarking means and the like.)

[0341] The disc drive unit that reads/writes (records and/or plays back) information to/from DVD disc 10 comprises disc drive 32, temporary storage buffer 34, data processor 36, and system time counter (or system time clock; STC) 38.

[0342] Temporary storage buffer 34 is used to buffer a given amount of data to be written on disc 10 (data output from encoder unit 50) via disc drive 32, and to buffer a given amount of data played back from disc 10 (data input to decoder unit 60) via disc drive 32.

[0343] For example, when temporary storage buffer 34 comprises a 4-Mbyte semiconductor memory (DRAM), it can buffer recording or playback data for approximately 8 seconds at an average recording rate of 4 Mbps. When temporary storage buffer 34 comprises a 16-Mbyte EEPROM (flash memory), it can buffer recording or playback data for approximately 30 seconds at an average recording rate of 4 Mbps. Furthermore, when temporary storage buffer 34 comprises a 100-Mbyte, very small HDD (hard disc), it can buffer recording or playback data for 3 minutes or more at an average recording rate of 4 Mbps.

[0344] Temporary storage buffer 34 can also be used to temporarily store recording information when disc 10 is used up during recording, until that disc 10 is exchanged with a new disc.

[0345] When disc drive 32 uses a high-speed drive (a speed equal to or higher than double speeds), temporary storage buffer 34 can also be used temporarily store readout data exceeding an amount read out from a normal drive per unit time. When temporary storage buffer 34 buffers readout data upon playback, even when an optical pickup (not shown) has caused read errors due to vibration shock or the like, playback data buffered by temporary storage buffer 34 can be used instead, thus preventing the playback picture from being discontinued.

[0346] If an external card slot (not shown in FIG. 29) is provided to the RTR video recorder, the EEPROM can be offered as an option IC card. On the other hand, if an external drive slot or SCSI interface is provided to the RTR video recorder, the HDD can be offered as an option extension drive.

[0347] When a personal computer is used as a DVD video recorder by software (not shown), the free area of a hard disc drive or a main memory of the personal computer itself can be partially used as temporary storage buffer 34 shown in FIG. 29.

[0348] Data processor 36 in FIG. 29 supplies DVD_RTR recording data from encoder unit 50 to disc drive 32, receives a DVD_RTR playback signal played back from disc 10, rewrites management information (some file data in FIG. 5) recorded on disc 10, and deletes data (some or all of files) recorded on disc 10, under the control of microcomputer block 30.

[0349] Microcomputer block 30 includes an MPU (or CPU), a ROM written with control programs and the like, and a RAM which provides a work area required for executing programs.

[0350] The MPU of this microcomputer block 30 (to be also referred to as MPU 30 hereinafter) executes, using its RAM as a work area, an entry point enter process, text information input process, playback menu display process, text information search process (recorded content search process), defect enter process, priority order of erasure enter process, and the like, in accordance with the control programs stored in its ROM.

[0351] In these processes, data (a text input of a short title of the recorded contents or the like) input by the RTR video recorder user is supplied from information input unit 100 to MPU 30. Information input unit 100 can use a keyboard of a personal computer or cursor keys/ten-key pad of a remote controller (not shown).

[0352] Of the execution results of MPU 30, the contents the user of the DVD_RTR video recorder should know are displayed on display unit 48 of the DVD_RTR video recorder. Such message contents are also displayed on a monitor display using on-screen display (OSD), sub-picture data, and the like, as needed.

[0353] Note that the control timings of disc drive 32, data processor 36, and encoder unit 50 and/or decoder unit 60 by MPU 30 can be determined based on time data supplied from STC 38 (video recording/playback are normally executed in synchronism with time clocks from STC 38, but other processes may be executed at timings independently of STC 38).

[0354] Furthermore, MPU 30 can process the recorded dates of individual programs recorded on disc 10, entered dates of entry points, and the like on the basis of time data from timepiece unit 40.

[0355] Decoder unit 60 comprises separator 62 for separating and extracting the respective packs from DVD_RTR playback data with the pack structure shown in FIG. 3, memory 63 used upon executing pack separation and other signal processes, video decoder (V decoder) 64 for decoding main picture data (the contents of video packs) separated by separator 62, sub-picture decoder (SP decoder) 65 for decoding sub-picture data (the contents of sub-picture packs) separated by separator 62, audio decoder (A decoder) 68 for decoding audio data (the contents of audio packs) separated by separator 62, video processor 66 for appropriately mixing sub-picture data from SP decoder 65 with video data output from V decoder 64 to superpose sub-picture data such as menus, highlight buttons, superimposed dialogs, and the like on main picture data, and outputting them, video digital-to-analog converter (V·DAC) 67 for converting the digital video output from video processor 66 into an analog video signal, and audio digital-to-analog converter (A·DAC) 69 for converting the digital audio output from A decoder 68 into an analog audio signal.

[0356] The analog video signal output from V·DAC 67 and the analog audio signal output from A·DAC 69 are supplied to an external component (not shown; a multi-channel stereo system having two to six channels+monitor TV or projector) via AV output section 46.

[0357] OSD data output from MPU 30 is input to video processor 66 in decoder unit 60. The OSD data is superimposed on main picture data, and they are supplied to an external monitor TV connected to AV output section 46. Thus, various kinds of text information are displayed together with main picture data.

[0358] The data processes in the RTR video recorder are roughly categorized into two processes, i.e., a recording process and playback process.

[0359] FIG. 30 is a flow chart for explaining an example of the recording operation in the RTR video recorder shown in FIG. 29.

[0360] Upon receiving an image recording command input by remote controller operation of the user or a timer recording program (not shown), MPU 30 reads management data (file system and the like) from disc 10 (FIG. 1) set in disc drive 32 (step ST10), and determines the recording area (write area).

[0361] If disc 10 has no unrecorded area with a minimum required size or an area that can be erased by overwriting data, i.e., if no free space exists (NO in step ST12), MPU 30 displays an alert message “no space is available for recording” (step ST14), thus stopping recording.

[0362] If a free space exists (YES in step ST12), MPU 30 determines a write address (step ST16), and writes data required for recording (writing) on the determined area in the management area (RTR_VMG file and the like) (step ST18).

[0363] MPU 30 then executes an initial setting process for recording (step ST20). More specifically, MPU 30 sets the average transfer rate (e.g., 4 Mbps) in the respective encoders in encoder unit 50 shown in FIG. 29, resets STC 38 to a predetermined value (e.g., zero), sets a write start address in drive 32, initializes formatter 56 (e.g., for NTSC recording based on MPEG2/4 Mbps), enters dummy packs (FIGS. 3 and 4), sets the segmentation time of cells to be a predetermined value, and sets the number C_EPI_Ns (FIG. 24) of pieces of cell entry point information to zero.

[0364] Upon completion of the aforementioned initial setting process, MPU 30 sets a recording start command in the respective encoders in encoder unit 50 to start recording (step ST22), and starts a record process (step ST23).

[0365] The flow of a video signal in the record process (step ST23) is as follows.

[0366] An AV signal input to external AV input section 42 or a broadcast signal received by TV tuner 44 are A/D-converted by ADC 52. The A/D-converted digital video signal is input to V encoder 53, and the digital audio signal is input to A encoder 54. Also, a closed caption signal or text signal such as teletext or the like contained in the broadcast signal is input from TV tuner 44 to SP encoder 55.

[0367] The respective encoders compress the input signals by a predetermined method and packetize them to have 2,048 bytes per pack, and input packets to formatter 56.

[0368] Note that the respective encoders determine PTS (presentation time stamp or playback time stamp) and DTS (decoding time stamp) of each packet in accordance with the count value from STC 38, as needed, upon recording.

[0369] Formatter 56 temporarily stores packet data in buffer memory 57, then packs the input packet data, mixes them in units of GOPs, and transfers the packs to data processor 36.

[0370] Data processor 36 forms groups of 16 transferred packs (2 kbytes), executes an ECC process of these packs using, e.g., a product code, and sends them to disc drive 32.

[0371] At this time, when disc drive 32 is not ready to record, data processor 36 transfers the recording signal to the temporary storage buffer, and waits until disc drive 32 is ready to record data. When disc drive 32 is ready to record data, drive 32 starts recording.

[0372] In this case, a large-size memory is used as temporary storage buffer 34 so as to store recording data for several minutes or more by high-speed access.

[0373] During the record process, a process for automatically entering entry points at prescribed time intervals (e.g., at 5-sec intervals) is done (step ST25; see FIG. 33). The user can arbitrarily set this entry point entering time interval in units of minutes. If this time interval is set to be longer than the free space (recordable time) of disc 10, no entry points are automatically entered.

[0374] During recording (NO in step ST27), if the user requires entering of an entry point (YES in step ST29), a process for entering an entry point is done (step ST31; see FIG. 31) independently of the process in step ST25.

[0375] For example, when a remote controller (not shown) has an entry point key, and the user has pressed this entry point key during the record process, entry point information (FIG. 25) is entered at a position corresponding to the recorded contents at that time.

[0376] At this time, MPU 30 records entry point information in management information (RTR_VMG file in FIG. 5) in response to the entry point enter request from the user or set (RTR video recorder).

[0377] Upon completion of recording (YES in step ST27), MPU 30 initializes the respective encoders and formatter in encoder unit 50, sends predetermined management information to drive 32, and records it in RTR_VMGI of disc 10 (step ST34).

[0378] FIG. 31 is a flow chart for explaining an example of the playback operation in the RTR video recorder shown in FIG. 29.

[0379] Upon receiving a playback command input by remote controller operation by the user or a timer playback program (not shown), MPU 30 reads the contents of the management area (RTR_VMG) of disc 10 via drive 32 and data processor 26 (step ST40), and determines the playback address.

[0380] MPU 30 selects a program chain and programs to be played back on the basis of the read management data (step ST42), and sets a playback start command in the respective decoders in decoder unit 60 (step ST44).

[0381] MPU 30 then sends the determined playback address and read command to drive 32 and starts a playback process (step ST46).

[0382] Drive 32 reads out sector data of disc 10 (FIG. 1) in accordance with the received read command, and data processor 36 corrects errors of readout data, and outputs the data to decoder unit 60 in the form of pack data.

[0383] In decoder unit 60, separator 62 receives the readout pack data. Separator 62 packetizes the received data, and transfers packets in accordance with the types of data (video data, audio data, sub-picture data, and the like). That is, separator 62 transfers video packet data (MPEG video data) to V decoder 64, audio packet data to A decoder 68, and sub-picture data to SP decoder 65.

[0384] At the beginning of transfer of packet data to the respective decoder, SCR (system clock reference or reference system clock) data is loaded onto STC 38. The respective decoders execute playback processes in synchronism with PTS values (see FIG. 3) in packet data (that is, by comparing PTS and STC values). In this manner, a moving picture with audio and superimposed dialog data, which are synchronous with a video, can be played back.

[0385] If playback from an entry point of a specific cell is required during playback (YES in step ST50), MPU 30 converts EP_PTM (see FIG. 25) of the target entry point into a file pointer with reference to TMAP (see FIG. 14), and accesses a VOBU (see FIG. 28) corresponding to that entry point (step ST52).

[0386] If playback from an entry point is not required (NO in step ST50), the playback process continues.

[0387] If enter of an entry point is required during the playback process (YES in step ST54), a process for entering an entry point can be executed (step ST31). This entry point enter process can have the same contents as that (ST31 in FIG. 30) upon recording.

[0388] If playback is to end (YES in step ST48), MPU 30 waits for completion of playback of the VOBU, playback of which is in progress at that time, and then sets the respective decoders in decoder unit 60 upon stopping decoding (step ST58), thus ending the playback process.

[0389] FIG. 32 is a flow chart for explaining an example of a process executed when recording or playback of the RTR video recorder (recorder/player) is underway, and the user or recorder/player requests enter of an entry point with respect to specific video or audio data. This entry point enter process corresponds to step ST31 in FIG. 30 or 31.

[0390] Upon receiving the entry point enter request from the user or recorder/player (step ST310), MPU 30 of the RTR video recorder (recorder/player) shown in FIG. 29 increments C_EPI_Ns (FIG. 24) in movie cell general information M_C_GI by “1” (step ST312).

[0391] If no entry point enter request is input, C_EPI_Ns is set at “0”.

[0392] Incrementing C_EPI_Ns by “1” means addition of one entry point information in a cell of a program whose recording (or playback) is underway. Hence, MPU 30 assures an area for movie cell entry point information (M_C_EPI) in movie cell information (M_CI).

[0393] Assume that the user has made a text input or the recorder/player has given closed caption data or the like of a broadcast program, air-check of which is underway, as a text input within a predetermined period of time (e.g., within 30 sec) after that (YES in step ST314).

[0394] Note that the text input is not limited to a character input but includes an operation result input when the user has selected a menu item or has clicked a mouse button.

[0395] MPU 30 sets “1” in entry point type EP_TY in movie cell entry point information M_C_EPI (step S316). EP_TY=“1” indicates that M_C_EPI includes primary text information PRM_TXTI.

[0396] Subsequently, MPU 30 reads the current count value of STC 38 and writes the read value in entry point playback time EP_PTM (FIG. 25) in M_C_EPI (step ST320).

[0397] Furthermore, MPU 30 reads the current time (year, month, day, hour, minute, and second) from timepiece unit 40, and writes the read value in an information date (FIG. 25) in primary text information PRM_TXTI in M_C_EPI (step ST322).

[0398] After that, MPU 30 writes the following attribute data (one of 0 to 7) in information type [1] in primary text information PRM_TXTI (step ST324):

[0399] information type [1]=0, user mark (the user enters an entry point)

[0400] information type [1]=1; set mark (the recorder/player enters an entry point)

[0401] information type [1]=2; defect start mark

[0402] information type [1]=3; defect end mark

[0403] information type [1]=4; presentation start mark

[0404] information type [1]=5; presentation end mark

[0405] information type [1]=6; erasure prohibition mark

[0406] information type [1]=7; another mark (e.g., an instruction from other than the user or recorder/player).

[0407] Note that [1] in information type [1] means the first data field of the information type. If this data field has a 3-bit configuration, information type [1] can express eight different attributes; if it has an 8-bit configuration, 256 different attributes.

[0408] More specifically, when the user requests enter of an entry point, information type [1]=0; when the recorder/player, i.e., the RTR video recorder set requests enter of an entry point, information type [1]=1.

[0409] Information type [1]=2 is set for a defect start mark (to be described later), and information type [1]=3 is set for a defect end mark.

[0410] Also, information type [1]=4 is set for a presentation start mark (to be described later), and information type [1]=5 is set for a presentation end mark.

[0411] Information type [1]=6 is set for an erasure prohibition mark (to be described later).

[0412] Furthermore, information type [1]=7 is set when the entry point enter request is sent from a broadcast station during recording of a broadcast program or is sent from a communication partner during downloading of digital video data via a communication line.

[0413] If no text input is made for the entry point in the entry point enter process (NO in step ST314), “0” is set in EP_TY (step ST318).

[0414] MPU 30 sets “0” in EP_TY in movie cell entry point information M_C_EPI (step ST316). EP_TY=“0” indicates that primary text information PRM_TXTI in M_C_EPI is empty.

[0415] In this case, MPU 30 sets PTS in EP_PTM (step ST330), and sets predetermined contents in information type [1] in PRM_TXTI (step ST324), thus ending the entry point enter process.

[0416] FIG. 33 is a flow chart for explaining an example of an automatic entry point enter process (for entering entry points at given time intervals) in the RTR video recorder shown in FIG. 29.

[0417] In this process, entry points are automatically entered at prescribed time intervals (without interrupting recording) irrespective of the contents of video picture or audio data to be recorded.

[0418] Before the start of recording, the user executes an initial setting process. That is, the user sets a numerical value of parameter a which designates the entry point enter interval in units of minutes, and index parameter n is preset to “1” (step ST200).

[0419] If the user does nothing, a predetermined default value (for example, a=5 indicating 5-min intervals, a=0 that prohibits entry points from being automatically entered, or the like) is selected, and n is preset to “1”.

[0420] If recording is started after the initial setting process at the start of recording, the process for entering entry points at prescribed intervals is executed at, e.g., the timing of step ST25 in FIG. 30.

[0421] That is, STC indicating an elapse of recording time is compared with a (n (5400000 (corresponding to an minutes when 90-kHz clocks are used) (step ST250).

[0422] If an minutes (initially, an=5 min) have not elapsed yet after the start of recording (NO in step ST250), the control returns to the record process in step ST23 in FIG. 30.

[0423] If an minutes (an=5 min) have elapsed after the start of recording (YES in step ST250), the entry point enter process with the contents that have been explained with reference to, e.g., FIG. 32 is executed (step ST31).

[0424] If the entry point at that time (when 5 minutes have elapsed after the start of recording) has been entered, index parameter n is incremented by “1” (step ST252), and the control returns to the record process in step ST23 in FIG. 30.

[0425] If an minutes (next, an=10 min) have not elapsed yet after the start of recording (NO in step ST250), the control returns to the record process in step ST23 in FIG. 30.

[0426] If an minutes (an=10 min) have elapsed after the start of recording (YES in step ST250), the entry point enter process with the contents that have been explained with reference to, e.g., FIG. 32 is executed (step ST31).

[0427] The aforementioned processes are repeated until recording is completed. As a result, when a television broadcast program for 54 min is recorded, 10 entry points are automatically recorded at 5-min intervals.

[0428] Note that the RTR video recorder automatically enters entry points at the start of recording, at the end of recording, at the pause of recording, at the start of playback, at the end of playback, at the pause of playback, upon switching video picture data to be recorded, upon switching video audio data to be recorded, and so forth, in addition to the aforementioned process for entering entry points at given time intervals irrespective of recorded contents.

[0429] For example, whether or not the audio level of the recording source has changed (whether or not a predetermined audio level or lower continues for a predetermined period of time) is detected, and an entry point can be automatically entered at that detection position.

[0430] Alternatively, a scene change is detected from a change in MPEG video data in the recording source (when the image contents have changed drastically due to a scene change, since the moving picture compression ratio lowers, the buffer capacity in an MPEG encoder is consumed abruptly within a short period of time), and an entry point can be automatically entered at that detection position.

[0431] FIG. 34 is a flow chart for explaining an example of the text information input process in the RTR video recorder shown in FIG. 29.

[0432] MPU 30 reads management data (RTR_VMG and the like in FIGS. 5 and 6) from disc 10 (step ST100). As a result of reading this data, MPU 30 can detect the play list information contents (FIGS. 8 to 11), PGC information contents (FIGS. 19 to 21), and contents of movie cell information M_CI (FIGS. 23 to 25), as needed.

[0433] MPU 30 reads the contents of movie cell entry point information M_C_EPI of all the entry points from the read management data (step ST102).

[0434] More specifically, MPU 30 selectively extracts entry points with entry point type EP_TY=“01b” (with primary text information PRM_TXTI) from M_C_EPI (FIG. 25) of the individual entry points. Then, MPU 30 reads entry point playback time EP_PTM and primary text information PRM_TXTI from the entry point information with PRM_TXTI. Furthermore, MPU 30 reads the information type, information date, and text information of that entry point from read PRM_TXTI.

[0435] This M_C_EPI read process is repeated if unprocessed entry points still remain (NO in step ST104).

[0436] If all entry points have undergone the M_C_EPI read process (YES in step ST104), MPU 30 outputs input menu information to the monitor on the basis of the read contents (step ST106).

[0437] In this input menu, for example, as shown in FIG. 35, playback times (hour, minute) based on EP_PTM, titles based on text information in PRM_TXTI, thumbnail images based on THM_PTRI (FIG. 10), attributes based on the information types in PRM_TXTI, and mark recording dates (year, month, day, hour, minute, and second) based on the information dates in PRM_TXTI are displayed while being categorized in units of items and are sorted in the order of playback times (or recording times).

[0438] The user moves the cursor to a predetermined line position of a title field in the menu using the cursor keys of a remote controller (not shown), an optional keyboard, or the like, and selects an entry point or points which is or are to undergo text input (step ST108). In this manner, the user can input desired text to a target entry point or points by operating the remote controller or keyboard (step ST110).

[0439] The aforementioned text input is done for all the entry points the user wants (YES in step ST112, ST106 to ST110).

[0440] If the text input is complete for all the entry points the user wants (NO in step ST112), text information (FIG. 25) in PRM_TXTI of M_C_EPI is updated to the contents exemplified in FIG. 35 (step ST114), and the updated data is written in a predetermined area of the management data (RTR_VMG) (step ST116).

[0441] In this fashion, the user inputs his or her desired text information or the like to an entry point or points he or she wants, and the input contents are entered in disc 10 (FIG. 1).

[0442] FIG. 36 depicts a state wherein information exemplified in FIG. 35 has been entered in disc 10 by the processes shown in FIG. 34.

[0443] Referring to FIG. 36, attribute “10” of an entry point at the start of recording (recording time 00′00″) and attribute “10” of an entry point at the end of recording (recording time 02′00″) indicate that the RTR video recorder has automatically entered entry points. Note that the recording date is written on the basis of time data from timepiece unit 40 in FIG. 29, and text “Cinderella” is extracted from closed caption data at the beginning of a broadcast program (broadcast with text) and is automatically written.

[0444] Entry points at three positions of recording times 00′30″, 01′00″, and 01′10″ of the disc indicate overwritten recorded portions in the middle of the recorded program “Cinderella” by user operations. For this reason, the attributes of these entry points are “00” indicating the user mark, and their recording dates are largely different from that of “Cinderella”.

[0445] At each entry point entered by the user, an image (obtained by reducing the I-picture of MPEG) at that position is extracted as a thumbnail, which is entered in THM_PTRI of play list search pointer PL_SRP (FIG. 10) as one entry point data.

[0446] FIG. 37 exemplifies a case wherein the user inputs text at each entry point in place of the thumbnails entered, as shown in FIG. 36, and text information is entered in PRM_TXTI (FIG. 25) of movie cell entry point information M_C_EPI.

[0447] FIG. 38 is a flow chart for explaining an example of the playback menu display process in the RTR video recorder shown in FIG. 29.

[0448] MPU 30 reads management data (RTR_VMG and the like) from disc 10 (step ST700). As a result of reading this data, MPU 30 can detect the play list information contents (FIGS. 8 to 11), PGC information contents (FIGS. 19 to 21), and contents of movie cell information M_CI (FIGS. 23 to 25), as needed.

[0449] MPU 30 reads the contents of movie cell entry point information M_C_EPI of all the entry points from the read management data (step ST702).

[0450] More specifically, MPU 30 selectively extracts entry points with entry point type EP_TY=“01b” (with primary text information PRM_TXTI) from M_C_EPI (FIG. 25) of the individual entry points. Then, MPU 30 reads primary text information PRM_TXTI, and information [1] of that entry point.

[0451] The description contents of this information type [1] are:

[0452] information type [1]=0, user mark (the user enters an entry point)

[0453] information type [1]=1; set mark (the recorder/player enters an entry point)

[0454] information type [1]=2; defect start mark

[0455] information type [1]=3; defect end mark

[0456] information type [1]=4; presentation start mark

[0457] information type [1]=5; presentation end mark

[0458] information type [1]=6; erasure prohibition mark

[0459] information type [1]=7; another mark (e.g., an instruction from other than the user or recorder/player).

[0460] If read information type [1] is “0” (user mark) or “1” (set mark) (YES in step ST703), MPU 30 further reads the information date and text information from primary text information PRM_TXTI (step ST704).

[0461] If read information type [1] is neither “0” nor “1” (NO in step ST703), the control skips step ST704.

[0462] The M_C_EPI information read process (ST702 to ST704) is repeated if unprocessed entry points still remain (NO in step ST706).

[0463] By repeating this process, MPU 30 can fetch all pieces of movie cell information at entry points of the user marks or set marks.

[0464] If all entry points have undergone the M_C_EPI read process (YES in step ST706), MPU 30 outputs playback menu information to the monitor on the basis of the read contents (step ST708).

[0465] In this playback menu, for example, as shown in FIG. 39, playback times (hour, minute) based on EP_PTM, titles based on text information in PRM_TXTI, thumbnail images based on THM_PTRI (FIG. 10), attributes based on the information types in PRM_TXTI, and mark recording dates (year, month, day, hour, minute, and second) based on the information dates in PRM_TXTI are displayed while being categorized in units of items and are sorted in the order of playback times (or recording times).

[0466] The user moves a title select cursor to a desired line position in the playback menu by operating the cursor keys of a remote controller (not shown) and selects an entry point to be played back (step ST710).

[0467] MPU 30 converts the entry point playback time value of the selected entry point into a corresponding file pointer on the basis of time map information (FIGS. 14 to 16) (step ST712). Using this file pointer, the entry point playback time value is converted into a physical address (VOBU address) by the file system, thus starting playback.

[0468] FIG. 40 is a flow chart for explaining an example of the text information search process in the RTR video recorder shown in FIG. 29.

[0469] MPU 30 executes a process for displaying the playback menu used to input a search keyword (step ST400).

[0470] This playback menu for search is used when the user inputs a keyword upon searching information recorded in M_C_EPI (FIG. 25) of respective entry points.

[0471] For example, assume that the user inputs search keywords to search for all entry points which include a character string “Cinderella” in their titles and were marked on January 1999 (step ST402), as shown in FIG. 41.

[0472] MPU 30 reads management data (RTR_VMG) from disc 10, and acquires the contents of movie cell information M_CI of all the recorded entry points (step ST404).

[0473] MPU 30 then extracts M_C_EPI from the acquired information, and reads the information date and text information from PRM_TXTI (FIG. 25) in that information (step ST406).

[0474] MPU 30 searches based on the keywords (to search for entry points which include a character string “Cinderella” and were marked on January 1999) set by the user.

[0475] As a result, if an entry point that is a match to the keywords is found (YES in step ST408), MPU 30 reads information type [1] of that entry point from PRM_TXTI of the entry point (step ST410).

[0476] The description contents of this information type [1] are:

[0477] information type [1]=0, user mark (the user enters an entry point)

[0478] information type [1]=1; set mark (the recorder/player enters an entry point)

[0479] information type [1]=2; defect start mark

[0480] information type [1]=3; defect end mark

[0481] information type [1]=4; presentation start mark

[0482] information type [1]=5; presentation end mark

[0483] information type [1]=6; erasure prohibition mark

[0484] information type [1]=7; another mark (e.g., an instruction from other than the user or recorder/player).

[0485] Based on the contents of read information type [1], entry points with information type [1] other than “1” can be excluded from the search results, and only entry points written by the RTR video recorder upon recording can be left as search results.

[0486] Alternatively, if read information type [1] is “2” (or 2X; X is an arbitrary integer value) or 3 (or 3X), a defect (e.g., ECC error correction failure upon playback or the like) is present at the recording position of the cell corresponding to that entry point, and such entry point can be excluded from search results in some cases.

[0487] If the search is complete and no entry point to be searched remains (YES in step ST412), MPU 30 displays the search results on the monitor, as shown in, e.g., FIG. 42 (step ST414).

[0488] MPU 30 converts the entry point playback time value of each entry point found by search into a corresponding file pointer on the basis of time map information (in FIGS. 14 to 16) (step ST418). Using this file pointer, the entry point playback time value can be converted into a physical address (VOBU address) by the file system, and only an entry point mark portion found by search can be selectively played back.

[0489] FIG. 43 is a flow chart for explaining an example of the defect enter process in the RTR video recorder shown in FIG. 29.

[0490] This defect enter process is executed, for example, when the user wants to check an old disc.

[0491] MPU 30 reads management data (RTR_VMG) (step ST500), and resets a defect flag to “0” (step ST502).

[0492] This defect flag can be set in a given field of the internal RAM or register of MPU 30.

[0493] Then, MPU 30 plays back disc 10 (step ST504). This playback process is the same as that in step ST46 in FIG. 31.

[0494] Initially, the defect flag is “0” (YES in step ST506). During playback, if no defect (ECC error correction failure) is found (NO in step ST508), and playback is not terminated (NO in step ST516), playback is normally continued (loop of steps ST504 to ST516).

[0495] If any defect (ECC error correction failure) is found during playback (YES in step ST508), MPU 30 increments the number C_EPI_Ns (FIG. 24) of pieces of cell entry point information by “1”, sets “1” in entry point type EP_TY (FIG. 25), sets PTS (FIG. 3) at that time in entry point playback time EP_PTM (FIG. 25), and sets current date (date data from timepiece unit 40) in the information date (FIG. 25) in primary text information PRM_TXTI (step ST510).

[0496] Then, MPU 30 sets 2X (X is an arbitrary integer value) in the information type in primary text information PRM_TXTI (step S512). With this information type set with 2X, the defect start point is entered.

[0497] If a defect is found for the first type, 2X of information type is set to be “20”. If the second defect is found, 2X=21; if the third defect is found, 2X=22.

[0498] Upon completion of entering of the defect start points, MPU 30 sets the defect flag at “1” (step ST514).

[0499] If playback is not terminated (NO In step S516), playback continues (step ST504).

[0500] Since the defect flag is set at “1” immediately before continuation of playback (NO in step ST506), the control enters another processing loop in turn.

[0501] The presence/absence of defects (the presence/absence of ECC error correction failures) is checked. If a defect still continues to be detected (YES in step ST518), and playback is not terminated (NO in step S526), MPU 30 transfers data that informs the user that playback of a defective portion is in progress to video decoder 64. Then, alert characters or mark “playback of defective portion now in progress” are displayed on the blue back on the monitor screen (not shown) (step ST528). Alternatively, if I-picture data (free from any defect) immediately before the defect flag is set at “1” remains on a video buffer (not shown) of decoder unit 60, that I-picture data may be transferred to video decoder 64 for the purpose of informing the user that playback of a defective portion is in progress.

[0502] If the defect disappears after the defect flag is set at “1” (ECC error correction has succeeded), that position corresponds to the end point of the defective portion.

[0503] If playback of the defective portion comes to an end, and ECC error correction recovers normal function (NO in step ST518), MPU 30 increments the number C_EPI_Ns (FIG. 24) of pieces of cell entry point information by “1”, sets “1” in entry point type EP_TY (FIG. 25), sets PTS (FIG. 3) at that time in entry point playback time EP_PTM (FIG. 25), and sets current date (date data from timepiece unit 40) in the information date (FIG. 25) in primary text information PRM_TXTI (step ST520).

[0504] MPU 30 then sets 3X (X is an arbitrary integer value) in the information type (FIG. 25) in primary text information PRM_TXTI (step ST522). With the information type set with 3X, the defect end point is entered.

[0505] If a defect is found for the first type, 3X of information type is set to be “30”. If the second defect is found, 3X=31; if the third defect is found, 3X=33.

[0506] Note that 2X (20, 21, 22, . . . ) in step S512 is paired with 3X (30, 31, 32, . . . ) in step ST522. More specifically, a pair of information types “20” and “30” are assigned to the first defect as those of the entry points of the defect start and end points.

[0507] Upon completion of entering of the defect end point, MPU 30 resets the defect flag to “0” (step ST524).

[0508] After that, if playback is not terminated (NO in step S526), playback continues (step ST504).

[0509] Since the defect flag is “0” in this case, the loop of steps ST504 to ST516 is executed until a new defective portion begins to be played back.

[0510] If playback is terminated without any defects (NO in step ST508, YES in step ST516), no information type=2X is entered, and only an information type=3X is entered (step ST522). In this case, entry points do not form any pairs mentioned above. This record shows that no defect is found during playback of the disc.

[0511] FIG. 44 shows an example of entry points when two defects are found by the process shown in FIG. 43.

[0512] If the defect positions of the disc of interest can be detected beforehand based on pairs of information types (contents of PRM_TXTI in FIG. 25) entered in steps ST512 and ST522 in FIG. 43, how to play back such defective portions can also be determined. Hence, a menu that prompts the user to select a defective portion reproduction manner is needed. FIG. 45 shows an example of such defect management menu.

[0513] More specifically, even when the disc of interest has a defect, and suffers many MPEG block noise components (or digital audio data is distorted and sometimes discontinued), if the user wants to play back to confirm the contents of that portion, he or she can select a reproduction manner “incomplete video playback”.

[0514] When a defect is disagreeable to see, the user can select a reproduction manner “skip that portion, and display alert on blue back on monitor”.

[0515] Alternatively, in place of alert display on the blue back, the user may select a reproduction manner “display alert while displaying still image of I-picture immediately before error has occurred as background image”.

[0516] The data that pertain to the reproduction manners can be entered anywhere (e.g., as a kind of information type) in M_C_EPI in FIG. 25.

[0517] FIG. 46 is a flow chart for explaining an example of the process for entering the priority order of erasure in the RTR video recorder shown in FIG. 29.

[0518] MPU 30 reads management data (RTR_VMG and the like) from disc 10 (step ST600). As a result of reading this data, MPU 30 can detect the play list information contents (FIGS. 8 to 11), PGC information contents (FIGS. 19 to 21), and contents of movie cell information M_CI (FIGS. 23 to 25), as needed.

[0519] MPU 30 reads the contents of movie cell entry point information M_C_EPI of all the entry points from the read management data (step ST602).

[0520] More specifically, MPU 30 selectively extracts entry points with entry point type EP_TY=“01b” (with primary text information PRM_TXTI) from M_C_EPI (FIG. 25) of the individual entry points. Then, MPU 30 reads primary text information PRM_TXTI, and information [1] of that entry point.

[0521] The description contents of this information type [1] are:

[0522] information type [1]=0, user mark (the user enters an entry point)

[0523] information type [1]=1; set mark (the recorder/player enters an entry point)

[0524] information type [1]=2; defect start mark

[0525] information type [1]=3; defect end mark

[0526] information type [1]=4; presentation start mark

[0527] information type [1]=5; presentation end mark

[0528] information type [1]=6; erasure prohibition mark

[0529] information type [1]=7; another mark (e.g., an instruction from other than the user or recorder/player).

[0530] If read information type [1] is “4” (presentation start mark) or “6” (erasure prohibition mark) (YES in step ST603), MPU 30 further reads the information date and text information from primary text information PRM_TXTI (step ST604).

[0531] If read information type [1] is neither “4” nor “6” (NO in step ST603), the control skips step ST604.

[0532] The M_C_EPI information read process (ST602 to ST604) is repeated if unprocessed entry points still remain (NO in step ST606).

[0533] By repeating this process, MPU 30 can fetch all pieces of movie cell information at entry points of the presentation start marks or erasure prohibition marks.

[0534] If all entry points have undergone the M_C_EPI read process (YES in step ST606), MPU 30 outputs erasure (or delete) menu information to the monitor on the basis of the read contents (step ST608).

[0535] In this erasure menu, for example, as shown in FIG. 48, playback times (hour, minute) based on EP_PTM, titles based on text information in PRM_TXTI, thumbnail images based on THM_PTRI (FIG. 10), attributes based on the information types in PRM_TXTI, playback dates (year, month, day, hour, minute, and second) based on the information dates in PRM_TXTI, and the erasure order (or erasure prohibition marks) based on information type [0] of PRM_TXTI are displayed while being categorized in units of items and are sorted in the order of playback times (or recording times).

[0536] Note that a pair of information type [0]=4X (erasure start point) and information type [0]=5X (erasure end point) are set as information type [0], as exemplified in the attribute fields of entry points in FIG. 47.

[0537] In information type [0], identical values are written in turn from “0” in pairs of movie cell information, but the same value as that of another pair of movie cell information must not be written.

[0538] For example, in FIG. 47, a recorded video (recording time=15 min from 00′30″ to 00′45″) with a title “peace”, which has a pair of entry point attributes (information type [0]) “40” and “50” has the first erasure order on the erasure menu in FIG. 48, if the remaining size of the disc becomes short during recording, this recorded video with the title “peace” is erased at the very beginning by overwriting another data.

[0539] The user moves the cursor to a predetermined position of an erasure order field in the menu in FIG. 48 using the cursor keys of a remote controller (not shown), an optional keyboard, or the like, and selects entry points, the erasure order of which is to be changed.

[0540] If the user wants to set a lower erasure order of a cell corresponding to the selected entry points (YES in step ST610), he or she decreases the order of information type [0] of each entry point to be changed by “1” (for both entry points with information type [1]=4 and information type [1]=5) (for example, to change the erasure order from the second to the third) (step ST612).

[0541] Conversely, if the user wants to set a higher erasure order, he or she increases the order of information type [0] of each entry point to be changed by “1” (for both entry points with information type [1]=4 and information type [1]=5) (for example, to change the erasure order from the second to the first) (step ST612).

[0542] If the erasure order is not to be changed (NO in step ST610), and erasure is to be prohibited (YES in step ST614), information type [1] of that entry point is set at “6” (erasure prohibition mark) (step ST616).

[0543] Upon completion of the erasure order change or erasure prohibition mark set process (YES in step ST618), management data (RTR_VMG) written with information corresponding to PRM_TXTI shown in FIG. 25 is written in disc 10 (step ST620).

[0544] If the remaining size of disc 10 becomes short during recording, MPU 30 can proceed with recording while erasing some data on disc 10 by overwriting in units of entry points in the erasure order (or in ascending order of recording dates or playback dates if no erasure order is set).

[0545] FIG. 49 shows a stream pack structure used when a streamer is used for the DVD-RTR recorder. As shown in the figure, one stream pack (2048 bytes) is formed of a pack header (14 bytes) and a stream PES packet (2034 bytes).

[0546] The pack header of the stream pack has 14 bytes in size. In this pack header, a pack start code is described in the first 4 bytes (000001Bah). In the next 6 bytes, reference information of system clock reference SCR (SCR_base with 32 bits total) defined by a provider, marker bits, and extension of system clock reference (SCR_extension with 9 bits) are described. In the subsequent 3 bytes (0189C3h), a program multiplexed rate (program_mux_rate with 22 bits) and marker bits are described. In the last 1 byte (F8h), a pack stuffing length (pack_stuffing_length with 3 bits) is described, and a reserved area of 5 bits is further provided.

[0547] The 32nd bit of SCR_base is set to zero. The program_mux_rate is set to 10.08 Mbps.

[0548] In stream recording, an application performs its own stuffing, so that the pack length adjustment methods of DVD-VIDEO or DVD-VR (DVD video recording) need not be used. In stream recording, it is safe to assume that the stream packs will always have the necessary length.

[0549] A stream PES packet of the stream pack has the following data structure.

[0550] FIG. 50 illustrates a structure of the stream data area contained in the stream PES packet shown in FIG. 49.

[0551] As shown, one stream PES packet (2034 bytes) includes a PES header (6 bytes), a substream ID (1 byte), and a stream data area (2027 bytes).

[0552] In the PES packet header of the stream PES packet, a packet start code prefix (packet_start_code_prefix with 24 bits) is recorded at the first 3 bytes (000001h). In the next 1 byte, a stream ID (stream_id=10111111b; indicating private stream 2) is recorded. In the subsequent 2 bytes (07Ech), a PES packet length (PES_packet_length with 16 bits) is recorded, In the last 1 byte, a substream ID (sub-stream-id=00000010b; indicating stream recording data) is recorded.

[0553] The stream data area (2027 bytes) within the stream packet of FIG. 50 includes an application header (9 bytes), an application header extension (optional), a stuffing byte (optional), and an application packet area.

[0554] The application packet area of FIG. 50 contains one or more application packets each of which is associated with an application time stamp.

[0555] At the leading portion of the application packet area, a partial application packet can be recorded. Thereafter, a plurality of pairs of application time stamp ATS and application packet are sequentially recorded. At the trailing portion of the application packet area, another partial application packet can be recorded.

[0556] In other words, at the start of the application packet area, a partial application packet may exist, and at the end of the application packet area, another partial application packet or a stuffing area of reserved bytes may exist.

[0557] The application time stamp (ATS) arranged in front of each application packet has 32 bits in size. An ATS can be divided into two parts, namely a base part and an extension part. The base part holds a 90 kHz unit value, and the extension part holds the less significant value measured in 27 MHz.

[0558] In the structure of FIG. 50, the application header extension may be used to store information that can differ from application packet to application packet. Such information may not be required for all kinds of applications.

[0559] Therefore, a data field of the application header is defined to describe the presence of the optional application header extension in the stream data area.

[0560] At stream recording, the first byte of application time stamp ATS of the first application packet should be aligned to the start of the application packet area in the first stream packet at the beginning of a stream object (SOB).

[0561] Any following stream packets in an SOB may split application packets across stream packet boundaries. The partial application packets in FIG. 50 show examples obtained by the above splitting.

[0562] The byte offset to the first application time stamp that starts in a stream packet, as well as the number of application packets starting in the stream packet, should be described in its application header.

[0563] This mechanism automatically allows for stuffing in front of the first application time stamp and after the last application packet in a stream packet.

[0564] The above automatic mechanism corresponds to said “an application performs its own stuffing” mentioned in the description for FIG. 49.

[0565] The application header extension (optional) is formed of a list of entries, where there is exactly one entry of 1 byte length for each application packet, which starts in this stream packet. These bytes can be used to store information that may differ from application packet to application packet.

[0566] In the 1 byte application header extension (optional), 1 bit AU_START, 1 bit AU_END, and 2 bits COPYRIGHT are described.

[0567] When AU_START is set to “1”, this indicates that the associated application packet contains a random access entry point (start of a random access unit) in the stream.

[0568] When AU_END is set to “1”, this indicates that the associated application packet is the last packet of a random access unit.

[0569] The COPYRIGHT describes the copyright status of the associated application packet.

[0570] FIG. 51 shows entry point relating information with respect to movie cell information M_CI contained in PGCI of the RTR video manager.

[0571] More specifically, movie cell general information M_C_GI contained in M_CI includes the number of cell entry point information C_EPI_Ns (cf. FIG. 24), and movie cell entry point information M_C_EPI contained in M_CI includes entry point type EP_TY, entry point presentation time EP_PTM and primary text information PRM_TXTI (cf. FIG. 25). In this PRM_TXTI, the information type, information date and text information can be described.

[0572] FIG. 52 shows entry point relating information with respect to still picture cell information S_CI contained in PGCI of the RTR video manager.

[0573] More specifically, still picture cell general information S_C_GI contained in S_CI includes the number of cell entry point information C_EPI_Ns, and still picture cell entry point information S_C_EPI contained in S_CI includes entry point type EP_TY, still picture VOB entry number S_VOB_ENTN and primary text information PRM_TXTI. In this PRM_TXTI, the information type, information date and text information can be described.

[0574] FIG. 53 shows entry point relating information with respect to stream cell information SCI contained in PGCI of the RTR stream manager.

[0575] More specifically, stream cell information general information SCI_GI contained in SCI includes the number of stream cell entry point information SC_EPI_Ns, and stream cell entry point information SC_EPI contained in SCI includes entry point type EP_TY, application packet arrival time of entry point EP_APAT and primary text information PRM_TXTI. In this PRM_TXTI, the information type, information date and text information can be described.

[0576] According to the embodiment (real-time digital video recording/playback system) of the present invention, the user can write or erase a mark (entry point) at an arbitrary recording position of video data, audio data, and the like as if he or she placed a bookmark between pages or at an important position while reading a book.

[0577] When information that pertains to the mark (entry point) is recorded at a predetermined position (movie cell entry point information or the like) on a medium (disc), the user can enjoy the following merits using this information upon playing back or recording (including overwrite and erasure).

[0578] 1) An index that indicates programs and their recording positions on a disc can be freely generated.

[0579] That is, when that disc is set in the apparatus, the user can easily know the recorded contents of marked portions (entry points), and can start to play back such portions by simple operation.

[0580] 2) A desired program can be easily found by searching various program recorded on a disc.

[0581] That is, when that disc is set in the apparatus (RTR video recorder), the user can search for titles of the marked portions (entry points) using a keyword. As a result of search, the user can easily know only a desired program of various ones recorded on the disc, and can start to play back that portion by simple operation.

[0582] 3) A portion that can be erased (by overwrite recording) (or a portion that is not to be erased) of various programs recorded on a disc can be easily specified.

[0583] That is, when that disc is set in the apparatus, the user can easily know the priority order of erasure or erasure permission/prohibition of the marked portions (entry points), and can change the priority order of erasure or erasure permission/prohibition of a desired portion by simple operation. A program corresponding to a marked portion which is not prohibited from being erased is automatically erased by overwriting in accordance with the priority order of erasure upon recording new data on that disc.

[0584] 4) When a portion of the recorded disc becomes defective, and cannot be normally played back, the defective portion that cannot be normally played back can be easily specified.

[0585] More specifically, when that disc is set in the apparatus, the user can easily know if the respective marked positions (entry points) suffer defects. If any defect is found, the reproduction manner of that portion (skip a defective portion, display the blue back during playback of a defective portion, play back a still image immediately before a defect until a normal portion is played back, and so forth) can be arbitrarily designated.

[0586] As described above, according to the real-time digital video recording/playback system of the present invention, even when the size of the disc to be recorded increases, the user can easily manage its contents, and can start recording/playback from a position of his or her choice.

[0587] Additional advantages and modifications will readily occur to those skilled in the art. Therefore, the invention in its broader aspects is not limited to the specific details and representative embodiments shown and described herein. Accordingly, various modifications may be made without departing from the spirit or scope of the general inventive concept as defined by the appended claims and their equivalents.