JP2006139523A - User management method and program having user authority management function - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a protection technique so that the knowhow of programs and data related to additional functions provided by a dealer and for reducing the possibility of being broken by a malicious user, when the dealer, or the like provides additional functions to a system having each kind of function, such as a mixer control program for controlling a digital mixer for processing acoustic signals. <P>SOLUTION: In a user management method, information input by a user in log-on is also used for checking in case of a request for use or editing of the program and data related to the additional function. The program and data related to the additional function include authentication information on a user who utilizes them in advance. When there is a request for use and editing, it is checked whether the user is a user who is allowed to utilize the additional function by using the information input by the user in log-on and the authentication information. <P>COPYRIGHT: (C)2006,JPO&NCIPI

Description

  The present invention relates to a user management method for managing the authority of a user who uses various devices and software, and a program having a user authority management function.

  Conventionally, a digital mixer capable of custom-made a mixer configuration as described in Non-Patent Document 1 is known. This is a mixer configuration (signal processing) in which an acoustic signal processing unit is configured using a processor (for example, a digital signal processing device (DSP)) operable according to a program, and is created and edited using an external PC (personal computer). The acoustic signal can be processed based on the configuration. Creation and editing of the mixer configuration on the PC is performed by a dedicated mixer control program. In other words, run the mixer control program on the PC to display the mixer edit screen, place the components that will be used for signal processing on the screen, and connect the placed components with connections to define the input / output relationship. Create and edit the mixer configuration. By transferring the created mixer configuration to the digital mixer and executing it, the digital mixer realizes the operation of the mixer configuration. Also, the mixer control program on the PC and the digital mixer are synchronized in the online mode, and the digital mixer can be controlled in real time from the mixer control program on the PC.

  As the above-mentioned components, there are preset components (hereinafter referred to as P components) and custom components (hereinafter referred to as C components). The P component is a component that is a basic unit of components of the mixer configuration. The C component is a combination of a plurality of P components that can be handled as one component. A C component can be arbitrarily created and edited by a user having a predetermined authority.

In such a mixer control program, a user authority for each user who uses the program can be defined, and a setting range that can be edited for each user authority can be defined. Normally, a user name (for example, Administrator) with the highest administrator authority is defined in advance, so the user who purchased the mixer engine first logs on to the mixer control program with that user name, and the user name Are registered as appropriate, and user authority for each user name is freely set.
"DIGITAL MIXING ENGINE DME32 Instruction Manual", Yamaha Corporation, 2001

  By the way, there are vendors who create and sell mixer configurations and parameters, but the mixer configurations and parameters created by those vendors can all be seen if the user gives the highest user authority to the user name they use. Could not be protected as. The same applies when a vendor creates and sells a C component, and the user can freely view the configuration and parameters of the C component. As a trader, there is a case where the mixer configuration and C component to be sold are desired to hide the entire configuration and details of parameters from the user.

  This is a common problem when an additional function is incorporated into a system having an arbitrary basic function. When an additional function is incorporated, there are known methods that require the user to enter a password to use the additional function when a request is made to use the additional function. May break the protection.

  The present invention relates to an additional function provided by a supplier when the supplier provides an additional function to a system having various functions such as a mixer control program for controlling a digital mixer that processes an acoustic signal. Protect programs and data (for example, mixer configurations and C components (custom components) in the case of digital mixers) so that their know-how can be protected, and can be broken by malicious users as much as possible. It aims at providing protection technology to make it small.

  In order to achieve this object, the present invention is characterized in that information input at the time of logon by a user is also used for checking when there is a request for using / editing a program or data related to an additional function. Include the authentication information of the user who uses them in advance in the programs and data related to the additional functions, and when there is a request for use / editing, add the information using the information entered by the user at logon and the authentication information Check if the user is allowed to use the function. That is, for example, the user ID and password that are input at logon are included in the program and data of the additional function, and when the use of the additional function is requested, the user ID and password input at logon are the program and data of the additional function. It is characterized by confirming that it matches with the user ID and password contained in.

  If you want to set detailed protection contents for an additional function, include the protection contents in the program or data related to the additional function, and when the user requests to use the additional function, , The authority according to the protection contents is given.

  In addition, in order for a vendor or the like to log on and freely use / edit the additional functions, the vendor must be registered as a user of the system, but the user of the vendor is registered in the administrator of the system. What is necessary is just to have ID registered. Thereafter, if the supplier logs on, changes the password, and logs on again, the additional function can be freely used and edited. Thereafter, the user ID of the trader may be deleted.

  According to the present invention, the information entered by the user at the time of logon is also used for checking when there is a request for use / editing of a program or data related to the additional function. If you try to break the protection, you must try to use / edit additional functions while logging on again and again, and the operation is complicated, so the protection is hard to break. On the other hand, if a supplier who wants to use or edit the additional function freely includes his or her authentication information in the program or data related to the additional function, the additional function can be freely entered by simply entering the authentication information at logon. Can be used / edited. As a result, protection that can protect know-how regarding the additional function is realized.

  Embodiments of the present invention will be described below with reference to the drawings.

  FIG. 1 shows the configuration of an engine of a digital mixer according to an embodiment of the present invention. The engine 100 includes a central processing unit (CPU) 101, a flash memory 102, a RAM (random access memory) 103, a PC input / output interface (I / O) 104, a MIDI I / O 105, other I / Os 106, and a display. 107, an operator 108, a waveform I / O 109, a signal processing unit (DSP group) 110, a cascade I / O 111, and a system bus 120.

  A central processing unit (CPU) 101 is a processing device that controls the operation of the entire mixer. The flash memory 102 is a nonvolatile memory that stores various programs and data used by the CPU 101 and the DSP of the signal processing unit 110. The RAM 103 is a volatile memory used for a load area and a work area for programs executed by the CPU 101. The PC I / O 104 is an interface (for example, LAN, USB, serial I / O, etc.) for connecting an external personal computer (hereinafter referred to as a PC) 130. The MIDI I / O 105 is an interface for connecting various MIDI devices. The other I / O 106 is an interface for connecting other devices. The display 107 is a display for displaying various information provided on the external panel of the mixer. The operator 108 is various operators that are provided on the external panel and are operated by the user. The waveform I / O 109 is an interface for exchanging an acoustic signal with an external device. For example, an analog acoustic signal is input, converted into a digital signal, and passed to the signal processing unit 110. Digital) conversion function, a digital signal input function for inputting a digital sound signal and passing it to the signal processing unit 110, and a digital sound signal output from the signal processing unit 110 being converted into an analog sound signal to be converted into a sound system Implements D / A (digital / analog) conversion function for output. The signal processing unit 110 includes several DSPs (digital signal processors). These DSPs execute various microprograms based on instructions from the CPU 101 to perform mixing processing, effect applying processing, volume level control processing, and the like of the waveform signal input via the waveform I / O 109. Are output via the waveform I / O 109. The cascade I / O 111 is an interface for cascading with other digital mixers. By cascade connection, the number of input / output channels and DSP processing power can be increased.

  In the engine 100 of this digital mixer, the mixer configuration realized by the signal processing unit 110 can be custom-made. The mixer configuration can be created and edited on the screen of the PC 130 by a predetermined mixer control program 131 operating on the PC 130. A collection of multiple created mixer configurations is called a configuration. The mixer control program 131 generates a configuration as configuration data 132 on the memory in response to an operation instruction on the user's screen. The configuration data 132 can be saved as a file in any storage device writable from the PC 130. Each mixer configuration of configuration data on a storage device such as a memory or a hard disk on the PC 130 side can be transferred to the engine 100 after being compiled (converted into information that can be interpreted by the engine 100). The engine 100 can store and save the configuration data transferred from the PC 130 in the flash memory 102. By designating one mixer configuration in the configuration data stored in the flash memory 102 as a current by a predetermined operation, the engine 100 operates on the basis of the mixer configuration. Realize.

  The mixer control program 131 has an online mode and an offline mode as operation modes. These modes can be switched by a predetermined operation. The offline mode is a mode for creating and editing configuration data only on the PC 130 side. The online mode is a mode for controlling the engine 100 in real time from the mixer control program 131 of the PC 130. When the online mode is designated, the configuration data currently expanded on the RAM of the PC 130 is transferred to the engine 100 (after compilation) and stored in the flash memory 102, whereby the PC 130 and the engine 100 configure the configuration data. The data matches. Further, the state of the mixer configuration (parameter setting value, etc.) designated as current on the PC 130 side is sent to the engine 100 so that the PC 130 and the engine 100 are completely synchronized, and the engine 100 can be controlled from the PC 130. become. For example, when a component displayed on the mixer configuration screen of the PC 130 has a fader, or when a control screen of a certain component has a fader, when the fader is operated using a mouse in the online mode, The operation is reflected in the engine 100 in real time. In the online mode, the configuration and connection of components cannot be changed on the PC 130 side. When changed, it automatically enters offline mode.

  The user who creates and edits the configuration data using the PC 130 is not limited to an end user, but may be a trader. For example, when a mixer is installed in a certain venue, a contractor goes to the venue, connects a PC 130 to the mixer, creates and edits configuration data of the mixer configuration that matches the venue from the PC 130, and the configuration data. And the like are stored in the flash memory 102. In this case, the mixer may be non-programmable (the end user is not permitted to create and edit the mixer configuration, and the end user simply calls and uses the mixer configuration created by the vendor). Since the end user can read out the mixer configuration of the configuration data stored in the flash memory 102 using the operation unit 108 on the panel and operate as a mixer of the mixer configuration, it is not necessary to connect the PC 130 during the operation. . Of course, it is possible to connect the PC 130 and set the online mode to control the mixer by an operation from the PC 130.

  Specifically, the creation and editing of the mixer configuration by the mixer control program 131 is performed by arranging and connecting P (preset) components and C (custom) components on the mixer configuration screen of the PC 130. Drawing a connection between components is equivalent to defining a signal input / output relationship between components. The P component and the C component are simply referred to as a component. The P component is a component block prepared by the manufacturer as a basic unit for configuring the mixer configuration. For example, an audio processor such as an automixer, compressor, effect, crossover, fader, switch, pan, meter, etc. The parts component is prepared. The C (custom) component is a component created and edited by the user, and includes a plurality of P components or C components.

  FIG. 2A shows a configuration of P component data (PC data) used by the mixer control program 131 of the PC 130. One PC data is definition data that defines one P component, and is stored in advance in any storage means accessible by the mixer control program 131. PC data is prepared for each type of P component. Here, it is assumed that there are Npc types. The version of the P component set is assigned to the entire Npc PC data. One piece of PC data includes a PC header, PC configuration information, a PC processing routine, and a display editing processing routine. The PC header includes a P component ID (PC_ID), a P component version (PC_Ver), and the like. PC data can be specified by PC_ID and PC_Ver. The PC configuration information is information (including the order of elements) indicating what elements the P component is composed of, and includes display data such as a control screen of the P component. An element refers to a component corresponding to a part constituting a P component. Further, the PC configuration information indicates parameter item configuration information for each element constituting the P component (for example, the data format of the parameter of the element is a single value, a one-dimensional array, or a two-dimensional array). Array information and data size of one element). The PC processing routine is a program for performing various processes related to PC configuration information. When the mixer control program 131 processes the mixer configuration, a PC processing routine for each P component is used. The display edit processing routine is a program group used when creating and editing CF data described later.

  FIG. 2B shows a configuration of C component data (CC data) used by the mixer control program 131 of the PC 130. The CC data is definition data that defines the C component. One CC data is composed of a CC header and PC CAD data. The CC header includes a C component ID (CC_ID), a C component version (CC_Ver), a system version (SYS_Ver), and the like. CC data can be specified by CC_ID and CC_Ver. The CAD data for PC in the CC data is data that defines what components are connected and how the C components are connected. The C data that is data specifying P components and C components, and It consists of connection data connecting those components. Further, the CAD data for PC in the CC data includes display data such as a C component configuration screen of FIG. The CC data may further include user control screen data created for the C component.

  The C component data shown in FIG. 2B can be arbitrarily created and edited by a user having a predetermined authority and stored in a predetermined storage device. The CC data provided by the vendor is taken into the PC 130 by a predetermined installation procedure (for example, a file copy of CC data). In particular, when a supplier provides CC data, there are parts that the end user does not want to see or edit due to the CC data configuration, parameter settings, etc., so the CC header has a user ID and password ( What is not notified to the end user), and if necessary, the contents of the vendor protection are encrypted and stored. When the display or editing of the configuration indicated by the CAD data for PC of the CC data is instructed, it is determined whether the logged-on user is logged on by entering the user ID and password of the supplier. The display or editing of the CC data composition screen is not allowed. The CC data created by the end user himself / herself, or the CC data that the vendor allows the end user to use freely, the vendor user ID and password in the CC header are blank. Has permission to use. In addition, partial permission information or partial prohibition information for a user other than the vendor user who provided the CC data is described in the column of the vendor protection content, and the CC data is sent to the user other than the vendor user. Display and editing may be partially permitted or prohibited with respect to. Details of the method for controlling the CC data provided by the vendor so that only the vendor can operate will be described in detail later.

  FIG. 3A shows the structure of configuration data on the RAM processed by the mixer control program 131 in the PC 130. Reference numeral 210 denotes configuration data expanded on the RAM, which is composed of a plurality of CF data 1 to Ncf and a scene memory. The entire configuration data 210 can be stored as one file in an arbitrary storage device (for example, a hard disk in a PC). Conversely, the configuration data read from an arbitrary storage device can be expanded on the RAM of the PC 130 in a format such as 210. In the CF data 1 to Ncf, the numbers 1 to Ncf are called configuration numbers (CF numbers). CF data (or an area in which the CF data is stored) can be specified by the config number. The current pointer is a pointer that points to the CF data to be processed. The CF data pointed to by the current pointer is displayed on the mixer configuration screen described later with reference to FIG. The CF data pointed to by the current pointer is called “current configuration”.

  One CF data is data defining one mixer configuration, and includes a CF header, PC CAD data, Nps presets, and a predetermined number of UC data (user control screen data). The CF header includes a configuration ID (CF_ID), a configuration version (CF_Ver), a system version (SYS_Ver), and the like. CF data can be specified by CF_ID and CF_Ver. The CAD data for PC is data that defines what component and how the mixer configuration of the CF data is configured, and the P component and C component used as the components of the mixer configuration It consists of C data, which is data to be specified, and connection data connecting those components. The CAD data for PC includes display data for a mixer configuration screen shown in FIG. The C data in the PC CAD data includes a component ID (C_ID) and a component version (C_Ver), a unique ID (U_ID), and other data (for example, a property) specifying the P component or the C component. As C_ID and C_Ver of C data, P component is specified by specifying PC_ID and PC_Ver of PC data in FIG. 2 (a), or C component is specified by specifying CC_ID and CC_Ver of CC data in FIG. 2 (b). Is identified.

  Next, presets in CF data will be described. One CF data includes a plurality of presets (the number is arbitrary), and the plurality of presets are collectively referred to as a library of the CF data. In presets 1 to Nps, numbers 1 to Nps are called preset numbers. A preset (or an area in which the preset is stored) in the CF data can be specified by the preset number. The preset indicates specific parameter value set data used in the mixer configuration of the PC CAD data of the CF data including the preset. One mixer configuration is defined by the above-mentioned CAD data for PC. When a digital mixer actually operates with the mixer configuration, it is necessary to set predetermined parameters for each component. For example, it is necessary to set a parameter value such as an input level and an output level in the case of an automixer, and a level in the case of a fader. A preset is a data set of parameter values used when each such component actually operates.

  One preset consists of a header and any number of C (component) scenes. The portion of the C scene in the preset is called a parameter data set. The order of arrangement of C scenes in the parameter data set corresponds to the arrangement of C data in the CAD data for PC. In the figure, the parameter of the component specified by C data A is C scene 3A, the parameter of the component specified by C data B is C scene 3B,. One C scene is composed of a sequence of element scenes, and each element scene is composed of a sequence of parameter scenes. The preset header holds the data structure of the subsequent parameter data set.

  Next, UC data will be described. The UC data is data that defines a user control screen, and can be arbitrarily created and edited by a user having a predetermined authority and stored in the CF data. Further, the UC data provided by the supplier is taken into the CF data in the PC 130 by a predetermined installation procedure (for example, a file copy of the UC data). As with the CC data above, when a supplier provides UC data, the user control screen that the supplier provides only for later use, or parameters that are displayed on the screen but that the end user does not want to change. In some cases, the user control screen includes Therefore, similarly to the CC data shown in FIG. 2B, the UC data provided by the vendor stores the user ID and password of the vendor and the contents of the vendor protect if necessary. When an instruction to display or edit the user control screen of the UC data is given, it is determined whether the logged-on user is logged on by entering the user ID and password of the supplier. Otherwise, the configuration of the UC data is determined. Screen display and editing are not allowed. The UC data created by the end user himself / herself or the UC data that the merchant has allowed the end user to freely use is basically blank because the merchant user ID and password in the UC data are blank. Has the right to use. In addition, partial permission information or partial prohibition information for a user other than the trader user who provided the UC data is described in the column of the trader protection content, and the UC data is sent to a user other than the trader user. Display and editing may be partially permitted or prohibited with respect to. Details of the method for controlling the UC data provided by the vendor so that only the vendor can operate will be described in detail later.

  Next, the scene memory will be described. The scene memory stores Ns (the number is arbitrary) scenes 1 to Ns. The numbers 1 to Ns are called scene numbers. The area where each scene is stored or the scene stored in the area can be specified by the scene number. One scene includes a configuration number, a preset number, a security level, an owner ID, and the like. The user can call a scene by designating a scene number (this is called scene recall). When a scene recall is instructed, the current pointer is set so that the CF data of the configuration number of the scene becomes the current configuration, and the CF data is displayed on a mixer configuration screen (FIG. 6) to be described later. The preset with the preset number is read and set in the current scene (described later in FIG. 3B). Conversely, the user can specify the scene number and save the current configuration and the current current scene in the scene memory (this is called a scene store). The security level and owner ID will be described in detail with reference to FIG.

  FIG. 3B shows the structure of other data on the RAM processed by the mixer control program 131 in the PC 130. The current scene indicates a parameter data set set in the mixer configuration of the current configuration, that is, the current parameter value (current value) of each component of the current configuration. The current scene access routine is a method that provides an access function to the current scene. The engine CAD data formation buffer is a buffer that generates engine CAD data from PC CAD data when CF data is compiled.

  FIG. 4A shows a part of the configuration of P component data (PC data) stored in advance in the flash memory 102 in the mixer engine 100. This PC data is almost the same as the PC data configuration on the PC side shown in FIG. 2 (a), and the description in FIG. 2 (a) can be applied as it is, so only the different part is shown in FIG. 4 (a). It was. That is, on the engine 100 side, the display edit processing routine portion of FIG. 2A is replaced with the PC microprogram of FIG. 4A. Since the engine 100 cannot display the mixer configuration screen or the control screen, the display editing routine for the display editing is not necessary. Instead, the engine 100 needs to form a microprogram corresponding to the mixer configuration of the engine CAD data and send it to the DSP group, so a PC microprogram corresponding to each component as shown in FIG. is there. It is assumed that all the PC microprograms corresponding to variations in the number of inputs and outputs that may be specified are prepared. Although not shown, the PC processing routine is assumed to be various programs for processing each piece of configuration information in the engine.

  FIG. 4B shows a part of configuration data on the flash memory 102 of the engine 100. Since this data is almost the same as the configuration data in the PC shown in FIG. 3A, the description in FIG. 3A can be applied as it is, so FIG. 4B shows only different parts. . That is, on the engine 100 side, the CAD data for PC in FIG. 3A is replaced with the CAD data for engine in FIG. 4B. The CAD data for engines is the same as the CAD data for PCs in that it is data representing the mixer configuration as shown on the mixer configuration screen, but no data for display is required in the engine, and the amount of data is reduced. Therefore, it is expressed in binary format without including display data. The engine CAD data is generated on the engine CAD data formation buffer of FIG. 3B by compilation. The engine 100 side also has a current pointer, and the CF data pointed to by the current pointer is “current configuration”. Note that there is no concept of a C component on the engine side, and CF data including the C component on the PC side is expanded into a lowermost P component at the time of compilation. Accordingly, all the C data in the engine CAD data in FIG. 4B indicates the PC data. Furthermore, since the user control screen cannot be displayed on the engine side, the CF data on the engine side does not have the UC data 1, 2,... Of FIG.

  FIG. 4C shows other data on the RAM 103 of the engine 100. The current scene is a parameter data set set in the mixer configuration of the current configuration on the engine side, and is the same data as the current scene on the PC side shown in FIG. The description of the current scene in FIG. 3B can be applied to the engine-side current scene in FIG. Although not shown in FIG. 4C, an access routine is also prepared. The microprogram forming buffer is a buffer used to form a microprogram corresponding to the mixer configuration. When the current pointer is switched, a microprogram that realizes the mixer configuration of the engine CAD data of the CF data that has newly become the current configuration is expanded on the microprogram formation buffer, and the microprogram is transferred to the signal processing unit 110. The As a result, the DSP group of the signal processing unit 110 realizes the operation of the mixer configuration of the CAD data of the current configuration. Further, when a new current scene is read or when the current scene is changed, the current scene is automatically transferred to the signal processing unit 110. The signal processing unit 110 expands the transferred current scene in the coefficient memory of the DSP group. The DSP group of the signal processing unit 110 executes the transferred microprogram using the coefficient of the coefficient memory, whereby the signal processing unit 110 has the mixer configuration of the CAD data for the engine of the current configuration and the current scene. Operation with the parameter data set is realized.

  Although the method for storing the configuration data in the flash memory 102 of the engine 100 as described with reference to FIG. 4B is arbitrary, it is normally performed by designating the online mode on the PC 130. When the online mode is designated by the PC 130, each CF data of the configuration data 210 on the RAM shown in FIG. 3A is compiled and transferred to the engine 100, and the contents of the scene memory are also transferred to the engine 100. In the engine 100, the transferred CF data and the contents of the scene memory are stored in the flash memory 102 as described with reference to FIG. As a result, the configuration data matches between the PC 130 and the engine 100. Further, in the online mode, the current scene on the PC 130 side in FIG. 3B is transferred and stored in the current scene of the engine 100 in FIG. 4C, and its access routine is prepared. As described above, in the online mode, the PC 130 and the engine 100 are completely synchronized, and when the current scene on the PC 130 side is changed, the change is reflected in the current scene of the engine 100.

  Since the flash memory 102 is non-volatile, the stored configuration data is retained even when the engine power is turned off. Once the configuration data is stored in the flash memory 102, even if the PC 130 is not connected to the engine 100, the engine 100 alone calls a scene by specifying a scene number (the current mixer configuration (CF data ), The parameter value of the current scene can be changed, and the current mixer configuration and the current scene can be specified and stored in an arbitrary scene number.

  FIG. 5A shows a logon screen 500 that is initially displayed when the mixer control program 131 is started. Reference numeral 501 denotes a user name input area, 502 denotes a password input area, 503 denotes an OK button, and 504 denotes a cancel button. When the user inputs a user name and password in areas 501 and 502 and presses an OK button 503, a basic screen 510 described below is displayed.

  FIG. 5B shows a basic screen 510 that is first displayed when the user properly logs on to the mixer control program 131 on the PC 130. On the basic screen 510, an initial screen corresponding to the connection status of the mixer engine 100 is displayed. Here, since only one engine 1 is provided, a block 511 corresponding to the engine 1 is displayed. In addition, it can also be set as the structure which connected the some engine in cascade, and in that case, the block corresponding to each engine is connected and displayed. Reference numeral 514 denotes a menu displayed when the mouse cursor is placed on the block 511 indicating the engine 1 and the right button of the mouse is clicked. Using the right-click menu 514 or the menu at the top of the basic screen 510, various processes relating to the mixer configuration of the engine connected to the PC 130 can be advanced.

  When “Open control screen” is selected from the right-click menu 514, user control screens 800 and 810 as shown in FIGS. 8A and 8B are displayed. The number of user control screens that can be defined in one CF data is arbitrary, but in this embodiment, it is assumed that two are defined. In the property screen of each engine opened by “Property” in the right-click menu 514, any one of a plurality of user control screens can be set as the control screen of the engine. When “Open control screen” is selected from the right-click menu 51, the user control screen set as the control screen of the engine is opened. On the other hand, when “Open configuration screen” is selected from the right-click menu 514, a mixer configuration screen 600 of the engine as shown in FIG. 6 is displayed. When “Open” is selected from the right-click menu 514, either the control screen or the mixer configuration screen is displayed. Which screen is opened is set on the property screen of each engine as in the control screen. The same instruction as the operation from the right click menu 514 can be performed using the menu at the top of the basic screen 510. Further, when the block 511 indicating the engine is double-clicked, the same processing as when “Open” is selected from the right-click menu 514 is performed.

  A mixer configuration screen 600 in FIG. 6 is a screen showing a mixer configuration of CF data (current configuration) pointed to by the current pointer in the engine 1. On the mixer configuration screen 600, P or C components that are constituent elements are displayed based on the current configuration, and are connected by connections that define the input / output relationship between the constituent elements. Reference numerals 601 and 606 denote elements representing an input terminal and an output terminal for the engine 1. Reference numerals 602 and 607 denote elements representing terminals used when a plurality of engines are cascade-connected. Reference numerals 603 and 604 denote C components, and 605 denotes a P component. These displayed P or C components are components specified by the C data of the PC CAD data of the current configuration, and correspond to the PC data of FIG. 2A and the CC data of FIG. 2B. ing. When the mixer configuration is created and edited on the mixer configuration screen 600, the creation and editing is reflected in the current configuration.

  When the element 603 or 604 indicating the C component is right-clicked, a right-click menu similar to 514 in FIG. 5B is displayed, and in the same manner as the operation on the basic screen 510, FIGS. 8A and 8B are displayed. The user control screen and the C component configuration screen of FIG. 7 can be opened. When the element 605 indicating the P component is right-clicked, the same right-click menu is also displayed. However, since there is no P component configuration screen, there is no “Open Configuration Screen” option. The control screen “Open control screen” means “User control screen” when the engine or C component block is right-clicked, but “Open control screen” in the right-click menu of the P component This means that a unique control screen (in the PC configuration information in FIG. 2A) prepared by the manufacturer for the P component is opened. The P component control screen is provided with operators for changing the settings of various parameter items of the P component. When these operators are operated, the current scene is changed according to the operation. The value of the parameter corresponding to the operator is changed.

  The C component configuration screen 700 in FIG. 7 is an example of a screen showing the C component configuration (CC data read into the current memory in the PC) of the C component 604 displayed in FIG. In the C component configuration screen 700, as in the mixer configuration screen 600, the P or C component that is the component of the C component is displayed based on the CC data on the current memory, and the input / output relationship between the components is displayed. It is connected with the prescribed connection. Reference numerals 701 and 705 denote elements representing input terminals and output terminals to the C component. Reference numerals 702 to 704 denote P or C components. These displayed P or C components are components specified by the C data of the CAD data for PC of the CC data on the current memory. The PC data of FIG. 2A and the CC data of FIG. It corresponds to data. When an instruction is given to save the C component in the current memory being created and edited on the C component configuration screen, the CC data representing the configuration of the C component displayed at that time is specified in the format described in FIG. The file name can be stored in any storage means. Conversely, when the CC data in the format of FIG. 2B stored in an arbitrary storage means is opened, the CC data is read into the current memory, and the C component configuration screen corresponding to the CC data is shown in FIG. Will be displayed and can be edited.

  The user control screen shown in FIGS. 8A and 8B will be described. The user can create an arbitrary number of user control screens in one piece of CF data. When editing an existing user control screen, for example, an “edit mode” is selected from a right-click menu (not shown) that appears when the user control screen is right-clicked (for example, right-clicking on a background portion). As a result, the user control screen is shifted from the normal mode to the edit mode, and an operator or the like is dragged from the control screen of the P component which is a component of the mixer configuration or C component to the window of the user control screen in the edit mode. It is created by copying and arranging by & dropping and performing various edits such as the position on the window, the color, size, and shape of the operation element. For example, the user control screen 800 of FIG. 8A opens the control screen of any component displayed on the mixer configuration screen of the engine 1 of FIG. 6, and the operator 801 and the display element 802 are displayed from the control screen. It was created by drag and drop. Similarly, the user control screen 810 of FIG. 8B opens the control screen of any component displayed on the C component configuration screen of FIG. 7, and from the control screen, the meter 811 and the operator (knob) 812 and the display element 813 are created by dragging and dropping. Here, the copy source of the controls and display elements arranged on the user control screen is the P component which is a component of the mixer configuration of any engine of the CF data to which the user control screen belongs, or the mixer configuration thereof It is a control screen of P component which is a component of the C component made. It cannot be copied from the control screen of the P component which is a component of another CF data mixer configuration. When the desired editing is completed, it is possible to return from the editing mode to the normal mode by selecting “normal mode” from a right-click menu (not shown) that appears when the user control screen is right-clicked. Note that the method for creating the user control screen is not limited to that described here. When an operator in the user control screen is operated in the normal mode, the parameter value corresponding to the operator in the current scene is changed according to the operation.

  5 to 8 described above, it is assumed that the logged-on user has authority to execute all operations. In practice, it is assumed that the mixer 100 and the mixer control program 131 in FIG. 1 are used by a plurality of users, and the usage authority of each user is managed. Hereinafter, setting of such use authority (security setting) will be described.

  FIG. 9 shows a screen example of a security setting dialog 900. With this dialog 900, user registration / change / deletion and application function security settings in the digital mixer of this system are performed. The dialog 900 can be called on the PC 130 by a predetermined operation (for example, menu selection on the basic screen 510). Users (accounts) of this system are incorporated in a hierarchical structure to be described later. Therefore, there is an upper, peer, and lower relationship among the users in the hierarchical structure. When viewed from a certain user, a user who can be traced in the lower direction is referred to as a “lower user”, and a user who is traced in the upper direction is referred to as a “super user”. Among logged-on users, a user who has authority over the owner of the group to be described later can edit the account of a user lower than himself / herself by this dialog 900. You cannot create a user higher than the logged-on user or edit the logged-on user's own account. Note that the user account data created in this dialog 900 is stored in an initial setting file (not shown) of the mixer control program 131. Since this initial setting file is different from the configuration data file, the user account settings will not change even if different configuration data is read.

  In the dialog 900, an Enable Auto Log On check box 901 is used to switch the automatic logon function between enabled and disabled. When this is turned on (checked), the automatic logon function (which can log on without entering a password when logging on) is enabled. When this check is removed, a dialog requesting input of the password of the currently logged-on user is displayed. This is to prevent the automatic logon function from being invalidated when the password is lost or forgotten, and the situation where the user cannot log in again. An Auto Log On user combo box 902 is a combo box for designating an automatic logon user when the Enable Auto Log On check box 901 is turned on. When the automatic logon function is disabled, it is disabled. Also, it is not possible to select a person with a user level higher than the logon user.

  The User List 903 is an area for displaying and editing various types of information related to registered users. The User List view 904 displays a hierarchical structure of a list of user names currently registered. The top-level user is Administrator. When the system is shipped from the factory, only the Administrator is registered as a user. Supervisor A and Supervisor B are subordinates of Administrator, Operator A and Operator B are subordinates of Supervisor B, and Support is subordinates of Operator A. The Administrator can set an arbitrary user in this hierarchical structure as a group owner, which will be described later, by performing a predetermined operation. For example, it is assumed that Supervisor A and Supervisor B are set as owners. A user set as an owner can edit a user under his / her (logged on user name). When a user name is arbitrarily selected from those displayed in the User List view 904, a user with the selected name becomes an editing target. Editing includes adding a user with the Add User button 906, deleting a user with the Remove User button 907, changing a user name and other items with the Change button 908, turning on / off each check box 951 of the Operation Security 905, and Scene Store / Recall Level. And user control level 952 level setting. Note that, even in the hierarchical structure displayed in the User List view 904, even a logged-on user set as an owner, a user who cannot follow the logged-in user in a lower direction is lower than the logged-on user. That said, you cannot edit the user's account. For example, in FIG. 9, Operator B cannot edit Support. In addition, a user higher than the user set as the owner can edit the accounts of all the users traced down from the user (self).

  For a given user, all users who follow from that user to the lower level are referred to as “subordinate” users. Also, in the user hierarchy displayed in the User List view 904, the user set as the owner and all the users under the user are defined as one “group”, and the user set as the owner is the owner of the group. It becomes. Another user who can be traced upward or downward from the user set as the owner cannot be set as the owner. That is, different groups are configured such that users constituting those groups do not overlap each other. In addition, in the User List view 904 of the screen of FIG. 9, by changing the display color of the user set as the owner and the members of the group or by underlining, the state of the owner and grouping can be understood at a glance. Yes.

  FIG. 10 shows a display mode in the security setting dialog 900 of FIG. In FIGS. 10A and 10B, the column “user selected in tree” indicates the user to be edited selected in the User List view 904. The columns “Add User button”, “Remove User button”, and “Change button” indicate how the buttons 906 to 908 are displayed. The column “each check box” indicates the display mode of each check box indicated by 951 in FIG. 9. The column of “each security level setting unit” indicates a display mode of each security level setting unit indicated by 952 in FIG.

  FIG. 10A shows a case where the logged-on user is Supervisor B set as the owner. In this case, when an administrator or supervisor A who is a higher-order or peer user of Supervisor B is selected, the Add User button 906, Remove User button 907, and Change button 908 are all “grayed out”, that is, invalid buttons that cannot be operated. Is displayed. Each check box 951 and each security level setting unit 952 display how they are set, but are displayed as “grayed out” and cannot be operated. When the logged-on user Supervisor B selects himself, the Add User button 906 is displayed as an operable “valid” button, but otherwise “grayed out” is displayed and cannot be operated. When Operator A, Operator B, or Support, which is a user under Supervisor B, is selected, the Add User button 906, Remove User button 907, and Change button 908 are all displayed as “valid” buttons. Each check box 951 is basically displayed as “valid” and can be operated. However, for an item for which an authority is not given to the user immediately above the user to be edited (direct user), an X mark is displayed as “grayed out”. Inoperable. For example, when the item of Supervisor DSP's View DSP Design Window is checked off, the check box of the same item of the Operator A (and Support) user is displayed as “grayed out” with a cross. Each security level setting section 952 is basically displayed as “valid” and can be operated, but within a range lower than the level given to the user immediately above the user to be edited (in terms of level value, the level value of the user immediately above) It can be set with a large value. In short, the items to be checked are within the range below the authority given to the immediate user, and the security level is within the range lower than the authority granted to the direct user and higher than the right granted to the direct user. Thus, each subordinate user can be given authority.

  FIG. 10B shows a case where the logged-on user is Administrator. In this case, the Remove User button 907 is displayed as “grayed out” and cannot be operated so that the Administrator itself is not deleted. Everything else is displayed as “valid” and can be operated.

  Returning to FIG. 9, the contents that can be changed by each button or check box will be described.

  By clicking the Add User button 906 displayed as valid, a new user can be added immediately below the user to be edited in the selected state. FIG. 11 shows an Add User dialog 1100 displayed when the Add User button 906 is clicked. In the Name column 1101, a user name to be added is input. In the Password column 1102, a password used when the user to be added logs in is input. The Confirm Password column 1103 is a column for inputting again in order to prevent erroneous input of the password. The Startup User Control check box 1104 sets ON / OFF of Startup User Control for the user to be added. For users with Startup User Control on, the user control screen is automatically opened when the user logs on or switches the current configuration. However, as will be described in detail later, only when the security level set on the user control screen of the CF data to be opened is equal to or lower than the user control level of the user (say by value) If Security Level ≧ User Control Level), the user control screen is opened. When a new user is added, as a default, each check box 951 is left unchecked, and each security level setting unit 952 has 1 for each of the scene store / recall level and user control level of the user to be edited. The added value (one lower level). As will be described later, since 10 corresponds to the lowest level in these level values, when the scene store / recall level or the user control level of the user to be edited is 10, a new user cannot be created below that.

  In FIG. 9, when the Remove User button 907 displayed as valid is clicked, the user to be edited is deleted. In this case, the subordinate users are also deleted at the same time. When the change button 908 displayed as valid is clicked, a Change User Information dialog is opened, and information on the user to be edited can be changed. The Change User Information dialog is the same content / function as the Add User dialog shown in FIG.

  Each check box 951 of Operation Security 905 means that the authority is given to the editing target user when the check is turned on, and that the authority is not given when the check is turned off. The Edit check box creates and edits the mixer configuration on the mixer configuration screen of FIG. 6, creates and edits the C component on the C component configuration screen of FIG. 7, and creates and edits the user control screen as shown in FIGS. Authority, View DSP Design Window check box is an authority to display the C component configuration screen and mixer configuration screen, Control Component Editor check box is an authority to change parameter settings on the P component control screen and user control screen, View Component Editor The check box includes authority to display those control screens, and the Change Configuration check box includes switching of the current configuration, that is, changing the current pointer (scene switching accompanied by switching of the current configuration. Turn off if you want to prevent switching )), And the Synchronization check box turns on the authority to switch the mixer control program 131 and the mixer engine 100 to the online mode, which is a mode in which the configuration data and the current scene operate in synchronization with each other. Check box to turn off.

  The scene store / recall level of the security level setting unit 952 sets the authority to store and recall scenes with level values. Levels from 1 to 10 can be set. Level 1 indicates the strongest authority and level 10 indicates the lowest authority. As will be described later, each scene in the scene memory has a security level (specifically, Edit Security and Recall Security), and when the logged-on user tries to store / recall a scene, the user's Scene Store / Recall The Level and the Security Level of the scene to be stored / recalled are compared. Store is possible when Scene Store / Recall Level is higher than or equal to Edit Security (Scene Store / Recall Level ≦ Edit Security in the level value), and cannot be stored otherwise. In addition, when the Scene Store / Recall Level is higher than or equivalent to the Recall Security (the level value is Scene Store / Recall Level ≦ Recall Security), the recall is possible, and otherwise the recall is impossible.

  User Control Level sets the authority to display (and operate) the user control screen described with reference to FIGS. 8A and 8B as a level value. Levels from 1 to 10 can be set. Level 1 indicates the strongest authority and level 10 indicates the lowest authority. As will be described later, a security level is set for each user control screen, and when a logged-on user tries to display the user control screen, the user control level of the user and the security level of the user control screen to be displayed Are compared. When the User Control Level is higher than or equal to the Security Level (the level value is User Control Level ≦ Security Level), the user control screen can be displayed, otherwise it is not displayed. A new user cannot be created below a user whose level value of Scene Store / Recall Level or User Control Level is the lowest level value 10. That is, when the user is to be edited, the Add User button 906 is displayed “grayed out”. As described above, since the level that can be set for each user is limited to a level lower than the user immediately above, the number of users that can be created from the user in the lower direction by the lower value of the two level values. Is limited.

  The setting of each check box 951 has priority over the setting of each security level setting unit 952. For example, no matter how the User Control Level is set, if the View Component Editor check box is cleared, there is no authority to display the control screen.

  When a setting is made to turn off (invalidate authority) any of the check boxes 951 of a certain user, if the check box is turned on for the user under the user, it is automatically turned off And In addition, when a setting is made to lower any security level of each security level setting unit 952 of a certain user to a predetermined value, if the security level is equal to or higher than the predetermined value for a user immediately below that user, It is assumed that the level is automatically lowered to one level below the predetermined value. Further, when another user is directly under the user immediately below, similarly, the level value of the other user is limited to be lower than the level value of the user immediately below. In this way, in the hierarchical structure of users, a rule is established that each user has authority below the user immediately above and authority above the user immediately below. In this hierarchical structure, by performing an operation for restricting the authority of a certain user, it is possible to restrict the authority of all users under the user at the same time.

  FIG. 12 shows a screen example of a scene memory manager dialog 1200. This dialog 1200 is used to edit the contents of the scene memory described with reference to FIG. The dialog 1200 can be called by a predetermined operation on the PC 130.

  The scene memory view 1201 displays the contents of the scene memory. One line corresponds to one scene, and up to 999 scenes can be registered. By selecting a row (the selected row is highlighted like 1211), the scene to be operated is selected. The “Scene No.” column is the scene number, the “Name” column is the scene name (“No Data” if not), the “Config” column is the config number, the “Owner ID” column is the user ID of the owner of the group to which the scene belongs ( The Edit Security column displays the security level of the scene editing (and store) function, and the Recall Security column displays the security level of the scene recall function. Items other than Scene No. can be edited in the selected scene. However, Edit Security and Recall Security cannot be set higher than the logged-in user's Scene Store / Recall Level. In addition, the logged-on user cannot edit a scene that is not a scene of the group to which the logged-on user belongs or a scene having Edit Security higher than the logged-on user's Scene Store / Recall Level. For example, since the Edit Security of the scene 1211 is 3, the scene 1211 can be edited only when the logged-in user's Scene Store / Recall Level is 1 to 3. In this case, the Edit Security and the Recall Security are the logged-in user's Scene. It can be changed in the range from the Store / Recall Level value to 10.

  The preset view 1203 displays a list of preset numbers included in the current configuration. The preset number stored in the selected scene has the radio button in front of the preset number turned on. If the logged-on user has the right to edit the scene, the preset of the scene can be changed by clicking this radio button. In the preset view 1203, a preset can be deleted. However, you cannot delete a preset that you are using. Also, it is not possible to delete all presets, and there is always one. Although the configuration number and the preset number are used here, the configuration name and the preset name may be specified for easy understanding by the user.

  Reference numeral 1205 denotes buttons such as Cut, Copy, Paste, Insert, and Clear for editing a scene, and buttons such as Rename, Delete, Store, and New for editing a preset. When the Store button 1206 is clicked, the current configuration and the current current scene are stored in the selected scene. When the Recall button 1207 is clicked, the selected scene is read as the current configuration and the current current scene.

  Note that the current scene described with reference to FIG. 3B includes storage areas for Name, Owner ID, Edit Security, and Recall Security. When a scene is recalled, the Name of the scene is stored in these storage areas. Shall. When the current scene is stored as any scene number, the name of the storage area is written as the name of the scene number. When the current scene is initialized, there is no name etc., so when storing, Name is appropriately assigned according to the predetermined rule, owner ID is the user ID of the owner of the group to which the logged-on user belongs, Edit Security and Recall Security are logged on The user's Scene Store / Recall Level value shall be set. Further, when storing / recalling a scene, as described in the security level setting unit 952 in FIG. 9, it is checked whether the logged-on user has the authority to perform the store / recall.

  FIG. 13 shows a screen example of a user control screen management (User Control Manager) dialog 1300. With this dialog 1300, the security of the user control screen described with reference to FIGS. 8A and 8B is edited. The dialog 1300 can be called by a predetermined operation on the PC 130. The User Control view 1301 displays a list of user control screen names (User Control), owner IDs, and security levels. If it is not the user control screen of the group to which the logged-on user belongs, or if it is a user control screen that has a higher Security Level (User Control Level> Security Level in terms of value) than the User Control Level of the logged-on user, that user control Cannot edit screen security. This dialog 1300 allows the user control screen name to be changed, newly created (by the New button 1302), deleted (by the Delete button 1303), the owner ID setting change, and the Security Level change. However, the Security Level can be changed within the range from the value of User Control Level of the logged-on user to 10. The OK button 1304 enables the operation in the dialog 1300 and ends, and the cancel button 1305 cancels the operation and ends.

  When new creation is instructed by the New button 1302, a new user control screen in which no operation element or display element is arranged is opened in the edit mode, and the logged-on user starts editing the user control screen from there. be able to. At that time, the owner ID of the user control screen is initially set to the user ID of the owner of the group to which the logon user belongs, and the Security Level is initially set to the user control level of the logon user. Further, by selecting the name of the user control screen displayed in the User Control view and performing a predetermined operation, the user screen can be opened in the edit mode. Of course, when editing the user control screen, it is checked that the logged-on user has the authority, that is, that the Edit and View Component Editor check boxes are on and the user control level is higher than the security level of the user control screen.

  Here, the owner ID displayed in FIGS. 12 and 13 will be described in detail. The owner ID of each scene in FIG. 12 indicates that the scene is shared by the group of the owner ID. Similarly, the owner ID of the User Control view 1301 in FIG. 13 indicates that the user control screen is shared by the group of the owner ID. Sharing means that all users belonging to the group are given the basic authority to use and edit the scene and user control screen (however, the security level of each user is checked). A user belonging to a certain group cannot use / edit scenes and user control screens shared by other groups to which the user does not belong. For example, in the hierarchical structure of the User List view 404 in FIG. 9, when the logged-on user is Supervisor A, a scene whose owner ID is Supervisor B cannot be edited or stored / recalled. On the other hand, a user higher than the group owner can freely use and edit scenes and user control screens owned by the subordinate users or groups. For example, you can use and edit scenes and user control screens shared by groups owned by subordinate owners, but use and edit scenes and user control screens shared by groups owned by non-subordinate owners. I can't do it. In addition, a scene created by a user higher than the owner of the group has the owner ID as the user ID of the user, and if it is not changed, the scene becomes a scene that can be used by all users under the user. For example, a scene created by an Administrator can be used by all users who log on to the control program. However, even if the owner ID is confirmed to be authorized, in the case of a scene, the logged-on user uses the scene by comparing the scene store / recall level of the logged-on user with the Edit Security and Recall Security of the scene. It is necessary to have authority, and in the case of the user control screen, the logon user is authorized to use the user control screen by comparing the user control level of the logged-on user with the security level of the user control screen. It is necessary to have. In other words, the owner ID check and the security level (Scene Store / Recall Level or User Control Level) check cannot be instructed unless both are authorized. If it is recognized that no user authority is found in either check, the operation instructed by the logon user cannot be performed.

  In the user authority setting based on the owner ID described above, the authority to use the scene and the user control screen can be controlled in units of groups. What can be set as the owner ID is the user ID of the owner of any group or the user ID of a user who does not belong to any group. In a scene created by a user of a certain group, the owner ID of the group is automatically set so that it cannot be used by a user of another group. When it is desired to share the scene among a plurality of groups, the owner ID of the scene may be set to the user ID of a user who is higher than any of the owners of the group. The user higher than the owner of each group can change the owner ID only when the user ID of the user or the user under the user ID is set as the owner ID of the scene or the user control screen. However, only the user ID of the user higher than the own user ID or the subordinate group owner can be set at that time. On the other hand, in the setting of user authority based on the security level, the security level set on the scene or user control screen is compared with the user level set for each user. Control screen usage authority can be controlled. Either one of these two checks is effective, and the user authority can be set more finely by using both in combination.

  Next, a case where a supplier provides a C component and a user control screen will be described in detail. If the end user can freely use these data provided by the vendor, there is no need to protect them. On the other hand, the signal processing configuration of the C component provided by the supplier, the types of parameters for controlling the C component, the parameter values set for each parameter, etc. each include know-how unique to that supplier. In some cases, the user does not want to show the configuration or parameters to the user or does not want to change the set parameter value. Further, even if the user restricts the configuration and parameters of the C component from being visible to the user, when the contractor goes to the mixer installation location and performs the adjustment, only the contractor configures the configuration of the C component. There is a request to set the authority so that it can edit parameters.

  In order to respond to such a request, in this system, when a C component provided by a vendor or a user control screen includes the user ID and password of the vendor and an attempt is made to open the C component configuration screen for that C component. Or, when trying to open the user control screen, it is checked that the logged-on user is logged on with the trader user ID and password included in the C component or user control screen. The trader user who has logged on with the trader user ID and password can open the C component configuration screen including the trader user ID and password and edit the configuration of the C component, or the trader user ID and password can be edited. It is possible to change the value of the corresponding parameter item by opening the user control screen including the control screen. On the other hand, a user who logs on with a user other than the vendor user ID and password, regardless of the security settings of that user (even the Administrator), the C component configuration screen or user including the vendor user ID and password The control screen cannot be opened. Such a function will be described in more detail with reference to FIG.

  Various processes included in the mixer control program 131 executed by the PC 130 are shown in FIGS. FIG. 14A shows a processing procedure when the mixer control program 131 is activated. In step 1401, the initial setting file is read into the RAM 103 and various initial settings are made. In step 1402, the user logon screen shown in FIG. When the user name and password are input in step 1403 and the OK button is clicked, in step 1404 they are checked based on the user account data included in the initial setting file, and the user of that user name is authenticated. If so, the process proceeds to step 1405. If the user name or password is incorrect, the process returns to step 1403. In step 1405, the user authority (authority set in FIG. 9) corresponding to the user name is given, and in step 1406, the basic screen of FIG. 5B is displayed. The configuration data read at this time is the configuration data read when the mixer control program 131 was last activated. Thereafter, the operation shifts to the normal operation of the mixer control program 131. If the Enable Auto Log On check box 901 in FIG. 9 is turned on, steps 1402 to 1404 are skipped and the user is automatically logged on with the user name specified in the Auto Log On user combo box 902. In FIG. 14A, the process is omitted.

  FIG. 14B shows a processing procedure when security setting is selected from the menu on the basic screen. In step 1411, the security setting dialog 900 described with reference to FIG. 9 is displayed. In step 1412, a tree representing a hierarchy is displayed in the User List view 903 based on the user account data on the RAM, and the logged-on user (self) on the tree is selected as an initial state. In step 1413, various buttons and check boxes are displayed in a display mode (FIG. 10) according to the selected user.

  FIG. 14C shows a processing procedure executed when the current configuration is switched by switching scenes or the like. This process can be executed only when the Change Configuration check box of the logged-on user is turned on. A configuration data file was read not only when a scene recall operation with CF data different from the current configuration was performed, or when CF data selection operation different from the current configuration was performed, but also during logon. At this time, default CF data (for example, the CF data last selected in the configuration data) is selected, and this processing is executed. In step 1421, various controls are initialized according to the CF data newly set as the current configuration. That is, the data structure of the current scene is changed to the data structure based on the CAD data for PC of the CF data, and the preset that was last selected when the CF data was the current configuration is the current scene. Is read. In step 1422, a basic screen (FIG. 5B) showing the entire mixer configuration of the current configuration is displayed. If the online mode is selected at step 1423, an event for instructing the engine 100 to change the CF data is sent to the engine 100 at step 1424. In step 1425, it is determined whether Startup User Control of the logged-on user is on. If it is on, all user control screens below the security level of the user are opened in step 1426, and this process is terminated. In step 1426, the user control screen is opened when various checks are performed in the processing of FIG.

  FIG. 15A shows a processing procedure when an instruction to open the C component configuration screen (FIG. 7) is given. After initial setting in step 1501, whether or not the user name and password at logon in step 1502 match the vendor user ID and password (FIG. 2B) described in the CC header of the C component to be opened now Judge whether or not. If they are different, it means that a user other than the merchant is trying to open the C component configuration screen provided by the merchant. When the user name and password match (including the case where the merchant user ID and password in the CC header of the C component are blank), in step 1503, the user authority is checked. This check confirms that the View DSP Design Window check box is checked in the operation security of the logged-on user. If there is no user authority, the process ends. If there is user authority, in step 1504, the designated C component configuration screen is displayed, and the operation moves to that screen. For example, if the Edit check box for the logged-on user is turned on, the configuration of the C component displayed on the screen can be edited. If the View Component Editor check box for the logged-on user is turned on, By selecting a P component on the screen and performing an “open control screen” operation, the control screen for the selected P component can be opened.

  FIG. 15B shows a processing procedure when an instruction to open the user control screen (FIG. 8) is given. After the initial setting in step 1511, it is determined in step 1512 whether or not the user name and password at the time of logon match the vendor user ID and password described in the UC data of the user control screen to be opened now. If they are different, the process ends. If they match (including the case where the supplier user ID and password in the data of the user control screen are blank), in step 1513, whether the logged-on user belongs to the group indicated by the owner ID (FIG. 13) of the user control screen. judge. Here, it is assumed that not only a user of the group indicated by the owner ID but also a user higher than the user indicated by the owner ID belongs to the group. If the user does not belong, the logged-on user does not have the authority to use the user control screen, and thus the process ends. If the logged-on user belongs to the group, the user authority is checked in step 1514. This check verifies that the View Component Editor check box is checked in Operation Security for the logged-on user, and that the User Control Level for the logged-on user is higher than or equal to the Security Level of the user control screen. Is. If there is no user authority, the process ends. If there is user authority, in step 1515, the designated user control screen is displayed in the normal mode, and the operation moves to that screen. For example, if the Control Component Editor check box of the logged-on user is turned on, the value of the parameter corresponding to the control in the current scene can be changed by operating the control on the screen. If the Edit check box of the logged-on user is turned on, the user control screen can be switched to the edit mode and edited by selecting “edit mode” in the right-click menu.

  Through the above-described steps 1502 and 1512, the C component and the user control screen provided by the vendor can be opened only by the vendor, and the end user and other vendors (even the Administrator) cannot be opened.

  Here, the protection in the case where the supplier provides the C component and the user control screen as an additional function is illustrated, but any data included in the configuration data in FIG. 3A and the library of each component are also necessary. Accordingly, if the user ID and password are changed so that the memory is stored, it can be protected in the same manner. In particular, the present system is characterized in that when an additional function provided by a vendor is to be used, it is checked whether the ID and password assigned to the additional function match the ID and password at the time of logon. In general applications and the like, when an attempt is made to use an additional function, authentication information such as a password attached to the additional function is input to confirm the user authority. In this case, it is conceivable that a malicious user breaks the protection by trying to input authentication information many times. In this system, a person who wants to break the protection such as the C component provided by the supplier has to log on again and again, and since the operation is complicated, the protection is difficult to break.

  In the system of the present embodiment, the processing when an instruction is given from the user is basically performed by the same processing as in FIG. That is, the check in step 1502 related to the function provided by the supplier and the user authority check described in FIGS. 9 to 11 are performed, and the instructed process is performed only when both are authorized. It is a processing procedure. Further, in addition to these checks, in response to an instruction to use a function or data to check whether the logged-on user is in the owner group in step 1513, the same procedure as in FIG. Processing.

  As for the C component provided by the supplier, as described with reference to FIG. 15A, the end user cannot open the component control screen, but instead of opening the configuration screen, the user control screen is automatically displayed. You may make it open. In that case, when the supplier user ID and the password do not match in step 1502, a process for displaying a predetermined user control screen may be performed. The user control screen to be displayed is described, for example, in the column of contents of vendor protection. Further, the data provided by the vendor is installed with the Administrator authority and incorporated in the system so that the above-mentioned owner ID becomes Administrator.

  FIG. 16A shows a processing procedure when the logged-on user operates a knob displayed on the opened user control screen. In step 1601, the user authority is checked. This is to determine whether or not the Control Component Editor check box of Operation Security of the logged-on user is turned on. If there is authority, in step 1602, the value of the parameter (in the current scene) corresponding to the knob is changed according to the operation amount of the knob. If the online mode is selected at step 1603, an operation event corresponding to the operation is sent to the engine 100 at step 1604, and the process is terminated. Similar processing is performed not only for the knob operation but also for other parameter changes.

  FIG. 16B shows a processing procedure when an instruction to recall the scene i (FIG. 3A) is given. In step 1611, it is determined whether the logon user belongs to the group indicated by the owner ID of the scene i. As in step 1513, not only the user in the group indicated by the owner ID but also the user above the user indicated by the owner ID is determined to belong to the group. If so, it is determined in step 1612 whether the logged-on user has the authority to recall the scene. This compares the logon user's Operation Security Scene Store / Recall Level with the Recall Security of the scene to be recalled, and determines whether or not the user has the right to recall. If it is authorized, it is determined in step 1613 whether the current configuration changes by recalling the scene i. If so, it is determined in step 1614 whether the logged-on user has the authority to change the configuration. This confirms whether the Change Configuration check box of Operation Security of the logged-on user is turned on. If there is authority, in step 1615 the CF data designated by the scene i is selected to be the current configuration, and the process proceeds to step 1616. If the current configuration does not change in step 1613, the process proceeds directly to step 1616. In step 1616, the preset designated by the scene i is read and set in the current scene.

  Although the scene recall process has been described here, the same applies to scene store. In the store process, when a scene is already stored in the scene number designated as the store destination, it is checked whether the logon user belongs to the group of the owner of the scene stored in the scene number.

  In the above embodiment, a user who does not belong to a certain group cannot use the scene data and user control screen of that group. In addition, for example, the same restriction can be applied to CF data. May be.

  Further, the copy source of the controls and display elements arranged on the user control screen set as the control screen of the C component supplied by the supplier is limited to the control screen of the P component that is a component of the C component. The CC data may be data included in the configuration data in FIG.

  In the above embodiment, if the user ID and the password are stored in the CC header of the CC data or the UC data of the CF data, the merchant protection is on. If not, the merchant protection is off. On / off of the merchant protection may be controlled by other data (contents of the merchant protection, etc.).

  In the above embodiment, a plurality of protections are applied to a process executed in response to a user's operation. However, when the process is not executed with protection, it is determined which protection was not executed with the user. You may make it show to.

Configuration diagram of an engine of a digital mixer according to an embodiment of the present invention Configuration diagram of various data on PC Configuration of various data on PC memory Configuration diagram of various data on the engine Diagram showing logon screen and basic screen Diagram showing the mixer configuration screen Diagram showing C component configuration screen Figure showing the user control screen Figure showing the security settings dialog The figure which shows the display mode in the security setting dialog Figure showing the Add User dialog Figure showing the scene memory management dialog Figure showing the user control screen management dialog Flow chart of the mixer control program startup process, the process when security settings are selected, and the process when switching the current configuration Flowchart diagram of processing when an instruction to open a C component configuration screen is made, processing when an instruction to open a user control screen is given, and processing when a parameter change instruction is made on the user control screen The flowchart figure of the process at the time of knob operation, and a scene recall process

Explanation of symbols

  DESCRIPTION OF SYMBOLS 100 ... Engine, 101 ... CPU, 102 ... Flash memory, 103 ... RAM, 104 ... PC I / O, 105 ... MIDI I / O, 106 ... Other I / O, 107 ... Display, 108 ... Operator, 109 ... Waveform I / O, 110... Signal processing unit (DSP group), 111. Cascade I / O, 120... System bus, 130. Personal computer (PC), 131 Mixer control program, 132.

Claims (8)

A user authority management method for managing an end user's authority to use the program or data when a program or data for realizing an additional function is incorporated into a system having an arbitrary basic function,
A step of storing authentication information used for authenticating a user having authority to use the first storage means included in the computer;
The logon confirmation means provided in the computer confirms that the logged-on user is a legitimate user by using the information input when the user logs on and the authentication information stored in the first storage means. Allowing users to log on,
A step of storing a program or data including authentication information for authenticating a user who is permitted to use or edit the program or data, wherein the second storage means included in the computer is a program or data providing the additional function;
When the logged-on user requests use / editing of the program or data, the authentication means included in the computer is included in the information input when the logged-on user logs on and the program / data requested to use / edit Authenticating whether the logged-on user is authorized to use or edit the program or data using authentication information; and
The control means provided in the computer permits the use / editing if the logged-on user is authenticated by the authentication means as a user authorized to use / edit the program or data, and otherwise uses / edits the use / editing. A user authority management method comprising a step of disabling editing at least partially. A user authority management method for managing an end user's authority to use the program or data when a program or data for realizing an additional function is incorporated into a system having an arbitrary basic function,
A step of storing authentication information used for authenticating a user having authority to use the first storage means included in the computer;
The logon confirmation means provided in the computer confirms that the logged-on user is a legitimate user by using the information input when the user logs on and the authentication information stored in the first storage means. Allowing users to log on,
The second storage means provided in the computer includes authentication information for authenticating a user who is permitted to use / edit the program or data, and protect content related to the program or data, which is the program or data providing the additional function. The process of storing programs or data,
When the logged-on user requests use / editing of the program or data, the authentication means included in the computer is included in the information input when the logged-on user logs on and the program / data requested to use / edit Authenticating whether the logged-on user is authorized to use or edit the program or data using authentication information; and
The control means included in the computer permits use / editing when the logged-on user is authenticated by the authentication means as a user who is permitted to use / edit the program or data; otherwise, the program or A method for managing user rights, comprising a step of disabling use / editing within a range corresponding to protection contents included in data. A program with a function to manage the authority of multiple users,
Computer
First storage means for storing authentication information used to authenticate a user having the authority to use;
Means for confirming that the logged-on user is a legitimate user by using information input when the user logs on and authentication information stored in the first storage means, and permitting the user to log on;
Second storage means for storing a program or data providing a predetermined function, and storing a program or data including authentication information for authenticating a user permitted to use and edit the program or data;
When the logged-on user requests use / editing of the program or data, using the information entered when the logged-on user logs on and the authentication information included in the program or data requested to use / edit, Means for authenticating whether or not the logged-on user is permitted to use / edit the program or data; and
If the logged-on user is authenticated as a user authorized to use / edit the program or data by the authenticating means, the use / edit is permitted, and if not, the use / edit is at least partially A program having a user authority management function characterized by functioning as a means for disabling. A program with a function to manage the authority of multiple users,
Computer
First storage means for storing authentication information used to authenticate a user having the authority to use;
Means for confirming that the logged-on user is a legitimate user by using information input when the user logs on and authentication information stored in the first storage means, and permitting the user to log on;
A second memory storing a program or data providing a predetermined function and including authentication information for authenticating a user who is permitted to use / edit the program or data and a protection content related to the program or data means,
When the logged-on user requests use / editing of the program or data, using the information entered when the logged-on user logs on and the authentication information included in the program or data requested to use / edit, Means for authenticating whether or not the logged-on user is permitted to use / edit the program or data; and
If the logged-on user is authenticated as a user who is permitted to use / edit the program or data by the authenticating means, the use / edit is permitted; otherwise, it is included in the program or data. A program provided with a user authority management function, characterized in that it functions as a means for disabling the use / editing within the scope according to the protection content. In the program provided with the user authority management function according to claim 3 or 4,
The program or data that provides the predetermined function is a program or data that provides an additional function to a system that realizes an arbitrary basic function. In the program provided with the user authority management function according to claim 3 or 4,
A program having a user authority management function, wherein the user authentication information stored in the first storage means and the second storage means is an identifier and a password for identifying a user. In the program provided with the user authority management function according to claim 4,
When the authentication information column of the program or data stored in the second storage means is blank, the protection content included in the program or data is referred to, and when the protection content is blank, the use / A program having a user authority management function, wherein editing is permitted, and when the protected content is not blank, the use / editing is permitted within a range corresponding to the protected content. In the program provided with the user authority management function according to any one of claims 3 to 7,
The program is a mixer engine that realizes a mixer configuration display / editing function that defines an audio signal mixing process executed by the signal processing apparatus, and a control function that controls the audio signal mixing process executed by the signal processing apparatus. A program having a user authority management function characterized by being a control program.

Images