JP2002158965A - Information processor and its method, recording medium, program and recording medium - Google Patents

Abstract

PROBLEM TO BE SOLVED: To quickly and surely perform access to a desired position of an AV stream. SOLUTION: The start point of a program and a picture in which the title of the program is displayed are respectively described in mark entry() and representative picture entry() in a clip constituting an AV stream.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

The present invention relates to an information processing apparatus and method, a recording medium, a program, and a recording medium.
In particular, an information processing apparatus and method capable of quickly accessing a desired position of an AV stream,
The present invention relates to a recording medium, a program, and a recording medium.

[0002]

2. Description of the Related Art In recent years, various types of optical disks have been proposed as disk-type media that can be recorded and removed from a recording / reproducing apparatus. Such recordable optical discs
It has been proposed as a large-capacity medium of several gigabytes,
There is high expectation as a medium for recording AV (Audio Visual) signals such as video signals.

As a source (supply source) of a digital AV signal to be recorded on the recordable optical disk, the recording apparatus itself converts an analog input audio video signal into an MPEG signal.
There are bitstreams created by compressing images in the -2 format, and bitstreams in the MPEG2 format directly obtained from digital television broadcast radio waves. Generally, in digital television broadcasting, an MPEG2 transport stream is used. The transport stream is a stream in which transport packets are continuous. The transport packets include, for example, an MPEG2 video stream and an MPEG2 video stream.
One audio stream is packetized. The data length of one transport packet is 188
Bytes. If the AV program of the transport stream received in the digital television broadcast is recorded as it is on the optical disk by the recording device, it is possible to record without deteriorating the quality of the video or audio at all.

[0004]

In order to enable a user to search a transport stream recorded on an optical disc for a scene of interest, for example, a cue point of a program, a reproducing apparatus is used. It must be able to play.

[0005] Generally, an MPEG2 video stream is
I pictures are encoded at intervals of about 0.5 seconds, and other pictures are encoded as P pictures or B pictures. Therefore, when performing random access and video reproduction from an optical disc on which an MPEG2 video stream is recorded, an I picture must first be searched.

However, conventionally, it has been difficult to efficiently search for the start byte of an I picture when performing random access to a transport stream recorded on an optical disc and video reproduction. That is, from the random byte position of the transport stream on the optical disk, the syntax of the read video stream must be analyzed and the start byte of the I picture must be searched.
It has been difficult to perform random access reproduction with a fast response to an input from a user.

The present invention has been made in view of such circumstances, and in response to a user's instruction for random access reproduction, determination of a read position of a transport stream from a recording medium and prompt start of decoding of the stream are performed. It is possible to do it.

[0008]

According to a first information processing apparatus of the present invention, a ClipMark composed of a mark indicating a characteristic image extracted from an input AV stream is converted into an A mark.
It is generated as management information for managing the V stream, and includes a mark indicating an image arbitrarily designated by the user from a playback section corresponding to a PlayList that defines a combination of predetermined sections in the AV stream. It is characterized by having a generating means for generating a PlayListMark, and a recording means for recording a ClipMark and a PlayListMark as independent tables on a recording medium.

[0009] The generating means converts the ClipMark into a ClipMarkInfo.
Generate a rmation file and create a PlayList
It can be generated as a layList file.

[0010] The PlayListMark may further include a mark indicating a Resume point when the PlayList is reproduced.

[0011] When reproducing the PlayList, a mark constituting a ClipMark of an AV stream corresponding to a reproduction section of the PlayList can be referred to.

[0012] The mark of the PlayListMark may include a presentation time stamp and identification information indicating one designated playback section on AV stream data constituting a playback path of the PlayList.

A mark constituting the ClipMark, or
The mark constituting the PlayListMark can include information for specifying an entry point of the elementary stream.

The mark of the PlayListMark is the starting point of the favorite scene specified by the user or the Re
Information of a type including at least the sume point can be included.

[0015] The mark constituting the ClipMark and the PlayList
The mark constituting the Mark can be represented by a relative source packet address corresponding to the entry point of the AV stream.

The mark constituting the ClipMark and the PlayList
The mark constituting the Mark is represented by a first address of the source packet relative to the entry point of the AV stream and a second address which is an address offset from the first address. Can be.

The image processing apparatus further includes type detection means for detecting a characteristic image type detected at the time of recording by the first recording means, wherein the first recording means comprises a mark constituting ClipMark, and a type detection means. And can be recorded in correspondence with the type detected.

The ClipMark mark may include a scene change point, a commercial start point, a commercial end point, or a scene in which a title is displayed.

According to the first information processing method of the present invention, a ClipMark composed of marks indicating characteristic images extracted from an input AV stream is generated as management information for managing the AV stream. , PlayLi which defines a combination of predetermined sections in the AV stream
a generation step of generating a PlayListMark composed of a mark indicating an image arbitrarily specified by the user from the reproduction section corresponding to st, ClipMark, and PlayListMa
and a recording control step of performing control when recording rk as an independent table on a recording medium.

[0020] The program of the first recording medium of the present invention comprises:
A PlayList that generates a ClipMark composed of marks indicating characteristic images extracted from the input AV stream as management information for managing the AV stream, and defines a combination of predetermined sections in the AV stream. From the playback section corresponding to, and a mark indicating an image arbitrarily designated by the user.
A generation step for generating a ListMark, a ClipMark, and
A recording control step of performing control when recording the PlayListMark as an independent table on a recording medium.

[0021] The first program of the present invention generates a ClipMark composed of marks indicating characteristic images extracted from an input AV stream as management information for managing the AV stream, and generates an AV stream. PlayList that defines a combination of predetermined sections in the stream
A PlayListMark consisting of a mark indicating an image arbitrarily designated by the user from the playback sections corresponding to the PlayListMark, a ClipMark, and a PlayListMark.
And a recording control step of performing control when recording on a recording medium as independent tables.

[0022] The second information processing apparatus of the present invention comprises management information for managing an AV stream including a ClipMark composed of marks indicating characteristic images extracted from the AV stream, and a predetermined information in the AV stream. Reading means for reading out a PlayListMark composed of marks indicating images arbitrarily designated by the user, from the playback sections corresponding to the PlayList defining the combination of sections, and management information and PlayLisMark read by the reading means.
And a reference unit that refers to the ClipMark corresponding to the PlayList that the user has instructed to reproduce from the information presented by the presentation unit, and a ClipMark that is referred to by the reference unit. Playback means for playing back the AV stream from the position.

The presenting means can present a list of thumbnail images corresponding to PlayLisMark to the user.

The mark constituting the ClipMark and the PlayList
The mark constituting the Mark can be represented by a relative source packet address corresponding to the entry point of the AV stream.

The mark constituting the ClipMark and the PlayList
The mark constituting the Mark is represented by a first address of the source packet relative to the entry point of the AV stream and a second address which is an address offset from the first address. Can be.

The ClipMark mark may include a scene change point, a commercial start point, a commercial end point, or a scene in which a title is displayed.

[0027] A second information processing apparatus according to the present invention comprises: management information for managing an AV stream including a ClipMark composed of marks indicating characteristic images extracted from the AV stream; A read control step for controlling reading of a PlayListMark composed of marks indicating images arbitrarily designated by the user from among the reproduction sections corresponding to the PlayList defining the combination of sections, and reading is performed by the processing of the reading control step. A presentation step of presenting the controlled management information and the information by PlayLisMark; a reference step of referring to the ClipMark corresponding to the PlayList to which the user has instructed the reproduction from the information presented in the processing of the presentation step; A playback control that includes the referenced ClipMark and controls playback of the AV stream from a position corresponding to the ClipMark. Characterized in that a control step.

The program of the second recording medium of the present invention comprises:
Management information for managing an AV stream including a ClipMark composed of marks indicating characteristic images extracted from the AV stream, and a playback section corresponding to a PlayList that defines a combination of predetermined sections in the AV stream. A read control step for controlling reading of a PlayListMark composed of a mark indicating an image arbitrarily designated by the user, and a presentation step for presenting management information and information on PlayLisMark whose reading is controlled in the processing of the read control step. And a reference step of referring to the ClipMark corresponding to the PlayList to which the user has instructed the reproduction from the information presented in the processing of the presentation step, and a ClipMark referred to in the processing of the reference step, from the position corresponding to the ClipMark. And a playback control step of controlling playback of the AV stream.

The program according to the present invention includes a combination of management information for managing an AV stream including a ClipMark composed of marks indicating characteristic images extracted from the AV stream, and a predetermined section in the AV stream. Consists of marks that indicate images arbitrarily specified by the user from the playback section corresponding to the PlayList to be defined.
A read control step of controlling the reading of PlayListMark, a presentation step of presenting the management information controlled by the read control step and the information by PlayLisMark, and a reproduction by the user from the information presented in the processing of the presentation step. ClipMa corresponding to the specified PlayList
The computer causes the computer to execute a reference step of referring to rk, and a reproduction control step of controlling reproduction of an AV stream including a ClipMark referred to in the processing of the reference step and starting from a position corresponding to the ClipMark.

[0030] The third recording medium of the present invention includes management information for managing an AV stream including a ClipMark composed of marks indicating characteristic images extracted from the AV stream, and predetermined information in the AV stream. From the playback sections corresponding to the PlayList that defines the combination of sections,
A PlayListMark composed of marks indicating images arbitrarily designated by the user is recorded as independent tables.

A first information processing apparatus and method according to the present invention,
In the program, a ClipMark composed of marks indicating characteristic images extracted from the input AV stream is generated as management information for managing the AV stream, and a ClipMark of a predetermined section in the AV stream is generated. A PlayListMark consisting of a mark indicating an image arbitrarily designated by the user is generated from a playback section corresponding to a PlayList defining a combination, and a Clip is generated.
Mark and PlayListMark are recorded on the recording medium as independent tables.

A second information processing apparatus and method according to the present invention,
And a program that defines a combination of management information for managing an AV stream including a ClipMark including a mark indicating a characteristic image extracted from the AV stream, and a predetermined section in the AV stream.
A PlayListMark consisting of a mark indicating an image arbitrarily designated by the user is read from the playback section corresponding to st, and the read management information and PlayLisMark are read.
Is presented, and from the presented information, a ClipMark corresponding to the PlayList to which the user has instructed to reproduce is referenced, and the AV stream is reproduced from the position including the referenced ClipMark and corresponding to the ClipMark.

[0033]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a diagram showing an example of the internal configuration of a recording / reproducing device 1 to which the present invention has been applied. First, the configuration of the recording unit 2 that performs an operation of recording an externally input signal on a recording medium will be described. The recording / reproducing apparatus 1 is configured to be able to input and record analog data or digital data.

The terminal 11 receives an analog video signal,
An analog audio signal is input to the terminal 12. The video signal input to the terminal 11 is output to the analysis unit 14 and the AV encoder 15, respectively. The audio signal input to the terminal 12 is sent to the
Output to the encoder 15. The analysis unit 14 extracts a feature point such as a scene change from the input video signal and audio signal.

The AV encoder 15 encodes the input video signal and audio signal, respectively, and multiplexes the encoded video stream (V), the encoded audio stream (A), and system information (S) such as AV synchronization. 16
Output to

The encoded video stream is, for example, MPEG
(Moving Picture Expert Group) A video stream encoded by the 2 system, and the encoded audio stream is, for example, an audio stream encoded by the MPEG1 system or an audio stream encoded by the Dolby AC3 system (trademark). And so on. The multiplexer 16 multiplexes the input video and audio streams based on the input system information,
The data is output to the multiplexed stream analyzer 18 and the source packetizer 19 via the switch 17.

The multiplexed stream is, for example, an MPEG2 transport stream or an MPEG2 program stream. The source packetizer 19 converts the input multiplexed stream into a recording medium 10 for recording the stream.
In accordance with an application format of 0, encoding is performed into an AV stream composed of source packets. The AV stream includes an ECC (error correction) encoder 20 and a modulator 2
The ECC code addition and modulation processing are performed in 1 and the writing unit 2
2 is output. The writing unit 22 writes (records) the AV stream file on the recording medium 100 based on the control signal output from the control unit 23.

A transport stream such as a digital television broadcast input from a digital interface or a digital television tuner is input to a terminal 13. There are two types of recording methods for the transport stream input to the terminal 13, a method for recording transparently and a method for recording after re-encoding for the purpose of lowering the recording bit rate. . The instruction information of the recording method is input to the control unit 23 from a terminal 24 as a user interface.

When the input transport stream is recorded transparently, the transport stream input to the terminal 13 is output to the multiplexed stream analyzer 18 and the source packetizer 19 via the switch 17. Subsequent processing until the AV stream is recorded on the recording medium 100 is the same processing as when the analog input audio signal and the video signal are encoded and recorded, and the description thereof is omitted.

When recording after re-encoding the input transport stream, the transport stream input to the terminal 13 is input to the demultiplexer 26. The demultiplexer 26 performs demultiplex processing on the input transport stream, and performs a video stream (V), an audio stream (A),
And system information (S) is extracted.

Of the streams (information) extracted by the demultiplexer 26, the video stream is output to the AV decoder 27, and the audio stream and system information are output to the multiplexer 16. AV decoder 2
7 decodes the input video stream and outputs the reproduced video signal to the AV encoder 15. The AV encoder 15 encodes the input video signal and outputs an encoded video stream (V) to the multiplexer 16.

On the other hand, the audio stream and system information output from the demultiplexer 26 and input to the multiplexer 16 and the video stream output from the AV encoder 15 are multiplexed and multiplexed based on the input system information. The multiplexed stream is output to the multiplexed stream analyzer 18 and the source packetizer 19 via the switch 17. Subsequent recording medium 10
The processing up to the recording of the AV stream to 0 is the same as the processing of encoding and recording the analog input audio signal and video signal described above, and a description thereof will be omitted.

The recording / reproducing apparatus 1 of the present embodiment records an AV stream file on the recording medium 100,
Also record application database information describing the file. The application database information is created by the control unit 23. The input information to the control unit 23 is the characteristic information of the moving image from the analysis unit 14, the characteristic information of the AV stream from the multiplexed stream analysis unit 18, and the instruction information from the user input from the terminal 24.

The characteristic information of the moving image supplied from the analysis unit 14 is generated by the analysis unit 14 when the AV encoder 15 encodes a video signal. The analysis unit 14 analyzes the contents of the input video signal and the audio signal, and generates information related to a characteristic image (clip mark) in the input moving image signal. This is, for example,
It is the instruction information of the image of the program start point, scene change point, start / end point of commercials, and characteristic clip mark points such as titles and telops in the input video signal. Also includes thumbnails. Further, information such as a switching point of the audio signal between stereo and monaural and a silent section is also included.

The instruction information of these images is input to the multiplexer 16 via the control unit 23. When multiplexing the coded picture specified as the clip mark from the control unit 23, the multiplexer 16 returns information for specifying the coded picture on the AV stream to the control unit 23. Specifically, this information is the PT of the picture.
S (presentation time stamp) or address information of the encoded picture on the AV stream. The control unit 23 stores the characteristic image type and information for specifying the encoded picture in the AV stream in association with each other.

The characteristic information of the AV stream from the multiplexed stream analyzer 18 is information related to the encoded information of the AV stream to be recorded, and is generated by the analyzer 18. For example, it includes the time stamp and address information of the I picture in the AV stream, discontinuous point information of the system time clock, coding parameters of the AV stream, and change point information of the coding parameters in the AV stream. When the transport stream input from the terminal 13 is recorded transparently, the multiplexed stream analyzer 18 detects the image of the above-mentioned clip mark from the input transport stream, and determines the type and the clip mark. Generates information for specifying a picture to be specified.

The user's instruction information from the terminal 24 includes, in the AV stream, designation information of a reproduction section specified by the user, character characters for explaining the contents of the reproduction section,
Information such as a bookmark and a resume point set by the user in a favorite scene.

The control unit 23 groups the AV stream database (Clip) and the AV stream playback section (PlayItem) based on the input information (PlayLimit).
st), the management information (info.dvr) of the recorded content of the recording medium 100, and the information of the thumbnail image are created. The application database information composed of these pieces of information is processed by the ECC encoding unit 20 and the modulation unit 21 and input to the writing unit 22 in the same manner as the AV stream. The writing unit 22 records a database file on the recording medium 100 based on a control signal output from the control unit 23.

The details of the application database information will be described later.

When the AV stream file (image data and audio data file) and the application database information thus recorded on the recording medium 100 are reproduced by the reproducing unit 3, first, the control unit 23 28 to read application database information from the recording medium 100. Then, the reading unit 28 reads the application database information from the recording medium 100, and the application database information is read by the demodulation unit 29 and the ECC decoding unit 30.
After being demodulated and error-corrected, it is input to the control unit 23.

The control unit 23 is recorded on the recording medium 100 based on the application database information.
The list of PlayList is output to the user interface of the terminal 24. The user wants to play Pl from the PlayList list.
The ayList is selected, and information on the PlayList designated to be reproduced is input to the control unit 23. The control unit 23 transmits the Play
The reading unit 28 is instructed to read an AV stream file necessary for reproducing the List. The reading unit 28 reads the corresponding AV stream from the recording medium 100 and outputs the read AV stream to the demodulation unit 29 according to the instruction. The AV stream input to the demodulation unit 29 is demodulated by performing predetermined processing, and is further output to the source depacketizer 31 through the processing of the ECC decoding unit 30.

The source depacketizer 31 stores the recording medium 1
The demultiplexer 26 converts the application format AV stream read from 00 and subjected to predetermined processing into a stream that can be processed by the demultiplexer 26. The demultiplexer 26 is a video stream constituting a playback section (PlayItem) of the AV stream specified by the control unit 23.
(V), an audio stream (A), and system information (S) such as AV synchronization are output to the AV decoder 27. The AV decoder 27 decodes the video stream and the audio stream, and outputs a reproduced video signal and a reproduced audio signal from the corresponding terminals 32 and 33, respectively.

When information for instructing random access reproduction or special reproduction is input from a terminal 24 serving as a user interface, the control unit 23 transmits the information to the storage medium 100 based on the contents of the AV stream database (Clip).
, And instructs the reading unit 28 to read the AV stream. For example, when playing the PlayList selected by the user from a predetermined time, the control unit 23 instructs the reading unit 28 to read data from an I picture having a time stamp closest to the specified time.

Also, when the user selects a certain clip mark from the start point and scene change point of the program stored in the ClipMark in the Clip Information (for example, this operation is performed when the clip mark is stored in the ClipMark). The thumbnail image list of the start point or the scene change point of the program being displayed is displayed on the user interface, and the user selects a certain image from the list, and the control unit 23 performs processing based on the contents of the Clip Information. Then, the reading position of the AV stream from the recording medium 100 is determined, and the reading of the AV stream is instructed to the reading unit 28. That is, the read unit 28 is instructed to read data from the I picture at the address closest to the address on the AV stream in which the image selected by the user is stored. The reading unit 28 reads data from the designated address, and the read data is input to the demultiplexer 26 through the processing of the demodulation unit 29, the ECC decoding unit 30, and the source depacketizer 31, and is input to the AV decoder 27. And the AV data indicated by the address of the picture at the mark point is reproduced.

In addition, the user performs high-speed playback (Fast-forw
When “ard playback” is instructed, the control unit 23 instructs the reading unit 28 to sequentially and sequentially read the I-picture data in the AV stream based on the database (Clip) of the AV stream.

The reading unit 28 reads the data of the AV stream from the designated random access point,
The read data is reproduced through the processing of each unit at the subsequent stage.

Next, a case where the user edits an AV stream recorded on the recording medium 100 will be described. When the user wants to create a new playback path by designating the playback section of the AV stream recorded on the recording medium 100, for example, the part of the singer A is reproduced from the song program A, and then the program B is continued. When the user wants to create a reproduction path such as reproducing the part of the singer A of the song program, the information of the start point (in point) and the end point (out point) of the reproduction section is transmitted from the terminal 24 as a user interface to the control unit 2.
3 is input. The control unit 23 creates a database of a group (PlayList) of playback sections (PlayItems) of the AV stream.

When the user wants to erase a part of the AV stream recorded on the recording medium 100, information on the IN point and the OUT point of the erase section is input to the control unit 23 from the terminal 24 as a user interface. The control unit 23
PlayList to refer only to the necessary AV stream part
To change the database. In addition, the writing unit 22 deletes unnecessary stream portions of the AV stream.
To instruct.

A case where the user wants to create a new playback path by designating a playback section of an AV stream recorded on the recording medium 100 and wants to seamlessly connect the playback sections will be described. In such a case, the control unit 23 sets the playback section (PlayI
tem) are grouped (PlayList), and a video stream near the connection point of the playback section is partially re-encoded and re-multiplexed.

First, the information of the picture at the IN point and the information of the picture at the OUT point in the playback section are transmitted from the terminal 24 to the control unit 2.
3 is input. The control unit 23 instructs the reading unit 28 to read out data necessary for reproducing the in-point side picture and the out-point side picture. Then, the reading unit 28 reads data from the recording medium 100, and outputs the data to the demultiplexer 26 via the demodulation unit 29, the ECC decoding unit 30, and the source depacketizer 31.

The control unit 23 analyzes the data input to the demultiplexer 26, and determines a video stream re-encoding method (change of picture_coding_type, allocation of a coded bit amount to be re-encoded) and a re-multiplexing method. Then, the system is supplied to the AV encoder 15 and the multiplexer 16.

Next, the demultiplexer 26 separates the input stream into a video stream (V), an audio stream (A), and system information (S). The video stream includes data input to the AV decoder 27 and data input to the multiplexer 16. The former data is necessary for re-encoding,
This is decoded by the AV decoder 27, and the decoded picture is re-encoded by the AV encoder 15 to be a video stream. The latter data is data copied from the original stream without re-encoding. Audio streams and system information are directly input to the multiplexer 16.

The multiplexer 16 multiplexes the input stream based on the information input from the control unit 23,
Output multiplexed stream. The multiplexed stream is EC
The signals are processed by the C encoding unit 20 and the modulation unit 21 and input to the writing unit 22. The writing unit 22 records an AV stream on the recording medium 100 based on a control signal supplied from the control unit 23.

Hereinafter, application database information and operations such as reproduction and editing based on the information will be described. FIG. 2 is a diagram illustrating the structure of the application format. The application format has two layers, PlayList and Clip, for AV stream management. Volume Information manages all Clips and PlayLists in the disc. here,
A pair of one AV stream and its attached information is considered as one object, and is called a Clip. An AV stream file is referred to as a Clip AV stream file, and its accompanying information is referred to as a Clip Information file.

One Clip AV stream file stores data in which an MPEG2 transport stream is arranged in a structure defined by an application format. Generally, a file is treated as a byte sequence, but the contents of a Clip AV stream file are developed on a time axis, and an entry point (I picture) in the Clip is specified mainly on a time basis. When a time stamp of an access point to a predetermined Clip is given, Cl
The ip Information file is useful for finding address information to start reading data from the Clip AV stream file.

The PlayList will be described with reference to FIG. The PlayList is provided in order to allow the user to select a playback section desired to be viewed from the Clip and easily edit it. One PlayList is a group of playback sections in a Clip. One playback section in a predetermined Clip is called a PlayItem, which is represented by a pair of an IN point (IN) and an OUT point (OUT) on the time axis. Therefore, P
The layList is configured by collecting a plurality of PlayItems.

There are two types of PlayList. One is Real PlayList and the other is Virtual PlayL
ist. Real PlayList is the Clip it refers to
Share the stream part. That is, Real Pla
yList occupies the data capacity in the disc corresponding to the stream portion of the Clip referred to by the
When the ist is deleted, the data of the stream portion of the Clip referred to by the ist is also deleted.

The Virtual PlayList does not share Clip data. Therefore, even if the Virtual PlayList is changed or deleted, there is no change in the contents of the Clip.

Next, editing of the Real PlayList will be described. FIG. 4A shows the creation (crea) of Real PlayList.
te: creation), where the AV stream is a new Cli
If recorded as p, Real refers to the entire Clip
This is an operation in which a PlayList is newly created.

FIG. 4B is a diagram relating to the division of the Real PlayList, and is an operation in which the Real PlayList is divided at desired points and divided into two Real PlayLists. This division operation is performed, for example, when two programs are managed in one clip managed by one PlayList.
This is performed when the user wants to register (record) as one program again. This operation does not change the contents of the Clip (the Clip itself is divided).

FIG. 4C is a diagram relating to a combine of Real PlayLists.
This is an operation for combining Lists into one new Real PlayList. The operation of this combination is performed when the user
This is performed when one program is to be re-registered as one program. This operation does not change the Clip (the Clip itself is changed to one).

FIG. 5A is a diagram relating to the deletion (delete) of the entire Real PlayList.
If an operation to delete the entire yList is performed, the deleted Rea
l The corresponding stream portion of the Clip referenced by the PlayList is also deleted.

FIG. 5B is a diagram relating to the partial deletion of the Real PlayList. When a desired portion of the Real PlayList is deleted, the corresponding PlayItem refers to only the necessary Clip stream portion. Is changed to Then, the corresponding stream portion of the Clip is deleted.

FIG. 5C is a diagram relating to the minimization (Minimize) of Real PlayList.
The PlayItem corresponding to the t
This operation refers to only the stream part of p. The corresponding stream portion of the Clip unnecessary for the Virtual PlayList is deleted.

By the operation as described above, Real PlayLis
If the t is changed and the stream portion of the Clip referred to by the Real PlayList is deleted, there is a Virtual PlayList using the deleted Clip, and
In PlayList, there is a possibility that a problem may occur due to the deleted Clip.

In order to prevent such a case from occurring, the user instructs the user to delete the “Virt referencing the stream portion of the Clip referenced by the Real PlayList”.
ual PlayList exists, and if the Real PlayList is deleted, the Virtual PlayList will also be deleted. Is that ok? Is displayed, thereby prompting confirmation (warning), and then executing or canceling the deletion process according to the user's instruction. Alternatively, instead of deleting the Virtual PlayList, a minimizing operation is performed on the Real PlayList.

Next, the operation for the Virtual PlayList will be described. Even if an operation is performed on the Virtual PlayList, the contents of the Clip are not changed. FIG.
Is a diagram related to assemble editing (IN-OUT editing).
This is an operation to create an Item and a Virtual PlayList. Seamless connection between PlayItems is supported by the application format (described later).

As shown in FIG. 6A, two Real Ps
layList1, 2 and C corresponding to each RealPlayList
If lip1 and lip2 exist, the user
A predetermined section in st1 (section from In1 to Out1: PlayI
tem1) as a playback section, and as a section to be continuously played back, a predetermined section (In2 to Out) in Real PlayList2.
2 (PlayItem 2) is designated as a playback section, and as shown in FIG.
One Virtual PlayList composed of two is created.

Next, the virtual play list is re-edited (Re-edi
ting) will be described. For reediting, Virtual PlayLis
Change in and out points in t, insert (insert) and add (append) new PlayItems to Virtual PlayList, Virt
For example, there is a deletion of PlayItem in the ual PlayList. Also,
The Virtual PlayList itself can be deleted.

FIG. 7 is a diagram regarding audio dubbing (Audio dubbing (post recording)) to the Virtual PlayList, and refers to an operation of registering audio dubbing to the Virtual PlayList as a sub path. This audio dubbing is supported by the application format. An additional audio stream is added as a sub-path to the main stream AV stream of the Virtual PlayList.

As a common operation between the Real PlayList and the Virtual PlayList, there is a change (Moving) in the playback order of the PlayList as shown in FIG. This operation is a change in the playback order of the PlayList in the disk (volume), and the Table Of P
layList (described later with reference to FIG. 20 and the like). This operation does not change the contents of the Clip.

Next, the mark (Mark) will be described.
The mark is, as shown in FIG. 9, Clip and PlayList.
It is provided to specify the highlight and the characteristic time in. The mark added to the Clip is called ClipMark (clip mark). The ClipMark specifies a characteristic scene caused by the contents of the AV stream, such as a program start point or a scene change point. ClipMark
Is generated by, for example, the analysis unit 14 in FIG. Play
When the List is reproduced, it can be used by referring to the mark of the Clip referred to by the PlayList.

The mark added to the PlayList is a PlayList
It is called Mark (playlist mark). PlayListMark
Are mainly set by the user, such as a bookmark and a resume point. Clip or PlayList
Is set by adding a time stamp indicating the time of the mark to the mark list. Deleting a mark means removing the time stamp of the mark from the mark list. Therefore, the AV stream is not changed at all by setting or deleting the mark.

As another format of ClipMark, Clip
The picture referenced by Mark may be specified on an address basis in the AV stream. The setting of the mark in the Clip is performed by adding address-based information indicating the picture at the mark point to the mark list. Deleting a mark means removing address-based information indicating a picture at the mark point from the mark list. Therefore, the AV stream is not changed at all by setting or deleting the mark.

Next, the thumbnail will be described. The thumbnail is a still image added to Volume, PlayList, and Clip. There are two types of thumbnails, and one is a thumbnail as a representative image representing the content. This is mainly used on a menu screen for allowing a user to operate a cursor (not shown) or the like to select a desired item. The other is an image representing the scene indicated by the mark.

It is necessary that the Volume and each Playlist can have a representative picture. When a disk (recording medium 100; hereinafter, recording medium 100 is disk-shaped and is appropriately described as a disk) is set at a predetermined location of recording / reproducing apparatus 1, a representative image of the Volume is It is assumed that it is used when a still image representing the content is displayed first. The representative image of Playlist is
It is assumed that the menu screen for selecting a Playlist is used as a still image for representing the contents of the Playlist.

As a representative image of the playlist, it is conceivable that the first image of the playlist is a thumbnail (representative image), but the image at the beginning of the reproduction time 0 is not always the most suitable image in representing the contents. Therefore, the user can set an arbitrary image as a thumbnail of the playlist. The thumbnail as a representative picture representing Volume and Pl
The two types of thumbnails as representative images representing the ayList are called menu thumbnails. Since menu thumbnails are displayed frequently, they need to be read from the disk at high speed. Therefore, it is efficient to store all menu thumbnails in one file. The menu thumbnail need not necessarily be a picture extracted from a moving image in the volume, but may be an image captured from a personal computer or a digital still camera as shown in FIG.

On the other hand, it is necessary to put a plurality of marks on the Clip and the Playlist, and it is necessary to easily see the image of the mark point in order to know the contents of the mark position. A picture representing such a mark point is called a mark thumbnail (Mark Thumbnails). Therefore, the image serving as the basis of the mark thumbnail is mainly an image obtained by extracting the image at the mark point, rather than an image fetched from outside.

FIG. 11 is a diagram showing the relationship between the mark attached to the PlayList and the mark thumbnail, and FIG. 12 is a diagram showing the relationship between the mark attached to the Clip and the mark thumbnail. The mark thumbnail, unlike the menu thumbnail, is used in a submenu or the like when representing the details of the playlist, so that it is not required to be read out in a short access time. Therefore, each time a thumbnail is required, the recording / reproducing device 1
It doesn't matter if it takes some time to open the file and read part of it.

In order to reduce the number of files existing in the volume, it is preferable to store all the mark thumbnails in one file. A Playlist can have one menu thumbnail and a plurality of mark thumbnails, but there is no need to provide a menu thumbnail because the Clip does not need to be directly selected by the user (usually specified via the Playlist).

FIG. 13 is a diagram showing the relationship among menu thumbnails, mark thumbnails, PlayLists, and Clips in consideration of the above. In the menu thumbnail file, menu thumbnails provided for each PlayList are filed. The menu thumbnail file includes a volume thumbnail representing the content of data recorded on the disc. In the mark thumbnail file, thumbnails created for each PlayList and each Clip are stored.

Next, CPI (Characteristic Point Inform)
ation) will be described. The CPI is data contained in the Clip information file.
When the time stamp of the access point to the ip is given, it is used to find a data address to start reading data in the Clip AV stream file.
In the present embodiment, two types of CPI are used. One is EP_
map, and the other is TU_map.

EP_map is a list of entry point (EP) data, which is extracted from the elementary stream and the transport stream. It has address information for finding the location of the entry point where decoding should start in the AV stream. One piece of EP data includes a pair of a presentation time stamp (PTS) and a data address in an AV stream of an access unit corresponding to the PTS.

The EP_map is mainly used for two purposes. First, it is used to find the data address in the AV stream of the access unit referenced by the presentation time stamp in the PlayList. Second, it is used for fast forward reproduction and first reverse reproduction. The recording / reproducing device 1
When recording the input AV stream, when the syntax of the stream can be analyzed, an EP_map is created and recorded on the disc.

[0095] The TU_map has a list of time unit (TU) data based on the arrival time of the transport packet input through the digital interface. This gives a relation between the time based on the arrival time and the data address in the AV stream. The recording / reproducing apparatus 1 receives the input AV
When recording a stream, when the syntax of the stream cannot be analyzed, a TU_map is created,
Recorded on the disc.

[0096] STCInfo is an STCInfo in an AV stream file storing an MPEG2 transport stream.
Store the discontinuity information of C. If the AV stream is S
When there is a discontinuity point of TC, there is a possibility that a PTS of the same value appears in the AV stream file. Therefore, AV
When a predetermined time on a stream is indicated on a PTS basis, the PTS of the access point alone is not enough to specify that point.

Further, an index of a continuous STC section including the PTS is required. In this format, a continuous STC section is called an STC-sequence, and its index is described as an STC-sequence-id. STC-sequence information is defined by STCInfo of the Clip Information file. The STC-sequence-id is used for an AV stream file having an EP_map, and is optional for an AV stream file having a TU_map.

A program is a collection of elementary streams, and shares a single system time base for synchronous reproduction of these streams. It is useful for the playback device to know the contents of the AV stream before decoding the AV stream. For example, it is information such as a PID value of a transport packet for transmitting a video or audio elementary stream, or a component type of a video or audio (eg, an HDTV video and an MPEG-2 AAC audio stream).

This information is useful for creating a menu screen for explaining to the user the contents of the PlayList, which refers to the AV stream, and, prior to decoding the AV stream, Useful for setting the initial state of the demultiplexer.
For this reason, the Clip Information file has ProgramInfo for describing the contents of the program.

An AV stream file storing an MPEG2 transport stream may have its contents changed in the file. For example, the PID of a transport packet that transmits a video elementary stream changes, or the component type of a video stream changes from SDTV to HDTV.

[0101] ProgramInfo stores information on a change point of the program content in the AV stream file. AV
In the stream file, the section where the program content defined by this format is constant
Call it a quence. Program-sequence is used for AV stream files with EP_map and has TU_map
Optional for AV stream files.

In the present embodiment, a self-encoding stream format (SESF) is defined. SESF is used for encoding an analog input signal and for decoding a digital input signal (for example, DV) and then encoding it into an MPEG2 transport stream.

The SESF defines the encoding restriction of the elementary stream for the MPEG-2 transport stream and the AV stream. When the recording / reproducing apparatus 1 encodes and records an SESF stream, an EP_map is created and recorded on a disc.

The digital broadcast stream is recorded on the recording medium 100 by using one of the following methods. First, a digital broadcast stream is transcoded into a SESF stream. In this case, the recorded stream must conform to SESF. In this case, an EP_map must be created and recorded on the disc.

Alternatively, the elementary stream constituting the digital broadcast stream is transcoded into a new elementary stream, and re-multiplexed into a new transport stream conforming to a stream format defined by the standardization organization of the digital broadcast stream. In this case, an EP_map must be created and recorded on the disc.

For example, the input stream is an MPEG-2 transport stream conforming to ISDB (standard name of digital BS broadcasting in Japan), which is an HDTV video stream and an MPEG-2 transport stream.
Assume that it contains an AAC audio stream. Transcode the HDTV video stream into an SDTV video stream and remultiplex the SDTV video stream and the original AAC audio stream into TS. Both the SDTV stream and the recorded transport stream are ISDB
Must conform to format.

The digital broadcast stream is recorded on the recording medium 1
Another method for recording at 00 is to record the input transport stream transparently (record without changing the input transport stream), at which time an EP_map is created and recorded on the disc. You.

Alternatively, the input transport stream is recorded transparently (recording the input transport stream without any change), at which time a TU_map is created and recorded on the disc.

Next, directories and files will be described. Hereinafter, the recording / reproducing apparatus 1 is connected to a DVR (Digital Video Rec).
ording). FIG. 14 shows an example of a directory structure on a disk. The directory required on the DVR disk is "DVR" as shown in FIG.
A “PLAYLIST” directory, a “CLIPINF” directory, a “M2TS” directory, and a “DVR” directory that includes a “DATA” directory. Other directories may be created under the root directory, but they are
In the application format of the present embodiment, it is assumed that this is ignored.

[0110] Under the "DVR" directory, all files and directories specified by the DVR application format are stored. The “DVR” directory includes four directories. Under the “PLAYLIST” directory, database files of Real PlayList and Virtual PlayList are placed. This directory is
It exists even if there is no PlayList.

[0111] Under the "CLIPINF" directory, a Clip database is placed. This directory exists even if there is no Clip. An AV stream file is placed under the "M2TS" directory. This directory exists even if there is no AV stream file. The “DATA” directory stores data broadcast files such as digital TV broadcasts.

The “DVR” directory stores the following files. The "info.dvr" file is created under the DVR directory and stores the overall information of the application layer. There must be only one info.dvr under the DVR directory. The file name is info.d
Suppose it is fixed to vr. The "menu.thmb" file stores information related to the menu thumbnail image. DVR
There must be zero or one menu thumbnail below the directory. The file name is memu.thmb
And fixed to If there is no menu thumbnail image, this file does not have to exist.

[0113] The "mark.thmb" file stores information related to the mark thumbnail image. Under the DVR directory, there must be zero or one mark thumbnail. It is assumed that the file name is fixed to mark.thmb. If there is no menu thumbnail image, this file does not have to exist.

[0114] The "PLAYLIST" directory contains two types of Play.
Stores List files, which are Real
PlayList and Virtual PlayList. "Xxxxx.rpls"
The file stores information related to one Real PlayList. One file is created for each Real PlayList. The file name is "xxxxx.rpls".
Here, "xxxxx" is five numbers from 0 to 9.
Assume that the file extension must be "rpls".

The “yyyyy.vpls” file has one Virtual
Stores information related to PlayList. Each Virt
One file is created for each ual PlayList. The file name is "yyyyy.vpls". Here, "yyyyy" is 5
Are numbers from 0 to 9. The file extension is "vpl
s ".

The “CLIPINF” directory stores each AV
One file is stored corresponding to the stream file. The "zzzzz.clpi" file is a single AV stream file (Clip AV stream file or Bridge-Clip
AV stream file). The file name is "zzzzz.clpi", and "zzzzz" is
Five numbers from 0 to 9. Assume that the file extension must be "clpi".

The “M2TS” directory stores AV stream files. The “zzzzz.m2ts” file is an AV stream file handled by the DVR system. This is a Clip AV stream file or Bridge-Clip AV stre
am. The file name is "zzzzz.m2ts" and "zzzz
"z" is five numbers from 0 to 9. Assume that the file extension must be "m2ts".

[0118] The "DATA" directory stores data transmitted from a data broadcast, and the data is, for example, an XML file or an MHEG file.

Next, the syntax and semantics of each directory (file) will be described. First, “info.dv
r "file. FIG. 15 shows the" info.dv
r "is a diagram showing the syntax of the file." info.dv
The r ”file consists of three objects, DVRVolume (), TableOfPlayLists (), and Mak
ersPrivateData ().

To describe the syntax of info.dvr shown in FIG. 15, TableOfPlayLists_Start_address is
Indicates the start address of TableOfPlayList () in units of relative bytes from the start byte of the info.dvr file. Relative bytes are counted from zero.

MakersPrivateData_Start_address is inf
Indicates the start address of MakersPrivateData () in units of relative bytes from the first byte of the o.dvr file. Relative bytes are counted from zero. padding_
The word (padding word) is inserted according to the syntax of info.dvr. N1 and N2 are zero or any positive integer. Each padding word may take an arbitrary value.

DVRVolume () is a volume (disk)
Stores information that describes the contents of FIG. 16 shows the DVRVol
It is a figure showing the syntax of ume (). DVR shown in FIG.
To explain the syntax of Volume (), use version_number
Indicates four character characters indicating the version number of this DVRVolume (). version_number is ISO 646
Is encoded as “0045”.

The length is represented by a 32-bit unsigned integer indicating the number of bytes of the DVRVolume () from immediately after the length field to the end of the DVRVolume ().

[0124] ResumeVolume () stores the file name of the Real PlayList or Virtual PlayList that has been reproduced last in the volume. However, the playback position when the user interrupts the playback of Real PlayList or Virtual PlayList is the resume-mar defined in PlayListMark ().
k (FIGS. 42 and 43).

FIG. 17 is a diagram showing the syntax of ResumeVolume (). To explain the syntax of ResumeVolume () shown in FIG. 17, valid_flag indicates that when this 1-bit flag is set to 1, resume_PlayList_name
This flag indicates that the field is valid. If this flag is set to 0, it indicates that the resume_PlayList_name field is invalid.

[0126] The 10-byte field of resume_PlayList_name contains the Real PlayList or V to be resumed.
Indicates the file name of irtual PlayList.

UIAppInfoVolume in the syntax of DVRVolume () shown in FIG. 16 stores the parameters of the user interface application for the volume. FIG. 18 is a diagram showing the syntax of UIAppInfoVolume, and its semantics will be described below.
The 8-bit field of character_set is Volume_name
Shows how to encode character characters encoded in the field. The encoding method corresponds to the values shown in FIG.

The 8-bit field of name_length is Volu
Indicates the byte length of the volume name indicated in the me_name field. The Volume_name field indicates the name of the volume. Name_lengt from left in this field
The h number of bytes is a valid character character, which indicates the name of the volume. The value after those valid character characters in the Volume_name field may contain any value.

[0129] Volume_protect_flag is a flag indicating whether contents in the volume may be shown without restriction to the user. When this flag is set to 1, showing (reproducing) the contents of the volume to the user is permitted only when the user can correctly input the PIN number (password). If this flag is set to 0, the user
The user is allowed to show the contents of the volume without entering the PIN number.

First, at the time when the user inserts the disc into the player, if this flag is set to 0, or if this flag is set to 1, the user can correctly input the PIN number. Then, the recording / reproducing apparatus 1 displays a list of PlayLists in the disc. The playback limit of each PlayList is volume_p
Unrelated to rotect_flag, it is UIAppInfoPlayLi
Indicated by playback_control_flag defined in st ().

The PIN is composed of four numbers from 0 to 9, and each number is encoded according to ISO / IEC 646. The field of ref_thumbnail_index indicates information of a thumbnail image added to the volume. ref_th
If the umbnail_index field is not 0xFFFF,
Thumbnail images are added to the volume,
The thumbnail image is stored in the menu.thum file. The image is r in the menu.thum file
It is referenced using the value of ef_thumbnail_index. ref_thum
When the bnail_index field is 0xFFFF, it indicates that no thumbnail image is added to the volume.

Next, TableOfPlayLists () in the syntax of info.dvr shown in FIG. 15 will be described. TableOfPla
yLists () is a PlayList (Real PlayList and Virtual PlayLi
Store the file name of st). All PlayList files recorded in the volume are stored in TableOfPlayLis
Included in t (). TableOfPlayLists () indicates the default playback order of the PlayList in the volume.

FIG. 20 is a diagram showing the syntax of TableOfPlayLists (). The syntax will be described.
Four character characters indicating the version number of fPlayLists are shown. version_number must be encoded as "0045" according to ISO 646.

[0134] length is TableOfPlayLists () from immediately after this length field to the end of TableOfPlayLists ().
Is an unsigned 32-bit integer indicating the number of bytes of
The 16-bit field of number_of_PlayLists is Pla
Indicates the number of times of for-loop including yList_file_name.
This number must be equal to the number of PlayLists recorded on the volume. PlayList_file_name 10
The byte number indicates the file name of the PlayList.

[0135] Fig. 21 is a diagram illustrating another configuration of the syntax of TableOfPlayLists (). The syntax shown in FIG. 21 is obtained by adding UIAppinfoPlayLis to the syntax shown in FIG.
t (described later) is included. Thus, U
By including IAppinfoPlayList, TableO
A menu screen can be created simply by reading fPlayLists. Here, the following description is made assuming that the syntax shown in FIG. 20 is used.

[0136] In the syntax of info.dvr shown in FIG.
MakersPrivateData will be described. MakersPrivateDa
ta is provided so that the maker of the recording / reproducing apparatus 1 can insert the maker's private data into MakersPrivateData () for a special application of each company. Each manufacturer's private data has a standardized maker_ID to identify the manufacturer that defined it. MakersPrivateData () may include one or more maker_IDs.

When a predetermined maker wants to insert private data, if the private data of another maker is already included in MakersPrivateData (), the other maker does not delete the existing old private data. New private data MakersPrivateDat
Add it inside a (). Thus, in the present embodiment, private data of a plurality of manufacturers can be included in one MakersPrivateData ().

FIG. 22 is a diagram showing the syntax of MakersPrivateData. MakersPrivateData shown in Fig. 22
To explain the syntax of, version_number is
4 indicating the version number of this MakersPrivateData ()
Character characters. version_number is the ISO
It must be encoded as "0045" according to 646. l
ength is MakersPriva immediately after this length field.
Indicates a 32-bit unsigned integer indicating the number of bytes of MakersPrivateData () up to the end of teData ().

[0139] mpd_blocks_start_address is MakersPriv
Indicates the first byte address of the first mpd_block () in units of the relative number of bytes from the first byte of ateData (). Relative bytes are counted from zero. number_o
f_maker_entries is a 16-bit unsigned integer giving the number of entries of maker private data included in MakersPrivateData (). MakersPrivateDat
In a (), there must not be more than one maker private data with the same maker_ID value.

Mpd_block_size is a 16-bit unsigned integer giving the size of one mpd_block in units of 1024 bytes. For example, if mpd_block_size = 1, it indicates that the size of one mpd_block is 1024 bytes. number_of_mpd_blocks is Makers
1 that gives the number of mpd_blocks contained in PrivateData ()
6-bit unsigned integer. maker_ID is a 16-bit unsigned integer indicating the maker of the DVR system that created the maker private data. The value encoded in maker_ID is specified by the licensor of this DVR format.

Maker_model_code is a 16-bit unsigned integer indicating the model number code of the DVR system that created the maker private data. maker_mo
The value encoded in del_code is set by the manufacturer who has licensed this format. start_
The mpd_block_number is a 16-bit unsigned integer indicating the number of the mpd_block at which the maker private data starts. The head data of the maker private data must be aligned with the head of the mpd_block. start_mpd_block_number is the for-loop of mpd_block
Corresponds to the variable j in.

The mpd_length is a 32-bit unsigned integer indicating the size of the maker private data in byte units. mpd_block is an area where maker private data is stored. All mpd_blocks in MakersPrivateData () must be the same size.

Next, Real PlayList file and Virtual Play
For the List file, in other words, xxxxx.rpls and yyyyy.v
pls is explained. FIG. 23 shows xxxxx.rpls (Real Pl
ayList) or yyyyy.vpls (Virtual PlayList). xxxxx.rpls and yyyyy.vpls
Have the same syntax configuration. xxxxx.rpls and yyyyy.
vpls are each composed of three objects,
They are PlayList (), PlayListMark (), and Makers
PrivateData ().

[0144] PlayListMark_Start_address is a PlayList
Indicates the start address of PlayListMark () in units of relative bytes from the first byte of the file. Relative bytes are counted from zero.

MakersPrivateData_Start_address is Pla
Indicates the start address of MakersPrivateData () in units of relative bytes from the first byte of the yList file. Relative bytes are counted from zero.

[0146] The padding_word (padding word) is Pl
inserted according to the syntax of the ayList file, N
1 and N2 are zero or any positive integer. Each padding word may take an arbitrary value.

Here, as described briefly above, PlayLi
st will be further described. Everything in the disc
The playback section in all Clips except for the Bridge-Clip (described later) must be referenced by the Real PlayList. And two or more RealPlayLists
The playback section indicated by Item must not overlap in the same Clip.

Referring further to FIG. 24, FIG.
As shown in FIG. 4 (A), all Clips have the corresponding Real
PlayList exists. This rule is maintained even after the editing operation is performed, as shown in FIG. Therefore, all Clips are any Real PlayLis
By referring to t, it is always possible to view.

As shown in FIG. 24C, Virtual Pl
The playback section of ayList is the playback section of Real PlayList or B
Must be included in the playback section of the ridge-Clip. Bridge-Cli not referenced in any Virtual PlayList
p must not be in the disk.

[0150] The Real PlayList includes a list of PlayItems, but does not include SubPlayItems. Virtual PlayL
ist includes a list of PlayItems, CPI_type indicated in PlayList () is EP_map type, and PlayList_ty
When pe is 0 (PlayList including video and audio), Virtual PlayList can include one SubPlayItem. In the PlayList () in the present embodiment, Su
bPlayIte is used only for the purpose of audio dubbing, and the SubPlayI that one Virtual PlayList has
The number of tems must be 0 or 1.

Next, the PlayList will be described. FIG.
Fig. 4 is a diagram illustrating the syntax of a PlayList. To explain the syntax of the PlayList shown in FIG. 25, version_numb
er is four character characters indicating the version number of this PlayList (). version_number is ISO 64
According to 6, it must be encoded as "0045". len
gth is a 32-bit unsigned integer indicating the number of bytes of PlayList () from immediately after this length field to the end of PlayList (). PlayList_type is an 8-bit field indicating the type of the PlayList, an example of which is shown in FIG.

CPI_type is a 1-bit flag.
Clip referenced by ayItem () and SubPlayItem ()
Indicates the value of CPI_type of All Clips referenced by one PlayList are CPIs defined in their CPI ().
_type values must be the same. number_of_PlayI
tems is a 16-bit field indicating the number of PlayItems in the PlayList.

[0153] PlayItem_id corresponding to a predetermined PlayItem ()
Is the PlayItem () in the for-loop that contains the PlayItem ()
Are defined by the order in which they appear. PlayItem_id starts from 0. number_of_SubPlayItems is a 16-bit field indicating the number of SubPlayItems in the PlayList. This value is 0 or 1. Additional audio stream path (audio stream path)
Is a kind of sub-path.

Next, the UIAppInfoPlayList of the syntax of the PlayList shown in FIG. 25 will be described. UIAppInfoPl
ayList stores the parameters of the user interface application for PlayList. FIG.
Fig. 5 is a diagram illustrating the syntax of UIAppInfoPlayList.
To explain the syntax of the UIAppInfoPlayList shown in FIG. 27, character_set is an 8-bit field, and indicates the encoding method of the character characters encoded in the PlayList_name field. The encoding method is
This corresponds to a value based on the table shown in FIG.

[0155] The name_length is an 8-bit field, and the PlayList indicated in the PlayList_name field.
Indicates the byte length of the name. PlayList_name field is P
Indicates the name of layList. Nam from left in this field
The number of bytes of the e_length number is a valid character character, which indicates the name of the PlayList. The value after these valid character characters in the PlayList_name field may contain any value.

[0156] record_time_and_date is a 56-bit field that stores the date and time when the PlayList was recorded. This field is a four-bit Binary Coded Decimal for 14 numbers for year / month / day / hour / minute / second.
(BCD). For example, 2001/12/23: 0
1:02:03 is encoded as "0x20011223010203".

The duration is a 24-bit field indicating the total playback time of the PlayList in units of hours / minutes / seconds. This field is a 6-bit binary binary
Coded with CodedDecimal (BCD). For example,
01:45:30 is encoded as "0x014530".

[0158] The valid_period is a 32-bit field indicating a period during which the PlayList is valid. In this field, 8 numbers are converted to 4-bit Binary Coded Decimal (B
CD). For example, the recording / reproducing device 1
Is used to automatically delete a PlayList whose validity period has passed. For example, 2001/05/07 is "0x
20010507 ".

[0159] The maker_id indicates the manufacturer of the DVR player (recording / reproducing apparatus 1) that last updated the PlayList.
An unsigned integer of bits. The value encoded in maker_id is assigned by the licensor in DVR format. maker_code last updated its PlayList
This is a 16-bit unsigned integer indicating the model number of the DVR player. The value encoded in maker_code is determined by the manufacturer who has licensed the DVR format.

When the playback_control_flag flag is set to 1, the PlayList is reproduced only when the user can correctly input the PIN number. When this flag is set to 0, the user can view the PlayList without the user inputting a PIN number.

When the write_protect_flag is set to 1 as shown in the table of FIG.
Except for e_protect_flag, the contents of the PlayList are not deleted or changed. When this flag is set to 0, the user can freely delete and change the PlayList. When this flag is set to 1, the recording / reproducing apparatus 1 displays a message for reconfirming the user before the user deletes, edits, or overwrites the PlayList.

A Real PlayList in which write_protect_flag is set to 0 exists, and
There is a Virtual PlayList that refers to the Clip and its Virtua
l The write_protect_flag of the PlayList may be set to 1. When the user wants to delete the RealPlayList, the recording / reproducing apparatus 1 warns the user of the existence of the Virtual PlayList or “Minimize” the Real PlayList before deleting the Real PlayList.

As shown in FIG. 28B, when the flag is set to 1, is_played_flag
st indicates that the recording has been performed once since it was recorded, and 0
When the PlayList is set to, this indicates that the PlayList has never been reproduced since it was recorded.

The archive is, as shown in FIG.
This is a 2-bit field indicating whether the PlayList is an original or a copied one. ref_thum
The bnail_index field indicates information on a thumbnail image representing the PlayList. If the ref_thumbnail_index field has a value other than 0xFFFF, the PlayList contains Pl
A thumbnail image representing ayList is added, and the thumbnail image is stored in the menu.thum file. The image is called ref in the menu.thum file
It is referenced using the value of _thumbnail_index. ref_thumbn
If the ail_index field is 0xFFFF, the Play
No thumbnail image representing the PlayList is added to the List.

Next, PlayItem will be described. One Pl
ayItem () basically includes the following data. Clip_information_file_name to specify the file name of Clip, Cl
A pair of IN_time and OUT_time for specifying the playback section of ip, and CPI_type defined in PlayList () is EP_map t
ype, where IN_time and OUT_time refer to
STC_sequence_id, preceding PlayItem and current P
connection_cond indicating the state of the connection with the layItem
ition.

When a PlayList is composed of two or more PlayItems, those PlayItems are arranged in a line on the global time axis of the PlayList without a time gap or overlap. CPI_ty defined in PlayList ()
pe is EP_map type and the current PlayItem is BridgeS
When there is no equence (), the pair of IN_time and OUT_time defined in the PlayItem must point to a time on the same STC continuous section specified by STC_sequence_id. FIG. 29 shows such an example.

FIG. 30 is defined in PlayList ().
CPI_type is EP_map type and current PlayItem is B
When ridgeSequence () is used, the following rules are applied. Play preceding the current PlayItem
Item IN_time (indicated as IN_time1 in the figure)
Indicates the time on the STC continuous section specified by the STC_sequence_id of the preceding PlayItem. Preceding Pla
OUT_time of yItem (shown as OUT_time1 in the figure) indicates the time in the Bridge-Clip specified in BridgeSequenceInfo () of the current PlayItem. This O
UT_time must comply with the encoding restrictions described below.

[0168] The IN_time of the current PlayItem (IN_ti in the figure)
me2) is the BridgeS of the current PlayItem
Points to the time in the Bridge-Clip specified in equenceInfo (). This IN_time must also comply with the encoding restrictions described below. PlayItem of current PlayItem
OUT_time (shown as OUT_time2 in the figure)
Indicates the time on the STC continuous section specified by the STC_sequence_id of the current PlayItem.

As shown in FIG. 31, CPI_ty of PlayList ()
If pe is TU_map type, IN_time and OUT_ of PlayItem
A pair of time points to a time on the same Clip AV stream.

[0170] The syntax of the PlayItem is as shown in FIG. To explain the syntax of the PlayItem shown in FIG. 32, the field of Clip_Information_file_name is
Indicates the file name of the ClipInformation file. This Clip I
Clip_ defined in ClipInfo () of nformation file
stream_type must indicate a Clip AV stream.

[0171] STC_sequence_id is an 8-bit field, and the STC_sequence of the STC continuous section referred to by PlayItem.
Indicates nce_id. CPI_type specified in PlayList () is
If it is TU_map type, this 8-bit field has no meaning and is set to 0. IN_time is 32
This is a bit field and stores the playback start time of the PlayItem. As shown in FIG. 33, the semantics of IN_time differ depending on the CPI_type defined in PlayList ().

[0172] OUT_time is a 32-bit field and stores the playback end time of PlayItem. The semantics of OUT_time differ depending on the CPI_type defined in PlayList (), as shown in FIG.

[0173] Connection_Condition is a 2-bit field indicating the connection state between the preceding PlayItem as shown in Fig. 35 and the current PlayItem. FIG.
FIG. 36 is a diagram illustrating each state of Connection_Condition illustrated in FIG. 35.

Next, BridgeSequenceInfo will be described with reference to FIG.
This will be described with reference to FIG. BridgeSequenceInfo () is information attached to the current PlayItem, and has the following information. Br
idge-Clip AV stream file and corresponding Clip In
Bridge_Clip_Info that specifies the formation file (Figure 45)
Contains rmation_file_name.

Also, Clip A referred to by the preceding PlayItem
This is the address of the source packet on the V stream, and the first source packet of the Bridge-Clip AV stream file is connected following this source packet. This address is called RSPN_exit_from_previous_Clip. In addition, it is the address of the source packet on the Clip AV stream referred to by the current PlayItem, and Br
The last source packet of the idge-Clip AV stream file is connected. This address is RSPN_enter_to_curren
It is called t_Clip.

In FIG. 37, RSPN_arrival_time_disc
ontinuity indicates the address of the source packet where the arrival time base has a discontinuity in the Bridge-Clip AVstream file. This address is
Info () (FIG. 46).

[0177] Fig. 38 is a diagram illustrating the syntax of BridgeSequenceinfo. BridgeSequenceinfo shown in FIG. 38
Bridge_Clip_Information_
The file_name field indicates the file name of the Clip Information file corresponding to the Bridge-Clip AV stream file. Clip_stream_type defined in ClipInfo () of this Clip Information file is' Bridge-Clip AV st
must show ream '.

[0178] The 32-bit field of RSPN_exit_from_previous_Clip is the Clip AV referenced by the preceding PlayItem.
This is the relative address of the source packet on the stream, and the first source packet of the Bridge-Clip AV stream file is connected following this source packet. RSPN_exit_fr
The om_previous_Clip has a size in units of a source packet number, and a Clip AV st referenced by a preceding PlayItem.
The value of offset_SPN defined in ClipInfo () is counted from the first source packet of the ream file as an initial value.

[0179] The 32-bit field of the RSPN_enter_to_current_Clip is a Clip AV stream referenced by the current PlayItem.
This is the relative address of the source packet on am, and the last source packet of the Bridge-Clip AV stream file is connected before this source packet. RSPN_exit_from_pre
The vious_Clip has a size in units of a source packet number, and is counted from an initial value of offset_SPN defined in ClipInfo () from the first source packet of the Clip AV stream file referenced by the current PlayItem.

Next, SubPlayItem will be described with reference to FIG. SubPlayItem () uses PlayList ()
Is allowed only when the CPI_type of the is the EP_map type.
In the present embodiment, it is assumed that the SubPlayItem is used only for the purpose of audio dubbing. SubPla
yItem () includes the following data. First, Clip_inf for specifying the Clip referenced by the sub path in the PlayList
ormation_file_ name is included.

[0181] Also, SubPath_IN_time and SubPath_OUT_time for designating the playback section of the sub path in the Clip are included. Furthermore, sync_PlayItem_id and sy for specifying the time when the sub path starts playing on the time axis of the main path
nc_start_PTS_of_PlayItem is included. The audio Clip AV stream referenced by the sub path must not include STC discontinuities (system time base discontinuities). su
The clock of the audio sample of the Clip used for the b path is locked to the clock of the audio sample of the main path.

FIG. 40 is a diagram showing the syntax of SubPlayItem. To describe the syntax of the SubPlayItem shown in FIG. 40, the field of Clip_Information_file_name indicates the file name of the Clip Information file, which is used by the sub path in the PlayList. this
Clip_stream_type defined in ClipInfo () of the Clip Information file must indicate a Clip AV stream.

The 8-bit field of SubPath_type is
Indicates the type of sub path. Here, as shown in FIG. 41, only '0x00' is set, and other values are reserved for the future.

[0184] The 8-bit field of sync_PlayItem_id indicates the PlayItem_id of the PlayItem including the time at which the reproduction of the sub path starts on the time axis of the main path. Prescribed Pla
The value of PlayItem_id corresponding to yItem is defined in PlayList () (see FIG. 25).

[0185] The 32-bit field of sync_start_PTS_of_PlayItem indicates the time at which playback of the sub path starts on the time axis of the main path, and is referred to by sync_PlayItem_id.
Top 32 of PTS (Presentaiotn Time Stamp) on PlayItem
Indicates a bit. The 32-bit field of SubPath_IN_time stores the playback start time of the Sub path. SubPath_
IN_time indicates the upper 32 bits of a 33-bit PTS corresponding to the first presentation unit in the Sub Path.

[0186] The 32-bit field of SubPath_OUT_time stores the reproduction end time of the Sub path. SubPath_OU
T_time is Presentation_end_TS calculated by the following equation
Shows the upper 32 bits of the value of. Presentation_end_TS =
PTS_out + AU_duration Here, PTS_out is a 33-bit PTS corresponding to the last presentation unit of SubPath. AU_duration is a display period of the last presentation unit of the SubPath in units of 90 kHz.

Next, xxxxx.rpls and yyyyy.
PlayListMark () in the syntax of vpls will be described. Mark information about the PlayList is
Stored in rk. FIG. 42 is a diagram illustrating the syntax of PlayListMark. To explain the syntax of PlayListMark shown in FIG. 42, version_number
Four character characters indicating the version number of ayListMark (). version_number must be encoded as "0045" according to ISO 646.

[0188] length is a 32-bit unsigned integer indicating the number of bytes of PlayListMark () from immediately after this length field to the end of PlayListMark (). number_of_
PlayList_marks is a 16-bit unsigned integer indicating the number of marks stored in PlayListMark. number_of_PlayList_marks may be 0. mark_type is an 8-bit field indicating the type of mark, and is encoded according to the table shown in FIG.

[0189] The 32-bit field of mark_time_stamp stores a time stamp indicating the point at which the mark is specified. The semantics of mark_time_stamp are
As shown in FIG. 44, the CP defined in PlayList ()
Depends on I_type. PlayItem_id is an 8-bit field that specifies the PlayItem where the mark is placed. The value of PlayItem_id corresponding to a predetermined PlayItem is defined in PlayList () (see FIG. 25).

The 8-bit field of the character_set indicates the encoding method of the character character encoded in the mark_name field. The encoding method is shown in FIG.
9 corresponds to the value shown in FIG. The 8-bit field of name_length indicates the byte length of the mark name indicated in the Mark_name field. The mark_name field indicates the name of the mark. Name_len from left in this field
gth bytes are valid character characters,
It indicates the name of the mark. In the Mark_name field, any value may be set as the value after the valid character characters.

[0191] The ref_thumbnail_index field indicates the information of the thumbnail image added to the mark. ref_th
If the umbnail_index field is not 0xFFFF,
A thumbnail image is added to the mark, and the thumbnail image is stored in a mark.thmb file. The image is ref_t in the mark.thmb file
It is referenced using the value of humbnail_index (described later). ref_
When the thumbnail_index field is 0xFFFF, it indicates that no thumbnail image is added to the mark.

Next, the Clip information file will be described. zzzzz.clpi (Clip information file file) is composed of six objects as shown in FIG. They are ClipInfo (), STC_Info (), Progra
mInfo (), CPI (), ClipMark (), and MakersPrivateDat
a (). AV stream (Clip AV stream or Bri
dge-Clip AV stream) and corresponding Clip Informatio
For the n files, "zzzzz" of the same numeric string is used.

[0193] zzzzz.clpi (Clip informa) shown in FIG.
ClipInfo_Start_address is described in terms of the relative number of bytes from the first byte of the zzzzz.clpi file as ClipIn_Start_address.
Indicates the start address of fo (). Relative bytes are counted from zero.

[0194] STC_Info_Start_address indicates the start address of STC_Info () in units of relative bytes from the first byte of the zzzzz.clpi file. Relative bytes are counted from zero. ProgramInfo_Start_address
Indicates the start address of ProgramInfo () in units of relative bytes from the start byte of the zzzzz.clpi file. Relative bytes are counted from zero. CPI_Star
t_address indicates the start address of CPI () in units of relative bytes from the start byte of the zzzzz.clpi file. Relative bytes are counted from zero.

ClipMark_Start_address indicates the start address of ClipMark () in units of the relative number of bytes from the first byte of the zzzzz.clpi file. Relative bytes are counted from zero. MakersPrivateData_Start_ad
dress indicates the start address of MakersPrivateData () in units of relative bytes from the start byte of the zzzzz.clpi file. Relative bytes are counted from zero. padding_word (padding word) is zzzzz.clpi
Inserted according to file syntax. N1,
N2, N3, N4, and N5 must be zero or any positive integer. Each padding word may have an arbitrary value.

Next, ClipInfo will be described. FIG.
Fig. 4 is a diagram illustrating the syntax of ClipInfo. ClipInfo ()
Stores attribute information of the corresponding AV stream file (Clip AV stream or Bridge-Clip AV stream file).

The syntax of the ClipInfo shown in FIG. 46 will be described. Version_number is four character characters indicating the version number of this ClipInfo (). version_number must be encoded as "0045" according to ISO 646. length is a 32-bit unsigned integer indicating the number of bytes of ClipInfo () from immediately after the length field to the end of ClipInfo (). Clip
As shown in FIG. 47, the 8-bit field of _stream_type indicates the type of the AV stream corresponding to the Clip Information file. The stream type of each type of AV stream will be described later.

The 32-bit field of offset_SPN is
AV stream (Clip AV stream or Bridge-Clip A
Vstream) Gives the source packet number offset value for the first source packet in the file. This offset_SPN must be 0 when the AV stream file is first recorded on the disc.

As shown in FIG. 48, when the first part of the AV stream file is deleted by editing, the offset
_SPN may take a value other than zero. In the present embodiment, a relative source packet number (relative address) referring to offset_SPN is often described in syntax in the form of RSPN_xxx (xxx is deformed, eg, RSPN_EP_start). The relative source packet number has a size in units of the source packet number, and is counted from the first source packet of the AV stream file using the value of offset_SPN as an initial value.

The number of source packets (SPN_xxx) from the first source packet of the AV stream file to the source packet referenced by the relative source packet number is calculated by the following equation. SPN_xxx = RSPN_xxx-offset_SPN FIG. 48 shows an example in which offset_SPN is 4.

[0201] TS_recording_rate is a 24-bit unsigned integer, and the value of A_A is transmitted from the DVR drive (write unit 22) or from the DVR drive (read unit 28).
Gives the required input / output bit rate of the V stream. r
ecord_time_and_date is a 56-bit field that stores the date and time when the AV stream corresponding to the Clip was recorded. For the year / month / day / hour / minute / second, 14 numbers are used as a 4-bit Binary Coded Decimal. (BCD). For example, 2001/12/23: 01: 02: 03 is "
0x20011223010203 ".

The duration is a 24-bit field indicating the total playback time of the Clip in units of time / minute / second based on the arrival time clock. This field is
Six numbers are encoded by 4-bit Binary Coded Decimal (BCD). For example, 01:45:30 is "0x01453
Encoded as 0 ".

[0203] The flag of time_controlled_flag indicates the recording mode of the AV stream file. This time_control
When led_flag is 1, it indicates that the recording mode is a mode in which the file size is recorded in such a manner that the file size is proportional to the elapsed time from the recording, and the condition shown in the following equation must be satisfied. TS_average_rate * 192/188 * (t-start_time) -α <= si
ze_clip (t) <= TS_average_rate * 192/188 * (t-start_time) + α where TS_average_rate is the average bit rate of the transport stream of the AV stream file in bytes /
It is expressed in the unit of second.

[0204] In the above equation, t indicates a time expressed in seconds, start_time is the time when the first source packet of the AV stream file was recorded,
Expressed in seconds. size_clip (t) is A at time t
The size of the V stream file is expressed in bytes. For example, if 10 source packets are recorded from start_time to time t, size_clip (t) is 10
* It is 192 bytes. α is a constant that depends on TS_average_rate.

[0205] When time_controlled_flag is set to 0, it indicates that the recording mode is not controlled so that the elapsed time of recording and the file size of the AV stream are proportional. For example, this is the case when the input transport stream is recorded transparently.

TS_average_rate is time_controlled_fla
When g is set to 1, this 24-bit field indicates the value of TS_average_rate used in the above equation. If time_controlled_flag is set to 0, this field has no meaning and must be set to 0. For example, a transport stream with a variable bit rate is encoded by the following procedure. First, set the transport rate to TS_recording_rat
Set to the value of e. Next, the video stream is encoded at a variable bit rate. Then, the transport packet is intermittently encoded by not using the null packet.

[0207] RSPN_arrival_time_discontinuity of 32
The bit field is a relative address of a place where the arrival time base discontinuity occurs in the Bridge-Clip AV stream file. RSPN_arrival_time_discontinuit
y is a size in units of a source packet number, and B
The value of offset_SPN defined in ClipInfo () is counted from the first source packet of the ridge-Clip AV stream file as an initial value. That Bridge-Clip AV str
The absolute address in the eam file is calculated based on SPN_xxx = RSPN_xxx-offset_SPN described above.

[0208] A 144-bit field of reserved_for_system_use is reserved for the system. is_for
When the flag of mat_identifier_valid is 1, format_i
Indicates that the dentifier field is valid. is_or
If the flag of iginal_network_ID_valid is 1, ori
Indicates that the ginal_network_ID field is valid. When the flag of is_transport_stream_ID_valid is 1, it indicates that the field of transport_stream_ID is valid. When the flag of is_servece_ID_valid is 1, it indicates that the field of serve_ID is valid.

When the flag of is_country_code_valid is 1, it indicates that the field of country_code is valid. The format_identifier 32-bit field is used in the transport stream for registration deascriotor
Format_ide (defined in ISO / IEC13818-1)
Indicates the value of ntifier. The 16-bit field of original_network_ID indicates the value of original_network_ID defined in the transport stream. transport_s
The 16-bit field of stream_ID indicates the value of transport_stream_ID defined in the transport stream.

[0210] The 16-bit field of the servece_ID is defined in the servece_ID defined in the transport stream.
Indicates the ID value. The 24-bit field of country_code indicates a country code defined by ISO3166. Each character character is encoded in ISO8859-1. For example, Japan is represented as "JPN" and "0x4A 0x500
x4E ". stream_format_name is a 16-character ISO-646 character code indicating the name of the format organization that defines the stream of the transport stream. The invalid bytes in this field are:
The value '0xFF' is set.

Format_identifier, original_network_I
D, transport_stream_ID, servece_ID, country_code
, And stream_format_name indicate the service provider of the transport stream, and thereby, the audio and video stream encoding restrictions, SI
(Service Information) standards and stream definitions of private data streams other than audio / video streams can be recognized. This information can be used to determine whether the decoder can decode the stream and, if so, to initialize the decoder system before decoding starts.

Next, STC_Info will be described. Here, a time section in the MPEG-2 transport stream that does not include STC discontinuities (system timebase discontinuities) is referred to as an STC_sequence, and a STC_sequen
ce is specified by the value of STC_sequence_id. FIG.
0 is a diagram illustrating a continuous STC section. The same STC value in the same STC_sequence never appears (however, the maximum time length of the Clip is limited as described later). Therefore, the same PTS in the same STC_sequence
Also never appears. AV stream is N (N> 0)
When the STC discontinuous points are included, the system time base of the Clip is divided into (N + 1) STC_sequences.

STC_Info stores the address of the place where STC discontinuity (system time base discontinuity) occurs. As described with reference to FIG. 51, the RSPN_STC_sta
rt indicates the address, excluding the last STC_sequence
The kth (k> = 0) STC_sequence is the kth RSPN_STC_sta
It starts from the time at which the source packet referred to by rt arrives, and ends at the time at which the (k + 1) th source packet referred to by RSPN_STC_start arrives. Last STC_sequence
Starts at the time at which the last source packet referenced by RSPN_STC_start arrives and ends at the time at which the last source packet arrives.

FIG. 52 is a diagram showing the syntax of STC_Info. To describe the syntax of STC_Info shown in FIG. 52, version_number is four character characters indicating the version number of this STC_Info ().
version_number must be encoded as "0045" according to ISO 646.

[0215] length is a 32-bit unsigned integer indicating the number of bytes of STC_Info () from immediately after this length field to the end of STC_Info (). CPI_type of CPI () is T
When the U_map type is indicated, the length field may be set to zero. When CPI_type of CPI () indicates EP_map type, num_of_STC_sequences must be a value of 1 or more.

[0216] The 8-bit unsigned integer of num_of_STC_sequences indicates the number of STC_sequences in the Clip. This value indicates the number of for-loops following this field. STC_sequence_id corresponding to predetermined STC_sequence
Is the STC_se in the for-loop including RSPN_STC_start
It is defined by the order in which RSPN_STC_start corresponding to the queue appears. STC_sequence_id starts from 0.

[0217] The 32-bit field of RSPN_STC_start indicates the address at which STC_sequence starts on the AV stream file. RSPN_STC_start indicates an address at which a discontinuity point of the system time base occurs in the AV stream file. RSPN_STC_start may be the relative address of the source packet having the first PCR of the new system time base in the AV stream. RSPN_STC_sta
rt is a size in units of a source packet number,
Clip from the first source packet of the AV stream file
The offset_SPN value defined in Info () is counted as an initial value. The absolute address in the AV stream file is already SPN_xxx = RSPN_xxx-off
Calculated by set_SPN.

Next, ProgramInfo in the syntax of zzzzz.clip shown in FIG. 45 will be described. As described with reference to FIG. 53, a time section having the following characteristics in a Clip is referred to as a program_sequence. First, PCR_PI
The value of D does not change. Next, the number of video elementary streams does not change. Also, the value of the PID for each video stream and the coding information defined by the VideoCodingInfo do not change. Furthermore, the number of audio elementary streams does not change. Also, the PID value for each audio stream and the encoding information defined by its AudioCodingInfo do not change.

Program_sequence has only one system time base at the same time. program_
A sequence has only one PMT at the same time. ProgramInfo () stores the address of the place where program_sequence starts. RSPN_program_sequence_st
art indicates the address.

FIG. 54 is a diagram showing the syntax of ProgramInfo. In describing the syntax of ProgramInfo shown in FIG. 54, version_number is four character characters indicating the version number of ProgramInfo (). version_number must be encoded as "0045" according to ISO 646.

Length is a 32-bit unsigned integer indicating the number of bytes of ProgramInfo () from immediately after the length field to the end of ProgramInfo (). CPI_t of CPI ()
If ype indicates TU_map type, this length field may be set to zero. CPI_type of CPI () is EP_map
When indicating type, number_of_programs must be a value of 1 or more.

[0222] The 8-bit unsigned integer of number_of_program_sequences indicates the number of program_sequences in the Clip. This value indicates the number of for-loops following this field. If program_sequence does not change in the Clip, number_of_program_sequences must be set to 1. RSPN_program_sequence_start
Is a relative address of the place where the program sequence starts on the AV stream file.

[0223] RSPN_program_sequence_start has a size in units of source packet numbers, and is counted from the first source packet of the AV stream file using the value of offset_SPN defined in ClipInfo () as an initial value. The absolute address in the AV stream file is calculated by SPN_xxx = RSPN_xxx-offset_SPN. RSPN_p in syntax for-loop
rogram_sequence_start values must appear in ascending order.

The 16-bit field of the PCR_PID has its p
Indicates the PID of a transport packet including a valid PCR field in rogram_sequence. The 8-bit field of number_of_videos is video_stream_PID and VideoCodingInf
Indicates the number of for-loop loops including o (). number_of_aud
The 8-bit field of ios is audio_stream_PID and Audio
Indicates the number of times of for-loop including CodingInfo (). vide
The 16-bit field of o_stream_PID is
Indicates the PID of a transport packet containing a valid video stream in the sequence. VideoCo following this field
dingInfo () must describe the content of the video stream referenced by the video_stream_PID.

[0225] The 16-bit field of audio_stream_PID indicates the PID of a transport packet including an audio stream valid for the program_sequence. AudioCodingInfo () following this field is the audio_strea
The content of the video stream referenced by m_PID must be explained.

[0226] In the for-loop of the syntax, video_
The order in which the stream_PID values appear is the program_sequence
Must be equal to the order in which the PIDs of the video streams are encoded in the valid PMT. Also, the order in which the value of audio_stream_PID appears in the syntax for-loop must be equal to the order in which the PID of the audio stream is encoded in the PMT valid for the program_sequence.

FIG. 55 is a diagram showing the syntax of VideoCodingInfo in the syntax of Programinfo shown in FIG. To explain the syntax of VideoCodingInfo shown in FIG. 55, the 8-bit field of video_format is
As shown in FIG. 56, video_strea in ProgramInfo ()
Indicates the video format corresponding to m_PID.

The 8-bit field of frame_rate is shown in FIG.
As shown in FIG. 7, video_stream_PI in ProgramInfo ()
Indicates the frame rate of the video corresponding to D. display_a
As shown in FIG. 58, the 8-bit field of spect_ratio indicates the display aspect ratio of the video corresponding to video_stream_PID in ProgramInfo ().

FIG. 59 is a diagram showing the syntax of AudioCodingInfo in the syntax of Programinfo shown in FIG. To describe the syntax of AudioCodingInfo shown in FIG. 59, the 8-bit field of audio_coding is
As shown in FIG. 60, audio_strea in ProgramInfo ()
This section shows the audio encoding method corresponding to m_PID.

As shown in FIG. 61, the 8-bit field of audio_component_type is audio in ProgramInfo ().
Indicates the audio component type corresponding to _stream_PID. As shown in FIG. 62, the 8-bit field of sampling_frequency is audio_s in ProgramInfo ().
Indicates the audio sampling frequency corresponding to tream_PID.

Next, the CPI (Characteristic Point Information) in the syntax of zzzzz.clip shown in FIG. 45 will be described. The CPI is for associating time information in an AV stream with an address in the file. There are two types of CPI, EP_map and TU_
map. As shown in FIG. 63, CPI_type in CPI ()
Is EP_map type, the CPI () includes EP_map. FIG.
As shown in FIG. 4, when CPI_type in CPI () is TU_map type, CPI () includes TU_map. One AV stream has one EP_map or one TU_map. When the AV stream is a SESF transport stream, the corresponding Clip must have an EP_map.

FIG. 65 is a diagram showing the syntax of CPI. To explain the syntax of the CPI shown in FIG.
sion_number is 4 indicating the version number of this CPI ()
Character characters. version_number is the ISO
It must be encoded as "0045" according to 646. l
“ength” is a 32-bit unsigned integer indicating the number of bytes of CPI () from immediately after the length field to the end of CPI (). CPI_type is a 1-bit flag, as shown in FIG. 66, and represents the CPI type of the Clip.

Next, the EP_map in the syntax of the CPI shown in FIG. 65 will be described. There are two types of EP_maps, EP_map for video streams and EP_map for audio streams. EP_map_t in EP_map
ype distinguishes the type of EP_map. EP for video stream if Clip contains one or more video streams
_map must be used. If the Clip contains no video stream but one or more audio streams, an EP_map for the audio stream must be used.

About EP_map for Video Stream FIG. 6
This will be described with reference to FIG. EP_map for video stream
Is stream_PID, PTS_EP_start, and RSPN_EP_star
It has data called t. stream_PID indicates a PID of a transport packet transmitting a video stream. PTS
_EP_start indicates the PTS of the access unit starting from the sequence header of the video stream. RSPN_EP_start
Indicates the address of the source packet including the first byte of the access unit referenced by PTS_EP_start in the AV stream.

[0235] A sub-table called EP_map_for_one_stream_PID () is created for each video stream transmitted by transport packets having the same PID.
If there are multiple video streams in the Clip, EP
_map may include a plurality of EP_map_for_one_stream_PID ().

The EP_map for the audio stream is stre
It has data of am_PID, PTS_EP_start, and RSPN_EP_start. stream_PID indicates a PID of a transport packet transmitting an audio stream. PTS_EP_st
art is the PTS of the audio stream access unit
Is shown. RSPN_EP_start is the PTS_EP_
Indicates the address of the source packet including the first byte of the access unit referenced by start.

[0237] A sub-table called EP_map_for_one_stream_PID () is created for each audio stream transmitted by transport packets having the same PID. When a plurality of audio streams exist in a Clip, the EP_map may include a plurality of EP_map_for_one_stream_PID ().

To explain the relationship between EP_map and STC_Info, 1
One EP_map_for_one_stream_PID () is created in one table regardless of STC discontinuities. By comparing the value of RSPN_EP_start with the value of RSPN_STC_start defined in STC_Info (), it belongs to each STC_sequence
The boundaries of the EP_map data are known (see FIG. 68).・ EP
The _map must have one EP_map_for_one_stream_PID for a range of continuous streams transmitted with the same PID. In the case as shown in FIG. 69, program # 1
And program # 3 have the same video PID, but the data range is not continuous.
Must have _for_one_stream_PID.

[0239] Fig. 70 is a diagram illustrating the syntax of the EP_map. To explain the syntax of the EP_map shown in FIG. 70, EP_type is a 4-bit field.
Indicates the entry point type of EP_map. EP_type indicates the semantics of the data field following this field. If the Clip contains one or more video streams, EP_type must be set to 0 ('video'). Alternatively, if the Clip does not include a video stream but includes one or more audio streams, the EP_type must be set to 1 ('audio').

[0240] The 16-bit field of number_of_stream_PIDs indicates the number of times of a for-loop in which number_of_stream_PIDs in EP_map () is a variable. stream_PID
The 16-bit field of (k) is EP_map_for_one_stre
Indicates the PID of the transport packet transmitting the k-th elementary stream (video or audio stream) referenced by am_PID (num_EP_entries (k)). If EP_type is equal to 0 ('video'), the elementary stream must be a video stream. When EP_type is equal to 1 ('audio'), the elementary stream must be an audio stream.

The 16-bit field of num_EP_entries (k) is EP_map_for_one_stream_PID (num_EP_entries
(k)) indicates num_EP_entries (k). EP_
map_for_one_stream_PID_Start_address (k): This 32-bit field is used for EP_map_for_one_s in EP_map ().
Indicates the relative byte position where tream_PID (num_EP_entries (k)) starts. This value is indicated by the size from the first byte of EP_map ().

Padding_word must be inserted according to the syntax of EP_map (). X and Y must be zero or any positive integer. Each padding word may take any value.

FIG. 72 is a diagram showing the syntax of EP_map_for_one_stream_PID. EP_map_for shown in FIG. 72
To explain the syntax of _one_stream_PID, use PTS_EP_st
The semantics of the 32-bit field of art is EP_
Depends on EP_type defined in map (). EP_typ
If e is equal to 0 ('video'), this field has the upper 32 bits of the 33-bit precision PTS of the access unit beginning with the video stream sequence header. E
If P_type is equal to 1 ('audio'), this field has the upper 32 bits of the 33-bit PTS of the access unit of the audio stream.

[0244] The semantics of the 32-bit field of RSPN_EP_start are the same as those of EP_t defined in EP_map ().
Depends on ype. If the EP_type is equal to 0 ('video'), this field shall be set to the PTS_EP_sta
Indicates the relative address of the source packet including the first byte of the sequence header of the access unit referenced by rt. Or, if EP_type is equal to 1 ('audio'),
This field indicates the relative address of the source packet including the first byte of the audio frame of the access unit referenced by PTS_EP_start in the AV stream.

[0245] RSPN_EP_start has a size in units of source packet numbers, and is defined in ClipInfo () from the first source packet of the AV stream file.
Counted using the value of fset_SPN as the initial value. The absolute address in the AV stream file is calculated by SPN_xxx = RSPN_xxx-offset_SPN. RSPN_E in syntax for-loop
The values of P_start must appear in ascending order.

Next, the TU_map will be described with reference to FIG. TU_map creates one time axis based on the arrival time clock (arrival time based clock) of the source packet. The time axis is called TU_map_time_axis. The origin of TU_map_time_axis is of TU_map ()
Indicated by fset_time. TU_map_time_axis is off
It is divided into certain units from set_time. The unit is ti
Called me_unit.

In each time_unit in the AV stream, the address of the first complete source packet on the AV stream file is stored in TU_map. These addresses are called RSPN_time_unit_start. TU_map
On the _time_axis, the time when the k-th (k> = 0) time_unit starts is called TU_start_time (k). This value is calculated based on the following equation. TU_start_time (k) = offset_time + k * time_unit_size TU_start_time (k) has an accuracy of 45 kHz.

FIG. 74 is a diagram showing the syntax of TU_map. To explain the syntax of TU_map shown in FIG. 74, the 32-bit field of offset_time is TU_map_t
Gives the offset time for ime_axis. This value indicates the offset time for the first time_unit in the Clip. The offset_time is a size in units of a 45 kHz clock derived from an arrival time clock with a precision of 27 MHz. If the AV stream is recorded as a new Clip, offset_time must be set to zero.

[0249] The 32-bit field of time_unit_size gives the size of time_unit.
The size is in units of a 45 kHz clock derived from an arrival time clock with 7 MHz accuracy. time_unit
_size is preferably 1 second or less (time_unit_size <= 45000). The 32-bit field of number_of_time_unit_entries is the time_u stored in TU_map ().
Shows the number of nit entries.

[0250] The 32-bit field of RSPN_time_unit_start indicates the relative address of the place where each time_unit starts in the AV stream. RSPN_time_unit_sta
rt is a size in units of a source packet number,
ClipInf from the first source packet of the AV stream file
The value of offset_SPN defined in o () is counted as an initial value. The absolute address in the AV stream file is calculated by SPN_xxx = RSPN_xxx-offset_SPN. RSPN_t in the syntax for-loop
The values of ime_unit_start must appear in ascending order.
If there are no source packets in the (k + 1) th time_unit, the (k + 1) th RSPN_time_unit_start is the kth RS_time_unit_start.
Must be equal to PN_time_unit_start.

[0251] The ClipMark in the syntax of zzzzz.clip shown in Fig. 45 will be described. ClipMark is mark information about a clip, and is stored in ClipMark. This mark is set by the recorder (recording / reproducing apparatus 1), and is not set by the user.

FIG. 75 is a diagram showing the syntax of ClipMark. To explain the syntax of the ClipMark shown in FIG. 75, version_number is four character characters indicating the version number of this ClipMark (). versio
n_number must be encoded as "0045" according to ISO 646.

[0253] length is a 32-bit unsigned integer indicating the number of bytes of ClipMark () from immediately after this length field to the end of ClipMark (). number_of_Clip_mar
ks is a 16-bit unsigned integer indicating the number of marks stored in ClipMark. number_of_Clip_mar
ks may be 0. mark_type is an 8-bit field indicating the type of mark, and is encoded according to the table shown in FIG.

[0254] mark_time_stamp is a 32-bit field and stores a time stamp indicating the point at which the mark is specified. The semantics of mark_time_stamp is, as shown in FIG. 77, CPI_type in PlayList ().
Depends on

STC_sequence_id is CPI_type in CPI ()
Indicates the EP_map type, this 8-bit field indicates the STC_sequence_id of the STC continuous section where the mark_time_stamp is located. CPI_type in CPI () is TU
When indicating _map type, this 8-bit field has no meaning and is set to zero. character_set
The 8-bit field indicates the encoding method of the character character encoded in the mark_name field.
The encoding method corresponds to the values shown in FIG.

An 8-bit field of name_length is Mar
Indicates the byte length of the mark name indicated in the k_name field. The mark_name field indicates the name of the mark. The number of name_length bytes from the left in this field is a valid character character, which indicates the name of the mark. The value after these valid character characters in the mark_name field may contain any value.

[0257] The field of ref_thumbnail_index indicates the information of the thumbnail image added to the mark. ref_th
If the umbnail_index field is not 0xFFFF,
A thumbnail image is added to the mark, and the thumbnail image is stored in a mark.thmb file. The image is ref_t in the mark.thmb file
It is referenced using the value of humbnail_index. ref_thumbnai
If the l_index field is 0xFFFF, no thumbnail image is added to the mark.

FIG. 78 is a diagram showing another syntax of ClipMark instead of FIG. 75, and FIG. 79 shows an example of a mark_type table instead of FIG. 76 in that case. r
eserved_for_maker_ID is mark_type from 0xC0 to 0xFF
Is a 16-bit field indicating the manufacturer ID of the manufacturer defining the mark_type.
The manufacturer ID is specified by the DVR format licensor. mark_entry () is information indicating a point designated as a mark point, and details of its syntax will be described later. representative_picture_entry () is mark_entry ()
Is information indicating a point of an image representing the mark indicated by the mark, and details of the syntax will be described later.

ClipMark is used to enable a user to visually search the contents of an AV stream when playing back the stream. The DVR player presents ClipMark information to the user using a GUI (graphical user interface). In order to visually display ClipMark information, it is better to show the picture indicated by representative_picture_entry () rather than the picture indicated by mark_entry ().

In FIG. 80, mark_entry () and representative
Here is an example of _picture_entry (). For example, it is assumed that a program name (title) of a program is displayed a while (several seconds later) after a program starts. Clip
When creating a Mark, mark_entry () should be placed at the start of the program, and representative_picture_entry ()
May be placed at the point where the program name (title) of the program is displayed.

[0261] The DVR player uses the representative_picture_
When the image of the entry is displayed on the GUI and the user specifies the image, the DVR player starts reproduction from the point where the mark_entry is placed.

Mark_entry () and representative_pic
The syntax of ture_entry () is shown in FIG.

[0263] mark_time_stamp is a 32-bit field. In the case of mark_entry (), a time stamp indicating the point at which the mark is specified is stored.
In the case of tative_picture_entry (), a time stamp indicating a point of an image representing a mark indicated by mark_entry () is stored.

Next, in order to specify a ClipMark, instead of using time stamp-based information by PTS, mark_entry when address-based information is used.
FIG. 82 shows an example of syntax of () and representative_picture_entry ().

[0265] In the case of mark_entry (), RSPN_ref_EP_start indicates the relative address of the source packet indicating the entry point of the stream for decoding the picture at the mark point in the AV stream. Also, representati
In the case of ve_picture_entry (), it indicates the relative address of the source packet indicating the entry point of the stream for decoding the picture representing the mark indicated by mark_entry (). The value of RSPN_ref_EP_start is EP_ma
must be stored as RSPN_EP_start in p and the PTS_EP_star corresponding to that RSPN_EP_start
The value of t must be the closest past value in the EP_map to the PTS of the picture at the mark point.

[0266] offset_num_pictures is a 32-bit field and indicates the number of offset pictures from the picture referenced by RSPN_ref_EP_start to the picture indicated by the mark point in display order. This number is counted from zero. In the case of the example of FIG. 83, offset_num_pictu
res is 6.

Next, mark_entry () and repr when address-based information is used to specify a ClipMark
Another example of the syntax of esentative_picture_entry () is shown in FIG.

[0268] In the case of mark_entry (), RSPN_mark_point indicates the relative address of the source packet including the first byte of the access unit referenced by the mark in the AV stream. Also, representative_picture_entry
In the case of (), it indicates the relative address of the source packet including the first byte of the encoded picture representing the mark indicated by mark_entry ().

[0269] RSPN_mark_point has a size in units of source packet numbers, and is counted from the first source packet of the AV stream file using the value of offset_SPN defined in the Clip Information file as an initial value.

The relationship between ClipMark and EP_map will be described with reference to FIG. In the case of this example, it is assumed that the EP_map specifies I0, I1, and In as the addresses of the entry points, and the I picture following the sequence header starts from these addresses. When ClipMark specifies M1 as the address of a certain mark, in order to be able to decode the picture starting from the source packet, M1
Is the closest entry point before the address
What is necessary is just to start reading data from I1.

Since MakersPrivateData has already been described with reference to FIG. 22, its description will be omitted.

Next, thumbnail information (Th
(umbnail Information) will be described. Thumbnail images are stored in menu.thmb or mark.thmb files. These files have the same syntax structure and have only one Thumbnail (). The menu.thmb file stores menu thumbnail images, that is, images representing Volume and images representing respective PlayLists. All menu thumbnails are stored in a single menu.thmb file.

The mark.thmb file stores a mark thumbnail image, that is, a picture representing a mark point.
All mark thumbnails for all PlayLists and Clips are stored in only one mark.thmb file. Since thumbnails are frequently added and deleted, it is necessary to easily and quickly perform addition and partial deletion operations. For this reason, Thumbnail () has a block structure. The image data is divided into several parts, and each part is stored in one tn_block. One image data is stored in a continuous tn_block. An unused tn_block may exist in the column of tn_block.
The byte length of one thumbnail image is variable.

FIG. 86 shows the syntax of menu.thmb and mark.thmb. FIG. 87 shows the syntax of menu.tmb shown in FIG.
It is a figure which shows the syntax of Thumbnail in the syntax of hmb and mark.thmb. To describe the syntax of Thumbnail shown in FIG. 87, version_number
Four character characters indicating the version number of bnail (). version_number is, according to ISO 646, "
0045 ".

[0275] length is a 32-bit unsigned integer indicating the number of bytes of MakersPrivateData () from immediately after this length field to the end of Thumbnail (). tn_block
s_start_address is a 32-bit unsigned integer indicating the first byte address of the first tn_block in units of the relative number of bytes from the first byte of Thumbnail (). Relative bytes are counted from zero. number_of_thum
bnails is a 16-bit unsigned integer giving the number of entries of thumbnail images included in Thumbnail ().

[0276] tn_block_size is a 16-bit unsigned integer giving the size of one tn_block in units of 1024 bytes. For example, if tn_block_size = 1, it indicates that the size of one tn_block is 1024 bytes. number_of_tn_blocks is tn in this Thumbnail ()
This is a 116-bit unsigned integer representing the number of entries of _block. The thumbnail_index is a 16-bit unsigned integer representing the index number of the thumbnail image represented by the thumbnail information for one for loop starting from the thumbnail_index field. As thumbnail_index,
Do not use the value 0xFFFF. thumbnail_inde
x is UIAppInfoVolume (), UIAppInfoPlayList (), PlayL
ref_thumbnail_ind in istMark () and ClipMark ()
referenced by ex.

The thumbnail_picture_format is an 8-bit unsigned integer representing the picture format of a thumbnail image, and takes a value as shown in FIG. DCF and PNG in the table
Is only allowed in "menu.thmb". The mark thumbnail must take the value "0x00" (MPEG-2 Video I-picture).

[0278] picture_data_size is a 32-bit unsigned integer indicating the byte length of the thumbnail image in byte units. start_tn_block_number is a 16-bit unsigned integer representing the tn_block number of the tn_block at which the thumbnail image data starts. The head of the thumbnail image data must match the head of tb_block. tn
The _block number starts at 0 and relates to the value of the variable k in the for-loop of tn_block.

X_picture_length is a 16-bit unsigned integer representing the number of pixels in the horizontal direction of the frame picture frame of the thumbnail image. y_picture_length is 16 representing the number of pixels in the vertical direction of the frame picture frame of the thumbnail image.
An unsigned integer of bits. tn_block is an area where thumbnail images are stored. All tn_blocks in Thumbnail () have the same size (fixed length), and the size is defined by tn_block_size.

FIG. 89 is a diagram schematically showing how thumbnail image data is stored in tn_block. As shown in FIG. 89, each thumbnail image data is tn_blo
Starting from the beginning of ck, if the size exceeds 1 tn_block, it is stored using the next successive tn_block. This makes it possible to manage variable-length picture data as fixed-length data,
Editing such as deletion can be handled by simple processing.

Next, the AV stream file will be described. The AV stream file is stored in the “M2TS” directory (FIG. 14). There are two types of AV stream files, which are a Clip AV stream and a Bridge-Clip AV stream file. Both
Both AV streams must have the structure of a DVR MPEG-2 transport stream file defined hereafter.

First, the DVR MPEG-2 transport stream will be described. The structure of the DVR MPEG-2 transport stream is as shown in FIG. An AV stream file has the structure of a DVR MPEG2 transport stream. The DVR MPEG2 transport stream is composed of an integer number of Aligned units. Alignedu
The size of the nit is 6144 bytes (2048 * 3 bytes).
The Aligned unit starts from the first byte of the source packet. The source packet is 192 bytes long. One source packet includes TP_extra_header and a transport packet. TP_extra_header is 4 bytes long, and the transport packet is 188 bytes long.

One Aligned unit consists of 32 source packets. The last Aligned unit in the DVR MPEG2 transport stream also consists of 32 source packets. Therefore, the DVR MPEG2 transport stream ends at the boundary of the Aligned unit. When the number of transport packets of the input transport stream recorded on the disc is not a multiple of 32, a source packet having a null packet (transport packet of PID = 0x1FFF) must be used for the last Aligned unit. The file system must not add extra information to the DVR MPEG2 transport stream.

FIG. 91 shows a recorder model of the DVR MPEG-2 transport stream. The recorder shown in FIG. 91 is a conceptual model for defining a recording process. The DVR MPEG-2 transport stream follows this model.

[0285] The input timing of the MPEG-2 transport stream will be described. The input MPEG2 transport stream is a full transport stream or a partial transport stream. Input
The MPEG2 transport stream must conform to ISO / IEC13818-1 or ISO / IEC13818-9. MPEG
2 The i-th byte of the transport stream is T-STD
(Transport stream system specified in ISO / IEC 13818-1
m target decoder) 51 and source packetizer (sourse
packetizer) 54 at the same time at time t (i). Rp
k is the instantaneous maximum value of the input rate of the transport packets.

The 27 MHz PLL 52 generates a 27 MHz clock frequency. 27MHz clock frequency is MPEG-2
Transport Stream PCR (Program Clock Refer
ence). Arrival time clock counter 53 is 27
It is a binary counter that counts pulses with a frequency of MHz. Arrival_time_clock (i) is the count value of arrival time clock counter 53 at time t (i).

[0287] The source packetizer 54 adds TP_extra_header to all transport packets to create a source packet. Arrival_time_stamp represents the time when the first byte of the transport packet arrives at both the T-STD 51 and the source packetizer 54. Arrival_
time_stamp (k) is given by Arrival_time_
This is a sample value of clock (k), where k indicates the first byte of the transport packet. arrival_time_stamp (k) = arrival_time_clock (k)% 2 ³⁰

[0288] two time intervals of the transport packet is successively inputted, 2 ^30/27000000 seconds may become (about 40 seconds) or more, Arri of the two transport packets
difference val_time_stamp should be set to be 2 ^30/27000000 seconds. The recorder is prepared for such a case.

[0289] Smoothing buffer
r) 55 smoothes the bit rate of the input transport stream. Smoothing buffer 55
Must not overflow. Rmax is an output bit rate of a source packet from the smoothing buffer 55 when the smoothing buffer 55 is not empty.
When the smoothing buffer 55 is empty, the output bit rate from the smoothing buffer 55 is zero.

Next, the parameters of the recorder model of the DVR MPEG-2 transport stream will be described. Rm
The value of ax is the ClipIn corresponding to the AV stream file.
Given by TS_recording_rate defined in fo (). This value is calculated by the following equation. Rmax = TS_recording_rate * 192/188 The value of TS_recording_rate is a size in units of bytes / second.

When the input transport stream is a SESF transport stream, Rpk is TS_rec defined in ClipInfo () corresponding to the AV stream file.
Must be equal to ording_rate. If the input transport stream is not a SESF transport stream, this value is the descriptor of the MPEG-2 transport stream, such as maximum_bitrate_descriptor or partial_
A value defined in transport_stream_descriptor or the like may be referred to.

If the input transport stream is a SESF transport stream, the smoothing buffer 5
The size (smoothing buffer size) of 5 is zero.
When the input transport stream is not the SESF transport stream, the size of the smoothing buffer 55 is a descriptor of the MPEG-2 transport stream, for example, smoothing_buffer_descriptor, short_smoothing_buf
fer_descriptor, partial_transport_stream_descripto
You may refer to the value defined in r or the like.

Recording Machine (Recorder) and Recording / Reproducing Apparatus 1
(Player) must provide a buffer of sufficient size. The default buffer size is 1536
bytes.

Next, a player model of the DVR MPEG-2 transport stream will be described. FIG. 92 shows a DVR
FIG. 3 is a diagram illustrating a player model of an MPEG-2 transport stream. This is a conceptual model for defining the regeneration process. The DVR MPEG-2 transport stream follows this model.

27 MHz X-tal (crystal oscillator) 61
Generates a frequency of 27 MHz. The error range for the 27 MHz frequency must be +/- 30 ppm (27000000 +/- 810 Hz). arrival time clock counter 62 is 27MH
It is a binary counter that counts pulses of frequency z. arrival_time_clock (i) is the count value of the arrival time clock counter 62 at time t (i).

In the smoothing buffer 64, Rmax is
This is the input bit rate of the source packets to the smoothing buffer 64 when the smoothing buffer 64 is not full. When the smoothing buffer 64 is full, the input bit rate to the smoothing buffer 64 is zero.

[0297] To explain the output timing of the MPEG-2 transport stream, the arriva of the current source packet will be described.
When l_time_stamp is equal to the LSB 30-bit value of arrival_time_clock (i), the transport packet of the source packet is extracted from the smoothing buffer 64. Rpk is the instantaneous maximum value of the transport packet rate. The smoothing buffer 64 must not underflow.

For the parameters of the player model of the DVR MPEG-2 transport stream,
It is the same as the parameter of the recorder model of the EG-2 transport stream.

[0299] Fig. 93 is a diagram illustrating the syntax of the Source packet. transport_packet () supports ISO / IEC 13818-
This is an MPEG-2 transport packet specified by 1.
TP_Extr in the syntax of the source packet shown in FIG. 93
FIG. 94 shows the syntax of a_header. As shown in FIG.
To explain the syntax of TP_Extra_header, use cop
y_permission_indicator is an integer representing the copy restriction of the payload of the transport packet. Copy restrictions can be copy free, no more copy, copy once, or copy
can be prohibited. FIG. 95 shows copy_perm
Indicates the relationship between the value of ission_indicator and the mode specified by them.

[0300] copy_permission_indicator is added to all transport packets. When recording the input transport stream using the IEEE1394 digital interface, the value of copy_permission_indicator is set to the value of EMI in the IEEE1394 isochronous packet header.
(Encryption Mode Indicator). When recording the input transport stream without using the IEEE1394 digital interface, copy_p
The value of ermission_indicator may be associated with the value of CCI embedded in the transport packet. Copy_permi when self-encoding analog signal input
The value of ssion_indicator may be associated with the value of CGMS-A of the analog signal.

Arrival_time_stamp is given by arrival_time_stamp (k) = arrival_time_clock (k)% 2
³⁰ is an integer having the value specified by arrival_time_stamp.

To define a Clip AV stream, a Clip
The AV stream is a DVR MPEG defined as described above.
-2 Must have a transport stream structure. arrival_time_clock (i) must increase continuously in the Clip AV stream. Even if a discontinuity point of the system time base (STC base) exists in the Clip AV stream, the arriv of the Clip AV stream
al_time_clock (i) must increase continuously.

[0303] The maximum value of the difference of arrival_time_clock (i) between the start and end of the Clip AV stream must be 26 hours. This restriction guarantees that the same PTS (Presentation Time Stamp) will not appear in the Clip AV stream if there is no discontinuity in the system time base (STC base) in the MPEG2 transport stream. I do. MPEG2 Systems Standard, P
The wraparound period of TS is 233/90000 seconds (about 26.5 hours).
It is prescribed.

To define a Bridge-Clip AV stream, the Bridge-Clip AV stream must have the structure of a DVR MPEG-2 transport stream defined as described above. The Bridge-Clip AV stream must include one arrival time base discontinuity point. Transport streams before and after the discontinuity point of the arrival time base must comply with the encoding restrictions described later, and must conform to the DVR-STD described later.

In the present embodiment, Pl in editing
Support video and audio seamless connection between ayItems. To make a seamless connection between PlayItems,
Guarantees "continuous supply of data" and "seamless decoding processing" to the player / recorder. "Continuous supply of data"
It is possible to guarantee that the file system supplies data at a required bit rate so as not to cause the decoder to underflow the buffer. The data is stored in contiguous blocks of a sufficient size so that the data can be read from the disk while guaranteeing the real-time property of the data.

[0306] "Seamless decoding processing" means that a player can display audio / video data recorded on a disc without causing a pause or a gap in the reproduction output of the decoder.

[0307] The AV stream referred to by the seamlessly connected PlayItems will be described. Preceding PlayItem
Whether or not the connection between the current PlayItem and the current PlayItem is guaranteed to be seamlessly displayed can be determined from the connection_condition field defined in the current PlayItem. Seamless connection between PlayItems
There are methods that use Bridge-Clip and methods that do not.

[0308] Fig. 96 shows the relationship between the preceding PlayItem and the current PlayItem when Bridge-Clip is used. In FIG. 96, stream data read by the player is shown with a shadow. TS shown in FIG. 96
1 is the stream data with the shadow of Clip1 (Clip AV stream) and RSPN_arrival_time_dis of Bridge-Clip
Consists of shaded stream data before continuity.

[0309] The stream data shaded by Clip1 of TS1 is the IN_time of the preceding PlayItem (I_time in FIG. 96).
This is stream data from the address of the stream necessary for decoding the presentation unit corresponding to N_time1) to the source packet referenced by RSPN_exit_from_previous_Clip. RSPN_arrival_time_discontinuity of Bridge-Clip included in TS1
The earlier shaded stream data is Bridge-C
From the first source packet of lip, RSPN_arrival_time_d
This is stream data up to the source packet immediately before the source packet referenced by iscontinuity.

Also, TS2 in FIG. 96 is Clip2 (Clip
AV stream) and the shaded stream data and B
It is composed of stream data shaded after RSPN_arrival_time_discontinuity of the ridge-Clip. The shaded stream data after RSPN_arrival_time_discontinuity of Bridge-Clip included in TS2 is RSPN_arrival
This is stream data from the source packet referenced by _time_discontinuity to the last source packet of the Bridge-Clip. The shaded stream data of Clip2 of TS2 is necessary for decoding the presentation unit corresponding to OUT_time (shown as OUT_time2 in FIG. 96) of the current PlayItem from the source packet referenced by RSPN_enter_to_current_Clip. Stream data up to the stream address.

[0311] Fig. 97 shows the relationship between the preceding PlayItem and the current PlayItem when Bridge-Clip is not used. In this case, the stream data read by the player is shaded. TS1 in FIG. 97 is C
It is composed of stream data with a shadow of lip1 (Clip AV stream). The shaded stream data of Clip1 of TS1 starts from the address of the stream necessary to decode the presentation unit corresponding to IN_time (shown as IN_time1 in FIG. 97) of the preceding PlayItem, and ends at the end of Clip1. Up to the source packet. Also, TS2 in FIG. 97 is Clip2
(Clip AV stream).

[0312] The shaded stream data of Clip2 of TS2 starts from the first source packet of Clip2, and is used to decode the presentation unit corresponding to OUT_time (shown as OUT_time2 in Fig. 97) of the current PlayItem. Is the stream data up to the stream address required.

In FIGS. 96 and 97, TS1 and T2 are continuous streams of source packets. Next, TS1
And TS2 stream specifications and connection conditions between them. First, consider the encoding restriction for seamless connection. As a limitation of the encoding structure of the transport stream, first, the number of programs included in TS1 and TS2 must be one. The number of video streams included in TS1 and TS2 must be one. The number of audio streams included in TS1 and TS2 must be 2 or less. The number of audio streams included in TS1 and TS2 must be equal. TS1 and / or TS2 may include an elementary stream or a private stream other than the above.

[0314] The limitation of the video bit stream will be described. FIG. 98 is a diagram illustrating an example of seamless connection in the picture display order. To be able to seamlessly display the video stream at the connection point, use OUT_time1
After (OUT_time of Clip1) and IN_time2 (IN_tim of Clip2)
Unnecessary pictures displayed before e) must be removed by the process of re-encoding the partial stream of Clip near the connection point.

In the case as shown in FIG.
An example of achieving a seamless connection using geSequence,
As shown in FIG. The video stream of Bridge-Clip before RSPN_arrival_time_discontinuity is Clip1 in FIG.
From the encoded video stream up to the picture corresponding to OUT_time1. Then, the video stream is connected to the video stream of the preceding Clip1, and is re-encoded so as to be one continuous elementary stream according to the MPEG2 standard.

Similarly, RSPN_arrival_time_disconti
The video stream of Bridge-Clip after nuity is shown in FIG.
Of the clip corresponding to IN_time2 of Clip2. Then, the video stream can start decoding correctly, and
Connected to Video stream of Clip2, MPE in one continuous
It has been re-encoded to be an elementary stream according to the G2 standard. In order to make a Bridge-Clip, generally, several pictures must be re-encoded, and other pictures can be copied from the original Clip.

In the case of the example shown in FIG. 98, BridgeSequence
FIG. 100 shows an example in which seamless connection is realized without using
Shown in The video stream of Clip1 is OUT_tim in FIG.
It consists of an encoded video stream up to the picture corresponding to e1, which has been re-encoded into one continuous elementary stream according to the MPEG2 standard. Similarly, the video stream of Clip2 is shown in FIG.
8 consisting of an encoded video stream after the picture corresponding to IN_time2 of Clip2, which is MPEG
It has been re-encoded to be an elementary stream according to the two standards.

[0318] To explain the encoding restriction of the video stream, first, the frame rates of the TS1 and TS2 video streams must be equal. The video stream of TS1 must end with sequence_end_code. The video stream of TS2 is Sequence Header, GO
Must start with P Header, and then I-picture. The TS2 video stream must start with a closed GOP.

A video presentation unit (frame or field) defined in a bit stream must be continuous across connection points. There must be no frame or field gaps at the connection points. At the point of attachment, the top-bottom field sequence must be continuous. 3-2 For encoding using pull-down, "top_field_f
The irst "and" repeat_first_field "flags may need to be rewritten, or may be locally re-encoded to prevent field gaps.

To explain the encoding restriction of the audio bit stream, the audio sampling frequencies of TS1 and TS2 must be the same. TS1 and TS2 audio encoding methods (eg MPEG1 Layer 2, AC-3, SESF
LPCM, AAC) must be the same.

Next, the encoding restriction of the MPEG-2 transport stream will be described. The last audio frame of the audio stream of TS1 is composed of audio samples having the same display time at the end of the display of the last display picture of TS1. Must include. The first audio frame of the TS2 audio stream is TS2
Must contain an audio sample with a display time equal to the start of the display of the first display picture of.

At the connection point, there must be no gap in the sequence of audio presentation units. As shown in FIG. 101, there may be an overlap defined by the length of an audio presentation unit less than two audio frame periods. The first packet transmitting the TS2 elementary stream is
Must be a video packet. The transport stream at the connection point must follow the DVR-STD described later.

To explain the limitations of Clip and Bridge-Clip, TS1 and TS2 must not include an arrival time base discontinuity in each.

[0324] The following restrictions apply only when Bridge-Clip is used. TS1 last source packet and TS2
Only at the point of attachment of the first source packet of the Bridge
-A ClipAV stream has only one arrival time base discontinuity. Defined in ClipInfo ()
RSPN_arrival_time_discontinuity indicates the address of the discontinuity, which must indicate the address referring to the first source packet of TS2.

Defined in BridgeSequenceInfo ()
The source packet referenced by RSPN_exit_from_previous_Clip may be any source packet in Clip1. It need not be the boundary of an Aligned unit. Br
RSPN_enter_to_ defined in idgeSequenceInfo ()
The source packet referenced by current_Clip is Cl
Any source packet in ip2 can be used. It is Align
It does not need to be the boundary of an ed unit.

[0326] To explain the limitation of PlayItem, OUT_time of the preceding PlayItem (OUT_time1 shown in Figs. 96 and 97) must indicate the display end time of the last video presentation unit of TS1.
The IN_time of the current PlayItem (IN_time2 shown in FIGS. 96 and 97) must indicate the display start time of the first video presentation unit of TS2.

With reference to FIG. 102, the limitation on data allocation when using a Bridge-Clip will be described. A seamless connection must be made so that continuous supply of data is guaranteed by the file system. This is Clip1 (ClipAV stream file) and C
Bridg connected to lip2 (Clip AV stream file)
It must be performed by arranging the e-Clip AV stream so as to satisfy the data allocation rules.

[0328] Clip before RSPN_exit_from_previous_Clip
The stream part of 1 (Clip AV stream file)
RSPN_exit_from_previous_Clip must be selected so that it is located in a continuous area equal to or greater than a half fragment. The data length of the Bridge-Clip AV stream is
It must be chosen so that it is located in a contiguous region of half a fragment or more. RSPN_enter_to_curren
RSPN_enter_to_current_Clip must be selected so that the stream portion of Clip2 (Clip AV stream file) after t_Clip is arranged in a continuous area of half fragment or more.

With reference to FIG. 103, a description will be given of the limitation of data allocation when seamless connection is performed without using Bridge-Clip. Seamless connection is made so that continuous supply of data is guaranteed by the file system. There must be. This is Clip1 (Clip AV
This has to be done by arranging the last part of the stream file) and the first part of Clip2 (Clip AV stream file) so as to satisfy the data allocation rules.

[0330] The last stream part of Clip1 (Clip AV stream file) must be arranged in a continuous area of half fragment or more. Clip2 (Clip AV
The first stream portion of the stream file) must be arranged in a continuous area of half a fragment or more.

Next, the DVR-STD will be described. DVR-STD
Is a conceptual model for modeling a decoding process when generating and verifying a DVR MPEG2 transport stream. The DVR-STD is also a conceptual model for modeling a decoding process at the time of generating and verifying an AV stream referred to by the two seamlessly connected PlayItems described above.

FIG. 104 shows the DVR-STD model. FIG.
The model shown in FIG. 4 includes a DVR MPEG-2 transport stream player model as a component.
n, TBn, MBn, EBn, TBsys, Bsys, Rxn, Rbxn, Rxsys, D
The notation of n, Dsys, On and Pn (k) is ISO / IEC13818-1
It is the same as that defined in T-STD. That is, it is as follows. n is the index number of the elementary stream. TBn is a transport buffer for the elementary stream n.

MBn is a multiplex buffer for elementary stream n. Only present for video streams. EBn is an elementary stream buffer for the elementary stream n. Only present for video streams. TBsys is an input buffer for system information of the program being decrypted. Bsys is the main buffer in the system target decoder for the system information of the program being decoded. Rxn is the transmission rate at which data is removed from TBn. Rbxn, PES
The transmission rate at which the packet payload is removed from MBn. Only present for video streams.

Rxsys is the transmission rate at which data is removed from TBsys. Dn is the elementary stream n
Decoder. Dsys is a decoder for the system information of the program being decoded. On is the re-ordering buffer of the video stream n. Pn (k) is the k-th presentation unit of the elementary stream n.

[0335] The decoding process of DVR-STD will be described. While playing a single DVR MPEG-2 transport stream, transport packets are transferred to TB1,
The timing to input to the buffer of TBn or TBsys is
Determined by arrival_time_stamp of the source packet. The specification of buffering operation of TB1, MB1, EB1, TBn, Bn, TBsys and Bsys is the same as T-STD specified in ISO / IEC 13818-1. The definition of the decoding operation and the display operation is also the same as T-STD defined in ISO / IEC 13818-1.

[0336] The decoding process during playback of a seamlessly connected PlayItem will be described. Here, reproduction of two AV streams referred to by seamlessly connected PlayItems will be described. In the following description, reproduction of the above-described TS1 and TS2 (for example, shown in FIG. 96) will be described. TS1 is the preceding stream, and TS2 is the current stream.

[0337] Fig. 105 shows a case where one AV stream (TS1) is seamlessly connected to the next AV stream (TS1).
A timing chart of input, decoding, and display of a transport packet when the process proceeds to 2) is shown. From a given AV stream (TS1) to the next AV seamlessly connected to it
During the transition to the stream (TS2), the time axis of the arrival time base of TS2 (denoted by ATC2 in FIG. 105) is changed to the time axis of the arrival time base of TS1 (FIG. 1).
05 as indicated by ATC1).

Also, the time axis of the system time base of TS2 (indicated by STC2 in FIG. 105) is not the same as the time axis of the system time base of TS1 (indicated by STC1 in FIG. 105). Video display is required to be seamlessly continuous. The display time of the audio presentation unit may overlap.

[0339] The input timing to the DVR-STD will be described. Time to time T _1, that is, until the last video packet of TS1 is input ends TB1 of DVR-STD is, DVR-
The input timing of the STD to the buffer of TB1, TBn or TBsys is determined by arrival_time_stamp of the source packet of TS1.

The remaining packets of TS1 are TS_recording_ra
It must be input to the buffer of TBn or TBsys of DVR-STD at the bit rate of te (TS1). Where TS_recor
ding_rate (TS1) is a value of TS_recording_rate defined in ClipInfo () corresponding to Clip1. The time at which the last byte of TS1 enters the buffer is time T2. Thus, in a section from time T ₁ to T _2, arrival_time_stamp of the source packet is ignored.

N1 is the TS1 following the last video packet of TS1.
Is the number of bytes of the transport packet at time T
₁ to time DT1 of up to T ₂ is, N1 byte is TS_recording_ra
This is the time required to complete input at the bit rate of te (TS1) and is calculated by the following equation. _{ΔT1 = T 2 -T 1 = N1} / TS_recording_rate (TS1) the time T ₁ to until T ₂ are the values of RXn and RXsys together, TS
Changes to the value of _recording_rate (TS1). The buffering operation other than this rule is the same as T-STD.

At time T ₂ , arrival time clock
counter is arrival_time of the first source packet of TS2
Reset to the value of _stamp. The input timing to the buffer of TB1, TBn or TBsys of DVR-STD is determined by arrival_time_stamp of the source packet of TS2. RX
Both n and RXsys change to the values defined in T-STD.

[0343] By way of explaining additional audio buffering and system data buffering, the audio decoder and the system decoder, from time T ₁
To be able to process the input data section of up to T _2, additional buffer amount in addition to the buffer amount defined in T-STD (approximately 1 second of data amount) is needed.

To illustrate the video presentation timing, the presentation of the video presentation unit must be continuous through the connection points without gaps. Here, STC1 is a time axis of the system time base of TS1 (shown as STC1 in FIG. 105).
STC2 is a time axis of the system time base of TS2 (illustrated as STC2 in FIG. 97. To be precise, STC2
Starts from the time when the first PCR of TS2 enters the T-STD. ).

The offset between STC1 and STC2 is determined as follows. PTS ¹ _end is the PTS on STC1 corresponding to the last video presentation unit of TS1,
² _{sta rt} is the PTS on STC2 corresponding to the first video presentation unit of TS2, and T _pp is the offset STC_ between the two system time bases, given the display period of the last video presentation unit of TS1.
delta is calculated by the following equation. STC_delta = PTS ¹ _end + T _pp -PTS ² _start

To illustrate the timing of audio presentation, at the connection point, there may be an overlap in the presentation timing of the audio presentation units, which is less than 0 to 2 audio frames (shown in FIG. 105). audio o
verlap "). Which audio sample to select and resynchronizing the presentation of the audio presentation unit to the corrected time base after the splice point is set by the player. .

[0347] By way of explaining the system time clock of DVR-STD, at time T _5, the last audio presentation unit of TS1 is displayed. System time clock may be from time T ₂ not overlap between T _5. In this section, the DVR-STD switches the system time clock between the old time base value (STC1) and the new time base value (STC2). STC2
Is calculated by the following equation. STC2 = STC1-STC_delta

The continuity of buffering will be described. _STC1 ¹ _{video_end} is the value of STC on the system time base STC1 when the last byte of the last video packet of TS1 arrives at TB1 of DVR-STD. _STC2 ² _{video_start}
Means that the first byte of the first video packet of TS2 is DVR-S
S on the system time base STC2 when arriving at TB1 of TD
This is the TC value. _STC2 ¹ _{video_end} is a value obtained by _converting the value of _STC1 ¹ _{video_end into} a value on system time base _STC2 . _STC2 ¹ video_end is calculated by the following equation. ^{_{STC2 1 video_end = STC1 1 video_end -}} STC_delta

In order to comply with the DVR-STD, it is required to satisfy the following two conditions. First, the arrival timing of the first video packet of TS2 at TB1 must satisfy the following inequality. Then, the following inequality must be satisfied. _STC2 ² _{video_start} > _STC2 ¹ _{video_end} + ΔT1 If it is necessary to re-encode and / or re-multiplex the partial stream of Clip1 and / or _Clip2 so that this inequality is satisfied, Done.

Next, on the time axis of the system time base obtained by converting STC1 and STC2 on the same time axis, the input of a video packet from TS1 and the subsequent input of a video packet from TS2 overflow the video buffer and Do not underflow.

[0351] Based on such syntax, data structure, and rules, it is possible to appropriately manage the contents of data recorded on the recording medium, reproduction information, and the like. The user can confirm the contents of the data recorded in the file, and can easily reproduce the desired data.

In the present embodiment, an MPEG2 transport stream has been described as an example of a multiplexed stream. However, the present invention is not limited to this, and is used in an MPEG2 program stream or a DirecTV service (trademark) in the United States. D
It is also possible to apply to the SS transport stream.

Next, mark_entry () and representative
FIG. 106 shows a process in which the beginning of the scene indicated by the mark point is reproduced when the syntax of _picture_entry () has a configuration as shown in FIG.
This will be described with reference to the flowchart of FIG.

First, in step S 1, the control unit 23 of the recording / reproducing apparatus 1 reads the EP_M, which is the data database of the DVR transport stream file, from the recording medium 100.
ap (FIG. 70), STC_Info (FIG. 52), Program_Info (FIG. 54), and ClipMark (FIG. 78) are read.

At step S2, the control unit 23
A list of thumbnails is created from the pictures referenced by the representative_picture_entry (FIG. 81) of ipMark (FIG. 81) or ref_thumbnail_index, output from the terminal 24 as a user interface input / output, and displayed on the GUI menu screen. In this case, ref_thumbnail_
If index has a valid value, representative_picture_
ref_thumbnail_index has priority over entry.

[0356] In step S3, the user designates a mark point as a reproduction start point. This is performed, for example, when the user selects a thumbnail image from a menu screen displayed as a GUI. The control unit 23 acquires a mark point associated with the specified thumbnail in response to the selection operation.

[0357] In step S4, the controller 23 sets the mark_t of the mark_entry (Fig. 81) specified in step S3.
Get PTS of ime_stamp and STC_sequence_id.

At step S5, the control unit 23
The STC_se obtained in step S4 from C_Info (FIG. 52)
The source packet number at which the STC time axis corresponding to quence_id starts is obtained.

In step S6, the control unit 23 sets the packet number at which the STC time axis obtained in step S5 starts and the PTS of the mark point obtained in step S4 in time before the PTS of the mark point, and , The source packet number having the nearest entry point (I picture) is obtained.

[0360] In step S7, the control unit 23 reads the transport stream data from the source packet number having the entry point acquired in step S6, and supplies the data to the AV decoder 27.

At step S8, the control unit 23
The decoder 27 is controlled to start displaying from the PTS picture of the mark point acquired in step S4.

The above operation will be further described with reference to FIGS.

Now, as shown in FIG. 107, the DV
R transport stream file is STC_sequence_
It has an STC time axis of id = id0, and the source packet number at which the time axis starts is smaller than the source packet number of the scene start point A. It is assumed that a commercial (CM) is inserted between the source packet numbers B and C.

At this time, in the EP_Map corresponding to the EP_Map shown in FIG. 70, as shown in FIG. 108, the RSPN_EP_
Each PTS corresponding to A, B, C indicated by start
Are registered as PTS_EP_start as PTS (A), PTS (B), and PTS (C).

As shown in FIG. 109, FIG.
As shown in FIG. 109, mark types (FIG. 79) 0x92, 0x94, 0 representing a scene start, a CM start, and a CM end
mark_entry and representative_pi corresponding to the value of x95
cture_entry is recorded.

As Mark_Time_stamp of mark_entry,
PTS (a1), PTS (b0), and PTS (c0) are registered corresponding to the scene start, the CM start, and the CM end, respectively, and each of the STC_sequence_id is set to id0.

Similarly, the representation_picture_entry
Mark_Time_stamp is PTS (a2), PTS respectively corresponding to scene start, CM start, and CM end.
(b0) and PTS (c0) are registered, and they are all STC_
sequence_id is set to id0.

If PTS (A) <PTS (a1), the packet number A is obtained in step S6, the transport stream starting from the packet number A is supplied to the AV decoder 27 in step S7, and in step S8 , PTS (a1) starts display.

Next, with reference to the flowchart of FIG. 110, CM skip reproduction processing in the case where the syntax of mark_entry and representative_picture_entry has a configuration as shown in FIG. 81 will be described with reference to the flowchart of FIG. 110. I do.

In step S21, the control unit 23
EP_map (FIG. 70), STC_Info (FIG. 52), Program_Info
(FIG. 54) and ClipMark (FIG. 78) on the recording medium 10.
Read from 0. In step S22, the user
CM skip reproduction is designated from a terminal 24 as a user interface input / output.

In step S23, the control unit 23
The PTS of the mark information whose mark type (FIG. 79) is the CM start point (0x94), the PTS of the mark information whose CM end point is (0x95), and the corresponding STC_sequence_id are acquired (FIG. 81).

At step S24, the control unit 23
STC_sequ of CM start point and end point from STC_Info (FIG. 52)
Get the source packet number where the STC time axis corresponding to ence_id starts.

In step S25, the control unit 23
The transport stream is read from the recording medium 100, supplied to the AV decoder 27, and decoding is started.

At step S26, the control unit 23
It is checked whether the current display image is a PTS image at the CM start point. If the current display image is not the image of the PTS at the CM start point, the process proceeds to step S27, and the control unit 23 continues to display the image. Thereafter, the process returns to step S25, and the subsequent processes are repeatedly executed.

If it is determined in step S26 that the current display image is the PTS image at the CM start point, the process proceeds to step S28, where the control unit 23 controls the AV decoder 27 to stop decoding and displaying. .

Next, in step S29, the control unit 2
3 obtains a packet number at which the STC time axis corresponding to the STC_sequence_id of the CM end point starts, and obtains a time difference from the PTS of that point based on the packet number and the PTS of the CM end point obtained in the process of step S23. And the source packet number with the closest entry point.

At step S30, the control unit 23
The data of the transport stream is read from the source packet number having the entry point acquired in the process of step S29, and supplied to the AV decoder 27.

At step S31, the control unit 23
The AV decoder 27 is controlled to restart the display from the picture of the PTS at the CM end point.

The above operation will be further described with reference to FIGS. 107 to 109. In this example, the CM start point and the CM end point exist on a common STC time axis of STC_sequence_id = id0. The source packet number at which the STC time axis starts is smaller than the source packet number A at the start point of the scene.

[0380] If the transport stream is decoded and it is determined in step S26 that the display time has reached PTS (b0) (if it has been determined that it is the CM start point),
The display is stopped by the AV decoder 27. And PTS
If (C) <PTS (c0), the packet number C
The decoding is restarted from the stream starting from the data of the above, and in step S31, the display is restarted from the picture of PTS (c0).

Note that this method is applicable not only to CM skip reproduction but also to reproduction in which a scene between two points specified by ClipMark is generally skipped.

Next, mark_entry and representative_pictu
With reference to the flowchart in FIG. 112, a description will be given, with reference to the flowchart in FIG. 112, of the process of searching for a CM indicated by a mark point when re_entry has the syntax structure shown in FIG.

In step S41, the control unit 23
EP_map (FIG. 70), STC_Info (FIG. 52), Program_Info
(FIG. 54) and ClipMark (FIG. 78) information.

Next, in step S42, the control unit 23
Generates a list of thumbnails from the pictures referenced by the representative_picture_entry (FIG. 82) or the ref_thumbnail_index included in the ClipMark (FIG. 78) read in step S41, and displays the thumbnail list on the menu screen of the GUI. If ref_thumbnail_index has a valid value, ref_thumbnail_
index takes precedence.

[0385] In step S43, the user specifies a mark point of a reproduction start point. This designation is performed, for example, by the user selecting a thumbnail image from the menu screen displayed in the process of step S42 and designating a mark point associated with the thumbnail.

In step S44, the control unit 23
RSPN_ref of the mark point specified in the processing of step S43
_EP_start and offset_num_pictures (FIG. 82) are obtained.

[0387] In step S45, the control unit 23
The data of the transport stream is read from the source packet number corresponding to RSPN_ref_EP_start obtained in step S44, and supplied to the AV decoder 27.

At step S46, the control unit 23
The AV decoder 27 is controlled, and the picture to be displayed is counted up from the picture referenced by RSPN_ref_EP_start (not displayed), and the count value becomes offset_n
When it becomes um_pictures, display is started from that picture.

The above processing will be further described with reference to FIGS. 113 to 115. In this example, the scene starts from the source packet number A in the DVR transport stream file, and CMs are inserted from the source packet number B to the source packet C. Therefore, as shown in FIG. 114, the EP_map includes the RSPN_EP_
PTS (A), PTS (B), and PTS (C) are registered as PTS_EP_start corresponding to A, B, and C as start.

Also, as shown in FIG. 115, mark_entry and representative_picture_ent correspond to the mark types of scene start, CM start, and CM end.
ry is registered. mark_entry contains RSPN_ref corresponding to the scene start, CM start, and CM end.
A, B, and C are registered as _EP_start, and off
M1, N1, and N2 are registered as set_num_pictures. Similarly, representative_picture_entry contains
A, B, and C are registered as RSPN_ref_EP_start corresponding to a scene start, a CM start, and a CM end, respectively, and M2, N1, as offset_num_pictures.
N2 are registered.

When playback is instructed starting from the picture corresponding to the scene start, decoding is started from the stream starting from the data of packet number A, and the picture to be displayed (without display) is started from the picture of PTS (A). Count up, offset_num_pictures,
When the value of M1 is reached, display is started from the picture.

Further, mark_entry and representative_pic
FIG. 11 shows the CM skip reproduction process when the syntax of the “ture_entry” has the configuration shown in FIG.
This will be described with reference to the flowchart of FIG.

In step S61, the control unit 23
EP_map (FIG. 70), STC_Info (FIG. 52), Program_Info
(FIG. 54) and ClipMark (FIG. 78) information.

[0394] In step S62, when the user instructs CM skip reproduction, in step S63, the control unit 23 sets RSPN_ref_EP_START as mark information of each point whose mark type (FIG. 79) is the CM start point and the CM end point.
And offset_num_pictures (FIG. 82). The data at the CM start point is RSPN_ref_EP_start (1), offse
t_num_pictures (1), and the data at the CM end point is RSPN_pictures.
ref_EP_start (2) and offset_num_pictures (2).

In step S64, the control unit 23
The PTS corresponding to RSPN_ref_EP_start (1) and RSPN_ref_EP_start (2) is acquired from EP_map (FIG. 70).

In step S65, the control unit 23
The transport stream is read from the recording medium 100 and supplied to the AV decoder 27.

At step S66, the control unit 23
PTS whose current display image corresponds to RSPN_ref_EP_start (1)
It is determined whether the current picture is RS
If the picture is not a PTS picture corresponding to PN_ref_EP_start (1), the process proceeds to step S67, and the picture is continuously displayed as it is. Thereafter, the process returns to step S65, and the subsequent processes are repeatedly executed.

If it is determined in step S66 that the current display image is a PTS picture corresponding to RSPN_ref_EP_start (1), the flow advances to step S68 to execute control unit 2
3 controls the AV decoder 27, and RSPN_ref_EP_start (1)
The picture to be displayed is counted up from the picture of the PTS corresponding to, and the count value is offset_num_picture.
Stops the display when s (1) is reached.

At step S69, the control unit 23
The data of the transport stream is read from the source packet number of RSPN_ref_EP_start (2),
7 is supplied.

In step S70, the control unit 23
The AV decoder 27 is controlled to count up the picture to be displayed (without display) from the picture of the PTS corresponding to RSPN_ref_EP_start (2), and the count value becomes offs
When et_num_pictures (2) is reached, display starts from that picture.

The above operation will be further described with reference to FIGS. 113 to 115. First, based on the EP_map (FIG. 114), the times PTS (B) and PTS corresponding to the packet numbers B and C are determined.
(C) is obtained. When the Clip AV stream is decoded and the display time reaches PTS (B), the display picture is counted up from the picture of PTS (B), and when the value becomes N1 (FIG. 115), The display is stopped.

[0402] Further, decoding is restarted from the stream starting from the data of the packet number C, and the pictures to be displayed are counted up (not displayed) from the picture of the PTS (C), and the value is set to N2 (Fig. 115). ), The display is restarted from the picture.

The above processing is not limited to CM skip reproduction,
The present invention is also applicable to a case where a scene between two points designated by ClipMark is skipped and reproduced.

Next, mark_entry and representative_pictu
With reference to the flowchart of FIG. 118, a description will be given, with reference to the flowchart of FIG. 118, of the process of searching for the beginning of a scene indicated by a mark point when the syntax of re_entry has the configuration shown in FIG.

In step S81, the EP_map (FIG. 7)
0), STC_Info (FIG. 52), Program_Info (FIG. 54),
In addition, information of ClipMark (FIG. 78) is obtained.

[0406] In step S82, the control unit 23
A list of thumbnails is generated from the pictures referenced by the representative_picture_entry or ref_thumbnail_index of ClipMark (FIG. 78) and displayed as a GUI menu screen. If ref_thumbnail_index has a valid value, ref_thumbnai from representative_picture_entry
l_index has priority.

[0407] In step S83, the user specifies a mark point of the reproduction start point. For example, the user selects a thumbnail image from the menu screen,
This is performed by designating a mark point associated with the thumbnail.

[0408] In step S84, the control unit 23
RSPN_mark_point of mark_entry specified by user
(FIG. 84).

[0409] In step S85, the control unit 23
The source packet number of the entry point that is before the RSPN_mark_point of the mark point and is the closest is EP_m
ap (FIG. 70).

[0410] In step S86, the control unit 23
The transport stream data is read from the source packet number corresponding to the entry point acquired in step S85, and supplied to the AV decoder 27.

[0411] In step S87, the control unit 23
The AV decoder 27 is controlled to start displaying from the picture referenced by the RSPN_mark_point.

[0412] The above processing will be further described with reference to Figs. In this example, the DVR transport stream file starts a scene with a source packet A, and CMs from source packet numbers B to C are inserted. For this reason, the EP_map in FIG.
PTS_EP_st corresponding to A, B, and C as PN_EP_start
art is registered as PTS (A), PTS (B), PTS (C), respectively. In addition, mark corresponding to the scene start, the CM start, and the CM end is added to the ClipMark shown in FIG.
As the RSPN_mark_point of the entry, a1, b1, c1 are:
Also, RSPN_mark_poin of representative_picture_entry
a2, b1, and c1 are registered as t.

[0413] In the case of starting playback from the picture corresponding to the scene start, if packet number A <a1, decoding starts from the stream starting from the data of packet number A, and display starts from the picture corresponding to source packet number a1. You.

Next, mark_entry and representative_pictu
With reference to the flowcharts of FIGS. 122 and 123, a description will be given of the CM skip reproduction process in the case where the syntax of re_entry has a configuration as shown in FIG.

[0415] In step S101, the control unit 23
Are EP_map (FIG. 70), STC_Info (FIG. 52), Program_
Info (FIG. 54) and ClipMark (FIG. 70) information are acquired.

[0416] In step S102, the user sets the CM
Specify skip playback.

[0417] In step S103, the control unit 23
Acquires the RSPN_mark_point (FIG. 84) of the mark information of each mark whose mark type (FIG. 79) is the CM start point and the CM end point. Then, the control unit 23 sends the data of the CM start point to the RS
PN_mark_point (1) and CMPN end point data is RSPN_ma
Let it be rk_point (2).

[0418] In step S104, the control unit 23
Causes the transport stream to be read from the recording medium 100, output to the AV decoder 27, and decoded.

[0419] In step S105, the control unit 23
Determines whether the current display image is a picture corresponding to RSPN_mark_point (1) and determines whether the current display image is RSPN_mark_point (1).
If the picture does not correspond to PN_mark_point (1), the process proceeds to step S106, and the picture is continuously displayed as it is. Thereafter, the process returns to step S104, and the subsequent processes are repeatedly executed.

[0420] If it is determined in step S105 that the current display image is a picture corresponding to the RSPN_mark_point (1), the flow advances to step S107, and the control unit 2
3 controls the AV decoder 27 to stop decoding and display.

Next, in step S108, RSPN_m
The source packet number before ark_point (2) and having the nearest entry point is EP_map (FIG. 7).
0).

At step S109, control unit 23
Reads the data of the transport stream from the source packet number corresponding to the entry point acquired in step S108, and supplies the data to the AV decoder 27.

[0423] In step S110, the control unit 23
Controls the AV decoder 27 and RSPN_mark_point (2)
The display is restarted from the picture referenced by.

The above processing will be further described with reference to the examples of FIGS. 119 to 121. When the Clip AV stream is decoded and the display picture corresponding to the source packet number b1 (FIG. 121) is displayed, the display is stopped. You. And
If the source packet number C is smaller than the source packet number c1, the decoding is restarted from the stream starting from the data of the packet number C, and when the picture corresponding to the source packet number c1 is reached, the display is restarted from the picture.

[0425] As described above, as shown in Fig. 124, a predetermined position is designated by the time stamp on the PlayList, and this time stamp is set to the Clip Informa of each Clip.
is converted to a data address in the Clip AV stre
am able to access a given location.

More specifically, as shown in FIG. 125, when a user designates a bookmark or a resume point as a PlayListMark on a PlayList as a time stamp on a time axis, the PlayList is reproduced at the time of reproduction.
Using the ClipMark of the Clip referenced by the PlayList, the scene start point and scene end point of the Clip AV stream can be accessed.

Note that the syntax of ClipMark can be as shown in FIG. 126 instead of the example of FIG.

In this example, RSPN_mark is
Reserved_for_MakerID, mark_entry (), and repr
Inserted instead of esetative_picture_entry (). The 32-bit field of the RSPN_mark indicates the relative address of the source packet including the first byte of the access unit referred to by the mark on the AV stream file. The RSPN_mark has a size in units of source packet numbers, is defined in the Clip Information file from the first source packet of the AV stream file, and is counted using the value of offset_SPN as an initial value.

The other structures are the same as those in FIG.

The syntax of ClipMark is further shown in FIG.
It can also be configured as shown in FIG. In this example, instead of RSPN_mark in FIG. 126, RSPN_ref_
EP_start and offset_num_pictures are inserted. These are the same as those shown in FIG.

FIG. 128 shows a case where the analog AV signal is encoded and recorded, and the syntax Clip shown in FIG. 81 is used.
6 is a flowchart illustrating creation of a Mark. This will be described with reference to the block diagram of the recording / reproducing apparatus 1 in FIG. In step S200, the analysis unit 14 determines that the terminal 1
By analyzing the input AV signals from 1 and 12, feature points are detected. The characteristic point specifies a characteristic scene caused by the contents of the AV stream, and is, for example, a head point of a program or a scene change point.

[0432] In step S201, the control unit 23 acquires the PTS of the image of the feature point. In step S202, the control unit 23 stores feature point information in ClipMark. Specifically, the information described in the syntax and semantics of ClipMark of the present embodiment is stored. In step S203, the Clip Information file and the Clip
p AV stream file is recorded on the disc.

[0433] Fig. 129 is a flowchart for describing creation of a ClipMark of the syntax shown in Fig. 81 when recording a transport stream input from the digital interface. This will be described with reference to the block diagram of the recording / reproducing apparatus 1 in FIG. Step S2
At 11, the demultiplexer 26 and the control unit 23 obtain the elementary stream PID of the program to be recorded. When there are a plurality of elementary streams to be analyzed, all the elementary streams PID
Is obtained.

[0434] In step S212, the demultiplexer 2
6 separates an elementary stream from a transport stream program input from the terminal 13,
The AV decoder 27 decodes it into an AV signal. In step S213, the analysis unit 14 analyzes the AV signal and detects a feature point.

In step S214, control unit 23
Is the PTS of the image of the feature point and the ST of the STC to which it belongs.
Get C-sequence-id. In step S215, the control unit 23 stores the feature point information in the ClipMark. Specifically, the information described in the syntax and semantics of ClipMark in the present embodiment is stored.

[0436] In step S216, Clip Informa
The Action file and Clip AV stream file are recorded on the disc.

As shown in the flowchart of FIG. 128 and the flowchart of FIG.
A ClipMark that stores a mark indicating a characteristic image in a V stream file, that is, a Clip AV stream file, is recorded in the management information data file of the AV stream, that is, a Clip Information file.

[0438] Fig. 130 is a flowchart illustrating the creation of a Real PlayList. This will be described with reference to the block diagram of the recording / reproducing apparatus 1 in FIG. Step S2
At 21, the control unit 23 records a Clip AV stream. In step S222, the control unit 23
A PlayList () including PlayItems covering the entire playable range of the Clip is created. If there is an STC discontinuity point in the Clip and PlayList () consists of two or more PlayItems,
The connection_condition between PlayItems is also determined.

In step S223, the control unit 23
Creates UIAppInfoPlayList (). Step S22
In 4, the control unit 23 creates a PlayListMark.
In step S225, the control unit 23 sets the MakersPriv
Create ateData. In step S226, the control unit 23 records a Real PlayList file.

[0440] In this way, each time a new Clip AV stream is recorded, one Real PlayList file is created.

FIG. 131 is a flowchart for explaining the creation of a Virtual PlayList. Step S231
In, reproduction of one Real PlayList recorded on the disc is designated through the user interface. Then, from the reproduction range of the Real PlayList, a reproduction section indicated by an IN point and an OUT point is specified through a user interface.

[0442] In step S232, the control unit 23
Determines whether or not all the operation of designating the reproduction range by the user has been completed. If it is determined in step S232 that the user has not completed the reproduction range designating operation, the process returns to step S231, and the subsequent processes are repeated.
Proceed to 233.

In step S233, the connection state (connection_cond
) is determined by the user through the user interface or by the control unit 23. In step S234, the user specifies the sub-path (audio for dubbing) information through the user interface. If the user does not create a sub-pass, the process in step S234 is skipped.

[0444] In step S235, the control unit 23
Is the playback range information specified by the user, and connection
Create PlayList () based on _condition. In step S236, the control unit 23 sets the UIAppInfoPlayLis
Create t (). In step S237, the control unit 2
3 creates a PlayListMark. In step S238, the control unit 23 creates MakersPrivateData.
In step S239, the control unit 23
Record the ayList file on the disc.

[0445] In this way, the user selects a playback section to be viewed from the playback range of the Real PlayList recorded on the disc, and for each of the playback sections grouped, one Virtual PlayList file. Is created.

[0446] Fig. 132 is a flowchart for describing the reproduction of the PlayList. This will be described with reference to the block diagram of the recording / reproducing apparatus 1 in FIG. In step S241, the control unit 23 sets the Info.dvr, Clip Information f
ile, PlayList file and thumbnail file information are obtained, a GUI screen showing a list of PlayLists recorded on the disc is created, and displayed on the GUI through the user interface.

[0447] In step S242, the user instructs the control unit 23 to reproduce one PlayList through the user interface. In step S243, the control unit 23 sets the STC-sequence-id and IN_ti of the current PlayItem.
From the PTS of me, the source packet number having the closest entry point in time before IN_time is obtained. In step S244, the control unit 23 reads the data of the AV stream from the source packet number having the entry point and supplies the data to the AV decoder 27.

[0448] If the PlayItem has been reproduced temporally before the PlayItem, the control unit 2 proceeds to step S245.
No. 3 indicates connection processing for display with the PlayItem in connection_c
Control is performed so as to be performed according to the ondition. In step S246, the AV decoder 27 starts display from the PTS picture of IN_time.

[0449] In step S247, the AV decoder 27 continuously decodes the AV stream. In step S248, the control unit 23 determines whether the currently displayed image is a PTS image of OUT_time. If it is determined in step S248 that the currently displayed image is a PTS image of OUT_time, the process proceeds to step S25.
0, and if it is determined that the image is not a PTS image, the process proceeds to step S249.

In step S249, processing for displaying an image determined to be a PTS image is performed, and thereafter, the flow returns to step S247, and the subsequent processing is repeated. On the other hand, in step S250, the control unit 23 determines whether the current PlayItem is the last PlayItem in the PlayList. In step S250, the current PlayItem is the last PlayItem in the PlayList.
132, the process of the flowchart shown in FIG. 132 is terminated, and if it is determined that the PlayItem is not the last PlayItem, the process returns to step S243, and the subsequent processes are repeated.

[0451] Fig. 133 is a flowchart for describing the creation of a PlayListMark. Recording / reproducing apparatus 1 of FIG.
This will be described with reference to the block diagram of FIG. Step S26
1, the control unit 23 sets the Info.dvr, Clip Informati
The information of on file, PlayList file and Thumbnail file is acquired, a GUI screen showing a list of PlayLists recorded on the disc is created, and displayed on the GUI through the user interface.

[0452] In step S262, the user instructs the control unit 23 to reproduce one PlayList through the user interface. In step S263, the reproduction unit 3 starts reproduction of the instructed PlayList (performed as described with reference to the flowchart in FIG. 132).

In step S264, the user instructs the control unit 23 to set a mark at a favorite scene through the user interface. In step S265, the control unit 23 acquires the PTS of the mark and the PlayItem_id of the PlayItem to which the mark belongs.

In step S266, control unit 23
Stores mark information in PlayListMark (). In step S267, the PlayList file is recorded on the disc.

[0455] As described above, the mark point designated by the user from the reproduction range of the PlayList or the PlayList
To store the mark indicating the Resume point when playing
ayListMark is recorded in the PlayList file.

FIG. 134 shows that when the PlayList is reproduced, Pl
ayListMark and ClipMa of Clip referenced by its PlayList
It is a flowchart explaining head reproduction | regeneration which used rk. The syntax of ClipMark () is shown in FIG. This will be described with reference to the block diagram of the recording / reproducing apparatus 1 in FIG.

In step S271, the control unit 23
Is Info.dvr, Clip Information file, PlayList file
And Thumbnail file information, create a GUI screen showing a list of PlayLists recorded on the disc,
Display on GUI through user interface.

[0458] In step S272, reproduction of one PlayList is instructed by the user through the user interface. In step S273, the control unit 2
3 is a PlayListMark and the PlayList refers to
Through the user interface, a list of thumbnails generated from the pictures referenced by Clip's ClipMark
Display on GUI.

[0459] In step S274, a mark point of a reproduction start point is designated by the user to the control unit 23 through the user interface. In step S275, the control unit 23 determines whether the mark selected in the processing in step S274 is a mark stored in PlayListMark. If it is determined in step S275 that the selected mark is a mark stored in PlayListMark, the process proceeds to step S276,
If it is determined that the mark is not stored, the process proceeds to step S278.

[0460] In step S276, control unit 23
Acquires the PTS of the mark and the PlayItem_id to which it belongs. In step S277, the control unit 23
STC of AV stream referred to by PlayItem indicated by Item_id
Get -sequence-id.

At step S278, control unit 23
Is based on the STC-sequence-id and the PTS of the mark,
The V stream is input to the AV decoder 27. Specifically, using the STC-sequence-id and the PTS of the mark point,
Steps S243 and S24 in the flowchart of FIG. 132
The same processing as in No. 4 is performed. In step S279, the reproducing unit 3 starts displaying from the PTS picture of the mark point.

[0462] As described with reference to FIG.
Is played, the ClipMa of the Clip referenced by the PlayList
You can refer to the mark stored in rk. Therefore, one Clip is transferred to Real PlayList or multiple Virtual P
If referenced by layList, their PlayList
Can share the ClipMark of the one Clip, so that mark data can be managed efficiently.

[0466] If ClipMark is not defined for Clip, Pl
If a combination of PlayListMark and ClipMark is defined only for ayList, one Clip
Are referred to by Real PlayList or multiple Virtual PlayLists, each PlayList has the same Clip
, And the efficiency of data recording is low.

[0464] Fig. 135 is a diagram illustrating another example of the syntax of PlayListMark (). length indicates the number of bytes from the byte immediately after this length field to the last byte of PlayListMark (). number_of_PlayList_marks is Pl
Indicates the number of mark entries stored in ayListMark.

Mark_invalid_flag is a 1-bit flag, and when its value is set to zero, it indicates that this mark has valid information. When its value is set to 1, Indicates that this mark is invalid.

[0466] When the user performs an operation of deleting an entry of one mark on the user interface, the recording / reproducing apparatus 1 replaces the mark entry with the mark_invalid_flaa instead of deleting the mark entry from the PlayListMark.
The value of g may be changed to 1.

[0467] mark_type indicates the type of mark, and has the meaning shown in FIG. mark_name_length is Mark_n
Indicates the byte length of the mark name shown in the ame field. The value of this field is 32 or less. ref_to_PlayI
The tem_id indicates the value of PlayItem_id that specifies the PlayItem where the mark is placed. A PlayItem
Is defined in PlayList ().

[0468] The mark_time_stamp stores a time stamp indicating the point at which the mark is specified. mark
_time_stamp is PlayIte indicated by ref_to_PlayItem_id
Indicates the time within the playback range specified by IN_time and OUT_time as defined in m. The meaning of the time stamp is the same as in FIG.

When entry_ES_PID is set to 0xFFFF, the mark is a pointer on the time axis common to all elementary streams used by the PlayList. If entry_ES_PID is set to a value other than 0xFFFF, entry_ES_PID indicates the value of the PID of the transport packet containing the elementary stream pointed to by the mark.

[0470] ref_thumbnail_index indicates information of a thumbnail image added to a mark. The meaning is shown in FIG.
Same as ref_thumbnail_index. mark_name indicates the name of the mark. Mark_n from left in this field
The number of bytes indicated by ame_length is a valid character character and indicates a name. This character character is UI
It is encoded in the method indicated by character_set in AppInfoPlayList.

In the mark_name field, any value may be entered as the value of the byte following the valid character characters. In this syntax, the mark can point to a specific elementary stream. For example, when a PlayList refers to a multi-view program with multiple video streams in the program,
entry_ES_PID is used to set a video PID indicating one video stream in the program.

[0472] It is assumed that the user is playing a PlayList that refers to the multi-view program, and that the user is viewing one of the multi-views. Now, it is assumed that the user has sent a command to the recording / reproducing apparatus 1 to skip the reproduction to the next mark point. In this case, the recording / reproducing apparatus 1 should use the entry_ES_PID mark having the same value as the video PID of the view that the user is currently viewing, and the recording / reproducing apparatus 1 should not change the view without permission. . The recording / reproducing device 1 also includes:
A mark in which entry_ES_PID is set to 0xFFFF may be used. Also in this case, the recording / reproducing apparatus 1 does not change the view without permission.

FIG. 137 shows the syntax of the syntax shown in FIG.
FIG. 35 is a diagram illustrating another example of ipMark (). length is this length
Indicates the number of bytes from the byte immediately after the field to the last byte of ClipMark (). maker_ID is mark_type 0x6
When indicating a value from 0 to 0x7F, it indicates the maker ID of the maker that defines the mark_type.

[0474] number_of_Clip_marks indicates the number of mark entries stored in ClipMark. mark_i
nvalid_flag is a 1-bit flag that, when its value is set to zero, indicates that this mark has valid information, and when its value is set to 1, This mark indicates that it is invalid.

[0475] When the user presses 1
When the operation of erasing the entry of one mark is performed, the recording apparatus may change the value of the mark_invalid_flag to 1 instead of deleting the entry of the mark from the ClipMark. mark_type indicates the type of mark, and has the meaning shown in FIG.

[0476] ref_to_STC_id is mark_time_stamp and repr
STC-sequence specifying the STC-sequence where both esentative_picture_time_stamp is located
Indicates -id. The value of STC-sequence-id is defined in STCInfo (). mark_time_stamp is mark_entr in FIG.
It has the same meaning as mark_time_stamp in the case of y ().

If entry_ES_PID is set to 0xFFFF, the mark is a pointer on the time axis common to all elementary streams in the Clip.
If entry_ES_PID is set to a value other than 0xFFFF, entry_ES_PID indicates the value of the PID of the transport packet containing the elementary stream pointed to by the mark.

[0478] ref_to_thumbnail_index indicates the information of the thumbnail image added to the mark. The meaning is shown in FIG.
8 is the same as ref_thumbnail_index. representativ
e_picture_time_stamp is representative_pic in FIG.
This has the same meaning as mark_time_stamp in the case of ture_entry ().

In the case of the syntax shown in FIG. 137, a mark can point to a specific elementary stream. For example, when the Clip includes a multi-view program having a plurality of video streams in the program, entry_ES_PID is used to set a video PID indicating one video stream in the program.

[0480] A user is playing back a PlayList that refers to a multi-view program.
Suppose that you are looking at one view in the multiview. now,
It is assumed that the user has sent a command to the recording / reproducing apparatus 1 to skip the reproduction to the next mark point. In this case, the recording / reproducing apparatus 1 should use the entry_ES_PID mark that has the same value as the video PID of the view currently being viewed by the user, and the recording / reproducing apparatus 1 should not change the view without permission. . The recording / reproducing device 1 also includes:
A mark in which entry_ES_PID is set to 0xFFFF may be used. Also in this case, the recording / reproducing apparatus 1 does not change the view without permission.

[0481] Based on such syntax, data structure, and rules, the contents of data recorded on the recording medium 100, reproduction information, and the like can be appropriately managed, so that the user can appropriately manage the contents during reproduction. It is possible to confirm the contents of data recorded on the recording medium and to easily reproduce desired data.

According to the database configuration of the present embodiment, a PlayList file and a Clip Information file are separately recorded separately, so that a predetermined
When the contents of the PlayList or Clip are changed, there is no need to change other files not related to the file. Therefore, the contents of the file can be easily changed, and the time required for the change and recording can be reduced.

Also, first, only Info.dvr is read,
If the recorded contents of the disc are presented to the user interface, and only the PlayList file instructed by the user to be reproduced and the Clip Information file related thereto are read from the disc, the waiting time of the user can be reduced.

[0487] If all PlayList files and Clip I
When the nformation file is collectively recorded in one file, the file size becomes very large. Therefore, the time required to change the contents of the file and record it is much greater than in the case where individual files are separately recorded. By applying the present invention, such a situation can be prevented.

As described above, an AV stream file, that is, a ClipMark that stores a mark indicating a characteristic image in a Clip AV stream file is stored in a management information data file of the AV stream, that is, a ClipMark.
An object recorded in the Clip Information file and having information of one reproduction procedure defined by a combination of designated sections in the AV stream, ie, Pl
Resume when playing the mark point specified by the user or the object from the playback range of ayList
A PlayListMark that stores a mark indicating a point is recorded in the object.

[0486] By doing so, when the PlayList is reproduced, it is possible to refer to the mark stored in the ClipMark of the Clip referred to by the PlayList. Therefore, one Clip is transferred to Real PlayList or multiple Virtual PlayL
If referenced by ist, those PlayLists
Since the ClipMark of the one Clip can be shared, mark data can be managed efficiently.

[0487] If ClipMark is not defined for Clip, Pl
If a combination of PlayListMark and ClipMark is defined only for ayList, one Clip
Are referred to by Real PlayList or multiple Virtual PlayLists, each PlayList has the same Clip
, And the efficiency of data recording is low. By applying the present invention, such a situation can be prevented.

[0488] As described above, the EP_map for storing the address of the entry point, the type of the picture at the mark point (for example, the start point of the program), and the information in the AV stream of the picture as the additional information of the AV stream. ClipMark for storing the address, Clip Information
By forming a file as a file and recording the file on the recording medium 100, it is possible to appropriately manage the encoding information of the stream necessary for reproducing the stream necessary for reproducing the AV stream.

[0489] According to the Clip Information file information,
The user can search an AV stream recorded on the recording medium 100 for a scene of interest, for example, a cue point of a program, etc., and can record in response to the user's random access or special reproduction instruction. AV from medium 100
It is easy to determine the stream reading position, and it is possible to quickly start decoding the stream.

[0490] The series of processes described above can be executed by hardware, but can also be executed by software. In this case, for example, the recording / reproducing device 1 is configured by a personal computer as shown in FIG.

In FIG. 139, the CPU (Central Process
ing unit) 201 is a ROM (Read Only Memory) 202
From the program stored in the storage unit 208
Various processes are executed according to a program loaded in a RAM (Random Access Memory) 203. The RAM 203 also appropriately stores data necessary for the CPU 201 to execute various processes.

[0492] CPU 201, ROM 202, and RAM 203
Are connected to each other via a bus 204. The bus 204 is also connected to an input / output interface 205.

The input / output interface 205 includes an input unit 206 including a keyboard and a mouse, a display including a CRT and an LCD, an output unit 207 including a speaker, a storage unit 208 including a hard disk, a modem, and a terminal. A communication unit 209 including an adapter and the like is connected. The communication unit 209 performs communication processing via a network.

[0494] A drive 210 is connected to the input / output interface 205 as necessary.
21, an optical disk 222, a magneto-optical disk 223, a semiconductor memory 224, and the like are appropriately mounted, and a computer program read therefrom is installed in the storage unit 208 as necessary.

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

[0496] As shown in FIG.
Apart from the computer, a magnetic disk 221 (including a floppy disk) storing the program, an optical disk 222 (CD-ROM (Compact Disk-Read Only Memory),
In addition to being constituted by package media including a VD (Digital Versatile Disk), a magneto-optical disk 223 (including an MD (Mini-Disk)), or a semiconductor memory 224, it is installed in a computer in advance. It is provided with a hard disk including a ROM 202 storing a program and a storage unit 208 provided to a user.

[0497] In this specification, the steps of describing a program provided by a medium are not limited to time-series processing, but may be performed in parallel according to the described order. Alternatively, it also includes individually executed processing.

[0498] In this specification, the system is
It represents the entire device composed of a plurality of devices.

[0499]

As described above, in the first information processing apparatus and method and program according to the present invention, a ClipMark composed of a mark indicating a characteristic image extracted from an input AV stream is converted into an AV stream. Is generated as management information for managing an AV stream, and defines a combination of predetermined sections in the AV stream.
Since a PlayListMark composed of a mark indicating an image arbitrarily designated by the user is generated from the playback sections corresponding to the PlayListMark, and the ClipMark and the PlayListMark are recorded on the recording medium as independent tables,
A desired position of the stream can be quickly and reliably accessed.

[0500] The second information processing apparatus, method, and program according to the present invention provide a ClipMark composed of marks indicating characteristic images extracted from an AV stream.
Management information for managing an AV stream including
Pl defining a combination of predetermined sections in the V stream
PlayListMa consisting of a mark indicating an image arbitrarily specified by the user from the playback section corresponding to ayList
rk is read, and the read management information and PlayLisMar
k, and refers to the ClipMark corresponding to the PlayList instructed by the user to reproduce from the presented information,
Since the AV stream is reproduced from the position corresponding to the ClipMark including the referenced ClipMark, it is possible to quickly and reliably access a desired position of the AV stream.

[Brief description of the drawings]

FIG. 1 is a diagram showing a configuration of an embodiment of a recording / reproducing apparatus to which the present invention is applied.

FIG. 2 is a diagram illustrating a format of data recorded on a recording medium by the recording / reproducing apparatus 1.

FIG. 3 is a diagram illustrating a Real PlayList and a Virtual PlayList.

FIG. 4 is a diagram illustrating creation of a Real PlayList.

FIG. 5 is a diagram illustrating deletion of a Real PlayList.

FIG. 6 is a diagram illustrating assemble editing.

FIG. 7 is a diagram illustrating a case where a sub path is provided in a Virtual PlayList.

FIG. 8 is a diagram illustrating a change in the playback order of a PlayList.

FIG. 9 is a diagram illustrating marks on a PlayList and marks on a Clip.

FIG. 10 is a diagram illustrating menu thumbnails.

FIG. 11 is a diagram illustrating marks added to a PlayList.

FIG. 12 is a diagram illustrating a mark added to a clip.

FIG. 13 is a diagram illustrating a relationship between a PlayList, a Clip, and a thumbnail file.

FIG. 14 is a diagram illustrating a directory structure.

FIG. 15 is a diagram illustrating the syntax of info.dvr.

FIG. 16 is a diagram illustrating the syntax of a DVR volume.

FIG. 17 is a diagram illustrating the syntax of Resumevolume.

FIG. 18 is a diagram illustrating the syntax of UIAppInfovolume.

FIG. 19 is a diagram showing a table of Character set value.

FIG. 20 is a diagram illustrating the syntax of TableOfPlayList.

FIG. 21 is a diagram illustrating another syntax of the TableOfPlayList.

FIG. 22 is a diagram illustrating the syntax of MakersPrivateData.

FIG. 23 is a diagram illustrating the syntax of xxxxx.rpls and yyyyy.vpls.

FIG. 24 is a diagram illustrating a PlayList.

FIG. 25 is a diagram illustrating the syntax of a PlayList.

FIG. 26 is a diagram showing a table of PlayList_type.

FIG. 27 is a diagram illustrating the syntax of UIAppinfoPlayList.

28 is a diagram illustrating a flag in the syntax of UIAppinfoPlayList shown in FIG. 27.

FIG. 29 is a diagram illustrating PlayItem.

FIG. 30 is a diagram illustrating PlayItem.

FIG. 31 is a diagram illustrating PlayItem.

FIG. 32 is a diagram illustrating the syntax of PlayItem.

FIG. 33 is a diagram illustrating IN_time.

FIG. 34 is a diagram illustrating OUT_time.

FIG. 35 is a diagram showing a Connection_Condition table.

FIG. 36 is a diagram for describing Connection_Condition.

FIG. 37 is a diagram for describing BridgeSequenceInfo.

FIG. 38 is a diagram illustrating the syntax of BridgeSequenceInfo.

FIG. 39 is a diagram for describing SubPlayItem.

[Fig. 40] Fig. 40 is a diagram illustrating the syntax of SubPlayItem.

FIG. 41 is a diagram illustrating a table of SubPath_type.

Fig. 42 is a diagram illustrating the syntax of PlayListMark.

Fig. 43 is a diagram illustrating a table of Mark_type.

FIG. 44 is a view for explaining Mark_time_stamp.

FIG. 45 is a diagram illustrating the syntax of zzzzz.clip.

Fig. 46 is a diagram illustrating the syntax of ClipInfo.

[Fig. 47] Fig. 47 is a diagram illustrating a Clip_stream_type table.

[Fig. 48] Fig. 48 is a diagram for describing offset_SPN.

Fig. 49 is a diagram for describing offset_SPN.

FIG. 50 is a diagram illustrating an STC section.

FIG. 51 is a diagram for describing STC_Info.

Fig. 52 is a diagram illustrating the syntax of STC_Info.

FIG. 53 is a view for explaining ProgramInfo.

Fig. 54 is a diagram illustrating the syntax of ProgramInfo.

Fig. 55 is a diagram illustrating the syntax of VideoCondingInfo.

Fig. 56 is a diagram illustrating a Video_format table.

Fig. 57 is a diagram illustrating a table of frame_rate.

Fig. 58 is a diagram illustrating a table of display_aspect_ratio.

Fig. 59 is a diagram illustrating the syntax of AudioCondingInfo.

Fig. 60 is a diagram illustrating a table of audio_coding.

Fig. 61 is a diagram illustrating a table of audio_component_type.

FIG. 62 is a diagram illustrating a table of sampling_frequency.

FIG. 63 is a diagram illustrating CPI.

FIG. 64 is a diagram illustrating CPI.

Fig. 65 is a diagram illustrating the syntax of CPI.

Fig. 66 is a diagram illustrating a table of CPI_type.

Fig. 67 is a diagram for describing a video EP_map.

Fig. 68 is a diagram for describing EP_map.

Fig. 69 is a diagram for describing EP_map.

Fig. 70 is a diagram illustrating the syntax of EP_map.

Fig. 71 is a diagram illustrating a table of EP_type values.

Fig. 72 is a diagram illustrating the syntax of EP_map_for_one_stream_PID.

Fig. 73 is a diagram for describing TU_map.

Fig. 74 is a diagram illustrating the syntax of TU_map.

Fig. 75 is a diagram illustrating the syntax of ClipMark.

Fig. 76 is a diagram illustrating a table of mark_type.

Fig. 77 is a diagram illustrating a table of mark_type_stamp.

Fig. 78 is a diagram illustrating another example of the syntax of ClipMark.

[Fig. 79] Fig. 79 is a diagram illustrating another example of the Mark_type table.

[Fig. 80] mark_entry () and representative_picture_ent
It is a figure showing an example of ry ().

[Fig. 81] mark_entry () and representative_picture_ent
It is a figure showing the syntax of ry ().

[Fig. 82] mark_entry () and representative_picture_ent
FIG. 35 is a diagram illustrating another example of the syntax of ry ().

[Fig. 83] Fig. 83 is a diagram for describing a relationship between RSPN_ref_EP_start and offset_num_pictures.

[Fig. 84] mark_entry () and representative_picture_ent
FIG. 35 is a diagram illustrating another example of the syntax of ry ().

[Fig. 85] Fig. 85 is a diagram illustrating the relationship between ClipMark and EP_map.

Fig. 86 is a diagram illustrating the syntax of menu.thmb and mark.thmb.

Fig. 87 is a diagram illustrating the syntax of Thumbnail.

Fig. 88 is a diagram illustrating a table of thumbnail_picture_format.

FIG. 89 is a view for explaining tn_block.

[Fig. 90] Fig. 90 is a diagram illustrating the structure of a transport stream of DVR MPEG2.

Fig. 91 is a diagram illustrating a recorder model of a transport stream of DVR MPEG2.

Fig. 92 is a diagram illustrating a player model of a transport stream of DVR MPEG2.

Fig. 93 is a diagram illustrating the syntax of a source packet.

Fig. 94 is a diagram illustrating the syntax of TP_extra_header.

FIG. 95 is a diagram illustrating a table of a copy permission indicator.

FIG. 96 is a diagram illustrating seamless connection.

FIG. 97 is a diagram illustrating seamless connection.

FIG. 98 is a diagram illustrating seamless connection;

FIG. 99 is a diagram illustrating seamless connection.

FIG. 100 is a diagram illustrating seamless connection;

FIG. 101 is a diagram illustrating audio overlap;

Fig. 102 is a diagram for describing seamless connection using BridgeSequence.

Fig. 103 is a diagram for describing seamless connection without using BridgeSequence.

FIG. 104 is a diagram illustrating a DVR STD model.

FIG. 105 is a diagram showing a timing chart of decoding and display.

FIG. 106 is a flowchart for describing cueing reproduction of a scene indicated by a mark point in the case of the syntax in FIG. 81.

Fig. 107 is a diagram for describing a playback operation in the case of the syntax in Fig. 81.

Fig. 108 is a diagram illustrating an example of an EP_map.

Fig. 109 is a diagram illustrating an example of a ClipMark.

Fig. 110 is a flowchart for describing CM skip playback processing in the case of the syntax in Fig. 81.

FIG. 111 is a flowchart illustrating CM skip playback processing in the case of the syntax in FIG. 81.

FIG. 112 is a flowchart for describing cueing reproduction of a scene indicated by a mark point in the case of the syntax of FIG.

FIG. 113 is a diagram for describing playback in the case of the syntax in FIG. 82;

Fig. 114 is a diagram illustrating an example of an EP_map.

Fig. 115 is a diagram illustrating an example of a ClipMark.

Fig. 116 is a flowchart for describing CM skip playback in the case of the syntax in Fig. 82.

Fig. 117 is a flowchart for describing CM skip playback in the case of the syntax in Fig. 82.

FIG. 118 is a flowchart for describing cueing reproduction of a scene indicated by a mark point in the case of the syntax in FIG. 84.

Fig. 119 is a diagram for describing reproduction in the case of the syntax in Fig. 84.

Fig. 120 is a diagram illustrating an example of an EP_map.

FIG. 121 is a diagram illustrating an example of a ClipMark.

FIG. 122 is a flowchart for describing CM skip playback in the case of the syntax in FIG. 84.

123 is a flowchart for describing CM skip playback in the case of the syntax in FIG. 84.

FIG. 124 is a diagram showing an application format.

Fig. 125 is a diagram for describing marks on a PlayList and marks on a Clip.

Fig. 126 is a diagram illustrating another example of the syntax of ClipMark.

Fig. 127 is a diagram illustrating another example of the syntax of ClipMark.

Fig. 128 is a flowchart for describing creation of a ClipMark when an analog AV signal is encoded and recorded.

Fig. 129 is a flowchart for describing creation of a ClipMark when a transport stream is recorded.

FIG. 130 is a flowchart illustrating creation of a RealPlayList.

FIG. 131 is a flowchart illustrating creation of a VirtualPlayList.

Fig. 132 is a flowchart for describing playback of a PlayList.

Fig. 133 is a flowchart for describing creation of a PlayListMark.

Fig. 134 is a flowchart for describing cueing playback when playing a PlayList.

Fig. 135 is a diagram illustrating the syntax of PlayListMark.

Fig. 136 is a diagram for describing Mark_type of PlayListMark.

Fig. 137 is a diagram illustrating another syntax of ClipMark.

Fig. 138 is a diagram for describing Mark_type of ClipMark.

FIG. 139 is a diagram illustrating a medium.

[Explanation of symbols]

Reference Signs List 1 recording / reproducing device, 11 to 13 terminals, 14 analyzing unit, 15 AV encoder, 16 multiplexer, 17 switch, 18 multiplexed stream analyzing unit, 19 source packetizer, 20 ECC encoding unit, 21 modulation unit, 22 writing unit, 23 control unit, 24 user interface, 25 switch, 26 demultiplexer, 27 AV decoder,
28 readout unit, 29 demodulation unit, 30 ECC decoding unit, 31 source packetizer, 32, 33 terminals

 ────────────────────────────────────────────────── ─── Continued on the front page F term (reference) 5C052 AA02 AB03 AB04 AC08 CC06 CC11 DD04 5C053 FA14 FA23 GB05 GB38 HA29 JA16 JA22 JA24 LA04 LA05 LA11

Claims (23)

[Claims] 1. A ClipMark composed of marks indicating characteristic images extracted from an input AV stream.
Is generated as management information for managing the AV stream, and a mark indicating an image arbitrarily designated by the user from reproduction sections corresponding to a PlayList defining a combination of predetermined sections in the AV stream. Play composed of
An information processing apparatus comprising: a generating unit that generates a ListMark; and a recording unit that records the ClipMark and PlayListMark on a recording medium as independent tables. 2. The method according to claim 1, wherein the generating unit generates the ClipMark from a ClipMa
Generate as rkInformation file and
The information processing apparatus according to claim 1, wherein the layList is generated as a PlayList file. 3. The information processing apparatus according to claim 1, wherein the PlayListMark further includes a mark indicating a Resume point when the PlayList is reproduced. 4. When reproducing the PlayList, the PlayList
ClipMa of the AV stream corresponding to the playback section of the List
2. The information processing apparatus according to claim 1, wherein the mark configuring rk is referred to. 5. The mark of the PlayListMark includes a presentation time stamp and identification information indicating one designated playback section on the AV stream data constituting a playback path of the PlayList. Item 2. The information processing device according to item 1. 6. The information processing apparatus according to claim 1, wherein the mark forming the ClipMark or the mark forming the PlayListMark includes information for specifying an entry point of an elementary stream. . 7. The mark of the PlayListMark may be a starting point of a favorite scene specified by a user or a PlayLimit.
The information processing apparatus according to claim 1, further comprising information of a type including at least a Resume point of st. 8. The system according to claim 1, wherein the mark forming the ClipMark and the mark forming the PlayListMark are represented by a relative source packet address corresponding to an entry point of the AV stream.
An information processing apparatus according to claim 1. 9. The mark forming the ClipMark and the mark forming the PlayListMark are a first address of a relative source packet corresponding to an entry point of the AV stream, and a mark from the first address. The information processing apparatus according to claim 8, wherein the information is represented by a second address that is an offset address. 10. The image processing apparatus according to claim 1, further comprising a type detection unit configured to detect a type of the characteristic image detected at the time of recording by the first recording unit, 2. The information processing apparatus according to claim 1, wherein a mark is recorded in correspondence with the type detected by the type detection unit. 11. The information processing apparatus according to claim 1, wherein the mark of the ClipMark includes a scene at which a scene change point, a commercial start point, a commercial end point, or a title is displayed. 12. A ClipMa comprising a mark indicating a characteristic image extracted from an input AV stream.
rk is generated as management information for managing the AV stream, and indicates an image arbitrarily designated by the user from reproduction sections corresponding to a PlayList that defines a combination of predetermined sections in the AV stream. Play composed of marks
An information processing method comprising: a generation step of generating a ListMark; and a recording control step of performing control when recording the ClipMark and the PlayListMark as independent tables on a recording medium. 13. A ClipMa comprising a mark indicating a characteristic image extracted from an input AV stream.
rk is generated as management information for managing the AV stream, and indicates an image arbitrarily designated by the user from reproduction sections corresponding to a PlayList that defines a combination of predetermined sections in the AV stream. Play composed of marks
A computer readable program is recorded, comprising: a generation step of generating a ListMark; and a recording control step of performing control when recording the ClipMark and PlayListMark on a recording medium as independent tables. Recording media. 14. A ClipMa comprising a mark indicating a characteristic image extracted from an input AV stream.
rk is generated as management information for managing the AV stream, and indicates an image arbitrarily designated by the user from reproduction sections corresponding to a PlayList that defines a combination of predetermined sections in the AV stream. Play composed of marks
A program for causing a computer to execute a generation step of generating a ListMark, and a recording control step of performing control when recording the ClipMark and the PlayListMark as independent tables on a recording medium. 15. Management information for managing the AV stream including a ClipMark including a mark indicating a characteristic image extracted from the AV stream;
Pl defining a combination of predetermined sections in the V stream
PlayListMa consisting of a mark indicating an image arbitrarily specified by the user from the playback section corresponding to ayList
read means for reading rk; presentation means for presenting the management information read by the read means and the information according to the PlayLisMark; and from the information presented by the presentation means, An information processing apparatus comprising: a reference unit that refers to the corresponding ClipMark; and a reproduction unit that includes the ClipMark referred to by the reference unit and reproduces the AV stream from a position corresponding to the ClipMark. 16. The information processing apparatus according to claim 15, wherein the presenting unit presents a list of thumbnail images corresponding to the PlayLisMark to a user. 17. The method according to claim 15, wherein the mark forming the ClipMark and the mark forming the PlayListMark are represented by a relative source packet address corresponding to an entry point of the AV stream. An information processing apparatus according to claim 1. 18. The mark forming the ClipMark and the mark forming the PlayListMark are a first address of a relative source packet corresponding to an entry point of the AV stream, and a mark from the first address. 18. The information processing apparatus according to claim 17, wherein the information is represented by a second address that is an offset address. 19. The information processing apparatus according to claim 15, wherein the mark of the ClipMark includes a scene at which a scene change point, a commercial start point, a commercial end point, or a title is displayed. 20. management information for managing the AV stream including a ClipMark including a mark indicating a characteristic image extracted from the AV stream;
Pl defining a combination of predetermined sections in the V stream
PlayListMa consisting of a mark indicating an image arbitrarily specified by the user from the playback section corresponding to ayList
a read control step of controlling the read of rk; a presentation step of presenting the management information and the information by the PlayLisMark, the read of which is controlled in the processing of the read control step; and from the information presented in the processing of the presentation step. , The Clip corresponding to the PlayList for which the user instructed the reproduction.
Information comprising: a reference step of referring to a Mark; and a reproduction control step of controlling reproduction of the AV stream from a position corresponding to the ClipMark, including the ClipMark referred to in the processing of the reference step. Processing method. 21. management information for managing the AV stream including a ClipMark including a mark indicating a characteristic image extracted from the AV stream;
Pl defining a combination of predetermined sections in the V stream
PlayListMa consisting of a mark indicating an image arbitrarily specified by the user from the playback section corresponding to ayList
a read control step of controlling the reading of rk; a presentation step of presenting the management information and the information by the PlayLisMark, the read of which has been controlled in the processing of the read control step; and , The Clip corresponding to the PlayList for which the user instructed the reproduction.
A computer comprising: a reference step of referring to a Mark; and a reproduction control step of controlling reproduction of the AV stream from a position corresponding to the ClipMark, including the ClipMark referred to in the processing of the reference step. A recording medium on which a readable program is recorded. 22. management information for managing the AV stream including a ClipMark including a mark indicating a characteristic image extracted from the AV stream;
Pl defining a combination of predetermined sections in the V stream
PlayListMa consisting of a mark indicating an image arbitrarily specified by the user from the playback section corresponding to ayList
a read control step of controlling the reading of rk; a presentation step of presenting the management information and the information by the PlayLisMark, the read of which has been controlled in the processing of the read control step; and , The Clip corresponding to the PlayList that the user instructed to reproduce
A program for causing a computer to execute a reference step of referring to a Mark, and a reproduction control step of controlling reproduction of the AV stream from a position corresponding to the ClipMark, including the ClipMark referred to in the processing of the reference step. 23. management information for managing the AV stream including a ClipMark including a mark indicating a characteristic image extracted from the AV stream;
Pl defining a combination of predetermined sections in the V stream
PlayListMa consisting of a mark indicating an image arbitrarily specified by the user from the playback section corresponding to ayList
rk is recorded as an independent table.