Source: http://www.google.com/patents/US20040213552?dq=6,424,354
Timestamp: 2013-12-06 01:38:25
Document Index: 734637594

Matched Legal Cases: ['art[0', 'art[0', 'art[1', 'art[0', 'art[1', 'art[0', 'art[0', 'art[1', 'art[0', 'art[1']

Patent US20040213552 - Data Transmission Apparatus and Data Transmission Method - Google PatentsSearch Images Maps Play YouTube News Gmail Drive More »Advanced Patent Search | Sign inAdvanced Patent SearchPatentsA data transmitting device and method capable of properly managing the content of data recorded on a recording medium and the reproduced information. Clips (a clip information file and a clip AV stream file) and a play list file are recorded on a recording medium or a copy source. The play list and clip...http://www.google.com/patents/US20040213552?utm_source=gb-gplus-sharePatent US20040213552 - Data Transmission Apparatus and Data Transmission MethodPublication numberUS20040213552 A1Publication typeApplicationApplication numberUS 10/344,957PCT numberPCT/JP2002/006089Publication dateOct 28, 2004Filing dateJun 19, 2002Priority dateJun 22, 2001Also published asCN1310508C, CN1465182A, CN1874243A, CN101902655A, CN101902655B, EP1408686A1, EP1408686A4, US7502543, US20080112685, US20090148123, WO2003001801A1Publication number10344957, 344957, PCT/2002/6089, PCT/JP/2/006089, PCT/JP/2/06089, PCT/JP/2002/006089, PCT/JP/2002/06089, PCT/JP2/006089, PCT/JP2/06089, PCT/JP2002/006089, PCT/JP2002/06089, PCT/JP2002006089, PCT/JP200206089, PCT/JP2006089, PCT/JP206089, US 2004/0213552 A1, US 2004/213552 A1, US 20040213552 A1, US 20040213552A1, US 2004213552 A1, US 2004213552A1, US-A1-20040213552, US-A1-2004213552, US2004/0213552A1, US2004/213552A1, US20040213552 A1, US20040213552A1, US2004213552 A1, US2004213552A1InventorsMotoki KatoOriginal AssigneeMotoki KatoReferenced by (35), Classifications (68), Legal Events (2) External Links: USPTO, USPTO Assignment, EspacenetData Transmission Apparatus and Data Transmission MethodUS 20040213552 A1Abstract A data transmitting device and method capable of properly managing the content of data recorded on a recording medium and the reproduced information. Clips (a clip information file and a clip AV stream file) and a play list file are recorded on a recording medium or a copy source. The play list and clip files are transferred to a recording medium or a copy destination from the copy source recording medium through an IEEEE digital bus and copied. The arrival time stamp of the TP_extra_header of each source packet of the copied clip AV stream file is the same as that of the copy source. The clip information file and the play list file corresponding to the copied clip AV stream file are also copied to the copy destination. The invention can be applied to, for example, a recorder or reproducer for processing an AV stream. Images(67) Claims(27)
[0291] num_of time unit entries[atc _id] indicates the number of entries of time-unit included in the ATC-sequence pointed by atc_id. [0292] SPN time unit_start[atc_id][i] is the address at which i-th time_unit in the ATC-sequence pointed by atc_id starts. This uses a source packet number as unit and is counted from the first source packet in the AV stream with zero being the initial value. [0293] If there is no source packet which is put in the current time_unit, the value of the SPN_time_unit_start for the current time_unit is equal to the value of the SPN_time_unit_start immediately preceding it. [0294] The entries of the value of SPN_time unit start in TU_map must be aligned in the ascending order. [0295] The start time of i-th time_unit in the ATC-sequence pointed by atc_id is TU_start time[atc_id][i] defined by the following equation. TU_start_time[atc_id][i]=offset_arrival_time[atc_id]+i*time_unit_size [0296] The following describes ClipMark( ). [0297] ClipMark( ) defines the information about a mark (Mark) in a Clip AV stream. The mark is provided to specify a highlight or a characteristic time in the Clip. The mark to be attached to the Clip specifies a characteristic scene caused by the contents of the AV stream. For example, this mark includes CM start point, CM end point, or a scene change point. The mark set to Clip is set by the recorder when an AV stream is recorded as a new Clip. It should be noted that each PlayList file has PlayListMark in order to store the mark to be set to the PlayList, which will be described later with the PlayList file. The mark to be set to the PlayList is mainly set by the user. For example, this mark includes a book mark and a resume point. [0298] The setting of the mark to the Clip or the PlayList is performed by adding a time stamp indicative of mark time to ClipMark/PlayListMark. The deletion of the mark is performed by deleting the time stamp of that mark from ClipMark/PlayListMark. Therefore, the setting or deletion of the mark does not affect any AV stream at all. [0299]FIG. 27 shows a relationship between the mark to be set to the Clip and the mark to be set to the PlayList. When the PlayList is reproduced, the mark stored in the ClipMark of the Clip to be referenced by that PlayList can be referenced. Therefore, in the case where one Clip is referenced by a Real PlayList or a plurality of Virtual PlayLists, these PlayLists can share the ClipMark of one Clip, so that the mark data can be efficiently managed. [0300]FIG. 28 shows syntax of ClipMark. [0301] length indicates the number of bytes from the byte immediately after this length field to the last byte of ClipMark( ). [0302] maker_ID indicates a maker ID of a maker which defines that mark_type. [0303] number_of_Clip_marks indicates the number of entries of the mark stored in ClipMark. [0304] mark_invalid_flag is a 1-bit flag and, when this value is set to zero, indicates that this mark has valid information and indicates that this mark is invalid when this value is set to 1. [0305] When user performs an operation to delete the entry of one mark on the user interface, the recorder may change the value of the mark_invalid_flag to 1 instead of deleting the entry of the mark from ClipMark. [0306] mark_type indicates the type of a mark. [0307] ref_to_STC id indicates stc-id which specifies the STC-sequence on which both mark_time_stamp and representative_picture_time_stamp are placed. The value of stc-id is defined in SequenceInfo( ). [0308] mark_time_stamp represents the points at which the marks are specified in the Clip AV stream with a presentation time stamp as the base. [0309] If entry_ES_PID is set to 0�FFFF, its mark is the pointer to the time axis common to all elementary streams in the Clip. [0310] If entry_ES_PID is set to a value other than 0�FFFF, entry_ES_PID indicates the value of PID of a transport packet which includes an elementary stream which is pointed by that mark. [0311] ref_to_thumbnail_index indicates the information about a thumbnail image to be attached to the mark. If the ref_to_thumbnail index field is not 0�FFFF, then that mark is attached with a thumbnail image which is stored in a mark.tdat file. This image is referenced by use of the value of thumbnail_index in a mark.tidx file (which will be described later). If the ref_to_thumbnail_index field is 0�FFFF, then it indicates that no thumbnail image is attached to that mark. [0312] representative_picture_time_stamp stores a time stamp indicative of the point of an image representing the mark indicated by mark_time_stamp. [0313]FIG. 29 shows syntax of a PlayList file. The PlayList file has UIAppInfoPlayList( ), PlayList( ), and PlayListMark( ). [0314] PlayList_start_address indicates the start address of PlayList( ) with the relative number of bytes from the start byte of the PlayList file being the unit. The relative number of bytes is counted from zero. [0315] PlayListMark_start_address indicates the start address of PlayListMark( ) with the relative number of bytes from the start byte of the PlayList file being the unit. The relative number of bytes is counted from zero. [0316] The other syntax fields are not necessary for the description of the embodiments of the invention, so that their descriptions will be skipped. [0317] UIAppInfoPlayList( ) stores the parameters of a user interface application about the PlayList. [0318]FIG. 30 shows syntax of UIAppInfoPlayList( ). [0319] ref_to_thumbnail_index indicates the information about a thumbnail image to be added to the mark. If ref_to_thumbnail index field is not 0�FFFF, then a thumbnail image is attached to that mark and the thumbnail image is stored in a menu.tdat file. The image is referenced by use of the value of thumnail_index in a menu.tidx file (which will be described later). If the ref_to_thumbnail_index field is 0�FFFF, then no thumbnal image is attached to that mark. [0320] The other syntax fields indicate the parameters of the user interface application about the PlayList, but they are not necessary for the description of the embodiments of the invention, so that their descriptions will be skipped. [0321]FIG. 31 shows syntax of PlayList( ). [0322] length indicates the number of bytes from the byte immediately after this length field to the last byte of PlayList( ). [0323] CPI_type is a 1-bit flag indicating the value of CPI_type of the Clip to be used by PlayItem( ). CPI_type is defined by the CPI_type of Clip Information file. [0324] number_of_PlayItems indicates the number of PlayItems( ) in PlayList( ). [0325] In the for-loop of PlayItem_id of the syntax, depending on the order in which PlayItemo appears, the value of PlayItem_id for that PlayItemo is determined. PlayItem_id starts with 0. [0326] The other syntax fields are not necessary for the description of the embodiments of the invention, so that their descriptions will be skipped. [0327] The following describes PlayItem. One PlayItem basically includes the following data. [0328] (1) Clip_information_file_name for specifying the file name of a Clip pointed by PlayItem. [0329] (2) A pair of IN_time and OUT_time for identifying the reproduction interval of that Clip. [0330] (3) connection_condition indicative of the state of connection between the preceding PlayItem and the current PlayItem which are continuous in the PlayList. [0331]FIG. 32 shows the PlayList of which CPI_type is EP_map (this is called the PlayList of EP_map type). In the case of the PlayList of EP_map type, IN_time and OUT_type of PlayItem indicate the time of PTS base. These IN_time and OUT_time point the time on the same STC-sequence. In order to indicate this STC-sequence, ref_to_STC_id is used. These IN_time and OUT_time point the time in the reproduction interval indicated by presentation_start_time and presentation_end_time defined for this STC_sequence. The information exists in SequenceInfo. [0332]FIG. 33 shows the PlayList of which CPI_type is TU_map (this is called the PlayList of TU_map type). In the case of the PlayList of TU_map type, IN_time and OUT_time of PlayItem indicate the time of arrival time base. The IN_time and Out_time indicate the time on the same ATC-sequence. [0333]FIG. 34 illustrates a relationship between the time information of the PlayList of EP_map type and the address information in an AV stream file. The time information of the PlayList is the PTS information of the picture and audio frames in the AV stream file. EP_map and SequenceInfo of the Clip Information file relates the time information in the AV stream with the address in its file. [0334]FIG. 35 illustrates a relationship between the time information of the PlayList of TU_map type and the address information in the AV stream file. The time information of the PlayList is the arrival time information in the AV stream file. The TU_map of the Clip Information file relates the time information in the AV stream with the address in its file. [0335]FIG. 36 shows syntax of PlayItem( ). [0336] length indicates the number of bytes from the byte immediately after this length field to the last byte of PlayItem( ). [0337] Clip_Information file name indicates_the file name of a Clip Information file to be referenced by PlayItem. [0338] connection_condition indicates the information whether or not the preceding PlayItem and the current PlayItem are seamlessly connected together. [0339] ref_to_STC_id indicates stc-id of an STC-sequence of the Clip to be referenced by PlayItem. The value of stc-id is defined in SequenceInfo. [0340] IN_time stores the reproduction start time of PlayItem. [0341] OUT_time stores the reproduction end time of PlayItem. [0342] Bridge_Clip_Information_file_name is reproduction auxiliary information for use in the case where the preceding PlayItem and the current PlayItem are seamlessly connected together. [0343]FIG. 37 shows syntax of PlayListMark( ). As described above, PlayListMark stores marks which are mainly set by the user. [0344] length indicates the number of bytes from the byte immediately after this length field to the last byte of PlayListMark( ). [0345] number_of_PlayList_marks indicates the number of entries of the marks stored in PlayListMark. [0346] mark_invalid_flag is a 1-bit flag which indicates that, when this value is set to zero, this mark has valid information and, when this value is set to 1, this mark is invalid. [0347] When the user performs an operation for deleting the entry of one mark on the user interface, the recorder may change the value of mark_invalid_flag to 1 instead of deleting the entry of one mark. [0348] mark_type indicates the type of mark. [0349] mark_name_length indicates the byte length of the mark name shown in the Mark_name field. The value of this field is less than 32. [0350] ref_to_PlayItem_id indicates the value of PlayItem_id which specifies the PlayItem on which the mark is placed. The value of the PlayItem_id for a certain PlayItem is defined in PlayList( ). [0351] mark_time_stamp stores the time stamp which indicates the point specified with that mark. mark_time_stamp indicates the time in the reproduction range identified by IN_time and OUT_time defined in the PlayItem indicated by ref_to_PlayItem_id. [0352] If the CPI_type of the PlayList is EP_map type, mark_time_stamp is represented with presentation time stamp as base. If the CPI_type is TU_map type, mark_time_stamp is represented with arrival time stamp as base. [0353] entry_ES_PID is set to 0�FFFF, its mark is the pointer to the time axis common to all elementary streams to be used by the PlayList. If entry_ES_PID is set to a value other than 0�FFFF, entry_ES_PID indicates the value of the PID of the transport packet which includes the elementary stream pointed by this mark. [0354] ref_to_thumbnail_index indicates the information of the thumbnail image to be attached to the mark. If the ref_to_thumbnail_index field is a value other than 0�FFFF, a thumbnail image is attached to the mark and stored in the mark.tdat file. This image is referenced by use of the value of thumbnail_index in the mark.tidx file (which will be described later). If the ref_to_thumbnail index field is 0�FFFF, no thumbnail image is attached to that mark. [0355] mark_name indicates the name of mark. The number of bytes indicated by mark_name_length from the left side of this field indicates the valid characters, which indicate the above-mentioned name. These characters are encoded by a method indicated by character_set in UIAppInfoPlayList. In the mark_name field, the value of the bytes following these valid characters may take any value. [0356] The following describes the �info.dvr� directory. FIG. 38 shows syntax of the �info.dvr� file. The �info.dvr� directory has UIAppInfoVolume( ) and TableOfPlayLists( ). [0357] TableOfPlayLists_Start_address indicates the start address of TableOfPlayLists( ) with the relative number of bytes from the start byte of the info.dvr file used as unit. The relative number of bytes is counted from zero. [0358]FIG. 39 shows syntax of UIAppInfoPlayList( ). [0359] ref_to_thumbnail_index indicates the information of a thumbnail image to be added to the mark. If the ref_to_thumbnail_index field is a value other than 0�FFFF, a thumbnail image is attached to that mark. This thumbnail image is stored in the menu.tdat file. This image is referenced by use of the value of thumbnail_index in the menu.tidx file (which will be described later). If the ref_to_thumbnail_index field is 0�FFFF, no thumbnail image is attached to that mark. [0360] The other syntax fields indicate the parameters of the user interface application about Volume, but they are not necessary for the description of the embodiments of the invention, so that their descriptions will be skipped. [0361]FIG. 40 shows syntax of TableOfPlayLists( ). TableOfPlayLists( ) stores the files names of PlayLists(Real PlayList and Virtual PlayList). All PlayList files recorded to a volume (disk) are included in TableOfPlayList( ). TableOfPlayLists( ) indicates the sequence of reproducing the defaults of the PlayList in the volume. [0362] length indicates the number of bytes of TableOfPlayLists( ) from the byte immediately after this length field to the last of TableOfPlayLists( ). [0363] number_of_PlayLists indicates the number of PlayLists recorded to the volume. [0364] A 10-byte number of PlayList_file_name indicates the file name of the PlayList. [0365] The following describes the contents of a file which stores the information about thumbnails. [0366] �menu.tidx� and �menu.tdat� store the information about one picture representing a menu thumbnail, namely Volume, and one picture representing each PlayList. The header information about all menu thumbnails is collectively managed by one menu.tidx. The picture data of all menu thumbnails are collectively managed by one menu.tdat. [0367] �mark.tidx� and �mark.tdat� store the information about the picture pointed by a mark thumbnail, namely a mark point. The header information about all mark thumbnails attached to all Clips and PlayLists in Volume is collectively managed by one menu.tidx. The picture data of all mark thumbnails are collectively managed by one mark.tdat. [0368] The thumbnail picture data are the data obtained by coding an image by JPEG for example. [0369] The following describes the syntaxes and semantics of these four files. [0370] �menu.tidx� and �mark.tidx� have a same syntax structure. FIG. 41 shows the syntax structure of �menu.tidx� and �mark.tidx�. [0371] version_number is a 4-digit number representing the version number of this thumbnail header information file. [0372] length is the number of bytes from the byte immediately after this length field to the last byte of menu.tidx/mark.tidx. [0373] number_of_thumbnails is the number of thumbnail pictures stored in menu.tdat in the case of menu.tidx and the number of thumbnail pictures stored in mark.tdat in the case of mark.tidx. [0374] tn_block_size indicates the size of one tn_block in menu.tdat in the case of menu.tidx and the size of one tn_block in mark.tdat in the case of mark.tidx. This size is based on a unit of 1024 bytes. For example, tn_block_size=1 indicates that the size of one tn_block is 1024 bytes. One thumbnail picture must be stored in one tn_block. [0375] number_of_tn_blocks indicates the number of tn_blocks stored in menu.tdat in the case of menu tidx and the number of tn_blocks stored in mark.tdat in the case of mark.tidx. [0376] thumbnail_index indicates the index number of the thumbnail information which follows this thumbnail_index field. The value of 0�FFFF must not be used for thumbnail_index. [0377] In the case of menu.tidx, thumbnail_index is referenced by ref_to_thumbnail_index in UIAppInfoVolume( ) and UIAppInfoPlayList( ). In the case of mark.tidx, thumbnail_index is referenced by ref_to_thumbnail_index in PlayListMark( ) and ClipMark( ). [0378] ref_to_tn_block_id indicates one tn_block in menu.tdat in the case of menu.tidx. This tn_block stores picture data pointed by thumbnail_index. The value of ref_to_tn_block_id references the value of tn_block id in the syntax of menu.tdat. [0379] In the case of mark.tidx, one tn_block in mark.tdat is indicated. This tn_block stores the picture data pointed by thumbnail_index. The value of ref_to_tn_block_id references the value of tn_block_id in the syntax of menu.tdat. [0380] picture_byte_size indicates the data length of one encoded thumbnail picture pointed by thumbnail_index on a byte unit basis. picture_byte_size must be less than the value of 1024*tn_block_size. Namely, the recorder must encode each thumbnail picture so that the data length of one encoded thumbnail picture becomes equal to or less than the value of 1024*tn_block_size. [0381] horizontal_picture_size indicates the number of horizontal pixels of the encoded thumbnail picture pointed by thumbnail_index. [0382] vertical_picture_size indicates the number of vertical pixels of the encoded thumbnail picture pointed by thumbnail_index. [0383] display_aspect_ratio indicates the display aspect ratio of the encoded thumbnail picture pointed by thumbnail_index. [0384]FIG. 42 shows the syntax structure of �menu.tdat� and �mark.tdat�. �menu.tdat� and �mark.tdat� have a same syntax structure. [0385] tn_block is an area in which one encoded thumbnail picture is stored. The byte length of one piece of thumbnail picture is equal to or less than one tn block. The first byte of one picture data must match the first byte of tn_block. [0386] In the case of menu.tdat, the size of one tn_block is indicated by tn_block_size in menu.tdat. In the case of mark.tdat, the size of one tn_block is indicated by tn_block_size in mark.tdat. [0387] Each tn_block is distinguished by the value of tn_block_id at the time when it appears in the for-loop in the syntax. The tn_block_id in menu.tidx is referenced by the ref_to_tn_block_id in menu.tidx. The tn_block_id in mark.tidx is referenced by the ref_to_tn_block_id in mark.tidx. [0388] Since thumbnails are frequently added and deleted, an adding operation and a partially deleting operation must be able to be executed with ease and at high speeds. For this reason, menu.tdat and mark.tdat have each a block structure. One picture data is stored in one tn_block. [0389] A tn_block not in use may be included in the tn_block sequence of menu.tdat and mark.tdat. For example, to delete a certain thumbnail, the thumbnail_index entered in the header information file of that thumbnail is deleted. If the picture data file of the thumbnail has not been changed at all, a tn_block not in use is generated in the tn_block sequence. [0390]FIG. 43 schematically shows how thumbnail picture data are stored in tn_block. As shown, the byte length of one thumbnail picture is equal to or less than one tn_block. A tn block not in use may exist in a tn block sequence. [0391] The following describes the concept of a PlayList editing operation. The following processing is executed on the basis of the operation by the user by the controller 17 shown in FIG. 44 to be described later. [0392]FIG. 45 shows the concept of the relationship between Clip and PlayList when an AV stream is recorded as a new Clip. When an AV stream is recorded as a new Clip, a Real PlayList for referencing the reproducible range of that Clip in its entirety is generated. [0393]FIG. 46 shows the concept of creating a Virtual PlayList. A Virtual PlayList is created when the user specifies IN_time and OUT_time from the reproducible range of a Real PlayList to create a PlayItem in the reproduction interval which the user wants to view. [0394]FIG. 47 shows the concept of the relationship between Clip and PlayList when the reproduction interval of a Real PlayList is partially deleted. The PlayItem of the Real PlayList is changed so that only the necessary reproduction portion of the Clip AV stream is referenced. Then, the unnecessary stream portion of the Clip AV stream is deleted. As shown in FIG. 47, if the data at the center portion of the Clip AV stream is deleted, the Clip AV stream file remains undivided to be one whole file. If the data of one Clip AV stream are partially deleted, the remaining data portion is compiled into one Clip AV stream. [0395] If a Real PlayList has been changed and the stream portion of the Clip which is referenced by the Real PlayList is deleted, the Clip which is referenced by a Virtual PlayList using the same Clip may be lost, thereby presenting a problem. To prevent such a problem from happening, the user interface must take any of the following actions. [0396] When the user wants to perform a �delete� operation, a confirmation and alert message is given: �A Virtual PlayList referencing the stream portion of the Clip referenced by this Real PlayList exists; if this Real PlayList is deleted, the Virtual PlayList will also be deleted. Is it OK?� Alternatively, instead of deleting the above-mentioned Virtual PlayList, �Minimize� process shown below is performed on the Real PlayList. [0397]FIG. 48 shows the concept of the relationship between Clip, Real PlayList and Virtual PlayList after minimize editing. Minimize editing changes the PlayItem of the Real PlayList so that only the stream portion of the Clip necessary for the Virtual PlayList is referenced. Then, the stream portion of the Clip unnecessary for the Virtual PlayList is deleted. [0398] As shown in FIG. 48, if the data at the center portion of the Clip AV stream is deleted, the Clip AV stream file remains undivided to be one whole file. If the data of one Clip AV stream are partially deleted, the remaining data portion is complied into one Clip AV stream. [0399] The following describes, on the basis of the above-mentioned concept, the change of a Clip Information file which partially deletes the data of a Clip AV stream. [0400] As described before, when an AV stream is newly recorded as a Clip file, the Clip includes no ATC discontinuity point and has only one ATC-sequence. It is assumed that the ATC discontinuity point is generated only when the stream data of a Clip AV stream file are partially deleted by editing for example. Namely, as shown in FIGS. 47 and 48, when the data of one Clip AV stream are partially deleted and the remaining data portion is compiled into one Clip AV stream, the Clip has an ATC discontinuity point and a plurality of ATC-sequences. For example, as shown in FIG. 49, it is assumed that the Clip before editing have no discontinuity point and has only one ATC-sequence. When the data at the center portion of the Clip AV stream are deleted, the Clip after editing has two ATC-sequences as shown. [0401]FIG. 50 shows the relationship between ATC-sequence, STC-sequence, and program-sequence after the partial deletion of the data of one Clip AV stream. It is assumed that the Clip before editing has only one ATC-sequence, one STC-sequence and one program-sequence. Namely, it is assumed that, in this Clip, the contents of the program-sequence do not change. At this moment, it is assumed that the AV stream data indicated by shadow be deleted. As a result of the editing, the Clip has three ATC-sequences and three STC-sequences, while there is only one program-sequence. This program-sequence extends over the boundaries of ATC-sequences and STC-sequences. [0402] The following describes the relationship between Clip and PlayList when the data of a Clip AV stream is partially deleted as described above. [0403]FIG. 51 shows the relationship between Clip and PlayList when the Clip AV stream of which CPI is EP_map is partially deleted. It is assumed that the Clip before editing have one ATC-sequence and three STC-sequences. The value of offset_STC_id[0] associated with this ATC-sequence is zero. It is assumed that the STC-sequence with stc=1 in the Clip be in use by PlayItem2 and PlayItem3. It is assumed here as shown that the AV stream data portion not in use by PlayItem2 and PlayItem3 be deleted for the AV stream data of the STC-sequence with stc=1. [0404] The Clip after editing has two ATC-sequences and the STC-sequence with stc_id=1 is divided into two STC-sequences. The value of offset_STC id[0] for the first ATC-sequence is set to zero and the value of offset_STC_id[1] for the second ATC-sequence is set to 1. Namely, the stc_id of the last STC-sequence in the first ATC-sequence and the stc_id of the first STC-sequence in the second ATC-sequence have the same value, 1. [0405] Consequently, the values of ref_to_STC_id of PlayItem3 and PlayItem4 of the edited Virtual PlayList need not be changed. When partially deleting the data of a Clip AV stream file, the Virtual PlayList not using this deleted portion need not be changed in any manner. [0406] Thus, the ATC discontinuity point can be generated in each Clip AV stream, so that, when the stream data at the middle portion of the Clip AV stream has been deleted, the Clip file need not be divided into two. Further, by use of offset_STC_id for STC-id of the first STC sequence on each ATC-sequence, when partially deleting the data of the Clip AV stream file, the Virtual PlayList not using this deleted portion need not be changed in any manner. [0407]FIG. 52 helps understand the above-mentioned effects by illustrating an example in which, when no ATC discontinuity point is permitted in the Clip, if a Clip AV stream is partially deleted, the Clip file is divided into two and shows the relationship between Clip and PlayList at that time. [0408] As with FIG. 51, it is assumed that the Clip before editing have one ATC-sequence and three STC-sequences. The value of offset_STC_id[0] associated with this ATC-sequence is zero. It is also assumed that the STC-sequence with stc_id=1 in the Clip be in used by PlayItem2 and PlayItem3. It is assumed here as shown that the AV stream data of the portion not in use by PlayItem2 and PlayItem3 be deleted for the AV stream data of the STC-sequence with stc_id=1. [0409] If no ATC discontinuity is permitted in the Clip, two Clip files are obtained after editing, Clip-A and Clip-B. This requires to change the name of the Clip file which is referenced by PlayItem3 and PlayItem4. Namely, when the data of a Clip AV stream file are partially deleted, the contents of the Virtual PlayList not using the deleted portion may have to be changed. [0410] If no ATC discontinuity is permitted in the Clip, it presents the following problems as compared with the case in which ATC discontinuity is permitted. [0411] (1) The number of Clip files in the disk increases too much: [0412] This presents a problem of increasing the time necessary for the processing of reading all Clip files at starting the reproduction of the disk and storing them into a memory (incorporated in the controller 17) of the reproducing apparatus (the moving picture recording/reproducing apparatus 1). This also presents a problem of increasing the number of Clip files by editing if the upper limit of the number of files recordable to the disk (recording medium 10) is set to a predetermined value, thereby causing the number of Clip files to reach the upper limit, which disables the recording even through there is still a free area on the disk. [0413] (2) The time necessary for changing the Virtual PlayList in the disk is too long when the data of a Clip AV stream file are partially deleted: [0414] The present invention solves the above-mentioned problems. To be more specific, the present invention can shorten the time necessary for reading all Clip files at starting the reproduction of the disk and storing them into the memory of the reproduction apparatus. The present invention can also set the number of files recordable to the disk to a level below the upper limit. In addition, the present invention can shorten the time necessary for changing the Virtual PlayList in the disk when the data of a Clip AV stream file are partially deleted. [0415]FIG. 53 shows the relationship between Clip and PlayList when a Clip AV stream of which CPI is TU_map is partially deleted. The Clip before editing has one ATC-sequence. The value of offset_arrival_time[0] associated with this ATC-sequence is zero. It is assumed that PlayItem1, PlayItem2, PlayItem3, and PlayItem4 of the Virtual PlayList reference this ATC-sequence. It is assumed here as shown that the AV stream data not in use by any PlayItem are deleted from the AV stream of the ATC-sequence. [0416] The Clip after editing has two ATC-sequences. The value of offset arrival time[0] associated with the first ATC-sequence is set to zero and the value of offset_arrival_time[1] associated with the second ATC-sequence is set to X. Value X is greater than OUT_time2 and smaller than IN_time3. Namely, the values of IN_time and OUT_time of PlayItem3 and PlayItem4 of the Virtual PlayList need not be changed. [0417] When partially deleting the data of a Clip AV stream file, the Virtual PlayList not using this deleted portion need not be changed in any manner. [0418] When reproducing the PlayList of TU_map type, the reproduction apparatus compares IN_time of the PlayItem with the value of offset_arrival_time of ATC-sequence to find the ATC-sequence pointed by the IN_time and the OUT_time. For example, in the example shown in FIG. 53, because IN_time3 of PlayItem3 is greater than offset_arrival time(=X) of the second ATC-sequence, it is known that IN_time3 and OUT_time3 of PlayItem3 point the second ATC-sequence. [0419] The following describes a system for recording and reproducing the data having a DVR application structure with reference to the block diagram of the moving picture recording/reproducing apparatus 1 shown in FIG. 44. [0420] For example, information recorded to a recording medium 10 constituted by an optical disk is read by a read section 11 of a reproducing section 61. A demodulator 12 demodulates the data read by the read section 11 from the recording medium 10 and supplies the demodulated data to an ECC decoder 13. The ECC decoder 13 separates the data supplied from the demodulator 12 into an AV stream and a database, supplying the AV stream to a source depacketizer 14 and the database to a controller 17. [0421] The source depacketizer 14 depacketize the inputted AV stream and outputs the depacketized stream to a demultiplexer 15. The demultiplexer 15 separates the data supplied from the source depacketizer 14 into video data(V), audio data (A), and system data (S) and outputs them to an AV decoder 16 and a multiplexer 25. [0422] The AV decoder 16 decodes the inputted video data and the audio data on the basis of the system data and outputs the obtained video signal from a terminal 18 and the obtained audio signal from a terminal 19. [0423] An AV encoder 23 of a recording section 62 is supplied with a video signal from a terminal 21 and an audio signal from a terminal 22. The video signal is also supplied to a video analyzer 24. The video signal outputted from the AV decoder 16 is supplied as required to the AV encoder 23 and the video analyzer 24 instead of the video signal inputted from the terminal 21. [0424] The AV encoder 23 encodes the inputted video signal and audio signal and outputs the resultant video signal (V), the resultant audio signal (A), and the system data (S) corresponding to the encoding to the multiplexer 25. [0425] The video analyzer 24 analyzes the inputted video signal and outputs the analysis result to the controller 17. [0426] In a terminal 33, a transport stream is inputted from a digital interface or a digital television tuner. The transport stream is supplied to the demultiplexer 15 via a switch 27 and to a multiplexed stream analyzer 26 and a source packetizer 29 via a switch 28. Signals outputted from the multiplexer 25 via the switch 28 can also be supplied to the multiplexed stream analyzer 26 and the source packetizer 29 instead of the signal from the switch 27. [0427] The multiplexed stream analyzer 26 analyzes the inputted signal and outputs the analysis result to the controller 17. The source packetizer 29 packetizes the inputted signal and supplies the resultant packets to an ECC encoder 30. The database outputted from the controller 17 is also supplied to the ECC encoder 30. [0428] The ECC encoder 30 attaches an error correction code to the input signal to encode it and outputs the resultant data to a modulator 31. The modulator 31 modulates the data inputted from the ECC encoder 30 and outputs the modulated data to a write section 32. The write section 32 executes the processing of writing the data inputted from the modulator 31 to the recording medium 10. [0429] The controller 17 has a storage section 17A for storing various data, manages the above-mentioned format, and controls each component for performing data recording and reproducing operations on the recording medium 10. [0430] The controller 17 is also connected to a drive 41 which drives a magnetic disk 51, an optical disk 52, a magneto-optical disk 53, or a semiconductor memory 54. [0431] It should be noted that the optical disk 52 may also be used as the recording medium 10. [0432] The following describes the basic recording operations by use of an example in which the moving picture recording/reproducing apparatus 1 itself encodes an audio video signal and records the encoded audio video signal. [0433] From the terminal 21 and the terminal 22 of the recording section 62, a video signal and an audio signal are inputted respectively. The video signal is inputted in the video analyzer 24 and the AV encoder 23. The audio signal is also inputted in the AV encoder 23. The AV encoder 23 encodes the inputted video signal and audio signal and outputs the resultant encoded video stream (V), encoded audio stream (A), and system information (A) to the multiplexer 25. [0434] The encoded video stream (V) is a MPEG-2 video stream for example and the encoded audio_stream (A) is a MPEG1 audio stream or Dolby AC3 (trademark) audio stream for example. The system information (S) is encoded information for video and audio (including the byte sizes of encoded picture and audio frame and picture encoded type for example) or time information such as AV synchronous. [0435] The multiplexer 25 multiplexes the input stream on the basis of the input system information and outputs the multiplexed stream. The multiplexed stream is a MPEG-2 transport stream or a MPEG-2 program stream for example. The multiplexed stream is inputted in the multiplexed stream analyzer 26 and the source packetizer 29. The source packetizer 29 encodes the input multiplexed stream into an AV stream constituted by source packets in accordance with the application format of the recording medium 10. The AV stream is added with an error correction encode by the ECC (Error Checking and Correction) encoder 30, the resultant stream being modulated by the modulator 31 to be inputted in the write section 32. The write section 32 records the AV stream file to the recording medium 10 on the basis of a control signal given by the controller 17. [0436] The following describes an example in which a transport stream such as digital TV broadcast inputted from a digital interface or a digital TV tuner, not shown. [0437] From the terminal 33, a transport stream is inputted. There are two types of methods of recording input transport streams. One is the recording in a transparent manner and the other is the recording by performing re-encoding for the purpose of lowering recording bit rate. The information for selecting one of these recording methods is inputted from the terminal 20 as a user interface into the controller 17, which controls the selected recording method. [0438] When recording an input transport stream in a transparent manner, the transport stream is inputted in the multiplexed stream analyzer 26 and the source packetizer 29. Subsequently, the processing up to the recording of the AV stream to the recording medium 10 is the same as the above-mentioned recording of input audio signal and video signal by encoding them. [0439] When recording an input transport stream by re-encoding it, the input transport stream is inputted in the demultiplexer 15. The demultiplexer 15 inputs the video stream (V) into the AV decoder 16. The AV decoder 16 decodes the video stream and inputs the resultant reproduction video signal into the AV encoder 23. The AV encoder 23 encodes the input video and inputs the encoded video stream (V) into the multiplexer 25. [0440] On the other hand, the audio stream (A) and the system information (S) outputted from the demultiplexer 15 are inputted directly into the multiplexer 25. The multiplexer 25 multiplexes the input stream on the basis of the input system information and outputs the multiplexed stream. Subsequently, the processing up to the recording of the AV stream to the recording medium 10 is the same as the above-mentioned recording of the input audio video signals by encoding them. [0441] The moving picture recording/reproducing apparatus 1 records an AV stream file and, at the same time, records the application database information associated with this file. The application database information is generated by the controller 17. The input information into the controller 17 includes the moving picture characteristics information from the video analyzer 24, the AV stream characteristics information from the multiplexed stream analyzer 26, and the user command information from the terminal 20 which is the user interface. [0442] The moving picture characteristics information from the video analyzer 24 is generated by the moving picture recording/reproducing apparatus 1 when the moving picture recording/reproducing apparatus 1 itself encodes video signals. The video analyzer 24 analyzes the contents of an input video signal to generate information associated with an image of characteristic mark points in the input moving picture signal. This information includes indicating information about the image of the characteristic mark points such as the program start point, scene change point, and CM start/end points for example in the input video signal. This information also includes a thumbnail of this image. The image indicating information is inputted in the multiplexer 25 via the controller 17. [0443] When multiplexing the encoded picture of the image of the mark points indicated by the controller 17, the multiplexer 25 returns the address information on that encoded picture AV stream to the controller 17. The controller 17 stores the type of characteristic image by relating it to the address information on the AV stream of that encoded picture. [0444] The AV stream characteristic information from the multiplexed stream analyzer 26 is associated with the AV stream encoded information to be recorded, which is generated by the moving picture recording/reproducing apparatus 1. For example, this information includes I-picture time stamp and address information, STC discontinuity information, program contents change information, and arrival time and address information in the AV stream. [0445] The I-picture time stamp and address information in the AV stream provide the data to be stored in the above-mentioned EP_map. The STC discontinuity information in the AV stream provides the data to be stored in the above-mentioned SequenceInfo. The program contents change information in the AV stream provides the data to be stored in the ProgramInfo. The arrival time and address information in the AV stream is stored in the above-mentioned TU_map. [0446] When recording a transport stream inputted from the terminal 33 in a transparent manner, the multiplexed stream analyzer 26 detects the image of the characteristics mark points in the AV stream to generate its type and address information. This information provides the data to be stored in the ClipMark. [0447] The AV stream characteristics information from the multiplexed stream analyzer 26 is stored in a database (Clip Information) of the AV stream. [0448] The user command information from the terminal 20 includes the information for specifying a desired reproduction interval in the AV stream, the character text describing the contents of this reproduction interval, and the time stamps in AV stream of book marks and resume points to be set to user-desired scene. These pieces of user command information are stored in the database of the PlayList. [0449] On the basis of the above-mentioned input information, the controller 17 generates a database (Clip Information) of AV stream, a database of the PlayList, management information (info.dvr) for the recorded contents of the recording medium 10, and the thumbnail information. As with an AV stream, these pieces of database information are processed by the ECC (Error Checking and Correction) encoder 30 and the modulator 31 to be inputted in the write section 32. On the basis of the control signal given by the controller 17, the write section 32 records this database information to the recording medium 10 as application database information. [0450] The following describes the basic operations of reproduction. [0451] The recording medium 10 records an AV stream file and application database information. [0452] First, the controller 17 instructs the read section 11 of the reproducing section 61 to read the application database information. In response, the read section 11 reads the application database information from the recording medium 10, the database information being inputted in the controller 17 via the demodulator 12 and the ECC (Error Checking and Correction) decoder 13. [0453] On the basis of the application database, the controller 17 outputs a list of PlayLists recorded to the recording medium 10 to the user interface of the terminal 20. Referencing the list, the user selects a PlayList to be reproduced, which is inputted in the controller 17. The controller 17 instructs the read section 11 to read the AV stream file necessary for the reproduction of this PlayList. In response, the read section 11 reads this AV stream from the recording medium 10, which is inputted in the source depacketizer 14 via the demodulator 12 and the ECC decoder 13. [0454] The source depacketizer 14 converts the AV stream having the application format of the recording medium into a stream which can be inputted in the demultiplexer 15. The demultiplexer 15 inputs, in the AV decoder 16, the video stream (V), audio stream (A), and system information (S) constituting the reproduction interval (PlayItem) of the AV stream specified by the controller 17. The AV decoder 16 decodes the video stream and the audio stream and outputs the resultant reproduction video signal and reproduction audio signal from the terminal 18 and the terminal 19 respectively. [0455] If the PlayList of EP_map type selected by the user is reproduced halfway, the controller 17 instructs the read section 11 to read the data from the address of the I-picture having the PTS nearest to the specified time. [0456] If the PlayList of TU_map type selected by the user is reproduced halfway, the controller 17 instructs the read section 11 to read the data from the address of a source packet having the arrival time nearest to the specified time. [0457] Further, when the user selects a mark from the program indexing point and scene change point of a program stored in the ClipMark in the Clip Information (for example, this selecting operation is performed by displaying to the user interface a thumbnail image list of the indexing point and scene change point of a program stored in the ClipMark and selecting an image therefrom by the user), the controller 17, on the basis of the contents of the Clip Information, determines the read position of the AV stream supplied from the recording medium 10 and instructs the read section 11 to read that AV stream. [0458] Namely, the controller 17 instructs the read section 11 to read the data from the I-picture at the address nearest to the address on the AV stream in which the user-selected image is stored. The read section 11 reads the data from the specified address and these data are inputted in the demultiplexer 15 via the demodulator 12 and ECC decoder 13 to be decoded by the AV decoder 16, thereby reproducing the AV data indicated by the address of the mark point picture. [0459] The following describes the editing of AV streams by the user. [0460] When the user wants to generate a new reproduction route by specifying the reproduction intervals of an AV stream recorded to the recording medium 10, the information about the IN-point and OUT-point of the reproduction interval are inputted from the terminal 20 of the user interface into the controller 17. The controller 17 generates a database of a group (PlayList) of AV stream reproduction intervals (PlayItems). [0461] When the user wants to partially delete the AV stream recorded to the recording medium 10, the information of the deletion interval is inputted from the terminal 20 of the user interface into the controller 17. The controller 17 changes the PlayList database so that only the necessary AV stream portion is referenced. The controller 17 also instructs the write section 32 to delete the unnecessary stream portion of the AV stream. On the basis of the change in the Clip AV stream, the controller 17 changes the contents of the Clip Information file. [0462] The following describes an operation in which the user wants to generate a new reproduction route by specifying the reproduction intervals of an AV stream recorded to the recording medium 10 and connect these reproduction intervals seamlessly. In this case, the controller 17 must generate a database of a group (PlayList) of AV stream reproduction intervals (PlayItems) and partially re-encode and re-multiplex the video stream in the proximity of the connection point between the reproduction intervals. [0463] First, the information of the picture of the IN-point and OUT-point of the reproduction interval is inputted from the terminal 20 of the user interface into the controller 17. The controller 17 instructs the read section 11 to read the data necessary for reproducing the picture of the IN-point and the OUT-point. In response, the read section 11 reads the specified data from the recording medium 10, these data being inputted into the demultiplexer 15 via the demodulator 12, the ECC decoder 13, and the source depacketizer 14. The controller 17 analyzes the stream inputted in the demultiplexer 15, determines the video stream re-encoding method (changing of picture_coding_type and assignment of encoded bit amount to be re-encoded) and the video stream re-multiplexing method, and supplies the determined methods to the AV encoder 23 and the multiplexer 25. [0464] Next, the demultiplexer 15 separates the inputted video stream into a video stream (V), an audio stream (A), and system information (S). The video stream includes �data to be inputted in the AV decoder 16� and �data to be directly inputted in the multiplexer 25.� The former data is required for re-encoding, which are decoded by the AV decoder 16 to be re-encoded by the AV encoder 23 to provide a video stream. The latter data are copied from the original stream without re-encoding. The audio stream and the system information are directly inputted in the multiplexer 25. [0465] On the basis of the information inputted from the controller 17, the multiplexer 25 multiplexes the input stream and outputs the resultant multiplexed stream. The multiplexed stream is processed by the ECC (Error Checking and Correction) encoder 30 and the modulator 31 to be inputted in the write section 32. On the basis of a control signal given by the controller 17, the write section 32 records the AV stream to the recording medium 10. [0466]FIG. 54 is the flowchart describing a recording operation of the moving picture recording/reproducing apparatus 1 when recording a Clip AV stream file and associated Clip Information file to newly record an AV stream as a Clip. [0467] In step S11, the controller 17 puts, into a file, the transport stream obtained by encoding AV inputs from the terminal 21 and the terminal 22 or a transport stream inputted from the digital interface of the terminal 33, generates a Clip AV stream file, and records it. [0468] In step S12, the controller 17 generates the ClipInfo (FIG. 8) associated with the above-mentioned AV stream file. [0469] In step S13, the controller 17 generates the SequenceInfo (FIG. 13) associated with the above-mentioned AV stream file. [0470] In step S14, the controller 17 generates the ProgramInfo (FIG. 15) associated with the above-mentioned AV stream file. [0471] In step S15, the controller 17 generates the CPI (EP-map or TU-map) (FIG. 24, FIG. 25 and FIG. 26) associated with the above-mentioned AV stream file. [0472] In step S16, the controller 17 generates the ClipMark associated with the above-mentioned AV stream file. [0473] In step S17, the controller 17 records the Clip Information file (FIG. 8) in which the above-mentioned ClipInfo, SequenceInfo, ProgramInfo, CPI, and ClipMark are stored. [0474] It should be noted that the above-mentioned processes have been described in a time-dependent manner; actually, however, step S11 through step S16 operates at the same time. [0475] The following describes an exemplary operation for generating the SequenceInfo (FIG. 13) when newly recording an AV stream as a Clip with reference to the flowchart shown in FIG. 55. This processing is executed in the multiplexed stream analyzer 26 shown in FIG. 44. [0476] In step S31, the controller 17 sets the first transport packets to the start point of the ATC sequence. Namely, SPN_ATC_start is set. At the same time, atc_id and stc_id are set. [0477] In step S32, the multiplexed stream analyzer 26 analyzes the PTS of the access unit (for example, picture or audio frame) included in the AV stream. [0478] In step S33, the multiplexed stream analyzer 26 checks if the PCR packet has been received. If the decision is No in step S33, then the procedure returns to step S32; if the decision is Yes, the procedure goes to step S34. [0479] In step S34, the multiplexed stream analyzer 26 checks if STC discontinuity has been detected. If the decision is NO, the procedure returns to step S32; if the decision is YES, the procedure goes to step S35. It should be noted that, in the case of the PCR packet received first after starting the recording, the procedure always goes to step S35. [0480] In step S35, the multiplexed stream analyzer 26 gets the number (address) of the transport packet which transmits the first PCR of the new STC. [0481] In step S36, the controller 17 gets the above-mentioned packet number as the source packet number at which to start the STC sequence. Namely, SPN_STC_start is set. At the same time, a new stc_id is set. [0482] In step S37, the controller 17 gets the display start PTS and display end PTS of the STC sequence and sets them to presentation_start_time and presentation_end_time respectively and, on the basis thereof, generates SequenceInfo (FIG. 13). [0483] In step S38, the controller 17 checks if the last transport packet has been inputted. If the decision is No, the procedure returns to step S32; if the decision is Yes, the processing comes to an end. [0484] The following describes an exemplary operation for generating ProgramInfo (FIG. 15) with reference to the flowchart shown in FIG. 56. This processing is executed in the multiplexed stream analyzer 26 shown in FIG. 44. [0485] In step S51, the multiplexed stream analyzer 26 checks if a transport packet including PSI/SI has been received. The transport packet of PSI/SI is PAT, PMT, SIT packets, to be more specific. SIT is a transport packet which describes the service information of a partial transport stream specified by the DVB standard. In step S51, if the decision is No, the procedure returns to step S51; if the decision is Yes, the procedure goes to step S52. [0486] In step S52, the multiplexed stream analyzer 26 checks if the contents of PSI/SI have changed. Namely, it is checked whether or not the contents of PAT, PMT, and SIT have each changed from their contents as they were received before, If the contents are found not changed, the procedure returns to step S51. If the contents are found changed, the procedure goes to step S53. It should be noted that in the case of the PSI/SI received first after starting the recording, the procedure always goes to step S53. [0487] In step S53, the controller 17 gets the number (address) of the transport packet which transits a new PSI/SI and its contents. [0488] In step S54, the controller 17 generates the information of Program-sequence to generate ProgramInfo(FIG. 15). [0489] In step S55, the controller 17 checks if the last transport packet has been inputted. If the decision is No, the procedure returns to step S51; if the decision is Yes, the processing comes to an end. [0490] The following describes an exemplary operation for generating EP_map with reference to the flowchart shown in FIG. 57. This processing is executed in the multiplexed stream analyzer 26 shown in FIG. 44. [0491] In step S71, the multiplexed stream analyzer 26 sets the video PID of the AV program to be recorded. If the transport stream includes two or more videos, the video PID of each of them is set. [0492] In step S72, the multiplexed stream analyzer 26 receives the transport packet of video. [0493] In step S73, the multiplexed stream analyzer 26 checks if the payload (the data portion following the packet header) of the transport packet starts with the first byte of the PES packet (the PES packet is a packet specified in MPEG-2 and packetizes elementary streams). This can be known by checking the value of �payload_unit_start_indicator� in the transport packet header. If this value is 1, the transport packet payload starts with the first byte of the PES packet. If the decision is No in step S73, the procedure returns to step S72; if the decision is Yes, the procedure goes to step S74. [0494] In step S74, the multiplexed stream analyzer 26 checks if the payload of the PES packet starts with the first byte of sequence_header_code (�0�000001B3� of 32-bit length) of MPEG video. If the decision is No in step S74, the procedure returns to step S72; if the decision is Yes, the procedure goes to step S75. [0495] In step S75, the controller 17 uses the current transport packet as an entry point. [0496] In step S76, gets the packet number of the above-mentioned packet, the PTS of the I-picture starting with the above-mentioned sequence_header_code, and the PID of the video to which the entry point belongs to generate an EP_map. [0497] In step S77, the multiplexed stream analyzer 26 determines whether or not the current packet is the transport packet which is inputted last. If the current packet is not the last packet, the procedure returns to step S72. If the current packet is the last packet, the processing comes to an end. [0498]FIG. 58 shows the flowchart describing a method of generating the Real PlayList. The following describes this method with reference to the block diagram of the moving picture recording/reproducing apparatus 1 shown in FIG. 44. [0499] In step S91, the controller 17 records a Clip AV stream. [0500] In step S92, the controller 17 generates PlayListo (FIG. 31) constituted by PlayItem (FIG. 36) which covers all reproducible range of the above-mentioned Clip. If there is an STC discontinuity point in the Clip and PlayListo is constituted by two or more PlayItems, the controller 17 also determines the connection_condition between the PlayItems. [0501] In step S93, the controller 17 generates UIAppInfoPlayList( ). UIAppInfoPlayList( ) includes the information for describing the contents of the PlayList for the user. Its description will be skipped herein. [0502] In step S94, the controller 17 generates PlayListMark (its description will be skipped herein). [0503] In step S95, the controller 17 generates MakersPrivateData (its description will be skipped herein). [0504] In step S96, the controller 17 records the real PlayList. [0505] Thus, every time a Clip AV stream is recorded, one Real PlayList file is generated. [0506]FIG. 59 shows the flowchart describing a method of generating a Virtual PlayList. [0507] In step S111, the reproduction of one Real PlayList recorded to the disk (the recording medium 10) is specified through the user interface. Then, from the reproduction range of that Real PlayList, a reproduction interval pointed by IN-point and OUT-point is specified through the user interface. [0508] In step S112, the controller 17 checks if the reproduction interval specifying operation by the user has all been completed. If the user wants to select an interval to be reproduced following the above-specified reproduction interval, the procedure returns to step S111. [0509] If the reproduction range specifying operation by the user has all been completed in step S112, the procedure goes to step S113. [0510] In step S113, the connection state (connection_condition) between the two reproduction intervals to be continuously reproduced is determined by the user through the user interface or by the controller 17. [0511] In step S114, the user specifies the sub-pass information (audio after recording) through the user interface. If the user generates no sub-pass information, this step is skipped. The sub-pass information is stored in the SubPlayItem in the PlayList but is unnecessary for the description of the present invention, so that its description will be skipped. [0512] In step S115, the controller 17 generates PlayList( ) (FIG. 28) on the basis of the user-specified reproduction range information and the connection_condition. [0513] In step S116, the controller 17 generates UIAppInfoPlayList( ) . UIAppPlayList( ) includes the information for describing the contents of PlayList for the user. The description will be skipped in the present embodiment. [0514] In step S117, the controller 17 generates PlayListMark (of which description will be skipped in the present embodiment). [0515] In step S118, the controller 17 generates MakersPrivateData (of which description will be skipped in the present embodiment). [0516] In step S119, the controller 17 records the Virtual PlayList file to the recording medium 10. [0517] Thus, from the reproduction range of Real PlayLists recorded to the recording medium 10, the user selects the reproduction intervals to be viewed by the user and one Virtual PlayList file is generated for each group of the user-selected reproduction intervals. [0518]FIG. 60 shows the flowchart describing a method of PlayList reproduction. [0519] In step S131, the controller 17 gets the information about Info.dvr, Clip Information file, PlayList file, and thumbnail file to generate a GUI screen showing a list of PlayLists recorded to the disk (the recording medium 10), displaying the generated list on the GUI through the user interface. [0520] In step S132, the controller 17 shows the PlayList describing information onto the GUI screen on the basis of UIAppInfoPlayListo of each PlayList. [0521] In step S133, the user specifies the reproduction of one PlayList on the GUI screen through the user interface. [0522] In step S134, the controller 17 gets the source packet number having the temporally nearest entry point from STC-id of the current PlayItem and the PTS of IN_time. [0523] In step S135, the controller 17 reads the AV stream data from the source packet number having the above-mentioned entry point and supplies the data to the decoder. [0524] In step S136, if there is a PlayItem temporally before the current PlayItem, the controller 17 executes the display connection processing between the preceding PlayItem and the current PlayItem in accordance with the connection_condition. [0525] In step S137, the controller 17 instructs the AV decoder 16 to start displaying with the picture of the PTS of IN_time. [0526] In step S138, the controller 17 instructs the AV decoder 16 to continue decoding the AV stream. [0527] In step S139, the controller 17 checks if the currently displayed image is the image of the PTS of OUT_time. If the decision is No, the procedure goes to step S140. In step S140, the current image is displayed, upon which the procedure returns to step S138. If the currently displayed image is the image of the PTS of OUT_time, the procedure goes to step S141. [0528] In step S141, the controller 17 checks if the current PlayItem is the last PlayItem in the PlayList. If the decision is No, the procedure returns to step S134. If the decision is Yes, the PlayList reproducing operation comes to an end. [0529] On the basis of the above-mentioned syntaxes, data structures, and rules, the contents of the data and the reproduction information recorded to the recording medium 10 can be properly managed, thereby allowing the user to properly confirm the contents of the data recorded to recording media at the time of reproduction and reproduce desired data with ease. [0530] The following describes a method of file-copying AV stream files and database files from a recording medium to which the AV stream files and database files according to the invention to another recording medium via a digital bus. [0531] First, in order to describe the purpose of this method, the difference between the data transfer of an AV stream file and its database together and the data transfer of only an AV stream file. [0532]FIGS. 61 and 62 show the case in which both an AV stream file and its database file are transferred. On the other hand, FIGS. 63 and 64 shows the case in which only an AV stream is transferred. [0533] A recording medium of the copy source (for example, a recording medium 10 shown in FIG. 71 to be described later) is recorded with Clip and PlayList. It is assumed here that a PlayList file using one Clip (Clip Information file and Clip AV stream file) is recorded to the recording medium of the copy source for the brevity of description. [0534]FIG. 61 shows an example in which the PlayList and Clip files are file-transferred from the copy source (for example, a reproducing apparatus shown in FIG. 71) to the copy destination (a recording apparatus 3 shown in FIG. 71) by asynchronous transfer via an IEEE 1394 digital bus (a digital bus 60 shown in FIG. 71) for example. In this case, the ATS (Arrival Time Stamp) of the TP_extra_header of each source packet of the copied Clip AV stream file is the same as that of the copy source and the Clip Information file and PlayList file corresponding to the copied Clip AV stream file are also copied to the copy destination. [0535]FIG. 62 shows an example in which a PlayList file and a Clip Information file are file-transferred from the copy source (the reproducing apparatus 2 shown in FIG. 71) to the copy destination (the recording apparatus 3 shown in FIG. 71) by asynchronous transfer via the IEEE 1394 digital bus (the digital bus 60 shown in FIG. 71), thereby transferring (stream-transferring) AV streams in real time from the copy source to the copy destination by isochronous transfer. [0536] In this case, when outputting the Clip AV stream file corresponding to the Clip Information file to the digital bus (the digital bus 60 shown in FIG. 71), the copy source (reproducing apparatus 2 shown in FIG. 71) outputs the transport packets in accordance with the arrival time stamp of each source packet (refer to the reproducing model shown in FIG. 7). The TP_extra_header(ATS) of each source packet is newly added at the copy destination (the recording apparatus 3 shown in FIG. 71) (a new Clip AV stream file is generated at the copy destination). The Clip Information file and PlayList file (database file) corresponding to the copied Clip AV stream file are also copied to the copy destination. [0537] In the case of FIG. 61 or FIG. 62, the contents of the PlayList and Clip on the copy source can all be transferred to the copy destination, making this case effective. Namely, the reproduction specifying information, UIAppInfoPlayList, PlayListMark, thumbnail information and the like set to the PlayList on the copy source and the CPI, SequenceInfo, ProgramInfo, ClipMark, thumbnail information and the like set to the Clip on the copy source can be transferred to the copy destination, making this case effective. [0538] On the other hand, FIG. 63 and FIG. 64 show the case in which only an AV stream is data-transferred. [0539]FIG. 63 shows the case in which only an AV stream is transferred (stream-transferred) in real time from the copy source (the reproducing apparatus 2 shown in FIG. 71) to the copy destination (the recording apparatus 3 shown in FIG. 71) by isochronous transfer via the IEEE 1394 digital bus (the digital bus 60 shown in FIG. 71). In this case, when outputting the AV stream of the reproduction interval specified by the PlayList to the digital bus, the copy source outputs the transport packet (refer to the reproducing model shown in FIG. 7) in accordance with the arrival time stamp of each source packet. When viewed from the copy destination, this is the same as the state of recording a digital broadcast transport stream, in which the inputted AV stream is newly recorded as a Clip. Namely, the TP_extra_header(ATS) of each source packet is newly added at the copy destination. A Real PlayList file for covering the reproduction range of that Clip is newly generated (the database file is newly generated on the copy source, so that it is different from that of the copy source). [0540]FIG. 64 shows the case in which only an AV stream is data-transferred at a real-time data reproducing speed when the recording apparatus on the copy destination (the recording apparatus 3 shown in FIG. 71) is not compliant with the DVR format. [0541] In this case, as with the case shown in FIG. 63, an AV stream is transferred in real time (stream-transferred) from the copy source to the copy destination by IEEE 1394 isochronous transfer. The copy destination records the inputted AV stream by use of the format of its recording apparatus (the recording apparatus 3 shown in FIG. 71) For example, if the recording apparatus on the copy destination is based on D-VHS (trademark), the inputted AV stream is recorded by this format. Thus, when the reproducing apparatus on the copy source compliant with DVR format (the controller 17 of the reproducing apparatus 2 shown in FIG. 71) mutually authenticates the recording apparatus on the copy destination (a controller 17-2 of the recording apparatus 3 shown in FIG. 71) and if the above-mentioned recording apparatus is found not compliant with DVR format, then the above-mentioned reproducing apparatus (the controller 17 of the reproducing apparatus 2 shown in FIG. 71) is controlled to transfer the AV stream in real time. [0542] In the case of FIG. 63 or FIG. 64, the contents of the PlayList and Clip of the copy source cannot all be transferred to the copy destination, thereby presenting a problem. That is, the reproduction specifying information, UIAppInfoPlayList, PlayListMark, thumbnail information and the like set to the PlayList of the copy source and the CPI, SequenceInfo, ProgramInfo, ClipMark, thumbnail information and the like set to the Clip of the copy source cannot be transferred to the copy destination. On the other hand, in the case of FIG. 61 or FIG. 62, the contents of the PlayList and Clip of the copy source can all be transferred to the copy destination. [0543] If the recording apparatus of the copy destination is compliant with the DVR format described in the present embodiment, then any one of the methods shown in FIG. 61 and FIG. 62 can be used. [0544] In the method shown in FIG. 61, AV streams are file-transferred, so that the data can be transferred at higher speeds than the data transfer at a speed of real-time data reproduction. However, it is difficult for this method to decode in real time the inputted data in the recording apparatus of the copy destination and reproduce the decoded data. [0545] On the other hand, in the method shown in FIG. 62, AV streams are data-transferred at a speed of real-time data reproduction, so that the inputted data can be decoded in real time and reproduced in the recording apparatus of the copy destination. However, it is necessary for the time for copying an AV stream to be equal to the time for reproducing the data in real time. The methods shown in FIGS. 61 and 62 are used alternately depending on the purpose of use. [0546] In the examples shown in FIG. 61 and FIG. 62, the PlayList covers the entire reproduction range of one Clip. As described with reference to FIG. 46, the reproduction range to be specified by the PlayList does not always cover one Clip AV stream in its entirety. This holds true both with the Real PlayList and the Virtual PlayList. When transferring the PlayList to the copy destination, it is preferable to transfer to the copy destination only the AV stream portion necessary for the reproduction of the PlayList and the Clip data which this AV stream portion references. Namely, as with the example shown in FIG. 65, the PlayList and the Clip portion required by the PlayList are copied from the copy source (the reproducing apparatus 2 shown in FIG. 72) to the copy destination (recording apparatus 3 shown in FIG. 1). Consequently, the free space on recording medium of the copy destination (a recording medium 10-2 of the recording apparatus 3 shown in FIG. 71) necessary for the reproduction may be made smaller. [0547] The following describes a method of determining, when copying the PlayList from the copy source (the reproducing apparatus on the output side) to the copy destination (the recording apparatus on the input side), the Clip AV stream portion necessary for the reproduction of this PlayList. [0548]FIG. 66 shows the stream portion necessary for the reproduction of a PlayList when this PlayList indicates the partial reproduction range of an original AV stream file. [0549] It is assumed that this PlayList point the IN_time and OUT_time on the original AV stream. In this case, the stream portion necessary for the reproduction of the PlayList is between X and Y of the source packet number as shown in the figure. In what follows, an exemplary method of determining these X and Y points is described. [0550]FIG. 67 a method of determining the copy start point (X point) of data before the IN-point without analyzing the contents of an AV stream. The PlayList points the IN-point on the original AV stream. It also points the EP_map of this AV stream. To decode the picture pointed by the IN-point, the I picture starting with address ISA2 is required. PAT, PMT, and PCR packets are also required after the X point. The PTS of SPN_EP_start=ISA1 if pts1 and the PTS of SPN EP start=ISA2 is pts2. If the time difference between pts1 and pts2 system time bases is equal to or higher than 100 msec, the PAT, PMT, and PCR packets exist between addresses ISA1 and ISA2 (at least in the case of SESF, DVB, ATSC, and ISDB). Therefore, the X point is determined before ISA1. And the X point must provide the boundary of the aligned unit. [0551] The reproducing apparatus of the copy source can determine the X point in the following steps by use of EP_map without analyzing the contents of AV stream. [0552] (S1) Find the SPN_EP_start having the value of PTS of display time which is nearest to the PTS of IN time on the system time base and before this PTS. [0553] (S2) Find the SPN_EP_start having the value of PTS of display time which is at least 100 msec before the value of the PTS of the SPN_EP_start found in step S1. [0554] (S3) The X point is determined before the SPN_EP_start found in step S2. And the X point must provide the boundary of aligned unit. [0555] The above-mentioned method is simple because it does not read,the AV stream data and analyze its contents to determine the X point. However, the AV stream after the X point may leave data which are unnecessary for the reproduction of the PlayList. If the AV stream data are read and its contents are analyzed to determine the X point, the data unnecessary for the reproduction of the PlayList can be eliminated with efficiency. [0556]FIG. 68 illustrates a method of determining the data copy end point (Y point) after the OUT-point without analyzing the contents of AV stream. The PlayList points the OUT-point on the original AV stream. It also points the EP_map of this AV stream. It is supposed that the video sequence which starts with SPN_EP_start=ISA4 be as follows: [0557] I2 B0 B1 P5 . . . [0558] where I, P, and B represent I picture, P picture, and B picture, respectively. The numbers indicate the sequence of display. In this processing, if the recording apparatus does not analyze the contents of AV stream, the moving picture recording/reproducing apparatus 1 (the recording apparatus 3 shown in FIG. 71) does not know the information about the picture (picture coding type, temporal reference, and so on) which the PTS of OUT_time references. The PTS of OUT_time may be referencing picture B0 or B1 (this is not known if the reproducing apparatus of the copy source (the reproducing apparatus 2 shown in FIG. 71) does not analyze the contents of AV stream). In this case, the decoding of pictures B0 and B1 requires 12. The PTS of 12 is greater than the PTS of OUT time (OUT_time<pts4, where pts4 is the PTS of 12). The PTS of 12 is greater than the PTS of OUT_time, but 12 is required for B0 and B1. [0559] Therefore, the Y point is determined after address ISA5 indicated by the figure. ISA5 is the value of SPN_EP_start located after ISA4 in the EP_map. The Y point must also provide the boundary of aligned unit. [0560] The reproducing apparatus of the copy source (the reproducing apparatus 2 shown in FIG. 71) can determine the Y point by the following steps by use of EP_map without analyzing the contents of AV stream. [0561] (S1) Find the SPN_EP_start having the value of PTS of display time which is nearest to the PTS of OUT time on the system time base and after this PTS. [0562] (S2) Find the SPN_EP_start immediately after the SPN_EP_start found in step S1. [0563] (S3) The Y point is determined after the SPN_EP start found in step S2. And the Y point must provide the boundary of aligned unit. [0564] The above-mentioned method is simple because it does not read the AV stream data and analyze its contents to determine the Y point. However, the AV stream before the Y point may leave data which are unnecessary for the reproduction of the PlayList. If the AV stream data are read and its contents are analyzed to determine the Y point, the data unnecessary for the reproduction of the PlayList can be eliminated with efficiency. [0565] The following describes a relationship between a Clip Information file and a PlayList when, in copying the PlayList from the copy source to the copy destination, a Clip AV stream necessary for the reproduction of the PlayList has been generated. [0566]FIG. 69 shows an example in which a PlayList is copied from the copy source to the copy destination and describes the relationship between the Clip and the PlayList when a Clip AV stream necessary for the reproduction of the PlayList has been generated. It is assumed here that the CPI of the Clip be EP_map. It is also assumed that one original Clip has one ATC-sequence and three STC-sequences. The offset_STC_id[0] associated with this ATC-sequence is zero. It is further assumed that, in the Clip, the STC-sequence having stc_id=0 is used for PlayItem1, the STC-sequence having stc_id=1 is used for PlayItem2 and PlayItem3, and the STC-sequence having stc_id=2 is used for PlayItem4. [0567] It is assumed here that this PlayList has been copied to another recording medium. Namely, by this copying, a Clip formed by the Clip portion necessary for the reproduction of this PlayList is generated as shown in FIG. 69. One or more stream portions extracted from one Clip AV stream on the copy source are combined into one Clip AV stream on the copy destination. The newly generated Clip has four ATC-sequences, each having one STC-sequence. [0568] The offset_STC_id[0] of the ATC-sequence in which the STC-sequence with stc_id=0 is set to zero. The STC-sequence having stc_id=1 is divided into two STC-sequences. The offset_STC_id[0] for the first ATC-sequence is set to zero and the offset_STC_id[1] for the second ATC-sequence is set to 1. Namely, the stc_id of the last STC-sequence in the first ATC-sequence and the stc_id of the first STC-sequence in the second ATC-sequence have the same value, 1. The offset_STC_id[0] of the ATC-sequence in which the STC-sequence having stc_id=2 is included is set to 2. [0569] Consequently, the ref_to_STC_id values of PlayItem1, PlayItem2, PlayItem3, and PlayItem4 of the PlayList to be copied need not be changed. When, in copying a certain PlayList to another recording medium, a Clip formed by a Clip portion necessary for the reproduction of this PlayList is generated, the contents of the PlayList need not be changed at all. [0570] Thus, an ATC discontinuity point can be generated in each Clip AV stream, the Clip file need not be divided when partially extracting the Clip stream data necessary for the reproduction of the PlayList. Moreover, by use of the offset_STC id for the STC_id of the first STC sequence on each ATC sequence, the contents of the PlayList need not be changed when a Clip formed by the Clip portion necessary for the reproduction of the PlayList has been generated. [0571] The following describes a method of changing a Clip when partially copying it as described above. FIGS. 70A through 70D show examples of partially copying a Clip, which describe a method of changing SequenceInfo, ProgramInfo, CPI(EP_map) and ClipMark. [0572] It is assumed that the Clip shown in FIG. 70A be recorded on the copy source. This Clip has one ATC-sequence which has two STC-sequences and two program-sequnences. The start addresses of the first STC-sequence and the first program-sequence are the same, which are source packet number 0 on the Clip AV stream. The start addresses of the second STC-sequence and the second program sequence are the same, which are source packet number B on the Clip AV stream. [0573] It is assumed here that the stream data portion indicated by shadow starting from source packet number A (A<B) shown in FIG. 70A be copied. This shadowed stream data portion is a stream portion necessary for the reproduction interval between IN_time and OUT_time of the AV stream. The Clip to be transferred to the copy destination is shown in FIG. 70B. The Clip to be transferred to the copy destination has one ATC-sequence, on which there are two STC-sequences and two program-sequences. The start addresses of the first STC-sequence and the first program-sequence are the same, which are source packet number 0 (A-A) on the Clip AV stream. The start addresses of the second STC-sequence and the second program sequence are the same, which are source packet number (B-A) on the Clip AV stream. [0574]FIG. 70C shows the contents of the Clip Information file of the Clip shown in FIG. 70A. As described above, [0575] SPN_ATC_start[0]=0 [0576] SPN_STC_start[0]=0, SPN_STC_start[1]=B [0577] SPN_program_sequence_start[0]=0, [0578] SPN_program_sequence_start[1]=B. [0579] It is also assumed that this Clip Information file have the EP_map and ClipMark as shown. In this, the data portion of the EP_map and ClipMark used by the Clip of the shadowed portion shown in FIG. 70A is in the following range. In EP_map, the data of the entry point having the value of PTS of [0580] IN_time<pts(xa), [0581] pts(xz)<OUT_time [0582] are necessary for the shadowed portion shown in FIG. 70A. [0583] In ClipMark, the data of the mark having the value of the PTS of [0584] IN_time<pts(F), [0585] pts(Q)<OUT_time [0586] are necessary for the Clip of the shadowed portion shown in FIG. 70A. [0587]FIG. 70D shows the contents of the Clip Information file of the Clip shown in FIG. 70B. As described above, [0588] SPN_ATC_start[0]=0 [0589] SPN_STC_start[0]=0, SPN_STC_start[1]=B−A [0590] SPN_program_sequence_start[0]=0, [0591] SPN_program_sequence_start[1]=B−A. [0592] The data of EP_map is generated from the data of EP_map used by the Clip of the shadowed portion shown in FIG. 70C. Namely, the values the PTS of the entry points are the same and start source packet number A of the Clip of the copy source is subtracted from the value of source pocket number. For the data of ClipMark, the data of the ClipMark used by the Clip of the shadowed portion shown in FIG. 70C are used as they are. [0593]FIG. 71 is the configurations for transferring AV streams and associated database from the reproducing apparatus 2 of the copy source (output side) to the recording apparatus 3 of the copy destination (input side) and transferring only AV streams in the same manner. With reference to the figure, components similar to those previously described with FIG. 44 are denoted by the same reference numerals. The recording medium 10-2 and the controller 17-2 of the recording apparatus 3 function in the same manner as the recording medium 10 and controller 17 respectively. [0594] First, an example in which an AV stream and its associated database are transferred together will be described. [0595] The information for indicating the copying of a desired PlayList from the recording medium 10 of the reproducing apparatus 2 to the recording medium 10-2 of the recording apparatus 3 is inputted in the reproducing apparatus 2 in a copy control command via a user interface, not shown. This command is inputted in the controller 17 via a digital bus interface 50 and a bus controller 52. [0596] The controller 17 determines the stream portion of AV stream necessary for the reproduction of the above-mentioned PlayList and instructs the read section 11 to read the determined AV stream data from the recording medium 10 (refer to FIGS. 66, 67, and 68). Also, the controller 17 instructs the read section 11 to read the database file (PlayList file, Clip Information file, and thumbnail file) associated with the above-mentioned PlayList from the recording medium 10. [0597] The controller 17 gives an instruction to supply the AV stream data retrieved through the demodulator 12 and ECC decoder 13 to the digital bus interface 50 as an AV stream file via the contact A side of a switch 61 (in the case shown in FIG. 61). The stream portion extracted from one Clip AV stream file is combined with one Clip AV stream file (refer to FIG. 69). [0598] Alternatively, the controller 17 may input the above-mentioned AV stream data retrieved via the demodulator 12 and the ECC decoder 13 into the source depacketizer 14 via the contact I side of the switch 61. In this case, the source depacketizer 14 supplies the transport stream to the digital bus interface 50 in accordance with the arrival time stamp. [0599] On the other hand, the database file corresponding to the AV stream data retrieved from the recording medium 10 is inputted in a memory 51 via the demodulator 12 and the ECC decoder 13. On the basis of the data stored in the memory 51, the controller 17 generates the database (Clip Information file and PlayList file) necessary for the reproduction of the above-mentioned AV stream file outputted from the digital bus interface 50 (refer to FIGS. 69, 70A through 70D). Also, the controller 17 generates the Clip corresponding to the above-mentioned stream file and a thumbnail file to be used by the PlayList file to be copied (refer to step S172 shown in FIG. 72). [0600] Then, the controller 17 gives an instruction to supply the above-mentioned newly generated database files (Clip Information file, PlayList file and thumbnail file) from the memory 51 to the digital bus interface 50. [0601] The bus controller 52 controls the file output from the digital bus interface 50. The controller 17 instructs the bus controller 52 to output the AV stream and its associated database from the digital bus interface 50. [0602] The above-mentioned AV stream and its associated database are inputted in the recording apparatus 3 of the copy destination via the digital bus 60. [0603] A bus controller 57 of the recording apparatus 3 of the copy destination controls the file input from a digital bus interface 55. The bus controller 52 and the bus controller 57 exchange file copy control commands to control the timing of data transmission/reception. [0604] If an AV stream file is inputted from the copy source into digital bus interface 55, the controller 17-2 of the recording apparatus 3 gives an instruction to record the AV stream file to the recording medium 10-2 via the ECC encoder 30, the modulator 31, and write section 32 through the contact A side of a switch 62. [0605] If a transport stream is inputted from the copy source into the digital bus interface 55, the controller 17-2 inputs the transport stream into the source packetizer 29 through the contact I side of the switch 62. The source packetizer 29 converts the transport packet into a source packet before outputting. The controller 17-2 gives an instruction to record the AV stream formed by the source packets to the recording medium 10-2 via the ECC encoder 30, the modulator 31, and the write section 32. [0606] The controller 17-2 also gives an instruction to write the database files to be inputted in the digital bus interface 55 to a memory 56. [0607] Also, the controller 17-2 gives an instruction to read the database files (Info.dvr file and thumbnail file) recorded to the recording medium 10-2 to the memory 56 via the read section 11, demodulator 12, and the ECC decoder 13. [0608] Then, the controller 17-2 updates the Info.dvr file and the thumbnail file stored in the memory 56. To be more specific, the controller 17-2 adds the PlayList file name to be newly recorded to the TableOfPlayList of the Info.dvr file on the copy destination and adds a thumbnail to be newly recorded to the thumbnail file stored in the copy destination (refer to steps 224 and 225 shown in FIG. 74 to be described later). [0609] The controller 17-2 gives an instruction to read the database files from the memory 56 and record them to the recording medium 10-2 via the ECC encoder 30, the modulator 31, and the write section 32. [0610] Thus, the AV stream and its associated database are transferred from the reproducing apparatus 2 to the recording apparatus 3 to copy the AV stream. [0611] The following describes an example in which the reproducing apparatus 2 transfers only an AV stream to the copy destination. This is through of as an operation for reproducing a transport stream by the reproducing apparatus 2 if the recording apparatus 3 of the copy destination is not compliant with DVR format. [0612] The controller 17 determines the stream portion of AV stream necessary for the reproduction of the above-mentioned PlayList and instructs the read section 11 to read the AV stream data from the recording medium 10. The controller 17 inputs the above-mentioned AV stream data read via the demodulator 12 and the ECC decoder 13 into the source depacketizer 14 via the contact I side of the switch 61. The source depacketizer 14 supplies the transport packets to the digital bus interface 50 in accordance with the arrival time stamp. The digital bus interface 50 transfers the received transport packet in an isochronous manner. [0613] The following describes the case in which only an AV stream is transferred to the recording apparatus 3. This is thought of as an operation for recording a transport stream by the recording apparatus 3 when the reproducing apparatus 2 of the copy source is not compliant with DVR format. [0614] The controller 17-2 of the recording apparatus 3 inputs the transport stream to be inputted in the digital bus interface 55 into the source packetizer 29 via the contact I side of the switch 62. The source packetizer 29 converts the transport packet into a source packet and outputs it. The controller 17-2 gives an instruction to record the AV stream composed of source packets to the recording medium 10-2 via the ECC encoder 30, the modulator 31, and the write section 32. [0615] The transport stream is also inputted in the multiplexed stream analyzer 26 via the contact I side of the switch 62. The contents of the processing to be executed here are as described with reference to FIG. 44. On the basis of the analysis result obtained by the multiplexed stream analyzer 26, the controller 17-2 generates a database file. The controller 17-2 gives an instruction to record the generated database file to the recording medium 10-2 via the ECC encoder 30, the modulator 31, and write section 32. [0616] Thus, the processing of data-transferring only an AV stream from the reproducing apparatus 2 or the processing of data-transferring only an AV stream to the reproducing apparatus 3 is executed. [0617]FIG. 72 shows the flowchart describing the processing to be executed by the controller 17 of the copy source when copying a PlayList from the copy source (the reproducing apparatus 2 of output side) to the copy destination (the recording apparatus 3 of input side). [0618] In step S170, it is determined an AV stream and its associated database are to be data-transferred for copying or only an AV stream is to be data-transferred for copying. For the former case, the procedure goes to step S171; for the latter case, the procedure goes to step S175. [0619] In step S171, the following processing is executed on the Clip. [0620] Determine the Clip AV stream portion necessary for the reproduction of that PlayList (refer to FIGS. 66, 67, and 68). [0621] Generate a Clip Information file for use by the AV stream portion determined above (refer to FIGS. 70A through 70D). [0622] In step S172, the following processing executed on a thumbnail file. [0623] Generate a file including menu thumbnails for use by that PlayList. [0624] Generate a file including mark thumbnails for use by that PlayList and the AV stream portion determined above. [0625] In step S173, the processing of transferring the AV stream file is executed. [0626] Transfer the AV stream data of the stream portion determined by the above-mentioned Clip processing to the copy destination (refer to FIG. 69). [0627] In step S174, the processing of database file transfer is executed. [0628] Transfer the above-mentioned PlayList file to the copy destination. [0629] Transfer a Clip Information file generated by the above-mentioned Clip processing to the copy destination. [0630] Transfer the thumbnail file generated in step S172 to the copy destination. [0631] If it is determined in step S170 that only the AV stream file is to be data-transferred for copying and the procedure goes to step S175, the AV stream data (the AV stream data to be read in step S135) to be read as described in the flowchart for reproducing the PlayList shown in FIG. 60 are converted into a transport stream to transfer it to the copy destination. [0632]FIG. 73 is a flowchart describing the details of the processing for the Clip in step S171 (refer to FIGS. 70A through 70D). [0633] In step S201, the PlayList gets the display start time and display end time of an reproduction interval to be used in that Clip. [0634] In step S202, the copy start packet (address) and the copy end packet (address) on the Clip AV stream corresponding to the above-mentioned time interval are determined on the basis of CPI. [0635] In step S203, the following processing is executed on CPI. [0636] Get the CPI entry for use by the AV stream portion of the interval to be copied. [0637] Change the value of the source packet number of CPI entry point to the value of the source packet number in the AV stream portion to be copied. [0638] In step S204, the following processing associated with SequenceInfo is executed. [0639] Update the ATC-sequence start packet number in the AV stream portion of the interval to be copied. [0640] Update the STC-sequence start packet number in the AV stream portion of the interval to be copied. [0641] Update the offset_STC_id so that the value of the STC-id for the STC-sequence on the ATC-sequence in the AV stream portion of the interval to be copied remains unchanged. [0642] In step S205, the following processing associated with ProgramInfo is executed. Update the program-sequence start packet number in the AV stream portion of the interval to be copied. [0643] In step S206, the following processing associated with ClipMark is executed. [0644] Get the Mark entry for use by the AV stream portion of the interval to be copied. [0645] In step S207, the following processing associated file creation is executed. [0646] Combine the AV stream portion of the interval to be copied to provide a Clip AV stream file. [0647] Generate a Clip Information file. [0648]FIG. 74 is a flowchart describing to be executed by the copy destination when a PlayList is copied from the copy source (the reproducing apparatus 2 of output side) to the copy destination (the recording apparatus 3 of input side). [0649] In step S221, it is determined whether or not an AV stream and its associated database are to be transferred for copying or only an AV stream is to be transferred for copying. For the former case, the procedure goes to step S222. For the latter case, the procedure goes to step S226. [0650] In step S222, the processing of managing the AV stream file is executed. [0651] The inputted AV stream data are recorded to the STREAM directory as a Clip AV stream file. [0652] In step S223, the processing associated with database management is executed. [0653] Record the inputted PlayList file into the PLAYLIST directory. [0654] Record the inputted Clip Information file to the CLIPINF directory. [0655] In step S224, the processing associated with Info.dvr is executed. [0656] The inputted PlayList file is added to the TableOfPlayList of Info.dvr of the copy destination. [0657] In step S225, the processing associated with thumbnail file is executed. [0658] The thumbnail data entered in the inputted thumbnail file are added to the thumbnail file of the copy destination. [0659] If only the AV stream is to be transferred for copying in step S221 and the procedure goes to step S226, a transport stream to be inputted in the copy destination is recorded to generate a Real PlayList as described in the flowchart for generating a Real PlayList shown in FIG. 58. [0660] On the basis of the above-mentioned syntaxes, data structures and rules, the contents of the AV stream files and their associated database files recorded to the recording medium 10 can be properly managed to allow the user to easily copy desired AV stream files and their associated database files to another recording medium. [0661] When copying the partial reproduction interval of an AV stream file recorded to the recording medium 10 to another recording medium, the AV stream file necessary for the reproduction of this reproduction interval can be easily generated and the database file necessary for the reproduction of this reproduction interval can be easily generated to allow the user to generate the AV stream file and the database file necessary for the reproduction of the partial reproduction interval of a desired AV stream file, thereby easily copying these files to another recording medium. [0662] In the description with reference to FIG. 71, the transmission route for use in transferring files from the copy source to the copy destination is the digital bus based on IEEE 1394 for example. It will be apparent to those skilled in the art that the transmission route may also be a radio wave of broadcasting for example as shown in FIG. 75. The copy control commands may not be the same as the transmission route for file transfer (refer to FIG. 75). [0663] The AV stream files and their associated database files may also be transferred from different recording media to the copy destination. As shown in FIG. 76, a server in which AV stream files are recorded and another server in which the associated database files are recorded may be arranged separately, in which, in response to the copy control command issued from the recording apparatus 3, the files may be transferred to the recording apparatus 3 from the AV stream file server and the database file server. [0664] The above-mentioned embodiments have been described by use of the MPEG2 transport stream as a multiplexed stream for example. It will be apparent to those skilled in the art that the above-mentioned embodiments are also applicable to DSS transport streams and MPEG2 program streams. [0665] The above-mentioned sequence of processing operations may also be executed by not only hardware but also software. This software is installed from a network or recording media in a computer in which the programs constituting this software are installed in a dedicated hardware component or a general-purpose personal computer which can execute various functions by installing corresponding programs. [0666] This recording medium is constituted not only by package media recorded programs such as the magnetic disk 51 (including a floppy disk), the optical disk 52 (including CD-ROM (Compact Disk-Read Only Memory) and a DVD (Digital Versatile Disk)), and the magneto-optical disk 53 (including MD (Mini-Disk) (trademark)), and the semiconductor memory 54 which are distributed to users to provide programs independently of equipment main body, but also by a hard disk including a ROM and a hard disk storing programs to be provided to users as installed in advance in the equipment main body. [0667] It should be noted that, in the present specification, the steps for describing the program to be recorded in a recording medium include not only the processing operations to be executed sequentially in time but also the processing operations to be executed in parallel or discretely. [0668] It should be noted that term �system� as used herein denotes entire equipment composed of a plurality of apparatuses. INDUSTRIAL APPLICABILITY [0669] As described and according to the invention, on the basis of the above-mentioned syntaxes, data structures and rules, the contents of the AV stream files and their associated database files recorded to the recording medium 10 can be properly managed to allow the user to easily copy desired AV stream files and their associated database files to another recording medium. [0670] Especially, according to the data transmission apparatus recited in claim 1 appended hereto, the data transmission method recited in claim 13 appended hereto, the program recorded to the recording medium recited in claim 14 appended hereto, and the program recited in claim 15 appended hereto, in copying the partial reproduction interval of an AV stream file recorded to the recording medium to another recording medium, an AV stream file necessary for the reproduction of that reproduction interval can be easily generated and the database file necessary for the reproduction of that reproduction interval can be easily generated to allow the user to generate the AV stream file and the associated database file necessary for the reproduction of the partial reproduction interval of a desired AV stream file and easily copy these files to another recording medium. At the same time, because only a PlayList and a Clip portion necessary for it are copied from the copy source to the copy destination, the free storage space on the recording medium of the copy destination can be made smaller. [0671] As described and according to the data transmission apparatus recited in claims 4 through 7 and 9 appended hereto, the contents of PlayList and Clip of the copy source can all be transferred to the copy destination, making this invention effective. Namely, the reproduction specifying information, UIAppInfoPlayList, PlayListMark, thumbnail information and the like set to the PlayList on the copy source and the CPI, SequenceInfo, ProgramInfo, ClipMark, thumbnail information and the like set to the Clip on the copy source can be transferred to the copy destination, making this invention effective. [0672] As described and according to the data transmission apparatus recited in claim 10 appended hereto, AV streams are file-transferred, so that the data can be transferred at a higher speed than the data transfer at the speed at which data are reproduced in real time. [0673] As described and according to the data transmission apparatus recited in claim 11 appended hereto, AV streams are data-transferred at a speed at which data are reproduced in real time, so that data inputted in the recording apparatus of the copy destination can be decoded and reproduced in real time. [0674] As described and according to the data transmission apparatus recited in claims 12 and 16 appended hereto, the data transmission method recited in claim 17 appended hereto, the program recorded to the recording medium recited in claim 18 appended hereto, and the program recited in claim 19 appended hereto, the processing operations can be switched between the methods in which data can be transmitted by the transmission apparatus recited in claim 1 appended hereto if the apparatus of the transmission destination is compliant with DVR format for example and data can be transferred at a speed at which only an AV stream is reproduced in real time if the apparatus of the copy destination is not compliant with DVR format for example, thereby enhancing the convenience for the user in copying AV streams. [0675] As described and according to the data processing apparatus recited in claim 20 appended hereto, the data transmission method recited in claim 21 appended hereto, the program recorded to the recording medium recited in claim 22 appended hereto, and the program recited in claim 23 appended hereto, inputted PlayLists can be properly managed on the recording medium, thereby allowing the user to easily understand the contents of each PlayList recorded to the recording medium. [0676] As descried and according to the data processing apparatus recited in claim 24, the data transmission method recited in claim 25 appended hereto, the program recorded to the recording medium recited in claim 26 appended hereto, and the program recited in claim 27 appended hereto, the inputted thumbnails can be properly managed on the recorded medium, thereby allowing the user to easily confirm the contents of the thumbnails copied to the recording medium. Referenced byCiting PatentFiling datePublication dateApplicantTitleUS7444664 *Aug 19, 2004Oct 28, 2008Microsoft Corp.Multi-view video formatUS7639921 *Nov 20, 2003Dec 29, 2009Lg Electronics Inc.Recording medium having data structure for managing reproduction of still images recorded thereon and recording and reproducing methods and apparatusesUS7664371Sep 8, 2003Feb 16, 2010Lg Electronics Inc.Recording medium having data structure for managing reproduction of still images recorded thereon and recording and reproducing methods and apparatusesUS7672566Jan 20, 2004Mar 2, 2010Lg Electronics Inc.Recording medium having data structure for managing reproduction of still pictures recorded thereon and recording and reproducing methods and apparatusesUS7684675Jan 20, 2004Mar 23, 2010Lg Electronics, Inc.Recording medium having data structure for managing reproduction of still pictures recorded thereon and recording and reproducing methods and apparatusesUS7734154Jan 29, 2004Jun 8, 2010Lg Electronics Inc.Recording medium having data structure for managing reproduction duration of still pictures recorded thereon and recording and reproducing methods and apparatusesUS7747133Sep 8, 2003Jun 29, 2010Lg Electronics Inc.Recording medium having data structure for managing reproduction of still images from a clip file recorded thereon and recording and reproducing methods and apparatusesUS7756205Aug 30, 2005Jul 13, 2010Panasonic CorporationMoving image encoding method and apparatusUS7782779 *May 4, 2006Aug 24, 2010Samsung Electronics Company, Ltd.Apparatus and method for transmitting a multimedia data streamUS7787755Sep 3, 2003Aug 31, 2010Lg Electronics Inc.Recording medium having data structure for managing reproduction of slideshows recorded thereon and recording and reproducing methods and apparatusesUS7801421Nov 29, 2006Sep 21, 2010Lg Electronics Inc.Recording medium having data structure for managing reproduction of still pictures recorded thereon and recording and reproducing methods and apparatusesUS7814555 *Mar 31, 2006Oct 12, 2010Panasonic CorporationInformation network system and information apparatusUS7822794May 26, 2006Oct 26, 2010Sanyo Electric Co., Ltd.Data recording apparatus and data file transmission method in data recording apparatusUS7949604 *Jun 26, 2002May 24, 2011Sony CorporationInformation providing system, and information processing apparatus and methodUS7974516Sep 3, 2003Jul 5, 2011Lg Electronics Inc.Recording medium having data structure of playlist marks for managing reproduction of still images recorded thereon and recording and reproducing methods and apparatusesUS8005346Nov 20, 2003Aug 23, 2011Lg Electronics Inc.Recording medium having data structure for managing reproduction of data recorded thereon and recording and reproducing methods and apparatusesUS8018609 *Sep 13, 2006Sep 13, 2011Sony CorporationInformation processing device, information recording medium manufacturing device, information recording medium, methods therefore, and computer programUS8041179Feb 23, 2004Oct 18, 2011Lg Electronics Inc.Methods and apparatuses for reproducing and recording still picture and audio data and recording medium having data structure for managing reproduction of still picture and audio dataUS8050538Jan 20, 2004Nov 1, 2011Lg Electronics Inc.Recording medium having data structure for managing reproduction of still pictures recorded thereon and recording and reproducing methods and apparatusesUS8055117Jan 29, 2004Nov 8, 2011Lg Electronics Inc.Recording medium having data structure for managing reproduction duration of still pictures recorded thereon and recording and reproducing methods and apparatusesUS8085851Oct 8, 2009Dec 27, 2011Panasonic CorporationMoving image encoding method and apparatusUS8098978Sep 3, 2003Jan 17, 2012Lg Electronics Inc.Recording medium having data structure for managing reproduction of still images recorded thereon and recording and reproducing methods and apparatusesUS8145033Jan 29, 2004Mar 27, 2012Lg Electronics Inc.Recording medium having data structure for managing reproducton duration of still pictures recorded thereon and recording and reproducing methods and apparatusesUS8203730 *Aug 2, 2011Jun 19, 2012Sony CorporationInformation processing device, information recording medium manufacturing device, information recording medium, methods therefore, and computer programUS8233770Oct 8, 2004Jul 31, 2012Sharp Kabushiki KaishaContent reproducing apparatus, recording medium, content recording medium, and method for controlling content reproducing apparatusUS8290340May 7, 2007Oct 16, 2012Sony CorporationInformation processing apparatus, information processing method, and computer programUS8369689Jan 12, 2006Feb 5, 2013Sharp Kabushiki KaishaInformation recording/reproduction device and information recording mediumUS8369691 *Apr 25, 2011Feb 5, 2013Hitachi Consumer Electronics Co., Ltd.Recording apparatus/method/medium and reproduction apparatus/methodUS8422049Apr 23, 2012Apr 16, 2013Sony CorporationInformation processing device, information record medium manufacturing device, information record medium, method therefore, and computer programUS8503858 *Jan 11, 2008Aug 6, 2013Corel CorporationMachine-implemented method for establishing a playback interface, and computer-readable recording medium for implementing the sameUS8532461Jan 19, 2010Sep 10, 2013Lg Electronics Inc.Recording medium having data structure for managing reproduction of still pictures recorded thereon and recording and reproducing methods and apparatusesUS20080178208 *Jul 6, 2007Jul 24, 2008Samsung Electronics Co., Ltd.Apparatus and method for editing ts program information and ts recording device using the sameUS20090052872 *Jan 11, 2008Feb 26, 2009Intervideo, Digital Technology CorporationMachine-implemented method for establishing a playback interface, and computer-readable recording medium for implementing the sameUS20100223304 *Feb 17, 2010Sep 2, 2010Sony CorporationInformation processing apparatus, information processing method and programUS20120002941 *Apr 25, 2011Jan 5, 2012Hitachi Consumer Electronics Co., Ltd.Recording apparatus/method/medium and reproduction apparatus/method* Cited by examinerClassifications U.S. Classification386/201, G9B/27.033, G9B/20.002, G9B/27.01, G9B/27.029, G9B/27.019, G9B/27.05, G9B/20.014, G9B/27.051, G9B/27.021, G9B/27.012, 386/E09.013, 386/318, 386/241, 386/248, 386/324, 386/337International ClassificationG11B20/00, H04N5/85, G11B27/30, H04N9/82, G11B20/10, G11B27/00, G11B27/11, G11B27/32, H04N9/804, H04J3/00, H04N5/765, G11B27/28, G11B27/031, H04N5/92, G11B27/034, H04N5/91, G11B27/10, G11B27/34, G11B20/12, G06F21/00Cooperative ClassificationH04N5/765, G11B2020/10537, G11B20/00086, G11B2220/2541, G11B2220/65, G11B27/034, H04N9/8042, H04N5/85, G11B2220/20, G11B27/105, H04N9/8205, G11B27/28, G11B20/10527, G11B27/34, G11B27/3027, G11B27/031, G11B27/11, G06F21/10, G11B27/329European ClassificationG06F21/10, G11B27/28, G11B27/10A1, G11B20/10C, G11B20/00P, H04N9/804B, G11B27/32D2, G11B27/034, G11B27/30C, G11B27/031, G11B27/11, G11B27/34Legal EventsDateCodeEventDescriptionSep 5, 2012FPAYFee paymentYear of fee payment: 4Jul 18, 2003ASAssignmentOwner name: SONY CORPORATION, JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:KATO, MOTOKI;REEL/FRAME:014291/0590Effective date: 20030424RotateOriginal ImageGoogle Home - Sitemap - USPTO Bulk Downloads - Privacy Policy - Terms of Service - About Google Patents - Send FeedbackData provided by IFI CLAIMS Patent Services©2012 Google