JP2006287306A - Scenario data converter, scenario data conversion method, and recording medium for recording scenario data conversion program - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a scenario data converter whereby a user can easily produce a reproduction method without the need for the user being familiar with the standards when the user produces the reproduction method including complicated constraints specified by the standards such as a multi-angle. <P>SOLUTION: The scenario data converter and method is characterized by including: a scenario edit means whereby the user can edit a scenario without the need for being conscious of the constraints and a data structure specified by the standards through the assistance of the GUI and which outputs first scenario data with a high degree of extraction; and a data conversion means for inputting the first scenario data and outputting second scenario data described in the data structure defined by the standards. <P>COPYRIGHT: (C)2007,JPO&INPIT

Description

  The present invention relates to a data generation apparatus in authoring work of content recorded on an optical disc, and in particular, based on a data structure describing a content scenario such as a movie, an application layer format of a read-only optical disc such as a BD-ROM The present invention relates to a scenario data conversion device that converts data to a data structure corresponding to the

  Paid distribution of movie content using optical discs is an extremely large source of income for movie supply companies such as Hollywood. A generation device used for authoring by a video production professional is an indispensable device for distributing movie content on an optical disc, and higher performance is required than ever before. The authoring by the generating device is an operation of determining data arrangement according to the application layer standard of the optical disc when creating the master disc of the optical disc. Data determined by authoring is called a volume image, and the volume image includes a digital / digital stream compressed and encoded in accordance with the MPEG2 standard and a scenario for the digital stream.

  Conventional authoring has been performed with a read-only DVD (generally called DVD-Video) as a target (see, for example, Patent Document 1). However, in recent years, how to author for a read-only Blu-ray Disc (hereinafter referred to as BD-ROM), which will appear in the near future, has become a major concern. The greatest merit of distributing movie contents by BD-ROM is that movie contents can be distributed with high-definition image quality. Since the movie content can be reproduced with an image quality closer to that of a movie theater, it is most suitable for viewing on a 32-inch or 40-inch wide TV, and a real-oriented movie mania can be revived.

  The DVD-Video standard was formulated around 1995. The hardware performance of the computer at the time of formulation was considerably poorer than that at present, and DVD-Video was trying to realize the various playback controls that Hollywood movie production companies require on this poor performance hardware. We had to give various constraints to the digital stream scenario. As a result, the scenario of the digital stream is complicated and difficult to understand. For this reason, authoring users are required to be familiar with the limitations of the standard and to acquire advanced know-how when creating scenarios.

  On the other hand, BD-ROM is a standard that is currently being developed (March 2005). Compared to the time when DVD-Video was formulated, the hardware performance has been greatly improved at present, so many of the restrictions in DVD-Video can be useless. Therefore, the scenario data structure in the BD-ROM is expected to be simpler and clearer.

  Then, it is not so whether the data structure of the BD-ROM scenario is a simplification of the data structure of the DVD-Video scenario. Since DVD-Video is determined prior to the recording standard, there are places where the compatibility is not considered, whereas BD-ROM is intended to be compatible with the recording standard (BD-RE). Therefore, the data structure of the scenario is completely different from that of DVD-Video.

The volume image for BD-ROM is “similar to the volume image for DVD-Video”, but BD-ROM is also trying to realize the various playback controls that Hollywood production companies demand. The same applies to DVD-Video, and a concept common to DVD-Video can be found in the underlying idea for realizing playback control. Therefore, it is expected that the user who performs the authoring work can utilize the same production know-how with the same idea as in the case of DVD-Video when authoring for BD-ROM.
JP 2000-339291 A

  Some conventional DVD-Video authoring systems developed for general users provide easy-to-understand GUIs so that users who do not have knowledge of the standards can easily create scenarios. However, in such an authoring system, for example, producing multi-angle and multi-audio titles is not supported because it includes complicated restrictions in the standard.

  On the other hand, a professional authoring system that fully supports the DVD-Video standard has been developed. In order to support playback including complicated restrictions such as multi-angle, the GUI provided by this authoring system is a standard Therefore, users who perform authoring work in content production need to be familiar with the data structure and restrictions in the standard beforehand. In the above system, the user is familiar with the standard. If it is not, creating a title is a very difficult task, and advanced knowledge and know-how are required to implement the data structure according to the scenario to be actually produced within the constraints of the standard.

  Therefore, it is required to construct a system that allows even a general user who is not familiar with the standard to easily create content according to the scenario intended by the user.

  In order to solve the above-described conventional problems, the present invention provides a scenario data conversion apparatus that outputs scenario data associated with a predetermined data structure that realizes a scenario created by a user. Reference is made by scenario editing means for producing, including the GUI, and outputting first scenario data corresponding to the display of the GUI on a one-to-one basis, the first scenario data, and the first scenario data Data conversion means for outputting the second scenario data associated with a predetermined data structure and the encoded information data for encoding the AV stream referenced by the second scenario data, with the material information data to be input as input It is characterized by comprising.

  According to the scenario data conversion apparatus of the present invention, when a user creates a playback method including complicated standard restrictions such as multi-angle, the user can display and edit with a data structure close to the scenario. This makes it easy to produce without knowing the standards. Therefore, it is possible to provide ease of user title production and to further improve the authoring work efficiency.

  Hereinafter, embodiments of a data generation apparatus according to the present invention will be described.

(Embodiment 1)
First, among the implementation acts of the recording medium according to the present invention, the mode of use acts will be described. FIG. 1 is a diagram for explaining a usage pattern of a recording medium according to the present invention. In FIG. 1, the recording medium according to the present invention is a BD-ROM 101. The BD-ROM 101 is used for supplying movie works to a home theater system formed by a playback device 102, a television 103, and a remote controller 104. The above is the description of the usage pattern according to the present invention.

FIG. 2 is a diagram showing the configuration of the BD-ROM.
The BD-ROM 201 is shown in the fourth level in the figure, and the track 202 on the BD-ROM is shown in the third level. The track 202 in the figure is drawn by extending the track formed in a spiral shape from the inner periphery to the outer periphery of the BD-ROM in the horizontal direction. This track includes a lead-in area, a volume area, and a lead-out area. The volume area in this figure has a layer model of a physical layer, a file system layer, and an application layer. When the application layer format (application format) of the BD-ROM is expressed using the directory structure, it becomes like the first row 204 in the figure. As shown in the figure, the BD-ROM 201 has a BDMV directory under the ROOT directory. Under the BDMV directory, an index file (index.bdmv) in which an index table constituting a title is defined, A movie object file (MovieObject.bdmv) that defines a scenario, a PLAYLIST directory, a CLIPINF directory, and a STREAM directory exist. A playlist that defines a file (XXX.M2TS) that stores AV clips, a clip information file (XXX.CLPI) that stores AV clip management information, and a logical playback path (playlist: PL) for AV clips. The files (YYY.MPLS) are placed under the above-mentioned STREAM directory, CLIPINF directory, and PLAYLIST directory, respectively.

Next, an operation until a movie title is reproduced will be described with reference to FIG.
First, when a disc is inserted into a player and recorded data is read, an index table 301 defining application titles and menus is loaded. The title in the index table 301 is associated with the movie object by the movie object ID. When Title # 1 is executed, for example, the movie object 302 associated with the title is called.

  The movie object 302 called from the title # 1 of the index table 301 includes a command constituting the scenario. When the “Play PL” command is executed on the movie object 1002, the designated playlist 303 is displayed. Played. Here, the movie object commands will be briefly described. The movie object dynamically defines a scenario for playing a movie, and the commands included in the movie object are used to control playback of a playlist. The “Play PL” command is a command for performing a process of reproducing a specified playlist.

  One or more play items are defined in the play list 303 reproduced by the movie object 302, and the play items are described in the order to be reproduced. Also, the play item defines a playback start time and playback end time of an AV clip that is actually played back. In reproduction of the playlist 303, the play items 1004 defined as described above are sequentially reproduced according to the reproduction order.

  When playing back a clip referenced from a play item in a playlist, an AV clip is played back via a clip information file.

  The clip 305 referred to from the play item 304 is composed of an AV clip 306 and a clip information file 307. The AV clip 306 is formed by packetizing a video stream, an audio stream, a subtitle stream, and a button stream, and multiplexing the MPEG- This is a stream based on the TS standard. The clip information file 307 defines the correspondence between time information and packet position information for the AV clip 306. Therefore, the playback start time and playback end time of the AV clip 306 defined in the play item 304 are replaced with the corresponding packet position information from the time information in the clip information file 307, and the AV clip 306 is played back from the appropriate position. .

  As described above, a movie can be played according to a scenario defined in the application layer.

  Next, FIG. 4 shows a configuration diagram of the authoring system 901 in the present embodiment. The authoring system 901 generates DVD video or BD-ROM disc image data from materials and material information and a scenario created by a user. A scenario creation unit 402, a material creation / introduction unit 403, and a disk image generation unit 404.

  The scenario creation unit 402 receives the scenario 405 created by the user and the material information 407 including the attributes relating to the material 406 such as a moving image and sound, and creates scenario data to be input to the disk image generation unit 404.

  The material generation / introduction unit 405 receives the material 406 and the material information 407 as input, encodes the material 406 into a stream defined by the standard, or describes the already encoded stream of the material 406 in the material information 407. Processed to match and output. The disc image generation unit 404 creates a disc image 408 based on the scenario data output from the scenario creation unit 402 and the stream output from the material generation / introduction unit 403.

  Here, a general authoring procedure will be briefly described. FIG. 5 is a flow showing the authoring process.

  First, when starting the authoring work as the first step S1001, a project is created as a data management unit for title production.

  After the project is created, several operations for preparing materials for creating a disk image are performed in parallel. First, in step S1002, an operation for encoding video materials into a stream defined by the standard is performed. Is called.

  Second, in step S1003, a material for preparing menu data is prepared. After that, in step S1005, a scenario editing operation for a title is performed, and scenario data is generated together with the menu data.

  Third, preparation of subtitle material for generating subtitles is performed in step S1004, and then, in step S1006, a subtitle stream is generated so that the subtitle material can be played back together with other video or audio streams. .

  In step S1007, the material prepared in the above process is converted into a disk image having a data structure that is actually recorded on the BD-ROM disk, and data is generated.

  The above is the work procedure performed by the authoring system 901 described above. In order to verify whether the disc image data generated in step S1007 is as intended by the user, a check using an emulator is further performed in step S1008 to confirm that the data has been generated correctly. In step S1009, the data is output as final master data.

  Next, a detailed configuration of the authoring system scenario creation unit 402 according to the present embodiment will be described with reference to FIG.

  The scenario creation unit 402 includes scenario editing means 601 and data conversion means 602.

  The scenario editing unit 601 provides a GUI that accepts editing 603 by the user, and the user edits the scenario using the GUI. The scenario edited by the user with the GUI is output as the first scenario data 605 from the scenario editing means 601. The first scenario data 605 is scenario data described in a data structure having a high level of abstraction that allows a user to easily edit a scenario without being aware of the details of the standard. At the same time, the first scenario data 605 has a data structure that can be uniquely converted into BD-ROM standard data and supports all functions that can be realized by the BD-ROM as much as possible.

  FIG. 7 shows an example of an input GUI provided by the scenario editing means 601. The scenario view 701 is a window that supports the editing work by displaying the data structure of the scenario created by the user on the GUI. When editing in the scenario view 701, icons assuming scenarios to be created are prepared in advance, and title icons 703, script icons 704, playlist icons 705, command icons 706, and menu icons 707 are classified according to functions and uses. It is classified. The user can edit the scenario by dragging and dropping these icons on the scenario view 701 in accordance with the titles to be produced. The property view 702 is a window used for editing the attribute value set for each icon described above, and is one icon on the scenario view 701 (“title 1” in the example of FIG. 7). When the focus is on, the attribute of the icon (“Name”, “Type”, etc. in the example of FIG. 7) is displayed on the property view 702, and the attribute value can be edited in the property view 702. The displayed attribute information is defined for each icon. For example, if the title icon is “title”, the title name and title type are defined, and the command icon “Set” is defined. If so, the name of the variable to set the value and the value to be set or the name of the variable storing the value are set. If the playlist icon is “movie”, link information for referring to material information data describing the type of encoding of the AV stream to be used, bit rate, reproduction time, and the like is set.

  The design view 708 is a window used for editing the layout or the like while previewing the screen display design of the title that the user actually wants to display. In the design view 708, the button arrangement and the focus transition order can be edited, and the button coordinate information and the button selection transition order information set in the design view 708 are attribute information of the corresponding icon on the scenario view 701. Automatically reflected. FIG. 8 shows an example of a scenario view 701 displayed on the GUI by editing 603 by the user.

  Subsequently, the data conversion unit 602 receives the first scenario data 605 created by the scenario editing unit 601 and outputs second scenario data 606 represented by a data structure defined by the standard. Further, the data conversion means 602 also inputs the material information data 604 referred to in the first scenario data 605 and creates the encoded information data 607 for encoding the material used in the first scenario data 605. And output.

  Next, the first scenario data 605 output by the scenario editing unit 601 will be described. 9 and 10 show the data structure of the first scenario data 605 that is output based on the information input by the user editing 603 to the scenario creation unit 402 shown in FIG. Here, the data structure represented by the first scenario data 605 is a format prepared in a one-to-one correspondence with each icon represented by the data structure edited by the user using the GUI. In addition, it is configured so that a plurality of items do not overlap with one piece of information. In addition, when creating a stylized data structure, it has a feature that is simplified as a flag or the like.

   "scenario" (A01) represents the directory where the disc titles to be produced are gathered. Among them, three directories "titles" (A02), "scripts" (A03), and "playlists" (A04) are included. Including.

  “titles” (A02) is a directory in which titles divided for each scenario to be played in the content are collected. “firstplay” (A05), “topmenu” (A06), zero or more “title” (A07) is included.

  “firstplay” (A05) defines a scenario in which a disc is automatically played first when a disc is inserted into a player.

  “topmenu” (A06) defines a title that is called by the player's menu display function, and is usually associated with a menu screen that links to each title or chapter.

  "title" (A07) defines the content scenario itself, and "title" is created for the number of scenarios to be created.

  "SidePath" (A08) may be defined under "title" (A07). Here, “SidePath” (A08) is defined when the main scenario in the title branches to another scenario halfway.

“scripts” (A03) is a directory in which zero or more “scripts” (A12) are collected.
“script” (A09) is not a title, but defines an object describing a series of fixed processes, and can define an object for an interactive title.

  “playlists” (A04) is a directory in which one or more “playlists” (A10) are collected.

  “playlist” (A10) defines a playback path of an actual stream and is associated with a stream to be played back.

  Further, “multipath” (A11) is defined for a title such as a director's cut, for example, including a portion where a plurality of “playlists” share a playback path.

  Among the data structures described above, “firstplay” (A05), “topmenu” (A06), “title” (A07), “SidePath” (A08), and “script” (A09) are shown in FIG. A scenario to be played back using a command as described in is described.

Here, the command will be described.
“play” plays a playlist defined in “playlists” (A04). In the attribute, a play list name to be reproduced is described.

  “call” plays another title while maintaining the state of the currently playing title. The title name to be called or the script name is described in the attribute.

  “resume” returns to the previously played title from the title played by “call” and plays it.

  “Set” is a command for setting a value for a storage area (register) of the player. In the attribute, a register name for setting a value and a set value or a register name storing the set value are described.

  “if” is a command for executing conditional branch processing. The attribute describes a conditional expression that gives a branch condition.

  “while” is a command for executing a repetition process. In the attribute, a conditional expression that gives a repetition condition is described.

  It is possible to define playback of any scenario by a combination of the above commands.

  On the other hand, “playlist” (A10) defines the playback paths with reference to the material information as shown in FIG.

FIG. 10 shows a data structure related to material information referred to by “playlist” (A10).
“movie” (B01) refers to the video material, among which “video” (B07) refers to video, “audio” (B09) refers to audio, and “subtitle” (B10) refers to subtitles. ) Is included.

  “angle” (B02) refers to the use of a plurality of moving image materials as a multi-angle, and includes two or more “movies” (B11).

  “still” (B03) refers to a still image material. Still images are used mainly for menu screens and slide show playback, and therefore may include a “page” (B12) structure.

  "page" (B12) is a structure used to display buttons and icon images on the screen. Also defined are "effect" (B13) for applying effects to buttons in "page" (B12), "animation" (B14) for displaying animations, and "widget" (B15) for defining button functions. May be.

  “Widget” (B15) is a structure that defines functions such as buttons arranged in “page”. Detailed description will be described later.

  “InteractiveStream” (B04) defines a menu to be displayed on a moving image, and refers to a stream displaying a menu that is played back together with the moving image material defined by “movie”.

  “audio” (B05) refers to audio material. Here, unlike “audio” included in “movie” (B07), “audio” (B05) is played back together with still images defined by “still” (B03). Refer to the audio material to be recorded.

  “Popupmenu” (B06) is similar to “InteractiveStream” (B04), but has a menu that can be displayed asynchronously with playback of other materials such as “movie” (B07) and “still” (B03). To define.

  By referring to the above-mentioned material information by “playlist”, a complicated reproduction method and various reproduction functions can be realized.

  The first scenario data 605 described above corresponds to each node edited by the scenario editing unit 601 on a one-to-one basis.

  The first scenario data 605 may be transferred in a state where the data is held in the memory of the computer, in addition to the case where the first scenario data 605 is output as a file.

The above is the description of the data structure of the first scenario data 605.
Next, the data structure of the material information data 604 will be described with reference to FIG.

  The material information data 604 includes sub-reel information that defines a combination of stream attribute information such as video, audio, and subtitles that can be used during authoring, and stream attributes that are reproduced on a scenario.

  The video attribute D02 includes attributes such as a video stream codec, a frame rate, and an aspect ratio.

The number of audio lines D03 defines the number of audio streams to be used.
There are as many audio attributes D04 as the number of audios, and attributes such as the codec, bit rate, sampling frequency, and number of channels of the audio stream are included.

The number of subtitles D05 defines the number of subtitle streams to be used.
Subtitle attributes D06 exist as many as the number of subtitles, and include attributes such as a display method, presence / absence of display subtitles, and data size.

The sub reel number D07 defines the number of sub reels.
Sub reel attributes D08 exist as many as the number of sub reels, and define encoding information and a system rate for encoding a material stream defined above into a multiplexed system stream. In addition, an entry number D09 representing the number of entry points inserted into the system stream encoded at the same time and an entry time code D10 indicating the entry time are defined.

  The attribute information data 604 is used for referring to the material information in the scenario creation unit 402, and at the same time, is attribute information set when the material generation / introduction unit 403 prepares the material.

This completes the description of the material information data 604.
FIG. 12 shows data output by the data conversion unit 602.

  From the data conversion means 602, the second scenario data 606 described in the data structure defined by the standard, the encode information data 607 for creating a disk image in a later process other than the scenario data, and the like are output. . The second scenario data will be specifically described. In the data structure of the BD-ROM standard, as a file describing a scenario, index.bdmv describing a title, MovieObject.bdmv describing an object including a command, and a stream The playlist files (00000.mpls, 00001.mpls, 00002.mpls,...) Including the reproduction control information are equivalent to these, and these files are output as text-described files such as an XML format. Therefore, the data described in the first scenario data is converted by the data conversion means 602 into index.bdmv, MovieObject.bdmv, and a playlist file in the data structure of the BD-ROM standard.

  When the data conversion means 602 converts the playlist list information describing the list of playlist files included in the second scenario data, and the stream referenced by the second scenario data into a disk image. Also, the layout information describing the arrangement method and the encoding information for encoding the material stream referred to by the second scenario data into a multiplexed system stream are also output.

  Next, the conversion from the first scenario data 605 to the second scenario data 606 in the data conversion means 602 will be described with reference to FIG.

  The first scenario data 605 input to the data conversion means 602 is defined by defining characteristic functions and special functions that can be realized by the BD-ROM standard as tag names and attribute values.

  The discriminating means 1301 discriminates the tag name and attribute value, and allocates the data to each conversion process so that the data is appropriately converted based on the conversion rule described below in order to convert it to the data structure of the BD-ROM. Perform the action.

In the following, a conversion rule for converting the data structure of the BD-ROM is shown.
Conversion to the second scenario data 606 described in the data structure defined in the BD-ROM standard is performed by one of the following methods. Note that data that does not need to be converted is directly passed to the combining unit 1302.

  First, when the “widget” tag described in the first scenario data 605 is detected by the determination unit 1301, the detected “widget” data is sent to the first conversion unit 1303.

  When the “playlist” tag described in the first scenario data 605 is detected, the detected “playlist” and “movie”, “still”, “audio”, etc. included below the “playlist” are detected. Are sent to the second conversion means 1304.

  When a tag representing a command such as “play” or “set” described in the first scenario data 605 is detected, it is sent to the detected command data third conversion means 1307.

  The above is a typical data structure of the first scenario data 605 that needs to be converted to the data structure of the BD-ROM standard. Details of other tags are also omitted here, but those that require data structure conversion are assigned to the corresponding data conversion means.

  Next, the data sorted by the discriminating means 1301 is converted by the respective converting means.

  In the first conversion means 1303, “widget” data is input, and the value set in the “type” attribute of “widget” is detected. Then, the data structure of the BD-ROM defined in advance by the first conversion unit 1303 is output according to the value set in “type”. There are “buttons”, “check boxes”, “static” and “radio buttons” defined in “type”, and the corresponding BD-ROM standard data structure is prepared. Outputs the data structure of the BD-ROM that realizes the display function. Further details will be described later.

  In the second conversion means 1304, data related to “playlist” defined in the first scenario data 605 is input. Under the input “playlist”, attribute information such as “movie” information and “still” is included as one or more pieces of material information.

  “Movie” includes link information that refers to material information data, obtains time information reproduced from the entry time code and end time code of the sub reel attribute described in the material information, and obtains second scenario data Set INtime and OUTtime of PlayItem included in. If “movie” does not exist and “still” is included, INtime and OUTtime are set as the time information to be set with reference to the “duration” attribute included in “still”.

  In the data conversion means 602, a value is set in a predetermined data area defined by the second scenario data 606. As a specific example, a plurality of material information is associated with “playlist” included in the first scenario data 605. At this time, referring to the respective time information included in the plurality of material information, PlayItem time information (INtime, OUTtime) defined in the playlist file of the second scenario data 606 is determined.

  In this way, the second conversion unit creates one node of the second scenario data from the plurality of tag information and attribute information of the first scenario data.

  The third conversion means 1305 converts the macro-defined command defined in the first scenario data 605 into a command defined in the BD-ROM. Even if the commands achieve the same behavior, there are cases where different commands must be used in the standard when the position where the command is described and the target processed by the command are different. In the conversion method 1305, the position where the command is described and the target of the command are determined, and conversion into a command defined in an appropriate BD-ROM standard is performed.

  The above is the conversion means. However, the conversion means is not limited to the first conversion means, the second conversion means, and the third conversion means described above. Each tag name defined in the scenario data 605 in the second scenario data 606 is converted into ID information defined in the BD-ROM standard in the second scenario data 606, or other than the above-described one included in the first scenario data For other tag information, appropriate conversion means is prepared as necessary.

  As described above, the data converted by the conversion unit is described in an appropriate data structure to be output by the combining unit 1302, and is output as second scenario data.

  FIG. 14A shows an example of the first scenario data, and FIG. 14B shows an example of the second scenario data converted by the data conversion means 602. The data conversion means 602 converts the data structure of FIG. 14A to the data structure of FIG. 14B in the following correspondence.

  First, “firstplay” (E03), “topmenu” (E04), and “title” (E05) included in “titles” (E02) in FIG. 14A are “index. bdmv "is converted into firstplayback (), topmenu () and title () fields. The commands defined in E03, E04, and E05 are converted into movie objects (mobj # 0 to # 1) in “MovieObject.bdmv”. Here, if no command exists as in the example of “topmenu” in FIG. 14, mobj is not created, and there is no movie object referred to in “topmenu ()” included in “index.bdmv”. Meaning value is set.

  “SidePath” (E06) represents an object that is called by branching in the middle of the title defined by “title # 0” (E05), and the command defined by E06 is the corresponding movie object (mobj # Converted to 2).

  “Script” (E09) included under “scripts” (E08) is converted into a movie object (mobj # 3) that defines a command in “MovieObject.bdmv” in FIG.

  “Playlist # 0” (E10), “playlist # 1” (E15), and “playlist # 2” (E20) included in “playlists” (E09) in FIG. 14 (a) are all in FIG. 14 (b). , Playlist files (00000.mpls (F05), 00001.mpls (F06), 00002.mpls (F07)) included in the PLAYLIST folder (F04). Note that if “multipath” (E14), which is the upper node of “playlist # 1” (E15) and “playlist # 2” (E20), exists, for example, an encoding parameter for seamless connection to realize director's cut. Is converted into a place where encoding information is output.

Furthermore, it is about the conversion to the detailed part of the playlist file,
In “movie” (E11), the material information data is referenced, and the playlist is based on the video attribute, audio attribute, subtitle attribute, and sub-reel attribute included in the material information data referenced from “movie” (E11). A PlayItem described in the file 00000.mpls (F05) is generated.

  Next, the interactive graphics stream will be described. Here, the interactive graphics stream is a stream including a data structure prepared mainly for realizing a button function defined in the BD-ROM standard. The interactive graphics stream is composed of functional segments called ICS (Interactive Composition Segment), PDS (Palette Definition Segment), ODS (Object_Definition_Segment), and END (END of Display Set Segment). In addition, a set of a plurality of functional segments constituting a graphics stream that constitute graphics for one screen is referred to as a Display Set (abbreviated as DS).

  The interactive screen defined by these functional segments is an interactive screen created by arranging GUI parts on the screen. FIG. 15A is a diagram showing an interactive screen realized by an interactive graphics stream. This interactive screen includes four GUI parts, button A to button D. Interactivity by the interactive graphics stream means changing the state of these GUI parts (buttons) according to user operations. The state of the GUI component (button) includes a normal state 401, a selected state 402, and an active state 403 shown in FIG. The normal state is a state that is merely displayed. On the other hand, the selected state refers to a state in which focus is applied by a user operation but has not yet been finalized. The active state means a state that has been finalized. The state of these buttons can be changed by pressing a key on the remote controller 104 shown in FIG.

  FIG. 15B is a diagram showing keys on the remote controller 104 for accepting an operation on the dialogue screen from the user. As shown in the figure, the remote controller 104 is provided with a MoveUp key 1504, a MoveLeft key 1505, a MoveDown key 1506, and a MoveRight key 1507.

  The MoveUp key 1504 is a key for setting a button above this button to the selected state when a certain button on the dialog screen is in the selected state. MoveLeft key 1505 is a key for setting a button on the left side of this button to a selected state, MoveDown key 1506 is a key for setting a button below this button to a selected state, and MoveRight key 1507 is a key for setting the selected state. A key for setting the button on the right side of the button to the selected state.

  An Activated key 1508 is a key for activating a button in the selected state. A numeric key 1509 of “0” to “9” is a key for setting a button to which a corresponding numeric value is assigned to a selected state. The “+10” key is a key for accepting an operation of adding 10 to the numerical value input so far. Since the “0” key and the “+10” key both accept input of numerical values of two digits or more, either the “0” key or the “+10” key may be provided.

  Each state such as a normal state, a selected state, and an active state is composed of a plurality of uncompressed graphics. Individual uncompressed graphics representing each state of the button is called a "graphics object". The reason why one button state is represented by a plurality of uncompressed graphics is because it is intended to animate one button state.

The above is the description of the dialogue screen assumed in the present embodiment.
Next, Interactive Composition Segment (ICS), which is a functional segment that composes an interactive screen, will be described. The Interactive Composition Segment (ICS) has a data structure shown in FIG. As shown in FIG. 16, the ICS has “segment_type”, “segment_length”, “composition_number”, “composition_state”, “command_update_flag”, “composition_timeout_PTS”, “selection_timeout_PTS”, “page information (page ( 1) (2) (3) ...) '', and `` Page information (page) '' is `` UO_mask_table '', `` in_effects '', `` out_effects '', `` animation_frame_rate_code '', `` default_selected_button_number '' , “Default_activated_button_number” and “button_overlap_group”.

  The “button_overlap_group” includes one or more “button information groups (button info (1) (2) (3)...)”. Hereinafter, the components of ICS will be described.

  “Composition_number” is a numerical value from 0 to 15 indicating that Update is performed in the DS to which the ICS belongs.

  “Composition_state” indicates whether the DS starting from this ICS is a normal case, an acquisition point, or an Epoch Start.

  “Command_update_flag” indicates whether or not the button command in this ICS has changed from the previous ICS. For example, if a DS to which a certain ICS belongs is an Acquisition Point, this ICS basically has the same contents as the previous ICS. However, if command_update_flag is set to ON, a button command different from the previous DS can be set in ICS. This flag is effective when the graphics object is used but the command is to be changed.

  “Composition_timeout_PTS” describes the end time of the interactive screen by the button. The display of the interactive screen at the end time is no longer valid and is not displayed.

  The composition_timeout_PTS is preferably described with time accuracy on the playback time axis in the moving image data.

  “Selection_timeout_PTS” describes the end point of an effective button selection period. At the time of selection_timeout_PTS, the button specified by default_activated_button_number is activated. selection_timeout_PTS is equal to or shorter than the time of composition_time_out_PTS. selection_timeout_PTS is described with the time accuracy of the video frame.

  “Page information (page)” is a structure that defines an interactive screen displayed at a time. The lead line hp1 in the figure focuses on the internal structure of the mth page, and the configuration of the page will be described below.

  “UO_mask_table” indicates permission / non-permission of user operation in the Display Set corresponding to ICS. If this mask field is set to non-permitted, the user operation on the playback device is invalidated.

  “In_effects” defines display effects when the screen is updated when the page is displayed on the screen.

  “Out_effects” defines display effects when the screen is updated when the page is deleted from the screen.

  “Animation_frame_rate_code” describes the frame rate to be applied to the animation type button. The animation frame rate is given by dividing the video frame rate by using the value of this field. If this field is 00, only those specified by Start_Object_id_xxx among the ODSs that define the graphics objects for each button are displayed and not animated.

  “Default_selected_button_number” indicates a button number to be set to the selected state as a default when the display of the interactive screen starts. If this field is “0”, the button with the button number stored in the register of the playback device is automatically set to the active state. If this field is non-zero, this field means a valid button value.

  “Default_activated_button_number” indicates a button that is automatically set to an active state when the user does not activate any button before the time defined by selection_timeout_PTS. If default_activated_button_number is “FF”, the currently selected button is automatically selected at the time defined by selection_timeout_PTS. If this default_activated_button_number is 00, automatic selection is not made. If the value is other than 00, FF, this field is interpreted as a valid button number.

  “Button_overlap_group” is a structure that defines a group of buttons described below. Only one button defined in this button_overlap_group exists in a state that is not invalid at any time.

  “Button information (button_info)” is information defining each button to be synthesized on the interactive screen. The lead line hp2 in the figure closes up the internal structure of the button information i for the i-th button controlled by the ICS. Hereinafter, the information elements constituting the button information i will be described.

“Button_number” is a numerical value that uniquely identifies the button i in the ICS.
“Button_numeric_select_value” is a flag indicating whether or not numerical selection of the button i is permitted.

  “Auto_action_flag” indicates whether or not the button i is automatically activated. If auto_action_flag is set to on (bit value 1), button i enters an active state instead of a selected state. If auto_action_flag is set to off (bit value 0), the button i is only in the selected state even if it is selected.

  “Object_horizontal_position” and “object_vertical_position” indicate the horizontal position and vertical position of the upper left pixel of the button i on the dialog screen.

 “Neighbor_info” has a structure indicated by the lead line hp3. More specifically, the “upper_button_number” indicates the number of the button that should be selected instead of the button i when the MoveUp key 1504 is pressed when the button i is in the selected state. If the number of the button i is set in this field, pressing of the MoveUp key 1504 is ignored. Similarly, “lower_button_number”, “left_button_number”, and “right_button_number” are used instead of pressing the button i when the MoveLeft key 1505, MoveDown key 1506, and MoveRight key 1507 are pressed when the button i is in the selected state. Indicates the number of the button that should be selected. If the number of button i is set in this field, pressing these keys is ignored.

“Normal_state_info” has a structure indicated by the lead line hp4.
In “normal_start_object_id”, when the button i in the normal state is drawn by animation, the first number among the serial numbers added to the plurality of ODSs constituting the animation is described in this normal_start_object_id.

  In “normal_end_object_id”, when the button i in the normal state is drawn by animation, the last number among “object_ID” which is a serial number added to the plurality of ODSs constituting the animation is described in this normal_end_object_id. When the ID indicated by the normal_end_object_id is the same as the ID indicated by the normal_start_object_id, the still image of the graphics object indicated by the ID becomes the pattern of the button i.

  “Normal_repeated_flag” indicates whether or not the animation display of the button i in the normal state is continuously repeated.

“Selected_state_info” has a structure indicated by the lead line hp5.
“Selected_state_sound_id” describes a reference to audio information that is reproduced when the button i transitions to the selected state.

  In “selected_start_object_id”, when the selected button i is drawn with animation, the first number among the serial numbers added to the plurality of ODSs constituting the animation is described in this selected_start_object_id. When the ID indicated by the selected_end_object_id is the same as the ID indicated by the selected_start_object_id, the still image of the graphics object indicated by the ID becomes the pattern of the button i.

  In “selected_end_object_id”, when a button in a selected state is drawn by animation, the last number among “object_ID” which is a sequential number added to a plurality of ODSs constituting the animation is described in this selected_end_object_id.

  “Selected_repeat_flag” indicates whether or not to continue the animation display of the button i in the selected state. If selected_start_object_id and selected_end_object_id have the same value, this field 00 is set.

“Activated_state_info” has a structure indicated by a lead line hp6.
“Activated_state_sound_id” describes reference to audio information that is reproduced when the button i transitions to the selected state.

  “Activated_start_object_id” describes the first number in the activated_start_object_id among the serial numbers added to the plurality of ODSs constituting the animation when the active button i is drawn by animation.

  “Activated_end_object_id” describes the last number among “object_ID”, which is a sequential number added to a plurality of ODSs constituting the animation, in the case of drawing an active button with animation.

Next, the button command will be described.
The “button command (button_command)” is a command that is executed when the button i becomes active.

  The above is the internal structure of ICS. A specific example of dialog control by ICS will be described below. This specific example assumes ODS and ICS as shown in FIG. FIG. 17 is a diagram illustrating the relationship between ODS and ICS included in a certain Display Set (DSn). This DSn includes ODS11-19, 21-29, 31-39, 41-49. Of these ODSs, ODS11-19 depict the states of button A, ODS21-29 depict the states of button B, and ODS31-39 depict the states of button C. The ODS 41 to 49 depict the states of the button D (see parentheses in the figure). It is assumed that the state control of these buttons A to D is described in button_info (1), (2), (3), (4) in ICS (arrows bh1, 2, 3 in the figure). , 4).

  FIG. 18 is a diagram illustrating a state where the selected state of the button on the menu screen is changed by an operation from the remote controller 104. FIG. 19 shows a specific example of the ICS used for realizing the transition of the selected state of the button shown in FIG.

  Here, the state of transition of the selected state for the buttons A to D shown in FIG. 18 will be described with reference to FIG. Arrows hh1 and hh2 in FIG. 18 symbolically represent state transitions by button_info (1) neighbor_info (). In FIG. 19, the lower_button_number of neighbor_info () of button info (1) is set to the button C. Therefore, if a user operation of pressing the MoveDown key 1506 occurs when the button A is in the selected state (FIG. 19). 18 up1), the button C is selected (sj1 in FIG. 18). In FIG. 19, right_button_number of neighbor_info () of button info (1) is set to button B. Therefore, if a user operation of pressing the MoveRight key 1507 occurs while button A is in the selected state. (Up2 in FIG. 18), button B enters the selected state (sj2 in FIG. 18).

  An arrow hh3 in FIG. 18 indicates control of state transition by neighbor_info () of button info (3). In FIG. 19, upper_button_number of neighbor_info () of button info (3) is set to button A. Therefore, when the button C is in the selected state (up3), a user operation of pressing the MoveUp key 1504 occurs. Button A returns to the selected state. In this way, “neighbor_info” of “button_info” is defined so as to reflect the positional relationship of each button, so that the transition of the selected state is realized by the key operation of the remote controller 104.

This completes the explanation of the ICS data structure.
Next, FIG. 20 illustrates correspondence of conversion from the first scenario data 605 to the second scenario data 606 corresponding to the interactive graphics stream described above.

  “Page” (G02, G08, G10) described in the first scenario data 605 means a data structure related to displaying a button in the scenario, and this data is a button stream in the standard data structure. Corresponds to the data structure. Therefore, the data structure of the BD-ROM standard corresponds to the above-described interactive graphics stream. The data conversion means 602 converts the data into an ICS data structure when creating an interactive graphics stream.

  FIG. 21 shows the definition of “widget” (G05) included in the first scenario data 605 shown in FIG. This “widget” (G05) defines a button function used on a menu screen in a scenario, for example.

  As shown in FIG. 21, “widget” includes “name”, “type”, “autoAction”, “numericSelect”, “x_pos”, “y_pos”, “Up”, “Down”, “Left”, “Right”. Include attributes such as ".

“Name” is an attribute that defines a tag name.
“Type” is an attribute that defines the type of button function, which will be described in detail later.

  “AutoAction” is an attribute indicating a flag indicating whether or not automatic execution of a button is permitted. “NumericSelect” is an attribute that defines a numerical value to be assigned when the button selects a numerical value. “X_pos” and “y_pos” are attributes that define the x-coordinate and y-coordinate displayed by the button.

  “Up”, “Down”, “Left”, and “Right” are attributes that define a transition destination button by each Move key when the focus of the button is transitioned to the cursor.

  Here, the types of button functions defined in the “type” attribute of “widget” will be described below. The functions defined by the “type” attribute include a button, a static, a check box, and a radio button.

  A button (button) is an object having a function of executing command processing set by selecting and pressing.

  Static is an object having a function of only displaying a static image or text.

  A check box is an object having a function of switching the display by pressing a selected item and switching a flag used for determining a playback path.

  A radio button is an object having a function of switching a flag so that only one check box exists in an ON state among two or more grouped check boxes.

  As described above, the object defined by “widget” is an object that is standardized as a typical function, and the data structure corresponding to the object is defined in advance in the data conversion unit 602 of the present invention. Thus, the second scenario data 606 compliant with the BD-ROM standard is output based on the description of the “widget” field of the input first scenario data 605.

  Note that the functions described above are merely examples, and if there is a function other than the above generally assumed by the user at the time of content production, the function may be converted.

  The data conversion unit 602 converts the data structure as described above from the first scenario data to the data structure of the second scenario data.

  Next, a conversion method for converting the function set in the “widget” field in the input first scenario data 605 into the data structure of the BD-ROM standard will be described.

  The functions defined by “widget” described above are realized by using the structure of the button overlap group “button_overlap_group” (hereinafter abbreviated as BOG) defined in the data structure of the BD-ROM standard. Can do. First, an operation example of a button overlap group (BOG) will be described with reference to FIG. As shown in FIG. 22, when there are three button objects and they are displayed in the same area on the screen, these three buttons can be configured as one BOG 801.

  For each button object grouped as a BOG, only one of these button objects is enabled and displayed on the screen.

  For example, now, on the screen (a) of FIG. 22, the button object # 2 belonging to the BOG is displayed in a valid state. Here, it is assumed that the command “EnableButton # 3” is executed when a certain button is pressed. The “EnableButton” command performs processing to enable the display of the button object with the button ID specified in the operand. If the button object specified at the same time belongs to the BOG, the button object specified in the BOG is specified. If a button object other than the selected button object is currently enabled, a process for invalidating it is performed. Therefore, the display of the button object # 2 included in the BOG to which the button object # 3 belongs is disabled, the display of the button object # 3 is enabled, and the screen display is switched to the screen display as shown in the screen (b) of FIG. As described above, the BOG has an effect of facilitating switching of button display by grouping button objects to be displayed in the same area on the screen.

Based on the above, a data structure conversion method related to “widget” will be described.
The realization of the button function is the BOG data structure described above, and is realized by applying an image and a command that apply to a standard field. In the case of a normal button, a BOG containing only one button is generated.
(1) Next, static is a function that displays a static image or text, and can be seen as a limited use of the button function. Specifically, it is necessary to restrict the execution of commands included in button functions, button adjacency information, and numerical input transitions. Therefore, as a feature for static objects, command invalidation
(2) Invalidate button neighbor information
(3) The static function is realized by setting the invalidation of the button selection function by numerical input at the time of data creation.

  As the method (1), there are a method of setting the number of commands set in the ICS button_command to 0, a method of setting a command (Nop) for performing no processing in the ICS button_command, and the like.

  The method of (2) is to set nothing in neighbor_info () in ICS, or set your own button ID in all of nieghbor_info () in ICS (upper_button_number, lower_button_number, left_button_number, right_button_number) There are ways to do it.

  As the method (3), there is a method in which nothing is set in button_numeric_select_value in ICS, or a method in which an invalid value (for example, a negative number) is set in button_numeric_select_value in ICS.

  In addition, as shown in FIG. 23, the static object is a structure using the BOG structure as shown in FIG. 23, and shows three static images set so as to satisfy the above three conditions. , “Japanese”, “English”, and “Deutsch” are displayed only. These are grouped as a BOG structure, and therefore only one of the three is valid and displayed on the screen.

Static objects cannot be switched by themselves, but the command “EnableButton (id + 1)% 3” is executed each time a button is executed for each image, for example.
(However, “id” is the currently displayed ID number, and “%” represents the remainder calculation.)
The static image to be displayed can be switched by executing.

  Next, the check box will be described with reference to FIG. The check box is a button function that represents two states of selection (ON) or non-selection (OFF) of an item. As shown in FIG. 24 (a), the button in each case of ON and OFF is changed to the item state. It is switched and displayed accordingly. Therefore, the check box is realized by making the ON button and OFF button into a BOG structure. FIG. 24B shows a display image transition method for each state of the ON button and the OFF button.

  First, switching from OFF to ON will be described. First, when the check box is in the normal state with the OFF button, when the cursor is moved to the check box button by the user operation, the state is changed to the selected state of the OFF button of the check box (ch01). Here, when the user depresses (activates) the check box, the state transits to the active state of the OFF button (ch02). The check box that has become active here switches from the OFF button to the ON button. That is, in the active state, the command “EnableButton id = 0” (where id = 0 is the ID of the ON button) is executed to switch the display button from OFF to ON simultaneously with switching of the variable corresponding to the check box. After the button command is executed, the selected state of the ON button is displayed (ch03).

  Next, switching from ON to OFF. When the check box is in the normal state with the ON button, when the cursor moves to the check box button by the user operation, it changes to the selected state of the check box ON button (ch04 ). Here, when the user depresses the check box, the state transits to the ON button active state (ch05). The check box that has become active here switches from the ON button to the OFF button. That is, in the active state, the command “EnableButton id = 1” (where id = 1 is the ID of the OFF button) is executed to switch the display button from ON to OFF at the same time as switching the variable corresponding to the check box. After the button command is executed, the selected state of the OFF button is displayed (ch06).

  As described above, the check box function can be realized by performing the conversion in which the command is set to perform the button transition as described above using the BOG structure in the BD-ROM standard.

  Next, the radio button function will be described with reference to FIG. A radio button is a check box with a function that allows only one of a plurality of selection items to be turned on. With radio buttons, when one item in a group is turned on, the other items in the same group that were previously turned on are automatically turned off. In FIG. 25, three radio buttons (radio A, radio B, radio C) are grouped. Each radio button consists of two buttons, ON and OFF, and has a BOG structure. This is a button display image transition method, but the difference from the check box is that the user can switch from OFF to ON for each button. When a button in the group is turned ON, the other buttons in the same group that are in the ON state are switched to OFF.

  Next, a case where the radio B button is switched from OFF to ON from the state in which the radio A button is selected as shown in FIG. 25 will be described with reference to FIG. First, to switch radio B in the normal state of the OFF button, when the cursor is moved to radio B by a user operation, the radio B transitions to the selected state of the radio B OFF button (ra01). Here, when the user presses radio B, the state transits to an active state of OFF (ra02). Radio B that has transitioned to the active state is switched from the OFF button to the ON button, and the command “EnableButton id = 2” for switching the display button from OFF to ON (where id = 2 is the radio B ON button ID is executed) (ra03). At this time, it is necessary to turn off the other radio A and radio C buttons in the same group, so “Enable Button id = 1” (where i = 1 is the ID of the radio A OFF button. ) And “Enable Button id = 5” (where i = 5 is the ID of the radio C OFF button), and radio A for which the ON button is displayed at this time is switched from ON to OFF. The display is switched to (ra04).

As described above, switching to turn on radio B is executed.
Note that switching from OFF to ON is realized for the other radio buttons in the same procedure as described above.

  In addition, since the radio button is not switched from ON to OFF by a user operation, when the button is pressed (activated) in a selected state with respect to the radio button on which the ON button is effectively displayed, the ON button Although transitioning to the active state, no processing is performed, and the state returns to the selected state again (ra05, ra06, ra07).

  As described above, in addition to the BOG structure, the function of the radio button can be realized by setting the above command for the grouped buttons.

  It is very difficult for users to create functions such as buttons, statics, check boxes, and radio buttons described above with a data structure that complies with the BD-ROM standard. By preserving possible data structures, it is possible to easily convert data set as an abstract data structure attribute into a data structure that conforms to the standard. The content can be easily produced without being aware of the restrictions, and work efficiency can be improved.

This completes the description of the data structure conversion method for widgets.
As described above, according to the present invention, it is possible to provide an authoring system that is easy for a user to produce a title and that can produce a complicated reproduction method, and work efficiency can be further improved.

  In addition, although it demonstrated by embodiment regarding this invention, of course, this invention is not restricted to said embodiment.

  The data conversion apparatus according to the present invention can supply high-value-added movie works with higher quality and rich variety of applications to the market, and can activate the movie market and consumer equipment market. . Therefore, the data conversion apparatus according to the present invention has high applicability in the movie industry and the consumer equipment industry.

The figure which shows the usage condition of the recording medium concerning this invention BD-ROM configuration diagram The figure which shows the title playback procedure in the data structure of BD-ROM The figure which shows the structure of the authoring system concerning this invention Flow diagram showing the authoring process The figure explaining the scenario production | generation part concerning this invention Example of GUI screen provided by scenario editing means Display example of scenario data edited on GUI The figure explaining the data structure based on the scenario input into the data generation apparatus concerning this invention The figure explaining the data structure about the material which a playlist refers to in the data structure based on the scenario Diagram explaining the data structure of attribute information data The figure explaining the data output by a data conversion means The figure which shows the structure which performs the conversion process in a data conversion means Diagram showing the correspondence of conversion from the first scenario data to the second scenario data Diagram explaining dialogue screen by interactive graphics Diagram showing the data structure of Interactive Composition Segment (ICS) Diagram showing the relationship between ODS and ICS The figure which shows the state transition of button A-button D A figure showing an example of setting button information in ICS Diagram showing the correspondence of conversion from the page in the first scenario data to the ICS in the second scenario data Diagram explaining the attributes of the widget field included in the first scenario data Diagram explaining the structure of the button overlap group Diagram explaining the structure of static attributes Diagram explaining the structure of check box attributes Diagram explaining the structure of radio button attributes Diagram explaining the button state transition of radio button attributes

Explanation of symbols

101 BD-ROM disc 102 Playback device 103 Television 104 Remote control 201 BD-ROM
202 Track configured in the physical layer 203 File system layer 204 Application layer 301 Index table 302 Movie object 303 Playlist 304 Play item 305 Clip 306 Clip information file 307 AV clip 401 Authoring system 402 Scenario production unit 403 Material generation / introduction unit 404 Disc image production unit 405, 603 Input of edit information by user 406 Collection of materials 407, 604 Material information data 408 Disc image 601 Scenario editing means 602 Data conversion means 605 First scenario data 606 Second scenario data 607 Encoding information data 701 Scenario view 702 Property view 703 Collection of title icons 704 Set of icon icons 705 set of playlist icons 706 set of command icons 707 set of menu icons 708 design view 1301 determining means 1302 combining means 1303 first conversion method 1304 second conversion method 1305 third conversion method 1501 normal state 1502 Button in selected state 1503 Button in active state 1504 MoveUp key 1505 MoveLeft key 1506 MoveDown key 1507 MoveRight key 1508 Activate key 1509 Numeric input key 2201 Button overlap group 2401 Check box 2501 Radio button group

Claims (18)

A scenario data conversion device that outputs scenario data associated with a predetermined data structure for realizing a scenario created by a user,
The user creates a scenario using the GUI,
Scenario editing means including the GUI and outputting first scenario data corresponding to the display of the GUI on a one-to-one basis;
With the first scenario data and the material information data referenced by the first scenario data as inputs, the second scenario data associated with a predetermined data structure and the AV referenced by the second scenario data A scenario data conversion apparatus comprising: data conversion means for outputting encoded information data for encoding a stream. The data conversion means detects a tag name or an attribute value associated with the tag described in the first scenario data, and determines a conversion method;
From the tag name or the attribute value associated with the tag determined by the determination means, one or more conversion means for appropriately converting based on a predetermined data structure;
The scenario data conversion apparatus according to claim 1, further comprising a combining unit that combines the data converted by the one or more conversion units and outputs the second scenario data. The first scenario data includes one or more first playlists describing a route or order of reproduction of the stream,
The first playlist includes stream information for multiplexing one or more elementary streams used for reproduction, and stream attribute information indicating attributes of the one or more elementary streams,
The data conversion means reads the first scenario data, detects a first playlist included in the first scenario data, and detects the first playlist when the first playlist is detected. 2. The scenario data conversion apparatus according to claim 1, wherein second scenario data including a second playlist created by referring to predetermined information included in the stream attribute information referred to by the list is output. . The first scenario data includes an item indicating whether or not to display a static object that does not have a command to execute processing and the focus of the cursor does not change by a user operation,
The data conversion means reads the first scenario data, detects an item indicating whether or not to display the static object included in the first scenario data, and displays the static object 2. The second scenario data including a data structure that displays a button that does not have a command and that does not cause the cursor focus to be changed by a user operation is output when detected. Scenario data conversion device. The first scenario data includes an item indicating whether or not to display a check box having a function of switching between the on state and the off state,
The data conversion means reads the first scenario data, detects whether or not the check box is included in the first scenario data, and when the check box is detected, the first data indicating the on state is displayed. And a second button representing the off state, one of the first button and the second button is displayed on the screen, and the first button is the first button When the button is pressed while the screen is displayed, the second button has a command for switching the screen display to the second button. The second button displays the screen when the second button is pressed while the screen is displayed. The scenario data conversion apparatus according to claim 1, wherein the second scenario data including a data structure having a command for performing a process of switching to the first button is output. The first scenario data includes an item indicating whether or not to display a radio button having a function of switching at least two or more and being switched on exclusively.
The data conversion means reads the first scenario data, detects whether or not the radio button is included in the first scenario data, and when the radio button is detected, the first data indicating the on state is displayed. And a second button indicating a cut-off state, one of the first button and the second button is displayed on the screen, and the second button has the second button A command that has a command that switches the screen display to the first button when pressed while the screen is displayed, and a button that switches the screen display of other radio buttons on the screen to a button that indicates the off state. The scenario data conversion device according to claim 1, wherein the second scenario data including a data structure including: is output. A scenario data conversion method that outputs scenario data associated with a predetermined data structure that realizes a scenario created by a user,
The user creates a scenario using the GUI,
A scenario editing step that includes the GUI and outputs first scenario data corresponding to the display of the GUI on a one-to-one basis;
With the first scenario data and the material information data referenced by the first scenario data as inputs, the second scenario data associated with a predetermined data structure and the AV referenced by the second scenario data A scenario data conversion method comprising: a data conversion step of outputting encoded information data for encoding a stream. In the data conversion step, a determination step of detecting a tag name or an attribute value associated with the tag described in the first scenario data and determining a conversion method to be executed;
One or more conversion steps for appropriately converting the tag name or the attribute value associated with the tag determined in the determination step into a predetermined data structure based on a generation rule;
The scenario data conversion method according to claim 7, further comprising a combining step of combining the data converted in the one or more conversion steps and outputting the second scenario data. The first scenario data includes one or more first playlists describing a route or order of reproduction of the stream,
The first playlist includes stream information for multiplexing one or more elementary streams used for reproduction, and stream attribute information representing attributes of the one or more elementary streams,
In the data conversion step, the first scenario data is read, a first playlist included in the first scenario data is detected, and when the first playlist is detected, the first playlist is detected. The scenario data conversion according to claim 7, wherein second scenario data including a second playlist created by referring to predetermined information included in the stream attribute information referred to by the playlist is output. Method. The first scenario data includes an item indicating whether or not to display a static object that does not have a command to execute processing and the focus of the cursor does not change by a user operation,
In the data conversion step, the first scenario data is read, an item indicating whether or not to display the static object included in the first scenario data is detected, and the static object is displayed. 8. The second scenario data including a data structure for displaying a button that does not have a command and that does not cause the cursor focus to be changed by a user operation is output when detected. Scenario data conversion method. The first scenario data includes an item indicating whether or not to display a check box having a function of switching between the on state and the off state,
In the data conversion step, the first scenario data is read to detect whether the check box is included in the first scenario data. When the check box is detected, the first scenario data indicates the on state. One button and a second button indicating the off state, and either the first button or the second button is displayed on the screen,
The first button has a command for performing a process of switching the screen display to the second button when the first button is pressed while the screen is displayed, and the second button has the second button The scenario according to claim 7, wherein the second scenario data including a data structure having a command for performing a process of switching the screen display to the first button when the button is pressed during the screen display is output. Data conversion method. The first scenario data includes an item indicating whether or not to display a radio button having a function of switching at least two or more and being switched on exclusively.
In the data conversion step, the first scenario data is read, whether or not the radio button is included in the first scenario data is detected, and when the radio button is detected, the first scenario data indicates the on state. One button and a second button indicating the off state, and either the first button or the second button is displayed on the screen,
The second button has a command for performing a process of switching the screen display to the first button when the second button is pressed while the screen is displayed, and screens of other radio buttons on the screen at the same time. The scenario data conversion method according to claim 7, wherein the second scenario data including a data structure having a command for performing a process of switching to a button indicating a cut-off state is output. A recording medium that records a scenario data conversion program that outputs scenario data associated with a predetermined data structure for realizing a scenario created by a user,
The user creates a scenario using the GUI,
A scenario editing step that includes the GUI and outputs first scenario data corresponding to the display of the GUI on a one-to-one basis;
With the first scenario data and the material information data referenced by the first scenario data as inputs, the second scenario data associated with a predetermined data structure and the AV referenced by the second scenario data And a data conversion step of outputting encoded information data for encoding the stream. A recording medium on which a scenario data conversion program is recorded. In the data conversion step, a determination step of detecting a tag name or an attribute value associated with the tag described in the first scenario data and determining a conversion method to be executed;
One or more conversion steps for appropriately converting the tag name or the attribute value associated with the tag determined in the determination step into a predetermined data structure based on a generation rule;
The recording medium recording the scenario data conversion program according to claim 13, further comprising a combining step of combining the data converted in the one or more conversion steps and outputting the second scenario data. The first scenario data includes one or more first playlists describing a route or order of reproduction of the stream,
The first playlist includes stream information for multiplexing one or more elementary streams used for reproduction, and stream attribute information representing attributes of the one or more elementary streams,
In the data conversion step, the first scenario data is read, a first playlist included in the first scenario data is detected, and when the first playlist is detected, the first playlist is detected. The scenario data conversion according to claim 13, wherein second scenario data including a second playlist created by referring to predetermined information included in the stream attribute information referred to by the playlist is output. A recording medium that records the program. The first scenario data includes an item indicating whether or not to display a static object that does not have a command to execute processing and the focus of the cursor does not change by a user operation,
In the data conversion step, the first scenario data is read, an item indicating whether or not to display the static object included in the first scenario data is detected, and the static object is displayed. 14. When the item is detected, the second scenario data including a data structure that displays a button that does not have a command and that does not cause the cursor focus to be changed by a user operation is output. A recording medium on which the described scenario data conversion program is recorded. The first scenario data includes an item indicating whether or not to display a check box having a function of switching between the on state and the off state,
In the data conversion step, the first scenario data is read to detect whether the check box is included in the first scenario data. When the check box is detected, the first scenario data indicates the on state. One button and a second button indicating the off state, and either the first button or the second button is displayed on the screen,
The first button has a command for performing a process of switching the screen display to the second button when the first button is pressed during the screen display, and the second button includes the second button The scenario according to claim 13, wherein the second scenario data including a data structure having a command for performing a process of switching the screen display to the first button when the button is pressed during the screen display is output. A recording medium on which a data conversion program is recorded. The first scenario data includes an item indicating whether or not to display a radio button having a function of switching at least two or more and being switched on exclusively.
In the data conversion step, the first scenario data is read, whether or not the radio button is included in the first scenario data is detected, and when the radio button is detected, the first scenario data indicates the on state. One button and a second button indicating the off state, and either the first button or the second button is displayed on the screen,
The second button has a command for performing a process of switching the screen display to the first button when the second button is pressed while the screen is displayed, and screens of other radio buttons on the screen at the same time. 14. The recording medium recording the scenario data conversion program according to claim 13, wherein the second scenario data including a data structure having a command for performing a process of switching the display to a button indicating the off state is output.

Images