JPH08202680A - Editing process method for scenario data - Google Patents

Abstract

PURPOSE: To easily grasp a screen image when scenario data are generated, a screen image at the time of execution, and a procedure for operation that a user performs at the time of execution by generating screen images of respective scenes described in the scenario data and arraying and listing the screen images on a single screen called stroboscopic screen. CONSTITUTION: A scenario data execution system 15 executes the scenario data and requests a stroboscopic command control part 11 for registration to stroboscopic data every time a scene changes. A stroboscopic screen control part 13 sets the number of screen images of the stroboscopic screen and the display size of the screen images on the basis of the stroboscopic data that a stroboscopic data management part 12 manages to display the stroboscopic screen. Consequently, every time time a screen image of a new scene is registered in the stroboscopic data, the screen image is added and displayed on the stroboscopic screen and at the end of the execution of the scenario data, screen images of all scenes are listed and displayed on the strobe screen.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method of editing scenario data for describing a scenario of presentation software or a multimedia title created by combining a plurality of media materials such as characters, images and sounds. In particular, in the presentation creation tool and multimedia title creation tool, screen images for each scene are displayed in a list so that scenario data can be edited and the efficiency of creating image data is improved.

[0002]

2. Description of the Related Art Presentation software and multimedia titles display characters (text) and images on a screen according to a scenario created in advance and output speech, sound, music, etc., depending on conditions or unconditional conditions. The screen is switched by and the comprehensive information is presented.

Such presentation software and multimedia titles select, process, and output the type and content of the media material to be used according to each scene (scene), each time, each condition, etc. A program that describes the flow of processing is called scenario data. FIG. 10 shows an example of scenario data. In FIG. 10, (a) stores scenario data, and (b) stores data of different media materials such as pictures, sounds, and texts used by the scenario data. It is a database.

In the scenario data (a), in the step after the start, the picture PC 1 is taken out from the database (b) and displayed on the screen, and the buttons are set. When the button is pressed, the sound SN1 is output, when the button is pressed, the sound SN2 is output, and when the button is pressed, the picture currently displayed is ended.

In the next step, a mathematical expression is calculated, and then the picture PC2 and the text TX1 are retrieved from the database (b). In the next step, the picture PC2 and the text TX1 are displayed for one minute, and the process ends.

When such scenario data is created by the conventional presentation creation tool and multimedia title creation tool, it is usual to create an image for each scene in advance. It was easy to understand the execution image of.
However, when the scenario data is retrieved from the database and displayed at the time of execution, or when the user handles the data specified at that time, there is a problem that the image at the time of execution of the scenario data cannot be predicted. It was

As described above, when the screen image of the user at the stage of creating the scenario data and the image at the stage of the actual use by the user do not match,
Even if there is a request to know what the screen image the user had at the stage of creating scenario data, there is no conventional method to satisfy this, and the screen at the stage when the scenario data is executed I could not edit the scenario data from the image again.

[0008] In addition, most of the conventional multimedia title creation tools use the icon base to display the scenario creation description without displaying the screen image.
It was difficult to understand the screen image at runtime during creation.

[0009]

SUMMARY OF THE INVENTION According to the present invention, in a presentation software or a multimedia title creation tool, a screen image at the time of creating scenario data, a screen image at the time of execution, and an operation procedure performed by the user at the time of execution. The purpose is to be able to easily understand such things.

[0010]

According to the present invention, a screen image is created for each scene described by scenario data, and the screen images are arranged in a single screen called a strobe screen and displayed in a list. ， By making it easy to recognize the flow of the whole screen image accompanying the execution of scenario data, and by editing the individual screen images displayed on the flash screen and automatically reflecting the results in the scenario data, Make it easy to edit data scenes. Furthermore, the data of the strobe screen and each screen image displayed there are managed by information called strobe data, which facilitates editing of the screen image, saving of strobe data, printing, and the like.

FIG. 1 illustrates the principle of the present invention. In FIG. 1, 10 is a processing device, 11 is a strobe command control unit, 12 is a strobe data management unit, 13 is a strobe screen control unit, 13a is a strobe screen editing unit, 14 is a scenario data editing system, and 15 is a scenario data execution system. , 16 is an initialization / post-processing unit, 17 is a strobe data file, 18 is a multimedia database, 19 is a display device, 20 is a strobe screen, 21 is a speaker, 22 is a mouse, and 23 is a keyboard.

The strobe command control unit 11 is a module for performing control related to the strobe screen by a command input from the strobe screen 20 and a command issued by the scenario data execution system 15. The control commands are as follows.

-Read (from strobe screen): Read the designated strobe data into the memory and display the strobe screen. -Save (from flash screen): Save the specified flash data to a file.

-Print (from strobe screen): Designate and print strobe data or an image on the strobe screen. -Edit (from strobe screen): Edit processing is performed on each screen image of the strobe screen.

-Initialization (from strobe screen / execution system): Performs initialization for starting strobe screen control. -Registration (from the execution system): When executing the scenario data, the screen image data for each scene is registered in the strobe data.

-Update (to editing system): The editing result on the flash screen is reflected in the scenario data. The strobe data management unit 12 is a module that manages strobe data that manages each screen image created for each scene to be displayed on the strobe screen 20. The contents of the strobe data are shown below: -Strobe file name-Address to each screen image managed in strobe data-Screen data storage address in this data-Scenario data name that created strobe data-Source of screen data -The number of screen data registered in the strobe data-The date of the scenario data The strobe screen controller 13 is a module that receives commands from the user on the strobe screen 20 and controls the screen. The methods for receiving commands from the user and controlling the screen are as follows.

-Receiving method by menu (Read, save, print, and initialization commands are set by the menu on the strobe screen.)-Receiving method by mouse (picture of icon on strobe screen (read, save) , Print, initialization commands drawn by icons) are pressed with the mouse.)-Strobe screen scroll control-Strobe screen display (for example, 1/8 of the display)
Stroke screen editing unit 13a is a module that enables editing of each screen image on the strobe screen. The screen image can be edited by selecting an arbitrary screen image by using the icon, and correcting, deleting, or replacing it. The editing result is notified from the strobe command control unit 11 to the scenario data editing system 14 by an update command, and the scenario data is reflected.

The scenario data editing system 14 is a module for editing the scenario data. When an arbitrary screen image is edited on the strobe screen by the strobe screen editing unit 13a and an update command is issued from the strobe screen control unit 13, the number of the scene corresponding to the screen image is known from the strobe data.
From now on, edit the scene that is the basis of the arbitrary screen image.

The scenario data execution system 15 is a module for executing scenario data. The strobe command control unit 11 is requested to register the screen image data for each scene of the execution result in the strobe data.
By registering the screen image data in the strobe data, the screen image is displayed on the strobe screen.

The initialization / post-processing section 16 is provided for each module 1
For 1 to 15: Initialize the memory required to open the strobe screen, strobe screen control information, and strobe data management information.

The processing for ending the strobe screen is performed. The strobe data file 17 is used to store strobe data.

The multimedia database 18 provides media material data such as images, sounds and texts used when the scenario data execution system 15 executes scenario data.

[0023]

The general operation of the configuration shown in FIG. 1 is as follows. (1) At the start of the scenario data editing process using the flash screen, the initialization / post-processing unit 16 is activated to acquire a memory for reading the flash data and initialize each module. (2) The strobe command control unit 11 reads the strobe data specified in the memory in response to the read command, or initializes the strobe data in the memory. (3) The scenario data execution system 15 executes the scenario data, and every time the scene changes, requests the strobe command control unit 11 to register the strobe data in order to additionally display the screen image on the strobe screen. (4) The strobe command control unit 11 causes the strobe data management unit 12 to perform registration processing to strobe data for the requested screen image, and then causes the strobe screen control unit 13 to display the strobe screen. (5) The strobe screen control unit 13 sets the number of screen images forming the strobe screen and the display size of the screen image based on the strobe data managed by the strobe data management unit 12, and displays the strobe screen. As a result,
Every time a screen image of a new scene is registered in the strobe data, the screen image can be additionally displayed on the strobe screen, and at the end of scenario data execution, the screen images of all scenes are displayed in a list on the strobe screen. To be done. (6) The strobe command control unit 11 responds to the save command, stores the strobe data in a file for long-term storage, or responds to the print command, and responds to the strobe data and the strobe screen managed by the strobe data. Print the image of. (7) The strobe screen editing unit 13a is activated by an editing command from the strobe screen, displays the strobe screen edit screen in a window, and modifies any screen image in the strobe screen in response to an instruction for editing operation by an icon or the like. Edit processing such as deletion, replacement, etc. The edited result is not immediately reflected on the strobe data and the strobe screen, but the strobe command control unit 11 issues an update command to the scenario data editing system 14, and at that time, the edited result on the strobe screen is notified. The screen image to be edited is associated with the scene number by the strobe data. In response to the update command, the scenario data editing system 14 re-edits the scene of the scenario data according to the editing result of the strobe screen and updates the scenario data. For example, if the result of editing the strobe screen is a correction of a screen image, the corresponding scene in the scenario data is changed to that corresponding to the corrected screen image. When a screen image is deleted or replaced with another screen image, the corresponding scene in the scenario data is deleted or replaced with another scene. (8) The scenario data updated by reflecting the editing result of the strobe screen can be re-executed by the scenario data execution system 15. In that case, as in the last time, each scene of the updated scenario data is re-executed. Are registered in the strobe data, and screen images of those scenes are displayed on the strobe screen. This operation can be repeated any number of times.

[0024]

EXAMPLE An example of the present invention will be described with reference to FIGS. FIG. 2 shows the configuration of an embodiment of a multimedia title creation processing system to which the method of the present invention is applied. The blocks denoted by 11 to 16 in FIG. 2 respectively correspond to the components 11 to 16 in FIG. 1, and therefore, the same reference numerals and element names are used.

In FIG. 2, the strobe command control unit 1
Reference numeral 1 has functions of initializing a strobe command, reading strobe data, saving strobe data, printing strobe data, and registering strobe data, each of which is activated by a control command.

The strobe command initialization function initializes strobe data controlled on the strobe screen.
The data required for initialization is the strobe file name,
The scenario data name that created the flash data, the scenario data date, and the number of screen data registered in the flash data are required. This function is initialized / read on the flash screen or initialized from the scenario data execution system (issued first when the flash screen is displayed)
Is started when you do.

The strobe data reading function reads strobe data and manages the strobe data under control. After reading, the display processing is instructed to the strobe screen control unit.

The strobe data saving function saves strobe data in a file. The strobe data print function prints strobe data and screen data. With the strobe data registration function, screen images are registered in strobe data. The data required for registration is the screen image and the scene ID that is the source of the screen image. When the registration process to the strobe data is performed, the display process for the strobe screen is performed.

The strobe data management unit 12 has a strobe data management function and a screen image table management function. The flash data management function manages the flash data that is being controlled on the flash screen. The management information is updated when the flash data is saved and registered.

The screen image table management function manages the screen image table being controlled by the flash screen. The screen image table stores a screen number, an address to the screen image, and a scene ID.

The flash screen control unit 13 has a screen image addition function, a screen display format setting function, and a screen control function. The screen image addition function is used to add a screen image to the flash screen.

The screen display format setting function initializes the format displayed on the flash screen. Here, the size of the screen image and the maximum number of vertical and horizontal screen images to be arranged and displayed on the screen are set.

The screen control function performs a process related to screen control of the flash screen. Screen control includes scrolling, displaying, changing the screen size, and the like. The scenario data editing system 14 has a scene editing function, and activates an editing screen of a matched scene from a scene ID of an arbitrary screen image of strobe data.

The scenario data execution system 15 has a screen image addition function and requests the strobe command control section 11 to register a screen image for each scene. The initialization / post-processing unit 16 has a strobe control initialization function and a post-processing function.

In the strobe control initialization function, a memory required for the strobe screen control section, strobe data management section, and strobe command control section is acquired, and initialization processing of each control section is performed.

The post-processing function of the strobe control performs post-processing of the strobe screen control section, strobe data management section and strobe command control section. FIG. 3 shows an example of a flash screen as a result of executing one scenario data. On the illustrated strobe screen, 10 screen images are arranged in 2 rows × 5 columns, and 10 scenes of the entire scenario data can be viewed on one screen. The screen image array and the size of the screen image are changed depending on the number of screen images to be displayed.

FIG. 4 shows the structure of a screen image table for managing each screen image displayed on the flash screen. Each screen image has a screen No. Are sequentially assigned, and an image pointer indicating the start address of the memory area in which the screen image data is stored and the corresponding scene ID in the scenario data are set for each.

5 to 9 show the flow of main processing of the system according to the embodiment of the present invention. The operation will be described below for each flow. FIG. 5 is a flow chart of reading processing of strobe data. In the flow, (5-1) Select the reading process from the flash screen,
Also select the strobe file name to read. (5-2) Request the reading of strobe data to the strobe command controller. (5-3) Open the file specified by the strobe file name and copy the file contents into memory. (5-4) The procedure for expanding the strobe data to be registered, which is to be registered in the strobe data management unit according to the strobe data structure, is as follows.

Screen image tables for storing the start addresses of the screen images are created for the number of screen images registered in the strobe data. The scene ID of the screen image creation source is also stored in this table at the same time (see FIG. 4). (5-5) Register the screen display format in the strobe data management unit. This information is called strobe screen information, and the strobe screen is reset according to this information.

The following information is set in this information. Screen image size Maximum number beside the screen image Strobe data name (5-6) From the screen image table, for each image,
Causes the strobe command control unit to process to display on the strobe screen. (5-7) The strobe command control unit displays a screen image on the strobe screen (see FIG. 3).

FIG. 6 is a flow of strobe data registration processing. In the flow, (6-1) the strobe data screen information is initialized. If the strobe data has not been read, initialization is performed before the execution of the scenario data is started. The data required for initialization are as follows.

Strobe data name Scenario data name that is the source of strobe data, screen image size
Vertical x horizontal number of screen image Vertical x horizontal size of screen image Scenario data date (6-2) Before execution of scenario data, inquires about the currently displayed strobe data information and if it does not match the strobe data to be executed Resets the flash screen information. (6-3) While executing the scenario data, request the strobe command control unit to register the screen image in the strobe management unit first for each scene. The processing required for registration is shown below.

An image of a scenario data execution screen is created according to the screen image size, 160 × 120.
Is the default. The pointer or handle of the screen image and the scene ID of the creation source are used as registration information and registered in the flash data management unit. (6-4) In the strobe data management unit, if the scene IDs of the screen images requested to be registered match, the screen images are replaced. The replaced screen image is discarded. If there is no matching data, a new screen image is registered. (6-5) Display the updated / newly registered screen image on the flash screen.

FIG. 7 is a flow of strobe data storage processing. In the flow, if (7-1) strobe data saving is selected from the strobe screen, the strobe command control unit is requested to save strobe data. (7-2) With the strobe command, the current command control state is checked, and if it can be saved, a saving request is issued to the strobe data management unit. (7-3) Save the strobe data. The storage procedure is as follows.

The VL (version level) of strobe data is set. Set the scenario data name from which the strobe data was created and its purpose.

Set the display format of the strobe screen (length x width, screen data size). Set screen image table. After that, the screen image data is continuously output.
The address (position from the beginning of the file) where the screen image is set is set in the screen image table.

After outputting the last screen image, the number of screen images is set. FIG. 8 is a flowchart of a strobe data printing process. In the flow, (8-1) printing of strobe data is selected on the strobe screen. There are three printing methods: a method of printing all the data one by one, a method of selecting and printing one screen image, and a method of printing the screen of the strobe screen as it is on one sheet of paper. (8-2) In the flash command control, the following (8-3-1) and (8) are used based on the printing method selected on the flash screen.
-3-2) and (8-3-3) are classified into three print controls. (8-3-1) When printing one screen data, the data is extracted from the selected screen number and printed on one paper. (8-3-2) When printing all screen images of strobe data, printing is performed in order from the first number in the screen image table. For example, if there are 20 screen images, the number of printed sheets is 20. (8-3-3) When printing with the flash screen as it is, printing is performed with the flash screen displayed. If 2 x 4 screen images are arranged on the screen,
The number of screen images output on the printing paper is eight (2 × 4).

FIG. 9 is a flow chart showing a scenario data editing process on the flash screen. In the flow, (9-1) an edit command is selected on the flash screen, and an arbitrary screen image is selected to edit the scene. When the edit command is selected, the edit screen is displayed. The edit screen is associated with each screen image of the flash screen, and editing operations can be performed on an icon basis. (9-2) When the edit command is selected, the strobe command control unit receives from the strobe data management unit the scene number from which the screen image was output. (9-3) Next, the strobe command control unit requests the scenario data editing system to edit the scene. At this time, the scene number is passed to the editing system. (9-4) The editing system activates an editing screen so that the scene corresponding to the scene number can be edited. The result edited here is not reflected on the strobe screen and strobe data.

The edited scenario data can be executed again. It can be output to the flash screen again by executing.

[0050]

By using the method of the present invention, a scene can be created by using the data of the database accessed at the time of execution of the scenario data created by the presentation creation tool or the multimedia title creation tool or the data specified by the user. Even if it is generated, the execution result of the scenario data can be easily confirmed by referring / comparing with a series of screen images and printing out.

In creating the scenario data, since the corresponding scene can be easily edited from the executed image, the efficiency of creating the scenario data is improved. The effect is obtained.

[Brief description of drawings]

FIG. 1 is a diagram illustrating the principle of the present invention.

FIG. 2 is a block diagram of an embodiment of a multimedia title creation processing system.

FIG. 3 is an explanatory diagram of an example of a flash screen.

FIG. 4 is a diagram illustrating the configuration of a screen image table.

FIG. 5 is a flow chart of reading processing of strobe data.

FIG. 6 is a flowchart of a strobe data registration process.

FIG. 7 is a flow diagram of strobe data storage processing.

FIG. 8 is a flowchart of a print process of strobe data.

FIG. 9 is a flowchart of a scenario data editing process using a flash screen.

FIG. 10 is an explanatory diagram of scenario data.

[Explanation of symbols]

 10 Processing Device 11 Strobe Command Control Unit 12 Strobe Data Management Unit 13 Strobe Screen Control Unit 13a Strobe Screen Editing Unit 14 Scenario Data Editing System 15 Scenario Data Execution System 16 Initialization / Post-Processing Unit 17 Strobe Data File 18 Multimedia Database 19 Display Device 20 Strobe screen 21 Speaker 22 Mouse 23 Keyboard

─────────────────────────────────────────────────── ─── Continuation of the front page (51) Int.Cl. ⁶ Identification code Internal reference number FI technical display location G06F 15/62 325 A

Claims (3)

[Claims] 1. A scenario data is described in a scenario data editing processing method for describing a scenario of a Machichi media title configured by connecting a plurality of scenes using a plurality of media materials including images. A method for editing scenario data, characterized by creating a screen image for each scene and displaying a strobe screen in which the created screen image for each scene is arranged on one screen. 2. The method for editing scenario data according to claim 1, wherein the screen image is edited on the flash screen and the edited result is reflected in the scenario data for editing. 3. The strobe data according to claim 1, wherein strobe data for managing a scene of scenario data and a screen image of a strobe screen in association with each other are created, and the strobe can be stored and printed. Edit processing method for scenario data.