JP5157543B2 - An acoustic system and a program comprising a network in which a plurality of audio devices and at least one control device for controlling the plurality of audio devices are connected - Google Patents

Description

  The present invention relates to a sound system including a network in which an audio device and a control device for controlling the audio device are connected, and relates to a technique for controlling and monitoring (monitoring) the audio device from the control device. .

  An acoustic system generally referred to as a PA system ("PA" is an abbreviation for Public Address) or an SR system ("SR" is an abbreviation for Sound Reinforcement) is basically an audio mixing device (mixer). In this system, an acoustic signal supplied from an acoustic signal supply source such as the above is sent to a power amplifier device, and a speaker is driven by an acoustic signal obtained by amplifying power by the power amplifier device. For example, large-scale sound systems are installed in large-area buildings such as music performance venues, theaters, and various halls. Since a large-scale sound system has a plurality of power amplifier devices, its control and management are complicated.

Conventionally known power amplifier apparatuses are connected to an Ethernet (registered trademark) standard network and can be remotely controlled from a control apparatus connected via the network. The control device includes, for example, a personal computer (PC) on which a dedicated application program (“remote control software”) for remotely controlling the power amplifier device is mounted. Various data for the PC to perform the remote control are stored in the memory of the PC as one project file. The remote control software opens one project file when starting the software, and performs remote control of the power amplifier device based on various data stored in the project file. By executing the remote control software, the user can remotely control the operation of one or more power amplifier devices on the network or monitor the operation status of the one or more power amplifier devices on one PC. (See, for example, Non-Patent Document 1 below).
http://www2.yamaha.co.jp/manual/pdf/pa/japan/amp/acu16c_en_om.pdf (Instruction manual for product name “NetworkAmp Manager”)

  By the way, when a plurality of PCs are connected to a network, remote control software is started on each of the plurality of PCs, and each of the plurality of PCs intends to control or monitor a power amplifier device on the network, In the technology, one power amplifier device can be controlled or monitored by only one PC that is first brought online (controllable or monitored), and other PCs The power amplifier device could not be controlled or monitored from the remote control software.

  In this regard, when the remote control software of a certain PC is controlling the power amplifier device, the parameter setting state and operation of the controlled power amplifier device using another remote control software of the PC There has been a demand for monitoring data such as the situation.

  However, in order to realize the above-mentioned demand to monitor a power amplifier device being controlled by a remote control software of a PC using a remote control software of another PC, the power amplifier device is connected to the network from the other PC that performs monitoring. It is not desirable to allow unlimited monitoring of any power amplifier device. Specifically, it is desirable that only the devices registered as control or monitoring targets can be monitored in the project file opened on each of the PC that performs control and the PC that performs monitoring. That is, for example, a power amplifier device newly added to the project file of the PC that performs control or a power amplifier device deleted from the project file of the PC that performs control cannot be monitored from the PC that performs monitoring. In other words, it is desirable to be able to limit the range of power amplifier devices that can be monitored from another PC.

  Also, when controlling a plurality of power amplifier devices, it would be convenient if the plurality of power amplifier devices could be managed in several groups by remote control software (PC). As described above, when a plurality of power amplifier devices are managed by being divided into several groups, it is desirable that the PC that monitors the plurality of power amplifier devices can also check the grouping state. However, even in such a case, it is desirable that the range of the power amplifier device that can be monitored from another PC can be limited as described above.

The present invention has been made in view of the above points, and in an acoustic system constituted by a network in which a plurality of acoustic devices and at least one control device for controlling the plurality of acoustic devices are connected. Provided is an acoustic system and a program that can display the same grouping state and other display modes of acoustic devices in a control device that remotely controls the system on a control device that monitors (monitors) the system. For the purpose.

The present invention is an acoustic system configured by a network in which a plurality of acoustic devices and at least one control device for controlling the plurality of acoustic devices are connected, the control device comprising: display means; Virtual device information including operation data for controlling each acoustic device corresponding to each of the plurality of acoustic devices, a virtual device ID for specifying virtual device information, and group information indicating a group to which the virtual device information belongs Based on the group information stored in the first storage means, a plurality of virtual device information divided into groups to which the virtual device information belongs and displayed on the display means, and the virtual device information the operation data contained and a display control means for performing a control to display on said display means, said plurality of acoustic devices, it Is provided with an acoustic device ID for identifying the audio devices, response and group information indicating the group to which the virtual device information belongs to, a second storage means for storing the operation data for controlling the operation of the acoustic apparatus The control device further receives the acoustic device ID stored in the second storage unit from each of the plurality of acoustic devices, and receives the received acoustic device ID and the virtual device ID stored in the first storage unit. The virtual device information stored in the first storage unit when the virtual device information and the acoustic device associated with the virtual device information are to be set as remote control targets. The first synchronization control means for writing the group information to the second storage means of the corresponding audio equipment, and the first synchronization control means For audio equipment set in the preparative controlled object, by changing the operating data of the virtual device information stored in the first storage unit, the remote control operation data stored in the second storage means of the corresponding acoustic equipment and remote control means for changing, when it should set the audio equipment associated with the virtual device information to monitored, receives the group information stored in the second storage means of sound equipment monitored, the received group Second synchronization means for controlling the display control means to update the grouping of the virtual device information in the display means by updating the group information in the first storage means based on the information; and the second synchronization Operation data stored in the second storage means in the acoustic device for the acoustic device set as a monitoring target by the converting means And a monitor control means for changing the operation data of the corresponding virtual device information stored in the first storage means in the same manner as that.

The control device associates the virtual device information with the acoustic device by the association unit based on the acoustic device ID received from each of the plurality of acoustic devices and the virtual device ID stored in the first storage unit. When a certain control device sets the associated audio device as a remote control target, the group information of the virtual device information stored in the first storage unit by the first synchronization control unit is set to the second information of the corresponding audio device. Write to storage means. The operation data of the audio equipment set as the remote control target is remotely controlled by the certain control device. When monitoring the acoustic device from another control device, the group information stored in the second storage unit of the acoustic device is received, and the group information in the first storage unit is updated based on the received group information. The grouping of the virtual device information on the display means is updated. Thereby, the grouping of the virtual device information in the control device that monitors the acoustic device is made the same as the grouping of the corresponding virtual device information in the control device that remotely controls the acoustic device.

Further, in the acoustic system of the present invention, the remote control means provided in the control device is linked to the change of the operation data of one virtual device information stored in the first storage means, and is in the same group as the virtual device information. The operation data of other virtual devices belonging to the virtual device information is changed, and the virtual device information and the operation data stored in the second storage means of the plurality of audio devices corresponding to the other virtual devices belonging to the same group are changed by remote control. Control is performed.

According to this, linked to the change of the operating data of one virtual device information in a certain control device, it can change the operation data of other virtual devices belonging to the same group as the virtual device information, sound the controller When the device is remotely controlled, the virtual device information and operation data of a plurality of acoustic devices corresponding to other virtual devices belonging to the same group can be remotely controlled simultaneously.

Further, in the acoustic system according to the present invention, before Symbol controller, said first storage means stores the display control information for controlling the display form when displaying virtual device information to said display means, said display control Means controls the display in a display mode based on the display control information stored in the first storage means, and the first synchronization means controls the display of the virtual device information stored in the first storage means. The information is written in the second storage means of the corresponding audio equipment, and the second synchronization means receives the display control information stored in the second storage means of the audio equipment to be monitored, and the received display control information Based on this, by updating the display control information of the virtual device information stored in the first storage means, the display mode of the virtual device in the display means is updated to the display control means Performs control to, the plurality of acoustic devices, respectively, to said second storage means and that you store display control information of the virtual device information the corresponding.

When a certain control device sets an audio device as a remote control target, the display control information of the virtual device information stored in the first storage unit by the first synchronization control unit is stored in the second storage unit of the corresponding audio device. Write. When monitoring the acoustic device from another control device, by receiving the display control information stored in the second storage unit of the acoustic device, and updating the group information of the first storage unit based on the received, The grouping display mode of the virtual device information in the display means is updated. Thereby, the grouping display of virtual device information and the display of operation data in the control device that monitors the acoustic device are made the same as the display mode of the corresponding virtual device information in the control device that remotely controls the acoustic device.

Further, in the acoustic system according to the present invention, before Symbol controller in the first storage means stores one or more areas information indicating one or a plurality of areas, stored in said first storage means Registration means for registering virtual device information in one area of one or more areas indicated by one or more area information, wherein the associating means includes the received acoustic device ID , the virtual device ID, and based on the area information, it associates the virtual device information and audio equipment, further wherein the acoustic equipment not get even correspondence with any of the virtual device information by associating means, creates a new corresponding virtual device information, Second display control means for displaying the created virtual device as virtual device information outside area registration on the display means; Features.

Control apparatus, the associating means, and audio equipment I D received from each of the plurality of audio devices, based on the bar Charu device ID and the area information, associates the virtual device information and audio equipment. For audio equipment could not get even correspondence between the virtual device information of displacement have, by the second display control means, the virtual device information corresponding to the audio equipment newly created, the display means a virtual device to which the creation Is displayed as virtual device information outside the area registration.

According to this invention, the audio device associated with the virtual device information can be monitored from a control device different from the control device that remotely controls the audio device. Since the grouping of the virtual device information in the control device that monitors the acoustic device can be made the same as the grouping of the corresponding virtual device information in the control device that remotely controls the acoustic device, As a result, it is possible to check not only the operation data of the audio device to be monitored but also the grouped state. In addition, the control device that remotely controls the acoustic device can simultaneously remotely control a plurality of other acoustic devices to which the acoustic device belongs. At this time, each acoustic device has group information, which is used for monitoring by the control device, and it is not necessary to perform a complicated operation for remote control received collectively in units of groups.

Further, according to the present invention, the display mode of the virtual device information in the control device that monitors the acoustic device can be made the same as the display mode of the corresponding virtual device information in the control device that remotely controls the acoustic device. In the control apparatus to monitor, there exists the outstanding effect that not only the operation data of the audio equipment to be monitored but also the display mode can be confirmed. Here, the display mode is not limited to the grouping state, but may be any icon shape, display font, or font that can be set by the user using the control device. Further, according to the present invention , the virtual device information and the acoustic device are associated with each other based on the acoustic device ID received from each of the plurality of acoustic devices , the virtual device ID, and the area information. Since it is displayed as virtual device information outside the area registration , when a certain virtual device is moved to another area or deleted from the area in the control device that performs remote control, the control to be monitored is The virtual device cannot be displayed, that is, the range that can be monitored from another control device can be limited.

  Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings. In this embodiment, an example in which the present invention is applied to an acoustic system including a power amplifier device and a personal computer for remotely controlling the power amplifier device will be described. The acoustic system is generally called a PA system or SR system, and is assumed to be a large-scale acoustic system installed in a large-scale building such as a music performance venue, a theater, or various halls. doing.

  FIG. 1 is a block diagram showing a module configuration example of an acoustic system according to an embodiment of the present invention. The acoustic system shown in FIG. 1 includes a plurality of power amplifier devices (hereinafter simply “amplifiers”) 1 and a plurality of personal computers (PCs) 2. The plurality of amplifiers 1 and the plurality of PCs 2 are physically connected using a general-purpose network cable such as an Ethernet (registered trademark) cable to form a local area network (LAN). Normal data communication according to the TCP / IP protocol is possible between devices on the network, but audio signals may be transmitted in real time using the same network. In that case, an appropriate data transmission format conventionally known, such as CobraNet (registered trademark), may be applied as the data transmission format.

  The amplifier 1 is an acoustic device that performs acoustic signal processing including power amplification on an externally input acoustic signal and outputs the processed acoustic signal to a speaker (not shown). In the acoustic system according to the present embodiment, a model that can be connected to the network and can be controlled by the control device (PC2) connected via the network is applied as the amplifier 1. In this embodiment, the casing of the amplifier 1 is assumed to be a so-called rack mount type that can be mounted on a dedicated shelf (rack). Mounting a plurality of amplifiers 1 on a rack is advantageous when transporting or installing a group of amplifiers. For this reason, for example, when an audio equipment rental company lends a plurality of rack-mounted power amplifier devices to a borrower, the plurality of amplifiers are often rented in a state of being mounted on a rack.

  The PC 2 is a general-purpose personal computer on which an operating system such as “Windows (trademark)” is installed, for example. It is called control software. The remote control software is an application program that operates on the operating system of the PC 2. By executing the remote control software, the PC 2 functions as a control device that controls the amplifier 1 connected via the network. That is, the user operating the PC 2 can control the operation of the plurality of amplifiers 1 on the network and monitor the operation status of the plurality of amplifiers 1 by using the function provided by the remote control software. . In FIG. 1, a plurality of PCs 2 exist on the network, and remote control software is activated on each of the plurality of PCs 2.

  The remote control of the amplifier 1 by the remote control software is performed in units of “area” as will be described in detail later. One or a plurality of amplifiers 1 can be registered in the “area”, and one or a plurality of amplifiers 1 registered in the area are controlled in the area. In FIG. 1, a range corresponding to “area” is surrounded by a dotted line. “Area 1” indicated by reference numeral 3A includes two amplifiers 1 and one PC 2. "Area 2" indicated by reference numeral 3B includes two amplifiers 1 and two PCs 2. There may also be an amplifier 1 that is not registered in the area on the network. The amplifier 1 that is not registered in the area cannot be controlled by the remote control software of the PC 2 recognized (detected) by the matching process described later.

  In addition to the amplifier 1 and the PC 2, the acoustic system shown in FIG. 1 includes a dedicated interface device (ACD) for connecting the amplifier 1 having no network I / O to the network. However, the illustration and description thereof are omitted here for the sake of convenience. It is a conventionally known technique to connect the power amplifier device to a remote control network via a dedicated interface device. In addition, audio equipment other than amplifiers, such as digital mixers, recorders, effectors, A / D converters, D / A converters, or synthesizers, are connected to the network, and the PC2 remote control software is used together with the amplifiers. May also be controlled collectively.

  FIG. 2 is a block diagram for explaining the outline of the hardware configuration of the amplifier 1 shown in FIG. The amplifier 1 includes a control unit including a CPU 10 and a memory 11 including a ROM and a RAM, an audio I / O (D / A, A / D) 12 including a DA converter and an AD converter, and a signal processing unit ( DSP) 13, a power amplifier (AMP) 14, a user interface (UI) 15 such as an operator or a display, and a network communication interface (communication I / F) 16, each of which has a data and communication bus 10B. Connected through. The communication I / F 16 is a network interface conforming to the Ethernet (registered trademark) standard. The amplifier 1 is connected to a network via the communication I / F 16 and performs various data communication with the PC 2 connected via the network. The amplifier 1 also has a user interface 15 such as a physical operation element such as a volume level adjustment knob, an area ID (to be described later) in the memory 11 of the amplifier 1 and an operation element for setting the area ID, or the operation of the amplifier 1. An operation panel including various indicators indicating the status is provided. In FIG. 2, a connection line between the external source or sink and the audio I / O 12, and a connection line between the power amplifier 14 and the external speaker are omitted.

  The CPU 10 executes a control program stored in the memory (ROM or RAM) 11 and controls the operation of the amplifier 1. The memory 11 stores various control programs executed by the CPU 10 and various data (see FIG. 6 described later) such as operation data used for acoustic signal processing performed by the amplifier 1 (operation of the DSP 13 and the power amplifier 14). Is done.

  The audio I / O 12 includes a plurality of predetermined sound signal input terminals. The amplifier 1 receives the predetermined plurality of analog waveform signals or digital waveform data from an external source (not shown) via the audio I / O 12. At this time, the analog waveform signal is converted into digital waveform data by the AD converter. A plurality of sound signals input from the outside are supplied to the DSP 13.

  The DSP 13 includes an acoustic signal processing channel corresponding to each of the predetermined plural systems of acoustic signal input terminals, and performs acoustic signal processing based on instructions from the CPU 10 on the digital waveform data input to each channel for each channel. To do. The acoustic signal processing performed by the DSP 13 is, for example, crossover processing, delay processing, equalizer processing, limiter processing, howling suppression processing, or the like. The acoustic signal processing is processing for adjusting the characteristics of the acoustic signal and protecting the power amplification unit 14 and the speaker, and the content thereof is controlled by operation data stored in the memory 11.

  The output signal of the DSP 13 is converted into an analog waveform signal for each channel by a DA converter (not shown) in the input section in the power amplification section 14 and supplied to a power amplification circuit (not shown) in the power amplification section 14. The The power amplification circuit amplifies the output signal of the DSP 13 converted into the analog waveform signal for each channel. The amplified analog waveform signal is output to an external speaker (not shown) through a plurality of predetermined acoustic signal output terminals provided in the power amplifier 14, and the speaker is driven by the output analog waveform signal. Is done. Basically, one audio signal output terminal is connected to one speaker. The power amplifying unit 14 also includes data indicating the operating state of the power amplifying unit 14 (for example, output stage temperature, input and output signal levels, power supply voltage, output voltage, output current, load impedance, protection status, etc. ) To the DSP 13. The data indicating the operation state is used in the DSP 13 for signal processing for protecting the power amplifying unit 14 and the speaker.

  In addition, although the example of a structure of the amplifier 1 provided with DSP13 was shown in FIG. 2, the amplifier 1 is a model (model in which the power amplifier 14 directly inputs / outputs an analog signal) without the audio I / O 12 and the DSP 13. In addition, any model that can be connected to the control device (PC2) via the network and can receive remote control from the control device can be applied to the acoustic system of the present invention.

  FIG. 3 is a block diagram illustrating a hardware configuration example of the PC 2. As described above, the PC 2 is a general-purpose personal computer, and includes a CPU 20, a memory 21 including a ROM and a RAM, a hard disk drive (HDD) 22, a network communication interface (communication I / F) 23, a display, and a mouse operation. And a user interface 24 including a child and a keyboard. Remote control software for remotely controlling the amplifier 1 may be stored in the HDD 22. The remote control software is read from the HDD 22 into the memory 21 when the remote control software is to be executed. When the CPU 20 executes the remote control software read into the memory 21, the PC 2 functions as a control device for remotely controlling the amplifier group 1 on the network.

  FIG. 4 is a diagram illustrating a configuration example of data prepared by the remote control software in the memory 21 and the HDD 22 of the PC 2. As shown in FIG. 4, the data is managed in a hierarchical structure, and this hierarchical structure corresponds to the management structure of the acoustic system by the remote control software.

  The hierarchy indicated by reference numeral 30 includes controller ID, project library, and current project data. The controller ID is, for example, on the network such as the MAC address (Media Access Control address) of the PC 2, the IP address of the PC 2, ID information for specifying the remote control software installed in the PC 2, or information combining them. The ID information for specifying the PC 2 or the remote control software installed on the PC 2. This controller ID is stored in a memory (RAM) 21, for example.

  The project library stores a plurality of project files (in the figure, “project file 1”, “project file 2”...) As indicated by reference numeral 31. The project library storage area may be provided in the HDD 22, for example. One project file stores various data necessary to control a group of amplifiers connected to the network. A group of data stored in one project file constitutes one project. The current project is a storage area for storing a data group of one project file currently launched in the remote control software, and is prepared in, for example, the memory (RAM) 21. When the remote control software is executed, one project file is loaded from the project library to the current project. The project stored in the project file loaded in the current project is the project to be controlled by the remote control software (current project).

  One project file includes a project ID, user information, a project name, and a plurality of area information 33 as indicated by reference numeral 32. The project ID is ID information for specifying one project from a plurality of project files in the project library. Each project file in the project library has a different project ID. The project name data is data of a name given to the project, and is used when, for example, displaying the project name on a basic screen described later. Each project file in the project library has a different project name. The name of the project file may be automatically created by the remote control software, or the user may set an arbitrary name.

  The user information of one project file stores one or a plurality of account information 34 corresponding to each user who has created an account for logging in to the project. That is, the account information 34 is created for each project file. Only a user who has account information 34 in the project file can open the project file and use it. One account information 34 includes a user ID and authentication information. The user ID is ID information for specifying one user among a plurality of users. The authentication information is, for example, a password associated with the user ID.

  In one project file, area information 33 (“area information 1”, “area information 2” in FIG. 4) corresponding to each “area” created in the project is stored. As described above, the “area” is a unit of remote control within one project. Each area information stores various data used for remote control of each area.

  One area information 33 includes an area ID 46, an area name, “RackTree” information, “Feed Structure Tree” information, and “User Defined Tree” information group information 36, user role information 35, and “OnLine” of the area. Information indicating the status and device information (“device information 1”, “device information 2”... In the figure) 37 corresponding to each of one or a plurality of amplifiers registered in the area are included. When the interface device that connects the amplifier to the network is included in the area, device information corresponding to the interface device may also be included in the area information 33.

  The area ID 46 is ID information for specifying one area from a plurality of areas created in one project. Each area in one project has a different area ID 46. The area name is a name given to this area, and is used when, for example, the area name of the area is displayed on a basic screen described later. Each area in a project has a different area name. The name of the area may be created automatically by the remote control software, or the user may set an arbitrary area name.

  The user role information 35 is information that defines the authority (user role) given in the area to each user who has account information 34 in the project. “User role” is information representing the authority given to each user who has an account in the area. There are five types of user roles: “Admin”, “Power User”, “User”, “Guest”, and “External”, listed in order from the higher authority. “Admin” has project editing authority, area editing authority, amplifier control authority and viewing authority in the area. The “power user” has the authority to edit the area, the authority to control the amplifier in the area, and the authority to browse the amplifier in the area. The “user” has the authority to control the amplifier in the area and the authority to browse the amplifier in the area. “Guest” has authority to view amplifiers in the area. An “outsider” is equivalent to having no authority in the area, that is, no account in the area (the user role information 35 is not in the area).

  FIG. 5 is a diagram showing in detail the contents of the user role information 35 stored in one area information 33. The user role information 35 stored in one area information 33 includes a plurality of user role information 35 corresponding to each one of all users who have account information 34 in the project. The user role information 35 for one user includes a user ID that identifies the user and a user role given to the user corresponding to the user ID in the area (any one of the values of the five types of user roles). It consists of. The user ID included here is a user ID included in the account information 34. Accordingly, the authority of a certain user in a certain area can be specified by referring to the account information 34 (user ID) of the user and the user role information 35 corresponding to the user ID. Since the user role information 35 is set for each area, the user authority based on the user role information 35 is defined for each area. For example, even if a user has account information 34 in a project, if the user role information 35 in a certain area is insufficient in authority, the amplifier in that area cannot be controlled or monitored.

  Returning to FIG. 4, the information 36 of “RackTree”, “Feed Structure Tree”, and “User Defined Tree” is information for managing the amplifiers registered in the area in groups. “RackTree” is information describing the configuration of a group (rack tree) in which amplifiers are grouped for each rack (shelf), and “Feed Structure Tree” is a group (feed) in which amplifier channels are grouped for each speaker of the amplifier signal output destination. The information describing the structure of the (structure group), and “User Defined Tree” is information describing the structure of the group (User Defined tree) arbitrarily defined by the user. In this specification, the grouping information 36 is collectively referred to as “group information”. The group information 36 is used when, for example, the amplifiers registered in each area of the project are displayed in a tree shape for each group on the basic screen described later. The three group information 36 includes a name given to each group, information for specifying the configuration of each group (information for specifying an amplifier group registered in the group, and the position of each amplifier in the group). Specific information).

  Each piece of device information 37 corresponds to one amplifier 1 and stores information necessary for remote control of one amplifier 1 from the remote control software of the PC 2. The remote control software creates one or a plurality of device information 37 corresponding to each of one or a plurality of amplifiers registered in the area in each area information 33.

  One device information 37 includes device ID 38, model information, IP address, device name information, amplifier operation data, information 39 indicating the “OnLine” status of the device information 37, and controller ID 40 information. It is.

  The device ID 38 includes a MAC address of the actual amplifier 1 corresponding to the device information 37 and an in-area ID for specifying the device information 37 in the area. The in-area ID is data automatically generated by remote control software when the device information 37 is registered in the area (when the device information 37 is created), or the amplifier 1 corresponding to the device information 37 Data manually set by the user using the user interface 15 on the side. On the other hand, the MAC address is data fixed to the amplifier 1 and cannot be set by the remote control software or the user. The device ID 38 is, for example, data used by the remote control internal area ID and the ft when associating (matching) the device information 37 with the actual amplifier 1.

  The model information is information for specifying the model of the amplifier 1 corresponding to the device information 37 and is, for example, the model name or model ID of the amplifier 1 (ID assigned to each model by the manufacturer). . The IP address is an IP address given to the amplifier 1 corresponding to the device information 37 on the network. The device name information is a name (amplifier name) given by the user to the amplifier 1 corresponding to the device information 37 in the remote control software, and when the name of the amplifier 1 is displayed on the basic screen described later, etc. Used.

  The operation data is information on setting values of various parameters necessary for remotely controlling the operation of the amplifier 1 corresponding to the device information 37. For example, the setting data of the volume level parameter for each channel of the amplifier is included. included. This operation data is data in the same format as the operation data stored in the memory 11 of the amplifier 1 corresponding to the device information 37. Model definition information for defining and editing operation data of each model is stored in a model library (not shown) provided in the remote control software. Here, the model definition information of each model includes the model name, model ID, information indicating the format of the operation data, an editing program for editing the operation data, and the like. The operation data includes various parameters and their set values such as gain parameter values for each channel, attenuator parameter values for each channel, phase switching parameter values, delay time parameter values, equalizer parameter values, etc. Is included.

  The OnLine status information 39 stores one value of “ONLINE”, “MONITOR”, and “OFFLINE”. The OnLine status information 39 indicates which of the above three states the device information 37 is for the actual amplifier 1 corresponding thereto.

  The controller ID 40 stored in the device information 37 is information for specifying the PC 2 (controlling master) controlling the amplifier 1 corresponding to the device information 37, and the PC 2 itself corresponds to the device information 37. If it is the control main of the amplifier 1 which performs, the value of controller ID (controller ID stored in the hierarchy shown with the code | symbol 30) stored in own memory 21 is written here. If the PC 2 other than itself is the main controller of the amplifier 1 corresponding to the device information 37, the controller ID of the other PC 2 is written here. The controller ID 40 in the control device 37 is data that is prepared only when the project is loaded into the current project. Specifically, the controller ID 40 is received from the amplifier 1 during a synchronization process described later. That is, when the project is stored in the project library (HDD 22), the data of the controller ID 40 is empty.

  FIG. 6 is a diagram for explaining a configuration example of data prepared in the memory 11 of the amplifier 1. As shown in FIG. 6, in the memory 11 of one amplifier 1, model information, device ID 41, IP address, operation data, controller ID 42, area ID 43, amplifier position information in “RackTree”, Amplifier position information in “Feed Structure Tree”, group information 44 of amplifier position information in “User Defined Tree”, and “User Info” information 45 are included. Each amplifier 1 on the acoustic system stores these pieces of information in its own memory 11 for its own unit. Of the stored contents of the amplifier 1, the controller ID 42, area ID 43, group information 44, and user info information 45 are data necessary for controlling or monitoring the amplifier 1 from the PC 2. Is not necessary. One of the main features of the present invention is that data for controlling or monitoring the amplifier 1 from the PC 2 such as User Info information 45 and group information 44 is stored in the memory 11 of the amplifier 1.

  The model information is information for specifying the model of the amplifier 1 and is, for example, the model name or model ID of the amplifier 1. The device ID 41 includes a MAC address and an in-area ID. The MAC address is data that the amplifier 1 has in a fixed manner and cannot be set by the user. The in-area ID is information for identifying the amplifier 1 in the area where the amplifier 1 is registered (specifically, the area where the device information 37 corresponding to the amplifier 1 is registered on the PC 2 side). Data automatically generated by the remote control software when the device information 37 corresponding to the amplifier 1 is registered in the area, or data manually set by the user using the user interface (operation panel) 15 of the amplifier 1 is there. The device ID 41 is data used by the remote control software when, for example, associating (matching) the amplifier 1 with the device information 37. The IP address is an IP address given to the amplifier 1 on the network.

  The operation data is information on setting values of various parameters necessary for remote control of the operation of the amplifier 1, for example, gain parameter values for each channel, attenuator parameter values for each channel, phase switching Various parameters such as parameter values, delay time parameter values, equalizer parameter values, and their set values are included. The CPU 10 of the amplifier 1 gives a command to the DSP 13 based on this operation data, and controls the contents of the acoustic signal processing executed by the DSP 13. Operation data on the amplifier 1 side is remotely controlled from the PC 2 side, or is controlled using the user interface 15 of the amplifier 1.

  The controller ID 42 stored in the amplifier 1 is data corresponding to the controller ID stored in the memory 21 of the control main PC 2 of the amplifier 1, and this is the control main PC 2 at the time of synchronization processing described later. Receive from. The controller ID 42 is used to determine whether or not the amplifier 1 is currently controlled by the PC 2. If the controller ID 42 has a value, the amplifier 1 is under control from the PC 2, and if the controller ID 42 does not have a value, the amplifier 1 is not under control from the PC 2. The area ID 43 is an area ID assigned to the area where the amplifier 1 is registered. By having an area ID in the memory 11 of the amplifier 1, it is possible to notify the PC 2 which area the amplifier 1 is registered in the current project. The area ID 43 is data received from the control main PC 2 of the amplifier 1 during a synchronization process described later. The area ID 43 can be manually set by the user using the user interface (operation panel) 15 of the amplifier 1.

  In addition, each amplifier position information 44 of “RackTree”, “Feed Structure Tree”, and “User Defined Tree” includes “RackTree”, “Feed Structure Tree”, and “User Defined Tree” in “User Defined Tree”. This is group information for specifying the position of the. The group information 44 held by each amplifier 1 is data based on the group information 36 stored on the PC 2 side. The group information 36 stored on the PC 2 side includes the configuration of each group created in one area (information specifying the amplifier group registered in each group) and the position information of each amplifier in each group. The group information 44 stored on the amplifier 1 side only needs to be able to specify the group in which the own device is registered and the position of the own device in each group. The group information 44 stored in the amplifier 1 is group information 36 on the PC 2 side received from the control main PC 2 of the amplifier 1 (group in the area information 33 in which the amplifier 1 is registered) during synchronization processing described later. Data set based on information 36).

  The “User info” information 45 is one or more “User info” information 39 corresponding to each of one or more users. “User info” information 45 for one user defines the user ID of the user, account information including authentication information corresponding to the user ID, and authority (user role) of the user having an account to the amplifier 1. Information. The “User info” information 45 includes user information (account information 34) in the current project received from the control main PC 2 of the amplifier 1 and area information 33 in which the amplifier 1 is registered during a synchronization process described later. It is data created based on the user role information 35 inside. That is, the “User info” information 45 is data in which the account information 34 is associated with the user role information 35 of each user in the area where the amplifier 1 is registered for each user.

  FIG. 7 is a diagram for explaining an operation screen provided by the remote control software, and shows a configuration example of a “basic screen” for performing the overall operation of the functions provided by the remote control software. When the remote control software is activated in the PC 2 and one project to be controlled is selected, the project (current project) selected as the control target is controlled and monitored on the display (user interface 24) of the PC 2. “Basic screen” is displayed.

  In the basic screen shown in FIG. 7, the tree display unit 50 is an area for displaying the configuration of the project to be controlled (current project) in a tree format based on the data in the current project. That is, in the tree display unit 50, there is a display object group corresponding to the area in the uppermost layer corresponding to the data structure of one project file, and in each area below the display object corresponding to each area. A display object group representing each of the group, amplifier, or amplifier channel to which it belongs is arranged in a branched state. On each display object, the name of the corresponding component (area name, group name, amplifier name, etc.) is displayed based on the data in the current project. In addition, when an element exists below a certain constituent element, a GUI component 51 for instructing whether to display or hide the lower element is displayed at the left end of the display object corresponding to the tree constituent element. Is done. When the lower element is displayed, a “−” mark is displayed on the GUI part 51, and when the lower element is hidden, a “+” mark is displayed on the GUI part 51.

  By the way, the configuration of the control target project displayed in the tree display unit 50 is based on the data of the current project stored in the PC 2 as described above. Accordingly, the display object representing the amplifier in the tree display unit 50 represents a virtual amplifier corresponding to the device information 37 created in the project file to be controlled. In this specification, the virtual amplifier (that is, the device information 37 stored in the PC 2) created in the project file is referred to as “virtual device” as necessary. The entity of the amplifier 1 connected to is referred to as a “real device” as necessary.

  The user selects any one of the display object groups displayed in the tree display unit 50, so that the area, group, amplifier (virtual device), or amplifier channel corresponding to the designated display object group is selected. The values of various parameters can be developed on the level display unit 52, the status display unit 53, and the attenuator operation unit 54. These regions indicated by reference numerals 52 to 54 are regions for performing main operations for remotely controlling the amplifier. An example of the detailed configuration of the area indicated by the reference numerals 52 to 54 will be described later.

  In addition to the above, the basic screen shown in FIG. 7 includes an area that is currently controlled (an area selected by the tree display unit 50, an area to which the selected group belongs, or an amplifier selected by the same). Area name display section 55 for displaying the area name of the area to which the channel of the selected amplifier belongs, or the name of the user currently logged in to the remote control software (for example, the user ID of the user). A user name display unit 56 to display, an “On-Line” button image 57 for activating the synchronization processing dialog function of the virtual device and the real device, a mute on / off switching instruction button image 58 of the currently controlled area, or A common operation panel 59 for performing operations common to the entire basic screen is included. In the common operation panel 59, for example, a GUI component for performing an instruction to read (load) a project file into the current project, an instruction to save (store) the file, an instruction to create a new file, etc. May be included. In addition to the above, on the basic screen, for example, authority ("Admin", "Power User", "User", "Guest") in the currently controlled area given to the logged-in user, A display unit for displaying other information such as the project name of the current project (shown as “other information display unit” in the figure) may be included.

  FIGS. 8A to 8C are diagrams for explaining the configuration of the tree display unit 50 in detail. The tree display portion 50 is provided with four tab images of a “Device” tab 60, a “Rack” tab 61, a “Feed Structure” tab 62, and a “User Defined” tab 63 at the upper end. The user can select the four tab images 60 to 63 and display the tree displayed on the tree display unit 50 in accordance with any one of the selected tab images 60 to 63. The form can be switched.

  When the “Device” tab 60 is selected, the project configuration is displayed on the tree display unit 50 in the “device tree” display form shown in FIG. The “device tree” is a display form for displaying, for each area, virtual devices registered in the area. In the “device tree”, devices directly connected to the network are displayed directly under any of the areas or directly under the “Unknown Device” category, and do not form a group. In FIG. 8A, an example in which “Amp3” and interface devices “ACD (1)” and “ACD (2)” for connecting the amplifier to the network are arranged immediately below “Area (1)”. Show. From the example in the figure, it can be seen that “Amp1” and “Amp2” are connected to “ACD (1)”. In this way, devices in the area other than the amplifier 1 (devices not grouped) can be displayed in the device tree. A maximum of 32 amplifiers can be connected to one interface device (ACD).

  In addition, an “Identify” button image 64 for confirming a real device corresponding to the virtual device is displayed in the “device tree” corresponding to the display object of each virtual device. The user can confirm the real device associated with the virtual device by operating the “Identify” button image 64. As an example of the confirmation method, the LED display of the real device associated with the virtual device can be turned on in response to the operation of the “Identify” button image 64. In addition, the “device tree” is provided with an ID display column 65 for displaying the in-area ID of each virtual device corresponding to the display item of each virtual device. In FIG. 8A, six virtual devices (“Amp1”, “Amp2”, “Amp3”, “Amp4”, “ACD (1)” and “ACD (2)” registered in “Area (1)” are registered. )), Serial numbers “1” to “6” consecutive in the area are assigned as in-area IDs.

  When the “Rack” tab 61 is selected, the project configuration is displayed in the tree display section 50 in the “rack group tree” display form shown in FIG. The “rack group tree” is a display form (group tree) in which the amplifiers registered in the area are divided into “rack groups” based on the information of “Rack tree” included in the area information 33 of each area. The rack group is a group in which amplifiers are grouped for each rack (shelf) on which amplifiers are mounted. A rack group can be further nested below one rack group, that is, an amplifier group in one group can be further divided into small groups. In the example of FIG. 8B, two groups “Rack-1A” and “Rack-1B” are created below one rack group “Rack-1” created in “Area (1)”. Furthermore, two groups “Rack-1B / 1” and “Rack-1B / 2” are provided below “Rack-1B”. Virtual devices in a certain area that are not classified into rack groups are classified into the category “Ungrouped Device”. In FIG. 8B, “AmpX1” and “AmpX2” are classified into the category “Ungrouped Device”. The “rack group tree” is also provided with an ID display field 65 for displaying the in-area ID of each virtual device corresponding to the display item of each virtual device.

  When the “Feed Structure” tab 62 is selected, the configuration of the project is displayed on the tree display unit 50 in the “feed structure group tree” display form shown in FIG. The “feed structure group tree” is a display form of a tree in which each channel of the amplifier registered in the area is divided into “feed structure groups” based on the information of “Feed Structure Tree” included in the area information 33 of each area. (Group tree). The feed structure group is a group in which amplifier channels are grouped for each speaker serving as a signal output destination of each channel of the amplifier. In this grouping, for example, in the first group (Group-in FIG. 8C), the amplifier channels for each of the high, middle, and low sound bands connected to the L channel of the stereo speaker are grouped. 1 "), a second group in which the channels of the amplifiers for each of the high, middle, and low frequencies connected to the R channel of the stereo speaker are grouped (" Group-2 "in FIG. 8 (c)). It is possible to make groupings such as ... Therefore, in the “feed structure group tree”, display items (such as “Amp1: ch1” in FIG. 8C) corresponding to the channel of the amplifier are displayed in each group. Further, in the “feed structure group tree”, virtual device channels in the area that are not classified as “feed groups” are classified into the “Ungrouped Channels” category.

  When the “User Defined” tab 63 is selected, the project configuration is displayed on the tree display unit 50 in the “User Defined tree” display form. This group is a group of amplifier channels in the area according to the grouping defined by the user, and the amplifiers registered in the area based on the information of “User Defined Tree” included in the area information 33 of each area. Is a display form of a tree divided by “User Defined Tree”. The display form is substantially the same as the feed structure group tree of FIG. 8C except for the difference of the group information 36 to be referred to, and therefore, the display example of the User Defined tree is omitted.

  In the tree display unit 50, by setting a plurality of areas in one project and grouping them into one or a plurality of groups for each area, (1) the display form of the tree configuration in the tree display unit 50 from a different viewpoint Since selection can be made according to grouping (group definition), there is an advantage that when the individual amplifiers are controlled, it is easy to reach the target amplifier or the channel of the amplifier from the tree display unit 50. . Further, (2) there is an advantage that a plurality of amplifiers can be collectively controlled by selecting a group as a control target.

  In addition, the display form of the display object corresponding to the virtual device displayed in the device tree and group tree of the tree display unit 50 includes (1) a display form indicating that “the entity is present” in which the corresponding real device exists on the network. There are two types of display modes: (2) a display mode indicating “no entity” in which the corresponding real device does not exist on the network. In this embodiment, the display object corresponding to the virtual device is displayed as “solid line” when “present” is displayed, and the display object corresponding to the virtual device is displayed as “dotted line” when “not exist”. .

  In the tree display unit 50, the virtual device registered in the area in the project file or the channel of the virtual device is displayed as “virtual device in the area” in both the device tree and the group tree. The display object corresponding to the virtual device in the area in which the virtual device and the real device are associated with each other by the matching process between the virtual device and the real device, which will be described later, is displayed in a display form indicating “entity exists”, that is, a solid line. The For example, in FIG. 8A, “Amp1” is an example of a display object representing a virtual device in an area displayed in the display form of “entity exists”. In addition, the display device corresponding to the virtual device in the area where the virtual device and the real device could not be matched by the matching process, that is, the virtual device in the area in which the real device was not detected is “no entity”. The displayed display form, that is, a dotted line. For example, in FIG. 8A, “Amp4” is an example of a display object representing a virtual device in an area displayed in the display form of “no entity”.

  On the other hand, if a real device is detected on the sound system by the matching process, but there is a real device that could not be associated with any virtual device in any area of the project file, the remote control software A display object corresponding to the device is automatically created in the category “Unknown Device” of the tree. In the present specification, this is referred to as “a virtual device outside the area”. For example, in FIG. 8A, “AmpX” is an example of a display object corresponding to a virtual device outside the area. Here, a display object representing “AmpX” is displayed with a dotted line (that is, a display form representing no entity). This means that after “AmpX” is created as a virtual device outside the area, the corresponding real device is disconnected from the network. Note that display objects corresponding to virtual devices outside the area are not displayed in the group tree. Further, instead of displaying the virtual device from which the corresponding real device is cut off with a dotted line, the display of the virtual device may be deleted from the tree.

  Further, in FIGS. 8A to 8C, in the bidirectional arrow image 66 displayed on the right side of the display object corresponding to the virtual device, the OnLine status of the corresponding virtual device is online (“ONLINE”). It is a mark indicating that. The one-way arrow image 67 displayed on the right side of the display object corresponding to the virtual device is a mark indicating that the OnLine status of the corresponding virtual device is in the monitor state (“MONITOR”). For virtual devices whose virtual device's OnLine status is offline ("OFFLINE"), no mark is displayed on the right side of the corresponding display object. The OnLine status of each virtual device is based on the OnLine status information 39 stored in the corresponding device information 37.

  The online state (ONLINE) is a state in which a “user” having the authority to control the amplifier in the area can remotely control the corresponding real device from the PC 2. The monitor state (MONITOR) is a state in which a “guest” having authority to view amplifiers in the area can remotely monitor the operation state of the corresponding real device from the PC 2. In addition, “OFFLINE” is a state in which remote communication is not performed between the virtual device and the real device. When the operation data of the virtual device is edited in the remote control software in the offline state, the data of the current project is updated according to the content of the editing operation. However, the operation is not reflected in real equipment.

  FIGS. 9A and 9B are diagrams showing a screen configuration example of the area indicated by reference numerals 52 to 54 in the basic screen of FIG. (A) is a configuration example of a screen when amplifiers are individually specified in the tree display unit 50, and (b) is a case where an area or group is specified in the tree display unit 50, that is, a plurality of amplifiers are selected. It is a structural example of the screen controlled collectively.

  In FIG. 9A or 9B, the level display section 52 displays the volume level of the input signal and the volume level of the output signal in one area, group, amplifier, or amplifier channel designated by the tree display section 50. The level of the load impedance connected to the output terminal and the output power level are displayed for each channel (in FIG. 9, two channels “CH A” and “CH B”), and for each channel. Input signal to output signal mute on / off switching button image, output polarity switching switch image, and the like. In addition, the status display unit 53 displays one area, group, amplifier, or operational state of the amplifier designated by the tree display unit 50. The attenuator operation unit 54 is provided with an operation element image for adjusting the attenuator parameter (volume level attenuation amount). The attenuator parameter of one area, group or amplifier 1 selected in the tree display unit 50 is provided. Is assigned to the control object of the manipulator image. As shown in FIG. 9, the screen configurations of (a) and (b) are generally the same. In the example shown in FIG. 9, the difference between the two is that the configuration of the attenuator operation unit 43 is different, the output polarity is not switched on the screen of (b), and the screen status display unit 53 of (b). Are three points where the setting state of “Output Mode” is not displayed.

  Various procedures performed by the PC 2 and the amplifier 1 in the acoustic system having the above-described configuration will be described with reference to flowcharts.

  FIG. 10 is a flowchart showing the outline of the flow of the operation procedure of the remote control software executed by the CPU 20 of the PC 2. When the remote control software is activated on the OS of the PC 2, the CPU 20 performs a predetermined initialization process including starting up a basic screen on the display (user interface 24) (step S1). After the initialization process is completed, the CPU 20 waits for an operation event to be input from the user (step S2). When any operation event input by the user is detected, the CPU 20 executes a process corresponding to the operation event (step S3). The CPU 20 repeats the processes of steps S2 and S3 until the user instructs the end of the remote control software (NO in step S4). When the end of the remote control software is instructed (YES in step S4), the CPU 20 performs a predetermined end process (step S5) and ends the remote control software.

  The operation event that the CPU 20 waits in step S2 is an operation event input by the user from an operation screen such as a basic screen displayed on the display (user interface 24). For example, a project file load instruction, a current project, Store instructions, various editing operations of data in the project, or online instructions or offline instructions for virtual devices and real devices. Hereinafter, an example of an operation procedure of the process executed by the CPU 20 in step S3 according to various operation events by the user will be described with reference to flowcharts.

  The various editing operations described below define the authority of the user who can execute each operation, thereby restricting the entity that performs the data editing operation. As already mentioned, the user's authority is “Admin” with full authority of the project, “Power user” with authority to edit the area, “User” with authority to control the amplifier in the area, and Amplifier in the area. There are five types: “Guest” who has only viewing authority and “Outsider” who has no authority in the area. Here, one of five types of authority defined in advance is applied to each user. However, each authority can be defined by the user, and further, the user can define the contents. The authority “custom” may be provided.

  FIG. 11 is a flowchart illustrating an example of an operation procedure of processing executed by the CPU 20 when a user inputs a project file load instruction as an operation event. The user can open the project file library 31 from the common operation panel 59 on the basic screen of FIG. 7, select one project file 32 in the library, and instruct loading of the selected project file 32. In step S6, the CPU 20 performs a process of opening the project file 32 selected by the user, and loads the data group included in the selected project file 32 into the current project.

  In step S7, the CPU 20 performs a process of logging in the user (user authentication) to the project loaded in the current project in step S6. Specifically, the CPU 20 displays a login screen (not shown) for requesting input of a user ID and authentication information on the display 24, allows the user to input the user ID and authentication information, and inputs the user ID and authentication information on the login screen. The obtained user ID and authentication information are collated with account information 34 (user ID and authentication information) in the user information included in the current project. If there is account information 34 that matches the user ID and authentication information input by the user, the CPU 20 determines that user authentication has been established and permits the user to log in to the current project. On the other hand, if the user does not have an account in this project, or if there is an error in at least one of the input user ID and authentication information, the CPU 20 determines that the login has failed, The loading operation ends.

  When the login process in step S7 is completed, the CPU 20 performs a “matching process” in step S8. The matching process detects each real device connected on the network, acquires a device ID 41 and an area ID 43 from each detected real device, and uses each of the acquired device ID 41 and area ID 43 for each current project. This is a process of collating the area ID 46 of the area with the device ID 38 of the virtual device registered in each area, and associating the real device connected to the acoustic system with the virtual device registered in each area. A detailed description of the operation procedure of the matching process will be described later with reference to FIG.

  In step S9, the CPU 20 performs screen initialization processing such as initial display of the tree display unit 50 based on the result of the “matching processing” in step S8. That is, as a result of the matching process in step S8, (1) of the virtual devices in the area that have been associated with the real device, a display object having a display form indicating “substance (real device) exists” is displayed. Those displayed in the device tree and group tree of the tree display unit 50 and (2) virtual devices in the area that cannot be associated with real devices represent “no real (real device)”. Display objects in the display form are displayed in the device tree and group tree of the tree display unit 50. In addition, if a real device is detected on the network but cannot be associated with a virtual device in any area, a display item representing a virtual device outside the area is displayed in the “Unknown Device” category of the device tree. It is automatically generated in a display form indicating “substance (real device) present”.

  With the processing of FIG. 11, the project selected by the user as the control target is displayed on the basic screen on the display of the PC 2, and the project selected as the control target from the PC 2 can be controlled or monitored.

  FIG. 12 is a flowchart illustrating an example of an operation procedure for saving a project file executed by the CPU 20 when a user inputs a project file save (store) instruction as an operation event. When the user instructs to save the project file, in step S10, the CPU 20 stores the contents of the current project on the memory (RAM) 21 as one project file 32 in the project file library 31 provided in the HDD 22. Process. As a result, the contents of the current project currently started up in the remote control software are saved in the project file library 31 as one project file 32.

  FIG. 13 is a flowchart illustrating an example of an operation procedure of processing executed by the CPU 20 when the user performs an editing operation on the tree display unit 50 as an operation event. The editing operation of the tree display unit 50 is an operation performed by a user who has an editing authority for the area ("power user" or higher authority), and when all virtual devices included in the editing target area are in an offline state. It can only be executed. The editing operation of the tree display unit 50 includes an operation for creating a new area, an operation for deleting an existing area, an operation for creating a new group in a certain area, an operation for deleting an existing group, Operation to move a group to another area, operation to create a new virtual device, operation to create a new virtual device in a certain area, operation to delete an existing virtual device, or virtual between areas or groups This includes operations such as moving devices. The user can perform these editing operations graphically by an operation using the user interface 24 of the PC 2, such as a drag-and-drop operation of a display object corresponding to each element.

  If the editing operation of the tree display unit 50 input by the user is addition of a new device (virtual device) (YES in step S11), the CPU 20 adds the new information to the area information 33 of the area designated as the addition destination. Device information 37 corresponding to the added virtual device is created. The new device addition operation is performed by, for example, performing an operation of opening the model library menu on the common operation panel 59 of the basic screen, and selecting a desired model name from among a plurality of model names displayed in the opened menu. A virtual device corresponding to the model name may be added. Here, the data that must be specified at a minimum as data for defining a newly created virtual device is model information and in-area ID (part of the device ID 38) of the newly added virtual device. In this embodiment, when a virtual device is newly created, the CPU 20 newly creates a serial number in the area designated as the addition destination (a number that is continuous with the ID group existing in the area in the area) and newly created. It is assumed that a process of automatically assigning the ID in the area is performed.

  When a new device (virtual device) is added (YES in step S11), the CPU 20 performs matching processing between the added virtual device and a real device connected to the acoustic system (step S12), and the new device The stored contents of the current project are updated according to the addition (step S13). In step S14, the CPU 20 updates the display of the basic screen (tree display unit 50) to reflect the operation for adding the new device on the screen. When an editing operation on the tree display unit 50 other than the addition of a new device (virtual device) is performed (NO in step S11), the CPU 20 changes the configuration of the tree selected as the editing target to the editing operation. Processing for editing is performed according to the contents of (step S15). Then, the CPU 20 updates the stored contents of the current project in accordance with the contents of the editing operation (step S13), and updates the display of the basic screen (tree display unit 50) (step S14). By this processing, the tree configuration displayed on the tree display unit 50 is changed according to the user's editing operation.

  In addition, a user who has control authority ("user" or higher authority) for amplifiers in the area can edit amplifier data. A user who has the authority to control the amplifier in the area selects the amplifier to be edited on the tree display unit 50, so that the data of the selected virtual device is stored in the area indicated by reference numerals 52 to 54 on the basic screen in FIG. The values of various parameters developed there can be changed using the GUI parts (see FIG. 9A or 9B) in the areas 41 to 43. Here, the amplifier (virtual device) to be edited is either a single amplifier, one group, or one area. That is, if one group or one area is an editing target, a plurality of amplifiers (virtual devices) are substantially editing targets. When the virtual device or group of virtual devices to be edited is in an online state, as shown in the flowchart of FIG. 14, the CPU 20 performs an editing operation on the amplifier (virtual device) performed by the user on the basic screen for the real device to be edited. An operation request for notifying the contents of is transmitted (step S16). In the real device that has received the operation request, if the user who has made the operation request has authority, the operation data of the own device is updated according to the content of the editing operation, and the update result is returned to the PC 2 (details). (See FIG. 28 described later). On the PC 2 side, the CPU 20 updates the stored contents of the current project in accordance with the response contents from the real device (step S17), and updates the screen display as necessary.

  When the virtual device to be edited is offline, as shown in the flowchart of FIG. 15, the CPU 20 updates the stored contents of the current project according to the editing operation of the amplifier (virtual device) performed on the basic screen by the user. (Step S18), the display on the screen is updated as necessary. In this case, the content of the editing operation performed by the user on the PC 2 side is not reflected on the real device.

  FIG. 16 is a flowchart illustrating an example of an operation procedure of processing executed by the CPU 20 when the user performs an editing operation on an account registered in a project to be controlled. The user account is set for each project file 31 and is managed by the account information 34 for each user stored in the project file 31. The account editing operation can be executed only by a user who has all the authority of the project ("admin" authority), and is executed only when all the virtual devices in the project are in an offline state.

  For example, the user may be able to make an account edit request from the common operation panel 59 on the basic screen. When an account editing request is input by the user, the CPU 20 displays a user management dialog screen (not shown) for editing the account on the display (step S19). Then, the CPU 20 receives an account editing operation on the user management dialog screen from the user (step S20), and updates the user information (account information 34) stored in the current project according to the input editing operation (step S20). S21 to S24). That is, when an operation for deleting an existing account is performed, in step S21, the CPU 20 stores the specified account information 34 and the user role information 35 corresponding to the account information 34 for each area into the current project. Delete from. When an operation for changing an existing account is performed, in step S21, the CPU 20 determines at least the user ID and authentication information of the specified account information 34 according to the content of the change operation performed by the user. Either one or processing for changing the user role information 35 corresponding to the account information 34 in the designated area is performed.

  When a new account is added, the CPU 20 creates a new account in step S23. In other words, the CPU 20 causes the user to set the user ID and authentication information to newly create the account information 34 in the current project, and allows the user to set the authority for each area that should be given authority to the user of the new account. The user role information 35 corresponding to the new account information 34 is newly created for each area. In step S24, the rule account created in step S23 is registered in the current project. That is, the user information (account information 34) stored in the current project and the user role information 35 for each area are updated.

  Next, a synchronization process between a virtual device and a real device will be described. When the user operates the “Online” button image 57 on the basic screen shown in FIG. 7, the CPU 20 displays the “Synchronized dialog” screen shown in FIG. 17 on the display. The “synchronized dialog” screen is a dialog screen for instructing online (synchronization) or offline for the amplifier group registered in the area currently selected as the control target in the tree display section 50 of the basic screen. In this case, an online instruction (“Go-Online”) button image 68 and an offline instruction (“Go-Offline”) button image 69 are included. When the user operates the on-line instruction button image 68 on the “synchronized dialog” screen, the CPU 20 executes a synchronization process for bringing the virtual device group in the area currently selected as the control target into an online state. That is, the synchronization process is performed for one area. A “Get Editable” button image 78 on the screen is a button for instructing whether the user selects an online state or a monitor state. The on state of the button image 78 indicates that the online state is selected, and the off state indicates that the monitor state is selected. The device information display unit 76 in the screen corresponds to the amplifier name and device ID of the virtual device (synchronization candidate virtual device) associated with the real device among the virtual devices in the area. The real crisis IP address and OnLine status are displayed.

  FIG. 18 is a flowchart illustrating an example of an operation procedure of processing executed by the CPU 20 when the user operates the online instruction button image 68. In step S25, the CPU 20 specifies a virtual device in the area that is associated with a real device and whose online status is not ONLINE as a “virtual device to be synchronized”. The first virtual device and the corresponding real device are designated as “synchronization target”. Here, the processing from step S26 onward is executed in order for each of the devices identified as virtual devices to be synchronized. Therefore, a device to be subjected to the synchronization processing is a virtual device registered in a certain area and matched with a real device (a virtual device in an area with an entity).

  In step S26, the UserInfo information 45 is acquired from the real device to be synchronized, and a plurality of sets of user ID and authentication information included in the acquired UserInfo information 45, and the user ID and authentication of the login user in the account information 34 are obtained. Check consistency with the information set. If the pair of the logged-in user's user ID and authentication information is included in the acquired UserInfo information 45 as it is (“match” in step S27), the process proceeds to step S30.

  In step S27, it is determined that the user ID of the login user is not included in the acquired UserInfo information 45, or the user ID of the login user is included in the acquired UserInfo information 45. There are three cases where the authentication information paired with the authentication information does not match the authentication information of the login user, or when the user info information 45 on the real device side is cleared.

When the acquired UserInfo information 45 and the user ID of the login user are included, but the authentication information paired with the user info is unmatched (the mismatch of step S27), in step S28, the CP 20 A password input screen that prompts the user to input a password (authentication information) is displayed, and re-authentication processing is performed to allow the user to input the password (authentication information). If the password input by this re-authentication process is correct, it is determined that the authentication is successful (“OK” in step S29).
If the UserInfo information 45 is cleared on the real device side, in step S28, the CPU 20 determines the authority of the logged-in user based on the user role information 35 in the area information 33 to which the virtual device belongs ( (User role) is checked, and if the user has authority over the editing authority of the area (authority over “power user”), it is determined that the authentication is successful (“OK” in step S29).

  Also, when the acquired UserInfo information 45 does not include the user ID of the logged-in user, or when the UserInfo information 45 of the real device is cleared and the logged-in user does not have authority over the editing authority for the area. The CPU 20 determines that the authentication has failed (“NG” in step S29), and the virtual device synchronization processing ends.

  In step S30, the CPU 20 checks the user role information 35 of the logged-in user. If the authority set in the user role information 35 is “user” or higher, that is, an authority higher than the control authority of the amplifier in the area, the logged-in user is a real device corresponding to the virtual device to be synchronized. Have the right to control. Therefore, in this case, the determination in step S30 branches to “editable”. In step S30, the branch is performed based on the user role information 35. The branch is divided into the user role information 35 of the logged-in user and the user role information of the same user in the acquired UserInfo information 45. The user role information with the lower authority may be performed based on the user role information. In this case, the authority check based on the UserInfo information 45 is duplicated on the PC 2 side and the amplifier side, and security is further strengthened. Also, authority determination (step S61) on the amplifier side, which will be described later, can be omitted.

  On the other hand, when the authority set in the user role information 35 of the logged-in user is “user” or less, that is, when there is no authority to control the amplifier in the area (when the authority to browse the amplifier in the area is present), step S30. This decision branches to “impossible to edit”. In this case, branching to disable editing means that monitoring is permitted. In this embodiment, when the virtual device that first performed the synchronization processing in the area is in the monitor state as a result of the synchronization processing (if the authority is insufficient, the amplifier has already been controlled by another user). Or if the “Get Editable” button 78 is in an off state, that is, if the user chooses to enter the monitor state), all virtual devices in the area are “not editable”. The determination process of step S30 is configured to branch to “. This operation is in accordance with the design policy that “the control of the devices in the area is performed by one PC”.

  When the determination in step S30 branches to “editable”, the CPU 20 controls the real device corresponding to the virtual device currently being synchronized in step S31 by the currently logged-in user. A “control request” command is sent to request permission. At this time, the user ID and authentication information of the login user are transmitted to the real device together with the control request. The real device that has received the “control request” command determines whether to permit control of the user by the logged-in user by the processing shown in FIG. 25 described later, and returns the determination result to the PC 2. To do.

  Note that the CPU 20 of the PC 2 sends the control request in step S31, and at an appropriate timing until receiving a response in step S31, the area ID 46 of the area stored in the current project and the controller ID 40 of the PC 2 are stored. The group information 36 in the area information 33 to which the virtual device to be synchronized belongs, the user information in the current project (group of account information 34), and the user role in the area information 33 to which the virtual device to be synchronized belongs. Information 35 is transmitted to the real device. The information group transmitted here is overwritten on the controller ID 42, area ID 43, group information 44, and UserInfo information 45 on the real device side when control is accepted on the real device side.

  In step S <b> 32, the CPU 20 determines a response (reply content) from the real device to the “control request”. There are three types of responses from the real device: “controllable”, “monitorable”, and “reject”. If the user has the right to control the real device and the real device is not controlled by another user, the response (reply content) from the real device is “controllable”. If the user has the right to view the real device, or if the user has the right to control the amplifier in the area, but the real device is controlled by another PC 2 (other control owner), the real The response (reply content) from the device is “monitorable”. In other cases, for example, when the user is an “outsider” who has no authority over the real device, or when the real device does not have the user account (user ID and authentication information), this control request Is determined to be illegal and a “rejection” response is transmitted from the real device to the PC 2.

  If the response (reply content) from the real device to the “control request” is “controllable” (“controllable” in step S32), in step S33, the CPU 20 performs the synchronization stored in the current project. “ONLINE” is set to the value of the OnLine status information 39 of the device information 37 corresponding to the target amplifier. The real device transmits the controller ID 42 (controller ID of the controller of the real device) stored in the real device to the PC 2 together with the response “control is possible”. The CPU 20 of the PC 2 overwrites the value of the controller ID 42 received together with the response “control possible” on the controller ID 40 of the device information 37 corresponding to the virtual device to be synchronized in the current project. When the response is “controllable”, the value of the controller ID 42 of the real device is the controller ID of the PC 2 itself.

  In addition, when “ONLINE” is set as the value of the OnLine status information 39 in the step S33, the device ID 38 of the virtual device and the device ID 41 of the real device only partially match (that is, both device IDs). If only one of the internal MAC address or the in-area ID matches), the process of matching both the device IDs is also performed. If only the MAC address of the device IDs matches, the device ID 41 of the real device is overwritten with the device ID 38 of the virtual device. When only the in-area IDs match among the device IDs, the device ID 38 of the virtual device is overwritten with the device ID 41 of the real device. At this time, the IP address and model information of the real device are overwritten on the IP address and model information (FIG. 4) of the virtual device.

  In step S <b> 34, the CPU 20 confirms the consistency between the operation data in the device information 37 of the virtual device and the operation data stored in the memory 11 of the real device, that is, confirms whether or not they match. If the two match, the CPU 20 determines that it is not necessary to perform data synchronization (synchronization) processing between the virtual device and the real device (“OK” in step S35), and synchronizes the virtual device. Finish the conversion process.

  On the other hand, when the operation data of the virtual device and the real device do not match (“NG” in step S35), the CPU 20 performs a process of displaying the “synchronization direction selection screen” shown in FIG. The “synchronization direction selection screen” is provided with a radio button 69 that allows the user to select “synchronization” (“Application → Device”) or “reverse synchronization” (“Device → Application”) as the direction of synchronization (synchronization). It has been. In the example of FIG. 19, the radio button 69 is in a state in which the “sync” direction is selected. A display field 70 is provided below the radio button 69 to display the name of the amplifier in which the data mismatch is detected in step S35. In the example of FIG. 19, the amplifier name “Amp3” is displayed in the display field 60. The user uses the radio button 69 to select either “synchronization” or “reverse synchronization” as the direction of the synchronization processing, and confirms the direction selection by the radio button 69 by operating the “OK” button image 71. To do. That is, the instruction to go online when the amplifier (virtual device) is brought into the online state includes an instruction to select the synchronization direction.

  In step S36, the CPU 20 synchronizes (synchronizes or reversely synchronizes) the data of the virtual device and the real device in accordance with the direction of synchronization processing (synchronized or reversely synchronized) selected by the user on the synchronization direction selection screen. And match them. When “synchronization” is selected as the synchronization direction, in step S36, the CPU 20 performs a process of overwriting the operation data of the virtual device over the operation data of the virtual device over the network. That is, the data setting state of the real device is matched with the data setting state of the current project. When “reverse sync” is selected as the sync direction, in step S35, the CPU 20 receives the operation data of the real device via the network and performs a process of overwriting the operation data of the virtual device. . That is, the data setting state of the current project is matched with the data setting state of the real device.

  Further, when branching to “impossible to edit” in the determination of the step S30, a “monitor request” is transmitted to the real device in a step (not shown), and “monitoring is possible” from the real device as in the case of the “control request”. Alternatively, a “reject” response is received. If a response “monitorable” is received here, or if the response determined in step S32 is “monitorable”, in step S37, the CPU 20 synchronizes the synchronization stored in the current project. “MONITOR” is set to the value of the OnLine status information 39 of the device information 37 corresponding to the target amplifier. When the response of the real device is “monitorable”, the real device transmits the controller ID 42 (the main controller of the real device, that is, the PC 2 executing the synchronization process) stored in the real device together with the response. Transmits the data of the controller ID of another PC 2 to the PC 2 together. That is, the PC 2 receives the “monitorable” response and the controller ID 42 of the controller of the real device in step S32.

  In step S <b> 38, the CPU 20 performs a process of synchronizing (reverse synchronizing) the data of the virtual device and the real device so as to match the two. As described above, when the amplifier (virtual device) is set to the monitor state, the synchronization processing is forcibly performed by “reverse synchronization”. Here, of the contents stored in the memory 11 of the real device (see FIG. 6), the data that looks into the area ID 43 and the UserInfo information 45 is transmitted to the PC 2 side, and the corresponding data in the current project is transmitted from the real device. Overwritten by data. Specifically, the device ID 38, device type information, IP address, operation data, and controller ID 40 in the device information 37, group information 36 (“RackTree” information, “Feed Structure Tree” information, “User” in the area information 33 are displayed. The “Defined Tree” information) is overwritten with the stored contents of the memory 11 of the real device. That is, the data setting state of the current project is matched with the data setting state of the real device. As a result, the virtual device enters a “monitor state (a state in which a real device can be monitored)”.

  It should be noted that when performing the reverse synchronization processing in step S38 (that is, when the virtual device is shifted to the monitor state), the device ID 38 in the device information 37 is overwritten with the device ID 41 of the real device. I want. That is, in the “matching process” to be described later, matching is performed in a state in which only one of the MAC address or the in-area ID is in a state where the device ID 38 of the virtual device and the device ID 41 of the real device are partially matched. If established, the device ID 38 in the device information 37 is overwritten with the device ID 41 of the real device when performing the reverse synchronization processing in step S38.

  If re-authentication fails in step S29 (“NG” in step S29), or if the response determined in step S32 is “rejected” (“rejected” in step S32), or “ If the response to the “monitor request” is “reject”, the synchronization processing for the virtual device is terminated. In this way, when the synchronization process is ended, or when any error occurs during the synchronization process from step S26 to S38, the CPU 20 displays a “warning dialog screen” shown in FIG. 20 on the display. The message display section 73 of the “warning dialog screen” displays a message for notifying the user of an error or warning content such as “authentication failure”. Note that, for example, when the authentication information does not match in the process of step S26, the “password input screen” may be displayed together with the “warning dialog screen”. In the case of an error that allows the synchronization process to be continued, a “Continue” button image 74 that instructs the continuation of the process and a “Skip” button image 75 that instructs the stop of the process are displayed. Asks whether to continue the synchronization process. Also, when an error that prevents the synchronization process from continuing, such as when the synchronization process is stopped for the amplifier in accordance with the determination in step S29 or S32, the “Continue” button image 74 and the “Skip” button image 75 are displayed. Instead, an “OK” button image that asks the user to approve the warning message content is displayed. In response to the operation of the “OK” button image, the synchronization processing for the virtual device is terminated.

  When the synchronization processing for one virtual device is completed by the processing in steps S26 to S38, until the synchronization processing for all virtual devices specified as virtual devices to be synchronized is completed by the determination in step S39, Steps S26 to S38 are repeated in order for each virtual device. Thereby, the synchronization processing of all virtual devices registered in one area (virtual devices in the area associated with the real device) is performed. By this synchronization processing, the user's control authority for each amplifier in the area is set on a first-come-first-served basis (only the monitor is allowed if there is a control master first). It can be understood from the fact that each amplifier 1 has UserInfo information 45, the control authority of the amplifier can be set for each amplifier. However, the remote control software of this embodiment performs control in units of areas, in other words, that one control person is attached to one area (one area is controlled by one PC 2). It is the original aim. Therefore, the person who has the authority to edit the area should design the area so as to be one control master for one area. At the end of the synchronization process of FIG. 18, “ONLINE” is set in the “Online” status information of the area stored in the area information 33 of the area where the synchronization process has been performed. It should be noted that “ONLINE” may be set in the “Online” status information of the area at the start of the synchronization process (when the on-line instruction button image 68 is operated).

  The “synchronized dialog” screen shown in FIG. 17 is provided with a display column 76 indicating the progress of processing. The display column 76 displays a list of virtual devices (synchronization candidate virtual devices) associated with the real device among the virtual devices in the area to be synchronized. The contents of the list include the amplifier name of each amplifier (virtual device), the in-area ID, the IP address, and the OnLine status information. In the example shown in the figure, the amplifiers on the list are arranged in the order of amplifier names. The initial value of the OnLine status information is “ONLINE”, “MONITOR”, or “OFFLINE” depending on the value stored in the OnLine status information of each amplifier. When synchronization processing is started for one amplifier, “Now Synchronizing” is displayed in the status information column corresponding to the amplifier in progress of the synchronization processing. Further, “Completed” is displayed in the status information column corresponding to the amplifier for which the synchronization processing has already been completed. The example of FIG. 17 shows a state in which the synchronization process has progressed partway through the target area, and the amplifier names “Amp1”, “Amp2”, and “Amp3” have already completed the synchronization process. The amplifier name “Amp4” is currently in the process of synchronization. At the bottom of the display column 76, a meter 77 is provided that indicates the progress of the synchronization process for the entire area as a percentage. When the interface device (“ACD (1)”, “ACD (2)”, etc. in “Area (1)”) is included in the area to be synchronized, these interface devices are also listed in the display column 76. May be up.

  When the virtual device is brought online (ONLINE) with respect to the corresponding real device by the synchronization processing of FIG. 18, when an editing operation for editing the operation data of the virtual device is performed on the PC 2, The editing operation is transmitted to the corresponding real device via the network, the operation data of the corresponding real device is edited, and the editing result is transmitted to the PC 2 via the network, and the virtual device (device) in the current project Information 37) is reflected in the operation data. In addition, when an editing operation for editing operation data is performed in the corresponding real device, the operation data in the real device is edited, and the editing result is transmitted to the PC 2 and the virtual device ( It is reflected in the operation data of the device information 37). In addition, data indicating various operating states detected in a real device (for example, output stage temperature, input and output signal levels, power supply voltage, output voltage, output current, load impedance, protection status, etc.) The data is transmitted from the device to the PC 2 and displayed on the level display unit 52 and the status display unit 53 of the basic screen as necessary.

  When the virtual device is in a monitor state (MONITOR) with respect to the corresponding real device by the synchronization processing of FIG. 18, the virtual device is displayed in the group tree of the tree display unit 50 and the reverse of step S38. It is displayed as a device in the group based on the group information 44 received from the real device in the synchronization process. When the operation data of the real device, the group information 44, etc. are edited, the edited content is reflected in the operation data, the group information 36, etc. of the virtual device (device information 37) in the current project of the PC 2. Data indicating various operation states detected in the real device is transmitted from the real device to the PC 2 and displayed on the level display unit 52 and the state display unit 53 of the basic screen as necessary.

  When the user operates an off-line instruction (“Go-Offline”) button image 68 on the “synchronized dialog” screen shown in FIG. 17, the CPU 20 selects the OnLine status information 39 among the virtual devices in the synchronization target area. Executes offline processing for bringing a real device associated with a virtual device of “ONLINE” or “MONITOR” offline. FIG. 21 is a flowchart illustrating an example of an operation procedure of a process executed by the CPU 20 when the user operates the off-line instruction button image 58.

  In step S40, the CPU 20 issues a “release” request command to each real device associated with a virtual device whose OnLine status information 39 is “ONLINE” or “MONITOR” among the virtual devices in the area. Send. Of each real device that has received the “open” request, the real device that has been controlled by the PC 2 that has transmitted the “open” request performs a process of “releasing” its own device by a process that will be described later. In the real device that has performed this “release” processing, the controller ID is set to “Null” and the UserInfo information 45 is cleared. That is, those real devices are in a free state where they are not receiving remote control from the user. In step S41, the CPU 20 sets the value of the OnLine status information of the area in the current project and the value of the OnLine status information 39 of each virtual device in the area to OFFLINE. As a result, the area that was in the online state and the virtual device that was in the online state or the monitor state in the area before the offline instruction is all in the offline state.

  FIG. 22 is a flowchart illustrating an example of an operation procedure of a timer operation executed by the CPU 20 of the PC 2 at predetermined time intervals. In step S42, the CPU 20 performs an active sensing process for periodically checking whether an online amplifier (real device) in the project is connected to the network. In this active sensing process, the real device associated with the virtual device whose OnLine status information 39 is “ONLINE” or “MONITOR” has been abnormally operated or not requested for a certain period of time (no data is sent). Only to do.

  In step S43, the CPU 20 acquires various data received from each real device since the previous timer operation was executed from a reception history buffer (not shown). Here, the “various data” to be acquired includes a “connection” message issued when each real device is connected to the network, a “setting change” message generated when various settings are changed on each real device, or the virtual device is online. For example, a “no response” message indicating that there is no response from a certain real device for a predetermined time. The “no response” state means that the real device is physically disconnected from the network or the real device is powered off, and this can be confirmed by active sensing. In the case of “no response”, in this routine, the CPU 20 determines that the real device is disconnected from the network.

  When the “connection” message indicating that a new real device is connected is detected in step 43 (YES in step S44), the CPU 20 detects the connection by performing “matching processing” in step S45. Correspondence between the real device and the virtual device is performed.

  If the “no response” message is acquired in step 43, that is, if disconnection of the real device is detected (YES in step S46), the CPU 20 responds to the real device in which disconnection is detected in step S47. The value of the OnLine status information 39 of the virtual device to be changed is changed to “OFFLINE”. As a result, the virtual device corresponding to the real device in which the disconnection has been detected enters an offline state.

  In step S48, the CPU 20 performs a process of updating the display of the tree display unit 50 on the basic screen according to the processing result of step S45 or S47. If there is a virtual device matched with the real device connected by the matching process in step S45, the display form of the display object corresponding to the virtual device is changed from the display form (dotted line) indicating “no entity” to “entity”. It is changed to a display form (solid line) representing “present”. If there is no virtual device that matches the newly connected real device, a corresponding virtual device is generated and displayed in the “Unknown Device” category of the device tree. For the virtual device whose OnLine status information 39 has been changed to “OFFLINE” in step S47 (that corresponds to the disconnected real device), the display form of the display object corresponding to the virtual device is “existent” Is changed from a display form (solid line) representing "" to a display form (dotted line) representing "no entity". Even if a real device corresponding to a virtual device outside the area is disconnected, the corresponding display object (display object categorized in “Unknown Device” in the device tree) is not deleted, and “no entity” is displayed. Display in a display form (dotted line). For example, the display item “AmpX” in “Unknown Device” illustrated in the device tree of FIG. 8A corresponds to this case. The virtual device left in the “Unknown Device” category as “no entity” in this way is convenient because it can be used for offline editing of the device tree. A user who has authority over a power user in an area can move a virtual device of the “Unknown Device” category into the area. When the movement is performed, an in-area ID is given to the moved virtual device, and the corresponding device information 37 is stored in the area information 33 of the area.

  In the flowchart shown in FIG. 22, only the operation when the connection or disconnection of the real device is detected is shown. However, when another message such as the “setting change” message of the real device is acquired in the step 43, the acquisition is performed. The CPU 20 executes a process corresponding to the received message as necessary.

  FIG. 23 is a flowchart showing an example of the operation procedure of the “matching” process executed by the CPU 20 in step S8 of FIG. 11, step S12 of FIG. 13, or step S45 of FIG. The operation procedure shown in FIG. 22 shows a matching process for one amplifier. The PC 2 detects a group of real devices (amplifiers) connected to the network, and executes the process shown in FIG. 23 for each of the detected real devices.

  In step S49, the CPU 20 acquires the area ID 43 stored in the real device to be matched, compares it with the area ID 46 of each area stored in the current project, and specifies the area to which the real device to be matched belongs. . When the area ID matches (match) (“match” in step S49), in step S50, the CPU 20 matches the device ID 41 stored in the real device with the area identified in step S49 (area ID matches). The device ID 38 of each device information 37 in the area) is collated. On the other hand, if the area ID 43 stored in the real device does not match any of the area IDs 46 in the current project (“mismatch” in step S48), the matching process is ended for the amplifier.

  As described above, the device ID includes a MAC address and an in-area ID. In the device ID collation process in step S50, the CPU 20 associates the device ID 41 stored in the real device with the device ID 38 of the device information 37 if at least one of the MAC address and the in-area ID matches. Judge that it was taken. Specifically, in this embodiment, when the device ID cannot be matched using the MAC address, the device ID matching process in step S50 is configured so that the device ID is matched with the in-area ID. Shall be. The case where the device ID cannot be matched using the MAC address is a case where the MAC address does not match or a case where the device ID 38 of the virtual device (device information 37) does not contain the MAC address.

  If at least one of the MAC address and the in-area ID matches (“at least one matches” in step S50), in step S51, the CPU 20 matches the virtual device with the real device (device ID and area ID). Remember. If at least one of the MAC address and in-area ID included in the device ID matches (if the device ID partially matches), the virtual device device ID 38 and the real device device ID 41 are matched. Processing (overwriting of the device ID) is not performed here. In that case, for the time being, the device IDs are left in a partially matched state. This is because the process of matching the device ID 38 of the virtual device and the device ID 41 of the real device (overwriting of the device ID) is performed by the synchronization process shown in FIG. When matching is obtained, the display of the virtual device with which the correspondence is taken in the display of each tree is changed from the “no entity” display (dotted line) to the “entity present” display (solid line).

  In step S52, the CPU 20 compares the model information stored in the real device with the model information of the virtual device (device information 37) that matches the device ID in step S49, and if the model information matches, The matching process is finished for the amplifier as it is, and the matching between the real device and the virtual device to be matched is established. If the model information does not match ("mismatch" in step S52), in step S53, the CPU 20 performs a process of displaying a warning display on the display to warn the user that the model information does not match, The matching process ends for the amplifier. That is, even if the model information does not match, the matching between the virtual device and the real device is established. In this case, the matched virtual device cannot be brought online by the synchronization process, but can be brought into a monitor state.

  If both the MAC address and the in-area ID do not match in step S50 (“mismatch” in step S50), the matching process for the amplifier is terminated. If a part of the device ID is duplicated in a plurality of amplifiers (“partial duplication” in step S50), in step S54, the CPU 20 determines that the device ID is partially duplicated in the plurality of devices. The warning display for warning is displayed on the display, and the matching process is finished for the amplifier. In this case, the duplicated virtual device cannot be placed in an online state or a monitor state. In order to prevent such duplication, virtual devices that have already been matched may be excluded from the target of matching processing with real devices in the processing of FIG.

  With the matching process shown in FIG. 23, it is possible to automatically associate (match) a real device connected to the network with a virtual device registered in the current project area. This matching processing is realized by matching based on the area ID (step S49) and matching using the device ID based on at least one of the MAC address and the intra-area ID (step S50). Therefore, for example, when a project file used in the past is used in an acoustic system having the same configuration as that used in the past, the area ID or MAC address given to the virtual device in each area in the project Etc. match the area ID, MAC address, etc. of each real device in the sound system, so the virtual device in each area in the project and each real device on the sound system are automatically Can be matched. Even when some or all of the real devices are replaced with another real device of the same model, if the same area ID and in-area ID are set in the real device, automatic matching can be similarly performed. In this embodiment, the user can input the area ID 43 and the in-area ID using the operation panel 15 of the amplifier 1.

  When the logged-in user is a user who has authority higher than “power user” (area editing authority), the configuration of the matching process is changed as follows. That is, before performing “area ID collation” in step S49, matching is performed with the MAC address of the device ID in step S50. If matching cannot be obtained, matching is performed between the area ID and the in-area ID. Thereby, automatic matching can be performed more flexibly. For example, when a project file that uses the same real device is closed and another project file is opened, a plurality of devices that are online in the certain project file can be automatically matched with another project file.

  In this embodiment, the user can input the area ID and the in-area ID using the operation panel 15 of the amplifier 1, but this is only for automatic matching. If the area ID or in-area ID of the amplifier 1 in the online state is changed on the operation panel, a serious error may occur in the operation of the entire system. Therefore, when the real device (amplifier 1) is in the online state, the operation panel 15 is locked so that the area ID and the in-area ID cannot be changed. Similarly, regarding the PC 2, the area ID of the online area and the in-area ID of the online virtual device are locked so that they cannot be changed.

  In addition, since the matching process using only the in-area ID is possible, for example, when one of a plurality of amplifiers 1 (real devices) in use in the acoustic system breaks down, an existing real device is changed. When exchanging with a real device, the matching processing of the other real device can be easily performed. That is, as the in-area ID of another real device, the same value as the in-area ID assigned to the existing real device (exchange partner) is set, and the existing real device (exchange partner) is set from the network. Disconnect, connect the other real device to the network, match the other real device, change to the existing real device (exchange partner), the other real device will automatically The original is matched with a virtual device associated with an existing real device. Therefore, the replacement (replacement) of the amplifier 1 on the acoustic system can be easily performed.

  Further, according to the matching process shown in FIG. 23, since the real device and the virtual device are associated with each other using the area ID and the device ID, the virtual device registered in any area in the current project. A real device having a device ID 41 that matches the device ID 38 (real device corresponding to the virtual device) is connected to the network, and the area ID 43 of the real device is an area in which the virtual device is registered. Only when the ID matches 46, that is, when the real device belongs to any area in the current project, the matching between the virtual device and the real device is established. Then, only when the virtual device in the area can be associated with the actual real device by the matching processing, the PC 2 synchronizes the real device with the synchronization processing shown in FIG. can do. Thus, for example, when a real device in a certain area is monitored from a certain PC 2 (each real device in that area has a different control main), the current project of the other control main Even if a new real device is added to the area, a virtual device that should correspond to the newly added real device is not registered in the area of the current project started on the certain PC 2. The newly added real device cannot be monitored from the PC 2. In this case, only some real devices in the same area are monitored from the PC 2.

  Further, even if a real device is detected, if there is no device corresponding to the virtual device registered in the area in the current project (“mismatch” in step S49 or “mismatch” in step S50), the real device is associated. Does not hold. In this case, “virtual device outside the area” is displayed in the device tree of the tree display unit 50 as described above. According to the matching process shown in FIG. 23, a real device corresponding to a virtual device deleted from an area in the current project or a virtual device moved to another area is identified as “ "Virtual device". In this case, since the matching between the virtual device and the real device is not established, the PC 2 cannot control and monitor the real device. A user who has authority over a power user in an area can move a virtual device outside the area into the area when the area is offline. After that, if the area is brought online, the virtual device is given an in-area ID in the area, and the corresponding real device is set as a real device in the area.

  In addition, the virtual device and the real device each store group information (group information 36 and group information 44) and can be grouped within an area. Information is not used. Therefore, even when a virtual device is moved from one group to another group in the same area (that is, when the group information 36 and the group information 44 are inconsistent), the virtual device and the real device have an area ID. Since the device ID matches the device ID, they can be matched. When monitoring a real device in a certain area from the PC 2, group information 36 stored in the area information 33 of the certain area of the current project of the PC 2 and group information possessed by the certain real device Even if 44 is inconsistent, (1) as described above, the matching between both devices can be made with the area ID and the device ID. (2) When shifting to the monitor state by the synchronization processing, “ In order to perform “reverse synchronization” processing, the group information 36 is overwritten with the group information 44 possessed by the certain real device. Therefore, when a real device is moved to another group in the same area, the PC 2 that performs monitoring automatically recognizes the real device as a device belonging to the destination group, and as a device belonging to the destination group. The operation data can be monitored.

  In this embodiment, in the device ID collating process in step S50, the process is configured so that the matching is performed using the in-area ID when the MAC address cannot be matched. The processing may be configured to perform matching using the in-area ID only when the MAC address is not stored in the device ID 38 of the side (device information 37). When the process of step S50 is configured as described above, it is determined that the MAC address mismatch does not match the device ID.

  FIG. 24 is a flowchart for explaining an outline of the overall operation procedure executed by the CPU 10 of the amplifier 1. The operation described here is an operation related to the control of the amplifier 1 realized by the control program executed by the CPU 10, and is not an operation of acoustic signal processing (operation of the DSP 13 and the power amplifying unit 14). The process shown in this flowchart starts in response to the power-on of the amplifier 1. In step S55, the CPU 10 performs a predetermined initialization process. This initialization process includes setting of an IP address, a process of broadcasting a “connection” message for notifying the network connection of the own apparatus on the network, and the like.

  When any command is received from the PC 2 on the network (“Yes” in step S56), the CPU 10 executes processing according to the received command in step S57. A specific example of processing executed by the CPU 10 according to the received command will be described later. When the user operates the panel operator (user interface 15) of the amplifier 1 (“Yes” in step S58), the CPU 10 executes a process corresponding to the panel operation in step S59. The panel operation includes, for example, an in-area ID setting operation. Specifically, the setting operation of the in-area ID is a numerical value input. When an in-area ID setting operation is performed, the CPU 10 stores the input numerical value in the in-area ID of the memory 11 of the amplifier 1 (real device).

  The amplifier 1 repeatedly executes the processes in steps S56 to S59 until the power is turned off.

  FIG. 25 is a flowchart showing an example of the operation procedure of the process executed by the CPU 10 of the amplifier 1 in step S57 when the “control request” transmitted from the PC 2 in step S31 of FIG. 18 is received. In step S <b> 60, the CPU 10 stores the UserInfo information 45 stored in the memory 11 of the amplifier 1 and the user ID and account information 34 of the user who transmitted the “control request” (the user who is logged in to the current project). In comparison, user authentication is performed. In user authentication, whether or not there is account information 34 (user ID and authentication information) of the user who made the request in the UserInfo information 45 stored in the memory 11 of the amplifier 1, and in the UserInfo information 45 If there is a user account, the authority given to the account is checked to determine whether or not the amplifier 1 has the control authority. If the UserInfo information 45 is cleared, it is determined that the user has control authority regardless of the user account information 34 (“OK” in step S61).

  If there is account information 34 of the user who made the request in the UserInfo information 45, and the account has the control authority of the amplifier 1, the CPU 10 determines that user authentication has been established (step S61). "OK"). In step S62, the CPU 10 checks whether the controller ID 42 stored in the memory 11 of the amplifier 1 contains the ID of the control main, so that the remote control by the PC 2 different from the PC 2 that made the control request is performed. Is determined whether or not the amplifier 1 is currently receiving. If the controller ID of the controller is included in the controller ID, the CPU 10 of the amplifier 1 determines that there is a controller (another PC) that has already remotely controlled the amplifier 1 (“Yes” in step S62). ). In this case, or in the user authentication in step S60, the account information 34 of the user who made the request is included in the UserInfo information 45 of the amplifier 1, but the corresponding user role in the UserInfo information 45 indicates When the authority is the browsing authority (that is, when the authority of the user is insufficient), in step S63, the CPU 10 sends a response (instructed to permit monitoring) to the PC 2 to which the “control request” is transmitted. Send “monitorable”. That is, subsequent control requests are not accepted. In other words, the control right of the amplifier 1 is acquired on a first-come-first-served basis. When a “monitorable” response is returned, the value of the ID contained in the controller ID 42 (the controller ID of the control master (another PC) already performing remote control) is also transmitted to the PC 2. Thus, the controller ID of another PC that remotely controls the amplifier 1 is notified to the PC 2. Note that, in the determination in step S62, it is possible to consider the coincidence with the controller ID of the PC2. That is, not only when the controller ID of the controller is not included in the controller ID, but also when the controller ID matches the controller ID acquired from the PC 2, the process branches to “none” (Null) in step S 62. You may make it make it.

  On the other hand, if the controller ID 42 stored in the memory 11 of the amplifier 1 has no value (controller ID = Null), it means that there is no control main (another PC) that remotely controls the amplifier 1. means. The CPU 10 of the amplifier 1 determines that the amplifier 1 has already not received remote control from any PC (“None” in step S62). In this case, in step S64, the CPU 10 obtains a controller ID of the PC 2 and a virtual device associated with the amplifier 1 in the current project from the PC 2 (new control master) that has transmitted the “control request”. The area ID 46 of the registered area and the group information 36 (“RackTree”, “Feed Structure Tree”, and “User Defined Tree”) of the area are acquired, and the memory 11 of the amplifier 1 is acquired based on the acquired information. The controller ID 42, the area ID 43, and the group information 44 (position information of the amplifier in each group of “RackTree”, “Feed Structure Tree”, and “User Defined Tree”) are updated.

  In step S65, the CPU 10 sends the user information (account information 34 of all users) of the current project of the PC 2 and the virtual device associated with the amplifier 1 in the current project from the PC 2 (new control owner). The user role information 35 included in the registered area is acquired, and the UserInfo information 45 in the memory 11 of the amplifier 1 is updated based on the acquired account information 34 and user role information 35. As a result, the amplifier 1 obtains the same account information set in the PC 2 (current project currently open in the PC 2) that is the main controller of the own device, and the user role information of each user in the account. Will have.

  In step S <b> 66, the CPU 10 transmits a response (“controllable”) indicating that control is permitted to the PC 2 that transmitted the “control request”. At this time, the controller ID value updated in step S63 is also transmitted to the PC 2. This controller ID is the controller ID of the destination PC 2.

  Based on the response “controllable” transmitted to the PC 2 in the step S66 or the response “monitorable” transmitted to the PC 2 in the step S63, the CPU 20 of the PC 2 performs the process of step S31 in the synchronization process of FIG. Making a decision is as already described.

  In the user authentication in step S60, if the account of the user who has made the “control request” does not exist in the UserInfo information 45 stored in the amplifier 1, the CPU 10 of the amplifier 1 has failed in user authentication. In step S67, a response ("rejection") indicating that the control request is rejected is transmitted to the PC2 that has transmitted the "control request". Note that the user authentication in step S60 may consider matching with the area ID of the corresponding virtual device of the PC 2. That is, not only when the account information 34 of the user who made the request does not exist in the user info information 45 of the real device, but also when the area ID of the corresponding virtual device acquired from the PC 2 and the area ID of the real device do not match, You may make it branch to "NG" by step S61.

  FIG. 26 is a flowchart showing an example of the operation procedure of the process executed by the CPU 10 of the amplifier 1 in step S57 when the “open” request command transmitted from the PC 2 in step S40 of FIG. 21 is received. . In step S68, the CPU 10 sets the value of the controller ID 42 of its own device to “Null” and clears the UserInfo information 45. As a result, the amplifier 1 is in a free state in which no remote control is received from any user (PC 2). In step S69, the CPU 10 broadcasts a message on the network notifying that the own device has been “released” from the remote control.

  FIG. 27 is a flowchart showing an example of the operation procedure of the process executed by the CPU 10 of the amplifier 1 in step S57 when the PC 2 requests the provision of information related to the setting status and operation status of various data of the amplifier 1. is there. The CPU 10 returns information related to the setting status and operation status of the own device requested from the PC 2 to the requested PC 2 (step S70). The information returned to the PC 2 in step S70 is, for example, the model information of the amplifier 1, the operation data value of the amplifier 1, the input level of the acoustic signal, the output level, or the temperature level of the amplifying unit 14. Part of the data stored in the memory 11 of the own device (requested from the PC 2). It should be noted that information relating to the operational status of the amplifier 1 such as the level of the acoustic signal may be provided periodically to the PC 2 that is controlling or monitoring the amplifier 1. That is, the same type of operation (providing information to the PC 2) as in FIG. 27 may be executed without a command from the PC 2. 27, the account information 34 of the user who requested the information is included in the UserInfo information 45, and the authority indicated by the corresponding user role in the UserInfo information 45 is higher than the viewing authority. It may be executed according to conditions. In this case, a double authority check is performed on the amplifier side and the PC 2 side.

  FIG. 28 is a flowchart illustrating an example of an operation procedure of the process executed by the CPU 10 of the amplifier 1 in step S57 when the “operation request” command transmitted from the PC 2 in step S15 of FIG. 14 is received. In step S71, the CPU 10 determines whether or not to accept an operation request from the PC 2 that has requested the operation request. When the operation request is accepted in the determination of step S71, the controller ID of the requesting PC 2 that made the operation request matches the controller ID 42 (the controller ID of the control master) stored in the memory 11 of the own device. In other words, this is a case where the PC 2 that is the transmission source of the operation request is the main controller of the amplifier 1 and a user who is logged in to the PC 2 that is the request source has the right to control the amplifier 1. On the other hand, when the operation request is not accepted in the determination of step S71, the controller ID of the requesting PC 2 that made the operation request does not match the controller ID 42 stored in the memory 11 of the own device, that is, the operation This is a case where at least one of a case where a PC different from the request source PC 2 is the control main of the amplifier 1 and a case where a user who is logged in to the request source PC 2 has insufficient authority. If the operation request is not accepted (“NG” in step S71), this process ends. If the same ID as the controller ID of the PC 2 matches the controller ID of the amplifier memory 11, it is determined in step S 30 in FIG. 18 that the login user has the right to control the area, and the controller ID of the PC 2 is stored in the memory 11. This means that a double authority check is performed together with step S71.

  When the operation request is accepted (“OK” in step S71), the CPU 10 updates the data in its own memory 11 in accordance with the command (contents of operation) transmitted from the PC 2 in step S72, and in step S73. The state (setting change message) after the data update in step S72 is broadcast on the network. Here, the change state (setting change message) is broadcast not only to the PC 2 of the control owner but also to the entire network. This is to notify the PC 2). By this. The change state of the real device is reflected in the virtual devices of all PCs (controlling PC and other PCs) that have received the setting change message.

  FIG. 29 is a flowchart illustrating an example of an operation procedure of a timer operation executed by the CPU 10 of the amplifier 1 at predetermined time intervals. In step S74, the CPU 10 of the amplifier 1 performs active sensing on the PC2 (all) on the network, and as a result, if there is no response from the PC2 on the network for a predetermined time (“YES” in step S74), in step S75. The value of the controller ID 42 of the own device is set to “Null”, and the UserInfo information 45 is cleared. As a result, the CPU 10 of the amplifier 1 puts its own device in a free state where it does not receive remote control. In step S75, the CPU 10 of the amplifier 1 broadcasts a message on the network notifying that the own device has been “released” from the remote control.

  If the “power user” having the authority to edit the area to which the amplifier 1 belongs is logged on in the PC 2 that has received the release notification broadcast in the step S75, the CPU 20 of the PC 2 The synchronization process shown in FIG. 18 is executed to bring the amplifier 1 that has transmitted the release notification into an online state. The synchronization process executed at this time may be executed only for the one amplifier 1 that has transmitted the release notification, and the processes in and after step S26 may be executed, or for all amplifiers registered in the area. It may be.

  In the description of the synchronization processing of FIG. 18 above, the controller ID, area ID, group information, user information, and user are sent after the control request is transmitted in step S31 until the response is received in step S32. The roll information is transmitted to the amplifier 1, but in the process in response to the control request on the amplifier side in FIG. 25, the “controllable” response in step S66 before the information update in steps S64 and S65. If a reply is to be made, the timing for transmitting each piece of information from the PC 2 side may be an appropriate timing between steps S31 to S32 (setting of OnLine status).

  In the above embodiment, the area ID 46, the controller ID 40, the group information 36, the account information 34, and the user role are transferred from the PC 2 to the real device after the “control request” is transmitted in step S31 until the response is received. The information 35 is always transmitted, but the information on the real device side is “overwritten” with the transmitted information only when a response of “controllable” is received in step S 32, The data transfer on the network is useless. This part may be improved so that the information is sent from the PC 2 to the real device only when the determination is “controllable” after the determination in step S32. In that case, the processing order must be changed so that steps S64 to S66 in FIG. 25 are processed in the order of step S66, then step S64, and then step S65.

  In the above embodiment, there are a plurality of places where the authority check is duplicated on the amplifier side and the PC side. However, the authority check may be performed only on either the amplifier side or the PC side.

  In the above embodiment, the device ID 38 and the device ID 41 are composed of the MAC address of the amplifier 1 and the in-area ID. However, the device ID is preferably some ID information (fixed information) that identifies the amplifier. ) And the in-area ID are not limited to the configuration of the embodiment.

  Moreover, in the said Example, although the example which applies this invention to the acoustic system with which the power amplifier apparatus 1 and the personal computer 2 which controls this were network-connected was demonstrated, the structure of an acoustic system is the said Example. However, the present invention can be applied to any acoustic system in which an audio device and a control device that controls the audio device are network-connected. The audio equipment is not limited to the power amplifier device, and for example, an audio mixer, a recorder, or the like may be applied.

  In the remote control software of the above embodiment, a plurality of areas can be created. However, remote control software that uses only one area prepared in advance and cannot create a new area may be used.

  Further, in the tree display unit 50, the user can set various display modes of areas, groups, group configurations (trees), and display objects (virtual devices) representing amplifiers, such as icon shapes, display fonts, or display colors. In this way, in the PC that monitors the acoustic system, the various display modes of the display object representing the area, the group, the group configuration (tree), and the amplifier are the display modes set in the PC that controls the monitoring target. It can also be configured to be the same.

  As described above, according to this embodiment, the user info information 45 stored on the amplifier 1 side corresponds to at least one of a user who does not have an account and a user whose authority of the user info information 45 is insufficient. For example, since the amplifier 1 cannot be controlled or monitored from the PC 2, the amplifier 1 on the network can be protected by effectively preventing the amplifier 1 from being controlled or monitored by an unintended user. Excellent effect.

The block diagram which shows the structural example of the power amplifier network which comprises the acoustic system which concerns on one Embodiment of this invention. The block diagram which shows the electrical hardware structural example of a power amplifier. The block diagram which shows the electrical hardware structural example of a personal computer. The figure explaining the structural example of the data which the remote control software of a personal computer prepares. The figure which shows the structure of the user role information of FIG. 4 in detail. The figure explaining the structural example of the data prepared in the memory of amplifier. The figure which shows the example of a display of the "basic screen" of the remote control software displayed on the display of a personal computer. (A)-(c) is a figure which shows the structural example of the tree display part in the basic screen of FIG. 7, (a) is a device tree, (b) is a rack group tree, (c) is a feed structure group. tree. (A) And (b) is a figure which shows the structural example of the area | region of the level display part in the basic screen of FIG. 7, a state display part, and an attenuator operation part, Comprising: (a) is the amplifier selected separately (B) is a screen configuration example when an area or group is selected. The flowchart which shows the outline | summary of the flow of the operation | movement procedure of the remote control software performed with a personal computer. 6 is a flowchart showing an example of an operation procedure executed by a personal computer when an instruction to load a project file is given. The flowchart which shows an example of the operation | movement procedure performed with a personal computer when the store of a project file is instruct | indicated. The flowchart which shows an example of the operation | movement procedure performed with a personal computer, when a tree structure is edited in the tree display part of the basic screen. The flowchart which shows an example of the operation | movement procedure performed by the personal computer when an amplifier (virtual device) is edited on the basic screen, and when the amplifier is in an online state. The flowchart which shows an example of the operation | movement procedure performed by the personal computer when an amplifier (virtual device) is edited on the basic screen, and the amplifier is in an offline state. The flowchart which shows an example of the operation | movement procedure performed with a personal computer when the account of a project file is edited. The figure which shows the structural example of the "synchronized dialog" displayed on a display, when an "On-Line" button image is operated on a basic screen. The flowchart which shows an example of the operation | movement procedure performed with a personal computer, when an online instruction | indication instruction button is operated by the "synchronized dialog". The figure which shows the structural example of the "synchronization direction selection screen" displayed on a display in order to make a user select the direction of a synchronization (synchronization) in the synchronization process of FIG. The figure which shows the structural example of the "warning dialog" displayed on a display, when an error generate | occur | produces during the synchronization process of FIG. The flowchart which shows an example of the operation | movement procedure performed with a personal computer, when an offline instruction | indication button is operated by the "synchronized dialog". The flowchart which shows an example of the operation | movement procedure of the timer operation | movement performed with a personal computer. The flowchart which shows an example of the operation | movement procedure performed with a personal computer when matching (matching) of a virtual apparatus and a real apparatus should be performed. Flowchart showing the outline of a flow of the operation procedure relating to the control of the amplifier to be performed by the amplifier. The flowchart which shows an example of the operation | movement procedure performed with an amplifier, when a control request is received from a personal computer. The flowchart which shows an example of an operation | movement procedure with amplifier, when the open request | requirement is received from a personal computer. The flowchart which shows an example of an operation | movement procedure with amplifier, when the information provision request | requirement is received from a personal computer. The flowchart which shows an example of an operation | movement procedure with amplifier, when the operation request is received from a personal computer. The flowchart which shows an example of the operation | movement procedure of the timer operation | movement performed with amplifier.

Explanation of symbols

DESCRIPTION OF SYMBOLS 1 Power amplifier apparatus (acoustic equipment) 2 Personal computer (control apparatus) 10 CPU, 11 Memory, 12 Audio I / O 13 Signal processing part (DSP), 14 Power amplification part, 15 User interface, 16 Communication I / F , 20 CPU, 21 memory, 22 HDD, 23 communication I / F audio, 24 user interface, 31 project library, 32 project file, 33 area information, 34 account information, 35, user role information, 36 group information, 37 device information , 38 Device ID, 39 OnLine Status Information, 40 Controller ID, 41 Device ID, 42 Controller ID, 43 Area ID, 44 Group Information, 45 UserInfo Information, 50 Tree Display, 52 Le display unit, 53 a state display unit, 54 an attenuator operating unit, 67 online instruction button image, 68 offline instruction button image

Claims (8)

An acoustic system configured by a network connecting a plurality of acoustic devices and at least one control device for controlling the plurality of acoustic devices,
The controller is
Display means;
Virtual device information including operation data for controlling each acoustic device corresponding to each of the plurality of acoustic devices, a virtual device ID for specifying virtual device information, and group information indicating a group to which the virtual device information belongs First storage means for storing
Based on the group information stored in the first storage means, a plurality of virtual device information is divided into groups to which the virtual device information belongs and displayed on the display means, and operation data included in the virtual device information is displayed on the display means. Display control means for performing display control,
Each of the plurality of acoustic devices is
A second storage means for storing an acoustic device ID for identifying the acoustic device, group information indicating a group to which the corresponding virtual device information belongs, and operation data for controlling the operation of the acoustic device;
The control device further includes:
The audio device ID stored in the second storage unit is received from each of the plurality of audio devices, and based on the received audio device ID and the virtual device ID stored in the first storage unit, virtual device information and audio Association means for associating devices;
When the acoustic device associated with the virtual device information is to be set as a remote control target, the group information of the virtual device information stored in the first storage unit is written in the second storage unit of the corresponding acoustic device. First synchronization control means;
When the operation data of the virtual device information stored in the first storage unit is changed for the audio device set as the remote control target by the first synchronization control unit, the second storage unit of the corresponding audio device Remote control means for changing stored operation data by remote control;
Wherein the acoustic device that associates with the virtual device information when to be configured to be monitored, receives the group information stored in the second storage means of sound equipment monitored, first memory based on the group information received the Second synchronization means for performing control to update the display control means to group the virtual device information in the display means by updating the group information of the means;
When the operation data stored in the second storage unit in the audio device is changed for the audio device set to be monitored by the second synchronization unit, the corresponding virtual device information stored in the first storage unit And a monitor control means for changing the operation data in the same manner. Remote control means provided in the control device, linked to change in the operation data of one virtual device information stored in the first storage unit, the operation data of other virtual devices belonging to the same group as the virtual device information The control is performed by changing the operation data stored in the second storage means of the plurality of acoustic devices corresponding to the virtual device information and other virtual devices belonging to the same group by remote control. The acoustic system according to claim 1. Before Symbol control device,
In the first storage means stores the display control information for controlling the display form when displaying virtual device information on the display means,
The display control means performs control to display in a display mode based on display control information stored in the first storage means ,
The first synchronization means writes the display control information of the virtual device information stored in the first storage means to the second storage means of the corresponding acoustic device; and
The second synchronization means receives the display control information stored in the second storage means of the acoustic device to be monitored, and based on the received display control information, the virtual device information stored in the first storage means By updating the display control information, control is performed to cause the display control means to update the display mode of the virtual device on the display means.
Is,
Each of the plurality of acoustic devices is
Wherein the second storage means, an acoustic system according to claim 1 or 2, characterized in that <br/> you stores display control information of the virtual device information the corresponding. Before Symbol control device,
In the first storage means stores one or more areas information indicating one or a plurality of areas,
Comprising registration means for registering virtual device information in one area of one or more areas indicated by one or more area information stored in the first storage means;
The association means associates the virtual device information with the acoustic device based on the received acoustic device ID , the virtual device ID and the area information ,
Further, for the acoustic device that could not be associated with any virtual device information by the associating means, corresponding virtual device information is newly created, and the created virtual device is stored in the display means as a virtual outside area registration. The acoustic system according to any one of claims 1 to 3, further comprising a second display control means for displaying as device information.   A program for causing a computer to function as the control device in an audio system including a network in which a plurality of audio devices and at least one control device for controlling the plurality of audio devices are connected. The control device includes virtual device information including operation data for controlling each acoustic device corresponding to each of the plurality of acoustic devices, a virtual device ID for specifying virtual device information, and virtual device information. First storage means for storing group information indicating a group, wherein each of the plurality of acoustic devices includes an acoustic device ID for identifying the acoustic device, and group information indicating a group to which the corresponding virtual device information belongs. And second storage means for storing operation data for controlling the operation of the audio equipment. ,
  The program is stored in the computer.
  Grouping of a plurality of virtual device information based on the group information stored in the first storage means, and a display step of displaying the operation data stored in the first storage means on a display means;
  The audio device ID stored in the second storage unit is received from each of the plurality of audio devices, and based on the received audio device ID and the virtual device ID stored in the first storage unit, virtual device information and audio An associating step for associating devices;
  When the acoustic device associated with the virtual device information is to be set as a remote control target, the group information of the virtual device information stored in the first storage unit is written in the second storage unit of the corresponding acoustic device. A first synchronization step;
  When the operation data of the virtual device information stored in the first storage unit is changed for the audio device set as the remote control target, the operation data stored in the second storage unit of the audio device is remotely controlled. Remote control step to be changed by
  When the acoustic device associated with the virtual device information is to be set as a monitoring target, the group information stored in the second storage means of the monitoring target acoustic device is received, and the first storage is performed based on the received group information. A second synchronization step of updating the grouping of the virtual device information in the display means by updating the group information of the means;
  When the operation data stored in the second storage unit is changed in the audio device set as the monitoring target, the operation data of the corresponding virtual device information stored in the first storage unit is Monitor control step to be changed in the same way
A program characterized by having executed. In the computer,
  In the remote control step, the operation data of one virtual device information stored in the first storage means is linked to the change of the operation data of another virtual device belonging to the same group as the virtual device information, Changing the virtual device information and operation data stored in the second storage means of a plurality of acoustic devices corresponding to other virtual devices belonging to the same group by remote control
The program according to claim 5, wherein the program is executed. The first storage means included in the control device further stores display control information for controlling a display mode when displaying the virtual device information, and the virtual device information is displayed in a display mode based on the display control information. And the second storage means provided in each of the plurality of audio devices further stores display control information of the corresponding virtual device information,
The program is stored in the computer.
In the display step, displaying in a display mode based on display control information stored in the first storage means;
In the remote control step, writing the display control information of the virtual device information stored in the first storage unit to the second storage unit of the corresponding acoustic device;
In the monitor control step, display control information stored in the second storage means of the acoustic device to be monitored is received, and display control of the virtual device information stored in the first storage means is based on the received display control information Updating the display mode of the virtual device in the display means by updating the information;
The program according to claim 5 or 6, wherein the program is executed . The first storage means provided in the control device further stores one or a plurality of area information indicating one or a plurality of areas,
The program is stored in the computer.
A registration step of registering virtual device information in one of the one or more areas indicated by the one or more area information stored in the first storage means;
In the associating step, associating the virtual device information with the acoustic device based on the received acoustic device ID and the virtual device and area information;
For the acoustic device that could not be associated with any virtual device information in the association step, corresponding virtual device information is newly created, and the created virtual device is not registered in the display means as virtual device information outside the area registration. A second display step for displaying as
The program according to claim 5, wherein the program is executed .

Images