JP4063566B2 - Program production method - Google Patents

Description

[0001]
BACKGROUND OF THE INVENTION
The present invention relates to a program production apparatus used for television broadcast program production, video program production, program simulator, presentation, demonstration, etc., in particular, the program information is described and described in order to generate a program using a computer. The present invention relates to a program production method for producing a program.
[0002]
[Prior art]
A conventional program production apparatus that combines a CG (computer graphics) animation technique, a voice synthesis technique, a moving picture reproduction technique, and the like to produce a program using a computer will be described.
[0003]
A block showing an example of the configuration of the program production apparatus is shown in FIG. 201 is a CPU (Central Processing Unit), 202 is a memory, 203 is a CG animation generation unit, 204 is a speech synthesis unit, 205 is a sequencer unit, 206 is an event storage unit, 207 is a program information production unit, 208 is a recording device, 209 Is a moving image generation unit, 210 is a display, 211 is a mouse and keyboard, and 212 is a bus.
[0004]
The CPU 201 is connected to a memory 202, a CG animation generation unit 203, a voice synthesis unit 204, a sequencer unit 205, an event storage unit 206, an editing screen generation unit 207, a recording device 208, a moving image generation unit 209, and a display 210 via a bus 212. , Connected to mouse, keyboard 211.
[0005]
In FIG. 2, a CG animation generating unit 203 generates a CG animation of an appearing character or a studio set, and a voice synthesizing unit 204 generates a voice of the appearing character (serif, cry, imitation, studio sound effect (BGM), etc.). The moving image generation unit 209 generates a moving image. Based on the program information recorded in the storage device 208, the sequencer unit 205 controls the CG animation generation unit 203, the voice synthesis unit 204, and the moving image generation unit 209 to sequentially generate television programs. The generated video is displayed on the screen of the display 210.
[0006]
In the program information creation unit 207, an operation window for the user to describe (operate and edit) the program information is displayed on the screen of the display 210, and the user can interactively write a TV program in the manner of writing a scenario. is doing.
[0007]
The recording device 208 stores CG character modeling data, studio set data, video information of moving images, audio data (music, background sounds, other audio data), and the like. Program information is also stored in the recording device 208. The recording device 208 may be a hard disk, a magneto-optical disk, a floppy (registered trademark) disk, or a remote file via a transmission network. In the case of a plurality of recording devices 208, it is not necessary that all the above-mentioned data is recorded in the same recording device 208. The modeling data of the CG character is the recording device A, and the audio data is the recording device B. It is also possible.
[0008]
It is assumed that program information handled by the CG animation generation unit 203, the voice synthesis unit 204, the moving image generation unit 209, and the program information creation unit 206 is written in a TVML (TV Program Making Language) language.
[0009]
According to the rules of the TVML language specification Ver1.0 (http://www.strl.nhk.or.jp/TVML/Japanese/J03.html), one event is described as follows. Event type: Command name (arg1 = data1, arg2 = data2, arg3 = data3 ...)
There are 11 event types, each with multiple commands. The args in the command arguments are in no particular order.
[0010]
The program information is stored in the recording device 208 as a text file. (Hereafter, a text file in which program information is described is referred to as a script file).
[0011]
An example in which the reading source script file stored in the recording device 208 is displayed on the display 210 is shown in FIG. FIG. 3 is a display example when an arbitrary text editor is used. 300 is a script file, 301 is a pull-down menu, 302-1 to 302-5, 303-1 to 303-5, and 304-1 to 304-5 are cut program information, of which 302-1 to 302-5 , 303-1 to 303-5 are comment lines extending over a plurality of lines, and 304-1 to 304-5 are TVML command groups. Here, comment lines 302-1 to 302-5 and 303-1 to 303-5 extending over a plurality of lines are cut numbers 302-1 to 302-5 indicating the top of the cut and cut descriptions 303-1 to 303. For each of the TVML command groups 304-1 to 304-5 in each cut, a plurality of comment lines (for example, a cut number consisting of 302-1 and 303-1 and a cut It consists of explanations).
[0012]
The reading source script file 300 of FIG. 3 recorded in the recording device 208 of FIG. 2 is read from the “script reading” in the pull-down menu 420 on the upper side of the editing screen 401 of FIG. An example is not shown).
[0013]
The vertical axis of the edit screen 401 is a time axis, and program information is generated in order from the top to the bottom of the screen.
[0014]
On the left side of the edit screen 401, there are a studio block 402, a movie block 403, and a title block 404 (not shown), and a column of these blocks indicates a video output on the television screen. In the studio block 402, a CG character can speak, walk, and set camera work in the CG studio. The movie block 403 is a part that performs playback control of an edited moving image prepared in advance, and the title block 404 is a part that controls display of character information on a television screen and display of a still image.
[0015]
On the editing screen 401, editing operations such as new block creation, copy, cut, insertion, and deletion can be performed. These edits are performed by “new creation”, “copy”, “cut”, “insert”, and “delete” in the pull-down menu 420 (a display example of the pull-down menu 420 is not shown).
[0016]
Further, the studio block 402 includes a serif setting unit 410, an operation setting unit 411, and a camera / lighting setting unit 412 as setting parts unique to the studio block 402. The serif setting unit 410 is a part for setting the serif of the CG character, the action setting unit 411 is a part for setting the movement of the CG character, and the camera / lighting setting unit 412 is a part for setting the camera work in the studio. is there.
[0017]
On the right side of the edit screen 401, there are a super setting unit 405, a sound setting unit 406, a narration setting unit 407, and various setting setting units 408 as common setting parts of the studio block 402, the movie block 403, and the title block 404. The super setting unit 405 is a part that controls the composition of superimpose characters on the video output to the television, the sound setting unit 406 is a part that controls the music to be synthesized to the video, and the narration setting unit 407 is a movie playback This is a part for synthesizing narration with video, etc., and various setting setting unit 408 is a part for setting waiting time and the like.
[0018]
Each block of studio, movie, and title is composed of units called events in the vertical direction. The event 422 is one event constituting the studio block 402, and the event 421 is one event constituting the movie block 403. Further, this event is composed of units called several cells in the horizontal direction. The event 422 includes cells from the serif setting unit 410 to various setting setting units 408, and the event 421 includes cells from the super setting unit 405 to various setting setting units 408. In the case of the studio block 402, the program information 428 is displayed in this cell, and in the case of the movie block 403 and the title block 404, the program information 428 is displayed above this block and the cell.
[0019]
In addition, a time code 409 corresponding to each event exists at the left end of the edit screen 401, and a representative screen 413 indicating the top screen of the block exists in each block of the movie and title.
[0020]
Processing until the reading source script file 300 in FIG. 3 is read by the conventional program information production unit 207 in the program production apparatus in FIG. 2 and displayed on the editing screen 401 in FIG. 4 will be described with reference to FIGS. . In addition, the same number was attached | subjected to the component same as the component demonstrated so far.
[0021]
The initial screen 401-1 of the display 210 when the reading source script file 300 of FIG. 3 recorded in the recording device 208 of FIG. 2 is read by the conventional program information production unit 207 in the program production device of FIG. As shown in FIG.
[0022]
When a program producer (hereinafter referred to as an operator) clicks a file menu 550 in the pull-down menu 420 with the mouse pointer 560, a file menu list 551 is displayed. The file menu list 551 includes a newly created item 552, a script reading item 553, a script saving item 554, and an application end item 555. On the initial screen, only a start block 556 indicating the beginning of the program and an end block 557 indicating the end of the program are displayed. 558 is a narration setup button, and 559 is various setting setup buttons. When reading the reading source script file 300, the script reading item 553 is selected.
[0023]
The read source script file 300 of FIG. 3 recorded in the recording device 208 of FIG. 2 is read into the conventional program information production unit 207 in the program production device of FIG. A specific flow will be described with reference to FIG.
[0024]
In step 600 of FIG. 6, the operator selects the script reading item 553 of FIG. Next, in step 601, the reading source script file 300 is opened. Next, in step 602, one line of the character string is read from the file in step 601. In step 603, it is compared whether the character string in step 602 is a TVML command or not. If true, go to step 604. If false, go to step 605.
[0025]
In step 604, a block or event is created on the editing screen 401 in accordance with the contents of the command, and characteristic contents such as a command name and an argument value described in the command are displayed in the block or cell. Next, in step 605, it is determined whether processing has been performed to the end of the file. If true, go to step 606. If it is false, the process returns to step 602 and the processes of steps 602 to 604 are repeated. In step 606, the file in step 601 is closed. This is the end of this process.
[0026]
FIG. 7 shows details of the processing in step 604 of the processing in FIG. At the start of FIG. 7, it is known that the character string in one line read from the read source script file 300 is a TVML command.
[0027]
First, in step 700, it is compared whether the command is a movie command. If true, go to step 701; if false, go to step 705. In step 701, it is checked whether or not a movie block has not been created on the edit screen 401. If true, go to step 702; if false, go to step 703. In step 702, a new movie block is created. Next, in step 703, one event is created in the movie block. In step 704, characteristic contents such as a command name and an argument value described in the command are displayed in the movie block.
[0028]
In step 705, it is compared whether the command is a title command. If true, go to step 706; if false, go to step 710. In step 706, it is checked whether a title block has not yet been created on the edit screen 401. If true, go to step 707; if false, go to step 708. In step 707, a new title block is created. Next, in step 708, one event is created in the title block. In step 709, characteristic contents such as a command name and an argument value described in the command are displayed in the title block.
[0029]
In step 710, it is compared whether the command is a character, camera, prop, or lighting command. If true, go to step 711; if false, go to step 715. In step 711, it is checked whether or not a studio block has not yet been created on the editing screen 401. If true, go to step 712; if false, go to step 713. In step 712, a new studio block is created. Next, in step 713, one event is created in the studio block. Next, in step 714, characteristic contents such as a command name and an argument value described in the command are displayed in the studio block line, operation, and cell of the camera / light setting unit.
[0030]
In step 715, it is compared whether the command is a super command. If true, go to step 716; if false, go to step 717. In step 716, characteristic contents such as a command name and an argument value described in the command are displayed in a cell of the super setting unit.
[0031]
In step 717, it is compared whether the command is a sound command. If true, go to step 718; if false, go to step 719. In step 718, characteristic contents such as a command name and an argument value described in the command are displayed in a cell of the sound setting unit.
[0032]
In step 719, it is compared whether the command is a narration command. If true, go to step 720; if false, go to step 721. In step 720, characteristic contents such as a command name and an argument value described in the command are displayed in a cell of the narration setting section.
In step 721, characteristic contents such as a command name and argument values described in the command are displayed in cells of various setting setting units.
[0033]
When the above processing is performed, an edit screen 401 shown in FIG. 4 is displayed. However, in this reading process, only the TVML command group 304 is read from the program information of each line described in the script file 300 in FIG. 3 in step 603 in FIG. 302-2, 302-3, 302-4, 302-5, 303-1, 303-2, 303-3, 303-4, 303-5 are not read, so the program information displayed on the edit screen 401 is The script file 300 is limited to the TVML command group 304.
[0034]
Next, the reading source script file 300 of FIG. 3 recorded in the recording device 208 of FIG. 2 is read after the reading process of reading into the conventional program information production unit 207 in the program production device of FIG. A process of saving the program information in the save destination script file of the recording device 208 will be described with reference to FIGS. In addition, the same number was attached | subjected to the component same as the component demonstrated so far.
[0035]
8 shows the display after the reading process of reading the reading source script file 300 of FIG. 3 recorded in the recording device 208 of FIG. 2 into the conventional program information production unit 207 in the program production device of FIG. This is the editing screen displayed in 210.
[0036]
When the reading result after the reading process is completed is saved in the save destination script file of the recording device 208 in FIG. 2, the file menu 550 of the pull-down menu 420 is clicked with the mouse pointer 560. Then, a file menu list 551 is displayed, and a script saving item 554 is selected.
[0037]
FIG. 19 shows a screen on which the saving result script file is displayed on the display 210 after saving the reading result after the reading process is completed in the saving script file of the recording device 208 of FIG. FIG. 19 is a display example when an arbitrary text editor is used. 1900 is a script file, and 1902 is a TVML command group.
[0038]
Hereinafter, a specific flow of the script file saving process for saving the reading result after the reading process is completed in the saving destination script file of the recording device 208 of FIG. 2 will be described with reference to FIG.
[0039]
In step 900 of FIG. 9, the operator selects the script storage item 554 of FIG. In step 901, the save destination script file 1900 is opened. In step 902, the data of one event on the editing screen is read from the memory. The event data stores the contents displayed in the block or cell. Next, in step 903, it is compared whether the event in step 902 is an event in the studio block or not. If true, go to step 904. If false, go to step 907. In step 904, storage processing is performed on the cell data of the speech setting unit. Next, in step 905, a storage process is performed on the cell data of the operation setting unit. Next, in step 906, the cell data of the camera / illumination setting unit is stored, and the process proceeds to step 911.
[0040]
In step 907, it is compared whether the event in step 902 is an event in the title block or not. If true, go to step 908. If false, go to step 909. In step 908, the title block data is saved and the process proceeds to step 911.
[0041]
In step 909, it is compared whether the event of step 902 is an event in a movie block or not. If true, go to step 910. If false, go to step 911. In step 910, the movie block data is saved, and the process proceeds to step 911.
[0042]
In step 911, the cell data of the super setting unit is stored. Next, in step 912, storage processing is performed on the cell data of the sound setting unit. Next, in step 913, storage processing is performed on the cell data of the narration setting unit. Next, in step 914, storage processing is performed on the cell data of the various setting setting units.
[0043]
Next, in step 915, it is determined whether the process has been completed up to the end of the edit screen. If true, go to step 916. If false, the process returns to step 902, and the processes of steps 902 to 614 are repeated. In step 616, the file in step 901 is closed. This is the end of this process.
[0044]
Here, FIG. 10 shows details of the processing related to the dialogue setting unit in step 904 of FIG. At the start of FIG. 10, it is known that one event read from the memory is in the studio block. First, in step 1000, it is determined whether or not there is data in the cell of the speech setting unit. If true, the process proceeds to step 1001, and if false, this process is terminated. In step 1001, the cell data is converted into a TVML command format according to the TVML language specification Ver1.0. In step 1002, the TVML command in step 1001 is saved in the save destination script file.
[0045]
Next, FIG. 11 shows details of processing related to the operation setting unit in step 905 of FIG. At the start of FIG. 11, it is known that one event read from the memory is in the studio block. First, in step 1100, it is determined whether or not there is data in the operation setting unit cell. If true, the process proceeds to step 1101, and if false, this process is terminated. In step 1101, the cell data is converted into a TVML command format in accordance with the TVML language specification Ver1.0. Next, in step 1102, the TVML command in step 1101 is saved in the save destination script file.
[0046]
Next, FIG. 12 shows details of processing relating to the camera / lighting setting unit in step 906 of FIG. At the start of FIG. 12, it is known that one event read from the memory is in the studio block. First, in step 1200, it is determined whether there is data in the cell of the camera / lighting setting unit. If true, the process proceeds to step 1201, and if false, this process is terminated. In step 1201, the block data is converted into a TVML command format in accordance with the TVML language specification Ver1.0. In step 1202, the TVML command in step 1201 is saved in the save destination script file.
[0047]
Next, FIG. 13 shows details of the processing relating to the title block in step 908 of FIG. At the start of FIG. 13, it is known that one event read from the memory is in the title block. First, in step 1300, the block data is converted into a TVML command format according to the TVML language specification Ver1.0. Next, in step 1301, the TVML command in step 1300 is saved in the save destination script file.
[0048]
Next, FIG. 14 shows details of the processing relating to the movie block in step 910 of FIG. At the start of FIG. 14, it is known that one event read from the memory is in the movie block. First, in step 1400, the cell data is converted into a TVML command format according to the TVML language specification Ver1.0. Next, in step 1401, the TVML command in step 1400 is saved in a save destination script file.
[0049]
Next, FIG. 15 shows details of processing related to the super setting unit in step 911 in FIG. First, in step 1500, it is determined whether or not there is data in the cell of the super setting unit. If true, the process proceeds to step 1501, and if false, this process is terminated. In step 1501, the cell data is converted into a TVML command format according to the TVML language specification Ver1.0. In step 1502, the TVML command in step 1501 is saved in the save destination script file.
[0050]
Next, FIG. 16 shows details of processing related to the sound setting unit in step 912 of FIG. First, in step 1600, it is determined whether there is data in the cell of the sound setting unit. If true, the process proceeds to step 1601, and if false, this process is terminated. In step 1601, the cell data is converted into a TVML command format according to the TVML language specification Ver1.0. In step 1602, the TVML command in step 1601 is saved in the save destination file.
[0051]
Next, FIG. 17 shows details of the processing related to the narration setting unit in step 913 of FIG. First, in step 1700, it is determined whether or not there is data in the cell of the narration setting section. If true, the process proceeds to step 1701, and if false, this process is terminated. In step 1701, the cell data is converted into a TVML command format according to the TVML language specification Ver1.0. In step 1702, the TVML command in step 1701 is saved in the save destination script file.
[0052]
Next, FIG. 18 shows details of processing related to various setting setting units in step 914 in FIG. First, in step 1800, it is determined whether or not there is data in the cells of the various setting setting units. If true, the process proceeds to step 1801, and if false, this process is terminated. In step 1801, the cell data is converted into a TVML command format according to the TVML language specification Ver1.0. In step 1802, the TVML command in step 1801 is saved in the save destination script file.
[0053]
When the above processing is performed, the save destination script file 1900 shown in FIG. However, as described above in the reading process, since the comment line is not read into the program information production unit 207 of FIG. 2, the comment line is not saved in the save destination script file 1900.
[0054]
[Problems to be solved by the invention]
A comment line exists in the reading source script file 300 in FIG. In particular, since the comment lines of the cut numbers 302-1 to 302-5 in the form of “// cut (number)” are described at the top of the cut program information, the cut information of the program information can be clearly understood. Since the comment lines 303-1 to 303-5 of the cut are described, the character of the cut can be easily understood.
[0055]
However, as described above, in the conventional technology, when the program information of the read source script file 300 is read into the program information production unit 207 of the program production device, the comment lines 302-1 to 302-5 and 303-1 to 303-5 are Ignored and only the contents of the TVML command group 304 are displayed on the edit screen 401 of FIG. Similarly, when the editing result of the editing screen 401 is saved in the save destination script file 1900, only the TVML command group 304 is saved in the save destination script file 1900, and comment lines 302-1 to 302-5, 303-1 to 303 are stored. -5 is not saved. As a result, even if the editing screen 401 or the save destination script file 1900 is viewed, there is a problem that the number of cuts and the explanation information of the cuts do not exist, and it is difficult for the operator to understand the program contents.
[0056]
An object of the present invention is to provide a program production method that displays comment lines and makes it easy to understand program contents.
[0057]
Another object of the present invention is to provide a program production method that displays comment lines in an easy-to-understand manner and makes program contents easier to understand.
[0058]
Still another object of the present invention is to provide a program production method for saving a displayed comment line in a save destination script file.
[0059]
[Means for Solving the Problems]
The present invention reads the comment line described at the head of the cut division cut when reading the program information of the cut division recorded in the recording device, and the read comment line and the comment line following the read comment line. A program production method characterized by displaying cut-cut program information on a screen.
[0060]
The present invention is the program production method, characterized in that the comment line is displayed in a comment block having the same width as the display block of the program information for the cut division.
[0061]
The present invention is the program production method characterized by editing the content of the comment line displayed on the screen.
[0062]
The present invention is a program production method characterized in that the read comment line and the cut program information following the comment line are stored in the recording device.
[0063]
The present invention is a program production method characterized in that a comment line displayed on a screen and the program information of the cut division following the comment line are stored in a recording device.
[0064]
The present invention is the program production method characterized in that the comment line is composed of a line of cut division number and a line of cut description.
[0065]
DETAILED DESCRIPTION OF THE INVENTION
Embodiments of the present invention will be described below. First, the read source script file 300 of FIG. 3 recorded in the recording device 208 of FIG. 2 is read into the program information production unit 207 of the embodiment of the present invention in the program production device of FIG. A specific flow of the file reading process is shown in FIG. Reading processing of the reading source script file 300 will be described with reference to FIGS.
[0066]
In step 100 of FIG. 1, the operator selects a script reading item 553 in the pull-down menu 420 on the initial screen 401-1 of FIG. Next, in step 101, the reading source script file 300 of FIG. 3 is opened. Next, in step 102, the comment flag which is an internal variable is set to “0” and initialized. Next, in step 103, one line of character string is read from the file in step 101. Next, in step 104, it is compared whether the character string in step 103 is a TVML command or not. If true, go to step 105. If false, go to step 109.
[0067]
In step 105, the comment flag is set to “0”. Next, in step 106, a block or event is created on the edit screen 401 according to the content of the command, and characteristic contents such as a command name and an argument value described in the command are displayed in the block or cell. Proceed to step 107.
[0068]
In step 109, it is compared whether the character string in step 103 is a comment line or not. If true, go to step 110. If false, go to step 107. In step 110, it is determined whether or not the character string in step 103 has a format of “// cut (number)”. If true, go to step 111. If false, go to step 114. In step 111, a new comment block is created. Next, in step 112, the comment flag is set to “1”, and the process proceeds to step 113.
[0069]
In step 114, it is compared whether the comment flag is “1”. If true, go to step 113. If false, go to step 107.
In step 113, the content of the comment is displayed in the comment block of step 111, and the process proceeds to step 107.
[0070]
In step 107, it is determined whether or not processing has been performed to the end of the file. If true, go to step 108. If false, the process returns to step 103, and the processes of steps 103 to 107 and 109 to 114 are repeated. In step 108, the file in step 101 is closed. This is the end of this process. In the process of FIG. 1, step 106 is the same as the conventional step 604 of FIG. 7, and the details of the process are the same as those already described in FIG.
[0071]
The reading source script file 300 of FIG. 3 recorded in the recording device 208 of FIG. 2 is read into the program information production unit 207 of the embodiment of the present invention in the program production device of FIG. A screen on which the file is displayed on the display 210 is shown in FIG. In FIG. 20, the same components as those in FIG. 8 are denoted by the same reference numerals.
[0072]
On the left side of the edit screen 401-2, there are comment blocks 2000-1 to 2000-4 having the same width as the studio block 402 and the movie block 403, as well as the studio block 402 and the movie block 403. In the comment blocks 2000-1 to 2000-4, the contents of the comment lines 302-1 to 302-4 and 303-1 to 303-4 of the reading source script file 300 in FIG. 3 are displayed, respectively.
[0073]
Note that the comment blocks 2000-1 to 2000-4 can be newly created, copied, cut, inserted, deleted, etc. in the same manner as other blocks. These edits are performed by “new creation”, “copy”, “cut”, “insert”, and “delete” in the pull-down menu 420 (a display example of the pull-down menu 420 is not shown). Furthermore, a character string input directly from the keyboard can be written in the comment blocks 2000-1 to 2000-4, and the operator can freely change the contents of the comments in the comment block.
[0074]
Thus, even on the edit screen 401-2, the program information cut numbers 302-1, 302-2, 302-3, 302-4, 302-5 and the cut descriptions 303-1, 303-2, 303-3, Since the comment lines 303-4 and 303-5 are displayed, the operator can easily understand the cut content of the program contents and the nature of the cut.
[0075]
Also, program information cut numbers 302-1, 302-2, 302-3, 302-4, 302-5 and explanations of cuts 303-1, 303-2, 303-3, 303-4, 303-5 Since the comment line is displayed in the comment blocks 2000-1, 2000-2, 2000-3, 2000-4 (FIG. 20) having the same width as the studio block 402, it is easier to understand the program contents.
[0076]
Next, after the reading source script file 300 of FIG. 3 recorded in the recording device 208 of FIG. 2 is read by the program information production unit 207 of the embodiment of the present invention in the program production device of FIG. Saving processing for saving the reading source script file in the saving destination script file of the storage device 208 will be described with reference to FIGS. 21 to 24 and FIGS. 21 to 24, the same components as those described above are denoted by the same reference numerals.
[0077]
FIG. 21 shows how a script storage item is selected in FIG. 20 when the reading result after the reading process according to the embodiment of the present invention is completed is stored in the storage destination script file of the recording device 208 of FIG. Shown in
[0078]
Next, the specific flow of the script file saving process is shown in FIGS.
[0079]
In step 2200 of FIGS. 22 and 23, the operator selects the script storage item 554 of FIG. Next, in step 2201, the save destination script file is opened. In step 2202, the data of one event on the editing screen is read from the memory. The event data stores the contents displayed in the block or cell.
[0080]
Next, in step 2203, it is compared whether the event of step 2202 is an event in the studio block or not. If true, go to step 2204. If false, go to step 2207. In step 2204, the cell setting data of the serif setting unit is saved. Next, in step 2205, a storage process is performed on the cell data of the operation setting unit. Next, in step 2206, storage processing is performed on the cell data of the camera / lighting setting unit, and the process proceeds to step 2215.
[0081]
In step 2207, it is compared whether the event in step 2202 is an event in the title block or not. If true, go to step 2208. If false, go to step 2209. In step 2208, the title block data is saved, and the process proceeds to step 2215.
[0082]
In step 2209, it is compared whether the event in step 2202 is an event in the movie block or not. If true, go to step 2210. If false, go to step 2211. In step 2210, the movie block data is stored, and the process proceeds to step 2215.
[0083]
In step 2211, it is compared whether the event in step 2202 is a comment block event or not. If true, go to step 2212. If false, go to step 2215. In step 2212, the character string described in the comment block is acquired. Next, in step 2213, the comment symbol “//” is added to the character string in step 2212. Next, in step 2214, the line feed and the comment in step 2213 are saved in the file in step 2201, and the process proceeds to step 2215.
[0084]
In step 2215, the cell data of the super setting unit is stored. Next, in step 2216, a storage process is performed on the cell data of the sound setting unit. Next, in step 2217, storage processing is performed for the cell data of the narration setting unit. Next, in step 2218, storage processing is performed on the cell data of the various setting setting units.
[0085]
Next, in step 2219, it is determined whether the process has been completed up to the end of the edit screen. If true, go to step 2220. If false, the process returns to step 2202, and the processing of steps 2202 to 2218 is repeated. In step 2220, the file in step 2201 is closed. This is the end of this process. Of the processes in FIG. 22, the details of the processes in steps 2204 to 2206, 2208, 2210, and 2215 to 2218 are the same as those already described with reference to FIGS.
[0086]
FIG. 24 shows a screen in which the reading result after the reading process according to the embodiment of the present invention is finished is saved in the saving destination script file of the recording device 208 of FIG. Shown in
[0087]
In the save destination script file 2400, the TVML command group 2401, comment lines 302-1 to 302-5, and 303-1 to 303-5 are saved in the same manner as the read destination script file 300 of FIG. The comment line is the result of saving the comment cut number and the cut description described in the comment block of FIG.
[0088]
As described above, since the cut number of the program information and the description of the cut are also displayed in the save destination script file 2400, it is possible to easily understand the character of the cut allocation and the cut.
[0089]
【The invention's effect】
According to the present invention, it is possible to obtain a program production method that displays comment lines and makes it easy to understand program contents. Further, according to the present invention, it is possible to obtain a program production method that displays comment lines in an easy-to-understand manner and makes program contents easier to understand. Furthermore, according to the present invention, it is possible to obtain a program production method for saving a displayed comment line in a save destination script file.
[Brief description of the drawings]
1 is a read source script file for reading the read source script file of FIG. 3 recorded in the recording device of FIG. 2 into the program information production unit of the embodiment of the present invention in the program production device of FIG. It is a flowchart figure which shows the specific flow of a reading process.
FIG. 2 is a block diagram illustrating an example of a configuration of a program production device.
3 is a view showing a reading source script file recorded in the recording apparatus of FIG. 2 on a display. FIG.
4 is a diagram showing a screen displayed on a display after the reading source script file of FIG. 3 recorded in the recording device of FIG. 2 is read into a conventional program information production unit in the program production device of FIG. 2; It is.
5 is a diagram showing an initial screen of a display when the reading source script file of FIG. 3 recorded in the recording device of FIG. 2 is read into a conventional program information production unit in the program production device of FIG. 2; .
6 is a specific example of reading source script file reading processing in which the reading source script file of FIG. 3 recorded in the recording device of FIG. 2 is read by the conventional program information production unit in the program production device of FIG. It is a flowchart figure which shows a flow.
FIG. 7 is a flowchart showing details of the process of step 604 in the process of FIG.
8 is displayed on the display after the reading process of reading the reading source script file of FIG. 3 recorded in the recording device of FIG. 2 into the conventional program information production unit in the program production device of FIG. 2; It is a figure which shows an edit screen.
9 is a flowchart showing a specific flow of a script file saving process for saving a reading result after the reading process is completed in a saving destination script file of the recording apparatus of FIG. 2; FIG.
FIG. 10 is a flowchart showing details of processing related to a dialogue setting unit in step 904 of FIG. 9;
FIG. 11 is a flowchart showing details of processing related to the operation setting unit in step 905 of FIG. 9;
12 is a flowchart showing details of processing relating to the camera / lighting setting unit in step 906 of FIG. 9; FIG.
FIG. 13 is a flowchart showing details of processing relating to the title block in step 908 of FIG. 9;
14 is a flowchart showing details of processing relating to a movie block in step 910 in FIG. 9; FIG.
FIG. 15 is a flowchart showing details of processing related to a super setting unit in step 911 of FIG. 9;
16 is a flowchart showing details of processing related to the sound setting unit in step 912 of FIG. 9;
FIG. 17 is a flowchart showing details of processing relating to the narration setting unit in step 913 in FIG. 9;
FIG. 18 is a diagram showing details of processing related to various setting setting units in step 914 in FIG. 9;
19 is a diagram showing a screen in which a reading result after the reading process is completed is saved in a saving destination script file of the recording apparatus in FIG. 2 and then the saving destination script file is displayed on a display.
20 is read after the reading source script file of FIG. 3 recorded in the recording device of FIG. 2 is read by the program information production unit of the embodiment of the present invention in the program production device of FIG. It is a figure which shows the screen which displayed the script file on the display.
21 shows how a script storage item is selected in FIG. 20 when the reading result after the reading process according to the embodiment of the present invention is completed is stored in the storage destination script file of the recording apparatus of FIG. FIG.
22 is a flowchart showing a specific flow of a script file saving process for saving a reading result after the reading process according to the embodiment of the present invention is completed in a saving destination script file of the recording apparatus of FIG. 2; is there.
23 is a flowchart showing a specific flow of a script file saving process for saving a reading result after the reading process according to the embodiment of the present invention is completed in a saving destination script file of the recording apparatus of FIG. 2; is there.
FIG. 24 shows a screen in which the reading result after the reading process according to the embodiment of the present invention is completed is saved in the saving destination script file of the recording apparatus of FIG. 2 and then the saving destination script file is displayed on the display. FIG.
[Explanation of symbols]
201: CPU, 202: Memory, 203: CG animation generation unit, 204: Speech synthesis unit, 205: Sequencer unit, 206: Event storage unit, 207: Program information production unit, 208: Recording device, 209: Moving image generation unit 210: Display, 211: Mouse, Keyboard, 212: Bus, 300: Source script file, 301: Pull-down menu, 302-1, 302-2, 302-3, 302-4, 302-5: Comment line, 303-1, 303-2, 303-3, 303-4, 303-5: comment line, 304: TVML command group, 401: edit screen, 402: studio block, 403: movie block, 404: title block, 405 : Super setting unit, 406: Sound setting unit, 407: Narration setting unit, 408: Various setting setting unit, 409: Time code, 410: Serif setting unit, 411: Operation setting unit, 412: Camera / lighting setting unit, 413 : Representative screen, 420: Pull-down menu, 421, 422: Event, 428 Program information, 550: File menu, 551: File menu list, 552: Newly created item, 553: Script reading item, 554: Script saving item, 555: Application end item, 556: Start block, 557: End block, 558 : Narration setup button, 559: Various setting setup buttons, 560: Mouse pointer, 1900: Save destination script file, 1902: TVML command group, 2000-1, 2000-2, 2000-3, 2000-4: Comment block, 2400 : Script file, 2401: TVML command group.

Claims (6)

When reading cut cut program information recorded in the recording device, the comment line described at the top of the cut cut is also read, and the read cut line and the cut program following the comment line are read. A program production method characterized by displaying information on a screen. 2. The program production method according to claim 1, wherein the comment line is displayed in a comment block having the same width as a display block of the cut-divided program information. 3. The program production method according to claim 1, wherein the content of a comment line displayed on the screen is edited. 4. The program production method according to claim 1, wherein the read comment line and the cut program information following the comment line are stored in the recording device. In programming method according to any one of claims 1 to 4, the display on the screen, the cut-split program information following the comment lines and the comment lines, be stored in the recording device A program production method characterized by In programming method according to any one of claims 1 5, wherein the comment lines described in the cut the head of the cut split is, lines of the description of row and cut numbers of the cut split A program production method characterized by:

Images