US 5,513,352 AGrant
Electronic Musical Instrument Having Secondary Storage of Files With Common Constituent Portions Identified by Entry Name
Issue Date:1996-04-30
•8 Claims
•18 Drawing Sheets
Abstract
Disclosed is an electronic appliance, for example such as an electronic musical instrument, having a secondary storage device for storing data to be recorded which can be easily divided into divisional elements under a plurality of predetermined items. With respect to information to be stored in the secondary storage device, a portion the same as the already stored information is not newly stored to thereby effectively use the storage capacity of the secondary storage device. In the electronic appliance, specifically, data to be stored as one file in the secondary storage device is divided into a plurality of constituent portions under predetermined items, file names are affixed respectively to files, and entry names are affixed respectively to the itemized constituent portions. A file to be newly stored is divided into a plurality of constituent portions under the predetermined items and a judgment is made as to whether any of the constituent portions of the new file is the same as any of the already stored constituent portions of the other file with respect to one and the same item, so that the same entry name is affixed to the same constituent portion without storing the contents of the constituent component in duplication so that the same data is used in common to a plurality of files.
Metadata
Assignee
- Yamaha Corporation
Inventor
- Akira Tozuka
Application Information
Application Number:US 3241548
Filing Date:1994-10-14
Priority Date:1991-01-17
Art Unit:237
Classifications
IPC:
G06F 1200G06F 1300
Field of Search:
36439584DIG. 1;DIG. 2600;456;404;497.04609;601
Patent Drawings (18 sheets)
Description
Background of the Invention
1. Field of the Invention
The present invention relates to an electronic appliance having a secondary storage device and particularly to an electronic appliance, for example, such as an electronic musical instrument, having a secondary storage device for storing data which can be easily divided into pieces under a plurality of predetermined items.
2. Description of the Related Art
Secondary storage devices such as magnetic tapes, floppy disks, hard disks, optical disks, and the like are widely used in electronic appliances such as computers, electronic musical instruments, and the like. Such a secondary storage device has a predetermined storage capacity. When the quantity of data storage has reached this storage capacity, the storage device becomes impossible to store data any more.
When generated or edited data are to be stored into such a secondary storage device through an input-output device of an electronic appliance or the like, all generated data are stored together with affix data such as file names for identifying the data.
In most cases, the portion to be subjected to alteration is partial in the same group of data, such as a program for controlling a certain electronic appliance, so that portions of the same data overlap each other in a plurality of data. In such cases, the constituent portions of the same data have had to be stored wastefully when different file names are affixed to the data are used.
As described above, a document or a file which is an unit of information treated in such a secondary storage device has been heretofore handled as one unit as a whole, so that portions of the document or file have been not noticed when the portions are written in or read out. Accordingly, information which is different only a portion thereof From other information has been stored as a file which is different from another file of the other information, so that the storage capacity of the secondary storage device has been consumed wastefully.
Summary of the Invention
An object of the present invention is to provide an electronic appliance having a secondary storage device in which in storing information, the same portion as that of already stored information is not newly stored to thereby make it possible to effectively use the storage capacity of the secondary storage device.
Another object of the present invention is to provide an electronic musical instrument in which the storage capacity of a secondary storage can be used effectively.
According to one aspect of the present invention, provided is a method for controlling information for a secondary storage device, in which data to be stored as one file in the secondary storage device is divided into a plurality of constituent portions under predetermined items, file names are affixed respectively to files, and entry names are affixed respectively to the itemized constituent portions. A file to be newly stored is divided into a plurality of constituent portions under the predetermined items and a judgment is made as to whether any of the constituent portions of the new file is the same as any of the already stored constituent portions of the other file with respect to one and the same item, so that the same entry name is affixed to the same constituent portion without storing the contents of the constituent component in duplication so that the same data is used common to a plurality of files.
Brief Description of the Drawings
Other features and advantages of the present invention will be apparent from the following description taken in connection with the accompanying drawings, wherein:
FIGS. 1A, 1B and 1C are schematic diagrams showing the basic structure of the present invention, in which FIG. 1A shows the case where writing is made, FIG. 1B shows the ease where reading is made, and FIG. 1C shows the ease where deleting is made;
FIGS. 2A through 2D show an embodiment of the present invention, in which FIG. 2A is a block diagram showing the structure of the system, FIG. 2B is a schematic view showing the structure of the data memory, FIG. 2C is a schematic view showing the structure of the management table, and FIG. 2D is a schematic view showing the structure of the file memory;
FIG. 3 is a flow chart showing the main routine;
FIG. 4 is a flow chart showing the disk format switch routine;
FIG. 5 is a schematic view showing the internal structure of a disk;
FIGS. 6A through 6D are schematic views showing the structure of the data management file, in which FIG. 6A shows the whole structure of the same, and FIGS. 6B through 6D show the partial structures of the same;
FIG. 7 is a schematic view showing the structure of a user file.
FIG. 8 is a schematic view showing the structure of a system RAM.
FIGS. 9A and 9B are flow charts showing a disk operating procedure, in which FIG. 9A shows the disk removal interrupt routine, and FIG. 9B shows the disk insertion interrupt routine.
FIG. 10 is a flow chart showing the play-screen switch-on event routine;
FIG. 11 is a flow chart showing the disk-write-screen switch-on event routine;
FIGS. 12A and 12B are flow charts showing the on event routine on a WD screen, in which FIG. 12A shows the F1/F2-on event routine in the case where the cursor is on a numeric character set, and FIG. 12B shows the F1/F2-on event routine in the case where the cursor is on a name character set;
FIG. 13 is a flow chart showing another form of the on event routine on a WD screen;
FIG. 14 is a flow chart showing the panel data change routine;
FIG. 15 is a flow chart showing the custom tone color write routine;
FIG. 16 is a flow chart showing the setup write routine;
FIG. 17 is a flow chart showing the external style write routine;
FIGS. 18A and 18B are flow charts showing the event routine on an RD screen, in which FIG. 18A shows the F1/F2-on event routine, and FIG. 18B shows the F3-and-F4 simultaneous touch event routine;
FIG. 19 is a flow chart showing the F3/F4-on event routine on an IRD screen;
FIG. 20 is a flow chart showing the F3-and-F4 simultaneous touch event routine on an IRDG screen;
FIGS. 21A and 21B are flow charts showing the processing routine on a DEL screen, in which FIG. 21A shows the F3-and-F4 simultaneous touch event routine and FIG. 21B shows the setup delete routine in the flow chart of FIG. 21A.
Description of the Preferred Embodiments
An electronic appliance having a secondary storage device according to a basic embodiment of the present invention will be described hereunder with reference to FIG. 1A. The electronic appliance has: a primary storage device 1 for storing new data divided into constituent portions under a plurality of items; a secondary storage device 2 for storing files each constituted by data divided into constituent portions under a plurality of items; an entry storage device 3 for storing the entry name structure of each file through entry names affixed to the respective itemized constituent portions stored in the secondary storage device 2; and a write control means 4 which operates in a manner so that when new data stored in the primary storage device 1 are to be stored as a file into the secondary storage device 2, the write control means judges whether or not a constituent portion of the new data is the same as that of any of the predetermined items already stored in the secondary storage device 2, so that when the constituent portion of the new data is the same as the constituent portion already stored in the secondary storage device 2, the write control means affixes the same entry name as that of the latter to the former without storing the former into the secondary storage device 2, while when the constituent portion of the new data is not the same as the constituent portion already stored in the secondary storage device 2, the write control means causes the secondary storage device 2 to store the former therein, affixes a new entry name to the former, and causes the entry storage device 3 to store an entry name structure therein.
Further, the electronic appliance having a secondary storage device will be described hereunder with reference to FIG. 1B. The electronic appliance has: a secondary storage device 2 for storing data divided into constituent portions under a plurality of predetermined items, the constituent portions being respectively identified by entry names; an entry storage device 3 for storing a predetermined combination of the itemized data stored in the secondary storage device 2 as a file in the form of a structure of entry names; a primary storage device 1 for newly storing the contents of a file; and a read control means 5 for reading the entry name structure of a file from the entry storage device 3 in response to a file reading instruction and then reading data corresponding to the respective entry names of the entry name structure from the secondary storage device 2 to supply the data to the primary storage device 1.
Further, the electronic appliance having a secondary storage device will be described hereunder with reference to FIG. 1C. The electronic appliance has: a secondary storage device 2 for storing data divided into constituent portions under a plurality of predetermined items, the constituent portions being respectively identified by entry names; an entry storage device 3 for storing a predetermined combination of the itemized data stored in the secondary storage device 2 as a file in the form of a structure of entry names; a management table 7 for storing the number of times by which each data constituent portion stored in the secondary storage device is repeatedly used throughout all files; and a delete control means 6 for reading the entry name structure of a file from the entry storage device 3 in response to a file deleting instruction and then not only deleting the entry name structure of the file in the entry storage device 3 while decreasing the number of times stored in the management table but deleting data from the secondary storage device 2 when the number of times reaches zero.
The repetition of storage of the same constituent portion can be avoided by: diving data stored as a file in the secondary storage device into constituent portions under predetermined items; identifying the respective constituent portions by entry names; and storing each file in the form of an entry name structure.
When data divided under items are stored so that the each data can be used through designating the entry name thereof, a combination of the divided data already stored can be identified easily by the entry name structure.
When data writing is made, the quantity of information to be stored can be reduced by: dividing data to be written under predetermined items; judging whether a divided data is the same as the already stored data with respect to the same item; and using the data in common to the same data.
Each file is constituted by a structure of entry names, so that by reading the entry name structure, reading of data used in common to a plurality of files can be preformed properly.
With respect to file deleting, a management system for storing the number of times by which a data constituent portion is repeatedly used throughout all files is used to prevent the deletion of constituent portions used in common to other files. When the number of times reaches zero the data constituent portions can be deleted because the data constituent portions become unnecessary any more.
As described above, the capacity of the secondary storage device can be used effectively for storing information. This invention is particularly effective in the case where information having a formatted pattern is partially changed and then stored.
Referring to FIG. 2A, there is shown the system structure of the electronic appliance according to an embodiment of the present invention. An electronic musical instrument taken as an example of the electronic appliance will be described hereunder.
A keyboard 11 having a plurality of keys, a CPU 22 for carrying out an arithmetic operation, an ROM 23 for storing programs and the like, an RAM 24 having work memories such as flags, registers, buffers and the like, an operation panel 14 including a display 12 such as a liquid crystal display and panel switches 13 for controlling performance, tone color and the like, a tone generator 26 for generating tone signals, and so on are connected to a bus 21. When a performance is made through the keyboard 11 after a performance environment is set through the operation panel 14, tone signals are formed by the CPU 22, the ROM 23 and the RAM 24 to thereby generate musical tones from a sound system 27 through the tone generator 26.
In this embodiment, further, a disk drive device 15 is connected to the bus 21 through a disk interface 16. The disk drive device 15 is used with a floppy disk 17 inserted therein.
When performance environment control data or the like edited by using the operation panel 14 including a display 12 and panel switches 13 are stored in the floppy disk 17, a wide variety of performances can be made.
However, having a predetermined storage capacity, the floppy disk 17 cannot store a larger quantity of information exceeding its capacity. In most cases, a performance style program or the like requires predetermined kinds of information, so that there is a limitation in novel points on the whole of data when a new performance style is recorded.
Therefore, each file is stored after divided under a plurality of items, in order to avoid the repetition of storage of the same constituent portion.
FIG. 2B schematically shows the structure of a data memory. A file to be stored is divided under a plurality of predetermined items A, B, C, D and E. A new data under one item is stored so that the new data can be identified by another entry name. The entry names may be replaced by directories. For example, under the item B, the entry names or directories B1, B2 and B3 respectively represent different data. Each of these constituent portions can be used in common to a plurality of files.
FIG. 2C schematically shows a management table for managing the situation of use of the respective constituent portions. In this management table, N(A1) represents the number of times by which the data constituent portion A1 is repeatedly used. As described above, the number of times by which each of the data constituent portions stored in the data memory is repeatedly used throughout all files is stored in the management table.
FIG. 2D shows the structure of a file memory. The first file (File 1) is constituted by data A1 under the item A, data B1 under the item B, . . . . Similarly to this, the i-th file (File i) is constituted by data A1 under the item A, data B2 under the item B, . . . . The file memory is constituted simply by entry names, so that the contents of the respective entries can be known by reading from the data memory.
When a new data to be stored, the new data is divided under items and then a judgment is made as to whether the data is the same as an old data already stored with respect to the same item. When the data is the same as the old data, information can be stored, without new storage, by using the entry name already used with respect to the constituent portion. When the data is new, the data is newly stored in the data memory to constitute a file by utilizing the entry name thereof.
The embodiment of the present invention will be described hereunder more in detail with reference to the flow charts.
FIG. 3 shows the main routine of an electronic musical instrument.
When the routine starts, initialization is made in a step S11. This initialization includes initialization in the item of memory management of the Floppy disk.
Then, in a step S12, the ordinary key processing routine (or the like) is carried out in response to the depression of a key in the keyboard 11. At the time of playing, tone signals are generated on the basis of the key processing. In an editing mode, the ordinary key processing routine is not carried out. Here, the keys in the keyboard can be used as information input means.
When a mode is selected from modes such as an editing mode, a writing mode and a reading mode through operating the panel switches 13 (or the like) of the system shown in FIG. 2A, a screen number corresponding to the selected mode is designated and, at the same time, a corresponding indication is made on the display 12. A step S13 shows these procedures.
In a step S14, the situation of the routine is separated according to the screen number GN to start a routine corresponding to the selected mode. In FIG. 3, the screen number GN=0 shows a playing mode in which a play screen process is carried out in a step S15. The screen number GN=1 shows a tone color editing mode in which a voice editing process is carried out in a step S16. Otherwise, a process in the general electronic musical instrument is carried out correspondingly to the value of the screen number GN.
In this embodiment, a process for collectively writing data in the floppy disk is carried out when the screen number GN=i (in a step 17). Further, a collectively reading process is carried out when the screen number GN=i+1 (an a step S18).
The screen number GN=i+2 shows an individually reading mode in which a process for reading individual data is carried out in a step S19. This mode is a mode for making preparation for reading, so that reading is not executed in this mode.
The screen number GN=i+3 shows an execution mode in which reading of individual data is executed in a step S20.
The screen number GN=i+4 shows a deleting mode in which a data deleting process is carried out in a step S21.
Among these processes, processes concerned with storage in the floppy disk are those indicated by the screen numbers GN=i to i+4.
Use of the floppy disk is made by the following method.
FIG. 4 shows a routine in the case where a disk format switch provided on the electronic musical instrument panel is operated. When the disk format switch is operated after a new floppy disk 17 is inserted in the disk drive device 15 in FIG. 2A, the floppy disk is formatted by using a command of MS-DOS in a step S31. After the format is generated according to MS-DOS, in the next step S32, a data management file is generated and, at the same time, initial data are written in the file.
In this embodiment, the data management file is named "MAYONE.EMI". Then, subdirectories are generated to store data under predetermined items (in a step S33). That is, the names of the respective subdirectories are registered in the route directory. The thus generated internal structure of the disk is shown in FIG. 5.
Subdirectories for data management File MAYONE.EMI, user file DESIGN.U##, instrument setup data SETUP, external style data EXTSTL, custom tone color data CUSVCE, custom accompaniment data CUSACMP, voice registration data VCEREG, panel registration data PNLREG, pad assign data PADASS. sequencer song data SONG, etc., are generated in the route directory.
The internal structures of the respective subdirectories will be considered hereunder more specifically.
FIGS. 6A to 6D show the structure of data management file MAYONE.EMI. FIG. 6A shows the total structure thereof. A data management file 39 contains a header (HD) 30, a setup management file (MNG1) 31, an external style management file (MNG2) 32, a custom tone color management file (MNG3) 33, a custom accompaniment management file (MNG4) 34, a voice registration management file (MNG5) 35, a panel registration management file (MNG6) 36, a pad assign management File (MNG7) 37, and a song management file (MNG8) 38.
The header file 30 has such contents as shown in FIG. 6B. That is, the header file 30 contains a file name, a minimum user file number NMIN, a maximum user file number NMAX, a finally written user file number LFILE, and a sample disk flag SDISK.
The seven items of management files MNG1 and MNG3 to MNG8 except the external style management file 32 respectively have such a structure as shown in FIG. 6C. The number of user files using the zero-order data stored in the disk, the number of user files using the first-order data, etc., are stored in the register 41. That is, the number of times by which a data constituent portion stored in the floppy disk is repeatedly used through files is successively stored for each item. The external style management file 32 (MNG2) has such a structure as shown in FIG. 6D. That is, the data ID of the data as well as the number of user files using the data are stored.
The external style data is set up in the factory of the maker, so that the ID is already affixed thereto. The contents of the data can be identified by this ID. Therefore, the ID is contributed to identification of the contents of the data by storing the ID.
The number of user files shown in FIGS. 6C and 6D is managed so that the number of user files is decreased whenever a file using the data is deleted.
If there is no user file using the data, the number, 0, of user files is detected and then the data itself is deleted.
FIG. 7 shows the structure of a user file. The structure of a user file to be stored will be described hereunder in the case where the file has eight items. With respect to the eight items, entries of data used are designated. In FIG. 7, the user file 59 has a setup entry (ENT1) 51, an external style entry (ENT2) 52, a custom tone color entry (ENT3) 53, a custom accompaniment entry (ENT4) 54, a voice registration entry (ENT5) 55, a panel registration entry (ENT6) 56, a pad assign entry (ENT7) 57, and a song entry (ENT8) 58. Entry numbers and data quantities are stored in the positions 51 to 58. Accordingly, both the position from where information is read and the quantity of information to be read can be found in a reading mode.
One item can have one entry data or can have a plurality of entry data. For example, a data of large data size such as an external style data or a custom accompaniment data may have a plurality of entries because it may be impossible to put the data in one entry.
A buffer memory for storing information of the same contents is provided also in the system side of the electronic musical instrument. That is, such a buffer memory structure as shown in FIG. 8 is provided in the RAM of the system. The buffer memory 72 has a first RAM area 61 for storing a setup data, a second RAM area 62 for storing an external style data, a third RAM area 63 for storing a custom tone color data, a fourth RAM area 64 for storing a custom accompaniment data, a fifth RAM area 65 for storing a voice registration data, a sixth RAM area 66 for storing a panel registration data, a seventh RAM area 67 for storing a pad assign data, and an eighth RAM area 68 for storing a song data. The buffer memory 72 further has a disk management work memory area 69, a DOS work memory area 70, and another work memory area 71.
The disk operating routine will be described hereunder in the case where a floppy disk is inserted into the disk drive 15 of the electronic musical instrument or removed from the disk drive 15.
FIG. 9A shows the interrupt routine in the case where a disk is removed. When the floppy disk is removed, in a step S81, zero is set to the flag DISK to indicate that there is no disk in the disk drive.
FIG. 9B shows the interrupt routine in the case where a disk is inserted. When the floppy disk is inserted, in a step S82, 1 set to the flag DISK to indicate that there is a disk in the disk drive.
Then, in a step S83, data of "1" are respectively written in the change flags CF1 to CF8 indicating the changes of the contents in eight RAM areas corresponding to the eight data in the floppy disk. That is, in a state where a floppy disk is inserted, data in the floppy disk are considered to be perfectly different from data in the RAM.
In a step S84, the management file MAYONE.EMI in the floppy disk is read into the body of the electronic musical instrument and stored in the buffer memory MFBUF.
In a step S85, zero is set to the register UFN indicating the user file number.
If information is read from the floppy disk and written in the RAM in the body, corresponding flags CF are changed to "0". When the contents thereof are then rewritten, the flags CF are changed to "1" again. A judgment can be made by the flags CF as to whether information in the floppy disk is the same as the information in the RAM. That is, this judgment can be made easily by discriminating the flags CF between "0" and "1" without actually comparing data.
Then, a judgment is made as to whether the same information exists when information is written in the RAM. A routine will be described hereunder with reference to FIG. 10 in the case where a play screen switch is operated in the screen number setting switch process in the step S13 of the main routine in FIG. 3.
When the play screen switch is operated to make general playing, in a step S61, "0" is set to the screen number GN. Then, in a step S62, a play screen is provided so that the voice number, the voice name, etc., for designating tone color are displayed.
When a voice editing switch is operated, "1" is set to the screen number GN and, at the same time, a voice editing screen is provided.
A routine will be described hereunder in the case where information in the floppy disk is read or written. FIG. 11 shows the routine in the case where the disk writing screen switch is operated in the same manner as this flow chart, flow charts can be formed in the case where the disk reading screen switch, the individual data reading screen switch, the deleting switch, etc., are operated. The switches for designating these screens are named "WD", "RD", "IRD", "DEL", etc.
When the WD switch is operated, in a step S71, i is set to the screen number GN. Accordingly, the screen number GN=i is selected in the distribution step S14 of the main routine shown in FIG. 3. When the RD switch, the IRD switch and the DEL switch are operated, i+1, i+2 and i+4 are correspondingly set to the screen number GN.
Because GN=i shows a mode :for carrying out a process of writing data in the disk, a judgment is made in the next step S72 as to whether the flag DISK is 1 or not. By this flag, a judgment is made as to whether there is any floppy disk in the disk drive. When there is no disk in the disk drive, the flag DISK is "0" and the situation of the routine goes to a step S76 according to the arrow of "NO". In the step S76, the massage "Insert disk." is presented on the display.
When there is an disk inserted, the situation of the routine goes to a step S73 according to the arrow of "YES". In the step S73, a judgment is made as to whether the flag SDISK is 1 or not to thereby judge whether the disk is a read-only sample disk or not. When SDISK=1, the disk is a read-only disk and the situation of the routine goes to a step S77 according to the arrow of "YES" to carry out a sample disk process.
When a disk exists but the disk is not a sample disk, the situation of the routine goes to a step S74. In the step S74, the number LFILE of the finally composed file is stored in the user file number register UFN to prepare the finally composed file having the highest possibility that the file will be written. Then, in a step S75, a writing process screen is prepared. That is, a file number and a file name are presented on the display on the basis of the value of UFN.
The step S74 may be omitted in the reading process. In the cases of the RD process, the IRD process and the DEL process, in a step S75, corresponding screens are prepared. In the IRD process For reading data individually under the respective items, a setup data is preferably prepared as the item of initial values.
FIGS. 12A and 12B show the on-event routine on the WD screen.
FIG. 12A shows an event in the case where the F1 key expressing a decrement or the F2 key expressing an increment is operated when the cursor is on a numeric character set expressing a file number. The user file number UFN is changed by one (.+-.1) correspondingly to the key operation in a range of 0 to 99 prepared as the file number (in a step S91). Then, in a step S92, a judgment is made as to whether there is any user file corresponding to the user file number UFN. When there is a file, the situation of the routine goes to a step S93. In the step S93, the file name is read and stored in the register FNAME and, at the same time, displayed.
When there is no user file, the situation of the routine goes to a step S94. In the step S94, "NEWFILE" expressing a new file is stored in the file name register FNAME and provided on the display. As a result, writing of a desired file is prepared.
FIG. 12B shows a process in the case where the F1 key expressing a decrement or the F2 key expressing an increment is operated when the cursor is on a file name. First in a step S96, the character code of the character in the position designated by the cursor is changed by one (.+-.1) in a predetermined range to change the file name. Then, in a step S97, the contents of the register FNAME are changed correspondingly to the new file name and, at the same time, the new file name is displayed.
As a result, changing of the file name is perfected.
FIG. 13 shows the other on-event routine on the WD screen. That is, FIG. 13 is a flow chart in the case where execution of writing is designated through pushing the function keys F3 and F4 simultaneously.
In a step S101, "Now Saving" expressing writing is displayed. Then, in a step S102, a process of writing respective data files under the eight items is carried out. In the writing process, a conditional branch procedure is carried out as to whether there is any rewriting of data or not. That is, it is necessary to compose a new data file and rewrite the new data when there is any rewriting of data, but the entry of the data is stored without any rewriting of the data itself when there is no rewriting of data. These preparations are made in this step S102.
Then, in a step S103, a user file having a file name stored in the register FNAME and an extension name corresponding to the file number stored in the register UFN is composed and then data such as an entry and a memory capacity stored in the user file buffer UFBUF are written in the floppy disk.
In a step S104, the data of the header in the management file buffer MFBUF is changed. Then, in a step S105, data stored in the management file buffer MFBUF are written in the management file MAYONE.EMI in the floppy disk. That is, because data such as the minimum file number, the maximum file number, the newest file, etc., can be changed by newly writing, a new management file is composed on the basis of these data.
Then, in a step S106, a judgment is made as to whether there is any error in writing. When there is no error, the situation of the routine goes to a step S107 according to the arrow of "YES". In the step S107, "Complete" expressing the completion of writing is presented on the display for about three seconds. When there is any error, the situation of the routine goes to a step S108 to carry out an error process.
As described above, writing of data with respect to the eighth items is perfected.
In the case where the number UFN of the user file to be written is already filled with the number of a user file, the contents of the user file are read into the buffer UFBUF and then the number of times by which the data of the management file MFBUF is repeatedly used is decreased by one because the user file is deleted. When the number of times reaches zero, a process of deleting the data is carried out.
The writing operation will be described hereunder more in detail.
FIG. 14 shows the routine in the case where data changing is made through the panel before the writing operation is carried out. The case where a setup data is changed will be described as an example.
When the panel data is to be changed while the setup data is edited, in a step S41, the panel data is changed to change data of a corresponding RAM area. Then in a step S42, the flag CF1 indicating data changing is changed to "1". The fact that the data has been changed is indicated by this flag "1".
FIG. 15 shows the routine in the case where custom tone color is written.
In a step S51, when a tone color number is designated, the tone color number is stored in the tone color number register VN. Then, in a step S52, the tone color in the panel is written as the VN-th tone color in the RAM 3. Then, in a step S53, "1" is stored the flag CF3 indicating the change of custom tone color data.
With respect to another item, "1" is stored in a corresponding flag CF in the same manner as described above to indicate the fact that data changing occurs, when data changing occurs in the period of data editing.
FIG. 16 shows the setup write process routine. First in a step S111, a judgment is made as to whether the flag CF1 is 1 or not. That is, the fact that there is any data change is indicated by the value "1" of the flag CF1 and the fact that there is no data change is indicated by the value "0" of the flag CF1. Because the data to be written already exists in the floppy disk when there is no change, writing of data is not made.
When there is no change, the situation of the routine goes to a step S112 according to the arrow of "NO". In the step S112, the file number is read from the user file buffer UFBUF1 and stored in the register DFN. Then, in a step S113, the number of files stored in the DFN-th order in the management file buffer MFBUF1 is increased by one to record the fact that the number of files using the data is increased by one.
In the case where the number of files is decreased by one by overwriting, the number of corresponding files in the management file buffer is decreased by one. When for example, the setup data in the user file U01 is changed from 3 to 4, the number of times of use of the management file for the setup data 3 is decreased by one and, at the same time, the number of times of use of the management file for the setup data 4 is increased by one.
When there is any change and the flag CF1 is "1", the situation of the routine goes to a step S114 according to the arrow of "YES". First any empty number is searched for by using the management file buffer MFBUF1. That is, positions in which the number of files used is zero are searched in ascending order or in descending order. The number obtained by searching is stored in the register DFN.
Then, in a step S115, a new setup data is written as SETUP.DFN in the setup data directory. In a step S116, a new file data entry is registered in the user file buffer UFBUF1. In a step S117, "1" is written in the number of files stored in the DFN-th order in the management file buffer MFBUF. That is, it indicates the fact that the number of files using this data is 1.
When a file using the same data is written in an after-process, the number of files in the DFN-th order is increased by one. Not only the entry number DFN but the file capacity are preferably registered in the user file so that the reading end position can be found at the time of reading.
FIG. 17 shows the external style write process routine. The external style data is generated in the factory of the maker and has a predetermined data number (DATAID). Accordingly, the difference between data can be found by using the data ID. When the routine starts in a step S121, a judgment is made as to whether the flag CF2 is 1 or not. When CF2 is 1, the fact that there is any change of data is indicated. When CF2 is 0, the fact that there is no change is indicated.
When there is no change, the situation goes to a step S122. In the step S122, the file number is read from the user file buffer UFBUF2 and stored in the register DFN. Then, in a step S123, the number of files in the DFN-th order in the management file buffer MFBUF2 is increased by one. That is, the fact that the number of files using this data is increased by one is stored.
When there is any change, the situation of the routine goes to a step S125. In the step S125, a file having the same ID as that to be written is searched for From the management file buffer MFBUF, so that a corresponding file number is stored in the register DFN. Then, in a step S126, a judgment is made as to whether there is any matched file in the floppy disk. When there is any matched file, the situation of the routine goes to the step S123. When there is no matched data, the situation of the routine goes to a step S127. In the step S127, an empty file number is searched for by using the management file buffer MFBUF1, so that the number is stored in the register DFN. Thereafter, the same procedure as the setup writing process routine is carried out.
FIGS. 18A and 18B show the respective event routine on the RD screen in a collective reading mode.
FIG. 18A shows time processing routine in the case where the function key F1 expressing a decrement or the function key F2 expressing an increment is operated on the reading screen. In a step S131, the maximum or minimum number file (that is, an adjacent file) in files having a smaller or larger number than the current file number is searched for in a range of from the minimum file number NMIN to the maximum file number NMAX in response to the on event of F1 or F2 and stored in the buffer BUF. When there is no matched file, a numerical character not actually used is stored in the buffer BUF.
Then, in a step S132, a judgment is made as to whether there is any file designated by the file number. When there is no file, the routine is terminated here. When there is any file, the situation of the routine goes to a step S133. In the step S133, the number of the register BUF is stored as the current file number in the register UFN. Then, in a step S134, the number of the register UFN and a corresponding file name are displayed. As described above, preparation for reading data is made.
FIG. 18B shows the processing routine in the case where the function keys F3 and F4 are pushed simultaneously on the reading (RD) screen to instruct execution of reading. First in a step S141, "Now Loading" expressing reading is displayed. Then, in a step S142, the UFN-th order user file corresponding to the user file number UFN is read and stored in the user file buffer UFBUF. Here, entries for constituting the file are written in the buffer. Then, in a step S143, data are read into the memory areas RAM1 to RAM8 by using the entries ENT1 to ENT8 in the register UFBUF. Then, in a step S144 a judgment is made as to whether there is any error in reading. When there is no error in reading, the situation of the routine goes to a step S145 according to the arrow of "YES". In the step S145, data of "0" are respectively written in the flags CF1 to CF8. That is, in this state, data written in the RAM are the same as data in the floppy disk. Then, the situation of the routine goes to a step S146. In the step S146, "Complete" expressing the completion of reading is provided on the display for three seconds. The reading process is thus terminated.
When there is any error in reading the situation of the routine goes to a step S147 according to the arrow of "NO" from the step S144. In the step S147 an error process is carried out.
The event routine on the IRD screen for reading data individually under each item will be described hereunder.
When the function key F1 expressing a decrement or the Function key F2 expressing an increment is operated on the screen, an adjacent file is searched for and displayed in the same manner as in the process on the RD screen shown in FIG. 18A.
When the next page switch is pushed on the IRD screen, the screen is changed to the IRDG screen. When the next page switch is pushed on the IRDG screen, the screen is returned to the IRD screen. Further, selection of a data item is made on the IRD screen. The data item is changed by operating the function key F3 (-) or F4 (+).
The process in the case where one of these function keys F3 and F4 is operated is shown in FIG. 19. It is now assumed that the first data item given to the IRD screen is SETUP(i).
When one of the Function keys F3 and F4 is operated, the data number x is changed in a range of 1 to 8 (in a step S151). Then, a data name corresponding to the value of x is displayed on the right side of the screen.
The process on the IRDG screen for executing reading of individual data will be described hereunder. On the IRDG screen, the function keys F1 and F2 have no Function. That is, reading of data with respect to a single item is executed by the F3-and-F4 simultaneous pushing event.
FIG. 20 shows the event routine in the case where the function keys F3 and F4 on the IRDG screen are simultaneously pushed. When the routine starts, in a step S161, "Now Loading" expressing reading is displayed. Then, in a step S162, the UFN-h user file corresponding to the user file number UFN is read and stored in the user file buffer UFBUFX.
Then, in a step S163, data are read from a directory corresponding to the entry ENTx in the user file buffer UFBUFX and stored in the memory area RAMx. In a step S164, data in the entry ENTx is copied to ENTx in UFBUFX. Then, in a step S165, a judgment is made as to whether there is any error in reading. When there is no error, the situation of the routine goes to a step S166. In the step S166, "0" is stored in the flag CFx to indicate the fact that data in the body of the instrument are the same as data in the floppy disk. Then, in a step S167, "Complete" expressing the completion of reading is displayed for about three seconds. When there is any error, the situation of the routine goes to a step S168 to carry out an error process.
The process on the deleting (DEL) screen will be described hereunder. The function keys F1 and F2 on the DEL screen respectively instruct the decrease of the data number and the increase thereof in the same manner as the function keys F1 and F2 on the RD screen.
FIG. 21A shows the routine for carrying out the deletion of a file through pushing the function keys F3 and F4 simultaneously on the DEL screen. When the routine starts in a step S181, the UFN-th user file corresponding to the user file number UFN is read and stored in the buffer UFBUFX. Then, in a step S182, data under each item are subjected to a deletion process. The deletion process is a process of changing the data management file by a deleting procedure without directly deleting the data itself. When there is no file using the data, a deleting procedure is carried out for the data.
The setup data deleting routine is shown in FIG. 21B as an example. In a step S171, the number of files in the management file MNG1 with respect to the data given by the entry ENT1 in the buffer UFBUFX is decreased by one. Then, in a step S172, a judgment is made as to whether the number of files using the data reaches zero. When the number of files is not zero, the routine is terminated here. When the number of files reaches zero, the situation of the routine goes to a step S173 according to the arrow of "YES". In the step S173, the setup file in the setup directory corresponding to the entry ENT1 is deleted. That is, only disused data is deleted. The same procedure is applied to files with respect to other items.
Referring to FIG. 21A, in a step S183, the UFN-th user file corresponding to the user file number UFN is deleted. In a step S184, data in the header of the management file buffer MFBUF are changed. For example, the maximum value (NMAX), the minimum value (NMIN), etc., may be changed.
Then, in a step S185, the contents of the management file MFBUF are written in the management file MAYONE.EMI in the floppy disk. Because the deleting procedure is completed here, in the next step S186, "Complete" expressing the completion of deletion is displayed for about three seconds.
As described above, the deleting procedure is carried out by changing the management file and the data file if necessary.
Although the present invention has been described as to the embodiments thereof, the present invention is not limited to these embodiments. For example, the management table need not be used if a storage disk capable of being subjected to writing by only once is used for storing data. Accordingly, in this case, the deleting procedure is not required. Even in this case, writing of data can be made while using the capacity of the disk effectively. The entries in the data memory may be given easily by a data sequence in the memory or entry names may be given individually. Although above description has been made upon the case where all files have one information set with respect to the same item, the present invention can be applied to the case where files are formed by arbitrary items among a large number of items.
Claims
What is claimed is:
1. An electronic musical instrument comprising: a primary storage device for storing a data file for the electronic musical instrument, the data file being divided into constituent data portions representing various functions or types of control data used by the electronic musical instrument; a secondary storage device for storing a plurality of data files each containing a group of data used or produced by the electronic musical instrument, the secondary storage device including: a file data storage section for storing the constituent data portions that are formed by dividing the group of data in each of the plurality of data files, each of the constituent data portions being identified by entry names, a file entry storage section for storing, for each data file, a plurality of entry names identifying the constituent data portions constituting the group of data that forms each data file of the plurality of data files, and an entry management storage section for storing, for each entry name, a number of times that each constituent data portion is used by the plurality of data files, the number of times being used to determine if particular constituent data portions should be written or stored in the file data storage section or deleted when none of the plurality of data files uses the particular constituent data portions, such that only constituent data portions used by at least one of the plurality of data files are stored in the file data storage section of the secondary storage device to thereby minimize the amount of storage space used in the secondary storage device; and a write control means for making a determination, upon storage of the group of data forming the data file in the secondary storage device, whether any of the constituent data portions are the same as any of the already stored constituent data portions in the secondary storage device, so that when a particular constituent data portion of the constituent data portions is the same as another already stored constituent data portion in the secondary storage device, the write control means uses the same entry name as that of the another already stored constituent data portion for the particular constituent data portion of the data file without causing the secondary storage device to store the particular constituent data portion of the data file, while when the particular constituent data portion of the data file is different from any of the already stored constituent data portions in the secondary storage device, the write control means causes the secondary storage device to store the particular constituent data portion of the data file, and at the same time the write control means uses a new entry name that is different from any of the other entry names of the already stored constituent data portions for the particular constituent data portion of the data file and causes the entry storage section to store an entry name structure with respect to each new entry name.
2. An electronic musical instrument comprising: a secondary storage device for storing a plurality of files each containing a group of data used or produced by the electronic musical instrument, the secondary storage device including: a file data storage section for storing constituent data portions that are formed by dividing the group of data in each of the plurality of files, the constituent data portions representing various functions or types of control data that are used by the electronic musical instrument, and each of the constituent data portions being identified by entry names, a file entry storage section for storing, for each file, a plurality of entry names identifying the constituent data portions constituting the group of data that forms each file of the plurality of files, and an entry management storage section for storing, for each entry name, a number of times that each constituent data portion is used by the plurality of files, the number of times being used to determine if particular constituent data portions should be written or stored in the file data storage section or deleted when none of the plurality of files uses the particular constituent data portions, such that only constituent data portions included in at least one of the plurality of files are stored in the file data storage section to thereby minimize the amount of storage space used in the secondary storage device; and file reading instruction generating means for generating a reading instruction to read a designated file; and a read control means for reading the entry names of the designated file from the entry storage section in response to the reading instruction, and for reading the constituent data portions corresponding to the respective entry names from the secondary storage device.
3. An electronic musical instrument comprising: a secondary storage device for storing a plurality of files each containing a group of data used or produced by the electronic musical instrument, the secondary storage device including: a file data storage section for storing constituent data portions that are formed by dividing the group of data in each of the plurality of files, the constituent data portions representing various functions or types of control data that are used by the electronic musical instrument, and each of the constituent data portions being identified by entry names, a file entry storage section for storing, for each file, a plurality of entry names identifying the constituent data portions constituting the group of data that forms each file of the plurality of files, and an entry management storage section for storing, for each entry name, a number of times that each constituent data portion is used by the plurality of files, the number of times being used to determine if particular constituent data portions should be written or stored in the file data storage section or deleted when none of the plurality of files uses the particular constituent data portions, such that only constituent data portions included in at least one of the plurality of files are stored in the file data storage section to thereby minimize the amount of storage space used in the secondary storage device; and a delete control means which operates, upon receipt of an instruction to delete a given file, to read the entry names of the given file from the entry storage section of the secondary storage device to decrease the corresponding number of times stored in the entry management section, and to delete a constituent data portion from the secondary storage device when the number of times for that constituent data portion becomes zero.
4. A secondary storage device for storing a plurality of files each containing a group of data used or produced by an electronic musical instrument, the secondary storage device comprising: a file data storage section for storing constituent data portions that are formed by dividing the group of data in each of the plurality of files, the constituent data portions representing various functions or types of control data that are used by the electronic musical instrument, and each of the constituent data portions being identified by entry names; a file entry storage section for storing, for each file, a plurality of entry names identifying the constituent data portions constituting the group of data that forms each file of the plurality of files; and an entry management storage section for storing, for each entry name, a number of times that each constituent data portion is used by the plurality of files, the number of times being used to determine if particular constituent data portions should be written or stored in the file data storage section or deleted when none of the plurality of files uses the particular constituent data portions, such that only constituent data portions included in at least one of the plurality of files are stored in the file data storage section to thereby minimize the amount of storage space used in the secondary storage device.
5. A secondary storage device according to claim 4, wherein the group of data in the files is automatic performance data, each group of data in the file being divided into the constituent data portions representing various categories of performance data, and in which a different one of a plurality of entry names is used for each of the constituent data portions, and wherein the entry management section of the secondary storage device includes a management table for storing the number of times each of the plurality of entry names is repeatedly used throughout all of the plurality of files in which the performance data is stored.
6. A secondary storage device according to claim 4, wherein the secondary device further includes a floppy disk for storing the data files, the constituent data portions, and the entry names.
7. A secondary storage device according to claim 4, wherein the entry names also designate directories and subdirectories containing the constituent data portions.
8. A method of storing information in a secondary storage device for an electronic musical instrument, the method comprising the steps of: dividing the information into a plurality of constituent data portions, the constituent data portions representing various functions or types of control data that are used by the electronic musical instrument; identifying each constituent data portion with an entry name; storing the information in the secondary storage device as a file among a plurality of files, the file being formed as a list of entry names identifying the corresponding constituent data portions that make up the information; storing a number of times each constituent data portion is used in the plurality of files that are stored in the secondary storage device; and deleting all constituent data portions from the secondary storage device that are not contained in any of the plurality of files stored in the secondary storage device.
Patent Citations (11)
| Patent | Date | Inventor | Cited By |
|---|---|---|---|
| US4730252 | 1988-03-01 | Bradshaw | |
| US4788672 | 1988-11-01 | Toyooka et al. | |
| US4807182 | 1989-02-01 | Queen | |
| US4912637 | 1990-03-01 | Sheedy | |
| US4960030 | 1990-10-01 | Fujimori | |
| US5056021 | 1991-10-01 | Ausborn | |
| US5220119 | 1993-06-01 | Shimada | |
| US5270476 | 1993-12-01 | Rokkaku et al. | |
| US5280438 | 1994-01-01 | Kanemaru | |
| US5369216 | 1994-11-01 | Miyamoto | |
| JPX60-07671 | 1985-01-01 |
Non-Patent Literature (1)
- Theodor Nelson, "The Tyranny of the File", Dec. 15, 1986 pp. 83-85.