US7738776B2 - Information processing apparatus and method, program, and recorded medium - Google Patents

Information processing apparatus and method, program, and recorded medium Download PDF

Info

Publication number
US7738776B2
US7738776B2 US10/018,846 US1884602A US7738776B2 US 7738776 B2 US7738776 B2 US 7738776B2 US 1884602 A US1884602 A US 1884602A US 7738776 B2 US7738776 B2 US 7738776B2
Authority
US
United States
Prior art keywords
map
stream
information
time
playlist
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Active, expires
Application number
US10/018,846
Other languages
English (en)
Other versions
US20020135607A1 (en
Inventor
Motoki Kato
Toshiya Hamada
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Sony Corp
Original Assignee
Sony Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Sony Corp filed Critical Sony Corp
Assigned to SONY CORPORATION reassignment SONY CORPORATION ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: HAMADA, TOSHIYA, KATO, MOTOKI
Publication of US20020135607A1 publication Critical patent/US20020135607A1/en
Priority to US10/925,658 priority Critical patent/US8670646B2/en
Application granted granted Critical
Publication of US7738776B2 publication Critical patent/US7738776B2/en
Active legal-status Critical Current
Adjusted expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/10—Digital recording or reproducing
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
    • G11B27/10—Indexing; Addressing; Timing or synchronising; Measuring tape travel
    • G11B27/34—Indicating arrangements 
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
    • G11B27/02—Editing, e.g. varying the order of information signals recorded on, or reproduced from, record carriers
    • G11B27/031—Electronic editing of digitised analogue information signals, e.g. audio or video signals
    • G11B27/034—Electronic editing of digitised analogue information signals, e.g. audio or video signals on discs
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
    • G11B27/02—Editing, e.g. varying the order of information signals recorded on, or reproduced from, record carriers
    • G11B27/031—Electronic editing of digitised analogue information signals, e.g. audio or video signals
    • G11B27/036—Insert-editing
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
    • G11B27/10—Indexing; Addressing; Timing or synchronising; Measuring tape travel
    • G11B27/102—Programmed access in sequence to addressed parts of tracks of operating record carriers
    • G11B27/105—Programmed access in sequence to addressed parts of tracks of operating record carriers of operating discs
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
    • G11B27/10—Indexing; Addressing; Timing or synchronising; Measuring tape travel
    • G11B27/19—Indexing; Addressing; Timing or synchronising; Measuring tape travel by using information detectable on the record carrier
    • G11B27/28—Indexing; Addressing; Timing or synchronising; Measuring tape travel by using information detectable on the record carrier by using information signals recorded by the same method as the main recording
    • G11B27/30—Indexing; Addressing; Timing or synchronising; Measuring tape travel by using information detectable on the record carrier by using information signals recorded by the same method as the main recording on the same track as the main recording
    • G11B27/3027—Indexing; Addressing; Timing or synchronising; Measuring tape travel by using information detectable on the record carrier by using information signals recorded by the same method as the main recording on the same track as the main recording used signal is digitally coded
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B27/00—Editing; Indexing; Addressing; Timing or synchronising; Monitoring; Measuring tape travel
    • G11B27/10—Indexing; Addressing; Timing or synchronising; Measuring tape travel
    • G11B27/19—Indexing; Addressing; Timing or synchronising; Measuring tape travel by using information detectable on the record carrier
    • G11B27/28—Indexing; Addressing; Timing or synchronising; Measuring tape travel by using information detectable on the record carrier by using information signals recorded by the same method as the main recording
    • G11B27/32—Indexing; Addressing; Timing or synchronising; Measuring tape travel by using information detectable on the record carrier by using information signals recorded by the same method as the main recording on separate auxiliary tracks of the same or an auxiliary record carrier
    • G11B27/327—Table of contents
    • G11B27/329—Table of contents on a disc [VTOC]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N9/00—Details of colour television systems
    • H04N9/79—Processing of colour television signals in connection with recording
    • H04N9/80—Transformation of the television signal for recording, e.g. modulation, frequency changing; Inverse transformation for playback
    • H04N9/804—Transformation of the television signal for recording, e.g. modulation, frequency changing; Inverse transformation for playback involving pulse code modulation of the colour picture signal components
    • H04N9/8042—Transformation of the television signal for recording, e.g. modulation, frequency changing; Inverse transformation for playback involving pulse code modulation of the colour picture signal components involving data reduction
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B20/00—Signal processing not specific to the method of recording or reproducing; Circuits therefor
    • G11B20/00086—Circuits for prevention of unauthorised reproduction or copying, e.g. piracy
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B2220/00—Record carriers by type
    • G11B2220/20—Disc-shaped record carriers
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B2220/00—Record carriers by type
    • G11B2220/20—Disc-shaped record carriers
    • G11B2220/25—Disc-shaped record carriers characterised in that the disc is based on a specific recording technology
    • G11B2220/2537—Optical discs
    • G11B2220/2541—Blu-ray discs; Blue laser DVR discs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N5/00—Details of television systems
    • H04N5/76—Television signal recording
    • H04N5/84—Television signal recording using optical recording
    • H04N5/85—Television signal recording using optical recording on discs or drums
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N9/00—Details of colour television systems
    • H04N9/79—Processing of colour television signals in connection with recording
    • H04N9/7921—Processing of colour television signals in connection with recording for more than one processing mode
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N9/00—Details of colour television systems
    • H04N9/79—Processing of colour television signals in connection with recording
    • H04N9/80—Transformation of the television signal for recording, e.g. modulation, frequency changing; Inverse transformation for playback
    • H04N9/82—Transformation of the television signal for recording, e.g. modulation, frequency changing; Inverse transformation for playback the individual colour picture signal components being recorded simultaneously only
    • H04N9/8205—Transformation of the television signal for recording, e.g. modulation, frequency changing; Inverse transformation for playback the individual colour picture signal components being recorded simultaneously only involving the multiplexing of an additional signal and the colour video signal

Definitions

  • This invention relates to an information processing method and apparatus, a program and a recording medium. More particularly, it relates to an information processing method and apparatus, a program and a recording medium for recording a file including the information indicated for explanation on the GUI, the information on the main reproducing path, the information on the subsidiary reproducing path, connection information between respective reproducing domains making up the main reproducing path, or the information on bookmarks or resume points useful for the user to set a desired scene.
  • optical discs have been proposed as a recording medium that can be removed from a recording apparatus.
  • These recordable optical discs have been proposed as a large capacity medium of several GBs and are thought to be promising as a medium for recording AV (audio visual) signals.
  • sources supplied sources
  • CS digital satellite broadcast and BS digital broadcast.
  • ground wave television broadcast of the digital system has also been proposed.
  • digital video signals furnished from these sources, are routinely compressed in accordance with MPEG (Moving picture Experts Group) 2 system.
  • MPEG Motion Picture Experts Group
  • a recording rate proper to the apparatus is set. If digital video signals, derived from the digital broadcast, are recorded by a conventional video storage medium for domestic use, in accordance with an analog recording system, digital video signals are first decoded and subsequently band-limited for recording.
  • the digital recording system exemplified first of all by MPEG1 video, MPEG2 video or DV system, the digital video signals are once decoded and subsequently re-encoded in accordance with the recording rate and a encoding system proper to the apparatus for recording.
  • the picture quality is necessarily deteriorated.
  • the transmission rate for input digital signals is not higher than the recording rate of the recording and/or reproducing apparatus, such a method in which the bitstream furnished is directly recorded without decoding or re-encoding suffers from picture quality deterioration to the least extent.
  • the transmission rate of the compressed digital signals exceeds the recording rate of the disc as the recording medium, it is truly necessary to first decode the digital signals in the recording and/or reproducing apparatus and to re-encode the digital signals for recording so that the transmission rate will be not higher than the upper limit of the recording rate of the disc.
  • the capacity of the recording medium can be exploited less wastefully in such a disc recording system in which data can be stored once in a buffer and recorded in a burst-like fashion than with a recording system in which the rotary head is of a fixed rpm and hence the recording rate is a fixed recording rate.
  • an AV stream data may be analyzed to enable fast replay to detect the position of an I-picture to effect recording such as to enable accessing an I-picture.
  • the AV stream may be directly recorded without analysis.
  • the conventional practice has been to provide respective dedicated application programs by means of which the AV stream is recorded on the recording medium as AV streams of different formats.
  • development of an application program tends to be costly and time-consuming.
  • the format is different, from one AV stream to another, with the result that the respective AV streams cannot be reproduced on the same apparatus because of lack of compatibility.
  • the conventional recording apparatus has a drawback that audio data, for example, are difficult to post-record.
  • An information processing apparatus for recording AV stream data on a recording medium includes first generating means for generating a first table describing the relation of correspondence between presentation time stamp and an address in the AV stream data of a corresponding access unit, or a second table describing the relation of correspondence between arrival time stamp derived from the arrival time point of a transport packet and an address in the AV stream data of a corresponding transport packet, and a recorder for recording one of the first table and the second table, as selected depending on a recording method, on the recording medium along with the AV stream data.
  • the first table may be EP_map and the second table may be TU_map.
  • the controller may select the second table in case of non-cognizant recording.
  • the controller may select the first table in case of self encoding recording.
  • the controller may select the first table in case of cognizant recording.
  • the controller may generate identification information indicating which of the first and second tables have been recorded and the recorder may memorize the identification information.
  • the controller manages control so that, if the first table is recorded along with the AV stream data, the reproduction domain specifying information expresses the time information of the reproduction domain of the AV stream data on the presentation time basis, and so that, if the second table is recorded along with the AV stream data, the reproduction domain specifying information expresses the time information of the reproduction domain of the AV stream data on the arrival time basis.
  • the reproduction specifying information expresses the time information of the reproduction domain of the AV stream data on the presentation time basis. If the second table is recorded along with the AV stream data, the reproduction specifying information expresses the time information of the reproduction domain of the AV stream data on the arrival time basis.
  • the present invention also provides an information processing method for recording AV stream data on a recording medium including a generating step of generating a first table describing the relation of correspondence between presentation time stamp and an address in the AV stream data of a corresponding access unit, or a second table describing the relation of correspondence between arrival time stamp derived from the arrival time point of a transport packet and an address in the AV stream data of a corresponding transport packet, and a recording step of recording one of the first table and the second table, as selected depending on a recording method, on the recording medium along with the AV stream data.
  • the present invention also provides a recording medium having recorded thereon a computer-readable program for an information processing apparatus recording AV stream data on a recording medium, in which the program includes a generating step of generating a first table describing the relation of corresponding between presentation time stamp and an address in the AV stream data corresponding access unit, or a second table describing the relation of correspondence between arrival time stamp derived from the arrival time point of a transport packet and an address in the AV stream data of a corresponding transport packet, and a recording step of recording one of the first table and the second table, as selected depending on a recording method, on the recording medium along with the AV stream data.
  • the present invention also provides a program for having a computer, controlling an information processing apparatus recording AV stream data on a recording medium, execute a generating step of generating a first table describing the relation of correspondence between presentation time stamp and an address in the AV stream data of a corresponding access unit, or a second table describing the relation of correspondence between arrival time stamp derived from the arrival time point of a transport packet and an address in the AV stream data of a corresponding transport packet, and a recording step of recording one of the first table and the second table, as selected depending on a recording method, on the recording medium along with the AV stream data.
  • the present invention also provides an information processing apparatus for reproducing AV stream data from a recording medium including reproducing unit for reproducing one of a first table describing the relation of correspondence between presentation time stamp and an address in the AV stream data of a corresponding access unit and a second table describing the relation of correspondence between arrival time stamp derived from the arrival time point of a transport packet and an address in the AV stream data of a corresponding transport packet, from the recording medium, which has the first table or the second table recorded thereon depending on a recording method, and control unit for controlling the outputting of the AV stream data based on the reproduced table.
  • the present invention also provides an information processing method for reproducing AV stream data from a recording medium including a reproducing step of reproducing one of a first table describing the relation of correspondence between presentation time stamp and an address in the AV stream data of a corresponding access unit and a second table describing the relation of correspondence between arrival time stamp derived from the arrival time point of a transport packet and an address in the AV stream data of a corresponding transport packet, from the recording medium, which has the first table or the second table recorded thereon depending on a recording method, and a controlling step of controlling the outputting of the AV stream data based on the reproduced table.
  • the present invention also provides a recording medium having recorded thereon a computer-readable program for an information processing apparatus recording AV stream data on a recording medium, in which the program includes a reproducing step of reproducing one of a first table describing the relation of correspondence between presentation time stamp and an address in the AV stream data of a corresponding access unit and a second table describing the relation of correspondence between arrival time stamp derived from the arrival time point of a transport packet and an address in the AV stream data of a corresponding transport packet, from the recording medium, which has the first table or the second table recorded thereon depending on a recording method, and a controlling step of controlling the outputting of the AV stream data based on the reproduced table.
  • the present invention also provides a program for having a computer, controlling an information processing apparatus recording AV stream data on a recording medium, execute a reproducing step of reproducing one of a first table describing the relation of correspondence between presentation time stamp and an address in the AV stream data of a corresponding access unit and a second table describing the relation of correspondence between arrival time stamp derived from the arrival time point of a transport packet and an address in the AV stream data of a corresponding transport packet, from the recording medium, having the first table or the second table recorded thereon depending on a recording method, and a controlling step of controlling the outputting of the AV stream data based on the reproduced table.
  • the present invention also provides a recording medium having recorded thereon one of a first table describing the relation of correspondence between presentation time stamp and an address in the AV stream data of a corresponding access unit and a second table describing the relation of correspondence between arrival time stamp derived from the arrival time point of a transport packet and an address in the AV stream data of a corresponding transport packet, depending on a recording method.
  • the present invention also provides an information processing apparatus for recording AV stream data on a recording medium including generating means for generating the reproduction specifying information made up of the first information indicating a main reproducing path and the second information indicating a subsidiary reproducing path, and recording means for recording the AV stream data and the reproduction specifying information on the recording medium.
  • the main reproducing path may be a path for the post-recording of audio data.
  • the first information may be main path and the second information may be the Sub-path.
  • the second information may include the type information indicating the type of the subsidiary reproducing information, a filename of the AV stream referenced by the subsidiary reproducing path, in- and out-points of the AV stream of the subsidiary reproducing path and the time on the main path at which the in-point of the reproducing path starts in synchronization on the time axis of the main path.
  • the present invention also provides an information processing method for an information processing apparatus recording AV stream data on a recording medium, including a generating step of generating the reproduction specifying information made up of the first information indicating a main reproducing path and the second information specifying a subsidiary reproducing path reproduced in synchronism with the main reproducing path, and a recording step of recording the AV stream data and the reproduction specifying information on the recording medium.
  • the present invention also provides a recording medium having recorded thereon a computer-readable program for an information processing apparatus recording AV stream data on a recording medium, in which the program includes a generating step of generating the reproduction specifying information made up of the first information indicating a main reproducing path and the second information specifying a subsidiary reproducing path reproduced in synchronism with the main reproducing path, and a recording step of recording the AV stream data and the reproduction specifying information on the recording medium.
  • the present invention also provides a program for having a computer, controlling an information processing apparatus recording AV stream data on a recording medium, execute a generating step of generating the reproduction specifying information made up of the first information indicating a main reproducing path and the second information specifying a subsidiary reproducing path reproduced in synchronism with the main reproducing path, and a recording step of recording the AV stream data and the reproduction specifying information on the recording medium.
  • the present invention also provides an information processing apparatus for reproducing AV stream data from a recording medium including reproducing means for reproducing, from the recording medium, reproduction specifying information made up of the first information indicating a main reproducing path and the second information specifying a subsidiary reproducing path reproduced in synchronism with the main reproducing path, and control means for controlling the outputting of the AV stream data based on the reproduced reproduction specifying information.
  • the present invention also includes an information processing method for reproducing AV stream data from a recording medium including a reproducing step of reproducing, from the recording medium, reproduction specifying information made up of the first information indicating a main reproducing path and the second information specifying a subsidiary reproducing path reproduced in synchronism with the main reproducing path, and a controlling step of controlling the outputting of the AV stream data based on the reproduced reproduction specifying information.
  • the present invention also provides a recording medium having recorded thereon a computer-readable program for an information processing apparatus recording AV stream data on a recording medium, in which the program includes a reproducing step of reproducing, from the recording medium, reproduction specifying information made up of the first information indicating a main reproducing path and the second information specifying a subsidiary reproducing path reproduced in synchronism with the main reproducing path, and a controlling step of controlling the outputting of the AV stream data based on the reproduced reproduction specifying information.
  • the present invention also provides a program for having a computer, controlling an information processing apparatus recording AV stream data on a recording medium, execute a reproducing step of reproducing, from the recording medium, the reproduction specifying information made up of the first information indicating a main reproducing path and the second information specifying a subsidiary reproducing path reproduced in synchronism with the main reproducing path, and a controlling step of controlling the outputting of the AV stream data based on the reproduced reproduction specifying information.
  • the recording medium according to the present invention has recorded thereon the reproduction specifying information made up of the first information indicating a main reproducing path and the second information specifying a subsidiary reproducing path reproduced in synchronism with the main reproducing path.
  • one of the first table describing the first table describing the relation of correspondence between presentation time stamp and an address in the AV stream data of a corresponding access unit and a second table describing the relation of correspondence between arrival time stamp derived from the arrival time point of a transport packet and an address in the AV stream data of a corresponding transport packet is recorded depending on a recording method.
  • one of a first table describing the relation of correspondence between presentation time stamp and an address in the AV stream data of a corresponding access unit and a second table describing the relation of correspondence between arrival time stamp derived from the arrival time point of a transport packet and an address in the AV stream data of a corresponding transport packet, is reproduced from the recording medium, which has the first table or the second table recorded thereon, depending on a recording method, and the outputting is controlled accordingly.
  • the reproduction specifying information comprised of the first information indicating the main reproducing path and the second information indicating the subsidiary reproduction path reproduced in synchronism with the main reproducing path is recorded.
  • the reproduction specifying information comprised of the first information indicating the main reproducing path and the second information indicating the subsidiary reproduction path reproduced in synchronism with the main reproducing path is reproduced to control the outputting accordingly.
  • FIG. 1 shows a configuration of an embodiment of a recording and/or reproducing apparatus according to the present invention.
  • FIG. 2 illustrates the data format of data recorded on a recording medium by a recording and/or reproducing apparatus 1 .
  • FIG. 3 illustrates Real PlayList and Virtual PlayList.
  • FIGS. 4A , 4 B and 4 C illustrate the creation of the Real PlayList.
  • FIGS. 5A , 5 B and 5 C illustrate deletion of the Real PlayList.
  • FIGS. 6A and 6B illustrate assemble editing.
  • FIG. 7 illustrates provision of a sub path in the Virtual PlayList.
  • FIG. 8 illustrates the changing of the playback sequence of the PlayList.
  • FIG. 9 illustrates a mark on the PlayList and a mark on the Clip.
  • FIG. 10 illustrates a menu thumbnail
  • FIG. 11 illustrates mark added to the PlayList.
  • FIG. 12 illustrates a mark added to the Clip.
  • FIG. 13 illustrates the relation between the PlayList, Clip and the thumbnail file.
  • FIG. 14 illustrates a directory structure
  • FIG. 15 illustrates a syntax of infr.dvr.
  • FIG. 16 shows a syntax of DVRVolume.
  • FIG. 17 shows a syntax of ResumeVolume.
  • FIG. 18 shows a syntax of UIAppInfoVolume.
  • FIG. 19 shows a table of character set values.
  • FIG. 20 shows a syntax of TableOfPlayList.
  • FIG. 21 shows another syntax of TableOfPlayList.
  • FIG. 22 shows a syntax of the MakersPrivateData.
  • FIG. 23 shows a syntax of xxxx.rpls and yyyy.vpls.
  • FIGS. 24A to 24C illustrate the PlayList.
  • FIG. 25 shows a syntax of PlayList.
  • FIG. 26 shows a table of PlayList_type.
  • FIG. 27 shows a syntax of UIAppInfoPlayList.
  • FIGS. 28A to 28C illustrate flags in the UIAppInfoPlayList syntax shown in FIG. 27 .
  • FIG. 29 illustrates a PlayItem.
  • FIG. 30 illustrates a PlayItem.
  • FIG. 31 illustrates a PlayItem.
  • FIG. 32 shows a syntax of the PlayItem.
  • FIG. 33 illustrates IN-time.
  • FIG. 34 illustrates OUT-time
  • FIG. 35 shows a table of Connection_Condition.
  • FIGS. 36A to 36D illustrate Connection_Condition.
  • FIG. 37 illustrates BridgeSequenceInfo.
  • FIG. 38 shows a syntax of BridgeSequenceInfo.
  • FIG. 39 illustrates SubPlayItem.
  • FIG. 40 shows a syntax of SubPlayItem.
  • FIG. 41 shows a table of Mark_type.
  • FIG. 42 shows a syntax of PlayListMark.
  • FIG. 43 shows a table of Mark_type.
  • FIG. 44 illustrates Mark_time_stamp.
  • FIG. 45 shows a syntax of zzzzz.clip.
  • FIG. 46 shows a syntax of ClipInfo.
  • FIG. 47 shows a table of Clip_stream_type.
  • FIG. 48 illustrates offset_SPN.
  • FIG. 49 illustrates offset_SPN.
  • FIGS. 50A , 50 B illustrate the STC domain.
  • FIG. 51 illustrates STC_Info.
  • FIG. 52 shows a syntax of STC_Info.
  • FIG. 53 illustrates ProgramInfo
  • FIG. 54 shows a syntax of ProgramInfo.
  • FIG. 55 shows a syntax of VideoCondingInfo.
  • FIG. 56 shows a table of Video_format.
  • FIG. 57 shows a table of frame_rate.
  • FIG. 58 shows a table of display_aspect_ratio.
  • FIG. 59 shows a syntax of AudoCondingInfo.
  • FIG. 60 shows a table of audio_coding.
  • FIG. 61 shows a table of audio_component_type.
  • FIG. 62 shows a table of sampling_frequency.
  • FIG. 63 illustrates CPI
  • FIG. 64 illustrates CPI
  • FIG. 65 shows a syntax of CPI.
  • FIG. 66 shows a table of CPI_type.
  • FIG. 67 illustrates video EP_map.
  • FIG. 68 illustrates EP_map.
  • FIG. 69 illustrates EP_map.
  • FIG. 70 shows a syntax of EP_map.
  • FIG. 71 shows a table of EP_typevalues.
  • FIG. 72 shows a syntax of EP_map_for_one_stream_PID.
  • FIG. 73 illustrates TU_map.
  • FIG. 74 shows a syntax of TU_map.
  • FIG. 75 shows a syntax of ClipMark.
  • FIG. 76 shows a table of Mark_type.
  • FIG. 77 shows a table of Mark_type_stamp.
  • FIG. 78 shows a syntax of menu.thmb and mark.thmb.
  • FIG. 79 shows the syntax of thumbnail.
  • FIG. 80 shows a table of thumbnail_picture_format.
  • FIGS. 81A and 81B illustrate tn_block.
  • FIG. 82 illustrates a structure of a transport stream of DVR MPEG2.
  • FIG. 83 shows a recorder model of a transport stream of DVR MPEG2.
  • FIG. 84 shows a player model of a transport stream of DVR MPEG2.
  • FIG. 85 shows the syntax of a source packet.
  • FIG. 86 shows the syntax of TP_extra_header.
  • FIG. 87 shows a table of a copy permission indicator.
  • FIG. 88 illustrates seamless connection.
  • FIG. 89 illustrates seamless connection.
  • FIG. 90 illustrates seamless connection.
  • FIG. 91 illustrates seamless connection.
  • FIG. 92 illustrates seamless connection.
  • FIG. 93 illustrates audio overlap
  • FIG. 94 illustrates seamless connection employing BridgeSequence.
  • FIG. 95 illustrates seamless connection not employing BridgeSequence.
  • FIG. 96 shows a DVR STD model.
  • FIG. 97 is a timing chart for decoding and display.
  • FIG. 98 shows the syntax of a PlayList file.
  • FIG. 99 shows the syntax of UIAppInfoPlayList in the PlayList file of FIG. 98 .
  • FIG. 100 shows the syntax of the PlayList( ) in the PlayList file of FIG. 98 .
  • FIG. 101 shows the syntax of SubPlayItem.
  • FIG. 102 is a flowchart for illustrating the method for forming RealPlayList.
  • FIG. 103 is a flowchart for illustrating the method for forming VirtualPlayList.
  • FIG. 104 is a flowchart for illustrating the method for reproducing the PlayList.
  • FIG. 105 is a flowchart for illustrating the method for reproducing a sub-path of PlayList.
  • FIG. 106 is a flowchart for illustrating the method for forming PlayListMark.
  • FIG. 107 is a flowchart for illustrating the locating reproducing method employing PlayListMark.
  • FIG. 108 illustrates a medium
  • FIG. 1 shows a typical inner structure of a recording and/or reproducing apparatus 1 embodying the present invention.
  • a recording unit 2 configured for recording signals input from outside
  • the recording and/or reproducing apparatus 1 is configured for being fed with and recording analog or digital data.
  • Analog video signals and analog audio signals are fed to terminals 11 , 12 , respectively.
  • the video signals, input to the terminal 11 are output to an analysis unit 14 and to an AV encoder 15 .
  • the audio signals, input to the terminal 12 are output to the analysis unit 14 and to the AV encoder 15 .
  • the analysis unit 14 extracts feature points, such as scene changes, from the input video and audio signals.
  • the AV encoder 15 encodes input video and audio signal to output the system information (S), such as an encoded video stream (V), an encoded audio stream (A) and AV synchronization, to a multiplexer 16 .
  • S system information
  • V encoded video stream
  • A encoded audio stream
  • AV synchronization AV synchronization
  • the encoded video stream is a video stream encoded e.g., with the MPEG (Moving Picture Expert Group) 2 system
  • the encoded audio stream is an audio stream encoded in accordance with the MPEG1 system, with the encoded audio stream being e.g., an audio stream encoded in e.g., the MPEG1 system or an audio stream encoded in accordance with the Dolby AC3 (trademak) system.
  • the multiplexer 16 multiplexes the input video and audio streams, based on the input system information, to output a multiplexed stream through a switch 17 to a multiplexed stream analysis unit 18 and to a source packetizer 19 .
  • the multiplexed stream is e.g., an MPEG-2 transport stream or an MPEG2 program stream.
  • the source packetizer 19 encodes the input multiplexed stream into an AV stream composed of source packets in accordance with an application format of a recording medium 100 on which to record the stream.
  • the AV stream is processed in ECC (error correction and coding) unit 20 and a modulation unit 21 with appendage of ECC codes and with modulation, before being output to a write unit 22 , which then writes (records) an AV stream file based on a control signals output by the controller 23 .
  • ECC error correction and coding
  • the transport stream such as digital television broadcast, input from a digital interface or a digital television tuner, is input to a terminal 13 .
  • There are two recording systems for recording the transport stream input to the terminal 13 one being a transparent recording system and the other being a system in which recording is preceded by re-encoding aimed to lower e.g., the recording bit rate.
  • the recording system command information is input from a terminal 24 as a user interface to a controller 23 .
  • a transport stream In the transparent recording of the input transport stream, a transport stream, input to a terminal 13 , is output through a switch 17 to a multiplexed stream analysis unit 18 and to the source packetizer 19 .
  • the ensuing processing of recording an AV stream on a recording medium is the same as that of encoding and recording analog input audio and video signals, as described above, and hence is not explained here for simplicity.
  • the transport stream input to the terminal 13 , is fed to a demultiplexer 26 , which demultiplexes the input transport stream to extract a video stream (V), an audio stream (A) and the system information (S).
  • V video stream
  • A audio stream
  • S system information
  • the video stream is output to an audio decoder 27 , whilst the audio stream and the system information are output to the multiplexer 16 .
  • the audio decoder 27 decodes the input transport stream to output the encoded video stream (V) to the multiplexer 16 .
  • the audio stream and the system information, output from the demultiplexer 26 and input to the multiplexer 16 , and the video stream, output by the AV encoder 15 , are multiplexed, based on the input system information, and output to the multiplexed stream analysis unit 18 and to the source packetizer 19 through switch 17 , as a multiplexed stream.
  • the ensuing processing of recording an AV stream on a recording medium is the same as that of encoding and recording analog input audio and video signals, as described above, and hence is not explained here for simplicity.
  • the recording and/or reproducing apparatus 1 of the present embodiment records a file of the AV stream on the recording medium 100 , while also recording the application database information which accounts for the file.
  • the input information to the controller 23 is the feature information for the moving picture from the analysis unit 14 , the feature information of the AV stream from the multiplexed stream analysis unit 18 and the user command information input at a terminal 24 .
  • the feature information of the moving picture is generated by the analysis unit 14 when the AV encoder 15 encodes video signals.
  • the analysis unit 14 analyzes the contents of the input video and audio signals to generate the information pertinent to the pictures characteristic of the input moving picture signals (clip mark).
  • This information is the information indicating a picture of characteristic clip mark points, such as program start points, scene change points, CM commercial start and end points, title or telop in input video signals, and also includes a thumbnail of the picture and the information pertinent to stereo/monaural switching points and muted portions of audio signals.
  • the above picture indicating information is fed through controller 23 to the multiplexer 16 .
  • the multiplexer 16 When multiplexing a encoded picture specified as clip mark by the controller 23 , the multiplexer 16 returns the information for specifying the encoded picture on the AV stream to the controller 23 .
  • this information is the PTS (presentation time stamp) of a picture or the address information on the AV stream of an encoded version of the picture.
  • the controller 23 stores the sort of feature pictures and the information for specifying the encoded picture on the AV stream in association with each other.
  • the feature information of the AV stream from the multiplexed stream analysis unit 18 is the information pertinent to the encoding information of the AV stream to be recorded, and is recorded by an analysis unit 18 .
  • the feature information includes the time stamp and address information of the I-picture in the AV stream, discontinuous point information of system time clocks, encoding parameters of the AV stream and change point information of the encoding parameters in the AV stream.
  • the multiplexed stream analysis unit 18 detects the picture of the aforementioned clip mark, from the input transport stream, and generates the information for specifying a picture designated by the clip mark and its type.
  • the user designation information from the terminal 24 is the information specifying the playback domain, designated by the user, character letters for explaining the contents of the playback domain, or the information such as bookmarks or resuming points set by the user for his or her favorite scene.
  • the controller 23 Based on the aforementioned input information, the controller 23 creates a database of the AV stream (Clip), a database of a group (PlayList) of playback domains (PlayItem) of the AV stream, management information of the recorded contents of the recording medium 100 (info.dvr) and the information on thumbnail pictures.
  • the application database information constructed from the above information, is processed in the ECC unit 20 and the modulation unit 21 and input to the write unit 22 , which then records a database file on the recording medium 100 .
  • the controller 23 When the AV stream file recorded on the recording medium 100 (files of picture data and speech data) and the application database information, thus recorded on the recording medium 100 , are reproduced by a reproducing unit 3 , the controller 23 first commands a readout unit 28 to read out the application database information from the recording medium 100 .
  • the readout unit 28 reads out the application database information from the recording medium 100 , which then reads out the application database information from the recording medium 100 to send the application database information through demodulation and error correction processing by a demodulating unit 29 and an ECC decoder 30 to the controller 23 .
  • the controller 23 Based on the application database information, the controller 23 outputs a list of PlayList recorded on the recording medium 100 to a user interface of the terminal 24 .
  • the user selects the PlayList, desired to be reproduced, from the list of PlayLists.
  • the information pertinent to PlayList, specified to be reproduced, is input to the controller 23 .
  • the controller 23 commands the readout unit 28 to read out the AV stream file necessary in reproducing the PlayList.
  • the readout unit 28 reads out the corresponding AV stream from the recording medium 100 to output the read-out AV stream to the demodulating unit 29 .
  • the AV stream thus input to the demodulating unit 29 , is demodulated by preset processing and output through the processing by the ECC decoder 30 to a source depacketizer 31 .
  • the source depacketizer 31 converts the AV stream of the application format, read out from the recording medium 100 and processed in a preset fashion, into a stream processable by the demultiplexer 26 .
  • the demultiplexer 26 outputs the system information (S), such as the video stream (V), audio stream (A) or the AV synchronization, forming the playback domain (PlayItem) of the AV stream specified by the controller 23 , to the audio decoder 27 , which AV decoder 27 decodes the video stream and the audio stream to output the playback video signal and the playback audio signal to associated terminals 32 , 33 , respectively.
  • S system information
  • V video stream
  • A audio stream
  • PlayItem the playback domain
  • the controller 23 determines the readout position of the AV stream from the recording medium 100 , based on the contents of the database (Clip) of the AV stream, to command the readout unit 28 to read out the AV stream. If the PlayList as selected by the user is to be reproduced as from a preset time point, the controller 23 commands the readout unit 28 to read out data from an I-picture having a time stamp closest to the specified time point.
  • the controller 23 determines the AV stream readout position from the recording medium 100 to command the readout unit 28 to read out the AV stream. That is, the controller 23 commands the readout unit 28 to read out data from an I-picture having an address closest to the address on the AV stream which has stored the picture selected by the user.
  • the readout unit 28 reads out data from the specified address.
  • the read-out data is processed by the demodulating unit 29 , ECC decoder 30 and by the source packetizer 19 so as to be supplied to the demultiplexer 26 and decoded by the audio decoder 27 to reproduce AV data indicated by an address of the mark point picture.
  • the controller 23 commands the readout unit 28 to sequentially read out I-picture data in the AV stream in succession based on the database (Clip) of the AV stream.
  • the readout unit 28 reads out data of the AV stream from a specified random access point.
  • the so read-out data is reproduced through processing by various components on the downstream side.
  • the controller 23 creates a database of the group (PlayList) of playback domains (PlayItem) of the AV streams.
  • the controller 23 When the user desires to erase a portion of the AV stream recorded on the recording medium 100 , the information pertinent to the IN-point and the OUT-point of the erasure domain is input to the controller 23 , which then modifies the database of the PlayList so as to refer to only the needed AV streams. The controller 23 also commands the write unit 22 to erase an unneeded stream portion of the AV stream.
  • the controller 23 creates a database of a group (PlayList) of the playback domains (PlayItem) of the AV stream and undertakes to partially re-encode and re-multiplex the video stream in the vicinity of junction points of the playback domains.
  • the picture information at the IN-point and that at the OUT-point of a playback domain are input from a terminal 24 to a controller 23 .
  • the controller 23 commands the readout unit 28 to read out data needed to reproduce the pictures at the IN-point and at the OUT-point.
  • the readout unit 28 reads out data from the recording medium 100 .
  • the data so read out is output through the demodulating unit 29 , ECC decoder 30 and the source packetizer 19 to the demultiplexer 26 .
  • the controller 23 analyzes data input to the demultiplexer 26 to determine the re-encoding method for the video stream (change of picture_coding_type and assignment of the quantity of encoding bits for re-encoding) and the re-multiplexing system to send the system to the AV encoder 15 and to the multiplexer 16 .
  • the demultiplexer 26 then separates the input stream into the video stream (V), audio stream (A) and the system information (S).
  • the video stream may be classed into data input to the audio decoder 27 and data input to the multiplexer 16 .
  • the former is data needed for re-encoding, and is decoded by the audio decoder 27 , with the decoded picture being then re-encoded by the AV encoder 15 and thereby caused to become a video stream.
  • the latter data is data copied from an original stream without re-encoding.
  • the audio stream and the system information are directly input to the multiplexer 16 .
  • the multiplexer 16 multiplexes an input stream, based on the information input from the controller 23 , to output a multiplexed stream, which is processed by the ECC unit 20 and the modulation unit 21 so as to be sent to the write unit 22 .
  • the write unit 22 records an AV stream on the recording medium 100 based on the control signals supplied from the controller 23 .
  • FIG. 2 shows the structure of an application format having two layers, that is PlayList and Clip, for AV stream management.
  • the Volume Information manages all Clips and PlayLists in the disc.
  • one AV stream and the ancillary information thereof, paired together, is deemed to be an object, and is termed Clip.
  • the AV stream file is termed a Clip AV stream file, with the ancillary information being termed the Clip Information file.
  • One Clip AV stream file stores data corresponding to an MPEG-2 transport stream arranged in a structure prescribed by the application format. By and large, a file is treated as a byte string. The contents of the Clip AV stream file are expanded on the time axis, with entry points in the Clip (I-picture) being mainly specified on the time basis. When a time stamp of an access point to a preset Clip is given, the Clip Information file is useful in finding the address information at which to start data readout in the Clip AV stream file.
  • PlayList is now explained, which is provided for a user to select a playback domain desired to be viewed from the Clip and to edit the playback domain readily.
  • One PlayList is a set of playback domains in the Clip.
  • One playback domain in a preset Clip is termed PlayItem and is represented by a pair of an IN-point and an OUT-point on the time axis. So, the PlayList is formed by a set of plural PlayItems.
  • the PlayList is classified into two types, one of which is Real PlayList and the other of which is Virtual PlayList.
  • the Real PlayList co-owns stream portions of the Clip it is referencing. That is, the Real PlayList takes up in the disc the data capacity corresponding to a stream portion of the Clip it is referencing and, when Real PlayList is erased, the data of the stream portion of the Clip it is referencing is also erased.
  • the Virtual PlayList is not co-owning Clip data. Therefore, if the Virtual PlayList is changed or erased, the contents of the Clip are in no way changed.
  • FIG. 4A shows creation of Real PlayList and, if the AV stream is recorded as a new Clip, the Real PlayList which references the entire Clip is a newly created operation.
  • FIG. 4B shows the division of the real PlayList, that is the operation of dividing the Real PlayList at a desired point to split the Real PlayList in two Real PlayLists.
  • This division operation is performed when two programs are managed in one clip managed by a sole PlayList and when the user intends to re-register or re-record the programs as separate individual programs. This operation does not lead to alteration of the Clip contents, that is to division of the Clip itself.
  • FIG. 4C shows the combining operation of the Real PlayList which is the operation of combining two Real PlayLists into one new Real PlayList.
  • This combining operation is performed such as when the user desires to re-register two programs as a sole program. This operation does not lead to alteration of the Clip contents, that is to combining the clip itself into one.
  • FIG. 5A shows deletion of the entire Real PlayList. If the operation of erasing the entire preset Real PlayList, the associated stream portion of the Clip referenced by the deleted Real PlayList is also deleted.
  • FIG. 5B shows partial deletion of the Real PlayList. If a desired portion of the Real PlayList is deleted, the associated PlayItem is altered to reference only the needed Clip stream portion. The corresponding stream portion of the Clip is deleted.
  • FIG. 5C shows the minimizing of the Real PlayList. It is an operation of causing the PlayItem associated with the Real PlayList to reference only the stream portion of the Clip needed for Virtual PlayList. The corresponding stream portion of the Clip not needed for the Virtual PlayList is deleted.
  • FIGS. 6A and 6B show the assembling and editing (ON-OUT editing). It is an operation of creating PlayItem of the playback domain the user has desired to view to create Virtual PlayList.
  • the seamless connection between PlayItems is supported by the application format, as later explained.
  • the user specifies a preset domain in the Real PlayList 1 (domain from IN 1 to OUT 1 : PlayItem 1 ) as the playback domain, and also specifies, as the domain to be reproduced next, a preset domain in the Real PlayList 2 (domain from IN 2 to OUT 2 : PlayItem 2 ) as the playback domain, as shown in FIG. 6A , a sole Virtual PlayList made up of PlayItem 1 and the PlayItem 2 is prepared, as shown in FIG. 6B .
  • the re-editing of the Virtual PlayList is now explained.
  • the re-editing may be enumerated by alteration of IN- or OUT points in the Virtual PlayList, insertion or appendage of new PlayItems to the Virtual PlayList and deletion of PlayItems in the Virtual PlayList.
  • the Virtual PlayList itself may also be deleted.
  • FIG. 7 shows the audio dubbing (post recording) to the Virtual PlayList. It is an operation of registering the audio post recording to the Virtual PlayList as a sub path. This audio post recording is supported by the application software. An additional audio stream is added as a sub path to the AV stream of the main path of the Virtual PlayList.
  • the mark (Mark) is now explained.
  • the mark is provided for specifying a highlight or characteristic time in the Clip and in the PlayList, as shown in FIG. 9 .
  • the mark added to the Clip is termed the ClipMark.
  • the ClipMark is e.g., a program indexing point or a scene change point for specifying a characteristic scene ascribable to contents in the AV stream.
  • the ClipMark is generated by e.g., the analysis unit 14 of FIG. 1 .
  • the mark of the Clip referenced by the PlayList may be referenced and used.
  • the mark appended to the PlayList is termed the PlayListMark (play list mark).
  • the PlayListMark is e.g., a bookmark point or a resuming point as set by the user.
  • the setting of the mark to the Clip and to the PlayList is by adding a time stamp indicating the mark time point to the mark list.
  • mark deletion is removing the time stamp of the mark from the mark list. Consequently, the AV stream is in no way changed by mark setting or by mark deletion.
  • a picture referenced by the ClipMark may be specified on the address basis in the AV stream.
  • Mark setting on the Clip is by adding the address basis information indicating the picture of the mark point to the mark list.
  • mark deletion is removing the address basis information indicating the mark point picture from the mark list. Consequently, the AV stream is in no way changed by mark setting or by mark deletion.
  • thumbnail is now explained.
  • the thumbnail is a still picture added to the Volume, PlayList and Clip.
  • Another sort of the thumbnail is a picture indicating a scene pointed by the mark.
  • the Volume and the respective PlayLists need to own representative pictures.
  • the representative pictures of the Volume are presupposed to be used for initially demonstrating a still picture representing the disc contents when the disc is set in position in the recording and/or reproducing apparatus 1 .
  • the disc means the recording medium 100 which is presupposed to be a of disc shape.
  • the representative picture of the PlayList is presupposed to be used as a still picture for representing PlayList contents.
  • the representative picture of the PlayList it may be contemplated to use the initial picture of the PlayList as the thumbnail (representative picture). However, the leading picture at the playback time of 0 is not necessarily an optimum picture representing the contents. So, the user is allowed to set an optional picture as a thumbnail of the PlayList.
  • Two sorts of the thumbnails that is the thumbnail as a representative picture indicating the Volume and the thumbnail as a representative picture indicating PlayList, are termed menu thumbnails. Since the menu thumbnails are demonstrated frequently, these thumbnails need to be read out at an elevated speed from the disc. Thus, it is efficient to store the totality of the menu thumbnails in a sole file. It is unnecessary for the menu thumbnails to be pictures extracted from the moving pictures in the volume, but may be a picture captured from a personal computer or a digital still camera, as shown in FIG. 10 .
  • the Clip and the PlayList need be marked with plural marks, whilst the pictures of the mark points need to be readily viewed in order to grasp the contents of the mark positions.
  • the picture indicating such mark point is termed a mark thumbnail. Therefore, the picture which is the original of the mark thumbnail is mainly an extracted mark point picture rather than a picture captured from outside.
  • FIG. 11 shows the relation between the mark affixed to the PlayList and the mark thumbnail
  • FIG. 12 shows the relation between the mark affixed to the Clip and the mark thumbnail.
  • the mark thumbnail is used in e.g., a sub-menu for representing details of the PlayList, while it is not requested to be read out in a short access time. So, whenever a thumbnail is required, the recording and/or reproducing apparatus 1 opens a file and reads out a portion of the file, while there is no problem presented even if file opening and reading out a portion of the file by the recording and/or reproducing apparatus 1 takes some time.
  • the totality of the mark thumbnails is stored in one file. While the PlayList may own one menu thumbnail and plural mark thumbnails, the user is not required to select the Clip directly (usually, the Clip is selected through PlayList), and hence there is no necessity of providing menu thumbnails.
  • FIG. 13 shows the relation between the menu thumbnails, mark thumbnails, PlayList and Clips.
  • the menu thumbnail file are filed menu thumbnails provided from one PlayList to another.
  • the menu thumbnail file is contained a volume thumbnail representing the contents of data recorded on the disc.
  • the menu thumbnail file are filed thumbnails created from one PlayList to another and from one Clip to another.
  • the CPI (Characteristic Point Information) is hereinafter explained.
  • the CPI is data contained in the Clip information file and is used mainly for finding a data address in the Clip AV stream file at which to start the data readout when a time stamp of the access point to the Clip is afforded.
  • two sorts of the CPI are used, one of them being EP_map and the other being TU_map.
  • the EP_map is a list of entry point (EP) data extracted from the elementary stream and the transport stream. This has the address information used to find the site of entry points in the AV stream at which to start the decoding.
  • One EP data is made up of a presentation time stamp (PTS) and a data address in the AV stream of the accessing unit associated with the PTS, with the data address being paired to the PTS.
  • PTS presentation time stamp
  • the EP_map is used mainly for two purposes. First, it is used for finding a data address in the AV stream in the accessing unit referenced by the PTS in the PlayList. Second, the EP_map is used for fast forward playback or fast reverse playback. If, in recording the input AV stream by the recording and/or reproducing apparatus 1 , the syntax of the stream can be analyzed, the EP_map is created and recorded on the disc.
  • the TU_map has a list of time unit (TU) data which is derived from the arrival time point of the transport packet input through a digital interface. This affords the relation between the arrival-time-based time and the data address in the AV stream.
  • TU_map is created and recorded on the disc.
  • the STCInfo stores the discontinuous point information in the AV stream file which stores the MPEG-2 transport stream.
  • the same PTS values may appear in the AV stream file.
  • the PTS pf the access point is insufficient to specify the point.
  • an index of the continuous STC domain containing the PTS is required.
  • the continuous STC domain and its index are termed an STC-sequence and STC-sequence-id, respectively.
  • the STC-sequence information is defined by the STCInfo of the Clip Information file.
  • the STC-sequence-id is used in an AV stream file and is optional in the AV stream file having the TU_map.
  • the programs are each a collection of elementary streams and co-own a sole system time base for synchronized reproduction of these streams.
  • a reproducing apparatus (recording and/or reproducing apparatus 1 of FIG. 1 ) to know the contents of an AV stream prior to its decoding.
  • contents include e.g., values of the PID of a transport packet transmitting an audio or video elementary stream or the type of the video or audio components, such as HDTV video or MPEG-2 AAC audio stream.
  • This information is useful for creating a menu screen foy illustrating to the user the contents of the PlayList referencing the AV stream. It is similarly useful for setting the initial state of the AV decoder and the demultiplexer of the respective apparatus.
  • the Clip Information file owns ProgramInfo for illustrating the program contents.
  • program contents be changed in the AV stream file in which the MPEG-2 transport stream is stored.
  • the PID of the transport packet transmitting the video elementary stream may be changed, or the component type of the video stream may be changed from SDTV to HDTV.
  • the ProgramInfo stores the information on change points of program contents in the AV stream file.
  • the domain of the AV stream file in which the program contents remain constant is termed program-sequence.
  • This program-sequence is used in an AV stream file having EP_map and is optional in an AV stream file having TU_map.
  • the present embodiment defines the self-encoding stream format (SESF).
  • SESF is used for encoding analog input signals and for decoding digital input signals for subsequently encoding the decoded signal into an MPEG-2 transport stream.
  • the SESF defines an elementary stream pertinent to the MPEG-2 transport stream and the AV stream.
  • an EP_map is created and recorded on the disc.
  • a digital broadcast stream uses one of the following systems for recording on the recording medium 100 : First, the digital broadcast stream is transcoded into an SESF stream. In this case, the recorded stream must conform to SESF and EP_map must be prepared and recorded on the disc.
  • an elementary stream forming a digital broadcast stream is transcoded to a new elementary stream and re-multiplexed to a new transport stream conforming to the stream format prescribed by the organization for standardizing the digital broadcast stream.
  • an EP_map must be created and recorded on the disc.
  • the input stream is an MPEG-2 transport stream conforming to the ISDB (standard appellation of digital BS of Japan), with the transport stream containing the HDTV video stream and the MPEG AAC audio stream.
  • the HDTV video stream is transcoded to an SDTV video stream, which SDTV video stream and the original AAC audio stream are re-multiplexed to TS.
  • the SDTV stream and the transport stream both need to conform to the ISDB format.
  • Another system of recording the digital broadcast stream on the recording medium 100 is to make transparent recording of the input transport stream, that is to record the input transport stream unchanged, in which case the EP_map is formulated and recorded on the disc.
  • the input transport stream is recorded transparently, that is an input transport stream is recorded unchanged, in which case TU_map is created and recorded on the disc.
  • FIG. 14 shows a typical directory structure on the disc.
  • the directories of the disc of the DVR may be enumerated by a root directory including “DVR” directory, and the “DVR” directory, including “PLAYLIST” directory, “CLIPINF” directory, “M2TS” 0 directory and “DATA” directory, as shown in FIG. 14 .
  • directories other than these may be created below the root directory, these are discounted in the application format of the present embodiment.
  • the “DVR” directory includes four directories.
  • Below the “PLAYLIST” directory Real PlayList and Virtual PlayList database files. The latter directory may exist in a state devoid of PlayList.
  • the “DVR” directory stores the following files: That is, an “info.dvr” is created below the DVR directory to store the comprehensive information of an application layer. Below the DVR directory, there must be a sole info.dvr. The filename is assumed to be fixed to info.dvr. The “menu.thmb” stores the information pertinent to the menu thumbnails. Below the DVR directory, there must be 0 or 1 mark thumbnail. The filename is assumed to be fixed to “menu.thmb”. If there is no menu thumbnail, this file may not exist.
  • the “mark.thmb” file stores the information pertinent to the mark thumbnail picture. Below the DVR directory, there must be 0 or 1 mark thumbnail. The filename is assumed to be fixed to “menu.thmb”. If there is no menu thumbnail, this file may not exist.
  • the “PLAYLIST” directory stores two sorts of the PlayList files which are Real PlayList and Virtual PlayList.
  • An “xxxxx.rpls” file stores the information pertinent to one Real PlayList.
  • One file is created for each Real PlayList.
  • the filename is “xxxxx.rpls”, where “xxxxx” denotes five numerical figures from 0 to 9.
  • a file extender must be “rpls”.
  • the “yyyyy.vpls” stores the information pertinent to one Virtual PlayList.
  • One file with a filename “yyyyy.vpls” is created from one Virtual PlayList to another, where “yyyyy” denotes five numerical figures from 0 to 9.
  • a file extender must be “vpls”.
  • the “CLIPINF” directory stores one file in association with each AV stream file.
  • the “zzzzz.clpi” is a Clip Information file corresponding to one AV stream file (Clip AV stream file or Bridge-Clip stream file).
  • the filename is “zzzzz.clpi”, where “zzzzz” denotes five numerical figures from 0 to 9.
  • a file extender must be “clpi”.
  • the “M2TS” directory stores an AV stream file.
  • the “zzzzz.m2ts” file is an AV stream file handled by the DVR system. This is a Clip AV stream file or a Bridge-Clip AV stream file.
  • the filename is “zzzzz.m2ts”, where “zzzzz” denotes five numerical figures from 0 to 9.
  • a file extender must be “m2ts”.
  • the “DATA” directory stores data transmitted from data broadcasting. This data may, for example, be XML or MPEG files.
  • FIG. 15 shows the syntax of the “info.dvr” file.
  • the “info.dvr” file is made up of three objects, that is DVRVoume( ), TableOfPlayLists( ) and MakersPrivateData( ).
  • the syntax of info.dvr shown in FIG. 15 is explained.
  • the TableOfPlayLists_Start_address indicates the leading address of the TableOfPlayLists( ) in terms of the relative number of bytes from the leading byte of the “info.dvr” file. The relative number of bytes is counted beginning from 0.
  • the MakersPrivate_Data_Start_address indicates the leading address of the MakersPrivateData( ), in terms of the relative number of bytes as from the leading byte of the “info.dvr” file. The relative number of bytes is counted from 0.
  • the padding_word is inserted in association with the syntax of “info.dvr”. N1 and N2 are optional positive integers. Each padding word may assume an optional value.
  • the DVRVolume( ) stores the information stating the contents of the volume (disc).
  • FIG. 16 shows the syntax of the DVRVolume. The syntax of the DVRVolume( ), shown in FIG. 16 , is now explained.
  • the version_number indicates four character letters indicting the version numbers of the DVRVolume( ).
  • the version_number is encoded to “0045” in association with ISO646.
  • Length is denoted by 32-bit unsigned integers indicating the number of bytes from directly after the length field to the trailing end of DVRVolume( ).
  • the ResumeVolume( ) memorizes the filename of the Real PlayList or the Virtual PlayList reproduced last in the Volume. However, the playback position when the user has interrupted playback of the Real PlayList or the Virtual PlayList is stored in the resume-mark defined in the PlayListMark( ) (see FIGS. 42 and 43 ).
  • FIG. 17 shows the syntax of the ResumeVolume( ).
  • the syntax of the ResumeVolume( ) shown in FIG. 17 is explained.
  • the valid_flag indicates that the resume_Play_List name field is valid or invalid when this 1-bit flag is set to 1 or 0, respectively.
  • the 10-byte field of resume_PlayList_name indicates the filename of the Real PlayList or the Virtual PlayList to be resumed.
  • the UIAppInfoVolume in the syntax of the DVRVolume( ), shown in FIG. 16 stores parameters of the user interface application concerning the Volume.
  • FIG. 18 shows the syntax of the UIAppInfoVolume, the semantics of which are now explained.
  • the 8-bit field of character_set indicates the encoding method for character letters encoded in the Volume_name field.
  • the encoding method corresponds to the values shown in FIG. 19 .
  • the 8-bit field of the name-length indicates the byte length of the Volume name indicated in the Volume_name field.
  • the Volume_name field indicates the appellation of the Volume.
  • the number of bytes of the number of the name_length counted from left of the field is the number of valid characters and indicates the volume appellation. The values next following these valid character letters may be any values.
  • the Volume_protect_flag is a flag indicating whether or not the contents in the Volume can be shown to the user without limitations. If this flag is set to 1, the contents of the Volume are allowed to be presented (reproduced) to the user only in case the user has succeeded in correctly inputting the PIN number (password). If this flag is set to 0, the contents of the Volume are allowed to be presented to the user even in case the PIN number is not input by the user.
  • the recording and/or reproducing apparatus 1 demonstrates a list of the PlayList in the disc.
  • the limitations on reproduction of the respective PlayLists are irrelevant to the Volume_protect_flag and are indicated by playback_control_flag defined in the UIAppInfoVolume.
  • the PIN is made up of four numerical figures of from 0 to 9, each of which is coded in accordance with ISO/IEC 646.
  • the ref_thumbnail_index field indicates the information of a thumbnail picture added to the Volume. If the ref_thumbnail_index field is of a value other than 0 ⁇ FFFF, a thumbnail picture is added to the Volume. The thumbnail picture is stored in a menu.thumb file. The picture is referenced using the value of the ref_thumbnail_index in the menu.thumb file. If the ref_thumbnail_index field is 0 ⁇ FFFF, it indicates that a thumbnail picture has been added to the Volume.
  • the TableOfPlayList( ) in the info.dvr syntax shown in FIG. 15 is explained.
  • the TableOfPlayList( ) stores the filename of the PlayList (Real PlayList and Virtual PlayList). All PlayList files recorded in the Volume are contained in the TableOfPlayList( ), which TableOfPlayList( ) indicates the playback sequence of the default of the PlayList in the Volume.
  • FIG. 20 shows the syntax of the TableOfPlayList( ), which is now explained.
  • the version_number of the TableOfPlayList( ) indicates four character letters indicating the version numbers of the TableOfPlayLists.
  • the version_number must be encoded to “0045” in accordance with ISO 646.
  • Length is a unsigned 32-bit integer indicating the number of bytes of the TableOfPlayList( ) from directly after the length field to the trailing end of the TableOfPlayList( ).
  • the 16-bit field of the number_of_PlayLists indicates the number of loops of the for-loop inclusive of the PlayList_file_name. This numerical figure must be equal to the number of PlayLists recorded in the Volume.
  • the 10-byte numerical figure of the PlayList_file_name indicates the filename of the PlayLists.
  • FIG. 21 shows another configuration of the syntax of the TableOfPlayList( ).
  • the syntax shown in FIG. 21 is comprised of the syntax shown in FIG. 20 in which is contained the UIAppInfoPlayList.
  • the UIAppInfoPlayList By such structure including the UIAppInfoPlayList, it becomes possible to create a menu picture simply on reading out the TableOfPlayLists.
  • the following explanation is premised on the use of the syntax shown in FIG. 20 .
  • the MakersPrivateData in the info.dvr shown in FIG. 15 is explained.
  • the MakersPrivateData is provided to permit the maker of the recording and/or reproducing apparatus 1 to insert private data of the maker in the MakersPrivateData( ) for special applications of different companies.
  • the private data of each maker has standardized maker_ID for identifying the maker who has defined it.
  • the MakersPrivateData( ) may contain one or more maker_ID.
  • FIG. 22 shows the syntax of the MakersPrivateData.
  • the syntax of the MakersPrivateData shown in FIG. 22 is explained.
  • the version_number of the TableOfPlayList( ) indicates four character letters indicating the version numbers of the TableOfPlayLists.
  • the version_number must be encoded to “0045” in accordance with ISO 646.
  • Length is a unsigned 32-bit integer indicating the number of bytes of the TableOfPlayList( ) from directly after the length field to the trailing end of the MakersPrivateData( ).
  • the mpd_blocks_start_address indicates the leading end address of the first mpd_block( ) in terms of the relative number of bytes from the leading byte of the MakersPrivateData( ).
  • the number_of_maker_entries is the 16-bit codeless integer affording the number of entries of the maker private data included in the MakersPrivateData( ). There must not be present two or more maker private data having the same maker_ID values in the MakersPrivateData( ).
  • the number_of_mpd_blocks is a 16-bit unsigned integer affording the number of mpd_blocks contained in the MakersPrivateData( ).
  • the maker_ID is the 16-bit unsigned integer indicating the model number code of the DVR system which has created the maker private data. The value encoded to the maker_ID is specified by the licensor.
  • the maker_model_code is a 16-bit unsigned integer indicating the model number code of the DVR system which has created the maker private data.
  • the value encoded to the maker_model_code is set by the maker who has received the license of the format.
  • the start mpd_block_number is a 16-bit unsigned integer indicating the number of the mpd_block number at which begins the maker private data. The leading end of the maker private data must be aligned with the leading end of the mpd_block.
  • the start_mpd_block_number corresponds to a variable j in the for-loop of the mpd_block.
  • the mpd_length is a 32-bit unsigned integer indicating the size of the maker private data.
  • the mpd_block is an area in which is stored maker private data. All of the mpd_blocks in the MakersPrivateData( ) must be of the same size.
  • FIG. 23 shows the syntax of xxxxx.rpls (Real PlayList) and yyyyy.vpls (Virtual PlayList), which are of the same syntax structure.
  • Each of the xxxxx.rpls and yyyyy.vpls is made up of three objects, that is PlayList( ), PlayListMark( ) and MakersPrivateData( ).
  • the PlayListMark_Start_address indicates the leading address of the PlayListMark( ), in terms of the relative number of bytes from the leading end of the PlayList file as a unit. The relative number of bytes is counted from zero.
  • the MakersPrivateData_Start_address indicates the leading address of the MakersPrivateData( ), in terms of the relative number of bytes from the leading end of the PlayList file as a unit. The relative number of bytes is counted from zero.
  • the padding_word (padding word) is inserted in accordance with the syntax of the PlayList file, with N1 and N2 being optional positive integers. Each padding word may assume an optional value.
  • PlayList will be further explained in the following although it has been explained briefly.
  • a playback domain in all Clips except Bridge-Clip must be referred by all PlayLists in the disc.
  • two or more Real PlayLists must not overlap the playback domains shown by their PlayItems in the same Clip.
  • FIGS. 24A , 24 B and 24 C For all Clips, there exist corresponding Real PlayLists, as shown in FIG. 24A . This rule is observed even after the editing operation has come to a close, as shown in FIG. 24B . Therefore, all Clips must be viewed by referencing one of Real PlayLists.
  • the playback domain of the Virtual PlayList must be contained in the playback domain and in the Bridge-Clip playback domain. There must not be present in the disc Bridge-Clip not referenced by any Virtual PlayList.
  • the Real PlayList containing the list of the PlayItem, must not contain SubPlayItem.
  • the Virtual PlayList contains the PlayItem list and, if the CPI_type contained in the PlayList( ) is the EP_map type and the PlayList_type is 0 (PlayList containing video and audio), the Virtual PlayList may contain one SubPlayItem. In the PlayList( ) in the present embodiment, the SubPlayItem is used only for audio post recording. The number of the SubPlayItems owned by one Virtual PlayList must be 0 or 1.
  • the PlayList is hereinafter explained.
  • FIG. 25 shows the PlayList syntax which is now explained.
  • the version_number indicates four character letters indicting the version numbers of the PlayList( ).
  • the version_number is encoded to “0045” in association with ISO 646.
  • Length is a 32-bit unsigned integer indicating the total number of byte of the PlayList( ) as from directly after the length field to the trailing end of the PlayList( ).
  • the PlayList_type one example of which is shown in FIG. 26 , is an 8-bit field indicating the PlayList type.
  • the CPI_type is one-bit flag indicating the value of the CPI_type of the Clip referenced by the PlayItem( ) and by the SubPlayItem( ).
  • the CPI_types defined in the CPIs of all Clips referenced by one PlayList must be of the same values.
  • the number_of_PlayItems is a 16-bit field indicating the number of PlayItems present in the PlayList.
  • the PlayItem_id corresponding to the preset PlayItem( ) is defined by the sequence in which the PlayItem( ) appears in the for-loop containing the PlayItem( ).
  • the PlayItem_id begins with 0.
  • the nimber_of_SubPlayItems is a 16-bit field indicating the number of SubPlayItem in the PlayList. This value is 0 or 1.
  • An additional audio stream path (audio stream path) is a sort of a sub path.
  • the UIAppInfoPlayList of the PlayList syntax shown in FIG. 25 is explained.
  • the UIAppInfoPlayList stores parameters of the user interface application concerning the PlayList.
  • FIG. 27 shows the syntax of the UIAppInfoPlayList, which is now explained.
  • the character_set is an 8-bit field indicating the method for encoding character letters encoded in the PlayList_name field.
  • the encoding method corresponds to the values conforming to the table shown in FIG. 19 .
  • the name_length is an 8-bit field indicating the byte length of the PlayList name indicated in the PlayList_name field.
  • the PlayList_name field shows the appellation of the PlayList.
  • the number of bytes of the number of the name_length counted from left of the field is the number of valid characters and indicates the PlayList appellation. The values next following these valid character letters may be any values.
  • the record_time and_date is a 56-bit field storing the date and time on which the PlayList was recorded.
  • This field is 14 numerical figures for year/month/day/hour/minute/second encoded in binary coded decimal (BCD). For example, 2001/12/23:01:02:03 is encoded to “0 ⁇ 20011223010203”.
  • the duration is a 24-bit field indicating the total replay time of the PlayList in terms of hour/minute/second as a unit.
  • This field is six numerical figures encoded in binary coded decimal (BCD). For example, 01:45:30 is encoded to “0 ⁇ 014530”.
  • the valid_period is a 32-bit field indicating the valid time periods of the PlayList. This field is 8 numerical figures encoded in 4-bit binary coded decimal (BCD).
  • BCD binary coded decimal
  • the valid_period is used in the recording and/or reproducing apparatus 1 e.g., when the PlayList, for which the valid period has lapsed, is to be automatically erased. For example, 2001/01/07 is encoded to “0 ⁇ 20010507”.
  • the maker_ID is a 16-bit unsigned integer indicating the maker of the DVR player (recording and/or reproducing apparatus 1 ) which has been the last to update its PlayList.
  • the value encoded to maker_ID is assigned to the licensor of the DVR format.
  • the maker_code is a 16-bit unsigned integer indicating the model number of the DVR player which has been the last to update the PlayList.
  • the value encoded to the maker_code is determined by the maker who has received the license of the DVR format.
  • the flag of the playback_control_flag is set to 1, its PlayList is reproduced only when the user successfully entered the PIN number. If this flag is set to 0, the user may view the PlayList without the necessity of inputting the PIN number.
  • the write_protect_flag is set to 1, the contents of the PlayList are not erased nor changed except the write_protect_flag. If this flag is set to 0, the user is free to erase or change the PlayList. If this flag is set to 1, the recording and/or reproducing apparatus 1 demonstrates a message requesting re-confirmation by the user before the user proceeds to erase, edit or overwrite the PlayList.
  • the Real PlayList in which the write_protect_flag is set to 0, may exist, the Virtual PlayList, referencing the Clip of the Real PlayList may exist, and the write_protect_flag of the Virtual PlayList may be set to 1. If the user is desirous to erase the Real PlayList, the recording and/or reproducing apparatus 1 issues an alarm to the user as to the presence of the aforementioned Virtual PlayList or “minimizes” the Real PlayList before erasing the Real PlayList.
  • is_played_flag is set to 1, as shown in FIG. 28B , it indicates that the PlayList was reproduced at least once since it was recorded, whereas, if it is set to 0, it indicates that the PlayList was not reproduced even once since it was recorded.
  • the Archive is a two-bit field indicating whether the PlayList is an original or a copy, as shown in FIG. 28C .
  • the field of ref_thumbnail_index indicates the information of a thumbnail picture representative of the PlayList. If the ref_thumbnail_index field is of a value other than 0 ⁇ FFFF, a thumbnail picture representative of the PlayList is added in the PlayList, with the PlayList being stored in the menu.thmb file. The picture is referenced using the value of ref_thumbnail_index in the menu.thmb file. If the ref_thumbnail_index field is 0 ⁇ FFFF, no thumbnail picture representative of the PlayList is added in the PlayList.
  • One PlayItem( ) basically contains the following data: Clip_Information_file_name for specifying the filename of the Clip, IN-time and OUT-time, paired together to specify the playback domain of Clip, STC_sequence_id referenced by IN-time and OUT-time in case the CPI_type defined in PlayList( ) is EP_map type, and Connection_Condition indicating the connection condition of previous PlayItem and current PlayItem.
  • PlayList is made up of two or more PlayItems, these PlayItems are arrayed in a row, without temporal gap or overlap, on the global time axis of the PlayList.
  • CPI_type defined in the PlayList is EP_map type and the current PlayList does not have the BridgeSequence( )
  • the IN-time and OUT-time pair must indicate the same time on the STC continuous domain as that specified by the STC_sequence_id. Such instance is shown in FIG. 29 .
  • FIG. 30 shows such a case in which the CPI_type defined by PlayList( ) and, if the current PlayItem has the BridgeSequence( ), the rules as now explained are applied.
  • the IN_time of the PlayItem previous to the current PlayItem shown as IN_time 1 , indicates the time in Bridge-Clip specified in the BridgeSequenceInfo( ) of the current PlayItem. This OUT_time must obey the encoding limitations which will be explained subsequently.
  • the IN_time of the current PlayItem indicates the time in Bridge-Clip specified in the BridgeSequenceInfo( ) of the current PlayItem. This IN_time also must obey the encoding limitations as later explained.
  • the OUT_time of PlayItem of the current PlayItem indicates the time on the STC continuous domain specified by STC_sequenbce_id of the current PlayItem.
  • the IN_time and OUT_time of PlayItem paired together, indicate the time on the same Clio AV stream, as shown in FIG. 31 .
  • the PlayItem syntax is as shown in FIG. 32 .
  • the field of the Clip_information_file_name indicates the filename of the Clip Information.
  • the Clip_stream_type defined by the ClipInfo( ) of this Clip Information file must indicate the Clip AV stream.
  • the STC_sequence_id is an 8-bit field and indicates the STC_sequence_id of the continuous STC domain referenced by the PlayItem. If the CPI_type specified in the PlayList( ) is TU_map type, this 8-bit field has no meaning and is set to 0.
  • IN_time is a 32-bit field and used to store the playback start time of PlayItem. The semantics of IN_time differs with CPI_type defined in the PlayList( ), as shown in FIG. 33 .
  • OUT_time is a 32-bit field and is used to store the playback end time of PlayItem.
  • the semantics of OUT_time differs with CPI_type defined in the PlayList( ), as shown in FIG. 34 .
  • Connection_condition is a 2-bit field indicating the connection condition between the previous PlayItem and the current PlayItem, as shown in FIG. 35 .
  • FIGS. 36A to 36D illustrate various states of Connection_condition shown in FIG. 35 .
  • BridgeSequenceInfo is explained with reference to FIG. 37 .
  • This BridgeSequenceInfo is the ancillary information of the current PlayItem and includes the following information. That is, BridgeSequenceInfo includes Bridge_Clip_Information_file_name for specifying the Bridge_Clip AV file and a Bridge_Clip_Information_file_name specifying the corresponding Clip Information file ( FIG. 45 ).
  • RSPN_exit_from_previous_Clip It is also an address of a source packet on the Clip AV stream referenced by the previous PlayItem. Next to this source packet is connected the first source packet of the Bridge-Clip AV stream. This address is termed the RSPN_exit_from_previous_Clip. It is also an address of the source packet on the Clip AV stream referenced by the current PlayItem. Ahead of this source packet is connected the last source packet of the Bridge_clip AV stream file. This address is termed RSPN_enter_to_current_Clip.
  • RSPN_arrival_time_discontinuity indicates an address of a source packet in the Bridge_Clip AV stream where there is a discontinuous point in the arrival time base. This address is defined in the ClipInfo( ) ( FIG. 46 ).
  • FIG. 38 shows the syntax of the BridgeSequenceInfo.
  • the field of Bridge_Clip_Information_file_name indicates the filename of the Clip Information file corresponding to the Bridge_Clip _Information_file.
  • the Clip_stream_type defined in ClipInfo( ) of this Clip information file must indicate ‘Bridge_Clip AV stream’.
  • the 32-bit field of the RSPN_exit_from_previous_Clip is a relative address of a source packet on the Clip AV stream referenced by the previous PlayItem. Next to this source packet is connected the first source packet of the Bridge_Clip AV stream file.
  • the RSPN_exit_from_previous_Clip has a size based on the source packet number as a unit, and is counted with the value of the offset_SPN defined in the ClipInfo( ) from the first source packet of the Clip AV stream file referenced by the previous PlayItem.
  • the 32-bit field of RSPN_enter_to_curent_Clip is the relative address of the source packet on the Clip AV stream referenced by the current PlayItem. Ahead of this source packet is connected the last source packet of the Bridge_Clip_AV stream file.
  • the RSPN_enter_to_curent_Clip has a size that is based on the source packet number as a unit.
  • the RSPN_enter_to_curent_Clip is counted with the value of the offset_SPN, defined in the ClipInfo( ) from the first source packet of the Clip AV stream file referenced by the current PlayItem, as an initial value.
  • the SubPlayItem is explained with reference to FIG. 39 .
  • the use of SubPlayItem( ) is permitted only if the CPI_type of the PlayList( ) is the EP_map type.
  • SubPlayItem is used only for audio post recording.
  • the SubPlayItem( ) includes the following data. First, it includes Clip_Information_file_name for specifying the Clip referenced by the sub path in the PlayList.
  • SubPath_IN_time and SubPath_OUT_time for specifying the sub path playback domain in the Clip. Additionally, it includes sync_PlayItem_id and start_PTS_of_PlayItem for specifying the time of starting the sub path reproduction on the main path time axis.
  • the Clip AV stream, referenced by the sub path must not contain STC discontinuous points (discontinuous points of the system time base). The clocks of audio samples of the Clip used in the sub path are locked to the clocks of the audio samples of the main path.
  • FIG. 40 shows the syntax of the SubPlayItem.
  • the field of the Clip__Information_file_name indicates the filename of the Clip Information file and is used by a sub path in the PlayList.
  • the Clip_stream_type defined in this ClipInfo( ) must indicate the Clip AV stream.
  • An 8-bit field of sync PlayItem id indicates the sub path type. Here, only ‘0 ⁇ 00’ is set, as shown in FIG. 41 , while other values are reserved for future use.
  • the 8-bit field of sync_PlayItem_id indicates the PlayItem_id of the PlayItem containing the time of playback start of the sub path on the time axis of the main path.
  • the value of PlayItem_id corresponding to the preset PlayItem is defined in the PlayList( ) ( FIG. 25 ).
  • a 32-bit field of sync_start_PTS_of_PlayItem denotes the time of playback start of the sub path on the time axis of the main path, and denotes the upper 32 bits of the PTS (presentation time stamp) on the PlayItem referenced by the sync_PlayItem_id.
  • the upper 32 bit field of the SubPath_IN_time stores the playback start time of the sub path.
  • SubPath_IN_time denotes upper 32 bits of the PTS of 33 bits corresponding to the first presentation unit in the sub path.
  • the upper 32 bit field of subPath_OUT_time stores the playback end time of the sub path.
  • PlayListMark( ) in the syntax of xxxxx.rpls and yyyyy.vpls shown in FIG. 23 is explained.
  • the mark information pertinent to the PlayList is stored in this PlayListMark.
  • FIG. 42 shows the syntax of PlayListMark.
  • version_number is four character letters indicating the version number of this PlayListMark( ).
  • the version_number must be encoded to “0045” in accordance with ISO 646.
  • Length is an unsigned 32-bit integer indicating the number of bytes of PlayListMark( ) from directly after the length field to the trailing end of the PlayListMark( ).
  • the number_of_PlayListMarks is a 16-bit unsigned integer indicating the number of marks stored in the PlayListMark.
  • the number_of_PlayListMarks may be zero.
  • the mark_type is an 8-bit field indicating the mark type and is encoded in the table shown in FIG. 43 .
  • a 32-bit filed of mark_time_stamp stores a time stamp indicating the point specified by the mark.
  • the semantics of the mark_time_stamp differ with CPI_type defined in the PlayList ( ), as shown in FIG. 44 .
  • the PlayItem_id is an 8-bit field specifying the PlayItem where the mark is put.
  • the values of PlayItem_id corresponding to a preset PlayItem is defined in the PlayList( ) (see FIG. 25 ).
  • An 8-bit field of character_set shows the encoding method of character letters encoded in the mark_name field.
  • the encoding method corresponds to values shown in FIG. 19 .
  • the 8-bit field of name_length indicates the byte length of the mark name shown in the mark_name field.
  • the mark_name field denotes the mark name indicated in the mark_name field.
  • the number of bytes corresponding to the number of name_lengths from left of this field is the effective character letters and denotes the mark name.
  • the value next following these effective character letters may be arbitrary.
  • the field of the ref_thumbnail_index denotes the information of the thumbnail picture added to the mark. If the field of the ref_thumbnail_index is not 0 ⁇ FFFF, a thumbnail picture is added to its mark, with the thumbnail picture being stored in the mark.thmb file. This picture is referenced in the mark.thmb file, using the value of ref_thumbnail_index, as explained subsequently. If the ref_thumbnail_index field is 0 ⁇ FFFF, it indicates that no thumbnail picture is added to the mark.
  • the Clip Information file is now explained.
  • the zzzzz.clpi (Clip Information file) is made up of six objects, as shown in FIG. 45 . These are ClipInfo( ), STC_Info( ), Program( ), CPI( ), ClipMark( ) and MakersPrivateData( ).
  • ClipInfo( ) STC_Info( )
  • Program( ) Program( )
  • CPI( ) CPI
  • ClipMark( ) MakersPrivateData( ).
  • the same string of numerals “zzzzz” is used for the AV stream (Clip AV stream or Bridge-Clip AV stream) and the corresponding Clip Information file.
  • the ClipInfo_Start_address indicates the leading end address of ClipInfo( ) with the relative number of bytes from the leading end byte of the zzzzz.clpi file as a unit. The relative number of bytes is counted from zero.
  • the STC_Info_Start_address indicates the leading end address of STC_Info with the relative number of bytes from the leading end byte of the zzzzz.clpi file as a unit.
  • the ProgramInfo_Start_address indicates the leading end address of ProgramInfo( ) with the relative number of bytes from the leading end byte of the zzzzz.clpi file as a unit. The relative number of bytes is counted from 0.
  • the CPI_Start_address indicates the leading end address of CPI( ) with the relative number of bytes from the leading end byte of the zzzzz.clpi file as a unit. The relative number of bytes is counted from zero.
  • the ClipMark_Start_address indicates the leading end address of ClipMark( ) with the relative number of bytes from the leading end byte of the zzzzz.clpi file as a unit. The relative number of bytes is counted from zero.
  • The_MakersPrivateData Start_address indicates the leading end address of MakersPrivateData( ) with the relative number of bytes from the leading end byte of the zzzzz.clpi file as a unit. The relative number of bytes is counted from zero.
  • the padding_word is inserted in accordance with the syntax of the zzzzz.clpi file. N1, N2, N3, N4 and N5 must be zero or optional positive integers. The respective padding words may also assume optional values.
  • FIG. 46 shows the syntax of ClipInfo.
  • FIG. 46 shows the syntax of ClipInfo.
  • the ClipInfo( ) is stored the attribute information of corresponding AV stream files (Clip AV stream or Bridge-Clip AV stream file).
  • version_number is the four character letters indicating the version number of this ClipInfo( ).
  • the version_number must be encoded to “0045” in accordance with the ISO 646.
  • Length is a 32-bit unsigned integer indicating the number of bytes of ClipInfo( ) from directly at back of the length field to the trailing end of the ClipInfo( ).
  • An 8-bit field of Clip_stream_type indicates the type of the AV stream corresponding to the Clip Information file, as shown in FIG. 47 . The stream types of the respective AV streams will be explained subsequently.
  • the 32-bit field of offset_SPN gives an offset value of the source packet number of the first source packet number of the first source packet of the AV stream (Clip AV stream or the Bridge-Clip AV stream). When the AV stream file is first recorded on the disc, this offset_SPN must be zero.
  • offset_SPN when the beginning portion of the AV stream file is erased by editing, offset_SPN may assume a value other than 0.
  • the relative source packet number (relative address) referencing the offset_SPN is frequently described in the form of RSPNxxx, where xxx is modified such that RSPN_xxx is RAPN_EP_start.
  • the relative source packet number is sized with the source packet number as a unit and is counted from the first source packet number of the AV stream file with the value of the offset_SPN as the initial value.
  • TS_recording_rate is a 24-bit unsigned integer, which affords an input/output bit rate required for the AV stream to the DVR drive (write unit 22 ) or from the DVR drive (readout unit 28 ).
  • the record_time_and date is a 56-bit field for storing the date and time of recording of the AV stream corresponding to the Clip and is an encoded representation of year/month/day/hour/minute in 4-bit binary coded decimal (BCD) for 14 numerical figures. For example, 2001/2/23:01:02:03 is encoded to “0 ⁇ 20011223010203”.
  • the duration is a 24-bit field indicating the total playback time of the Clip by hour/minute/second based on arrival time clocks.
  • This field is six numerical figures encoded in 4-bit binary coded decimal (BCD). For example, 01:45:30 is encoded to “0 ⁇ 014530”.
  • t denotes the time in seconds
  • start_time is the time point when the first source packet of the AV stream file was recorded.
  • the size_clip(t) is 10*192 bytes and ⁇ is a constant dependent on TS_average_rate.
  • time_controlled_flag is set to 0, it indicates that the recording mode is not controlling so that the time lapse of recording is proportionate to the file size of the AV stream. For example, the input transport stream is recorded in a transparent fashion.
  • variable bit rate transport stream is encoded by the following sequence: First, the transport rate is set to the value of TS_recording_rate. The video stream is encoded with a variable bit rate. The transport packet is intermittently encoded by not employing null packets.
  • the 32-bit field of RSPN_arrival_time_discontinuity is a relative address of a site where arrival timebase discontinuities are produced on the Bridge-Clip AV stream file.
  • the RSPN_arrival_time_discontinuity is sized with the source packet number as a unit and is counted with the value of offset_SPN defined in the ClipInfo( ) as from the first source packet of the Bridge-Clip AV stream file.
  • is_country_code_valid flag is 1, it indicates that the field country_code is valid.
  • the 32-bit field of format_identifier indicates the value of format_identifier owned by a registration descriptor (defined in ISO/IEC13818-1) in the transport stream.
  • the 16-bit field of original_network_ID indicates the value of the original_network_ID defined in the transport stream.
  • the 16-bit field in servece_ID denotes the value of servece_ID defined in the transport stream.
  • the 24-bit field of country_code shows a country code defined by ISO3166. Each character code is encoded by IS 0 8859-1. For example, Japan is represented as “JPN” and is encoded to “0 ⁇ 4A 0 ⁇ 50 0 ⁇ 4E”.
  • the stream_format_name is 15 character codes of ISO-646 showing the name of a format organization affording stream definitions of transport streams. An invalid byte in this field has a value of ‘0 ⁇ FF’.
  • Format_identifier, original_network_ID, transport_stream_ID, servece_ID, country_code and stream_format_name indicate service providers of transport streams. This allows to recognize encoding limitations on audio or video streams and stream definitions of private data streams other than audio video streams or SI (service information). These information can be used to check if the decoder is able to decode the stream. If such decoding is possible, the information may be used to initialize the decoder system before starting the decoding.
  • STC_Info The time domain in the MPEG-2 transport stream not containing STC discontinuous points(discontinuous points of the system time base) is termed the STC_sequence.
  • STC_sequence is specified by the value of STC_sequence_id.
  • FIGS. 50A and 50B illustrate a continuous STC domain.
  • the same STC values never appear in the same STC_sequence, although the maximum tine length of Clip is limited, as explained subsequently. Therefore, the same PTS values also never appear in the same STC_sequence. If the AV stream contains N STC discontinuous points, where N>0, the Clip system time base is split into (N+1) STC_sequences.
  • STC_Info stores the address of the site where STC discontinuities (system timebase discontinuities) are produced.
  • the RSPN_STC_start indicates the address and begins at a time point of arrival of the source packet referenced by the (k+1)st RSPN_STC_start and ends at a time point of arrival of the last source packet.
  • FIG. 52 shows the syntax of the STC_Info.
  • version_number is four character letters indicating the version number of STC_Info( ).
  • the version_number must be encoded to “0045” in accordance with ISO 646.
  • Length is a 32-bit unsigned integer indicating the number of bytes of STC_Info( ) from directly after this length field to the end of STC_Info. If CPI_type of CPI( ) indicates TU_map type, 0 may be set in this length field. If CPI_type of CPI( ) indicates EP_map type, the num_of_STC_sequence mut be of a value not less than 1.
  • the 32-bit field of RSPN_STC_start indicates an address at which the STC_sequence commences on the AV stream file.
  • RSPN_STC_start denotes an address where system time base discontinuities are produced in the AV stream file.
  • the RSPN_STC_start may also be a relative address of the source packet having the first PCR of the new system time base in the AV stream.
  • the RSPN_STC_start is of a size based on the source packet number and is counted from the first source packet of the AV stream file with the offset_SPN value defined in ClipInfo( ) as an initial value.
  • ProgramInfo in the syntax of zzzz.clip shown in FIG. 45 is now explained with reference to FIG. 53 .
  • the time domain having the following features in the Clip is termed program_sequence. These feature are that the value of PCR_PID is not changed, the number of audio elementary streams is also not changed, the PID values in the respective video streams are not changed, the encoding information which is defined by VideoCondingInfo thereof is not changed, the number of audio elementary streams is also not changed, the PID values of the respective audio streams are not changed, and that the encoding information, which is defined by AudoCodingInfo thereof, is not changed.
  • Program_sequence has only one system time base at the same time point.
  • Program_sequence has a sole PMT at the same time point.
  • ProgramInfo( ) stores the address of the site where the program_sequence commences.
  • RSPN program_sequence-start indicates the address.
  • FIG. 54 illustrates the syntax of ProgramInfo.
  • version_number is four character letters indicating the version number of ProgramInfo( ).
  • the version_number must be encoded to “0045” in accordance with ISO 646.
  • Length is a 32-bit unsigned integer indicating the number of bytes of ProgramInfo( ) from directly at back of this length field to the end of program(info( ). If CPI_type of CPI( ) indicates the TU_map type, this length field may be set to 0. If the CPI_type of CPI( ) indicates EP_map type, the number_of_programs must be of a value not less than 1.
  • An 8-bit unsigned integer of number_of_program_sequences denotes the number of program_sequences in the Clip. This value indicates the number of for-loops next following this field. If program_sequence in the Clip is not changed, 1 must be set in the number of program_sequences.
  • a 32-bit field of RSPN_program_sequence_start is a relative address where the program sequence commences on the AV stream.
  • RSPN_program_sequence_start is sized with the source packet number as a unit and is counted with the value of offset_SPN defined in the ClipInfo( ) as from the first source packet of the AV stream file.
  • a 16-bit field of PCR_PID denotes the PID of the transport packet containing an effective PCR field effective for the program_sequence.
  • An 8-bit field of number_of_audios indicates the number of for-loops containing audio_stream_PID and AudoCondingInfo( ).
  • a 16-bit field of video_stream_PID indicates the PID of the transport packet containing a video stream effective for its program_sequence.
  • VideoCodingInfo( ) next following this field, must explain the contents of the video stream referenced by its video_stream_PID.
  • a 16-bit field of audio_stream_PID indicates the PID of a transport packet containing the audio stream effective for its program_sequence.
  • the AudioCodingInfo( ), next following this field, must explain the contents of the video stream referenced by its audio_stream_PID.
  • FIG. 55 shows the syntax of VideoCodingInfo in the syntax of the ProgramInfo shown in FIG. 54 .
  • an 8-bit field of video_format indicates the video format corresponding to video_stream_PID in ProgramInfo( ), as shown in FIG. 56 .
  • an 8-bit field of frame_rate indicates the video frame rate corresponding to the video_stream_PID in ProgramInfo( ).
  • An 8-bit field of display_aspect_ratio indicates a video display aspect ratio corresponding to video_stream_PID in ProgramInfo( ).
  • FIG. 59 shows the syntax of AudioCodingInfo in the syntax of ProgramInfo shown in FIG. 54 .
  • an 8-bit field of audio_format indicates the audio encoding method corresponding to audio_stream_PID in ProgramInfo( ), as shown in FIG. 60 .
  • An 8-bit field of audio_component_type indicates an audio component type corresponding to audio_stream_PID in ProgramInfo( ) as shown in FIG. 61
  • an 8-bit field of sampling_frequency indicates an audio sampling frequency corresponding to audio_stream_PID in ProgramInfo( ) as shown in FIG. 62 .
  • the CPI (Characteristics Point Information) in the syntax of zzzzz.clip shown in FIG. 45 is explained.
  • the CPI is used for correlating the time information in the AV stream with the address in its file.
  • the CPI is of two types, namely EP_map and TU_map.
  • FIG. 63 if CPI_type in CPI( ) is EP_map, its CPI( ) contains EP_map.
  • FIG. 64 if CPI_type in CPI( ) is TU_map, its CPI( ) contains TU_map.
  • One AV stream has one EP_map or one TU_map. If the AV stream is an SESF transport stream, the corresponding Clip must own an EP_map.
  • FIG. 65 show the syntax of CPI.
  • the version_number is four character letters indicating the version number of this CPI( ).
  • the version_number must be encoded to “0045” in accordance with ISO 646.
  • Length is a 32-bit unsigned integer indicating the number of bytes as from directly after this length field to the trailing end of the CPI( ).
  • the CPI_type is a 1-bit flag and indicates the CPI type of Clip, as shown in FIG. 66 .
  • the EP_map in the CPI syntax shown in FIG. 65 is explained.
  • the EP_map_type in the EP_map differentiates between these EP_map types. If the Clip contains one or more video streams, the EP_map for the video stream must be used. If the Clip does not contain a video stream but contains one or more audio streams, the EP_map for the audio stream must be used.
  • the EP_map for a video stream is explained with reference to FIG. 67 .
  • the EP_map for the video stream has data stream_PID, PTS_EP_start and RSPN_EP_start.
  • the stream_PID shows the PID of the transport packet transmitting a video stream.
  • the PTS_EP_start indicates the PTS of an access unit beginning from the sequence header of the video stream.
  • the RSPN_RP_start indicates the address A of a source packet including the first byte of the access unit referenced by the PTS_EP_start in the AV stream.
  • EP_map_for_one_stream_PID( ) A sub table, termed EP_map_for_one_stream_PID( ) is created from one video stream transmitted by the transport packet having the same PID to another. If plural video streams exist in the Clip, the EP_map may contain plural EP_map_for_one_stream PID( ).
  • the EP_map for audio stream has data stream_PID, PTS_EP_start and RSPN_EP_start.
  • the stream_PID shows a PID of a transport packet transmitting an audio stream.
  • the PTS_EP_start shows the PTS of an accessing unit in the audio stream.
  • the RSPN_EP-start indicates an address of a source packet containing a first byte of the access unit referenced by PTS_EP_start of the AV stream.
  • EP_map_for_one_stream_PID( ) is created from one audio stream transmitted by the transport packet having the same PID to another. If there exist plural audio streams in the Clip, EP_map may contain plural EP_map_for_one_stream_PID( ).
  • FIG. 70 shows the EP_map syntax.
  • the EP_type is a 4-bit field and shows the EP_map entry point type, as shown in FIG. 71 .
  • the EP_type shows the semantics of the data field next following this field. If Clip includes one or more video stream, the EP_type must be set to 0 (‘video’). Alternatively, if the Clip contains no video stream but contains one or more audio stream, then EP_type must be set to 1 (‘audio’).
  • the 16-bit field of number_of_stream_PIDs indicates the number of times of loops of the for-loop having number_of_stream_PIDs in the EP_map( ) as a variable.
  • the 16-bit field of stream_PID(k) indicates the PID of the transport packet transmitting the number k elementary stream (video or audio stream) referenced by EP_map_for_one_stream_PID (num_EP_entries(k)). If EP_type is 0 (‘video’), its elementary stream must be a video stream. If EP_type is equal to 1 (‘audio’), its elementary stream must be the audio stream.
  • the 16-bit field of num_EP_entries(k) indicates the num_EP_entries(k) referenced by EP_map_entries(k)).
  • Padding_word must be inserted in accordance with the EP_map( ) syntax.
  • X and Y must be optional positive integers.
  • the respective padding words may assume any optional values.
  • FIG. 72 shows the syntax of EP_map_for_one_stream_PID.
  • the semantics of the 32-bit field of PTS_EP_start differs with the EP_type defined by EP_map( ). If EP_type is equal to 0 (‘video’), this field has upper 32 bits of the 33-bit precision PTS of the access unit beginning with a sequence header of the video stream. If the EP_type is equal to 1 (‘audio’), this field has upper 32 bits of PTS of 33 bit precision of the access unit of the audio stream.
  • EP_type is equal to 0 (‘video’)
  • this field indicates the relative address of the source packet including the first byte of the sequence header of the access unit referenced by the PTS_EP_start in the AV stream.
  • EP_type is equal to 1 (‘audio’)
  • this field indicates the relative address of the source packet containing the first byte in the audio stream of the access unit referenced by the PTS_EP_start in the AV stream.
  • RSPN_EP_start is of a size which is based on the source packet number as a unit, and is counted from the first source packet of the AV stream file, with the value of the offset_SPN, defined in ClipInfo( ), as an initial value.
  • TU_map forms a time axis based on the source packet arrival time clock (timepiece of the arrive time base). This time axis is termed TU_map_time_axis.
  • the point of origin of TU_map_time_axis is indicated by offset_time in the TU_map( ).
  • TU_map_time_axis is divided in a preset unit as from offset_time, this unit being termed time_unit.
  • TU_start_time(k) has a precision of 45 kHz.
  • FIG. 74 shows the syntax of TU_map.
  • the 32-bit field of offset_time gives an offset time relative to TU_map_time_axis. This value indicates the offset time relative to the first time_unit in the Clip.
  • the offset_time is of a size based on 45 kHz clock derived from the 27 MHz precision arrival time clocks as unit. If the AV stream is to be recorded as new Clip, offset_time must be set to 0.
  • time_unit_size affords the size of the time_unit, and is based on 45 kHz clocks, derived from the 27 MHz precision arrival time clocks, as unit.
  • time_unit_size is not longer than one second (time_unit_size ⁇ 45000).
  • the 32bit field of number_of_time_unit_entries indicates the number of entries stored in TU_map( ).
  • RSN_time_unit_start indicates the relative address of a site in the AV stream at which begins each time_unit.
  • RSN_time_unit_start is of a size based on the source packet number as unit and is counted with the value of offset_SPN defined in ClipInfo( ) as from the first source packet of the AV stream file as an initial value.
  • RSN_time_unit_start in the for-loop of the syntax must appear in the rising order. If there is no source packet in the number (k+1) time_unit, the number (k+1) RSN_time_unit_start must be equal to the number k RSPN_time_unit_start.
  • the ClipMark is the mark information pertinent to clip and is stored in the ClipMark. This mark is not set by a user, but is set by a recorder (recording and/or reproducing apparatus 1 ).
  • FIG. 75 shows the ClipMark syntax.
  • the version_number is four character letters indicating the version number of this ClipMark.
  • the version_number must be encoded in accordance with ISO 646 to “0045”.
  • Length is a 32-bit unsigned integer indicating the number of bytes of the ClipMark( ) as from directly after the length field to the trailing end of ClipMark( ).
  • the number_of_Clip_marks is a 16-bit unsigned integer indicating the number of marks stored in ClipMark and may be equal to 0.
  • Mark_type is an 8-bit field indicating the mark type and is encoded in accordance with the table shown in FIG. 76 .
  • Mark_time_stamp is a 32-bit field and stores the time stamp indicating a pointer having a specified mark.
  • the semantics of mark_time_stamp differs with CPI_type in the PlayList( ), as shown in FIG. 77 .
  • this 8-bit field indicates the STC_sequence_id of the continuous STC domain where there is placed mark_time_stamp. If CPI_type in CPI( ) indicates TU_map type, this 8-bit field has no meaning but is set to 0.
  • the 8-bit field of Character_set indicates the indicating method of character letters encoded in the mark_name field. The encoding method corresponds to the value shown in FIG. 19 .
  • the 8-bit field of name_length indicates the byte length of the mark name shown in the mark_name field.
  • This mark name field indicates the mark name.
  • the byte number corresponding to the number of the name_length from left of this field is the effective character number and denotes the mark name.
  • the values next following these effective character letters may be arbitrary.
  • the field of ref_thumbnail_index indicates the information of the thumbnail picture appended to the mark. If the ref_thumbnail_index field is of a value different from 0 ⁇ FFFF, a thumbnail picture is added to its mark, with the thumbnail picture being stored in the mark.thumb file. This picture is referenced using the value of ref_thumbnail_index in the mark.thumb file. If the ref_thumbnail_index field is of a value equal to 0 ⁇ FFFF, a thumbnail picture is not appended to its mark.
  • thumbnail_information is explained.
  • a thumbnail picture is stored in a menu.thmb file or in a mark.thmb file. These files are of the same syntax structure and own a sole Thumbnail( ).
  • the menu.thmb file stores a picture representing respective PlatyLists. The totality of menu thumbnails are stored in the sole menu.thmb file.
  • the mark.thmb file stores a mark thumbnail picture, that is a picture representing a mark point.
  • the totality of mark thumbnails corresponding to the totality of PlayLists and Clips are stored in the sole mark.thmb file. Since the thumbnails are frequently added or deleted, the operation of addition and partial deletion must be executable readily and speedily. For this reason, Thmbnail( ) has a block structure. Picture data is divided into plural portions each of which is stored in one tn_block. One picture data is stored in consecutive tn_blocks. In the string of tn_blocks, there may exist a tn_block not in use. The byte length of a sole thumbnail picture is variable.
  • FIG. 78 shows the syntax of menu.thmb and mark.thmb and FIG. 79 the syntax of Thumbnail in the syntax of menu.thmb and mark.thmb shown in FIG. 78 .
  • version_number is four character letters denoting the version number of this Thumbnail( ). Version_number must be encoded to “0045” in accordance with ISO 646.
  • Length is a 32-bit unsigned integer indicating the number of bytes of MakerPrivateData( ) as from directly at back of the length field up to the trailing end of Thumbnail( ).
  • Tu_block_start_address is a 32-bit unsigned integer indicating the leading end byte address of the first tn_block, in terms of the relative number of bytes as from the leading end byte of Thumbnail( ) as a unit. The number of relative bytes is counted from 0.
  • Number_of_thumbnails is a 16-bit unsigned integer which gives the number of entries of a thumbnail picture contained in Thumbnail( ).
  • Number_of_tn_blocks is a 116-bit unsigned integer indicating the number of entries of tn_block in this Thumbnail( ).
  • Thumbnail_index is a 16-bit unsigned integer indicating the index number of the thumbnail picture represented by the thumbnail information for one for-loop beginning from the thumbnail_index field. The value 0 ⁇ FFFF must not be used as Thumbnail_index. This Thumbnail_index is referenced by ref_thumbnail_index in UIAppInfoVolume( ), UIAppInfoPlayList( ), PlayListMark( ) and ClipMark( ).
  • Thumbnail_picture_format is an 8-bit unsigned integer representing the picture format of a thumbnail picture and assumes a value shown in FIG. 80 .
  • DCF and PNG are allowed only in menu.thumb.
  • the mark thumbnail must assume the value of “0 ⁇ 00” (MPEG-2 Video 1-picture).
  • Picture_data_size is a 32-bit unsigned integer indicating the byte length of a thumbnail picture in terms of bytes as a unit.
  • Start_tn_block_number is a 16-bit unsigned integer indicating the tn_block number of the tn_block where data of the thumbnail picture begins. The leading end of the thumbnail picture data must coincide with the leading end of the tn_block.
  • the tn_block number begins from 0 and is relevant to the value of a variable k in the for-loop of tn_block.
  • X_picture_length is a 16-bit unsigned integer indicating the number of pixels in the horizontal direction of a frame of a thumbnail picture.
  • Y_picture_length is a 16-bit unsigned integer indicating the number of pixels in the vertical direction of a frame of a thumbnail picture.
  • Tn_block is an area in which to store a thumbnail picture. All tn_block in the Thumbnail( ) are of the same size (fixed length) and are of a size defined by tn_block_sixe.
  • FIGS. 81A and 81B schematically show how thumbnail picture data are stored in tn_block. If, as shown in FIGS. 81A and 81B , the thumbnail picture begins at the leading end of tn_block, and is of a size exceeding 1 tn block, it is stored using the next following tn_block. By so doing, data with a variable length can be managed as fixed length data, so that the editing of deletion can be coped with by simpler processing.
  • the AV stream file is stored in the “M2TS” directory ( FIG. 14 ).
  • the AV stream file There are two types of the AV stream file, namely a Clip A stream file and a Bridge-Clip AV stream file. Both AV streams must be of the structure of DVR MPEG-2 transport stream file as hereinafter defined.
  • the structure of the DVR MPEG-2 transport stream is shown in FIG. 82 .
  • the AV stream file has the structure of a DVR MPEG 2 transport stream.
  • the DVR MPEG 2 transport stream is made up of an integer number of Aligned units.
  • the size of the aligned unit is 6144 bytes (2048*3 bytes).
  • the Aligned unit begins from the first byte of the source packet.
  • the source packet is 192 bytes long.
  • One source packet is comprised of TP_extra_header and a transport packet.
  • TP_extra_header is 4 bytes long, with the transport packet being 188 bytes long.
  • One Aligned unit is made up of 32 source packets.
  • the file system must not use excess information in the DVR MPEG 2 transport stream.
  • FIG. 83 shows a recorder model of the DVR MPEG 2 transport stream.
  • the recorder shown in FIG. 83 is a conceptual model for prescribing the recording process.
  • the DVR MPEG 2 transport stream obeys this model.
  • the input timing of the MPEG 2 transport stream is now explained.
  • the input MPEG 2 transport stream is a full transport stream or a partial transport stream.
  • the input MPEG 2 transport stream must obey the ISO/IEC13818-1 or ISO/IEC 13818-9.
  • the number i byte of the MPEG 2 transport stream is input simultaneously at time t(i) to T-STD (transport stream system target decoder provided for in SO/IEC13818-1) and to the source packetizer.
  • Rpk is an instantaneous maximum value of the input rate of the transport packet.
  • a 27 MHz PLL 52 generates a frequency of 27 MHz clock.
  • the 27 MHz clock frequency is locked at a value of the program clock reference (PCR) of the MPEG 2 transport stream.
  • An arrival time clock counter 53 counts the pulses of the 27 MHz frequency.
  • Arrival_time_clock(i) is a count value of the arrival time clock counter at time t(i).
  • a source packetizer 54 appends TP_extra header to the totality of the transport packets to create a source packet.
  • Arrival_time_stamp indicates the time when the first byte of the transport packet reaches both the T-STD and the source packetizer.
  • the difference of the arrival_time_stamp of the two transport packets should be set to 230/2 7000000 sec.
  • the recorder is provided for such case.
  • a smoothing buffer 55 smoothes the bitrate of the input transport stream.
  • the smoothing buffer must not overflow.
  • Rmax is the output bitrate of the source packet from the smoothing buffer when the smoothing buffer is not null. If the smoothing buffer is null, the output bitrate of the smoothing buffer is 0.
  • Rpk must be equal to TS_recording_rate as defined in ClipInfo( ) associated with the AV stream file. If the input transport stream is not an SESF transport stream, reference may be made to values defined e.g., in a descriptor of the MPEG 2 transport stream, such as maximum_bitrate_descriptor or partial_stream_descriptor for this value.
  • the smoothing buffer size is 0. If the input transport stream is an SESF transport stream, the smoothing buffer size is 0. If the input transport stream is not an SESF transport stream, reference may be made to values defined in the descriptor of the MPEG 2 transport stream, such as, for example, the values defined in the smoothing_buffer_descriptor, short_smoothing_buffer_descriptor or in the partial_transport_stream_descriptor.
  • the default buffer size is 1536 bytes.
  • FIG. 84 shows a player model of the DVR MPEG 2 transport stream. This is a conceptual model for prescribing the reproduction process.
  • the DVR MPEG 2 transport stream obeys this model.
  • a 27 MHz X-tal 61 generates the frequency of 27 MHz.
  • An error range of the 27 MHx frequency must be ⁇ 30 ppm (2 7000000 ⁇ 810 Hz).
  • the arrival time clock counter 62 is a binary counter for counting the pulses of the frequency of 27 MHz.
  • Arrival_time_clock(i) is a count value of the arrival time clock counter at time t(i).
  • Rmax is the input bitrate of the source packet to the smoothing buffer when the smoothing buffer is not full. If the smoothing buffer is full, the input bitrate to the smoothing buffer is 0.
  • the transport packet of the source packet is removed from the smoothing buffer.
  • Rpk is an instantaneous maximum value of the transport packet rate. The overflow of the smoothing buffer is not allowed.
  • the parameters of the player model of the DVR MPEG 2 transport stream are the same as those of the recorder model of the DVR MPEG 2 transport stream described above.
  • FIG. 85 shows the syntax of the source packet.
  • Transport_packet( ) is an MPEG 2 transport stream provided in ISO/IEC 13818-1.
  • the syntax of TP_Extra-header in the syntax of the source packet shown in FIG. 85 is shown in FIG. 86 .
  • copy_permission_indicator is an integer representing the copying limitation of the payload of the transport packet. The copying limitation may be copy free, no more copy, copy once or copying prohibited.
  • FIG. 87 shows the relation between the value of copy_permission_indicator and the mode it designates.
  • Copy permission_indicator is appended to the totality of transport packets. If the input transport stream is recorded using the IEEE1394 digital interface, the value of copy_permission_indicator may be associated with the value of EMI (encryption mode indicator). If the input transport stream is recorded without employing the IEEE1394 digital interface, the value of copy_permission_indicator may be associated with the value of the CCI embedded in the transport packet. If an analog signal input is self-encoded, the value of copy_permission_indicator may be associated with the value of CGMS-A of the analog signal.
  • EMI encryption mode indicator
  • the ClipAV stream must have a structure of the DVR MPEG 2 transport stream defined as described above. Arrival_time_clock(i) must increase continuously in the Clip AV stream. If there exists a discontinuous point of the system time base (STC base) in the Clip AV stream, arrival_time_clock(i) in the Clip AV stream must increase continuously.
  • STC base system time base
  • the maximum value of the different of the arrival_time_clock(i) between the beginning and the end of the Clip AV stream must be 26 hours. This limitation guarantees that, if there is no discontinuous point in the system time base (STC base) in the MPEG 2 transport stream, the PTS (presentation time stamp) of the same value never appears in the Clip AV stream.
  • STC base system time base
  • the MPEG 2 system standard provides that the PTS has a wraparound period of 233/90000 sec (about 26.5 hours).
  • the Bridge-Clip AV stream must have a structure of the DVR MPEG 2 transport stream defined as described above.
  • the Bridge-Clip AV stream must include a discontinuous point of one arrival time base. The transport stream ahead and at back of the discontinuous point of the arrival time base must obey the encoding limitations and the DVR-STD as later explained.
  • the present embodiment supports the video-audio seamless connection between PlayItems being edited. Seamless connection between PlayItems guarantees “continuous data supply” to the player/decoder and “seamless decoding processing”.
  • the “continuous data supply” is the capability of guaranteeing data supply to the decoder at a bitrate necessary to prevent buffer underflow. In order to enable data to be read out from the disc as data real-time properties are assured, data is to be stored in terms of a continuous block of a sufficiently large size as a unit.
  • the “seamless decoding processing” means the capability of a player in displaying audio video data recorded on the disc without producing pause or gap in the playback output of the decoder.
  • the AV stream referenced by the seamless connected PlayItems, is explained. Whether or not the seamless display of a previous PlayItem and the current PlayItem is guaranteed may be verified from the connection_condition field defined in the current PlayItem.
  • FIG. 88 shows the relation between the previous PlayItem and the current PlayItem in case of employing Bridge-Clip.
  • the stream data, read out by the player is shown shaded.
  • TS 1 is made up of shaded stream data of the Clip 1 (Clip AV stream) and shaded stream data previous to RSPN_arrival_time_discontinuity.
  • the shaded stream data of Clip 1 of TS 1 is stream data from an address of a stream required for decoding the presentation unit corresponding to IN_item of the previous PlayItem (shown as IN-time 1 in FIG. 88 ) up to the source packet referenced by RSPN_exit_from_previous_Clip.
  • the shaded stream data prior to RSPN_arrival_time_discontinuity of Bridge-Clip contained in TS 1 is stream data as from the first source packet of Bridge-Clip up to the source packet directly previous to the source packet referenced by RSPN_arrival time_discontinuity.
  • TS 2 is made up of shaded stream data of Clip 2 (Clip AV stream) and shaded stream data subsequent to RSPN_arrival_time_discontinuity of Bridge-Clip.
  • the shaded stream data of Clip 2 of TS 2 is stream data from the source packet referenced by RSPN_enter_to_current_Clip to the address of the stream required for decoding the presentation unit corresponding to OUT_time of current PlayItem (shown by OUT_time 2 in FIG. 88 ).
  • FIG. 89 shows the relation between the previous PlayItem and the current PlayItem in case of not employing Bridge-Clip.
  • the stream data read out by the player is shown shaded.
  • TS 1 is made up of shaded stream data of the Clip 1 (Clip AV stream).
  • the shaded stream data of Clip 1 of TS 1 is data beginning at an address of a stream necessary in decoding a presentation unit corresponding to IN_time of the previous PlayItem, shown at IN_time 1 in FIG. 89 as far as the last source packet of Clip 1 .
  • TS 2 is shaded stream data of Clip 2 (Clip AV stream).
  • the shaded stream data of Clip 2 of TS 2 is stream data beginning at a first source packet of Clip 2 as far as an address of the stream necessary for decoding the presentation unit corresponding to OUT_time of current PlayItem (shown at OUT_time 2 in FIG. 89 ).
  • TS 1 and T 2 are continuous streams of the source packet.
  • the stream provisions of TS 1 and TS 2 and the connection conditions therebetween are scrutinized.
  • encoding limitations for seamless connection are scrutinized.
  • the number of programs contained in TS 1 and TS 2 must be 1.
  • the number of video streams contained in TS 1 and TS 2 must be 1.
  • the number of audio streams contained in TS and TS 2 must be 2 or less.
  • the numbers of the audio streams contained in TS 1 and TS 2 must be equal to each other. It is also possible for elementary streams or private streams other than those depicted above to be contained in TS 1 and/or TS 2 .
  • FIG. 90 shows a typical seamless connection indicated by a picture display sequence.
  • unneeded pictures displayed at back of OUT_time 1 (OUT_time of Clip 1 ) and ahead of IN_time 2 (IN_time of Clip 2 ) must be removed by a process of re-encoding the partial stream of the Clip in the vicinity of the junction point.
  • FIG. 91 shows an embodiment of realizing seamless connection using BridgeSequence.
  • the video stream of Bridge-Clip previous to RSPN_arrival_time_discontinuity is comprised of an encoded video stream up to a picture corresponding to OUT_time 1 of Clip 1 of FIG. 90 .
  • This video stream is connected to the video stream of previous Clip 1 and is re-encoded to form an elementary stream conforming to the MPEG2 standard.
  • the video stream of Bridge-Clip subsequent to RSPN_arrival_time_discontinuity is made up of an encoded video stream subsequent to a picture corresponding to IN_time 2 of Clip 2 of FIG. 90 .
  • the decoding of this video stream can be started correctly for connecting the video stream to the next following Clip 2 video stream.
  • Re-encoding is made such that a sole continuous elementary stream conforming to MPEG 2 standard will be formed.
  • For creating Bridge-Clip several pictures in general need to be re-encoded, whilst other pictures can be copied from the original Clip.
  • FIG. 92 shows an embodiment of realizing seamless connection without employing BridgeSequence in the embodiment shown in FIG. 90 .
  • the Clip 1 video stream is comprised of an encoded video stream as far as the picture corresponding to OUT_time 1 of FIG. 90 and is re-encoded so as to give an elementary stream conforming to the MPEG2 standard.
  • the video stream of Clip 2 is made up of encoded bitstreams subsequent to the picture associated with IN_time 2 of Clip 2 of FIG. 90 . These encoding bitstreams are already re-encoded to give a sole continuous elementary stream conforming to the MPEG2 standard.
  • the frame rates of the video streams of TS 1 and TS 2 must be equal to each other.
  • the video stream of TS 1 must be terminated at sequence_end_code.
  • the video stream of TS 2 must commence at Sequence header, GOP Header and with an I-picture.
  • the video stream of TS 2 must commence at a closed GOP.
  • the video presentation units defined in a bitstream must be continuous with a junction point in-between. No gap of the fields or frames are allowed to exist at junction points.
  • the audio sampling frequency of TS 1 and that of TS 2 must be equal to each other.
  • the audio encoding method of TS 1 and that of TS 2 (for example, MPEG1 layer 2 , AC3, SESF LPCM and AAC) must be equal to each other.
  • the last audio frame of the audio stream of TS 1 must contain audio samples having a display timing equal to the display end time of the last display picture of TS 1 .
  • the first audio frame of the audio stream of TS 2 must contain an audio sample having a display timing equal to the display start timing of the first display picture of TS 2 .
  • no gap may be allowed to exist in a sequence of the audio presentation units. As shown in FIG. 93 , there may be an overlap defined by the length of the audio presentation unit less than two audio frame domains.
  • the first packet transmitting an elementary stream of TS 2 must be a video packet.
  • the transport stream at the junction point must obey the DVR-STD which will be explained subsequently.
  • the Bridge-Clip AV stream has a sole discontinuous point in the arrival time base only at a junction point of the last source packet of TS 1 and the first source packet of TS 2 .
  • the SPN_arrival_time_discontinuity defined in ClipInfo( ) represents an address of the discontinuous point, which must represent the address referencing the first source packet of TS 2 .
  • the source packet referenced by RSPN_exit_from previous_Clip defined in BridgeSequenceInfo( ) may be any source packet in Clip 1 . It is unnecessary for this source packet to be a boundary of the Aligned unit.
  • the source packet referenced by RSPN_enter_to_current_Clip defined in BridgeSequenceInfo( ) may be any source packet in Clip 2 . It is unnecessary for this source packet to be a boundary of the Aligned unit.
  • the OUT_time of the previous PlayItem (OUT_time 1 shown in FIG. 89 ) must represent the display end time of the last video presentation unit of TS 1 .
  • the IN_time of the current PlayTime (IN_time 2 shown in FIG. 88 and 89 ) must represent the display start time of the first presentation unit of TS 2 .
  • the seamless connection must be made to guarantee continuous data supply by the file system. This must be realized by arranging the Bridge-Clip AV stream, connecting to Clip 1 (Clip AV stream file) and Clip 2 (Clip AV stream file), such as to satisfy data allocation prescriptions.
  • RSPN_exit_from_previous_Clip must be selected so that the stream portion of Clip 1 (Clip AV stream file) previous to RSPN_exit_from_previous_Clip will be arranged in a continuous area not less than half fragment.
  • the data length of the Bridge-Clip AV stream must be selected so that the data will be arranged in the continuous area not less than half fragment.
  • RSPN_enter_to_current_Clip must be selected so that the stream portion of Clip 2 (Clip AV stream file) subsequent to RSPN_enter_to_current_Clip will be arranged in a continuous area not less than half fragment.
  • the seamless connection must be made so as to guarantee continuous data supply by the file system. This must be realized by arranging the last portion of the Clip 1 (Clip AV stream file) and the first portion of the Clip 2 (Clip AV stream file) so that the provisions on data allocation will be met.
  • the last stream portion of Clip 1 (Clip AV stream file) must be arranged in a continuous area not less than one half fragment.
  • the first stream portion of Clip 2 (Clip AV stream file) must be arranged in a continuous area not less than one half fragment.
  • This DVR-STD is a conceptual model for modeling the decoding processing in the generation and verification of the DVR MPEG 2 transport stream.
  • the DVR-STD is also a conceptual model for modeling the decoding processing in the generation and verification of the AV stream referenced by two PlayItems seamlessly connected to each other as described above.
  • FIG. 96 shows a DVR-STD model.
  • the model shown in FIG. 96 includes, as a constituent element, a DVR MPEG 2 transport stream player model.
  • the notation of n, Thn, Mbn, Ebn, Tbsys, Bsys, Rxn, Rbxn, Rxsys, Dn, Dsys, On and P9(k) is the same as that defined in T-STD of ISO/IEC 13818-1, wherein n is an index number of an elementary stream and TBn is a transport buffer of the elementary stream n.
  • MBn is a multiplexing buffer of the elementary stream n and exists only for the video stream.
  • EBn is an elementary stream buffer of the elementary stream n and is present only for the video stream.
  • TBsys is a main buffer in a system target decoder for the system information for a program being decoded.
  • Rxn is a transmission rate with which data is removed from TBn.
  • Rbxn is a transmission rate with which the PES packet payload is removed from MBn and is present only for a video stream.
  • Rxsys is a transmission rate with which data is removed from TBsys.
  • Dn is a decoder of the elementary stream n.
  • Dsys is a decoder pertinent to the system information of a program being decoded.
  • On is a re-ordering buffer of the video stream n.
  • Pn(k) is a number k presentation unit of the elementary stream.
  • the decoding process for DVR-STD is explained. During the time a sole DVR MPEG 2 transport stream is being reproduced, the timing of inputting the transport packet to TB 1 , TBn or TBsys is determined by arrival_time_stamp of the source packet.
  • the prescriptions for the buffering operation of TB 1 , MB 1 , EB 1 , TBn Bn, TBsys and Bsys are the same as those of the T-STD provided for in ISO/IEC 13818-1, while the prescriptions for the deciding and display operations are also the same as the T-STD provided for in ISO/IEC 13818-1.
  • TS 1 and TS 2 are a previous stream and a current stream, respectively.
  • FIG. 97 shows a timing chart for inputting, decoding and display of transport packets when transferring from a given AV stream (TS 1 ) to the next AV stream seamlessly connected thereto (TS 2 ).
  • TS 1 a given AV stream
  • TS 2 a preset AV stream
  • TS 2 the time axis of the arrival time base of TS 2 is not the same as the time axis of the arrival time base of TS 1 (indicated by ATC 1 in FIG. 97 ).
  • time axis of the system time base of TS 2 (indicated by ATC 1 in FIG. 97 ) is not the same as the time axis of the system time base of TS 1 (indicated by STC 1 in FIG. 97 ).
  • the video display is required to be continuous seamlessly, however, there may be overlap in the display tine of the presentation units.
  • the input timing to DVR-STD is explained. During the time until time T 1 , that is until the inputting of the last video packet to the TB 1 of DVR-STD, the input timing to the buffers of TB 1 , TBn or TBsys of DVR-STD is determined by arrival_time_stamp of the arrival time base of TS 1 .
  • the remaining packets of TS 1 must be input to buffers of TBn or to TBsys of DVR-STD at a bitrate of TS_recording_rate (TS 1 ).
  • the TS_recording_rate (TS 1 ) is the value of TS_recording_rate defined in ClipInfo( ) corresponding to Clip 1 .
  • the time the last byte of TS 1 is input to the buffer is the time T 2 . So, during the time between time T 1 and time T 2 , arrival_time_stamp of the source packet is discounted.
  • N1 is the number of bytes of the transport packet of TS 1 next following the last video packet of TS 1
  • both the values of RXn and RXsys are changed to the value of TS-recording_rate (TS 1 ). Except this rule, the buffering operation is the same as that of T-STD.
  • the arrival time clock counter is reset to the value of arrival_time_stamp of the first source packet of TS 2 .
  • the input timing to the buffer of TB 1 , TBn or TBsys of DVR-STD is determined by arrival_time_stamp of the source packet of TB 2 .
  • Both RXn and RXsys are changed to values defined in T-STD.
  • the audio decoder and the system decoder need to have an additional buffering amount (data amount equivalent to one second) in addition to the buffer amount defined in T-STD in order to allow input data of a domain from time T 1 to time T 2 .
  • STC 1 is the time axis of the system time base of TS 1 (indicated as STC 1 in FIG. 9 ), while STC 2 is the time axis of the system time base of TS 2 (shown at STC 2 in FIG. 97 ; correctly, STC 2 begins at time the first PCR of TS 2 has been input to the T-STD).
  • the offset between STC 1 and STC 2 is determined as follows: the PTS 1 end is the PTS on STC 1 corresponding to the last video presentation unit of TS 2 .
  • PTS 2 start is PTS on STC 2 corresponding to the first video presentation unit of TS 2 and Tpp is the display time period of the last video presentation unit of TS 1
  • the audio presentation timing there may be overlap in the display timing of the audio presentation unit, with the overlap being less than 0 to 2 audio frames (see “audio overlap” shown in FIG. 97 ).
  • the indication as to which of audio samples is to be selected and re-synchronization of the display of the audio presentation unit to the corrected time base at back of the junction point are set on the player.
  • the last audio presentation unit of TS 1 is displayed at time T 5 .
  • the system time clock may be overlapped between time T 2 and time T 5 .
  • the DVR-STD switches the system time clocks between the value of the old time base (STC 1 ) and the value of the new time base (STC 2 ).
  • STC 11 video_end is the value of STC on the system time base STC 2 when the first byte of the first video packet reaches TB 1 of DVR-STD.
  • STC 22 video_start is the value of STC on the system time base STC 2 when the first byte of the first video packet reaches TB 1 of DVR-STD.
  • STC 21 video_end is the value of STC 11 video_end calculated as the value on STC 2 of the system time base STC 2 .
  • the inputting of the video packet from TS 1 followed by the inputting of the video packet from TS 2 on the time axis of the system time base, mapped from STC 1 and STC 2 on the same time axis, must not overflow or underflow the video buffer.
  • the contents of data recorded on the recording medium or the reproduction information can be managed properly to enable the user to confirm the contents of data recorded on the recording medium at the time of reproduction or to reproduce desired data extremely readily.
  • the MPEG 2 transport stream is taken as an example of the multiplexed stream.
  • This, however, is merely exemplary, such that the MPEG 2 program stream DSS or the transport stream used in the DirecTV Service (trade mark) of USA may also be used as the multiplexed stream.
  • FIG. 98 shows a modification of a PlayList file.
  • the marked difference between the syntax of FIG. 98 and that of FIG. 99 is the place where UIAppInfoPlayList( ) is stored.
  • the future information expansion of UIAppInfoPlayList( ) may be achieved rather easily.
  • Version_number is four figures indicating the version number of the thumbnail header information file.
  • PlayList_start_address indicates the leading address of PlayList( ) in terms of the number of relative bytes from the leading end of the PlayList file as a unit. The number of relative bytes is counted from 0.
  • PlayListMark_start_address indicates the leading address of PlayListMark( ) in terms of the number of relative bytes from the leading byte of the PlayList file as a unit. The number of relative bytes is counted from 0.
  • MakersPrivateData_start_address denotes the leading address of MakersPrivateData in terms of the number of relative bytes from the leading byte of the PlayList file as a unit. The number of relative bytes is counted from 0.
  • FIG. 99 shows the syntax of UIAppInfoPlayList in the PlayList file of FIG. 98 .
  • PlayList_service_type indicates the type of the PlayList file, an example of which is shown in FIG. 26 .
  • the PlayList_service_type may have the same meaning as that of the service type shown by the digital TV broadcast. For example, in the BS broadcast in Japan, there are three service types, namely the TV service, audio service and data broadcast service. The value representing the service type of the program contained in the Clip AV stream used by the PlayList is set in the PlayList_service_type.
  • PlayList_character_set denotes the encoding method for character letters encoded in channel_name, PlayList_name and PlayList_detail field, while denoting the encoding method for character letters encoded in mark_name field in PlayListMark.
  • Channel_number denotes the broadcast channel number or service number as selected by the user when recording the PlayList. If plural PlayLists are combined into one PlayList, channel_number denotes a representative value of the PlayList. If this field is set to 0 ⁇ FFFF, the field has no meaning.
  • Channel_name_length denotes the byte length of the channel name indicated in the channel_name field. This field has a value not larger than 20.
  • Channel_name denotes the name of the service or the broadcast channel as selected by the user when the PlayList is recorded.
  • the number of bytes of a number indicated by the channel_name_length from left of this field represents effective character letters and denotes the above-mentioned name. The remaining bytes next following these effective character letters may be set to any arbitrary value. If plural PlayLists are combined into one PlayList, this field indicates the name representative of the PlayList.
  • PlayList_name_length denotes the byte length of the PlayList name indicated in the PlayList_name field.
  • Play_list_name shows the name of the PlayList.
  • the number of bytes of the number indicated by the PlayList_name_length from left of this field represents the effective character letters and denote the above-mentioned name.
  • the remaining bytes in this field next following these effective character letters may be set to any optional value.
  • PlayList_detail_length denotes the byte length of the detailed information of the PlayList indicated in the PlayList_detail field. This field has a value not larger than 1200.
  • PlayList_detail denotes the text for illustrating the detailed information of the PlayList.
  • the number of bytes of a number indicated by PlayList_detail_length as from left of this field is the effective character letters.
  • the remaining bytes in this field next following these effective character letters may be set to any optional value.
  • FIG. 100 shows the syntax of PlayList( ) in the PlayList file of FIG. 98 .
  • This syntax is basically the same as the embodiment of FIG. 25 except that the present syntax lacks in the UIAppInfoPlayList( ).
  • FIG. 101 shows a modification of the syntax of SubPlayItem.
  • the present syntax differs appreciably from the embodiment of FIG. 40 in that STC_sequence_id has now been added.
  • STC_sequence_id indicates STC_sequence_id of STC referenced by SubPath_IN_time and SubPath_OUT_time used for identifying the reproduction domain on the AV stream file corresponding to Clip_Information_file_name.
  • SubPath_IN_time and SubPath_OUT_time denote the time on the same STC continuous domain specified by the STC_sequence_id.
  • the syntax field otherwise has the same meaning as that of the field of the same name shown in FIG. 40 .
  • FIG. 102 shows the flowchart for illustrating the method for forming Real PlayList. Reference is had to the block diagram of the recording and/or reproducing apparatus shown in FIG. 1 .
  • step S 11 the controller 43 records a Clip AV stream.
  • step S 12 the controller 23 checks whether or not EP_map of the AV stream can be prepared. If the result of check at step S 12 is YES, the controller 23 proceeds to step S 13 . If otherwise, the controller 23 proceeds to step S 14 to form TU_map.
  • step S 15 the controller 23 then sets the CLI_type of PlayList.
  • the controller 23 forms the PlayList( ) comprised of PlayItem covering the possible reproduction range of the Clip in its entirety. If CPI_type is EP_map type, the time information is set on the PTS basis. If there is STC discontinuous point in the Clip, and the PlayList( ) is made up of two or more PlayItems, the connection_condition between PlayItems is also determined. If CPI_type is TU_map type, the time information is set on the arrival time basis.
  • step S 17 the controller 23 forms UIAppInfoPlayList( ).
  • step S 18 the controller 23 forms PlayListMark.
  • the controller 23 forms MakerPrivateData.
  • step S 20 the controller 23 forms RealPlayList file.
  • FIG. 103 is a flowchart for illustrating the method for forming Virtual PlayList.
  • one real PlayList, recorded on the disc is specified through user interface. From the reproduction range of the Real PlayList, the reproduction range specified by IN and OUT points is specified through the user interface. If CPI_type is EP_map type, the reproduction domain is set on the PTS basis. If CPI_type is TU_type, the reproduction domain is set on the arrival time basis.
  • step S 32 the controller 23 checks whether or not the entire operation of specifying the reproduction range by the user has been finished. If the user selects the domain to be reproduced next to the specified reproduction domain, the controller 23 reverts to step S 31 . If the entire operation of specifying the reproduction range by the user has come to a close, the controller 23 proceeds to step S 33 .
  • connection condition (Connection_condition between two consecutively reproduced reproduction domains is determined by the user through interface or by the controller 23 .
  • step S 34 the user specifies the sub-path information (post-recording audio information). This step is omitted if the sub-path is not formed by the user.
  • step S 35 the controller 23 forms PlayList( ) based on the reproduction range information specified by the user and on the connection_condition.
  • step S 36 the controller 23 forms UIAppInfoPlayList( ).
  • step S 37 the controller 23 forms PlayListMark.
  • step S 38 the controller 23 forms MakerPrivateData.
  • step S 39 the controller 23 forms VirtualPlayList file.
  • one virtual PlayList file is formed for each group of the reproduction domains which are selected from the reproduction range of the Real PlayList recorded on the disc and which the user is desirous to view.
  • FIG. 104 is a flowchart for explaining the reproducing method of the PlayList.
  • the controller 23 acquires the information on the Info.dvr, Clip Information file, PlayList file and thumbnail file and forms a GUI picture demonstrating a list of PlayLists recorded on the disc to display the GUI picture so formed on the GUI through user interface.
  • the controller 23 presents the information explaining the PlayList on the GUI picture based on the UIAppInfoPlayList in the respective PlayLists.
  • step S 53 the user commands reproduction of one PlayList from the GUI picture through user interface.
  • the controller 23 at step S 54 acquires, from the STC_sequence_id and IN_time PTS, the number of the source packet having an entry point temporally previous and closest to IN_time. If the CPI_type is TU_map type, the controller 23 acquires, from the IN_time of the current PlayItem, the number of the source packet where begins the time unit temporally previous and closest to IN_time.
  • step S 55 the controller 23 reads out data of the AV stream from the source packet number acquired at the above step to route the data so read out to the AV decoder 27 .
  • step S 56 If, at step S 56 , there is the PlayItem temporally previous to the current PlayItem, the controller 23 performs the connection processing of display between the previous PlayItem and the current PlayItem in accordance with the connection_condition.
  • the CPI_type is EP_map type
  • the AV decoder 27 commands display to be started as from the picture of the IN_time PTS. If the CPI_type is TU_map type, the AV decoder 27 commands display to be started as from the picture of the stream subsequent to IN_time.
  • step S 58 the controller 23 commands the AV decoder 27 to continue decoding the AV stream.
  • CPI_type is EP_map type
  • the controller 23 at step S 59 checks whether or not the picture currently displayed is the picture of the OUT_time PTS. Also, if the CPI_type is TU_map type, the controller 23 checks whether or not the stream currently decoded is past the OUT_time.
  • step S 59 If the result of check at step S 59 is NO, the controller 23 proceeds to step S 60 .
  • step S 60 the controller 23 displays the current picture to then revert to step S 58 . If the result of check at step S 59 is YES, the controller 23 proceeds to step S 61 .
  • step S 61 the controller 23 checks whether or not the current PlayItem is the last PlayItem in the PlayList. If the result of check is NO, the controller 23 reverts to step S 54 and, if otherwise, the PlayList reproduction is finished.
  • FIG. 105 is a flowchart for illustrating the reproducing method of the SubPath of the PlayList.
  • the subpath reproducing method of FIG. 105 is used only if CPI_type of PlayList is EP_map.
  • the processing of the flowchart is performed simultaneously with the processing subsequent to step S 54 in the reproduction of the PlayList of FIG. 104 . Meanwhile, it is presupposed that the AV decoder 27 is able to decode two audio streams simultaneously.
  • step S 71 the controller 23 acquires the information of SubPlayItem.
  • step S 72 the controller 23 acquires the source packet number having an entry point temporally previous and closest to SubPath_IN_time.
  • step S 73 the controller 23 reads out data of the AV stream of the subpath from the source packet number having the above entry point to route the data so read out to the AV decoder 27 .
  • step S 74 the controller 23 commands the AV decoder 27 to start displaying the subpath audio when the reproduction of the main path reaches the picture specified by the sync_PlayItem_id and sync_start_PTS_of_PlayItem.
  • step S 75 the AV decoder 27 continues decoding the AV stream of the subpath.
  • step S 76 the controller 23 checks whether or not the PTS of the subpath currently displayed is the SubPath_OUT_time. If the result of check is NO, the controller 23 proceeds to step S 77 , where the controller 23 continues displaying the subpath. The controller 23 then reverts to step S 75 .
  • step S 76 the PTS of the subpath currently displayed is SubPath_OUT_time, the display of the subpath is finished.
  • the main path and the subpath of one PlayList file, commanded to be reproduced by the user, are reproduced, as shown in FIGS. 104 and 105 .
  • FIG. 106 shows a flowchart for illustrating the method for forming the PlayListMark. Reference is made to the block diagram of the recording and/or reproducing apparatus of FIG. 1 .
  • the controller 23 acquires the information on the Info.dvr, Clip Information file, PlayList file and thumbnail file and forms a GUI picture demonstrating a list of PlayLists recorded on the disc to display the GUI picture so formed on the GUI through user interface.
  • step S 92 the user commands the controller 23 to reproduce one PlayList through user interface.
  • step S 93 the controller 23 causes reproduction of the specified PlayList as commanded to be started (see FIG. 104 ).
  • step S 94 the user commands the controller 23 to set a mark at a favorite scene through user interface.
  • the controller 23 acquires the mark PTS and the PlayItem_id of the PlayItem to which it belongs. Also, the controller 23 acquires the arrival time of the mark point, if the CPI_type is TU_map.
  • step S 95 the controller 23 stores the mark information in the PlayListMark( ).
  • step S 97 the controller 23 records the PlayList file on the recording medium 100 .
  • FIG. 107 is a flowchart for illustrating the locating reproducing method employing the PlayListMark. Reference is made to the block diagram of the recording and/or reproducing apparatus 1 of FIG. 1 .
  • the controller 23 acquires the information on the Info.dvr, Clip Information file, PlayList file and thumbnail file and forms a GUI picture demonstrating a list of PlayLists recorded on the disc (recording medium 100 ) to display the GUI picture so formed on the GUI through user interface.
  • step S 112 the user commands the controller 23 to reproduce one PlayList through user interface.
  • the controller 23 causes the list of thumbnails, generated from the picture referenced by PlayListMark, to be displayed on the GUI through user interface.
  • the user specifies the mark point of the reproduction start point through the user interface.
  • the controller 23 acquires the mark PTS and the PlayItem_id to which it belongs. If the CPI_type is TU_map type, the controller 23 acquires the ATS (Arrival Time Stamp) of the mark.
  • the controller 23 at step S 116 acquires the STC-sequence_id of the AV stream referenced by PlayItem specified by the PlayItem_id.
  • the controller 23 causes the AV stream to be input to the decoder based on the PTS of the mark and on the STC-sequence_id. Specifically, the controller 23 performs the processing similar to that at step S 55 , using the PTS of the mark and on the STC-sequence_id. If CPI_type is TU_type, the controller 23 causes the AV stream to be input to the decoder, based on the ATS of the mark. Specifically, the controller performs the processing similar to that at step S 54 and step S 55 of FIG. 104 , using the ATS.
  • the controller 23 causes display to be started as from the picture of the PTS of the mark point. If the CPI_type is the TU_map type, the controller 23 causes display to be started as from a picture at back of the ATS of the mark point.
  • the user selects e.g., a start point of a favorite scene from the PlayList.
  • the start point so selected is supervised by the recorder (controller 23 of the recording and/or reproducing apparatus 1 ) in the PlayListMark.
  • the user selects the reproduction start point from the list of the mark points stored in the playListMark so that the player begins reproduction at the start point, as shown in FIG. 107 .
  • the contents of data recorded on the recording medium or the reproduction information can be managed properly to enable the user to confirm the contents of data recorded on the recording medium at the time of reproduction or to reproduce desired data extremely readily.
  • the AV stream of different formats can be recorded, reproduced and managed using a common application program (software), subject to employing TU_map.
  • the EP_map is used, whereas, if the AV stream is directly recorded on the recording medium without analyzing its contents (I-picture position) (non-cognizant recording), the TU_map is used. So, the AV data can be recorded, reproduced and managed using a common application program.
  • the EP_map is used, whereas, if the scrambled AV data is directly recorded on the recording medium without descrambling (without analysis), the TU_map is used.
  • the AV data may be recorded, reproduced and managed using the common application program.
  • the EP_map type and the TU_map type can be described in the PlayList( ) as CPI_type , TU_map may be used if the I-picture position can be analyzed, whereas, if the I-picture position cannot be analyzed, the TU_map may be used.
  • the AV stream data recorded with analysis of the I-picture position and the AV stream data recorded without analysis of the I-picture position can be managed in a unified fashion by a common program simply on setting a corresponding flag.
  • the PlayList file and the Clip Information file are recorded separately, so that, if the contents of a given PlayList or Clip are changed by e.g., editing, it is unnecessary to change a file irrelevant to the changed file.
  • the result is that the file contents can be changed readily to reduce the time needed in such change or recording.
  • the user queuing time may be reduced.
  • the file size becomes bulky. So, the time involved in changing the file contents for recording is appreciably longer than that in case the respective files are recorded separately.
  • the present invention is aimed to overcome this deficiency.
  • sequence of operations may be executed not only by hardware but also by software. If the sequence of operations is to be executed by software, it is installed from a recording medium to a computer in the dedicated hardware of which the program forming the software or a general-purpose personal computer of FIG. 38 capable of executing various functions based on a variety of programs installed therein.
  • the recording medium is constituted not only by a package medium distributed for furnishing the program to the user, in addition to a computer, such as a magnetic disc 221 carrying the program thereon, inclusive of a floppy disc, an optical disc 222 , inclusive of a CD-ROM (Compact Disc-Read-Only memory) or a DVD (Digital Versatile Disc), a magneto-optical disc 223 , inclusive of a Mini-Disc, or a semiconductor memory 224 , but also by a hard disc, inclusive of a ROM 202 carrying a program and a memory 208 , furnished to the user as it is built-in in a computer, as shown in FIG. 108 .
  • a computer such as a magnetic disc 221 carrying the program thereon, inclusive of a floppy disc, an optical disc 222 , inclusive of a CD-ROM (Compact Disc-Read-Only memory) or a DVD (Digital Versatile Disc), a magneto-optical disc 223 , inclusive of
  • the steps of the program furnished by the medium include not only the chronological processing in accordance with the sequence indicated, but also the processing performed not chronologically but in parallel or separately.
  • system means an entire apparatus comprised of plural component devices.
  • program for a recording medium program and the recording medium, according to the present invention, one of a first table stating the relation of correspondence between the presentation time stamp and the address in the AV stream data in the corresponding access unit and a second table stating the relation of correspondence between the arrival time stamp derived from the arrival time point of the transport packet and the address in the AV stream data in the corresponding transport packet is recorded depending on the recording method.
  • the reproduction specifying information comprised of the first information specifying the main reproducing path and the second information specifying the subsidiary reproducing path reproduced in synchronism with the main reproducing path is recorded.
  • the reproduction specifying information comprised of the first information specifying the main reproducing path and the second information specifying the subsidiary reproducing path is reproduced from the recording medium to control the output accordingly.
  • the AV stream capable of high speed reproduction and the AV stream incapable of high speed reproduction can be managed in common, whilst post-recording also becomes possible.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Television Signal Processing For Recording (AREA)
  • Signal Processing For Digital Recording And Reproducing (AREA)
  • Management Or Editing Of Information On Record Carriers (AREA)
  • Indexing, Searching, Synchronizing, And The Amount Of Synchronization Travel Of Record Carriers (AREA)
US10/018,846 2000-04-21 2001-04-20 Information processing apparatus and method, program, and recorded medium Active 2025-03-12 US7738776B2 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US10/925,658 US8670646B2 (en) 2000-04-21 2004-08-23 Information processing method and apparatus, program and recording medium

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
JP2000-183771 2000-04-21
JP2000-183777 2000-04-21
JP2000183771 2000-04-21
JP2000271552 2000-09-07
JP2000-271552 2000-09-07
PCT/JP2001/003415 WO2001082606A1 (fr) 2000-04-21 2001-04-20 Appareil et procede de traitement d'information, programme et support d'enregistrement

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US10/925,658 Continuation US8670646B2 (en) 2000-04-21 2004-08-23 Information processing method and apparatus, program and recording medium

Publications (2)

Publication Number Publication Date
US20020135607A1 US20020135607A1 (en) 2002-09-26
US7738776B2 true US7738776B2 (en) 2010-06-15

Family

ID=26594227

Family Applications (2)

Application Number Title Priority Date Filing Date
US10/018,846 Active 2025-03-12 US7738776B2 (en) 2000-04-21 2001-04-20 Information processing apparatus and method, program, and recorded medium
US10/925,658 Expired - Fee Related US8670646B2 (en) 2000-04-21 2004-08-23 Information processing method and apparatus, program and recording medium

Family Applications After (1)

Application Number Title Priority Date Filing Date
US10/925,658 Expired - Fee Related US8670646B2 (en) 2000-04-21 2004-08-23 Information processing method and apparatus, program and recording medium

Country Status (22)

Country Link
US (2) US7738776B2 (zh)
EP (6) EP1280347A4 (zh)
JP (14) JP4599740B2 (zh)
KR (2) KR100948439B1 (zh)
CN (2) CN100348033C (zh)
AU (1) AU779673B2 (zh)
BR (3) BR0106082A (zh)
CA (1) CA2377690C (zh)
CZ (1) CZ20014489A3 (zh)
DK (1) DK1569449T3 (zh)
ES (1) ES2399331T3 (zh)
HK (1) HK1050975A1 (zh)
HU (1) HU229461B1 (zh)
IL (1) IL147155A (zh)
MX (1) MXPA01013122A (zh)
NO (1) NO20016292L (zh)
PL (1) PL351918A1 (zh)
PT (1) PT1569449E (zh)
RO (1) RO122068B1 (zh)
RU (1) RU2314653C2 (zh)
SK (1) SK18982001A3 (zh)
WO (1) WO2001082606A1 (zh)

Cited By (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030072557A1 (en) * 2001-09-27 2003-04-17 Park Sung-Wook Method of and apparatus for recording video data, and information storage medium thereby
US20060114776A1 (en) * 2002-10-01 2006-06-01 Takeshi Koda Information recording medium, information recording device and method, information reproduction device and method, information recording/reproduction device and method, recording or reproduction control computer program, and data structure containing control signal
US20070192697A1 (en) * 2003-06-11 2007-08-16 Takayoshi Kawamura Information process apparatus and method, record medium, and program
US20070196079A1 (en) * 2002-04-25 2007-08-23 Kim Mi H Method for managing recording and reproduction of multi-dubbed audio stream
US20080259173A1 (en) * 2004-06-10 2008-10-23 Hiroshi Yahata Data Processor
US20090129738A1 (en) * 2006-05-10 2009-05-21 Sony Corporation Information processing apparatus, information processing method, and computer program
US20140143515A1 (en) * 2005-05-26 2014-05-22 Hewlett-Packard Development Company, L.P. Virtual write protection system
US8917976B2 (en) 2011-11-28 2014-12-23 Sony Corporation Information processor, information processing method, and program
US10762929B2 (en) 2011-11-28 2020-09-01 Sony Corporation Display of content list in recording and playback apparatus

Families Citing this family (185)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6808709B1 (en) * 1994-12-30 2004-10-26 The Regents Of The University Of California Immunoglobulins containing protection proteins and their use
IL132859A (en) * 1999-11-10 2008-07-08 Nds Ltd Data stream processing system
WO2001082611A1 (fr) * 2000-04-21 2001-11-01 Sony Corporation Procede et appareil de traitement d'informations, support enregistre, et programme
GB0117926D0 (en) * 2001-07-23 2001-09-12 Nds Ltd Method for random access to encrypted content
JP3656248B2 (ja) 2001-10-09 2005-06-08 ソニー株式会社 ビデオ信号記録装置および方法、ビデオ信号再生装置および方法、記録媒体、プログラム、並びにデータ構造
JP3716920B2 (ja) * 2001-10-16 2005-11-16 ソニー株式会社 記録媒体再生装置および方法、記録媒体、並びにプログラム
GB0127234D0 (en) 2001-11-13 2002-01-02 British Sky Broadcasting Ltd Improvements in receivers for television signals
KR100563668B1 (ko) 2001-12-22 2006-03-28 엘지전자 주식회사 재기록 가능 고밀도 기록매체의 더빙 오디오 기록방법
KR100563667B1 (ko) 2001-12-24 2006-03-28 엘지전자 주식회사 재기록 가능 기록매체에의 정지영상 기록방법
KR20030062737A (ko) * 2002-01-18 2003-07-28 엘지전자 주식회사 재기록 가능 고밀도 기록매체의 축소영상 기록방법
KR100563670B1 (ko) 2002-01-28 2006-03-28 엘지전자 주식회사 재기록 가능 고밀도 기록매체의 정지영상 기록방법
WO2003085972A1 (fr) 2002-04-10 2003-10-16 Sony Corporation Dispositif d'enregistrement de donnees, support de memoire de programme et programme
KR20030087193A (ko) 2002-05-07 2003-11-14 엘지전자 주식회사 멀티 채널 방송 스트림의 기록 관리방법
US8027562B2 (en) * 2002-06-11 2011-09-27 Sanyo Electric Co., Ltd. Method and apparatus for recording images, method and apparatus for recording and reproducing images, and television receiver utilizing the same
JP4299779B2 (ja) 2002-06-21 2009-07-22 エルジー エレクトロニクス インコーポレーテッド ビデオデータの再生を管理するためのデータ構造を有する記録媒体
MXPA04002365A (es) * 2002-06-21 2004-11-22 Lg Electronics Inc Medio de grabacion que tiene estructura de datos para manejar la reproduccion de datos de video grabados en el mismo.
KR20040000290A (ko) * 2002-06-24 2004-01-03 엘지전자 주식회사 고밀도 광디스크의 멀티 경로 데이터 스트림 관리방법
US7889968B2 (en) 2002-06-24 2011-02-15 Lg Electronics Inc. Recording medium having data structure for managing reproduction of multiple reproduction path video data for at least a segment of a title recorded thereon and recording and reproducing methods and apparatuses
CN101350215B (zh) 2002-06-24 2012-08-29 Lg电子株式会社 记录和再现用于视频数据的再现的数据结构的方法及装置
WO2004001751A1 (en) 2002-06-24 2003-12-31 Lg Electronics Inc. Recording medium having data structure including navigation control information for managing reproduction of video data recorded thereon and recording and reproducing methods and apparatuses
CA2459086C (en) * 2002-06-28 2013-08-13 Lg Electronics Inc. Recording medium having data structure for managing recording and reproduction of multiple path data recorded thereon and recording and reproducing methods and apparatus
CN100580787C (zh) * 2002-06-28 2010-01-13 Lg电子株式会社 具有用于管理记录在其上面的多个重放路径视频数据的再现的数据结构的记录介质以及记录和再现方法及装置
BR0306158A (pt) 2002-09-05 2004-10-19 Lg Electronics Inc Meio de gravação tendo estrutura de dados para gerenciar reprodução de imagens fotográficas nele gravadas e métodos e aparelhos de gravação e reprodução
AU2003260975B8 (en) * 2002-09-06 2009-08-13 Lg Electronics Inc. Recording medium having data structure for managing reproduction of still images recorded thereon and recording and reproducing methods and apparatuses
CA2462192C (en) 2002-09-07 2013-07-30 Lg 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 apparatuses
JP3975147B2 (ja) * 2002-10-01 2007-09-12 パイオニア株式会社 情報記録媒体、情報記録装置及び方法、情報再生装置及び方法、情報記録再生装置及び方法、記録又は再生制御用のコンピュータプログラム、並びに制御信号を含むデータ構造
EP1408505A1 (en) 2002-10-11 2004-04-14 Deutsche Thomson-Brandt Gmbh Method and apparatus for synchronizing data streams containing audio, video and/or other data
RU2347284C2 (ru) 2002-10-14 2009-02-20 Эл Джи Электроникс Инк. Носитель записи со структурой данных для управления воспроизведением записанного на нем множества аудиопотоков и способы и устройства записи и воспроизведения
CN100479051C (zh) 2002-10-15 2009-04-15 Lg电子有限公司 具有管理多路图形流重现的数据结构的记录介质及记录和重现方法和装置
AU2003276759A1 (en) 2002-11-08 2004-06-07 Lg Electronics Inc. Method and apparatus for recording a multi-component stream and a high-density recording medium having a multi-component stream recorded theron and reproducing method and apparatus of said recording medium
US7720356B2 (en) 2002-11-12 2010-05-18 Lg Electronics Inc Recording medium having data structure for managing reproduction of multiple reproduction path video data recorded thereon and recording and reproducing methods and apparatuses
US7783160B2 (en) * 2002-11-20 2010-08-24 Lg Electronics Inc. Recording medium having data structure for managing reproduction of interleaved multiple reproduction path video data recorded thereon and recording and reproducing methods and apparatuses
CA2474229C (en) 2002-11-20 2014-11-04 Lg Electronics Inc. Recording medium having data structure for managing reproduction of still images recorded thereon and recording and reproducing methods and apparatuses
CA2474040C (en) * 2002-11-22 2010-02-02 Lg Electronics Inc. Recording medium having data structure for managing reproduction of multiple reproduction path video data recorded thereon and recording and reproducing methods and apparatuses
EP1570482A1 (en) * 2002-12-05 2005-09-07 Koninklijke Philips Electronics N.V. Editing of data frames
JP3815458B2 (ja) 2002-12-18 2006-08-30 ソニー株式会社 情報処理装置、情報処理方法及びプログラム
CN100448285C (zh) * 2002-12-18 2008-12-31 索尼株式会社 信息处理设备和信息处理方法
MY141419A (en) 2003-01-20 2010-04-30 Lg Electronics Inc Recording medium having data structure for managing reproduction of still pictures recorded thereon and recording and reproducing methods and apparatuses
CN100418140C (zh) * 2003-01-20 2008-09-10 Lg电子株式会社 具有用于管理记录在其上的静止图象的再现的数据结构的记录媒体以及记录和再现的方法和装置
WO2004066282A1 (en) * 2003-01-20 2004-08-05 Lg Electronics Inc. Recording medium having data structure for managing reproduction of still pictures recorded thereon and recording and reproducing methods and apparatuses
US8145033B2 (en) 2003-02-05 2012-03-27 Lg Electronics Inc. Recording medium having data structure for managing reproducton duration of still pictures recorded thereon and recording and reproducing methods and apparatuses
US7734154B2 (en) 2003-02-14 2010-06-08 Lg Electronics Inc. Recording medium having data structure for managing reproduction duration of still pictures recorded thereon and recording and reproducing methods and apparatuses
US8055117B2 (en) 2003-02-15 2011-11-08 Lg Electronics Inc. Recording medium having data structure for managing reproduction duration of still pictures recorded thereon and recording and reproducing methods and apparatuses
US7606463B2 (en) * 2003-02-24 2009-10-20 Lg Electronics, Inc. Recording medium having data structure for managing playback control and recording and reproducing methods and apparatuses
US8041179B2 (en) 2003-02-24 2011-10-18 Lg 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 data
US7693394B2 (en) * 2003-02-26 2010-04-06 Lg Electronics Inc. Recording medium having data structure for managing reproduction of data streams recorded thereon and recording and reproducing methods and apparatuses
US7809775B2 (en) * 2003-02-27 2010-10-05 Lg Electronics, Inc. Recording medium having data structure for managing playback control recorded thereon and recording and reproducing methods and apparatuses
EP1604356A4 (en) * 2003-02-28 2009-12-16 Lg Electronics Inc RECORD MEDIUM WITH A DATA STRUCTURE FOR MANAGING THE RANDOM / SHUFFLE PLAYBACK OF RECORDED VIDEO DATA, AND METHOD AND DEVICES FOR RECORDING AND PLAYING
US7620301B2 (en) 2003-04-04 2009-11-17 Lg Electronics Inc. System and method for resuming playback
ATE517413T1 (de) * 2003-04-09 2011-08-15 Lg Electronics Inc Aufzeichnungsmedium mit datenstruktur zur verwaltung der wiedergabe von textuntertiteldaten und verfahren und vorrichtungen zum aufzeichnen und wiedergeben
US7660511B2 (en) * 2003-04-23 2010-02-09 Panasonic Corporation Recording medium, playback device, recording method, playback program, and playback method designating cue-up position using playlist mark information
JP4228767B2 (ja) * 2003-04-25 2009-02-25 ソニー株式会社 再生装置、再生方法、再生プログラムおよび記録媒体
JP4902935B2 (ja) * 2003-05-08 2012-03-21 ソニー株式会社 情報処理装置、情報処理方法、プログラム、及び記録媒体
RU2360301C2 (ru) * 2003-05-27 2009-06-27 Эл Джи Электроникс Инк. Носитель записи со структурой данных для управления основными данными и данными дополнительного содержимого к ним и способы и устройства записи и воспроизведения
JP3931843B2 (ja) 2003-06-13 2007-06-20 株式会社日立製作所 記録媒体および再生方法
KR20050001171A (ko) * 2003-06-27 2005-01-06 엘지전자 주식회사 고밀도 광디스크의 부가 콘텐츠 데이터 관리 및 재생방법
EP1652184A4 (en) 2003-07-24 2007-05-23 Lg Electronics Inc RECORD MEDIA WITH A DATA STRUCTURE FOR MANAGING THE PLAYING OF TEXT SUBTITLE DATA RECORDED THEREFOR AND RECORDING AND PLAYBACK METHOD AND DEVICES
KR20050012328A (ko) 2003-07-25 2005-02-02 엘지전자 주식회사 고밀도 광디스크의 프레젠테이션 그래픽 데이터 관리 및재생방법과 그에 따른 고밀도 광디스크
WO2005018218A2 (en) * 2003-08-12 2005-02-24 Digital Networks North America, Inc. Method and apparatus for navigating content in a personal video recorder
KR100844706B1 (ko) 2003-10-10 2008-07-07 샤프 가부시키가이샤 재생 장치, 비디오 데이터의 재생 방법, 콘텐츠 기록 매체,및 컴퓨터 판독 가능한 기록 매체
JP5090415B2 (ja) * 2003-10-10 2012-12-05 シャープ株式会社 再生装置、ビデオデータの再生方法、制御プログラム、及びコンテンツ記録媒体
KR20050035678A (ko) * 2003-10-14 2005-04-19 엘지전자 주식회사 광디스크 장치의 부가 데이터 재생방법 및 장치와, 이를위한 광디스크
KR20050036277A (ko) * 2003-10-15 2005-04-20 엘지전자 주식회사 고밀도 광디스크의 네비게이션 정보 관리방법
KR20050047710A (ko) * 2003-11-18 2005-05-23 엘지전자 주식회사 고밀도 광디스크의 합성 플레이리스트 생성방법, 관리방법및 재생방법과 기록재생장치
KR20050048848A (ko) * 2003-11-20 2005-05-25 엘지전자 주식회사 고밀도 광디스크의 플레이리스트 생성방법, 관리방법 및재생방법과 기록재생장치
US8472792B2 (en) 2003-12-08 2013-06-25 Divx, Llc Multimedia distribution system
US7519274B2 (en) 2003-12-08 2009-04-14 Divx, Inc. File format for multiple track digital data
EP1542231A1 (en) * 2003-12-08 2005-06-15 Canon Kabushiki Kaisha Recording apparatus and recording method capable of recording series of content data on different recording media
KR101053575B1 (ko) * 2003-12-09 2011-08-03 엘지전자 주식회사 고밀도 광디스크 및 고밀도 광디스크의 파일 구성방법
JP4140518B2 (ja) * 2003-12-15 2008-08-27 ソニー株式会社 情報処理装置および方法、並びにプログラム
KR20050064150A (ko) * 2003-12-23 2005-06-29 엘지전자 주식회사 고밀도 광디스크의 메뉴 구성방법 및 실행방법과기록재생장치
KR20050066265A (ko) * 2003-12-26 2005-06-30 엘지전자 주식회사 고밀도 광디스크의 메뉴 구성방법 및 실행방법과기록재생장치
KR20050066264A (ko) 2003-12-26 2005-06-30 엘지전자 주식회사 고밀도 광디스크의 메뉴 구성방법 및 실행방법과기록재생장치
KR20050072255A (ko) * 2004-01-06 2005-07-11 엘지전자 주식회사 고밀도 광디스크의 서브타이틀 구성방법 및 재생방법과기록재생장치
JP2007518205A (ja) * 2004-01-06 2007-07-05 エルジー エレクトロニクス インコーポレーテッド テキスト・サブタイトル・ストリームの再生・記録のための記録媒体、方法及び装置
KR100937421B1 (ko) * 2004-01-13 2010-01-18 엘지전자 주식회사 고밀도 광디스크의 서브타이틀 관리를 포함한 파일구성방법 및 재생방법과 기록재생장치
KR20050078907A (ko) * 2004-02-03 2005-08-08 엘지전자 주식회사 고밀도 광디스크의 서브타이틀 재생방법과 기록재생장치
US8391672B2 (en) 2004-02-06 2013-03-05 Panasonic Corporation Recording medium, reproduction device, program, and reproduction method
US20080002947A1 (en) * 2004-02-06 2008-01-03 Wataru Ikeda Recording medium, reproduction device, program and reproduction method
BRPI0418524A (pt) * 2004-02-10 2007-05-15 Lg Electronics Inc meio fìsico de gravação, método e aparelho para gravar e reproduzir um estrutura de dados
EP1716701A1 (en) * 2004-02-10 2006-11-02 LG Electronic Inc. Text subtitle decoder and method for decoding text subtitle streams
BRPI0507596A (pt) * 2004-02-10 2007-07-03 Lg Electronics Inc meio fìsico de gravação, método e aparelho para decodificar um fluxo de subtìtulo de texto
WO2005074400A2 (en) 2004-02-10 2005-08-18 Lg Electronics Inc. Recording medium and method and apparatus for decoding text subtitle streams
US20050196146A1 (en) * 2004-02-10 2005-09-08 Yoo Jea Y. Method for reproducing text subtitle and text subtitle decoding system
KR20070028323A (ko) * 2004-02-10 2007-03-12 엘지전자 주식회사 상이한 언어들과 연관된 데이터 스트림을 관리하기 위한데이터 구조를 가지는 기록매체 및 기록재생 방법 및 장치
RU2377669C2 (ru) * 2004-02-10 2009-12-27 ЭлДжи ЭЛЕКТРОНИКС ИНК. Носитель записи, имеющий структуру данных для управления различными данными, и способ и устройство записи и воспроизведения
EP1716566A1 (en) * 2004-02-10 2006-11-02 LG Electronic Inc. Recording medium having a data structure for managing font information for text subtitles and recording and reproducing methods and apparatuses
CN1939060B (zh) * 2004-02-10 2010-09-29 汤姆逊许可公司 一种用于促进视频信息的流式传输的方法和设备
KR101104528B1 (ko) * 2004-02-16 2012-01-11 소니 주식회사 재생 장치, 재생 방법 및 기록 매체
AU2011218752A1 (en) * 2004-02-16 2011-09-22 Sony Corporation Reproduction device, reproduction method, program, recording medium, and data structure
WO2005081643A2 (en) * 2004-02-26 2005-09-09 Lg Electronics Inc. Recording medium and method and apparatus for reproducing and recording text subtitle streams
US8271752B2 (en) 2004-03-12 2012-09-18 Lg Electronics, Inc. Recording medium, method and apparatus for recording on recordable recording medium, and method for managing backup files of the same
KR20060043573A (ko) 2004-03-12 2006-05-15 엘지전자 주식회사 기록매체 및 기록매체에의 기록방법 및 기록장치와 기록매체의 백업 파일 관리방법
DK1728252T3 (da) 2004-03-18 2010-03-22 Lg Electronics Inc Optagemedium samt fremgangsmåde og apparat til at reproducere en undertekststrøm optaget på optagemediet
US7809244B2 (en) * 2004-03-26 2010-10-05 Lg Electronics Inc. Recording medium and method and apparatus for reproducing and recording text subtitle streams with style information
JP4177409B2 (ja) * 2004-04-07 2008-11-05 松下電器産業株式会社 情報記録装置及び情報記録方法
CN100518283C (zh) * 2004-04-07 2009-07-22 松下电器产业株式会社 记录可以高速转换的流的信息记录装置和记录方法
WO2005099259A1 (ja) * 2004-04-07 2005-10-20 Matsushita Electric Industrial Co., Ltd. 高速変換可能なストリームを記録した情報記録媒体並びにその記録装置及び記録方法
EP1737225B1 (en) * 2004-04-07 2011-11-09 Panasonic Corporation Information recording medium wherein stream convertible at high-speed is recorded, and recording apparatus and recording method therefor
JP4105207B2 (ja) * 2004-04-07 2008-06-25 松下電器産業株式会社 高速変換可能なストリームを記録した情報記録媒体並びにその記録装置及び記録方法
CN101815212B (zh) * 2004-04-16 2013-01-02 松下电器产业株式会社 重放装置以及记录方法
KR101129142B1 (ko) * 2004-04-16 2012-03-26 파나소닉 주식회사 재생장치, 기록매체, 재생시스템
JP4186871B2 (ja) * 2004-05-21 2008-11-26 船井電機株式会社 記録再生装置
EP1858014B1 (en) 2004-06-02 2009-11-18 Panasonic Corporation Recording medium, reproduction device, program, and reproduction method
JP4658986B2 (ja) * 2004-06-02 2011-03-23 パナソニック株式会社 システムｌｓｉ
JP4764855B2 (ja) * 2004-06-02 2011-09-07 パナソニック株式会社 記録方法、再生システム
JP4608953B2 (ja) * 2004-06-07 2011-01-12 ソニー株式会社 データ記録装置、方法およびプログラム、データ再生装置、方法およびプログラム、ならびに、記録媒体
KR100667756B1 (ko) * 2004-07-01 2007-01-11 삼성전자주식회사 방송 스트림 저장/검색 방법 및 장치
PL2357814T3 (pl) * 2004-08-17 2012-10-31 Panasonic Corp Urządzenie i sposób kodowania obrazu
US7725010B2 (en) * 2004-08-17 2010-05-25 Lg Electronics, Inc. Method and apparatus of reproducing data recorded on recording medium and local storage
US7609939B2 (en) * 2004-08-17 2009-10-27 Lg Electronics Inc. Method and apparatus of reproducing data recorded on recording medium and local storage
US7613384B2 (en) * 2004-08-17 2009-11-03 Lg Electronics Inc. Method for configuring composite file structure for data reproduction, and method and apparatus for reproducing data using the composite file structure
US7609945B2 (en) * 2004-08-17 2009-10-27 Lg Electronics Inc. Recording medium, and method and apparatus for reproducing data from the recording medium
JP2006066943A (ja) 2004-08-24 2006-03-09 Sony Corp 情報処理装置および方法、並びにプログラム
WO2006025606A1 (ja) * 2004-09-02 2006-03-09 Nec Corporation データ放送記録方法、装置、および記録媒体
US7609947B2 (en) * 2004-09-10 2009-10-27 Panasonic Corporation Method and apparatus for coordinating playback from multiple video sources
US20060056804A1 (en) * 2004-09-13 2006-03-16 Seo Kang S Recording medium, and method and apparatus for reproducing data from the recording medium
US7599611B2 (en) * 2004-09-13 2009-10-06 Lg Electronics Co. Recording medium, and method and apparatus of reproducing data recorded on the same
US8842977B2 (en) 2005-01-07 2014-09-23 Samsung Electronics Co., Ltd. Storage medium storing metadata for providing enhanced search function
KR100782810B1 (ko) 2005-01-07 2007-12-06 삼성전자주식회사 확장 검색 기능을 제공하기 위한 메타데이터가 기록된 저장매체를 재생하는 방법 및 장치
WO2006080194A1 (ja) 2005-01-26 2006-08-03 Sharp Kabushiki Kaisha 情報記録再生装置及び情報記録媒体
JP4968506B2 (ja) 2005-03-04 2012-07-04 ソニー株式会社 再生装置、再生方法、およびプログラム
EP1879191A4 (en) * 2005-03-22 2013-08-14 Panasonic Corp STREAM DATA RECORDING DEVICE, STREAM DATA RECORDING / REPLAYING DEVICE, STREAM DATA REPRODUCING DEVICE, STREAM DATA EDITING DEVICE, STREAM RECORDING METHOD AND STREAM REPLAYING METHOD
CN101996664B (zh) * 2005-07-27 2012-11-28 松下电器产业株式会社 信息记录装置以及信息记录方法
WO2007049189A2 (en) * 2005-10-24 2007-05-03 Koninklijke Philips Electronics N.V. Method and apparatus for editing an optical disc
CN101305425B (zh) 2005-11-07 2012-06-27 皇家飞利浦电子股份有限公司 光盘节目编辑方法及装置
EP1999883A4 (en) 2006-03-14 2013-03-06 Divx Llc FEDERATED DIGITAL RIGHTS MANAGEMENT SYSTEM COMPRISING CONFIDENCE SYSTEMS
US8125987B2 (en) * 2006-03-30 2012-02-28 Broadcom Corporation System and method for demultiplexing different stream types in a programmable transport demultiplexer
JP4719053B2 (ja) * 2006-03-31 2011-07-06 株式会社東芝 エントリポイントを用いた再生方法およびこの方法を用いる記録再生装置
JP4765733B2 (ja) 2006-04-06 2011-09-07 ソニー株式会社 記録装置、記録方法および記録プログラム
JP4162691B2 (ja) * 2006-09-27 2008-10-08 株式会社東芝 番組構造化装置、番組構造化方法およびプログラム
KR101318081B1 (ko) 2006-11-21 2013-10-14 엘지디스플레이 주식회사 액정표시장치와 그 구동방법
JP4735525B2 (ja) 2006-12-06 2011-07-27 株式会社日立製作所 記録方法
JP4735524B2 (ja) 2006-12-06 2011-07-27 株式会社日立製作所 記録方法
JP4775241B2 (ja) 2006-12-06 2011-09-21 株式会社日立製作所 記録方法
JP2008152871A (ja) * 2006-12-19 2008-07-03 Victor Co Of Japan Ltd 情報記録再生装置及び再生装置
EP4213033A1 (en) 2007-01-05 2023-07-19 DivX, LLC Video distribution system including progressive playback
JP2008204560A (ja) * 2007-02-21 2008-09-04 D & M Holdings Inc 再生装置、再生方法、プログラム及び記録媒体
JP4852453B2 (ja) 2007-03-19 2012-01-11 株式会社日立製作所 記録装置、映像再生装置、および、その特殊再生方法
JP5034608B2 (ja) 2007-03-30 2012-09-26 株式会社日立製作所 記録方法
CN101437150B (zh) * 2007-11-16 2011-11-09 华为技术有限公司 提供关联信息的装置及方法
KR20100106327A (ko) 2007-11-16 2010-10-01 디브이엑스, 인크. 멀티미디어 파일을 위한 계층적 및 감소된 인덱스 구조
JP4924447B2 (ja) * 2008-01-25 2012-04-25 ソニー株式会社 シーン切り替わり点検出器、シーン切り替わり点検出方法、記録装置、イベント生成器、イベント生成方法および再生装置
JP5031608B2 (ja) * 2008-02-01 2012-09-19 キヤノン株式会社 再生装置及び記憶媒体
JP4506879B2 (ja) * 2008-06-09 2010-07-21 ソニー株式会社 記録装置、記録方法、プログラム及び記録システム
CA2755896A1 (en) * 2009-03-23 2010-09-30 Medicis Technologies Corporation Analysis of real time backscatter data for fault signal generation in a medical hifu device
EP2507995A4 (en) 2009-12-04 2014-07-09 Sonic Ip Inc SYSTEMS AND METHODS FOR TRANSPORTING ELEMENTARY BIT TRAIN CRYPTOGRAPHIC MATERIAL
JP5494152B2 (ja) 2010-04-08 2014-05-14 ソニー株式会社 情報処理装置、情報記録媒体、および情報処理方法、並びにプログラム
JP5601006B2 (ja) 2010-04-08 2014-10-08 ソニー株式会社 情報処理装置、情報記録媒体、および情報処理方法、並びにプログラム
JP2011223247A (ja) 2010-04-08 2011-11-04 Sony Corp 情報処理装置、情報記録媒体、および情報処理方法、並びにプログラム
JP5577805B2 (ja) 2010-04-08 2014-08-27 ソニー株式会社 情報処理装置、情報記録媒体、および情報処理方法、並びにプログラム
JP2011223248A (ja) 2010-04-08 2011-11-04 Sony Corp 情報処理装置、情報記録媒体、および情報処理方法、並びにプログラム
JP2010225266A (ja) * 2010-04-23 2010-10-07 Toshiba Corp エントリポイントを用いた再生方法およびこの方法を用いる記録再生装置
JP5110135B2 (ja) * 2010-08-30 2012-12-26 ソニー株式会社 記録媒体
US8914534B2 (en) 2011-01-05 2014-12-16 Sonic Ip, Inc. Systems and methods for adaptive bitrate streaming of media stored in matroska container files using hypertext transfer protocol
JP2011175729A (ja) * 2011-04-08 2011-09-08 Hitachi Ltd 記録媒体および再生方法
US8812662B2 (en) 2011-06-29 2014-08-19 Sonic Ip, Inc. Systems and methods for estimating available bandwidth and performing initial stream selection when streaming content
CN102915316A (zh) * 2011-08-05 2013-02-06 宏碁股份有限公司 电子系统与多媒体播放方法
US9467708B2 (en) 2011-08-30 2016-10-11 Sonic Ip, Inc. Selection of resolutions for seamless resolution switching of multimedia content
KR101928910B1 (ko) 2011-08-30 2018-12-14 쏘닉 아이피, 아이엔씨. 복수의 최대 비트레이트 레벨들을 사용하여 인코딩된 비디오를 인코딩하고 스트리밍하기 위한 시스템들 및 방법들
US8787570B2 (en) 2011-08-31 2014-07-22 Sonic Ip, Inc. Systems and methods for automatically genenrating top level index files
US8799647B2 (en) 2011-08-31 2014-08-05 Sonic Ip, Inc. Systems and methods for application identification
US8909922B2 (en) 2011-09-01 2014-12-09 Sonic Ip, Inc. Systems and methods for playing back alternative streams of protected content protected using common cryptographic information
US8964977B2 (en) 2011-09-01 2015-02-24 Sonic Ip, Inc. Systems and methods for saving encoded media streamed using adaptive bitrate streaming
JP6010900B2 (ja) 2011-11-29 2016-10-19 ソニー株式会社 情報処理装置、情報処理方法、並びにプログラム
US8918908B2 (en) 2012-01-06 2014-12-23 Sonic Ip, Inc. Systems and methods for accessing digital content using electronic tickets and ticket tokens
US9936267B2 (en) 2012-08-31 2018-04-03 Divx Cf Holdings Llc System and method for decreasing an initial buffering period of an adaptive streaming system
US9191457B2 (en) 2012-12-31 2015-11-17 Sonic Ip, Inc. Systems, methods, and media for controlling delivery of content
US9313510B2 (en) 2012-12-31 2016-04-12 Sonic Ip, Inc. Use of objective quality measures of streamed content to reduce streaming bandwidth
US9906785B2 (en) 2013-03-15 2018-02-27 Sonic Ip, Inc. Systems, methods, and media for transcoding video data according to encoding parameters indicated by received metadata
US10397292B2 (en) 2013-03-15 2019-08-27 Divx, Llc Systems, methods, and media for delivery of content
US9094737B2 (en) 2013-05-30 2015-07-28 Sonic Ip, Inc. Network video streaming with trick play based on separate trick play files
US9100687B2 (en) 2013-05-31 2015-08-04 Sonic Ip, Inc. Playback synchronization across playback devices
US9380099B2 (en) 2013-05-31 2016-06-28 Sonic Ip, Inc. Synchronizing multiple over the top streaming clients
US9386067B2 (en) 2013-12-30 2016-07-05 Sonic Ip, Inc. Systems and methods for playing adaptive bitrate streaming content by multicast
US9866878B2 (en) 2014-04-05 2018-01-09 Sonic Ip, Inc. Systems and methods for encoding and playing back video at different frame rates using enhancement layers
KR102548789B1 (ko) 2014-08-07 2023-06-29 디빅스, 엘엘씨 독립적으로 인코딩된 타일을 포함한 기본 비트스트림을 보호하는 시스템 및 방법
KR102012682B1 (ko) 2015-01-06 2019-08-22 디브이엑스, 엘엘씨 디바이스들간에 콘텐트를 인코딩 및 공유하기 위한 시스템들 및 방법들
CN107251008B (zh) 2015-02-27 2020-11-13 帝威视有限公司 在实况视频编码和流传输中进行帧复制和帧扩展的系统和方法
US10075292B2 (en) 2016-03-30 2018-09-11 Divx, Llc Systems and methods for quick start-up of playback
US10231001B2 (en) 2016-05-24 2019-03-12 Divx, Llc Systems and methods for providing audio content during trick-play playback
US10129574B2 (en) 2016-05-24 2018-11-13 Divx, Llc Systems and methods for providing variable speeds in a trick-play mode
US10148989B2 (en) 2016-06-15 2018-12-04 Divx, Llc Systems and methods for encoding video content
US10498795B2 (en) 2017-02-17 2019-12-03 Divx, Llc Systems and methods for adaptive switching between multiple content delivery networks during adaptive bitrate streaming
US11825142B2 (en) 2019-03-21 2023-11-21 Divx, Llc Systems and methods for multimedia swarms

Citations (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH10145735A (ja) 1996-11-05 1998-05-29 Toshiba Corp 復号装置および画像／音声再生方法
JPH10271454A (ja) 1997-03-20 1998-10-09 Sony Corp データ再生装置及びデータ再生方法
EP0876063A2 (en) 1997-04-30 1998-11-04 Sony Corporation Signal reproducing apparatus and methods
US5838876A (en) 1996-09-24 1998-11-17 Sony Corporation Frame-accurate edit and playback in digital stream recording
EP0910087A2 (en) 1997-10-17 1999-04-21 Sony Corporation Recording apparatus and method, reproducing apparatus and method, recording/reproducing apparatus and method, recording medium and distribution medium
JPH11149717A (ja) 1997-11-19 1999-06-02 Toshiba Corp デコード処理方法及び装置
EP0929072A2 (en) 1997-12-12 1999-07-14 Kabushiki Kaisha Toshiba Digital recording system using variable recording rate
JPH11259992A (ja) 1998-03-10 1999-09-24 Toshiba Corp 情報記録媒体と情報記録装置と情報編集装置とディジタル放送記録装置
US6002834A (en) 1995-02-24 1999-12-14 Hitachi, Ltd. Optical disk having table relating sector address and time and optical disk reproducing apparatus
EP0971535A2 (en) 1998-07-07 2000-01-12 Kabushiki Kaisha Toshiba Storage system capable of recording and playing back a plurality of still pictures
EP0986062A1 (en) 1998-09-07 2000-03-15 Deutsche Thomson-Brandt Gmbh Method for addressing a bit stream recording
EP0991072A1 (en) 1998-09-07 2000-04-05 Deutsche Thomson-Brandt Gmbh Method for addressing a bit stream recording
US6445877B1 (en) * 1998-11-19 2002-09-03 Matsushita Electric Industrial Co., Ltd. Information recording medium, apparatus and method for recording or reproducing data thereof
US7076153B2 (en) 1999-01-14 2006-07-11 Kabushiki Kaisha Toshiba Digital video recording system and its recording medium

Family Cites Families (19)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2807456B2 (ja) 1995-02-03 1998-10-08 株式会社東芝 画像情報記録媒体およびその製造方法
JP4095681B2 (ja) * 1995-02-24 2008-06-04 株式会社日立製作所 データ記録方法及び装置及びデータ記録再生装置
JP3309656B2 (ja) 1995-08-18 2002-07-29 ソニー株式会社 画像処理装置及び画像処理方法
JPH09238303A (ja) 1996-02-29 1997-09-09 Ricoh Co Ltd デジタルスチルビデオカメラ
US5938876A (en) * 1997-01-31 1999-08-17 Morrison International, Inc. Method of making eyeglass lenses with add on segments
WO1999014757A2 (en) * 1997-09-17 1999-03-25 Matsushita Electric Industrial Co., Ltd. Video data editing apparatus, optical disc for use as a recording medium of a video data editing apparatus, and computer-readable recording medium storing an editing program
JP3324480B2 (ja) * 1997-12-05 2002-09-17 松下電器産業株式会社 記録再生装置及び再生装置
WO1999048094A2 (en) * 1998-03-19 1999-09-23 Koninklijke Philips Electronics N.V. Recording/reproduction and/or editing of real time information on/from a disc like record carrier
TW439054B (en) * 1998-04-08 2001-06-07 Matsushita Electric Ind Co Ltd Optical disc, optical disc recording method and apparatus, and optical disc reproducing method and apparatus
JPH11298845A (ja) * 1998-04-08 1999-10-29 Matsushita Electric Ind Co Ltd 光ディスク、光ディスクレコーダおよび光ディスクプレーヤ
JP3997367B2 (ja) 1998-04-30 2007-10-24 ソニー株式会社 記録再生装置および方法、並びに記録媒体
JP3356991B2 (ja) * 1998-06-17 2002-12-16 株式会社日立製作所 光ディスク、記録方法、記録装置、再生方法及び再生装置
GB9813831D0 (en) 1998-06-27 1998-08-26 Philips Electronics Nv Frame-accurate editing of encoded A/V sequences
JP3677176B2 (ja) 1998-07-07 2005-07-27 株式会社東芝 オブジェクト分割及び消去禁止フラグ処理用情報記録方法及び媒体及び再生装置
WO2000018117A1 (fr) * 1998-09-08 2000-03-30 Sharp Kabushiki Kaisha Procede d'edition d'images a variation temporelle et dispositif d'edition d'images a variation temporelle
EP1084494B1 (en) * 1999-03-01 2008-08-13 Koninklijke Philips Electronics N.V. A method of storing a real time stream of information signals on a disc like record carrier
JP2001076473A (ja) * 1999-09-07 2001-03-23 Fujitsu Ltd 記録再生装置
JP4389365B2 (ja) * 1999-09-29 2009-12-24 ソニー株式会社 トランスポートストリーム記録装置および方法、トランスポートストリーム再生装置および方法、並びにプログラム記録媒体
JP4328989B2 (ja) * 1999-11-24 2009-09-09 ソニー株式会社 再生装置、再生方法、並びに記録媒体

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6002834A (en) 1995-02-24 1999-12-14 Hitachi, Ltd. Optical disk having table relating sector address and time and optical disk reproducing apparatus
US5838876A (en) 1996-09-24 1998-11-17 Sony Corporation Frame-accurate edit and playback in digital stream recording
JPH10145735A (ja) 1996-11-05 1998-05-29 Toshiba Corp 復号装置および画像／音声再生方法
JPH10271454A (ja) 1997-03-20 1998-10-09 Sony Corp データ再生装置及びデータ再生方法
JPH10304309A (ja) 1997-04-30 1998-11-13 Sony Corp 信号再生装置及び方法
EP0876063A2 (en) 1997-04-30 1998-11-04 Sony Corporation Signal reproducing apparatus and methods
EP0910087A2 (en) 1997-10-17 1999-04-21 Sony Corporation Recording apparatus and method, reproducing apparatus and method, recording/reproducing apparatus and method, recording medium and distribution medium
JPH11149717A (ja) 1997-11-19 1999-06-02 Toshiba Corp デコード処理方法及び装置
EP0929072A2 (en) 1997-12-12 1999-07-14 Kabushiki Kaisha Toshiba Digital recording system using variable recording rate
JPH11259992A (ja) 1998-03-10 1999-09-24 Toshiba Corp 情報記録媒体と情報記録装置と情報編集装置とディジタル放送記録装置
EP0971535A2 (en) 1998-07-07 2000-01-12 Kabushiki Kaisha Toshiba Storage system capable of recording and playing back a plurality of still pictures
EP0986062A1 (en) 1998-09-07 2000-03-15 Deutsche Thomson-Brandt Gmbh Method for addressing a bit stream recording
EP0991072A1 (en) 1998-09-07 2000-04-05 Deutsche Thomson-Brandt Gmbh Method for addressing a bit stream recording
US6445877B1 (en) * 1998-11-19 2002-09-03 Matsushita Electric Industrial Co., Ltd. Information recording medium, apparatus and method for recording or reproducing data thereof
US7076153B2 (en) 1999-01-14 2006-07-11 Kabushiki Kaisha Toshiba Digital video recording system and its recording medium

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20030072557A1 (en) * 2001-09-27 2003-04-17 Park Sung-Wook Method of and apparatus for recording video data, and information storage medium thereby
US7903951B2 (en) * 2001-09-27 2011-03-08 Samsung Electronics Co., Ltd. Method of and apparatus for recording video data, and information storage medium thereby
US20070196079A1 (en) * 2002-04-25 2007-08-23 Kim Mi H Method for managing recording and reproduction of multi-dubbed audio stream
US20070206927A1 (en) * 2002-04-25 2007-09-06 Kim Mi H Method for managing recording and reproduction of multi-dubbed audio stream
US20060114776A1 (en) * 2002-10-01 2006-06-01 Takeshi Koda Information recording medium, information recording device and method, information reproduction device and method, information recording/reproduction device and method, recording or reproduction control computer program, and data structure containing control signal
US7970255B2 (en) * 2002-10-01 2011-06-28 Pioneer Corporation Information recording medium, information recording device and method, information reproduction device and method, information recording/reproduction device and method, recording or reproduction control computer program, and data structure containing control signal
US20070192697A1 (en) * 2003-06-11 2007-08-16 Takayoshi Kawamura Information process apparatus and method, record medium, and program
US20080259173A1 (en) * 2004-06-10 2008-10-23 Hiroshi Yahata Data Processor
US8306383B2 (en) * 2004-06-10 2012-11-06 Panasonic Corporation Data processor and hierarchy for recording moving and still picture files
US20140143515A1 (en) * 2005-05-26 2014-05-22 Hewlett-Packard Development Company, L.P. Virtual write protection system
US8997251B2 (en) * 2005-05-26 2015-03-31 Hewlett-Packard Development Company, L.P. Virtual write protection system
US20090129738A1 (en) * 2006-05-10 2009-05-21 Sony Corporation Information processing apparatus, information processing method, and computer program
US8155502B2 (en) * 2006-05-10 2012-04-10 Sony Corporation Information processing apparatus, information processing method, and computer program
US8917976B2 (en) 2011-11-28 2014-12-23 Sony Corporation Information processor, information processing method, and program
US10762929B2 (en) 2011-11-28 2020-09-01 Sony Corporation Display of content list in recording and playback apparatus

Also Published As

Publication number Publication date
JP2011004413A (ja) 2011-01-06
JP2012065359A (ja) 2012-03-29
JP2012065363A (ja) 2012-03-29
KR100875782B1 (ko) 2008-12-24
IL147155A (en) 2008-07-08
JP5051803B2 (ja) 2012-10-17
EP2256738A3 (en) 2012-01-18
IL147155A0 (en) 2002-08-14
JP5063808B2 (ja) 2012-10-31
US8670646B2 (en) 2014-03-11
BRPI0117209B1 (pt) 2019-01-15
RU2314653C2 (ru) 2008-01-10
RU2005117968A (ru) 2006-12-20
CA2377690C (en) 2013-09-10
HU229461B1 (hu) 2013-12-30
JP2011166803A (ja) 2011-08-25
NO20016292D0 (no) 2001-12-20
JP5051807B2 (ja) 2012-10-17
JP4999972B2 (ja) 2012-08-15
JP2012130005A (ja) 2012-07-05
CN100394791C (zh) 2008-06-11
EP2256738A2 (en) 2010-12-01
JP5051802B2 (ja) 2012-10-17
JP2012130019A (ja) 2012-07-05
EP1569449A2 (en) 2005-08-31
CA2377690A1 (en) 2001-11-01
EP2256737A3 (en) 2012-01-11
EP2256737A2 (en) 2010-12-01
SK18982001A3 (sk) 2003-01-09
PT1569449E (pt) 2013-01-24
JP4947159B2 (ja) 2012-06-06
RO122068B1 (ro) 2008-11-28
EP2256736A3 (en) 2012-01-11
JP4599740B2 (ja) 2010-12-15
PL351918A1 (en) 2003-06-30
AU779673B2 (en) 2005-02-03
JP4919129B2 (ja) 2012-04-18
JP2011166800A (ja) 2011-08-25
US20020135607A1 (en) 2002-09-26
HUP0202198A2 (en) 2002-10-28
EP1280347A4 (en) 2004-10-06
CN1607825A (zh) 2005-04-20
KR20080091525A (ko) 2008-10-13
EP1280347A1 (en) 2003-01-29
WO2001082606A1 (fr) 2001-11-01
EP2256739A2 (en) 2010-12-01
JP2011166802A (ja) 2011-08-25
JP4919130B2 (ja) 2012-04-18
JP4919127B2 (ja) 2012-04-18
MXPA01013122A (es) 2002-06-04
CN100348033C (zh) 2007-11-07
BRPI0106082B1 (pt) 2019-01-15
EP1569449A3 (en) 2005-11-09
EP2256736A2 (en) 2010-12-01
AU5440301A (en) 2001-11-07
JP5051805B2 (ja) 2012-10-17
JP2011166801A (ja) 2011-08-25
ES2399331T3 (es) 2013-03-27
JP2012130006A (ja) 2012-07-05
JP4915484B2 (ja) 2012-04-11
JP2002158972A (ja) 2002-05-31
HK1050975A1 (en) 2003-07-11
NO20016292L (no) 2002-02-20
JP2011135616A (ja) 2011-07-07
JP2012065361A (ja) 2012-03-29
US20050025461A1 (en) 2005-02-03
JP5051804B2 (ja) 2012-10-17
JP2010148140A (ja) 2010-07-01
KR100948439B1 (ko) 2010-03-17
JP4919128B2 (ja) 2012-04-18
DK1569449T3 (da) 2013-01-02
EP2256739A3 (en) 2012-01-18
BR0106082A (pt) 2002-05-21
KR20020020918A (ko) 2002-03-16
CN1381137A (zh) 2002-11-20
CZ20014489A3 (cs) 2002-10-16
EP1569449B1 (en) 2012-11-21

Similar Documents

Publication Publication Date Title
US7738776B2 (en) Information processing apparatus and method, program, and recorded medium
US7941033B2 (en) Information processing method and apparatus, program and recording medium
US8355619B2 (en) Information processing apparatus and method, recorded medium, and program
US7236687B2 (en) Information processing apparatus and method, program, and recording medium
US7646967B2 (en) Information processing apparatus and method, program and recorded medium
JP4517267B2 (ja) 記録装置および方法、再生装置および方法、プログラム、並びに記録媒体
JP4355988B2 (ja) 情報処理装置、情報処理方法、プログラム記録媒体、プログラム、および情報記録媒体
ZA200110323B (en) Information processing apparatus and method, program, and recorded medium.

Legal Events

Date Code Title Description
AS Assignment

Owner name: SONY CORPORATION, JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KATO, MOTOKI;HAMADA, TOSHIYA;REEL/FRAME:012808/0741

Effective date: 20011213

Owner name: SONY CORPORATION,JAPAN

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:KATO, MOTOKI;HAMADA, TOSHIYA;REEL/FRAME:012808/0741

Effective date: 20011213

FEPP Fee payment procedure

Free format text: PAYOR NUMBER ASSIGNED (ORIGINAL EVENT CODE: ASPN); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 8TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1552)

Year of fee payment: 8

MAFP Maintenance fee payment

Free format text: PAYMENT OF MAINTENANCE FEE, 12TH YEAR, LARGE ENTITY (ORIGINAL EVENT CODE: M1553); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

Year of fee payment: 12