JP4305218B2 - Acoustic signal processing system - Google Patents

Description

  The present invention includes an editing device that edits a configuration of acoustic signal processing by designating a combination of a plurality of components, and an acoustic signal processing device that processes an acoustic signal according to the signal processing configuration edited by the editing device. The present invention relates to an acoustic signal processing system.

  Conventionally, the signal processing unit is configured using a processor that can operate according to a program, and an external PC (personal computer) or other computer is caused to execute application software to function as an editing device, which is used for editing. 2. Description of the Related Art There is known an acoustic signal processing apparatus that can process an acoustic signal based on a signal processing configuration. Such an acoustic signal processing apparatus is referred to as a mixer engine in the present application. The mixer engine stores therein the signal processing configuration edited by the PC, and can independently process the acoustic signal based on the stored signal processing configuration.

In addition, editing of the above signal processing configuration on the editing apparatus graphically displays the signal processing configuration visually by displaying on the display the components that are components of signal processing during editing and the connection state between the input and output. An editing operation is performed in an easy state. The user can edit the signal processing configuration by arranging desired processing components and setting the connection between the arranged components.
Such a mixer engine and application software are described in Non-Patent Document 1, for example.
“DIGITAL MIXING ENGINE DME32 Instruction Manual”, Yamaha Corporation, 2001, p. 23-66

When operating such an acoustic signal processing apparatus, it is common to store data for performing necessary control for each component on the editing apparatus side and the acoustic signal processing apparatus side. It is preferable that this data can be upgraded as necessary, and that addition and change of components can be performed.
However, in the conventional mixer engine, component data is stored as part of the firmware. Therefore, in order to add or update a component, it is necessary to update the firmware, which is cumbersome and time consuming. It was hanging.

On the other hand, the present applicant proposes a system in which IDs are individually assigned to the data of each component, and data for controlling the components can be individually added or updated for each component. (Japanese Patent Application No. 2003-389649, unpublished).
When such a system is adopted, components can be added and updated relatively freely. Therefore, a business that sells newly developed components can be considered separately from the basic system.

However, in such a business, the data to be sold is data, so the data sold to customers is illegally copied and installed on devices outside the contract, or illegally copied data is distributed as pirated copies. There is a risk of getting lost.
Therefore, there is a demand for providing a protection mechanism that prevents an illegally obtained component from being used for acoustic signal processing. However, since such a component addition / update method itself is not yet known, there is a problem that an appropriate protection mechanism suitable for such a method is not known.

  The present invention solves such a problem, edits the configuration of signal processing in the acoustic signal processing device by the editing device, and causes the acoustic signal processing device to perform signal processing according to the editing content. It is an object of the present invention to effectively prevent unauthorized use of data related to signal processing components while maintaining the convenience and operability of the system.

In order to achieve the above object, an acoustic signal processing system according to the present invention has an input terminal and an output terminal for the acoustic signal processing contents to be executed by an acoustic signal processing apparatus having a programmable acoustic signal processing unit. Defined based on a plurality of signal processing components and a connection connecting the output terminal and the input terminal of the signal processing component, and configuration data specifying the configuration of the acoustic signal processing composed of the signal processing component and the connection, an editing device for editing according to the instructions received in the graphic display the display screen, an audio signal processing system comprising a sound signal processing apparatus having a signal processing unit for processing audio signals in accordance with configuration data edited by the editing apparatus, Each signal processing component has its own identification information Ri, and type is distinguishably structure of the signal processing components on the basis of the identification information, the acoustic signal processing device or the editing device, in the audio signal processing device, signal processing components of a particular type of the signal processing components When the prohibition means for prohibiting the execution of the acoustic signal processing based on the configuration data that defines the acoustic signal processing using the and the release key for canceling the prohibition by the prohibition means are stored in the acoustic signal processing device Canceling means for canceling the prohibition is provided, storage means for storing the release key is provided in the acoustic signal processing device, and in the editing device, whether or not the release key is stored in the acoustic signal processing device. not, configuration data that defines the acoustic signal processing using signal processing components of the specific type In which it was to allow editing.

In such an acoustic signal processing system, the editing device is provided with transfer means for transferring the edited configuration data to the acoustic signal processing device, and the prohibiting means uses the specific type of signal processing component for acoustic signal processing. It is preferable that execution of the acoustic signal processing is prohibited by prohibiting the configuration data defining the above from being transferred from the editing device to the acoustic signal processing device by the transfer means.
Alternatively, the editing device is provided with conversion means for converting the edited configuration data into a format that can be processed by the acoustic signal processing device, and the prohibiting means uses the specific type of signal processing component for acoustic signal processing. configuration data that defines, may be prohibited to execute the audio signal processing by prohibiting be converted into a format that can be processed in the audio signal processing device by said converting means.

Alternatively, the editing device is provided with transfer means for transferring the edited configuration data to the acoustic signal processing device, and the acoustic signal processing device receives the configuration data transferred by the editing device , and based on the received configuration data Te provided a program generation means for generating a program for executing a sound signal processing to the signal processing unit, the prohibiting means, in the audio signal processing device, configuration data received from the editing device, of the specific type If there was obtained by defining the sound signal processing using signal processing components, by prohibiting the program for executing the more the acoustic signal processing in the program generating means is generating the sound signal processing the execution may be prohibited.

Alternatively, the editing device is provided with transfer means for transferring the edited configuration data to the acoustic signal processing device, and the acoustic signal processing device receives the configuration data transferred by the editing device, and receives the received configuration data . the program generation means for generating a program for executing a sound signal processing to the signal processing unit based provided, said prohibiting means, the configuration data thus received was the source of the program the program generation means is generated, If that contained the signal processing components of the specific type, it may be prohibited to execute the audio signal processing by prohibiting execution of the program that generated by the signal processing unit.
Further, in each of the above acoustic signal processing systems, the release key includes identification information for specifying the acoustic signal processing device and identification information for specifying the signal processing component, and the release unit includes: Only when the release key includes identification information unique to the acoustic signal processing apparatus storing the release key and identification information unique to the signal processing component of the specific type included in the configuration data . it may be adapted to release the prohibition by the prohibiting means.

  According to the acoustic signal processing system of the present invention as described above, the acoustic signal processing is performed by editing the configuration of the signal processing in the acoustic signal processing device by the editing device and causing the acoustic signal processing device to perform signal processing according to the edited content. In the system, it is possible to effectively prevent unauthorized use of data related to signal processing components while maintaining the convenience and operability of the system.

Hereinafter, the best mode for carrying out the present invention will be specifically described with reference to the drawings.
[Description of Basic Configuration of Mixer System in Embodiment: FIGS. 1 and 2]
First, the configuration of a mixer system, which is an embodiment of an acoustic signal processing system of the present invention, constituted by a PC that is an editing apparatus and a mixer engine that is an acoustic signal processing apparatus will be described with reference to FIG. FIG. 1 is a block diagram showing the configuration of the mixer system.
As shown in FIG. 1, this mixer system includes a mixer engine 10 and a PC 30. The PC 30 is a known PC having a CPU, a ROM, a RAM, and the like as hardware and a display as a display unit, and a PC on which an operating system (OS) such as Windows XP (registered trademark) operates can be used. An editing apparatus that edits a signal processing configuration in the mixer engine 10 by executing a required editing program as an application program on the OS, transfers the editing result to the mixer engine 10, and operates according to the edited signal processing configuration Can function as. The operations and functions of the PC 30 described below are realized by executing this editing program unless otherwise specified.

  On the other hand, the mixer engine 10 includes a CPU 11, a flash memory 12, a RAM 13, a display 14, a controller 15, a PC input / output unit (I / O) 16, a MIDI (Musical Instruments Digital Interface: registered trademark) I / O 17, and other I. / O18, waveform I / O19, signal processor (DSP) 20, and cascade I / O21, which are connected by a system bus 22. A function for generating a microprogram for controlling the DSP 20 according to the signal processing configuration received from the PC 30, operating the DSP 20 according to the microprogram, performing various signal processing on the input acoustic signal, and outputting it. Have.

The CPU 11 is a control unit that performs overall control of the operation of the mixer engine 10, and controls communication in each I / O 16 to 19 and display on the display 14 by executing a predetermined program stored in the flash memory 12. Or by detecting the operation of the operator 15 and changing the parameter value according to the operation, or generating a microprogram for operating the DSP 20 from the signal processing configuration information received from the PC 30 and setting it in the DSP 20. Process.
The flash memory 12 is a rewritable nonvolatile storage unit that stores a control program executed by the CPU 11, preset component data described later, a release key, and the like.

The RAM 13 is a storage means for storing various data such as configuration data and current data, which will be described later, obtained by converting the signal processing configuration information received from the PC 30 into a required format, and used as a work memory for the CPU 11. is there. The configuration data storage area of the RAM 13 is backed up so that the mixer engine 10 can be used alone.
The display device 14 is a display means constituted by a liquid crystal display (LCD) or the like. Then, a screen showing the current state of the mixer engine 10, a screen for referring to, changing, saving, etc. of scenes that are setting data included in the configuration data are displayed.
The operation element 15 is composed of a key, a switch, a rotary encoder, and the like, and is an operation element for the user to directly operate the mixer engine 10 to edit a scene.

The PCI / O 16 is an interface for connecting and communicating with the PC 30. For example, a USB (Universal Serial Bus) method, an RS232C method, an IEEE (Institute of Electrical and Electronic Engineers) 1394 method, an Ethernet (registered trademark) method, or the like. Communication by the interface can be performed.
The MIDII / O 17 is an interface for exchanging data according to the MIDI standard, and is used for communicating with, for example, an electronic musical instrument compatible with MIDI or a computer equipped with an application program for outputting MIDI data.

  The waveform I / O 19 is an interface for receiving an input of an acoustic signal to be processed by the DSP 20 and outputting the processed acoustic signal. This waveform I / O 19 includes an A / D conversion board capable of four-channel analog input by one board, a D / A conversion board capable of four-channel analog output by one board, and eight channels by one board. A plurality of digital input / output boards capable of digital input / output can be mounted in an appropriate combination, and signals are actually input / output through these boards.

The other I / O 18 is an interface for connecting and inputting devices other than those described above. For example, an interface for connecting an external display, a mouse, a keyboard for inputting characters, an operation panel, and the like is prepared.
The DSP 20 is a module that performs signal processing on the acoustic signal input from the waveform I / O 19 according to the contents of the current scene that determines the set microprogram and its processing parameters. The DSP 20 may be configured by a single processor, or may be configured by connecting a plurality of processors.

  The cascade I / O 21 is an interface for exchanging acoustic signals, data and commands from the PC 30, etc. with other mixer engines when using a plurality of mixer engines 10 connected in cascade. When a plurality of mixer engines 10 are used in cascade connection, a plurality of mixer engines 10 can be operated cooperatively to perform a series of acoustic signal processing. Then, the PC 30 edits such acoustic signal processing, transfers the editing result to other mixer engines 10 via the mixer engine 10 directly connected to the PC 30, and edits each mixer engine 10. Can be operated according to.

Next, a signal processing configuration editing method in the PC 30 will be described. FIG. 2 is a diagram illustrating an example of an editing screen for a signal processing configuration displayed on the display of the PC 30.
When the user causes the PC 30 to execute the above editing program, the PC 30 displays a CAD (Computer Aided Design) screen 40 as shown in FIG. 2 as a graphic display screen on the display, and accepts an editing instruction from the user. In this screen, the signal processing component being edited is a signal processing component (A : hereinafter simply referred to as “component” ) indicating the signal processing function to be executed by the DSP 20 such as 4bandPEQ, AutoMixer, etc. And a connection line (D) connecting the output terminal (B) of the component and the input terminal (C). The terminals displayed on the left side of the component are input terminals, and the terminals shown on the right side are output terminals. The component indicating the input to the mixer engine 10 has only the output terminal, the component indicating the output from the mixer engine 10 has only the input terminal, and all other components have both the input terminal and the output terminal. Have.

On this screen, the user selects a component to be added to the signal processing configuration from the component list displayed by the operation of the “Component” menu, arranges it on the screen, and selects any output terminal of the arranged multiple components. The signal processing configuration can be edited by specifying the connection between the input terminal and any input terminal. The edited result is saved as a configuration by instructing execution of “Save” in the “File” menu, and a part of configuration data by instructing execution of “Compile” in the “File” menu. Can be transferred to and stored in the mixer engine 10 after being converted into a data format for the mixer engine.
Note that the PC 30 calculates the amount of resources necessary for signal processing according to the signal processing configuration on the screen during editing, and when this exceeds the resources of the DSP 20 included in the mixer engine 10, that is the case. Since this process cannot be performed, the user is notified.

Further, for each component included in the signal processing configuration, a storage for storing the operation parameters (for example, the level of each input in the case of a mixer) when the component is newly arranged and compiled in the signal processing configuration. An area is prepared in the current scene storing the current data, and a predetermined initial value is given as an operation parameter thereof.
Then, by operating the parameter control panel provided for each component by the user, the operation parameters stored in the parameter storage area can be edited. A plurality of parameters stored in the current scene as a result of editing here are stored in the scene memory in the configuration as scenes that are setting data relating to the configuration, and the mixer engine 10 performs signal processing according to the configuration. It can be arbitrarily called to the current scene when it is performed.

  Further, the user can set either the non-online mode or the online mode as the operation mode of the mixer engine 10 and the PC 30. In the non-online mode, the mixer engine 10 and the PC 30 operate independently of each other, and in the online mode, the operation is performed while synchronizing the operation parameters of the current memory with each other. It is possible to shift to the online mode only when the signal processing configuration of the mixer engine 10 and the signal processing configuration of the PC 30 match. In the online mode, control is performed so that the data of the current scene is the same between the mixer engine 10 and the PC 30. (Synchronized).

Further, when shifting to the online mode, the user can select which one of the current scene on the mixer engine 10 side and the current scene on the PC 30 side is used as the synchronized current scene, and further, the scene memory The stored contents can be instructed to be synchronized.
After the transition to the online mode, the operation performed on the PC 30 side is immediately reflected in the operation of the mixer engine 10, and conversely, the operation performed on the operation element 15 of the mixer engine 10 is immediately reflected in the operation of the PC 30. The current scene is controlled to be the same. It is also possible to automatically shift to the online mode when the above-mentioned “compilation” is executed, and to automatically shift to the non-online mode when the signal processing configuration is changed on the PC 30 side.

[Description of Data Structure Used in Mixer System of Embodiment: FIGS. 3 to 5]
Next, the structure of data related to the present invention used in the above mixer system will be described.
First, FIG. 3 shows the configuration of data used on the PC 30 side.
As shown in this figure, when the above editing program is executed on the OS of the PC 30, the PC 30 stores preset component data and configuration data in a memory space defined by the editing program.

  Of these, the preset component data is a set of component data that can be used when editing signal processing and may be customized by the user, but is basically supplied by the manufacturer. The data includes preset component set version data, which is version information for performing version management for the entire data set, and PC preset component data prepared for each type of a plurality of components constituting the data set. .

  Preset component data for each PC is information indicating the nature and function of the component, including a preset component header for identifying the component, component input and output, configuration information indicating the configuration of data and operation parameters handled by the component, A parameter processing routine for performing processing for changing the value of the individual operation parameter of each component in each scene of the current or scene memory according to the user's numerical input operation, and for displaying the operation parameter of each component in the scene Display / edit processing routines for conversion to text data and characteristic graphs.

The preset component header includes preset component ID that is identification information indicating the type of the preset component and information on the preset component version that indicates the version, and the preset component can be specified by these.
Further, in this mixer system, some preset components are protected, and execution of acoustic signal processing including the preset components is permitted only when the user has a predetermined release key. Therefore, in the preset component header, information on the presence / absence of protection indicating whether or not to protect the preset component is also described.

In addition to the input / output configuration information indicating the input / output configuration of the component, the data configuration information indicating the configuration of the data and parameters handled by the component, the component name and the component itself are displayed on the editing screen. PC display data indicating the design of the control panel displayed on the display for editing the appearance and the operation parameters of the component and the layout of the knobs and characteristic graphs on the control panel.
The preset component ID is related to the data configuration information, and the preset components having the same preset component ID have mutual data and parameter compatibility. Therefore, between components having the same preset component ID, copying between different configurations described later is possible.
Here, among the PC preset component data, the PC display data necessary for editing on the graphic display editing screen in the configuration information and the characteristics are displayed in a graph on the control panel during the display / edit processing routine. The routine for this is data that is not necessary for the operation on the mixer engine 10 side, and is stored only on the PC 30 side.

In this mixer system, a plurality of variations can be defined for each preset component. This variation is a component that has the same basic processing functions and a different number of processing repetitions. For example, a component with a different number of input and output terminals for a mixer, and a per-channel for an equalizer. Components with different numbers of filters (bands). Table 1 below shows still another specific example.

Since these components have the same basic processing functions, the parameters used for the processing are similar, and they are all associated with each other as variations rather than as separate preset components. Since management is more efficient, such a management method is adopted. That is, the variations have data compatibility and, of course, have the same preset component ID.
Therefore, for each variation, the PC display data, data configuration information, and input / output configuration information can be configured in a scalable manner, and the PC display data, data configuration information, and input / output configuration information are stored in one preset. Common to multiple component variations. The input / output configuration information also includes information indicating the correspondence between terminals and parameters included in each variation within the same preset component.

On the other hand, the configuration data is data indicating the signal processing configuration edited by the user. When the user selects to save the editing result, the signal processing configuration and the set value at that time are stored as one PC configuration data. Is done. Further, the user can instruct to store a plurality of PC configuration data as shown in FIG. 3 in the hard disk as one file, or conversely, to instruct to read from the hard disk to the RAM. In response to the instruction, a plurality of PC configuration data is written as one file on the hard disk or read out to the RAM.
Further, the user can select one of a plurality of PC configuration data on the RAM of the PC 30 as configuration data to be edited in the editing program. The PC 30 (editing program process) prepares for editing the PC configuration data (PC CAD described below) regardless of whether the selected PC configuration data includes a component to be protected. Data, each scene, and the corresponding current scene parameters).

Each PC configuration data includes a configuration header for identifying configuration data, PC CAD data indicating the contents of the edited signal processing configuration, and a scene that is the setting data described above.
Among these, the configuration header indicates the configuration ID that is uniquely assigned when configuration data is newly saved, the configuration version that is changed when the configuration data is modified, and the version of the editing program that created the configuration data. Includes system version information. That is, when a certain piece of configuration data is sequentially edited and compiled, the same configuration ID and version information that is changed at each compilation is given to the configuration data.

The CAD data for PC includes component data for each component included in the edited signal processing configuration and connection data indicating a connection state between these components. When the edited signal processing configuration includes a plurality of preset components of the same type, separate component data is prepared for each of them.
Each component data is a component ID indicating which preset component the component corresponds to, a component version indicating which version of the preset component is the same, and unique to the component in the signal processing configuration including the component. The unique ID that is the ID attached to the property, the property data that includes the variation information that indicates which variation of the preset component indicated by the component ID, and the position where the corresponding component is arranged on the editing screen on the PC 30 side PC display data indicating the above.

Here, the unique ID is an ID used for associating components included in the configuration data between the configuration data having the same configuration ID, and is managed as follows.
That is, when a new component is arranged on the editing screen of the above-described signal processing configuration, a new unique ID that is not used in the configuration data being edited is assigned to the component and added to the CAD data for PC. . When a variation or version of a component that has already been arranged is changed, the unique ID and component ID of the component are not changed, and the property data or component version is updated. Further, when a component that has already been arranged is deleted, the component is deleted from the PC CAD data, and the unique ID is abolished as a used ID, and is not used again in the same configuration data.

In addition, in the connection data, for each connection of a plurality of connections included in the edited signal processing configuration, connection data indicating which output terminal of which component is connected to which input terminal of which component, and PC display data indicating the shape and arrangement of the connection on the editing screen on the PC 30 side is included.
As can be seen from the above, the PC CAD data is data that defines the content of signal processing to be executed by the DSP 20 of the mixer engine 10 based on the component and the connection between the output terminal and the input terminal of the component. It is.
Each scene in the scene memory is a collection of component scenes that are parameters handled by each component of the signal processing configuration, and the data format and arrangement in each component scene is the component of that component included in the CAD data for PC. It is defined by the data configuration information in the preset component data for PC of the preset component specified by the ID and the component version, and the property data of the component included in the CAD data for PC.
The above is the main data used on the PC 30 side, and these data may be stored in a nonvolatile storage means such as an HDD (Hard Disk Drive) and read out to the RAM for use when necessary.

  In addition to the above data, the PC 30 also stores a current scene that is currently valid setting data in the currently valid configuration. The data of the current scene has the same configuration as each scene of the scene memory described above, and when editing the control parameter of one component of the signal processing configuration by the control panel or the like, the control of the component of the current scene is controlled. Editing can be performed by changing parameters, and the result can be stored as one scene in the scene memory.

  Further, when transferring the configuration data to the mixer engine 10 in the above-described “compile” process, the PC 30 forms engine transfer CAD data in a format suitable for the process in the mixer engine 10 from the PC CAD data. A buffer is also provided. For engine transfer CAD data, data that is not used on the mixer engine 10 side, such as the above-described component and connection PC display data, is deleted from the PC CAD data, and unused portions between the data are further packed. And packing.

Next, FIG. 4 shows a configuration of data stored on the mixer engine 10 side.
As shown in this figure, on the mixer engine 10 side, preset component data and configuration data are stored as main data. However, the preset component data is stored in the flash memory 12 and the configuration data is stored in the RAM 13, and the contents of the configuration are slightly different from those of the PC 30 side. Therefore, the difference from the data stored on the PC 30 side will be mainly described.

  As shown in FIG. 4, the preset component data on the mixer engine 10 side includes engine preset component data. The engine preset component data is data for causing the mixer engine 10 to perform acoustic signal processing on each component. First, instead of a part of the display / editing routine, the DSP 20 is operated to detect the component. It differs from the one for PC in that it includes a microprogram for functioning as a PC.

  In addition, since this micro program is different for each variation even if it is the same preset component, each variation is stored individually. However, since each variation has a relationship such that a common basic process is repeated a different number of times, a common microprogram can be used for the common part of the process, and the number of repeated executions of the program can be changed depending on the variation. In this case, the number of processing steps for executing signal processing related to components, the amount of resources such as a delay memory, and a register differ depending on variations, but the amount of stored microprograms can be made constant. Whether or not such a response is possible depends on the architecture of the DSP 20.

Further, since the mixer engine 10 does not edit the signal processing configuration or display the characteristic graph of the operation parameter, the display data for PC included in the configuration information for PC and the display / editing routine for PC are included. Of these, some routines such as routines for displaying characteristic graphs are not included. On the mixer engine 10 side, the parameter setting value is displayed on the display unit 14 and can be edited by the operation element 15. Therefore, the value of the operation parameter in the PC display / editing routine is displayed. A routine for converting to text data for display is required, and this routine is included in the parameter processing routine.
The other points are the same as the preset component data on the PC 30 side, and the ID and version are the same as the corresponding set and component on the PC 30 side so that the correspondence can be recognized.

  Next, the configuration data for the engine is different from that for the PC 30 in that the engine configuration data includes engine CAD data instead of the PC CAD data. Here, the engine CAD data is obtained by storing engine transfer CAD data received from the PC 30, and as described above, the PC display data is deleted from the PC CAD data and packed.

The other points are the same as the configuration data on the PC 30 side, and the ID and version are the same as the corresponding configuration and components on the PC 30 side so that the correspondence can be recognized.
The mixer engine 10 processes an acoustic signal based on the signal processing configuration edited in the PC 30. For this reason, the CPU 11 forms a microprogram to be executed by the DSP 20 based on the engine CAD data received from the PC 30, and a microprogram forming buffer is prepared as a work area therefor.

  In the microprogram formation process, first, the microprogram specified by the variation information is sequentially read out from the preset component data specified by the component ID and component version of each component included in the engine CAD data, and the properties of each component are read. Based on the variation information in the data and the specified preset component data, resources such as I / O registers, delay memory, and storage registers necessary for operation are allocated to each component, and the microprogram is based on the allocated resources. Is written into the microprogram forming buffer.

At that time, based on the connection data included in the engine CAD data, a data transfer program between the input / output registers corresponding to the input / output terminals of each component is also written in the microprogram forming buffer.
Here, the processing of the microprogram based on the resource allocation corresponds to the architecture of the DSP 20 provided in the mixer engine 10, and if the architecture is different, the microprogram itself is not processed. In addition, for example, a parameter corresponding to the allocated resource may be set in the DSP 20.

  Here, the engine preset component data shown in FIG. 4 is data that is transferred from the PC 30 to the mixer engine 10 to be stored by the consistency check and update processing of the preset component data described below. The data for transfer may be stored on the PC 30 side as independent data different from the PC preset component data, or stored as a part of each component in the PC preset component data. You may make it do. In the latter case, when transferring the preset component data to the mixer engine 10, unnecessary data is dropped from the PC preset component data to create transfer data.

Next, the consistency check and update processing of preset component data in the PC 30 will be described. FIG. 5 shows a flowchart of this process.
In the mixer system shown in FIG. 1, when a preset component is newly developed or improved by the manufacturer, the change can be provided in the form of an upgrade of the editing program. In such a case, the edited version of the editing program includes preset component data for PC or engine that includes preset component data that has been newly developed or improved. When this is installed in the PC 30, these data are stored in the PC 30.

  When the PC 30 executes the editing program in this state, when the PC 30 is instructed to update the preset component data in the mixer engine 10, the process shown in the flowchart of FIG. 5 is performed to check and update the consistency of the preset component data. . For example, when the PC 30 and the mixer engine 10 in operation are physically connected during the operation of the editing program, the mixer engine 10 that is physically connected to the PC 30 is turned on during the operation of the editing program. In this case, when the editing program is activated on the PC 30 physically connected to the mixer engine 10 in operation, the processing may be started as if the above update has been instructed.

  In this process, first, in steps S1 and S2, the version information of the preset component set on the PC 30 side and the mixer engine 10 side is compared. If the version on the PC 30 side is older, the process proceeds from step S3 to S13. A message indicating that the preset component data on the PC 30 side (or an editing program including this) needs to be updated is displayed on the display to prompt the user to update. In this mixer system, if the components included in the preset component data do not match between the PC 30 side and the mixer engine 10 side, the mixer engine 10 cannot be controlled normally, but the editing program on the PC 30 side can be upgraded relatively easily. So you can do this.

  However, since the update of the preset component data on the mixer engine 10 side is performed by transmitting new data from the PC 30 whose version of the editing program has been upgraded, such a situation hardly occurs. However, for example, when there are a plurality of PCs 30 and a PC 30 whose version of the editing program has been upgraded is connected to the mixer engine 10 and another PC 30 that has not yet been upgraded is connected. Can also happen.

  On the other hand, if the version on the PC 30 side is not older, the process proceeds from step S3 to step S4. Then, in the processing up to step S10, each preset component data on the PC side is sequentially targeted, and there is no preset component data with the same ID as the target on the mixer engine side (S5), or even if there is the same ID, the mixer If the version on the engine side is older (S6), the preset component data corresponding to the ID is updated. This update displays on the display that the data is being transferred, transfers the preset component data for transfer stored in the PC 30 to the mixer engine 10, and the flash memory 12 as the engine preset component data. (S7, 8).

  When the above processing is completed for all the preset component data on the PC side, all of the preset component data that needs to be updated is updated. Therefore, the process proceeds to step S11 and subsequent steps, and when the preset component data is updated, the preset component set on the mixer engine 10 side is updated. The version information of is updated to the updated version information, and the process ends. If the update has already been performed and the data is consistent between the PC 30 side and the mixer engine 10 side, the update is not performed again, but in this case, the process is terminated as it is.

By causing the PC 30 to execute the above processing, even when the editing program is upgraded and components are newly developed or improved, they are once installed and activated on the PC 30 side, and the mixer is started. By simply connecting to the engine 10, data relating to components on the mixer engine 10 side can be automatically updated. Therefore, the update operation for the entire mixer system can be easily performed.
Moreover, preset component data can be replaced in units of components for newly developed or improved components.

In the process shown in FIG. 5, the process of step S5 is a process corresponding to an update when a component is added, and the process of step S6 is a process corresponding to an update when a component is improved (version upgrade). It is not essential to do both.
Further, the determination in step S3 may be performed not by comparing the version information of the component set but by comparing the ID and version of each preset component. In this case, if there is a preset component with the same ID and the PC 30 side has an older version, or there is a preset component on the mixer engine 10 side that is not on the PC 30 side, the determination in step S3 is performed. Becomes YES.

Furthermore, FIG. 5 shows an example in which an update is always performed when a component is added or improved. However, before updating, a dialog box is displayed on the display to confirm with the user whether or not the update is possible. It may be.
Further, the components may be divided into essential components and non-essential components, and data of non-essential components may be deleted from the mixer engine or the PC. In this case, it is preferable not to update or warn the deleted component even if an inconsistency is detected.

  Further, in the process shown in FIG. 5, the free space in the storage area prepared for storing preset component data in the mixer engine 10 is managed, and the preset component data to be transferred to the mixer engine 10 is free space. If it is not possible to memorize, it is preferable to stop the transfer and issue a warning to that effect. Here, the size of the storage area can be grasped from the model code of the mixer engine 10 or the like. For the used capacity, if the size of the preset component data for the engine, including the old version, is stored, the ID and version information of the preset component stored in the mixer engine 10 is acquired. It can be grasped by searching based on the information.

[Explanation about component protection: FIGS. 6 to 13]
Next, component protection in this mixer system will be described.
In this mixer system, for some specific components, acoustic signal processing related to the components is permitted only when a predetermined release key is stored in the mixer engine 10 to protect the components. ing. However, editing of the signal processing configuration including the component is permitted regardless of the presence or absence of the release key.

The release key is first transferred from the license server prepared by the manufacturer to the PC 30, and the PC 30 is transferred to the mixer engine 10. The editing program executed on the PC 30 includes a key management program for managing the release key.
The reason why the release key is stored in the mixer engine 10 is that the correspondence between the presence / absence of the release key and the availability of the sound signal processing becomes clearer if the device is actually stored in a device that executes the sound signal processing. . In addition, the mixer engine and the PC can be connected in any combination, and if the mixer engine 10 is configured to be able to perform acoustic signal processing alone, the release key is stored on the PC 30 side. There is also a reason that it is difficult to manage the availability of acoustic signal processing for each engine.
Here, in the following description, for convenience of description, a preset component that performs protection is referred to as a “paid component”. However, this is not intended to limit the preset components for protection to components that require consideration for use. For example, it is conceivable to simply perform protection for user management without requesting a consideration for a release key described later.

By the way, as the release key management method as described above, for example, the following two methods can be considered. First, the first key management method will be described with reference to FIGS.
In the first key management method, the PC 30 simply functions to mediate transfer of the release key from the license server 100 to the mixer engine 10.
That is, in this method, the user first activates the key management program on the PC 30, accesses the license server 100, and the ID (identification information) of the paid component to be unprotected and the mixer engine that wants to use the paid component. And pay the price. When the license server 100 confirms payment of the consideration, the license server 100 transfers the release key to the PC 30. When the PC 30 receives the release key, the PC 30 transfers it to the mixer engine 10 corresponding to the transmitted ID, and the mixer engine 10 that has received the release key stores it in the flash memory 12 as storage means. The storage area for storing the release key is naturally provided in an area that is not operated by the user.

A known technique may be adopted as appropriate for the payment of the price and the safe data transfer between the license server 100 and the PC 30 and between the PC 30 and the mixer engine 10.
Also, the release key is preferably created for each paid component and each mixer engine. For example, as shown in FIG. 7, the ID of the paid component (preset component ID) for releasing the protection and the paid component are displayed. It may be data including information on the ID of the mixer engine to be used. These data may be encrypted, or may be collected into a series of data by a required calculation. Alternatively, a predetermined result may be obtained by performing a predetermined calculation using the release key, the preset component ID, and the mixer engine ID, and a license is given for a combination of a specific mixer engine ID and a preset component ID. Anything can be used.
Further, the release key as described above further includes a serial number for selling the package to the user as proposed by the present applicant in Japanese Patent Application No. 2003-287367, and the license is displayed with the serial number of the package. It may be possible to manage.

Next, the second key management method will be described with reference to FIGS.
In the second key management method, a key pool is provided in the PC 30 so that a release key can be assigned / recovered with any mixer engine connected to the PC 30.
That is, in this method, the user first activates the key management program on the PC 30, accesses the license server 100, and the ID of the paid component to be unprotected, the device ID of the PC 30, the editing program, and the ID of the user. And the number of necessary release keys (the number of licenses) is transmitted to pay the consideration. Then, when the license server 100 confirms the payment of the price, the license server 100 transfers the pool release key to the PC 30. Upon receiving this, the PC 30 adds the received release key to its own key pool.
The format of the pool release key is similar to that shown in FIG. 7, but includes an ID such as the PC 30 instead of the engine ID. When transferring a plurality of pool release keys for the same paid component, they may be identical keys or different keys with serial numbers and the like. The key pool is provided at a position where it is not operated by the user.

  When the user designates the mixer engine 10 to which the release key is to be assigned and the type of the paid component that is desired to be protected and instructs the release of the release key, the PC 30 decreases the number of keys in the key pool. At the same time, a release key as shown in FIG. 7 is generated and transferred to the mixer engine 10, and the mixer engine 10 that has received the release key stores it in the flash memory 12 as storage means. On the other hand, when the user designates the mixer engine 10 storing the release key and the type of the paid component for which the release key is to be collected and instructs the release of the release key, the PC 30 instructs the mixer engine 10 to release the release key. An instruction to delete the key is issued, and the number of keys in its own key pool is increased.

FIG. 9 shows a display example of a key pool management screen which is a display screen for giving the above-described release key assignment and collection instructions.
The release key management screen 50 shown here shows an example in the case where two mixer engines, engine A and engine B, are connected to the PC 30. The key pool management unit 51, the engine A management unit 52, the engine The B management unit 53 has three display units.
Among these, the key pool management unit 51 is a display unit that displays the number of release keys stored in the key pool of the PC 30, and all paid components stored in the PC 30 (with protection set in the header). The number of release keys existing in the key pool is displayed.

In the engine A management unit 52 and the engine B management unit 53, release keys corresponding to the mixer engine are stored for all the paid components among the preset components stored in each mixer engine connected to the PC 30. It is a display part which displays whether it is. These display units are provided in correspondence with the mixer engines connected to the PC 30, and information on the presence / absence of the release key displayed on these display units is obtained by inquiring each mixer engine at the time of display. When the release key management screen 50 is deleted, it is not necessary to store information about the presence / absence thereof.
As can be seen from these display formats, the key pool of the PC 30 can have a plurality of release keys for the same paid component, but each mixer engine has one release key for the same paid component. Just remember.

  In such a release key management screen 50, the user drags the “number of keys” of the release key to be assigned to the mixer engine from the key pool management unit 51 and drops it on the engine management unit corresponding to the mixer engine to which the assignment is made. By doing so, it is possible to instruct the mixer engine to be given a release key. Conversely, by dragging the “key presence / absence” of the release key to be collected from the corresponding mixer engine from the engine management unit and dropping it on the key pool management unit 51, it is possible to instruct the collection of the release key.

Further, by dragging “paid component” from the key pool management unit 51 and dropping it on the engine management unit, it is possible to instruct transfer of the paid component to the mixer engine. In this case, the PC 30 transfers the preset component data by the same processing as steps S7 and S8 in FIG. 5, and updates the display of the release key management screen 50 according to the state after the transfer.
In addition, it may be possible to instruct deletion of a paid component from the mixer engine. However, for those in which a release key is stored, it is preferable that the release key can be deleted only after the release key is first collected. Alternatively, if a release key is stored in response to an instruction to delete a paid component, the release key may be automatically collected from the mixer engine, and the instructed paid component may be deleted thereafter.

  Here, when receiving an instruction to give a release key to the mixer engine, the CPU of the PC 30 executes the processing shown in the flowchart of FIG. First, if the data of the paid component for which key assignment is instructed to the mixer engine is not stored, the process proceeds from step S21 to step S22. In steps S22 to S24, the user confirms whether or not the preset component data needs to be transferred, and if a transfer instruction is received, the transfer is performed. If an instruction that does not require transfer is received, the process ends.

If the data is stored in step S21 or after the transfer in step S24, the process proceeds to step S25 to determine whether there is a release key instructed to be assigned to the key pool of the PC 30. If not, the grant cannot be performed, and a warning to that effect is given to the user in step S29, and the process is terminated.
If there is a release key in step S25, the process proceeds to step S26, and it is determined whether or not the release key that has been instructed to be assigned is stored in the destination mixer engine. If it is stored, there is no need to give it, so a warning to that effect is given to the user in step S29, and the process is terminated.
If not stored in step S26, a release key to be given to the mixer engine is generated in steps S27 and S28, the number of keys in the key pool and the presence / absence of the release key in the mixer engine are changed, and the generated release key is also generated. Is transferred to the designated mixer engine, and the process is terminated.

Through the above processing, when an instruction to give a release key is appropriately given, the release key can be stored in the mixer engine 10 in accordance with the instruction.
Note that it is not essential to perform the processing of steps S22 to S24, and even if NO in step S21, a warning to that effect may be given to the user and the processing may be terminated. Also, it is not essential to execute warnings including those in step S29.
When receiving the release key collection instruction, the CPU of the PC 30 executes the processing shown in the flowchart of FIG. First, in step S31, the mixer engine instructed as the collection destination is instructed to return the release key, and in steps S32 and S34, a response notification from the mixer engine is awaited.

If there is a deletion notification, the process proceeds from step S32 to step S33, the presence / absence of the release key in the mixer engine and the number of keys in the key pool are changed in accordance with the deletion notification, and the process ends. On the other hand, if there is a notification that the key cannot be moved, it can be seen that the paid component related to the release key instructing the collection is being used in the mixer engine, so that a warning is displayed in step S35. The process ends. It should be noted that if neither notification is received within a predetermined time, a timeout error process may be performed.
Even if there is a notification that the key cannot be moved, by changing the program set in the DSP 20 to one that does not use the paid component related to the release key, The release key can be collected.

When the CPU 11 of the mixer engine 10 receives a release key return instruction from the PC 30, the CPU 11 executes the processing shown in the flowchart of FIG. 12. First, in step S41, it is determined whether or not a microprogram that uses the paid component related to the return instruction is set in the DSP 20. If not set, the paid component related to the return instruction is not in use and the release key may be returned. In step S42, the release key related to the return instruction is deleted from the flash memory 12, and A deletion notification indicating this is transmitted to the PC 30 and the process is terminated. Here, since the PC 30 manages only the number of release keys, it is not necessary to transmit the keys themselves. Further, it is not necessary to consider from which PC the release key stored in the mixer engine 10 is transmitted.
When the first or second protection method described later is adopted, when deleting the release key here, the configuration data including the paid component corresponding to the release key to be deleted is also included in the mixer engine 10. It must be deleted so that it does not remain.

On the other hand, if it is set in step S41, the paid component related to the return instruction is in use, and if the release key is returned, the acoustic signal processing related to the paid component without the release key is performed. Therefore, in step S43, a notification that the key cannot be moved is transmitted to the PC 30, and the process is terminated. When a paid component related to the return instruction is in use, signal processing including the component may be forcibly stopped and the release key may be returned.
According to the method as described above, the processing is somewhat complicated as compared with the first key management method, but the release key can be transferred as necessary, and key management with higher flexibility and convenience is performed. be able to.

Next, processing for prohibiting acoustic signal processing related to a paid component and processing for canceling the prohibition using the above-described release key will be described.
Such processing includes processing executed on the PC 30 side when the user is instructed to compile configuration data (data indicating the edited signal processing configuration) or engine transfer CAD data transferred by the processing. In this case, it can be performed by executing a predetermined protection process among the processes executed by the mixer engine 10. And it is preferable to carry out the protection processing at any one of the four locations described below. Hereinafter, the flow of the entire process will be described first, and then the contents of the protection process and the insertion location (shown by broken lines in FIGS. 13 and 14) will be described.

First, FIG. 13 shows a flowchart of processing executed on the PC 30 side when an instruction to compile configuration data is given.
When the CPU of the PC 30 receives a compiling instruction from the user, the CPU 30 starts the processing shown in the flowchart of FIG. First, in step S51, it is determined whether or not all the preset component data included in the configuration data is stored in the mixer engine 10 that executes the acoustic signal processing related to the configuration data to be compiled. If not stored, an error process is performed in step S58, a warning is displayed, and the process is terminated.
On the other hand, if it is stored, in step S52 and S53, the entire CAD data for PC being edited is compiled into CAD data for engine transfer, and this is transferred to the target mixer engine 10. The CPU of the PC 30 functions as a conversion unit in the process of step S52 and as a transfer unit in the process of step S53.

In step S54, it is determined whether or not the component included in the CAD data has changed since the previous compilation. This change includes variations. If there is a change, in steps S55 and S56, a storage area for storing parameters relating to the signal processing configuration is prepared based on the compiled CAD data for PC, and the current scene before compilation and each scene are stored. Copy to that storage area and end the process. However, this copy is an inter-configuration copy in which each component is associated before and after editing of CAD data with the unique ID described above, and only the corresponding data portion is copied between the associated components. The contents will be described in detail in the description of the variation change.
If there is no change in step S54, the current scene and each scene at the time of the previous compilation are taken over as they are in step S57 and the process is terminated. In general, there is a request to take over the parameter setting for a component that has not been changed, so this is the case.

Through the above processing, the signal processing configuration information edited on the PC 30 side is transferred to the mixer engine 10 and the corresponding parameter setting values related to the signal processing configuration at the previous transfer are changed to the latest signal processing configuration. Can take over. If importance is attached to response, parameter inheritance may be performed only for the current scene, or only the current scene may be performed first, and each scene may be subsequently performed as background processing. .
Note that when compiling while editing one piece of configuration data, the configuration ID is the same as the previous configuration ID, and therefore, copying between different configurations in steps S54 to S57 is possible. On the other hand, if the configuration ID is different from the previous compilation time, the signal processing configuration is expected to be completely different from the previous compilation time. Therefore, the processing in steps S54 to S57 is preferably not performed. Instead of this, a predetermined initial value may be written in a storage area prepared by the same processing as in step S55.

Next, FIG. 14 shows a flowchart of processing executed by the mixer engine 10 when engine transfer CAD data is received.
The CPU 11 of the mixer engine 10 starts the process shown in the flowchart of FIG. 14 when the PC 30 receives the engine transfer CAD data transferred by the process of step S53 of FIG. In step S61, the received engine transfer CAD data is stored as engine CAD data. In step S62, it is determined whether or not the component included in the CAD data has changed from the previously received CAD data. This change includes variations.

  If there is a change, in steps S63 and S64, as in steps S55 and S56 of FIG. 13, the current scene and each scene before the CAD data reception are stored in the storage area prepared based on the received CAD data. Copy to the storage area by copying between different configurations. If there is no change in step S62, the current scene and each scene at the time of CAD data reception are taken over in step S65 as in the case of step S57 in FIG. In this case, when the configuration ID is different from that at the previous compilation, it is preferable to write a predetermined initial value in the storage area prepared by the same process as step S63 instead of the process of steps S62 to S65. This is the same as in the case of steps S54 to S57 described above.

  After step S64 or S65, the process proceeds to steps S66 and S67. Based on the received engine CAD data, a microprogram for causing the DSP 20 to execute the acoustic signal processing related to the CAD data is generated and set in the DSP 20 Then, the acoustic signal processing based on the current data is started and the processing is ended. The CPU 11 functions as a program generation unit in the process of step S66.

  With the above processing, the DSP 20 can execute the acoustic signal processing according to the CAD data received from the PC 30. If the current scene before receiving CAD data and the contents of each scene match the contents before compiling on the PC 30 side, the current scene after receiving CAD data and the contents of each scene are obtained by the processing of steps S62 to S65. Can be matched with the contents after compiling on the PC 30 side.

Next, FIG. 15 shows a flowchart of the protection processing according to the first and second protection methods executed on the PC 30 side.
In this process, the CPU of the PC 30 first determines in step S71 whether the CAD data to be compiled includes a paid component. If it is not included, there is no need to protect, so the process returns to the original process and the process continues.
On the other hand, if it is included, it is checked in step S72 whether the transfer destination mixer engine stores all the necessary release keys. If no required release keys are stored, steps S73 to S74 are performed. Then, a warning display indicating that there is no necessary release key is displayed, and the process is terminated. In this case, the acoustic signal processing related to the target CAD data is prohibited. If all the necessary release keys are stored, it is not necessary to prohibit the acoustic signal processing related to the target CAD data, so the process returns to the original processing from step S73 and the processing is continued. That is, the prohibition of the acoustic signal processing related to the target CAD data is canceled.

  Through the above processing, execution of the acoustic signal processing including the paid component is prohibited, and when the release key for canceling the prohibition is stored in the mixer engine 10 that is going to execute the signal processing, the prohibition is canceled. be able to. In this process, in steps S72 to S74, the CPU of the PC 30 functions as a prohibiting unit, and when the determination in step S73 is YES, the CPU functions as a canceling unit.

The confirmation in step S72 may be performed by inquiring the mixer engine 10 and examining the contents of the stored release key. Since the mixer engine 10 and the PC 30 can be freely connected, the type of the release key actually stored in the mixer engine 10 may not match the type recognized on the PC 30 side. This is because it is considered.
At this time, it may be determined that an appropriate release key is stored only when the ID of the mixer engine storing the release key and the ID of the paid component are included in the release key. . By doing so, it is possible to prevent the act of duplicating the release key and using it in another mixer engine, which is effective in preventing fraud.

By the way, the timing of executing the processing shown in FIG. 15 is considered between steps S52 and S53 (first protection method) or between steps S51 and S52 (second protection method) in FIG. It is done.
In the case of the first protection method, the CPU of the PC 30 prohibits execution of acoustic signal processing by prohibiting the transfer of CAD data when the mixer engine 10 does not store a necessary release key. Will function as. In the case of the second protection method, it also functions as a means for prohibiting execution of acoustic signal processing by prohibiting conversion of CAD data.

Next, FIG. 16 shows a flowchart of protection processing according to the third and fourth protection methods, which is executed on the mixer engine 10 side. This process corresponds to the process shown in FIG.
In this process, the CPU 11 of the mixer engine 10 first determines in step S81 whether the acoustic signal processing related to the received CAD data requires a release key for use. Return to the original process and continue the process.

On the other hand, if necessary, it is checked in step S82 whether or not all necessary release keys are stored. If even one required release key is not stored, the process proceeds from step S83 to S84. A warning display indicating that the PC 30 does not have a necessary release key is instructed, and the process is terminated. At the same time, the warning may be displayed on the display 14 by the mixer engine 10 itself. In this case, the acoustic signal processing related to the target CAD data is prohibited. If all necessary release keys are stored, the process returns from step S83 to the original process and the process is continued. That is, the prohibition of acoustic signal processing is lifted.
Through the above processing, the acoustic signal processing can be prohibited and canceled as in the case of the processing in FIG. In this process, in steps S82 to S84, the CPU 11 functions as a prohibiting unit, and when the determination in step S83 is YES, the CPU functions as a canceling unit.

Further, the timing for executing the processing shown in FIG. 16 is considered between steps S61 and S62 in FIG. 14 (third protection method) or between steps S66 and S67 (fourth protection method). It is done.
Then, in the case of the third protection method, the CPU 11 prohibits the generation of a microprogram for causing the DSP 20 to perform acoustic signal processing when the mixer engine 10 does not store a necessary release key. It functions as a means for prohibiting execution of signal processing. In the case of the fourth protection method, it also functions as a means for prohibiting the execution of the acoustic signal processing by prohibiting the execution of the microprogram by the DSP 20. In the fourth protection method, it is not essential to refer to the CAD data in the protection process as long as the necessity of the release key can be determined only from the generated microprogram. Further, after setting a microprogram in the DSP 20 in step S67, the execution thereof may be prohibited.

The above first to fourth protection methods can be applied in duplicate, but it is sufficient to apply at least one of them. However, when the mixer engine 10 is configured to be able to perform acoustic signal processing alone, a prohibition means is provided on the mixer engine 10 side, and acoustic signal processing can be prohibited even with the mixer engine 10 alone. This protection method is preferable from the viewpoint of preventing fraud.
In addition, by performing each processing as described above, only when the mixer engine 10 stores an appropriate release key, it is possible to execute acoustic signal processing using a paid component in the mixer engine 10. . Therefore, even when paid component data is provided to the user, the provider side can manage the use of the paid component, and charging for the use of the data can be easily performed. Even if there is no release key, editing of the signal processing configuration using the paid component is possible, so that the user can recognize the usefulness of the paid component and motivate the license purchase.

  In the above-described processing, the number of stored release keys for the same paid component in the mixer engine 10 is not managed, and if there is one release key, there is any number of paid components in the signal processing configuration. An example of permitting processing has been described. However, the number of release keys stored may be managed, and the same number of release keys as the number of paid components included in the acoustic signal processing may be requested to execute the acoustic signal processing. However, the process described above can simplify the management process of the release key.

  In addition to the PC CAD data being edited as in the case of the processing described above, any PC configuration data stored in the PC 30 can be transferred to the mixer engine 10 and stored as engine configuration data. It is possible to make it possible. In this case, the PC 30 compiles the PC CAD data included in the instructed PC configuration data in response to the configuration data transfer instruction, and includes the configuration header, engine CAD data, and a plurality of scene data. Configuration data is generated and transferred to the mixer engine 10. Then, the mixer engine 10 stores the received engine configuration data in the storage area of the designated RAM 13.

When the above-described first or second protection method is employed (when protection processing is performed only on the PC 30 side), the following is also performed on the PC 30 side when such configuration data is transferred. It is recommended to perform proper protection processing.
That is, when the PC configuration data is transferred, the same processing as that shown in FIG. 15 or 16 is performed, and the PC CAD data in the PC configuration data to be transferred does not include a paid component. Alternatively, if it is confirmed that the required release key is stored in the transfer destination mixer engine 10 that includes a paid component, the configuration data for the PC is transferred only when the confirmation can be made. Good. If the confirmation cannot be made, a warning that a necessary release key is insufficient may be issued. As in the case of the second protection method, compilation may not be performed when the mixer engine 10 does not store a necessary release key.
Further, when the above-described third or fourth protection method is adopted (when the protection process is performed on the mixer engine 10 side), such a protection process on the PC 30 side may not be performed.

  Further, when the configuration data transferred to the mixer engine 10 is to be used for control of the mixer engine 10, one of a plurality of engine configuration data stored in the RAM 13 of the mixer engine 10 is given to the user. The configuration data may be selected as the configuration data indicating the configuration of the signal processing to be executed in step (1). In this case, when such a selection is made, the mixer engine 10 creates a microprogram based on the engine CAD data in the selected engine configuration data, supplies the microprogram to the DSP 20, and the corresponding signal processing operation. Is started, and each scene of the selected engine configuration data and the corresponding current scene are prepared for access on the basis of the engine CAD data. Further, the current scene is initialized, and based on the parameters of the current scene. Control of signal processing operation is started.

When the above-described third or fourth protection method is adopted (when protection processing is performed on the mixer engine 10 side), a time point when the microprogram is created or a time point when the DSP 20 starts a signal processing operation. It is recommended to perform protection processing with. That is, when starting these processes, it is confirmed that the release key necessary for the signal processing to be executed by the mixer engine 10 is stored and confirmed, as in the case of the transfer described above. It is better to execute the process only.
When the above-described first or second protection method is adopted, configuration data that does not store the release key necessary for execution by the mixer engine 10 should not be transferred to the mixer engine 10. Therefore, such protection processing on the PC 30 side may not be performed.

As a configuration of the mixer system as shown in FIG. 1, a configuration in which a microprogram is generated on the PC side and transferred to the mixer engine is also known. When the above-described protection process is to be applied to such a mixer system, the microprogram generated on the PC side uses the data indicating the edited signal processing configuration in a format suitable for the process in the mixer engine. Assuming that there is, it may be handled in the same way as engine transfer CAD data (or engine CAD data) in the above-described processing.
In this case, as a method corresponding to the first protection method, when a micro program is to be transferred from the PC to the mixer engine, the necessity of the release key from the preset component included in the CAD data for the PC which is the basis thereof is determined. It can be considered that the transfer is prohibited when the necessary release key is not stored in the mixer engine.

Further, as a method corresponding to the second protection method, when the PC tries to generate a microprogram, a method of prohibiting the generation in the same manner as described above can be considered.
Further, as a method corresponding to the fourth protection method, when the mixer engine tries to cause the DSP to execute the microprogram, a method of prohibiting the execution as described above can be considered.
Even when each of the above modifications is applied, the same management as the first or second key management method described above can be applied to the management of the release key.

[Explanation on variation change: FIGS. 17 to 28]
Next, a description will be given of component variation change during signal processing configuration editing in this mixer system.
First, the application and function of the variation will be described with reference to FIGS. 2 and 17, taking an automixer (AutoMixer) having variations regarding the number of input terminals as an example. The automixer is a component that outputs the input of the maximum level as it is and attenuates the other inputs.

For example, if the signal processing configuration as shown in FIG. 2 is edited, the components of the automixer are in a state where all input terminals are used. Accordingly, a new input unit as shown by a broken line in FIG. 17 is arranged, and even if an attempt is made to input a signal from the input unit to the automixer, since there is no free input terminal in the automixer, such a connection is set. I can't. However, by changing the automixer component to a 6-input variation with more input terminals, it is possible to set the connection as shown by the broken line in FIG.
On the other hand, when all of the six input terminals are used as shown in FIG. 17 and the input unit indicated by the broken line is deleted, the number of input terminals may be four. By changing to a four-input variation with few, it is possible to reduce resources required for signal processing in the DSP 20.

  In this mixer system, when the variation is changed, among the connections that were connected to the original component terminals, those that have corresponding terminals in the replaced component are also used as the replaced component. At the same time, with regard to the parameters, among the setting values of the parameters relating to the original component, those having parameters corresponding to the replaced component are also taken over by the replaced component.

In the case of variation change, since the basic function of the process is replacement with the same component, there is a strong demand for maintaining the settings related to the component before the change even in the component after the change. Therefore, by performing such processing, it is possible to minimize the trouble of wiring and parameter resetting when components are replaced, and to improve the operability of signal processing configuration editing. Further, the contents of the editing operation can be made intuitive and easy to understand.
And this kind of processing is possible because a special definition of variation is given to a group of components with the same basic processing functions, and the correspondence between the original component and the replaced component can be easily recognized. This is because it was made possible.

Next, operations and processing when such variation is changed will be described.
First, FIG. 18 shows an example of a property setting screen.
When a component arranged on the screen is selected on the CAD screen 40 shown in FIGS. 2 and 17 and property change is selected from the menu, a property setting screen 60 as shown in FIG. 18 is displayed as a pop-up window.
This screen includes a label setting unit 61, a width setting unit 62, a height setting unit 63, a variation setting unit 64, a color setting key 65, a cancel key 66, and an OK key 67.

Among them, the width setting unit 62 and the height setting unit 63 can respectively set the width and height of the symbol when the component is displayed on the CAD screen 40, and the label setting unit 61 can set the symbol of the component. The character string of the label to be attached can be set.
Further, the variation setting unit 64 can set which variation component in the corresponding preset component the selected component. The variation setting section 64 is a pull-down menu. When the right triangle icon is clicked, a menu as shown in FIG. 19 is displayed, and a variation can be selected.

  Since the variations of the automixer shown in the example are only those having different numbers of input terminals, the display contents of the variation setting section 64 are as shown in FIGS. 18 and 19, but for example, like a matrix mixer If there are variations in both the number of input / output terminals, it is also possible to accept the setting of two parameters, the number of input terminals and the number of output terminals, as shown in FIG. Further, when there is a variation in the number of bands as in the case of a parametric equalizer, setting of the number of bands is accepted as shown in FIG.

The color setting key 65 is a key for displaying a screen for setting the display color of the component on the CAD screen 40. When the cancel key 66 is pressed, the screen returns to the original CAD screen 40 without reflecting the setting change so far. When the OK key 67 is pressed, the screen returns to the original CAD screen 40 even if the setting change so far is reflected.
At this time, if the width, height, variation, color, etc. of the component are changed, the CAD screen 40 is redrawn according to the changed setting. The changed property data is stored as property data in the CAD data for PC shown in FIG.

Next, FIG. 21 shows a flowchart of processing for reflecting the setting contents on the property setting screen 60. This process is a process executed by the CPU of the PC 30 when the OK key 67 on the property setting screen 60 is pressed.
In this process, when the variation setting unit 64 is instructed to change the variation in steps S91 to S93, the variation information included in the property data in the CAD data for PC is changed according to the contents, In accordance with the terminal correspondence in the variation before and after the change, the connection data for the variation after the change is created from the connection data before the change. Among these, in the process of step S93, the CPU of the PC 30 functions as the first takeover means.

In steps S94 and S95, if there is a change in the size or color of the component, processing corresponding to the change such as changing the property data in the CAD data for PC according to the content is performed. In addition, when there is a change in the variation, it may be possible to automatically set an appropriate size according to the number of terminals after the change, and the processing related to the size change in that case is also performed here.
Thereafter, in step S96, the CAD screen 40 is redrawn based on the new property data after the change by the processing so far, and the processing ends.
With the above process, even when a component variation is changed and the component is replaced with a different variation, it is possible to transfer the possible connection among the connections set for the variation before the change to the replaced component. it can.

Here, the correspondence between terminals in each variation and the contents of connection takeover will be described in more detail. FIG. 22 shows display examples of 4-, 6-, and 8-input automixer components as examples of automixer variations.
And between these variations, the terminals with the same numbers correspond to each other. Of these, the right output terminal is one for every variation, so it can be said that these correspond to each other. The left input terminals are numbered in order from the terminal displayed on the upper side. If the number of terminals is increased, the terminal is added on the lower side. If the number of terminals is decreased, the terminal is added on the lower side. I try to delete it.

Then, when creating connection data for the replaced component based on this correspondence, if there is a terminal corresponding to the original component in the replaced component, the terminal will continue to be connected to the same counterpart as the original If there is no corresponding terminal, the connection data relating to the original terminal is deleted.
For example, when replacing a 4-input automixer with a 6-input automixer by changing the variation, the connection data for the output terminal and the 1st to 4th input terminals is the connection data for the 6-input automixer before the change. The data is taken over as it is, and there is no connection data for the 5th and 6th input terminals. Conversely, when 6 inputs are changed to 4 inputs, the connection data relating to the output terminals and the input terminals No. 1 to No. 4 are inherited as they are as the connection data relating to the 4-input automixer. No. 6 and No. 6 input terminals are deleted because there is no corresponding terminal after the change.
Even when the connection data is deleted, it is possible to easily reset the connection by displaying the connection with no connection destination in a free end state. Further, when the number of output terminals can be changed, the same correspondence is preferably applied to the output terminals. In addition, when changing the variation, the user may arbitrarily set the correspondence between the terminals.

  By the way, in this mixer engine, when the variation of a component is changed, the parameter value set for the component is also carried over to the replaced component if there is a parameter corresponding to the original. This process is performed in the processes of steps S55 and S56 in FIG. 13 as part of the process related to the compilation when “compile” is executed in the PC 30 after the property setting is completed. The takeover process is performed at this point because the current memory and scene memory, which are parameter storage areas, are prepared only after compilation. Note that the same processing is performed on the mixer engine 10 side in steps S63 and S64 of FIG.

  Here, the parameter takeover process will be described. In this processing, as shown in FIG. 23, a new work area is prepared on the memory, and the current scene and the data format of each scene for storing parameters related to the processing configuration compiled based on the CAD data for PC are determined. The storage area is provided. Then, as shown in FIG. 24, the current scene and the contents of each scene are copied from the original work area to the new work area. At this time, since the data structure of the scene is different between the original work area and the new work area, the copy is a copy between different structures.

A specific example of copying between different configurations of this scene is shown in FIG.
First, as shown in FIG. 25A, when a component is deleted, it is not necessary to simply copy a component scene related to the deleted component. Here, it is possible to confirm which component has been deleted by a newly abolished unique ID.
When the component is changed to a component having a different ID as shown in (b), a component scene related to the changed component is provided instead of the component scene related to the change source component. Since there is no data to be copied here, a predetermined initial value is set. It should be noted that the component before change and the component after change not only differ in component ID but also in unique ID.

When a component is added as shown in (c), a component scene related to the added component is provided at the end of the scene, and a predetermined initial value is also set. Here, which component is added can be confirmed by the newly added unique ID.
In addition, when the component variation is changed, the components before and after the change have the same unique ID and the same component ID. Therefore, the correspondence between the components before and after the change can be recognized, and the data is stored in the two components. Since it can be confirmed that there is compatibility, a parameter takeover process between different variations as shown in FIG. 26 is performed. It should be noted that when performing this parameter takeover processing, it is only necessary to have the component IDs, and it can be executed even between components having no unique ID.

In this takeover process, first, in step S101, among the parameter setting values specified for the original component, those having parameters corresponding to the replaced component are stored in the current memory secured in the new work area. Is copied to the area for storing the setting value of the corresponding parameter.
After that, in step S102, a predetermined initial value is set for the portion of the component parameter after replacement that has not been copied with the original component setting value in step S101, and the processing returns to the original processing.
The above processing is performed for each component when the variation has been changed for a plurality of components. In this process, the CPU of the PC 30 functions as a second takeover unit, and particularly functions as a writing unit in the process of step S101.

Next, the correspondence relationship of parameters before and after the variation change will be described.
In this mixer system, parameters for each component are defined by being divided into units called elements. FIG. 27 shows the configuration of elements in a 4-input automixer in (a) and in a 6-input automixer in (b). Each element is an aggregate of one or a plurality of parameters.
As shown in this figure, in the four-input automixer, the parameters are constituted by elements E1 to E5, and among these, the element E3 is an operation parameter group for controlling the input. Since there are four inputs, as the elements E3 [1] to E3 [4], a parameter storage area of the element E3 corresponding to each input terminal is provided.

On the other hand, the 6-input automixer has the same basic processing as the 4-input automixer, so the parameters to be set are also common, and is configured by elements E1 to E5 as in the case of the 4-input. Yes. However, since the number of input terminals is 6, six elements E3 [1] to E3 [6] are provided for the element E3.
Therefore, it can be said that the parameters related to the elements E1, E2, E4, and E5 are completely the same in the 4-input automixer and the 6-input automixer, and these parameters correspond to each other. In addition, since elements E3 have portions E3 [1] to E3 [4] in common, it can be said that these parameters also correspond. On the other hand, there is no corresponding parameter related to an element that exists only in one side, such as the element E3 [5] or E3 [6].

  Since components having different variations have the same basic processing, the types of elements are the same and the number of parameters to be set is different. Accordingly, parameters other than the automixer can be considered in the same manner as in the above-described case. Note that the element configuration in each variation and the types of parameters included in each element are described in the data configuration information portion in the preset component data.

Next, with reference to FIG. 28, a description will be given of a copy method used when parameters constituted by the elements as described above are handed over from a replacement source component to a replaced component. In this figure, Ex represents a parameter setting value for the original component, and Eo represents a predetermined initial value set when an area is prepared.
FIG. 28A shows an example in which only one identical element exists like the elements E1 and E2 shown in FIG. In this case, the setting value of the original component may be simply copied to the storage area prepared for the replaced component.
FIG. 28B shows an example in which a plurality of the same elements are arranged one-dimensionally like the element E3 shown in FIG. In this case, the setting value of the original component is copied to the corresponding element portion in the storage area prepared for the replaced component. Therefore, since the setting value is not copied to the part of the element that was not in the original component, the predetermined initial value remains set, and the setting value related to the element that is not in the copy destination is discarded.

FIG. 28 (c) shows an example in which a plurality of identical elements are two-dimensionally arranged. Although there is no such example in FIG. 27, for example, when there are a plurality of input terminals and output terminals, a parameter group set for each combination is such an element. In this case as well, the basic idea is the same as in the case of (b), and the setting value of the original component may be copied to the corresponding element portion in the storage area prepared for the replaced component. . Then, the initial value remains in the part that is not copied, and the setting value without the copy destination is discarded. The same applies when the elements are arranged in a three-dimensional or higher format.
With the above-described concept, it is possible to take over the parameter setting values as described with reference to FIG. Note that the initial value is not set when the parameter storage area for the replaced component is provided, and the initial value is set only for the part that has not been copied after the required setting value has been copied. Is also possible.

In addition, the following are examples of main cases for taking over parameter setting values as described here.
First, taking over the parameters for one component when the preset component is upgraded. In this case, the preset component ID does not change, but only the preset component version is changed. However, since the component having the same preset component ID has parameter data compatibility, the parameter of the previous version component stored in the scene or library is used. , Can be carried over as a parameter of the new version component. This is as described with reference to FIGS. At this time, the configuration IDs do not need to match.

  In addition, when the preset component is upgraded, the parameters for one scene are inherited from the configuration data having the same configuration ID and including the old version component to the configuration data including the new version component. In this case, since the configuration IDs are the same, it is possible to recognize the correspondence of each component including the upgraded component by the unique ID. The two components for which the correspondence relationship is recognized may have different versions, but the preset component IDs should be the same. Therefore, each associated component has parameter data compatibility, and a scene can be taken over between both configurations.

  In addition, when a paid component is upgraded, it is possible to take over the license and parameters for one component. Even when a paid component is upgraded, the preset component ID does not change, so if a release key is issued corresponding to the preset component ID as described above, the release key is upgraded with the release key corresponding to the old version. You can continue to use other components. Further, as in the case described above, the parameters of the component of the previous version can be inherited. At this time, the configuration IDs do not need to match. Further, as in the case described above, it is possible to transfer parameters for one scene from configuration data including an old version component to configuration data including a new version component.

  In addition, as described with reference to FIGS. 26 to 28, it is possible to inherit parameters between two components having different variation information with the same preset component ID, and the variations of components included in the signal processing configuration are changed. As described with reference to FIGS. 24 and 25, it is possible to inherit parameters for one scene between configuration data before and after the change.

  Although the description of the embodiment is finished as described above, the present invention is not limited to the above embodiment. For example, the data configuration is not limited to that shown in FIGS. 3 and 4, and a dedicated editing device or control device may be used instead of the PC 30 as the editing device of the mixer system. The number of acoustic signal processing apparatuses is not limited to one, and a plurality of acoustic signal processing apparatuses may be simultaneously connected to the editing apparatus.

  As is apparent from the above description, according to the acoustic signal processing system of the present invention, the configuration of the signal processing in the acoustic signal processing device is edited by the editing device, and the signal processing according to the edited content is performed on the acoustic signal processing device. In the acoustic signal processing system to be performed, unauthorized use of data relating to signal processing components can be effectively prevented while maintaining the convenience and operability of the system. Therefore, if this invention is utilized, utilization of the data regarding a component can be managed easily, and the business which sells the data can be developed.

It is a block diagram which shows the structure of the mixer system which is embodiment of the acoustic signal processing system of this invention. It is a figure which shows the example of the edit screen of the signal processing structure displayed on the display of PC shown in FIG. It is a figure which shows the structure of the data used by PC side among the data relevant to this invention. It is a figure which similarly shows the structure of the data used by the mixer engine side. It is a flowchart which shows the consistency check and update process of preset component data which PC shown in FIG. 1 performs. It is a figure for demonstrating the 1st key management system which manages a cancellation | release key in the mixer system shown in FIG. It is a figure which similarly shows the structure of a cancellation | release key. It is a figure for demonstrating the 2nd key management system similarly. It is a figure which shows the example of the cancellation | release key management screen displayed on the display of PC shown in FIG. 6 is a flowchart showing processing executed when the PC shown in FIG. 1 receives an instruction to give a release key to the mixer engine in the second key management method.

FIG. 6 is a flowchart showing processing executed when the PC receives an instruction to collect a release key. Similarly, it is a flowchart of processing executed when the mixer engine receives a release key return instruction from the PC. 3 is a flowchart of processing executed on the PC side when compiling configuration data is instructed in the mixer system shown in FIG. 1. Similarly, it is a flowchart of processing executed by the mixer engine when engine transfer CAD data is received. Similarly, it is a flowchart of the protection processing according to the first and second protection methods executed on the PC side. Similarly, it is a flowchart of the protection processing according to the third and fourth protection methods executed on the mixer engine side. FIG. 3 is a diagram showing an example of an editing screen corresponding to FIG. 2 for explaining a variation change of components in the mixer system shown in FIG. 1. It is a figure which similarly shows the example of a property setting screen. It is a figure which shows the example of a display of the variation setting part in the property setting screen shown in FIG. It is a figure which shows the other example of a display.

It is a flowchart of the process for reflecting the setting content in the property setting screen which PC performs in the mixer system shown in FIG. It is a figure which shows the example of the variation of the automixer in the mixer system shown in FIG. It is a figure for demonstrating the work area | region provided on the memory of PC similarly in the process of parameter taking over. It is a figure for demonstrating handling of the scene data when a component similarly changes. FIG. 25 is a diagram for describing inter-configuration copy shown in FIG. 24. FIG. 25 is a flowchart showing a parameter setting value takeover process between different variations that is executed as a part of the inter-configuration copy shown in FIG. 24. It is a figure for demonstrating the element structure of the parameter in the component used with the mixer system shown in FIG. It is a figure for demonstrating the copy system at the time of handing over the parameter comprised by an element as shown in FIG. 27 from the component of replacement origin to the component after replacement.

Explanation of symbols

DESCRIPTION OF SYMBOLS 10 ... Mixer engine, 11 ... CPU, 12 ... Flash memory, 13 ... RAM, 14 ... Display, 15 ... Operator, 16 ... PCI / O, 17 ... MIDII / O, 18 ... Other I / O, 19 ... Waveform I / O, 20 ... DSP, 21 ... Cascade I / O, 22 ... System bus, 30 ... PC, 40 ... CAD screen, 50 ... Release key management screen, 51 ... Key pool management unit, 52 ... Engine A management unit, 53 ... Engine B management unit, 60 ... Property setting screen, 64 ... Variation setting unit, 66 ... Cancel key, 67 ... OK key, 100 ... License server, A ... Component, B ... Output terminal, C ... Input terminal, D ... Connection

Claims (6)

A plurality of signal processing components each having an input terminal or an output terminal, and an output terminal and an input terminal of the signal processing component to be executed by an acoustic signal processing device having a programmable acoustic signal processing unit. An editing device that edits configuration data that defines the configuration of acoustic signal processing including the signal processing component and the connection according to instructions received on the display screen of the graphic display, and An acoustic signal processing system including an acoustic signal processing device having a signal processing unit that processes an acoustic signal according to configuration data edited by an editing device,
Specific identification information is attached to the signal processing component, and the type of the signal processing component can be determined based on the identification information.
In the acoustic signal processing device or the editing device,
In the audio signal processing device, and inhibiting means for inhibiting the execution of the audio signal processing based on the configuration data defining the audio signal processing using signal processing components of a specific type of the signal processing component,
A release means for releasing the prohibition when a release key for releasing the prohibition by the prohibiting means is stored in the acoustic signal processing device;
In the acoustic signal processing device,
A storage means for storing the release key;
In the editing device, editing of configuration data defining acoustic signal processing using the specific type of signal processing component is permitted regardless of whether or not the release key is stored in the acoustic signal processing device. An acoustic signal processing system. The acoustic signal processing system according to claim 1,
In the editing device,
A transfer means for transferring the edited configuration data to the acoustic signal processing device is provided,
The prohibiting unit prohibits the configuration data defining the acoustic signal processing using the specific type of signal processing component from being transferred from the editing device to the acoustic signal processing device by the transfer unit. acoustic signal processing system and inhibits the execution of the signal processing. The acoustic signal processing system according to claim 1,
In the editing device,
A conversion means for converting the edited configuration data into a format that can be processed by the acoustic signal processing device;
The prohibiting means prohibits the configuration data defining the acoustic signal processing using the specific type of signal processing component from being converted into a format that can be processed by the acoustic signal processing device by the converting means. acoustic signal processing system and inhibits the execution of the audio signal processing. The acoustic signal processing system according to claim 1,
The editing device is provided with transfer means for transferring the edited configuration data to the acoustic signal processing device,
In the acoustic signal processing device,
Receives configuration data the editing device has transferred, provided the program generation means for generating a program for executing a sound signal processing in the signal processing unit based on configuration data received,
In the acoustic signal processing device, the prohibiting unit is configured to send the program generation unit when the configuration data received from the editing device defines acoustic signal processing using the specific type of signal processing component. acoustic signal processing system characterized by prohibiting the execution of the audio signal processing by prohibiting the program for executing more the audio signal processing is generated. The acoustic signal processing system according to claim 1,
The editing device is provided with transfer means for transferring the edited configuration data to the acoustic signal processing device,
In the acoustic signal processing device,
Receives configuration data the editing device has transferred, provided the program generation means for generating a program for executing a sound signal processing in the signal processing unit based on configuration data received,
When the received configuration data that is a source of the program generated by the program generation unit includes the specific type of signal processing component , the prohibition unit executes the generated program when the signal processing is performed. acoustic signal processing system characterized by prohibiting the execution of the audio signal processing by prohibiting at parts. The acoustic signal processing system according to any one of claims 1 to 5,
The release key includes identification information for specifying an acoustic signal processing device and identification information for specifying a signal processing component,
In the release means, the release key includes identification information unique to the acoustic signal processing device storing the release key and identification information unique to the specific type of signal processing component included in the configuration data. The acoustic signal processing system is characterized in that the prohibition by the prohibiting means is canceled only when the acoustic signal is present.

Images