RU2538307C2 - Data structure and data medium, playback device, playback method, programme and programme storage medium - Google Patents

Abstract

FIELD: physics, computer engineering.

SUBSTANCE: invention relates to a playback device, a playback method and a programme storage medium, which provide a video format for 3D display. The playback device is configured to playback data of a data structure, comprising: image data used for 2D display of an auxiliary image comprising a header or a menu button, and a playlist file comprising a table in which, for said auxiliary image corresponding to said image data, shift information is described, which comprises the shift direction which is the direction of shift of an image L for the left eye and the image R for the right eye, used for 3D display of the auxiliary image, and a shift value which is a value of sift depending on the moment of playing back the auxiliary image.

EFFECT: displaying headers and menu buttons in 3D format.

7 cl, 30 dwg

Description

Technical field

The present invention relates to a data structure and a storage medium, a reproducing device, a reproducing method, a program and a storage medium for a program, and in particular, relates to a data structure and a storage medium, a reproducing device, a reproducing method, a program and a storage medium for a program that allows present a video format for 3D display, suitable for 3D display of headers and menu buttons.

State of the art

There are various types of displays having functions for reproducing 3D (three-dimensional) images (hereinafter 3D display). There are also various types of video formats for 3D display (hereinafter referred to as 3D video formats).

3D video formats include a method using images from three or more viewpoints (multi-view), in particular, for example, 3D video format using two-dimensional images and depth images suitable for 3D display in the so-called lens method, and so on.

Further, as a disc storage medium for recording data such as images and the like, there are playback-only optical discs that comply with the Blu-ray disc (registered trademark) standard. In accordance with this standard, headers are displayed in a plane separated from the plane on which moving images are displayed, and headers and moving images are superimposed and displayed by combining the header plane and the moving image plane. For example, a single screen with image data on which a title is displayed on a moving image is created by providing portions of the title plane other than the title with a transparent defining feature, and placing the title plane in front of the moving image plane. PTL 1 describes a method in which both the moving image plane and the title plane are presented based on a Blu-ray disc standard, which is a recording / reproducing standard, and moving images in accordance with video data and headers according to the title and image data are displayed on a screen.

References

Patent Literature

PTL 1: Japanese Patent Application Laid-Open No. 2004-304767.

Disclosure of invention

However, at present, there is no video format for 3D display suitable for 3D display of headers and menu buttons.

The present invention has been made in the light of this circumstance, and its purpose is to provide a video format for 3D display suitable for 3D display of headers and menu buttons.

A data structure or data carrier in accordance with one aspect of the present invention is a data structure or data carrier in which data structure data is recorded including image data used for 2D (two-dimensional) display of an auxiliary image consisting of a title or menu button; and a table in which, for the sub image corresponding to the image data, displacement information is described consisting of a displacement direction representing the displacement direction of the image L for the left eye and the image R for the right eye used for 3D display of the sub image and the displacement value, representing the amount of shift, in some way corresponding to the time of reproduction of the auxiliary image.

Together with the data structure or data carrier onto which data about the data structure is recorded in accordance with the first aspect of the present invention, image data used for 2D (two-dimensional) display of an auxiliary image composed of a title or menu button and a table in which for the auxiliary image corresponding to the image data, described information about the offset containing the direction of the offset, which is the direction of the shift of the image L for the left eye and image Ia R for the right eye, used for 3D display of the sub-image, and an offset value representing a shift amount, in a way corresponding to the time playback of the auxiliary image.

A reproducing apparatus in accordance with one aspect of the present invention is a reproducing apparatus which, in the case of reproducing data of a data structure including image data used for 2D (two-dimensional) display of an auxiliary image consisting of a title or menu button, and a table in which for the sub image corresponding to the image data, displacement information is described comprising a direction of displacement representing a direction of displacement of the image eniya L for the left eye and the image R for the right eye, used for 3D display of the sub-image, and an offset value representing a shift amount, in a way corresponding to the time playback sub-image; reads and holds the table included in the specified data; reads image data included in the specified data; and, if the reproduction time point of the image data is the reproduction time point contained in the table, creates and outputs image data for the image L and the image R from the specified image data based on the offset information described in accordance with the reproduction time point.

The reproduction method, program, and program storage medium in accordance with one aspect of the present invention correspond to the object of the present invention described above.

Thanks to the reproducing apparatus, the reproducing method, the program, and the program storage medium according to one aspect of the present invention, data structure data including image data used for 2D (two-dimensional) display of an auxiliary image consisting of a title or a menu button is reproduced, and a table in which for the sub image corresponding to the image data, displacement information is described consisting of a direction of displacement representing shift direction of the image L for the left eye and the image R for the right eye, used for 3D display of the sub-image, and an offset value representing a shift amount, in a way corresponding to the time playback of the auxiliary image, as described hereinafter. That is, the table included in the data is read and held. Image data included in the data is also read. In case the reproduction time point of the image data is a reproduction time point included in the table, image data for the image L and the image R from these image data are created and output based on the offset information described in accordance with this reproduction time point.

Beneficial effects of the invention

In accordance with the present invention, 3D display of headers and menu buttons can be carried out. In addition, a video format for 3D display can be provided suitable for 3D display of titles and menu buttons.

Brief Description of the Drawings

FIG. 1 is a diagram illustrating an example embodiment of a first embodiment of a disc to which the present invention is applied.

Figure 2 is a diagram illustrating a detailed example of the execution of the index file.

3 is a diagram conceptually illustrating a database of bias information.

4 is a diagram illustrating an example description of a playlist file.

5 is a diagram illustrating a detailed example of a description of data_block.

FIG. 6 is a block diagram illustrating a detailed embodiment of a reproducing apparatus for reproducing a disc of FIG. 1.

7 is a diagram illustrating an example of functional execution of a reproducing device when executing an object BD-J.

Fig. 8 is a flowchart for describing an offset setting performed by a reproducing apparatus when executing a BD-J object.

9 is a diagram describing the effects of a reproducing device.

10 is a diagram illustrating a detailed example of a description of “offset_metadata ()” in a second embodiment of a disc to which the present invention is applied.

11 is a block diagram illustrating an example embodiment of a reproducing device.

12 is a diagram illustrating an example of a functional implementation of a reproducing device when executing an object BD-J.

13 is a flowchart for describing an offset setting performed by a reproducing apparatus when executing a BD-J object.

14 is a diagram illustrating a detailed example of a description of “offset_metadata ()” in a third embodiment of a disc to which the present invention is applied.

15 is a block diagram illustrating an example embodiment of a reproducing device.

Fig. 16 is a diagram illustrating an example of a functional implementation of a reproducing device when executing an object BD-J.

17 is a flowchart for describing an offset setting performed by a reproducing apparatus when executing an object BD-J.

18 is a diagram for describing forbidden units of bias information.

19 is a diagram illustrating an embodiment of a fourth embodiment of a disc to which the present invention is applied.

FIG. 20 is a block diagram illustrating an example embodiment of a reproducing apparatus for reproducing a disc of FIG. 19.

FIG. 21 is a flowchart illustrating a detailed exemplary embodiment of the 3D display data generation unit of FIG.

Fig. 22 is a diagram illustrating an example of a functional implementation of a reproducing device when executing an object BD-J.

FIG. 23 is a flowchart for describing an offset setting performed by a reproducing apparatus when executing a BD-J object. FIG.

24 is a diagram illustrating an example embodiment of video data recorded on a disc in accordance with a fifth embodiment to which the present invention is applied.

25 is a diagram illustrating an example of a description of “offset_metadata ()”.

FIG. 26 is a block diagram illustrating an example embodiment of a reproducing apparatus for reproducing a disc on which the video data of FIG. 24 is recorded.

FIG. 27 is a diagram illustrating an example of a functional implementation of a reproducing device when executing an object BD-J.

FIG. 28 is a flowchart for describing an offset setting performed by a reproducing apparatus when executing a BD-J object.

29 is a block diagram illustrating an embodiment of a sixth embodiment of a reproducing apparatus to which the present invention is applied.

30 is a diagram for describing a method for generating 3D display data.

Description of Embodiments

First Embodiment

Disk Run Example

FIG. 1 is a diagram illustrating an example embodiment of a first embodiment of a disc to which the present invention is applied.

Disc 11 in FIG. 1 consists of a BD-ROM (Blu-ray disc is a permanent storage device) and the like with an index file (index.bdmv) and a movie object file (MovieObject.bdmv) recorded on disc 11. Also on disc 11 recorded playlist file (PLAYLIST / XXXXX.mpls), clip data file (CLIPINF / XXXXX.clpi), stream file (STREAM / XXXXX.m2ts) and so on. In addition, the BD-J object file (BDJO / XXXXX.bdjo), its dependent file (JAR / XXXXX.jar), and so on, are recorded on disk 11. It should be borne in mind that X is an arbitrary digit from 0 to 9.

As shown in FIG. 2, for example, a list of title numbers recorded on the disc 11 and types and numbers of objects used in accordance with the title numbers are described in the index file.

The title numbers described are not just integers represented in order of 1, but also “First Play” corresponding to the object executed when the disc 11 is inserted in the reproducing device. Also described is the “Top Menu” (main menu) corresponding to the object executed when the main menu screen is displayed. Regarding the types of objects, there are two types of movie object (MovieObject) and BD-J object (BD-J Object).

In the example shown in FIG. 2, “MovieObject # l”, “MovieObject # 2” and “MovieObject # M” are described in the index file as “First Play”, “Top Menu” and “Title # N”, respectively. In addition, “BD-J Object # l” is described as “Title # l”.

It should be borne in mind that MovieObject # i and BD-J Object # i each have a movie object and a BD-J object as the type of their object, where i represents the number of the object. In addition, Title # i represents that the title number is i. Such an index file is also called an index table.

Various movie objects are described in the movie object file, and commands (navigation commands) are described in movie objects. A reproducing device that plays the disc 11 sequentially executes these commands.

A playlist file is a file played back only by a movie object or a BD-J object, and it describes information reproduced with these objects related to the AV stream (to be described below).

In particular, the playlist file consists of various play units, a database of offset information (to be described later) needed to create 3D images from images for 2D display, and so on. Each playback unit has data described therein that defines the clip data file as the AV stream to be played back, and time data representing the reproduced part of the AV stream. Details of the base of the bias information will be described with respect to FIG. 3 and others described later.

Further, the AV stream consists of TS (transport stream) video data packets in which the video data for 2D display of main images, such as films, are encoded in MPEG2, MPEG-4 AVC (advanced video coding), VC1 and the like formats, and are multiplexed by ISO 13818-2, and from its corresponding audio data, header data for 2D displaying the title as auxiliary images, and menu data for 2D displaying the menu buttons as auxiliary images.

Also, the displacement information consists of a displacement direction indicating a direction of displacement of images for the left eye and for the right eye in 3D display relative to images for 2D display, and a displacement value indicating an amount of displacement. It should be borne in mind that the direction of displacement for the left eye and the direction of displacement for the right eye are opposite directions. The offset values are expressed, for example, by the number of pixels.

The clip data file contains a display map described therein, matching time information described in the playlist file, and packet numbers of the AV stream. Accordingly, the reproducing apparatus can recognize the packet number of the AV stream to be reproduced in accordance with each reproducing unit by accessing the clip data file.

The stream file is an AV stream file.

Many BD-J applications are described in the BD-J object file. A reproducing apparatus for reproducing a disc 11 calls these BD-J applications.

Description of the database and offset information

3 is a diagram conceptually illustrating a database of bias information.

As shown in FIG. 3, for a displacement information database, a table of displacement information in increments of screens with respect to header data and menu data for each point in time of playback is described.

Specifically, the bias direction and the bias value, acting as bias information, are described in the bias information database consistent with the timing of the playback of the screen on which the bias information is set, and the title (PG) or menu button (IG) in as the type of this screen.

Playlist file description example

4 is a diagram illustrating an example description of a playlist file on the disc 11.

As shown in FIG. 4, along with a playlist file on disk 11, numerical values are described indicating that the offset information database is described in the “data_block” section as “ID1” and “ID2” of the “ext_data_entry” section of “ExtensionData”. In the example of FIG. 2, “0 × 0001” is described as “ID1”, and “0 × 0003” is described as “ID2”.

Also, the displacement information database is described in the data_block section. A detailed description of an example of this “data_block” will be given in relation to the FIG. 5 described below.

Data block description example

5 is a diagram illustrating a detailed example of a description of “data_block”.

The left side of FIG. 5 illustrates an example description of “data_block”, and the right side illustrates the meaning of the description.

As shown in FIG. 5, “data_block” has “offset_metadata ()” located beneath it, and a database of offset information is described in this “offset_metadata ()”.

Details are 32-bit data indicating the length of "offset_metadata ()" (length), .. 16-bit data indicating the number of "metadata_block_entry" located in "offset_metadata ()" (number_of_ metadata_block_entries), "metadata_block_entry" and 16-bit empty area (reserved_for_future_use).

In “metadata_block_entry” is the identifier of the unit of play to which reference is given, that is, 16-bit data representing the identifier of the unit of play corresponding to the screen in relation to which the offset information is set (ref_to_PlayItem_id). Also in "metadata_block_entry" are single-bit data indicating the type of screen in relation to which the offset information (plane_identifier) is set. In the example of FIG. 5, in the case where the type of screen for which the offset information is set is a menu button (IG), “0” is set, and in the case of the title (PG), “1” is set.

In “metadata_block_entry” there is a 7-bit empty area for alignment of digits (reserved_for_word_align) and 8-bit data representing the identifier of the AV stream referenced, that is, the identifier of the AV stream corresponding to the screen for which the offset information is set (ref_to stream_id). However, it should be noted that during the execution of the BD-J object, the AV stream does not create a menu button screen, so there is no identifier of the AV stream to which the link is given. Accordingly, the data (ref_to stream_id) regarding the offset information set on the menu button screen when the BD-J object is executed are described as a numerical value indicating that the offset information is to be set when the BD-J object is executed (“OxFF” in the example of FIG. 5).

Also in the “metadata_block_entry” are the 16-bit blank area (reserved_for_future_use), 16-bit data representing the number “offset_metadata ()” located inside the “metadata_block_entry” (number_of_offset_metadata), and “offset_metadata”.

In "offset_metadata" there are 32-bit data representing the instant of playback time of the screen with respect to which offset information (offset_pts) is set, and one-bit data indicating information about the offset, direction of the offset (offset_flag). As for the data representing the direction of the displacement, for example, “0” is used in the case when the direction of the displacement causes the 3D image to protrude in the direction of the near side (user side), and “1” is used in the case when the direction of the displacement causes the 3D image to recede to direction to the far side.

Metadata_block_entry also has 7-bit data representing the offset value (offset_value), an 8-bit blank area for aligning bits, and a 16-bit blank area.

It should be noted that while in accordance with the example of FIG. 5, single-bit data (plane_identifier), which is the type of screen for which offset information is set, is located in “offset_metadata ()”, this data should not be provided. In this case, the descriptive position in the displacement information database for each of the header data and the menu data is described in the playlist file.

Example playback device

6 is a block diagram illustrating an example embodiment of a reproducing apparatus 20 for reproducing the above-described disc 11.

The reproducing device 20 shown in FIG. 6 comprises an input unit 21, a control unit 22, a reproducing unit 23, a memory unit 24, a communication unit 25, and a drive 26.

The input unit 21 consists of a keyboard, mouse, microphone, and the like. The input unit 21 receives instructions from the user that are supplied to the control unit 22. The control unit 22 controls the reproducing unit 23 in accordance with the commands from the input unit 21 by means of a predetermined program. For example, the control unit 22 supplies from the input unit 21 a playlist file recorded on the disc 11 to the 3D display data generating unit 36 in accordance with the 3D playback commands of the disc 11.

The reproducing unit 23 consists of a drive 31, a read buffer 32, a packet identifier (PID) filter 33, a 3D video generation unit 34, a 3D graphics generation unit 35, a 3D display data generation unit 36, and an audio generation unit 37.

The drive 31 plays the disc 11 that was installed under the control of the control unit 22. Accordingly, the drive 31 reads the index files, playlist files, stream files and the like recorded on the disc 11. The drive 31 supplies the index files and the playlist files and the like the like that were read to the control unit 22. The drive 31 supplies the AV streams serving as stream files that are read to the read buffer 32.

Under control of the control unit 22, the read buffer 32 holds the AV streams supplied from the drive 31, reads the AV streams held to be supplied to the PID filter 33, and so on.

The PID filter 33 extracts packets for each of the video data, header data, menu data, and audio data included in the AV stream based on the packet identifier (PID) of the packets of the AV stream from the read buffer 32. It should be noted that the PID is an identifier unique to each the type of data that makes up the packet and is added to the packet.

The PID filter 33 extracts PEP packets (PES) from each of the extracted packets for each video data, title data, menu data, and audio data. The PID filter 33 then feeds the PEP packets of the video data to the video generation unit 34 and supplies the PEP packets of the header data and the menu data to the graphics generation unit 35. The PID filter 33 also supplies PEP audio data packets to the audio generation unit 37.

The video generation unit 34 decodes the PEP video data packets supplied from the PID filter 33 and supplies the resulting video data to the 3D display data generation unit 36.

The 3D graphics generation unit 35 comprises a header generation unit 41 and a menu generation unit 42. The header generation unit 41 creates the header data using the PES packets for the header data supplied from the PID filter 33 and feeds them to the 3D display data generation unit 36.

The menu generating unit 42 creates the menu data using the probes for the menu data supplied from the PID filter 33 when the movie object is executed, and ignores the probes menu data and creates the menu data under the control of the control unit 22 when the BD-J object is executed. The menu generation unit 42 then supplies the created menu data to the 3D display data generation unit 36.

The 3D display data generating unit 36 holds the playlist files filed from the control unit 22 in the internal memory (not shown). Also, the 3D display data generation unit 36 creates image data for the left eye and image data for the right eye from the video data supplied from the video generation unit 34, and the header data and menu data supplied from the graphics generation unit 35.

Specifically, the 3D display data generating unit 36 generates image data obtained as a result of shifting the main image corresponding to the video data in one direction from the left and right directions to a predetermined offset value in screen increments, as video data for the left eye, and creates image data obtained as a result of a shift in the other direction, as video data for the right eye.

Also, the 3D display data generating unit 36 searches for the offset information corresponding to the time of reproduction of the title data to be reproduced from “offset_metadata ()” in the playlist file contained in the built-in memory and creates header data for the left eye and for the right eye on based on this bias information. Similarly, it creates menu data for the left eye and for the right eye based on the offset information in “offset_metadata ()” in the playlist file.

The 3D display data generating unit 36 combines the video data, the header data and the menu data for the left eye and the right eye, which are thus created, into data for each eye. The 3D display data generating unit 36 supplies the display data for the left eye and the display data for the right eye as a result to the display unit 51 as the 3D display data.

The audio generation unit 37 decodes PEP packets of audio data supplied from the PID filter 33, and supplies the resulting audio data to the speaker 52.

The display unit 51 consists of a 3D display and so on. The display unit 51 outputs data based on the 3D display data supplied from the 3D display data generation unit 36. As a result, the user can see 3D images.

A speaker 52 outputs audio as audio data supplied from the audio generation unit 37.

The memory unit 24 consists of a ROM (read-only memory, ROM), RAM (random access memory, RAM), a hard disk, and the like. The memory unit 24 stores a program to be executed by the control unit 22, data created by processing by the control unit 22, and so on. The communication unit 25 consists of a network board and the like.

It should be noted that the programs executed by the control unit 22 can be stored in the ROM of the memory unit 24 or can be recorded on a removable medium 53 installed on the hard disk of the memory unit 24 or in the drive 26, and loaded into the RAM of the memory unit 24 and executed.

Examples of removable media 53 include floppy disks, CD-ROMs (compact disk storage devices), MO (magneto-optical) discs, DVDs (universal digital discs), magnetic disks, semiconductor storage devices, and so on.

Also, the program executed by the control unit 22 can be installed on the reproducing device 20 from the removable medium 53, as described above, or can be downloaded to the reproducing device 20 through a communication network or broadcast network and installed on the hard disk of the memory unit 24. In other words, the program can be transmitted wirelessly to the reproducing device 20 via a digital satellite, broadcast satellite, or transmitted to the reproducing device 20 via cable through a network such as a LAN (local area network) or the Internet, from a download site, for example.

Functional example of a reproducing device

7 is a diagram illustrating an example of a functional implementation of the reproducing device 20 when executing an object BD-J.

Hardware 71 corresponds to an input unit 21, a reproducing unit 23, a memory unit 24, and so on. Also, the firmware 72 OS (operating system) 73, the virtual machine (VM) 74 Java (registered trademark) and the application 75 BD-J correspond to the control unit 22.

When installing the disk 11 on the hardware 71, the firmware 72 controls the hardware to read the index file from the disk 11. The firmware 72 further stores the index file on the hardware 71.

Also, the firmware 72 reads the index file from the hardware 71 and recognizes the type and number of the object corresponding to the number of the title to be processed, which are described in the index file. In the example of FIG. 7, the type of this object is a BD-J object.

The firmware 72 controls the hardware 71 based on the number of the BD-J object corresponding to the number of the title to be processed to read the BD-J object to be processed from the disk 11, which is then stored on the hardware 71. After recognizing the application 75, the BD- J to be executed based on this BD-J object, the firmware 72 activates Java VM 74 (registered trademark). The firmware 72 further downloads the BD-J application 75 to the Java VM 74 (registered trademark). It should be noted that the placement can be made when the Java VM 74 (registered trademark) is activated between the installation of the disk 11 on the hardware 71 and the recognition of the application 75 BD-J to be executed.

Also, the firmware 72 controls the hardware 71 in response to a call to the playlist reader function from the OS (operating system) 73 in accordance with the application program interface (PPI) for reading the playlist file by the BD-J application 75 (hereinafter referred to as the playlist invocation PPI ) to read the playlist file from disk 11 and store it.

According to a function received from Java VM 74 (registered trademark), OS 73 calls a function with respect to firmware 72 corresponding to that function. For example, according to the playlist read function received from Java VM 74 (registered trademark) in accordance with the call of the playlist read PPI from the BD-J application 75, OS 73 calls the playlist read function with respect to the firmware 72 in accordance with this playlist read function.

BM 74 Java (registered trademark) decrypts the functions corresponding to the PPI (application programming interface) that is called by the BD-J application 75 and notifies OS 73 about this. For example, BM 74 Java (registered trademark) decrypts the function in accordance with the PPI read the playlist, which is read by the application 75 BD-J, and makes a notification to the OS 73 about the function of reading the playlist.

Appendix 75 BD-J makes a PPI call defined by Java VM 74 (registered trademark) in relation to Java VM 74 (registered trademark). For example, the BD-J application 75 calls the read-list PPI of the Java VM 74 (registered trademark).

Reproduction processing

FIG. 8 is a flowchart for describing an offset setting made by the reproducing apparatus 20 when executing a BD-J object. This processing of the bias parameters begins when the firmware 72 downloads the BD-J application 75, which sets the bias information to the Java VM 74 (registered trademark), for example.

In step S31, the BD-J application 75 makes a call to the read list PPI in relation to Java VM 74 (registered trademark). Accordingly, Java VM 74 (registered trademark) recognizes the playlist read function as a function corresponding to the playlist read PPI, and notifies the OS 73. The OS 73 calls the playlist read function with respect to the firmware 72 corresponding to the playlist read function .

In step S32, the firmware 72 controls the hardware 71 to read the playlist file from the disk 11.

In step S33, the firmware 72 stores the read playlist file to the hardware 71.

In step S34, the hardware 71 searches for “offset__metadata” to be played in the stored playlist file. In particular, hardware 71 searches for “offset_metadata” in “metadata_block_entry”, for which 1 is described as “plane_identifier”, and also including the identifier of the unit of play corresponding to the data of the headers to be played and the identifier of their AV stream. Also, hardware 71 searches for “offset_metadata” in “metadata_block_entry”, for which 0 is described as “plane_identifier”, and also including the identifier of the unit of play corresponding to the menu data to be played, with “OXFF” described for “ref to stream_id”.

At step S35, hardware 71 determines whether the current playback time is the playback time specified in “offset_pts” in “offset_metadata” found in step S34. If it is determined in step S35 that the current playback time is not the playback time indicated by “offset_pts” in the “offset_metadata” in which the search was performed, the process is performed until the current playback time is the playback time specified in "Offset_pts" in the "offset_metadata" in which the search was performed.

On the other hand, in the case where it is determined in step S35 that the current playback time point is the playback time point indicated in “offset_pts” in the “offset_metadata” in which the search was performed, the process proceeds to step S3 6. In step S3 6, the hardware equipment 71 sets the offset information represented by “offset_flag” and “offset_value” in relation to the menu data and header data described in accordance with the current point in time of playback, as the offset information to be used to create Nia menu headers and data for the left eye and right eye, respectively.

In step S37, the hardware 71 creates 3D display data including menu data and header data for the left eye and for the right eye based on the offset information set in step S36, and also creates audio data.

In step S38, the hardware 71 displays a 3D image based on the 3D display data in the display unit 51 and outputs audio corresponding to the audio data from the speaker 52.

In step S39, the firmware 72 determines whether to complete the bias setting in accordance with the command from the OS 73. In the event that it is determined in step S39 not to complete the bias setting, the process returns to step S34, and the subsequent process repeats. until a determination is made to complete the installation of the offset. On the other hand, if a determination is made in step S39 to complete the bias setting, the process ends.

It should be noted that the placement can be made when, after it is determined in step S39 not to complete the offset setting information, the process returns to step S35 until the unit of reproduction to be reproduced is updated.

As described above, the reproducing apparatus 20 first reads and holds the playlist file and sets the offset information each time a playback time point described in the offset information database in the playlist file comes. Thus, as shown in FIG. 9, the reproducing apparatus 20 can set the offset information with respect to the desired screen 151. In other words, the reproducing apparatus 20 can set the offset information for titles and menu buttons with respect to the screen at the desired playback time, and 3D display of the title or menu buttons even if the BD-J object is executed without a time representation. Thus, the video format of the disc 11, including a database of information about the offset, can be called 3D video format, suitable for 3D display of the headers and buttons of the menu.

Although this is omitted in the drawings, when movie objects are also executed, the reproducing apparatus 20 first reads and holds the playlist file and sets the offset information each time a playback time point described in the offset information database in the playlist file occurs, as in the implementation of the bias setting in FIG.

Placement can also be done if VM 74 Java (registered trademark) defines a PPI (hereinafter referred to as shifting PPI) that turns on / off the offset functions for offset information included in the playlist file by the BD-J application 75 (hereinafter referred to as functions playlist settings). In this case, when calling the offsetting PPI, while the function of setting the playlist is turned off, the offset is set in Fig. 8, and when calling the offsetting PPI, while the function of setting the playlist is on, the offset information is not set , and the headings and menu buttons are displayed in 2D. Offset commands for movie objects can be defined in the same way.

Also, the arrangement can be made if the offset information is described in segments of the AV stream on the disc 11. In this case, the offset information for the titles and menu buttons is set to the offset information described in the segments for the titles and menu buttons. However, it should be noted that the offset information for the menu buttons while the BD-J object is running is set by the BD-J application. The offset information set as described above is changed by the offset information database. It should be noted that the bias values described in the bias information database may be bias values following the change, or may be bias values that have been changed.

Also in this case, if the offsetting PPI is detected and the offsetting PPI is called up while the playlist setting function is enabled, the offset information of the titles and menu buttons is no longer changed by the offset information database.

Second Embodiment

Playlist file description example

10 is a diagram illustrating a detailed example of a description of “offset_metadata ()” in a playlist file in a second embodiment of a disc to which the present invention is applied.

As shown in FIG. 10, an offset information database is described in “offset_metadata ()”.

In detail, 32-bit data indicating the length of "offset_metadata ()" (length) is located in "offset_metadata ()". Also, each playback unit contains 16-bit data indicating the number of predefined screens where offset information is set (hereinafter referred to as the offset screen) (number_of_Plane_offsets [i]), 32-bit data representing the playback time point of each offset screen (Plane_offset_pts [ i]), one-bit data representing whether each offset screen type is a menu button (is_IG_Offsets), and one-bit data representing whether each offset screen type is a header (is_PG_Offsets).

It should be noted that in the case where the type of the offset screen is a menu button, “1”, for example, is described as single bit data representing that the type of the offset screen is a menu button. Also, in the case where the offset screen type is a header, “1”, for example, is described as single bit data representing that the offset screen type is a header.

Also, when the offset screen type is a menu button, “offset_metadata ()” also describes single-bit data representing the offset direction set for the offset screen (IG_Plane_offset_direction [j]) and 6-bit data representing the offset value (IG_Plane_offset_value [ j]), 5-bit data representing the time intervals of the playback time of the auxiliary offset screen (described in detail below) (IG_Plane_sub_offset_rate [j]), 5-bit data representing the number of auxiliary offset screens (number_of_IG_l_Plane_sub_offsets [j]), single-bit e data representing the offset direction set in each screen auxiliary bias (IG_Plane_sub_offset_direction [k]), and 6-bit information representing the offset value set in each screen auxiliary bias (IG_Plane_sub_value [k]).

It should be noted that the auxiliary bias screen is a screen between the corresponding bias screen and the next bias screen where the bias information is set. In other words, the offset screens are represented at relatively long time intervals, and the auxiliary offset screens are represented at shorter time intervals between the offset screens.

On the other hand, in the case where the type of the offset screen is the heading, “offset_metadata ()” also describes single-bit data representing the offset direction set for the offset screen (PG_Plane_offset_direction [j]) and 6-bit data representing the offset value ( PG_Plane_offset_value [j]), 5-bit data representing the time intervals of the playback time of the auxiliary offset screen (PG_Plane_sub_offset_rate [j]), 5-bit data representing the number of auxiliary offset screens (number_of_PG_Plane_sub_offsets [j]), single-bit data, etc. dstavlyayuschie offset direction set in each screen auxiliary bias (PG_Plane_sub_offset_direction [k]), and 6-bit information representing the offset value set in each screen auxiliary bias (PG_Plane_sub_value [k]).

Example playback device configuration

11 is a block diagram illustrating an example configuration of a reproducing apparatus 210 for reproducing a disc 201 onto which a playlist file including the description “offset_metadata ()” shown in FIG. 10 is recorded.

Of the configurations shown in FIG. 11, configurations similar to those shown in FIG. 6 are denoted by the same reference numerals. A duplicate description will be omitted accordingly.

The configuration of the reproducing device 210 of FIG. 11 mainly differs from the configuration of the reproducing device 20 of FIG. 6 in that instead of the reproducing unit 23, a reproducing unit 211 is provided.

The configuration of the reproducing unit 211 mainly differs from the configuration of the reproducing unit 23 of FIG. 6 in that instead of the 3D display data generating unit 36, a 3D display data generating unit 221 is provided.

Similarly to the 3D display data generation unit 36 of FIG. 6, the 3D display data generation unit 221 holds the playlist files filed from the control unit 22 in the internal memory (not shown). Also, the 3D display data generation unit 221 creates display data for the left eye and display data for the right eye from the video data supplied from the video generation unit 34, and the header data and menu data supplied from the graphics generation unit 35.

In particular, similarly to the 3D display data generation unit 36, the 3D display data generation unit 221 generates image data obtained as a result of shifting the main image corresponding to the video data in one direction from the left and right directions to a predetermined offset value in screen increments, as video data for the left eye and creates image data obtained as a result of a shift in the other direction, as video data for the right eye.

Also, the 3D display data generation unit 221 recognizes from “offset_metadata ()” in the playlist file contained in the built-in memory, the playback time of the title offset screen and the auxiliary offset screen and the offset information corresponding to the playback time of the title offset screen and the auxiliary offset screen . The 3D display data generation unit 221 further creates header data for the left eye and for the right eye from the header data supplied from the graphics generation unit 35 based on the playback time point and the offset information. Similarly, the 3D display data generation unit 221 generates menu data for the left eye and for the right eye from the timing of the playback of the bias screen of the menu button and the auxiliary bias screen and the offset information corresponding to the bias screen and the auxiliary bias screen recognized with “offset_metadata ()” in the playlist file.

The 3D display data generation unit 221 combines the video data, the header data and the menu data for the left eye and the right eye, which are thus created, into data for each eye. The 3D display data generation unit 221 supplies the left eye display data and the right eye display data as a result to the display unit 51 as 3D display data.

Functional example of a reproducing device

12 is a diagram illustrating an example of a functional implementation of the reproducing device 210 when executing an object BD-J.

Of the configurations shown in FIG. 12, configurations similar to those shown in FIG. 7 are denoted by the same reference numerals. A duplicate description will be omitted accordingly.

The configuration of FIG. 12 mainly differs from the configuration of FIG. 7 in that instead of hardware 71, hardware 231 is provided.

Hardware 231 corresponds to an input unit 21, a reproducing unit 211, a memory unit 24, and so on.

Reproduction processing

FIG. 13 is a flowchart for describing an offset setting made by the reproducing apparatus 210 when executing a BD-J object. This implementation of the offset setting begins when the firmware 72 downloads the BD-J application 75, which sets the offset information to the Java VM 74 (registered trademark), for example.

The implementation of steps S51 to S53 is similar to the implementation of steps S31 to S33 of FIG. 8, so a description thereof will be omitted.

After performing step S53 in step S54, hardware 231 searches for data regarding a play unit from a stored playlist file. In particular, the hardware 231 searches for data representing a reproduction time point of each displacement screen corresponding to an identifier of a reproducing unit to be reproduced, and data representing a displacement direction of each displacement screen, and data representing a displacement value. Also, hardware 231 searches for data representing a time interval for a playback time of the sub-offset screen corresponding to the identifier of the unit of playback to be reproduced, data representing the bias direction of each sub-bias screen, data representing the bias value of each sub-bias screen, and so on. The hardware 231 further obtains a reproduction time point of each sub-bias screen based on data representing a reproduction time point of each bias screen and data representing a time interval for a reproduction time of the sub-offset screen.

In step S55, the hardware 231 makes a determination as to whether the current playback object is an offset screen or an auxiliary offset screen. In particular, the hardware 231 determines whether the current playback time is the playback time, representing the playback time of the offset screen that was searched in step S54, or the playback time of the auxiliary offset screen obtained in step S54.

In the case where it is determined in step S55 that the current playback object is an offset screen or auxiliary offset screen, in step S56, the hardware 231 sets the offset direction and the offset value of the offset screen or auxiliary offset screen that was searched in step S54 as data current offset. After performing step S56, the process proceeds to step S57.

On the other hand, in the case where it is determined in step S55 that the current playback object is neither an offset screen nor an auxiliary offset screen, step S56 is skipped and the process proceeds to step S57.

It should be noted that step S55 and step S56 are performed for each of the header data and the menu data.

In step S57, the hardware 231 creates 3D display data including menu data and header data for the left eye and for the right eye based on the displacement information set as the current displacement information, and also creates audio data.

In step S58, the hardware 231 displays a 3D image based on the 3D display data in the display unit 51 and outputs audio corresponding to the audio data from the speaker 52.

In step S59, the firmware 72 determines whether to complete the bias setting in accordance with the command from the OS 73. In the event that it is determined in step S59 not to complete the bias setting, the process returns to step S54 and the subsequent process repeats until it will be determined to complete the offset setting. On the other hand, if a determination is made in step S59 to end the bias setting, the process ends.

It should be noted that it is possible that, after the determination is made in step S59 not to complete the offset setting information, the process returns to step S55 until the unit of reproduction to be reproduced is updated.

As described above, the reproducing apparatus 210 first reads and holds the playlist file and sets the offset information each time the reproduction time of the offset image and the auxiliary offset image described in the offset information database in the playlist file comes. Thus, as shown in FIG. 9, the reproducing apparatus 210 can set the bias information in relation to the desired screen 151. Accordingly, the video format of the disc 201 including the bias information database can be called a 3D video format suitable for 3D display of titles and menu buttons.

Also, with the playlist file recorded on the disc 201, offset screens and sub offset screens are set, and offset information is described for each of the offset screens and sub offset screens. The reproducing device 210 updates the offset information each time a reproduction time occurs for the offset screens and the auxiliary offset screens. Accordingly, the data amount of the playlist file can be reduced in comparison with the disc 11 on which the offset information is described for all images for which the offset information is set.

Third Embodiment

Playlist file description example

14 is a diagram illustrating a detailed example of a description of “offset_metadata ()” in a playlist file in a third embodiment of a disc to which the present invention is applied.

As shown in FIG. 14, an offset information database is described in “offset_metadata ()”.

In detail, “offset_metadata ()” contains 32-bit data indicating the length of “offset_metadata ()” (length), 4-bit data representing an identifier unique to setting the offset information for each unit of play that is included in the setting of information about the offset (hereinafter referred to as the offset identifier), and a 12-bit empty area (reserved_for_future_use) for future use. Also presented are 16-bit data representing the number of offset screens corresponding to the offset information settings in which each offset identifier is included for each unit of play (number_of_offsets), and data related to the offset information settings (hereinafter referred to as setting information).

32-bit data representing the playing time of each offset screen (offset_pts [j]), one-bit data representing the direction of the offset (offset_direction [j]), and 6-bit data representing the offset value (offset_value [j]) are presented as installation information. Also 5-bit data representing the time intervals for the playback time of the auxiliary offset screen (sub_offset_rate [j]), 5-bit data representing the number of auxiliary offset screens (number_of_sub_offsets [j]), single-bit data representing the offset direction set in each sub-offset screen (sub_offset_direction [k]), and 6-bit data representing the offset value set in each sub-offset screen (sub_offset_value [k]) is described as setting information.

Each playlist unit of a playlist file with “offset_metadata ()”, as described above, has an identifier for header data and menu data of the AV stream to be reproduced, described associated with data defining a clip data file and time information representing the reproduced portion of the AV stream . Accordingly, the offset identifiers are associated with the header data and the menu data of the AV stream to be reproduced.

It should be noted that if the offset information is not set in the header data and menu data to be reproduced, 0 is described as an offset identifier. In other words, a suitable offset identifier has a value from 1 or more to 8 or less, therefore, if the offset identifier is 0, the offset information is not set. Also, the identifier of the bias of the menu data during the execution of the BD-J object is determined by the PPI. Accordingly, the offset identifier is associated with the menu data when the BD-J object is executed.

Example playback device configuration

FIG. 15 is a block diagram illustrating a configuration example of a reproducing apparatus 260 for reproducing a disc 251 onto which a playlist file including the description “offset_metadata ()” shown in FIG. 14 is recorded.

Of the configurations shown in FIG. 15, configurations similar to those shown in FIG. 6 are denoted by the same reference numerals. A duplicate description will be omitted accordingly.

The configuration of the reproducing device 260 of FIG. 15 is mainly different from the configuration of the reproducing device 20 of FIG. 6 in that the control unit 261 is presented in place of the control unit 22, and in that the reproducing unit 262 is presented in place of the reproducing unit 23.

The control unit 261 controls the reproducing unit 23 in accordance with the commands from the input unit 21 by executing a predetermined program. For example, the control unit 261 submits a playlist file recorded on the disc 251 to the 3D display data generation unit 36 in accordance with a command from the input unit 21 for 3D playback of the disk 251. Also, the control unit 261 provides an offset identifier, for example, to the generation unit 271 3D display data following the BD-J object file recorded on the disk 251.

The configuration of the reproducing unit 262 mainly differs from the configuration of the reproducing unit 23 of FIG. 6 in that the 3D display data generating unit 271 is presented in place of the 3D display data generating unit 36.

Similarly to the 3D display data generation unit 36 of FIG. 6, the 3D display data generation unit 271 holds playlist files filed from the control unit 261 in the internal memory (not shown). Also, the 3D display data generation unit 271 creates display data for the left eye and the display data for the right eye from the video data supplied from the video generation unit 34, and the header data and menu data supplied from the graphics generation unit 35.

In particular, similarly to the 3D display data generation unit 36 of FIG. 6, the 3D display data generation unit 271 generates image data obtained as a result of the shift of the main image corresponding to the video data in the increments of the screens in one direction from the left and right directions to a predetermined value displacement, as video data for the left eye, and creates image data obtained as a result of a shift in the other direction, as video data for the right eye.

Also, the 3D display data generation unit 271 recognizes from the playlist file contained in the built-in memory, an offset identifier of the data of the headers to be played. The 3D display data generation unit 271 searches for the setting information corresponding to the offset identifier from “offset_metadata ()” in the playlist file and creates header data for the left eye and the right eye from the header data supplied from the graphic generation unit 35 based on the setting information.

Similarly, when a movie object is executed, the 3D display data generation unit 271 generates menu data for the left eye and for the right eye based on the setting information corresponding to the offset identifier of the menu data to be reproduced, which are described in the playlist file. On the other hand, when the movie object is executed, the 3D display data generation unit 271 creates menu data for the left eye and for the right eye based on the setting information corresponding to the displacement identifier supplied from the control unit 261.

The 3D display data generation unit 271 combines the video data, the header data and the menu data for the left eye and the right eye, which are thus created, into data for each eye. The 3D display data generation unit 271 supplies the left eye display data and the right eye display data as a result to the display unit 51 as 3D display data.

Functional example of a reproducing device

16 is a diagram illustrating an example of a functional implementation of the reproducing device 260 when executing an object BD-J.

Hardware 281 corresponds to an input unit 21, a reproducing unit 262, a memory unit 24, and so on.

When installing the disk 251 on the hardware 281, the firmware 282 controls the hardware 281 to read the index file from the disk 251. The firmware 282 further stores the index file on the hardware 281.

Also, firmware 282 reads the index file from hardware 281 and recognizes the type and number of the object corresponding to the title number to be processed, which are described in the index file. In the example of FIG. 16, the type of this object is a BD-J object.

The firmware 282 controls the hardware 281 based on the number of the BD-J object corresponding to the title number to be processed in order to read the BD-J object to be processed from the disk 251, which is then stored on the hardware 281. After recognizing the BD-J application 285 to be executed based on this BD-J object, the firmware 282 activates Java VM 284 (registered trademark). The firmware 282 then downloads the BD-J application 285 to the Java VM 284 (registered trademark). It should be noted that the placement can be done when the Java VM 284 (registered trademark) is activated between the installation of the disk 251 on the hardware 281 and the recognition of the application 285 BD-J to be executed.

Also, the firmware 282 controls the hardware 281 in response to a call to the playlist read function from the OS 283 in accordance with the call PPI for reading the playlist file by the BD-J application 285 to read the playlist file from the disk 251 and store it.

Further, the firmware 282 controls the hardware 281 in response to a call to the offset reading function from the OS 283 in response to a call to the PPI to bias the settings by the BD-J application 285 (hereinafter referred to as the offset setup PPI) to set the offset information for the menu data.

According to a function received from Java VM 284 (registered trademark), OS 283 calls a function with respect to firmware 282 corresponding to that function. For example, according to the playlist read function and the offset setting function received from Java BM 284 (registered trademark), in accordance with the call to the read list PPI and offset setting PPI from the BD-J application 285, the OS 283 calls the play list read function and an offset setting function with respect to the firmware 282 in accordance with this playlist reading function and an offset setting function.

Java BM 284 (registered trademark) interprets the functions corresponding to the PPI that is invoked by the BD-J application 285 and notifies the OS 283. For example, Java BM 284 (registered trademark) interprets the function in accordance with the read list PPI and PPI the offset settings that were read by the BD-J application 285 and constitutes a notification to OS 283 about the playlist read function and the offset setting function.

Appendix 285 BD-J calls the PPI specified by Java VM 284 (registered trademark) in relation to Java VM 284 (registered trademark). For example, the BD-J application 285 makes a call to the read-list PPI or offset setting PPI for Java VM 284 (registered trademark).

Reproduction processing

17 is a flowchart for describing an offset setting performed by the reproducing apparatus 260 when executing the BD-J object. This implementation of the offset setting begins when the firmware 282 downloads the BD-J application 285, which sets the offset information on the Java VM (registered trademark) 284, for example.

The implementation of steps S71 to S73 is similar to the implementation of steps S31 to S33 of FIG. 8, so a description thereof will be omitted.

After performing step S73 in step S74, the BD-J application 285 makes a call to the Java VM 284 (registered trademark) for the offset setting PPI. Accordingly, Java VM 284 (registered trademark) recognizes the offset setting function as a function corresponding to the offset setting PPI, and notifies the OS 283. OS 283 calls the offset setting functions with respect to the firmware 282 corresponding to the offset setting function. Thus, the firmware 282 notifies the hardware 281 of a predefined offset identifier.

In step S75, the hardware 281 recognizes an offset identifier supplied from the firmware 282 as an offset identifier for the menu data to be reproduced. Also, the hardware 281 searches for the stored playlist file and recognizes an offset identifier of the data of the titles to be played.

In step S76, hardware 281 reads the setting information corresponding to the offset identifier recognized in step S75 from the “offset_metadata” of the stored playlist file. The hardware 281 further obtains a playback time point of each auxiliary bias screen based on the setting information from the data representing the playback time of each bias screen and the data representing the time intervals of the playback time of the auxiliary bias screens.

In step S77, hardware 281 makes a determination as to whether the current playback object is an offset screen or an auxiliary offset screen. In particular, the hardware 281 determines whether the current playback time point from the setup information read in step S76 is the playback time point that represents data representing the playback time of the offset screen, or the playback time of the auxiliary offset screen received in step S76.

In the case where it is determined in step S77 that the current playback object is an offset screen or an auxiliary offset screen, in step S78, the hardware 281 sets, from the setting information read in step S75, the offset information of the offset screen or the auxiliary offset screen as information about the current offset. After performing step S78, the process proceeds to step S79.

On the other hand, in the case where it is determined in step S77 that the current playback object is neither an offset screen nor an auxiliary offset screen, step S78 is skipped and the process proceeds to step S79.

It should be noted that step S77 and step S78 are performed for each of the header data and the menu data.

In step S79, the hardware 281 creates 3D display data including menu data and header data for the left eye and for the right eye, based on the offset information set as the current offset information, and also creates audio data.

In step S80, the hardware 281 displays a 3D image based on the 3D display data in the display unit 51 and outputs audio corresponding to the audio data from the speaker 52.

In step S81, software 282 makes a determination as to whether to complete the bias setting in accordance with a command from OS 283. If it is determined in step S81 not to complete the bias setting, the process returns to step S74, and the subsequent process repeats. until a determination is made to complete the installation of the offset. However, it should be noted that the processing of step S74 is performed as necessary.

On the other hand, if a determination is made in step S81 to end the bias setting, the process ends.

It should be noted that, while in the above description, the offset identifier of the header data and the menu data of the AV stream is described in the playlist file, placement can be made when this offset identifier is determined by the navigation command described in the movie object or menu data segment. In this case, the offset information setting can be dynamically changed while the movie object is being executed.

As described above, the reproducing device 260 first reads and holds the playlist file and sets the offset information each time the reproduction of the offset screen and the auxiliary offset screen described in the offset information database in the playlist file comes closest. Thus, as shown in FIG. 15, the reproducing apparatus 260 can set the offset information in relation to the desired screen 151. Accordingly, the video format of the disc 251 including the offset information database can be called a 3D video format suitable for 3D display of titles and menu buttons.

Also, with the playlist file recorded on the disc 251, an offset identifier is provided for the setting information, therefore, determining the setting information of the header data and the menu data with the offset identifier makes it unnecessary to describe the same setting information many times. Accordingly, the data value of the playlist file can be reduced.

For example, even in the case where the offset information is set for each AV stream, all that needs to be described with respect to the playlist file of the disc 251 is to set the offset information, which is not redundant. Accordingly, the data value of the playlist file can be reduced compared to the case when the offset information is fully described for each AV stream, as is the case with the playlist file on the disk 11. As a result, an AV stream with a sufficient length can be processed with using a single playlist file.

It should be noted that in the case where offset information is set for each AV stream, placement can be made, for example, when the vertical position with respect to the display plane of the Japanese headers is different from the vertical position with respect to the display plane of the English headers. This is especially useful when the display positions of Japanese headings and English headings are different.

Also, the offset information in the present embodiment is set so that the titles and menu buttons for the right eye and the titles and menu buttons for the left eye do not go beyond the edge of the screen. In other words, for example, in the case where the header data for the headers 481 and 482 are recorded on the disc, as shown in section A in FIG. 18, offset information that will shift the headers 481 and 482 to the headers 491 and 492 shown in section B to Fig. 18 is not installed.

Further, in accordance with the above description, the playlist file is supplied from the control unit 22 (261) to the 3D display data generation unit 36 (221, 271), and the 3D display data generation unit 36 (221, 271) holds the playlist file during the internal memory, but the playlist file may be stored in the memory unit 24. In this case, the control unit 22 (261) searches for the offset information corresponding to the time of reproduction of the header data and the menu data to be reproduced, and supplies this offset information to the 3D display data generation unit 36 (221, 271). The 3D display data generation unit 36 (221, 271) further creates 3D display data based on the displacement information.

Also, in accordance with the above description, the 3D display data generation unit 36 (221, 271) uses video data to perform 2D display of the main image to create video data for the right eye and for the left eye, but in the case where the video data for the right eye and for the left eye are recorded on the disc 11 (201, 251), the video data for the right eye and for the left eye are used as they are to create 3D display data, similar to the fourth to sixth embodiments described below.

Fourth Embodiment

Disk Run Example

19 is a diagram illustrating an embodiment of a fourth embodiment of a disc to which the present invention is applied.

The disk 501 in FIG. 19 has “offset_metadata ()” shown in FIG. 5, described in a separate file from a playlist file (PLAYLIST / XXXXX.mpls), in contrast to the disk 11 described above (201, 251).

In particular, as shown in FIG. 19, “offset_metadata ()” is recorded on the disc 501 as an offset file (OFFSET / XXXXX.ofmd) of a directory separate from the playlist file, separate from the playlist file (PLAYLIST / XXXXX.mpls) . It should be noted that X is an arbitrary digit from 0 to 9.

Also, with respect to the disc 501, the reference file data is described in the playlist file, which is data defining an offset file referenced during playback in accordance with the playlist file.

Further, an AV stream consisting of TS video data packets for 3D display of the main images, which are encoded in MPEG2, MPEG-4 AVC, VC1, MUS (video coding of many viewpoints) and the like, is multiplexed as a stream file to disk 501 according to ISO 13818-2, and related audio data, header data for 2D display of the title, and menu data for 2D display of menu buttons. In other words, the video data included in the AV stream recorded on the disc 501 is not data for 2D display of the main image, but data for 3D display.

It should be noted that since “offset_metadata ()” is recorded as an offset file for a directory other than the directories of the playlist file, it can be written as another file (PLAYLIST / XXXXX.ofmd) in the same directory as the playlist file .

Example playback device configuration

FIG. 20 is a block diagram illustrating an example configuration of a reproducing apparatus 510 for reproducing a disc 501 of FIG. 19.

Of the configurations shown in FIG. 20, configurations similar to those shown in FIG. 6 are denoted by the same reference numerals. A duplicate description will be omitted accordingly.

The configuration of the reproducing device 510 of FIG. 20 mainly differs from the configuration of the reproducing device 20 of FIG. 6 in that instead of the control unit 22 and the reproducing unit 23, the control unit 511 and the reproducing unit 512 are provided;

The control unit 511 controls the reproducing unit 23 in accordance with the commands from the input unit 21 by executing a predetermined program. For example, the control unit 511 reads the playlist file recorded on the disc 501 in accordance with a command from the input unit 21 for 3D playback of the disc 501 and holds it in the memory unit 24.

Also, the control unit 511 reads the offset file based on the link file data described in the playlist file stored on the memory unit 24 and holds it in the memory unit 24. The control unit 511 further searches for offset information corresponding to a time point for reproducing data of the titles to be reproduced from “offset_metadata ()” in the playlist file. Similarly, the control unit 511 searches for offset information corresponding to the current point in time of playback of the menu data to be reproduced from “offset_metadata ()” in the playlist file. The control unit 511 then provides the offset information of the header data and the offset information of the menu data obtained as a search result to the reproducing unit 512.

The configuration of the reproducing unit 512 mainly differs from the configuration of the reproducing unit 23 in that instead of the PID filter 33, the video generation unit 34 and the 3D display data generation unit 36, the PID filter 521, the video generation unit 522 and the 3D display data generation unit 523 are provided.

The PID filter 521 extracts packets for each of the left-eye video data, right-eye video data, header data, menu data and audio data included in the AV stream based on the packet identifier (PID) packet of the AV stream from the read buffer 32.

The PID filter 521 extracts PEP packets from each of the extracted packets for each video for the left eye, video for the right eye, header data, menu data, and audio data. The PID filter 521 further supplies the PEP video data packets for the left eye and for the right eye to the video generation unit 522 and supplies the PEP packets of the header data and menu data to the graphic generation unit 35. The PID filter 521 also supplies PEP audio data packets to the audio generation unit 37.

The video generation unit 522 decodes the PEP video data packets for the left eye and the right eye supplied from the PID filter 521, and supplies the video data for the left eye and the right eye, resulting in the 3D display data generation unit 523.

The 3D display data generating unit 523 generates header data for the left eye and the right eye based on the offset information for the header data supplied from the control unit 511. Similarly, the 3D display data generating unit 523 creates menu data for the left eye and for the right eye on based on the offset information for the menu data filed from the control unit 511.

The 3D display data generation unit 523 combines the header data and the menu data for the left eye and the right eye, which are created in this way, and the video data for the left eye and the right eye, supplied from the video generation unit 522, into data for each eye. The 3D display data generating unit 523 supplies the display data for the left eye and the display data for the right eye as a result to the display unit 51 as 3D display data.

Detailed description of the 3D display data generation unit

FIG. 21 is a flowchart illustrating a detailed embodiment of the 3D display data generating unit 523 of FIG. 20.

As shown in FIG. 21, the 3D display data generating unit 523 consists of a title plane 531, a menu plane 532, a left eye display generating unit 533, and a right eye display generating unit 534.

The header plane 531 holds the header data supplied from the header generation unit 41 (FIG. 20) of the graphics generation unit 35.

The menu plane 532 holds the menu data filed from the menu generation unit 42 (FIG. 20) of the graphics generation unit 35.

The left eye display data generating unit 533 consists of a left eye video plane 541, a transmitting unit 542 adding an offset unit 543 of a transmitting unit 544, a uniting unit 545, a transmitting unit 546, adding an offset unit 547, a transmitting unit 548 and a uniting unit 549.

The left eye video plane 541 holds the left eye video supplied from the 3D video generation unit 34.

The transmitting unit 542 reads video data for the left eye, which are held in the plane 541 of the video for the left eye. The transmitting unit 542 converts the read video data for the left eye so that the main image for the left eye is transmitted with a predetermined transmittance (1-α _1L ). The transmitting unit 542 supplies the video data for the left eye after conversion to the combining unit 545.

An offset adding block 543 reads the header data from the header plane 531. The offset adding unit 543 creates left-eye header data from the read header data based on the offset data of the header data filed from the control unit 511 of FIG. 20. In particular, the offset-adding unit 543 creates header data resulting from the shift of the headers in the screen increments corresponding to the read header data in the direction of the offset information shifting by the offset value as the header data for the left eye. The offset-adding block 543 supplies the left-eye header data to the transmitting block 544.

The transmitting unit 544 converts the video data for the left eye filed from the offset-adding unit 543, so that the header for the left eye is transmitted with a predetermined transmittance α _1L . The transmitting unit 544 provides header data for the left eye after conversion to the combining unit 545.

The combining unit 545 combines the video data for the left eye that is supplied from the transmitting unit 542 and the header data for the left eye supplied from the transmitting unit 544 and provides the resulting data to the transmitting unit 546.

The transmitting unit 546 converts the data from the combining unit 545 so that the image corresponding to these data is transmitted with a transmittance (1-α _2L ), and feeds them to the combining unit 549.

An offset adding unit 547 reads the menu data from the menu plane 532. The offset adding unit 547 creates menu data for the left eye from the read menu data based on the offset information of the menu buttons supplied from the control unit 521 of FIG. 21. In particular, the offset-adding unit 547 creates menu data resulting from the shift of the menu buttons in screen increments corresponding to the read data of the menu, in the direction of the offset information shift by the offset value, as the menu data for the left eye. The offset-adding block 547 provides the left-eye menu data to the transmitting block 548.

The transmitting unit 548 converts the menu data for the left eye, filed from the offset-adding unit 547, so that the menu buttons for the left eye are transmitted with a predetermined transmittance α _2L . The transmitting unit 548 supplies the menu data for the left eye after conversion to the combining unit 549.

The combining unit 549 combines the data that is supplied from the transmitting unit 546 and the menu data supplied from the transmitting unit 548, and outputs the resulting data as display data for the left eye.

The right-eye display data generating unit 534 consists of a right-eye video plane 551, a transmitting unit 552, adding an offset unit 553, a transmitting unit 554, a combining unit 555, a transmitting unit 556, adding an offset unit 557, a transmitting unit 558 and a combining unit 559 The implementation of each part of the right-eye display data generating unit 534 is similar to the implementation of each part of the left eye display data generating unit 533, except that the object being processed is data for the right eye eyes, so the description will be omitted.

Functional example of the execution of a reproducing device

FIG. 22 is a diagram illustrating an example of a functional embodiment of a reproducing apparatus 510 when executing an object BD-J.

Of the configurations shown in FIG. 22, configurations similar to those shown in FIG. 7 are denoted by the same reference numerals. A duplicate description will be omitted accordingly.

The configuration of FIG. 22 mainly differs from the configuration of FIG. 7 in that instead of hardware 71 and firmware 72, hardware 581 and firmware 582 are provided.

Hardware 581 corresponds to an input unit 21, a reproducing unit 512, a memory unit 24, and so on. Also, firmware 582, OS 73, Java BM 74 (registered trademark), and BD-J application 75 correspond to control unit 511.

When installing the disk 501 on the hardware 581, the firmware 582 controls the hardware 581 to read the index file from the disk 501 of FIG. 7. Firmware 582 further stores the index file on hardware 581.

Also, similarly to the firmware 72, the firmware 582 reads the index file from the hardware 581 and recognizes the type and number of the object corresponding to the title number to be processed, which are described in the index file. In the example of FIG. 22, the type of this object is a BD-J object.

Similar to the firmware 72, the firmware 582 controls the hardware 581 based on the number of the BD-J object corresponding to the number of the title to be processed to read the BD-J object to be processed from the disk 501, which is then stored on the hardware 581. After recognizing the BD-J application 75 to be executed based on this BD-J object, the firmware 582 activates Java VM 74 (registered trademark), similar to the firmware 72. The firmware 582 then downloads the BD-J application 75 to the Java VM 74 (registered trademark), similar to the firmware 72. It should be noted that the placement can be made when the Java BM 74 (registered trademark) is activated during the time between installing disk 501 on hardware 581 and recognizing the BD-J application 75 to be executed.

Also, similar to the firmware 72, the firmware 582 controls the hardware 581 in response to a call to the playlist read function from the OS 73 corresponding to the call of the read list PPI by the BD-J application 75 to read the playlist file from disk 501 and store him.

Next, the firmware 582 controls the hardware 581, reads the offset file from the disk 501 based on the link file data described in the playlist file stored on the hardware 581. The firmware 582 searches for data corresponding to the time of playback of the header data and menu data to be reproduced from "offset_metadata ()" in this offset file. Firmware 582 provides header data offset information and menu data offset information that is found to hardware 581.

Reproduction processing

23 is a flowchart for describing an offset setting performed by the reproducing apparatus 510 when executing an object BD-J. This implementation of the offset setting begins when the firmware 582 downloads the BD-J application 75, which sets the offset information to the Java VM 74 (registered trademark), for example.

The implementation of steps S101 to S103 in Fig.23 is similar to the implementation of steps S31 to S33 in Fig.8, therefore, their description will be omitted.

In step S104, the firmware 582 controls the hardware 71 based on the link file data described in the playlist file recorded on the hardware 71 and reads the offset file from the disk 501. The firmware 582 then stores the read offset file on the hardware 71 .

In step S105, the firmware 582 searches for “offset_metadata” to be reproduced from the stored offset file, similarly to the implementation of step S34 in FIG. 8.

In step S106, the firmware 582 determines whether the current playback time is the playback time specified in “offset_pts” in “offset_metadata” found in step S105. In the case where it is determined in step S106 that the current playback time point is not the playback time point indicated in “offset_pts” in the “offset_metadata” in which the search was performed, the process is performed until the current playback time point becomes a time point the playback specified in "offset_pts" in the "offset_metadata" in which the search was performed.

On the other hand, in the case where it is determined in step S106 that the current playback time point is the playback time point indicated in “offset_pts” in the “offset_metadata” in which the search was performed, the firmware 582 provides the offset information represented by “ offset_flag "and" offset_value ", in relation to the menu data and the header data described in accordance with the current point in time of playback, to the hardware 581.

Next, in step S107, the hardware 581 sets the offset information for the menu data from the firmware 582 as the offset information for the menu data of the current playback time point and sets the offset information for the header data as the offset information for the header data of the current playback time point.

The implementation of steps S108 to S110 is similar to the implementation of steps S37 to S39 of FIG. 8, so a description thereof will be omitted.

It should be noted that in the fourth embodiment, “offset_metadata ()” shown in FIG. 5 is recorded to the disk 501 as an offset file, but “offset_metadata ()” shown in FIG. 10 or FIG. 14 can be written to drive 501 as an offset file. In this case, the link file data is described in the playlist file or defined by the PPI. The reproducing apparatus 510 reads the offset file based on this reference file data and sets the offset information based on the “offset_metadata ()” of the offset file, similarly to the second and third embodiments.

Fifth Embodiment

Video Execution Example

24 is a diagram illustrating an example embodiment of video data recorded on a disc to which the present invention is applied in accordance with a fifth embodiment.

It should be noted that on the disk in accordance with the fifth embodiment recorded video data for the left eye, which is encoded using MVC or the like, as video data, similar to the disk 501.

24 is a diagram illustrating an example of executing a first dependent block (frame) in a display order in each GOP (group of frames) of right-eye video data, which is a dependent stream encoded using MVC.

As shown in FIG. 24, in the first dependent unit, in the order of displaying video data for the right eye in the GOP, the dependent separator, a subset of sequence parameter values, frame parameter value, additional spreading information and one or more segments are arranged in order from the beginning.

The dependent delimiter is the initial code indicating the head element of the dependent block. The dependent delimiter includes, for example, data indicating the type of segments included in the dependent block.

A subset of sequence parameter values is a header that includes data on the entire sequence. A subset of sequence parameter values includes, for example, data indicating a video data profile for the right eye and data indicating a video data level for the right eye. Also, for example, a subset of the values of the sequence parameters includes the data necessary to calculate the SEC (frame order counter) (POC). SEC is data indicating the display order of frames.

The value of the frame parameters is the header, which includes data related to the frames. For example, the value of the frame parameters includes the data needed to calculate the SEC.

Additional extension information is data indicating additional information that is not necessary for decoding a VCL (video encoding layer). Additional extension information can be classified into user additional extension information, which is data that is defined by the user who creates the disk (messages of additional extension information of user information BD in the additional extension markup information of expandable MVC), and other information (other messages of additional extension information in extensible markup information for extensible MVC). As for the disk in accordance with the fifth embodiment, at least the last of the described "offset_metadata ()" is described as user additional extension information. The segment is the video image of the main image for the right eye, encoded using MVC, and is the actual frame data.

After one or more segments, the Filler Data, End of Sequence, and End of Stream are positioned as needed.

Padding data is data added to control the size of the data. The end of a sequence is data representing the end of a sequence. The end of the stream is data representing the end of the video data for the right eye.

It should be noted that although the description is made for video data for the right eye, which is a dependent stream encoded using MVC, and video data for the left eye is the basic stream, placement can be done when the video data for the right eye is the basic stream, and video data for the left the eyes are a dependent stream.

Also, "offset_metadata ()" can be described as data other than user additional extension information of additional extension information compared to those described as user additional extension information of the dependent stream. Further, “offset_metadata ()” may be described as additional extension information of the base stream.

Example description for offset_metadata ()

FIG. 25 is a diagram illustrating an example of a description of “offset_metadata ()” described as user additional extension information of FIG. 24.

As shown in FIG. 25, an offset information database is described in “offset_metadata ()”.

Specifically, as shown in section A of FIG. 25, the “offset_metadata ()” describes the frame rate (frame_rate) of the video data for the right eye, which includes “offset_metadata (),” and the PTS (presentation time stamp) (offset_start_PTS) of the head frame in the order of displaying video data for the right eye. The timing of the playback of the offset screens can be determined by the frame rate and PTS. Also, as shown in section A of FIG. 25, “offset_metadata ()” describes the number of frames (number_of_frames) of the GOP for which “offset_metadata ()” is included in the additional extension information. Further, as shown in section A in FIG. 25, the “offset_metadata ()” describes the number of types of offset information for the header (number_of_PG_offset_sequence) set for that GOP and the number of types of offset information for the menu buttons (number_pf_IG_offset_sequence) set regarding that GOP. The type of offset information set during playback of the video data is determined by the playlist file, and so on.

Also, as shown in section A in FIG. 25, “offset_metadata ()” describes offset information (PG_offset_sequence) for each type of header offset information and offset information (IG_offset_sequence) for each type of menu button offset information. Data indicating the direction of the offset (offset_direction_flag) and data indicating the value of the offset (offset_value) set in the offset screen are described as offset information (PG_offset_sequence, IG_offset_sequence), as shown in section B in FIG. 25 and section C on Fig.25.

Example playback device configuration

26 is a block diagram illustrating an example embodiment of a reproducing apparatus 610 for reproducing a disc 601 on which video data for the right eye is recorded.

Of the configurations shown in FIG. 26, configurations similar to those shown in FIG. 20 are denoted by the same reference numerals. A duplicate description will be omitted accordingly.

The configuration of the reproducing device 610 of FIG. 26 is mainly different from the configuration of the reproducing device 510 of FIG. 20 in that the control unit 611 is presented in place of the control unit 511, and in that the reproducing unit 612 is presented in place of the reproducing unit 512.

The control unit 611 controls the reproducing unit 612 in accordance with the commands from the input unit 21 by executing a predetermined program. For example, similarly to the control unit 511 of FIG. 20, the control unit 611 reads a playlist file recorded on the disc 601 in accordance with a command from the input unit 21 for 3D playback of the disc 601 and holds it in the memory unit 24. The control unit 611 provides type information, which is information defining a type of offset information for the title data and the menu data to be reproduced described in the playlist file.

The configuration of the reproducing unit 612 of FIG. 26 is mainly different from the configuration of the reproducing unit 512 of FIG. 20 in that the video generating unit 621 is presented instead of the video generating unit 522.

Similarly to the video generation block 522 of FIG. 20, the video generation block 621 decodes the PEP video packets for the left eye and the right eye, extracted by the PID filter 521, and supplies the video data for the left eye and the right eye, resulting in the generation block 523 3D display data. Also, the video generation unit 621 searches for offset information for header data and menu data corresponding to the current instant of playback time based on the frame rate and PTS in “offset_metadata ()” included in the user additional extension information obtained by decoding and type information from the control unit 611, and feeds to the 3D display data generating unit 36.

Functional example of a reproducing device

FIG. 27 is a diagram illustrating an example of a functional embodiment of a reproducing apparatus 610 when executing an object BD-J.

Of the configurations shown in FIG. 27, configurations similar to those shown in FIG. 22 are denoted by the same reference numerals. A duplicate description will be omitted accordingly.

The configuration of FIG. 27 mainly differs from the configuration of FIG. 22 in that the hardware 731 and the firmware 732 are presented in place of the hardware 581 and the firmware 582.

Hardware 731 corresponds to an input unit 21, a reproducing unit 612, a memory unit 24, and so on. Also, firmware 732, OS 73, Java VM 74 (registered trademark) and BD-J application 75 correspond to control unit 611.

As with the firmware 72 in FIG. 7, when installing the disk 601 on the hardware 731, the firmware 732 controls the hardware 731 to read the index file from the disk 601. The firmware 732 further stores the index file on the hardware 731.

Also, similar to firmware 72, firmware 732 reads the index file from hardware 731 and recognizes the type and number of the object corresponding to the title number to be processed, which are described in the index file. In the example of FIG. 27, the type of this object is a BD-J object.

Similar to the firmware 72, the firmware 732 controls the hardware 731 based on the number of the BD-J object corresponding to the title number to be processed to read the BD-J object to be processed from the disk 601, which is then stored on the hardware 731 After recognizing the BD-J application 75 to be executed based on this BD-J object, the firmware 732 activates the Java BM 74 (registered trademark), similar to the firmware the software 72. The firmware 732 then downloads the BD-J application 75 to the Java BM 74 (registered trademark), similar to the firmware 72. It should be noted that the placement can be made when the Java BM 74 (registered trademark) is activated during the time between installing disk 601 on hardware 731 and recognizing the 75 BD-J application to be executed.

Also, similar to the firmware 72, the firmware 732 controls the hardware 731 in response to a call to the playlist read function from the OS 73 corresponding to the call of the read list PPI by the BD-J application 75 to read the playlist file from disk 601 and store him. The firmware 732 provides information about the type of title data and menu data to be reproduced described in the playlist file to the hardware 731.

Reproduction processing

FIG. 28 is a flowchart for describing an offset setting made by the reproducing apparatus 610 when the object BD-J is executed. This implementation of the offset setting starts when the firmware 732 downloads the BD-J application 75, which sets the offset information to the Java VM 74 (registered trademark), for example.

The implementation of steps S151 to S153 in FIG. 28 is similar to the implementation of steps S31 to S33 in FIG. 8, so a description thereof will be omitted.

After performing step S153 in step S154, the firmware 732 reads information about the data type of the titles and the menu data to be reproduced from the playlist file stored on the hardware 731 and feeds it to the hardware 731.

In step S155, the hardware 731 determines whether the current playback time is the playback time of the offset screen indicated by the PTS and the frame rate in “offset_metadata” included in the right-eye video to be reproduced. In the case where it is determined in step 5155 that the current playback time is not the playback time of the offset screen, the process is performed until the current playback time is the playback time of the offset screen.

In the case where it is determined in step S155 that the current playback time point is an offset screen, the process proceeds to step S156. In step 5156, the hardware 731 sets the offset information for the menu data corresponding to the playback time point and the type information from the firmware 732 as the offset information for the menu data of the current playback time point and sets the offset information for the header data corresponding to type information, as offset information for the header data of the current playback time point. The process then proceeds to step S157.

The implementation of steps S157 to S 159 is similar to the implementation of steps S37 to S39 of FIG. 8, so a description thereof will be omitted.

Sixth Embodiment

Example playback device configuration

29 is a block diagram illustrating an embodiment of a sixth embodiment of a reproducing apparatus to which the present invention is applied.

Of the configurations shown in FIG. 29, configurations similar to those shown in FIG. 20 are denoted by the same reference numerals. A duplicate description will be omitted accordingly.

The configuration of the reproducing device 800 of FIG. 29 is mainly different from the configuration of the reproducing device 510 of FIG. 20 in that the control unit 811 is presented in place of the control unit 511, and in that the reproducing unit 812 is presented in place of the reproducing unit 512. Instead of creating 3D display data the reproducing apparatus 800 provides video data for the left eye and for the right eye, header data, menu data, and offset information for header data and menu data, which serve as the basis for 3D display data tions on the display unit 821, and 3D display data are generated on the display unit 821.

Specifically, the control unit 811 of the reproducing apparatus 800 controls the reproducing unit 812 in accordance with the commands from the input unit 21 by executing a predetermined program. For example, the control unit 811 reads the playlist file recorded on the disk 11 in accordance with a command from the input unit 21 and holds it in the memory unit for 3D playback of the disk 11.

The control unit 811 also searches for offset information corresponding to the time of reproduction of the title data and the menu data to be reproduced from “offset_metadata ()” in the playlist file held in the memory unit 24. The control unit 811 then provides the header data bias information and the menu data bias information obtained as a search result to the reproducing block 821.

The configuration of the reproducing unit 812 mainly differs from the configuration of the reproducing unit 512 of FIG. 20 in that there is no 3D display data generating unit 523.

Video data for the left eye and for the right eye obtained from the video generating unit 522 of the video reproducing unit 812, the header data created by the header generating unit 41, and the menu data created by the menu generating unit 42 are transmitted to the display unit 821 in a format such as HDMI ( high-definition multimedia interface) and the like.

Similarly to the 3D display data generating unit 523 of FIG. 20, the display unit 821 creates display data for the left eye and display data for the right eye from video data supplied from the video generation unit 522, and header data and menu data supplied from the graphic generation unit 35 based on the bias information of the header data and the bias information of the menu data filed from the control unit 811. The display unit 821 then outputs based on the 3D display data. As a result, the user can see the 3D image.

It should be noted that when the reproducing apparatus 800 of FIG. 29 is a reproducing apparatus for reproducing a disc 11, the above reproducing apparatus for reproducing other discs 201, 251, 501 and 601 may also be adapted to create 3D display data on a display unit instead of creating 3D display data on their own playback devices.

Description of a method for generating 3D display data

30 is a diagram for describing a method for generating 3D display data.

As shown in section A in FIG. 30, three groups of data consisting of video data for the left eye, header data for the left eye and menu data for the left eye are combined to create display data for the left eye from 3D display data. Also, as shown in section B of FIG. 30, three groups of data consisting of video data for the right eye, header data for the right eye, and menu data for the right eye are combined to create display data for the right eye. It should be noted that the order of overlapping video data, header data and menu data for each eye is from the bottom up video data, header data and menu data.

Although this is omitted in the drawings, the reproducing apparatus 210 (260, 510, 610, 800) sets the offset information each time the reproduction time described in the offset information occurs, as with the offset setting in FIG. 8, FIG. 13, Fig.17, Fig.23 or Fig.28 during the execution of movie objects.

Also, “reproducing” the header data in the above description means reading the header data recorded on the disc and displaying the headers based on the header data. Also, “reproducing” the menu data in the above description means reading the menu data recorded on the disc when the movie object is executed and displaying the menu buttons based on the menu data, and when the movie object is executed, creating the menu data and the menu button data based on the menu data.

Although the present embodiment has been described with respect to menu buttons generated by the BD-J application, headers, animations and so on can be created.

It should be noted that in relation to the present description, the steps describing the program stored on the storage medium include an implementation executed in a time sequence, of course, following this order, but are not reduced to an implementation in a time sequence, and also include an implementation, executed in parallel or separately.

Embodiments of the present invention are not limited to the embodiments described above, and various modifications may be made without departing from the spirit of the present invention.

List of Reference Items

11 - Disc

20 - Playback device

22 - Control unit

31 - Drive

36 - 3D display data generation unit

Claims (7)

1. A reproducing device, characterized in that it is made with the possibility when reproducing data of a data structure containing:
image data used for 2D display of an auxiliary image containing a title or menu button, and
a playlist file containing a table in which, for said auxiliary image corresponding to said image data, offset information is described comprising an offset direction representing a shift direction of an image L for the left eye and an image R for the right eye used for 3D display of the auxiliary image , and an offset value representing the amount of shift, depending on the moment the auxiliary image is reproduced;
read and save said playlist file with said table included in said data structure data;
read said image data included in said data structure data; and
in the case where the reproduction time of said image data is a reproduction moment included in said table, to create and output image data for said image L and said image R from said image data based on the described offset information corresponding to said reproduction moment. 2. The reproducing device according to claim 1, characterized in that the information about the offset of said auxiliary image is described in units of screen offsets in said table corresponding to the time of playback of the auxiliary image in units of screen offsets;
in this case, when the playback time of said image data in screen offset units is the playback moment included in said table, the reproducing device is configured to create and output image data for said image L and said image R in screen offset units from image data in screen offset units based on the described offset information corresponding to said reproduction time. 3. The reproducing device according to claim 1, characterized in that the table describes information about the offset of said auxiliary image of the first screen corresponding to the time of reproduction of the first screen, and also describes information about the offset of said auxiliary image of the second screen at the time of playback, remote from said the moment of reproduction of the said first screen by a predetermined interval, moreover, the information about the offset of the auxiliary image of the second screen corresponds to adannomu interval;
wherein the reproducing device is configured to
in the case when the reproduction time of said image data in screen offset units is the reproduction time of the first screen, set the described offset information corresponding to said reproduction moment as current offset information
in the case where the reproduction time of said image data in screen offset units is the reproduction time of the second screen, set the offset information described as current offset information corresponding to said reproduction moment and corresponding to said predetermined interval, and
create and output, on the basis of the displacement information, image data of said image L and said image R in units of screen displacement from said image data in units of screen displacement. 4. The reproducing device according to claim 1, characterized in that the said playlist file contains many tables;
wherein each table is provided with an identifier, and the identifier corresponds to said image data;
wherein the reproducing device is configured to: read, on the basis of an identifier corresponding to image data to be reproduced, a table containing said identifier,
in the case where the reproduction time of said image data to be reproduced is a reproduction moment included in a readable table, set the described offset information corresponding to said reproduction moment as current displacement information, and
create and output, based on the displacement information, image data for said image L and said image R from image data to be reproduced. 5. The reproducing device according to claim 1, characterized in that it is configured to set said offset information so that said image L and said image R do not extend beyond the edge of the screen. 6. A reproducing method, comprising the steps performed by a reproducing apparatus when reproducing data of a data structure comprising:
image data for 2D display of an auxiliary image containing a title or menu button, and
a playlist file containing a table in which, for said auxiliary image corresponding to said image data, offset information is described comprising an offset direction representing a shift direction of an image L for the left eye and an image R for the right eye used for 3D display of the auxiliary image , and an offset value representing the amount of shift, depending on the moment the auxiliary image is reproduced;
at the same time at the mentioned stages:
reading and saving said playlist file with said table included in said data structure data;
reading said image data included in said data structure data; and
in the case where the reproduction time of said image data is a reproduction moment included in said table, image data for said image L and said image R are created and output from said image data based on the described offset information corresponding to said reproduction moment. 7. A medium for storing a program, characterized in that it contains a recorded program that causes the computer to execute data playback control of a data structure containing:
image data for 2D display of an auxiliary image containing a title or menu button, and
a playlist file containing a table in which, for said auxiliary image corresponding to said image data, offset information is described comprising an offset direction representing a shift direction of an image L for the left eye and an image R for the right eye used for 3D display of the auxiliary image , and an offset value representing the amount of shift, depending on the moment the auxiliary image is reproduced;
management process, comprising the stages in which:
reading and saving said playlist file with said table included in said data structure data;
reading said image data included in said data structure data; and
in the case where the reproduction time of said image data is a reproduction moment included in said table, image data for said image L and said image R are created and output from said image data based on the described offset information corresponding to said reproduction moment.

Images