SOUND DEVICE, ACOUSTIC DEVICE SETTING PROCEDURE AND PROGRAM

Abstract

A sound device comprises an acoustic unit and a control unit. The control unit is configured to receive a trigger request and a condition request. The control unit is further configured to receive an action corresponding to the trigger request. It is also configured to associate the trigger request with the action and to associate a macro main, which displays the trigger request and its associated action, with the condition request. Finally, the control unit is configured to determine that the condition request is met and to execute the action when the trigger request is met.

Description

Technical area

[0001] An embodiment according to the present invention relates to an acoustic device setting method, an acoustic device setting apparatus and a program.

[0002] “Avid VENUE | S6L System” [online], accessed on June 16, 2023, at<URL: https: / / resources.avid.com / SupportFiles / VENUE / VENUE_S6L_System_Guide_v7.0.1.pdf> >, specifies an audio mixer in which, by configuring an event to set any action for a trigger and executing the set action concurrently with performing a trigger operation, any action is also executed concurrently with performing a trigger operation. Summary

[0003] An embodiment of the present invention aims to provide an acoustic device setting method that can set a fixed progression more variably when a certain requirement is met.

[0004] An acoustic device setting method includes receiving a trigger request, receiving a condition request, receiving an action corresponding to the trigger request, associating the trigger request with the action, and associating a macro main showing the associated trigger request and action with the condition request, and determining that the condition requirement is met, and executing the action when the trigger request is met.

[0005] The acoustic device setting method can set a fixed progression when a certain requirement is met, or more variable. Brief description of the drawings Fig. 1 is a block diagram showing a configuration of an audio mixer 1. Fig. 2 is a block diagram showing a functional configuration of a signal processor. Fig. 3 is a block diagram showing a functional configuration of an input channel 302, a stereo bus 303, and a mix bus 304. Fig. 4 is an external view of a cabinet of the audio mixer 1. Fig. 5 is a flowchart showing a progression of an acoustic device setting process to be performed by a CPU 206. Fig. 6 is an example of a macro editing screen displayed on a display 201 when a callback operation of a macro editing function is received. Fig. 7 is a flowchart showing a progression of the CPU 206 when a macro function is enabled. Fig. 8 is a front view of the audio mixer 1 when a condition request is met and a trigger request is met. Fig. 9 is an example of a macro editing screen 71 when a reverse action is received. Fig. 10 shows an example of a macro editing screen 71 when the reverse action is received. Fig. 11 is a flowchart showing a progress of the acoustic device setting process to be executed by the CPU 206. Fig. 12 is a flowchart showing a progress of the acoustic device setting process to be executed by the CPU 206. Fig. 13 is a front view of the audio mixer 1 when the condition request is met and the trigger request is met. Fig. 14 is a front view of the audio mixer 1 when the condition request is met and the trigger request is met. Fig. 15 is a flowchart showing a progression of the acoustic device setting process when a selection of ON / OFF of an AutoSync function is received. Fig. 16 shows an example of the macro editing screen 71 when the selection of ON / OFF of the AutoSync function is received. Fig. Figure 17 is a front view of Audio Mixer 1 when the AutoSync function is OFF. Fig. Figure 18 is a front view of Audio Mixer 1 when the AutoSync function is ON. Detailed description

[0006] Fig. Figure 1 is a block diagram showing a configuration of an audio mixer 1. The audio mixer 1 is an example of an acoustic device. The audio mixer 1 includes components such as a display 201, an operator 202, an audio I / O 203, a signal processor 204, a network interface 205, a CPU 206, a flash memory 207, and a RAM 208.

[0007] These components are connected to each other via a bus 171. In addition, the audio I / O 203 and the signal processor 204 are also connected to a waveform bus 172 to transmit a digital audio signal.

[0008] The CPU 206 is a control device that controls the progress of the audio mixer 1. The CPU 206 performs various types of progress by reading a predetermined program stored in the flash memory 207, which is a storage medium for the RAM 208, and executing the program. Note that the program may also be stored on a server. The CPU 206 can download the program from the server via a network and execute the program.

[0009] The signal processor 204 includes a DSP for performing various types of sound processing, such as mixing processing. The signal processor 204 performs signal processing, such as effect processing, level adjustment processing, and mixing processing, on the audio signal received via the network interface 205 or the audio I / O 203. The signal processor 204 outputs a digital audio signal on which the signal processing has been performed via the audio I / O 203 or the network interface 205.

[0010] Fig. 2 is a block diagram showing a functional configuration of the signal processing performed in the signal processor 204, the audio I / O 203 (or the network interface 205), and the CPU 206. As shown in Fig. 2, the signal processing is functionally performed by an input patch 301, an input channel 302, a stereo bus 303, a mix bus 304, an output channel 305 and an output patch 306.

[0011] Input patch 301 receives an audio signal from a microphone, a musical instrument, a musical instrument amplifier, or the like. Input patch 301 supplies the received audio signal to each channel of input channel 302. Fig. Figure 3 is a block diagram showing a functional configuration of the input channel. Each channel of the input channel 302 receives the audio signal from the input patch 301 and performs signal processing on the audio signal.

[0012] Fig. 3 is a block diagram showing a functional configuration of the input channel 302, the stereo bus 303, and the mix bus 304. For example, a first input channel and a second input channel each include an input signal processor 350, a fader 351, a pan (panorama) 352, and a transmit level adjustment circuit 353. Other input channels not shown have the same configuration.

[0013] Input signal processor 350 performs effect processing such as an equalizer, compressor, level adjustment, or the like. Fader 351 adjusts the gain of each input channel.

[0014] Fig. 4 is a front view of the audio mixer 1. The display 201 is located on the upper front side of a cabinet. A control panel area 25 is located on the lower front side of the cabinet. A channel strip section 27 and a user-defined key area 51 are located in the control panel area 25.

[0015] The channel strip section 27, for example, comprises eight input channel sections and one master section. A plurality of physical control devices, including a slider, a switch, and a knob, are arranged in each channel section. The slider corresponds to the fader 351 of Fig. 3. A user of audio mixer 1 adjusts the gain of a corresponding input channel by changing the position of the slider.

[0016] In this embodiment, a plurality of six user-defined buttons (hereinafter referred to as BD buttons) are arranged in the user-defined button area 51. A user-defined button functions as a physical controller that executes a function optionally assigned to the audio mixer 1. Furthermore, the user-defined button area 51 can switch a plurality of banks and assign any six functions to each bank.

[0017] The knob of each channel section in the channel strip section 27 corresponds, for example, to the Pan 352 of Fig. 3. The user of audio mixer 1 adjusts the left-right balance of a stereo by turning the knob clockwise or counterclockwise. The audio signal distributed by pan 352 is sent to the stereo bus 303. Alternatively, the knob corresponds, for example, to the transmit level adjustment circuit 353 of Fig. 3. The user of the audio mixer 1 sets a transmit level to the mixing bus 304 by turning the knob clockwise or counterclockwise. Alternatively, the slider can also function as an operator that sets the transmit level to the mixing bus 304. In this case, the slider corresponds to the transmit level adjustment circuit 353 of Fig. 3.

[0018] Stereo bus 303 is a bus corresponding to a main speaker in a hall or conference room. Stereo bus 303 mixes the audio signal emitted from each input signal. Stereo bus 303 outputs the mixed audio signal to output channel 305.

[0019] Mix bus 304 is a bus for sending a mixed audio signal from one or more input channels to a specific acoustic device, such as a monitor speaker or monitor headphones. Mix bus 304 outputs the mixed audio signal to output channel 305.

[0020] The output channel 305 performs effect processing such as an equalizer or compressor, level adjustment processing, or the like on the audio signal output from the stereo bus 303 and the mix bus 304. The output channel 305 outputs the mixed audio signal, on which the signal processing has been performed, to the output patch 306.

[0021] The output patch 306 assigns each channel of the output channel to one of a plurality of ports serving as an analog output port or a digital output port. As a result, the audio signal on which signal processing has been performed is fed to the audio I / O 203 or the network interface 205.

[0022] Fig. 5 is a flowchart showing the progression of an acoustic device setting process to be executed by the CPU 206. The CPU 206 proceeds to execution when a callback operation of a macro editing function is received. When a callback operation of the macro editing function is received, the CPU 206 displays a macro editing screen on the display 201 (S10).

[0023] Fig. 6 shows an example of a macro editing screen 71 displayed on the display 201 when the callback operation of the macro editing function is received. A macro displays the entire macro function, including a trigger, an action, a reverse action, a condition, an auto-sync function, or an activation switch (the condition, the auto-sync function, or the like will be described later). The macro function is a function for executing a predetermined operation (such as an action) when a state of a device satisfies a specific requirement (such as a trigger request) in the audio mixer 1. The macro editing screen 71 includes a management number display 72, a macro name input area 73, a trigger request input area 74, an activation switch 75, an action input area 76, and a condition request input area 77.

[0024] The audio mixer 1 receives a trigger request on the macro editing screen 71 (S11). In the example of Fig. 6, a user inputs a trigger request to the trigger request input area 74 displayed on the left side of the macro editing screen 71. The trigger request mainly corresponds to a state of a physical control device for designating sound processing for inputting, mixing, or outputting an audio signal. However, in the present description, the trigger request is entirely related to a state of the audio mixer 1. For example, a case where the power consumption of the audio mixer 1 reaches a certain value, a case where the CPU resource usage is greater than or equal to a predetermined value, or the like can also be input as the trigger request.

[0025] Fig. Figure 6 shows an example in which the state of the physical control device for designating a sound processing for an input of an audio signal is input as the trigger request. In particular, in Fig. 6 as the trigger request, a case where in the input channel for parameters (“channel parameter” in the figure) an ON switch (“ON” in the figure) of a fader of the first input channel (“input channel 1” in the figure) is turned on (“=ON” in the figure) is input.

[0026] The CPU 206 receives an action corresponding to the trigger request (S12). In the example of Fig. 6, the user enters an action in the action input area 76 displayed on the right side of the macro editing screen 71. In the example of Fig. 6, as the action, such a progression is entered that in a cue button of the input channel within the parameters (channel parameters in the figure) the ON switch (ON in the figure) of the cue button (input channel 1 Cue A in the figure) of the first input channel is turned on (“=ON” in the figure).

[0027] The CPU 206 further receives a condition request (S13). In other words, the user enters a trigger request, a condition request, and an action. In the example of Fig. 6, a case where in the BD key (“Keys” in the figure) of user definitions (“User-defined” in the figure) the number 1 of bank A (“BDT Bank A No. 1” in the figure) is pressed (“=PRESSED” in the figure) is entered as the condition requirement.

[0028] The CPU 206 associates the trigger request with the received action and associates the condition request with a macro main (S14). For example, when an ON operation of the activation switch 75 is received, the CPU 206 associates the trigger request with the action and associates the condition request with the macro main. Alternatively, when an ON operation of an execution switch ("EXEC" in the figure) of the action input area 76 is received, the CPU 206 associates the trigger request with the action and associates the condition request with the macro main. The macro main shows the trigger and the associated action, as well as the trigger and the associated reverse action that are part of the macro (the activation switch 75 shows a switch that toggles between enabling / disabling the macro main).An association here means, for example, that with respect to an operation A (a received trigger request) and an operation B (a received action) that is different from operation A, a progression is created on a system for automatically executing operation B under the condition that operation A is performed.

[0029] The CPU 206 performs the associated action when the condition requirement is met and the state of the acoustic device satisfies the trigger requirement. Fig. Figure 7 is a flowchart showing the operation of CPU 206. First, CPU 206 determines whether the state of an acoustic device satisfies the condition requirement (S201). If it determines that the condition requirement is not met (NO in S201), CPU 206 repeats the determination from the beginning.

[0030] The CPU 206, when it is determined that the condition requirement is met (YES in S201), proceeds to the determination of S21 and executes an action (S22).

[0031] Fig. Fig. 8 is a front view of the audio mixer 1 when a condition request is met and a trigger request is met. Fig. The trigger request shown in Figure 6 is a request that the ON switch of the fader of the first input channel is switched on. Fig. 6 received condition request is a request that the BD key of number 1 of bank A is pressed. So if as in Fig. 8, when the BD button of number 1 of bank A is pressed and the ON switch of the fader of the first input channel is also turned on, the CPU 206 turns on the CUE button (“CH1 CUE” in the figure) of the first input channel.

[0032] It should be noted that if the condition requirement is not met, the CPU 206, as in Fig. 6 can turn off the activation switch 75. As a result, the user can easily understand a state in which the action is not executed even if the trigger request is met.

[0033] As described above, the CPU 206 activates the macro main only when the condition requirement is met. The CPU 206 performs no action if the condition requirement is not met, regardless of whether the trigger requirement is met or not. In other words, the condition requirement works in such a way that the macro main is deactivated if the condition requirement is not met. This allows the user to easily implement a more complex setting. For example, in the example of Fig. 6 The main macro is only activated while number 1 of bank A of the BD key is pressed. Furthermore, the user prepares multiple macros, each with different trigger requirements and actions or reverse actions, and, for example, sets a BD key color for the conditional requirement of each macro. Then, the user also prepares a macro for changing the color of the BD key when the BD key is pressed. In this case, the macro function of changing the progression each time the BD key is pressed can be achieved.

[0034] This allows for a new user experience to be provided for the user because the user can set a fixed progression when a certain requirement is met in a more variable way.

[0035] Fig. 9 and Fig. 10 shows an example of the macro editing screen 71 when the reverse action is received. When a user selects a reverse action tab (“REVERSE ACTION” in the figure) in the action input area 76 of Fig. 9, the CPU 206 displays the macro editing screen 71, which contains the Fig. 10 receives the reverse action shown. Fig. 11 and Fig. 12 are flowcharts showing a progression of the acoustic device setting process to be executed by the CPU 206. The same reference numerals are used for the same configurations as in Fig. 5, although a repeated description is omitted here.

[0036] In the example of Fig. 9 and Fig. 10, the user enters an action and a reverse action into the action input area 76 displayed on the right side of the macro editing screen 71. In the example of Fig. 9, the action is a progression such as changing the display color (label / color) of bank A number 1 (“BDT Bank A No. 1” in the figure) to blue (“=Blue” in the figure) in the BD keys (“Keys” in the figure) of the user definitions (“User-defined” in the figure). In the example of Fig. 10, as the reverse action, such a progression that in the BD key (“Keys” in the figure) of the user definitions (“User Defined” in the figure) the display color (label / color) of the number 1 of the bank A (“BDT Bank A No. 1” in the figure) is changed to red (“=Red” in the figure) is entered.

[0037] The CPU 206 receives the reverse action to be performed when the trigger request is not met on the macro editing screen 71 (S15). The CPU 206 associates the trigger request with the reverse action and associates the condition request with the macro main (S16). For example, when the ON operation of the activation switch 75 is received, the CPU 206 associates the trigger request with the reverse action and associates the condition request with the macro main. Alternatively, when the ON operation of the execution switch (“EXEC” in the figure) of the action input section 76 is received, the CPU 206 associates the trigger request with the reverse action and associates the condition request with the macro main. The CPU 206 executes when the state of the acoustic device does not meet the trigger request (NO in S21 of Fig. 12), the associated reverse action from (S23).

[0038] Fig. 13 is a front view of the audio mixer 1 when the condition request is met and the trigger request is met. Fig. 14 is a front view of the audio mixer 1 when the condition request is met and the trigger request is not met. Fig. 9 received trigger request is a request that the ON switch of the fader of the first input channel is switched ON. So if as in Fig. 13, the ON switch of the fader of the first input channel is turned off, the CPU 206 changes the display color of number 1 of bank A of the BDT bank in the user-defined key area 51 to red.

[0039] Fig. 14 is a front view of the audio mixer 1 when the trigger request is not met. Fig. 10 received trigger request is a request that the ON switch of the fader of the first input channel is switched on. So if as in Fig. 9, the ON switch of the fader of the first input channel is turned off, the CPU 206 changes the display color of number 1 of bank A of the BDT bank in the user-defined key area 51 to red.

[0040] If the user clicks an action tab (“ACTION” in Fig. 8) in the action input area 76 in the state of Fig. 9, the CPU 206 displays the Fig. 10 shows the macro editing screen 71.

[0041] In other words, the CPU 206 receives a selection of a first reception state (the macro editing screen 71 of Fig. 9), in which a setting of the action corresponding to the trigger request is received, or a second reception state (the macro editing screen 71 of Fig. 10), in which a setting of the reverse action corresponding to the trigger request is received, in a state in which the first reception state is selected, receives the setting of the action corresponding to the trigger request, associates the trigger request with each of the received action and the reverse action, in a state in which the second reception state is selected, receives the setting of the reverse action corresponding to the trigger request, and associates the trigger request with each of the received reverse action and the action.

[0042] It should be noted that the trigger request can receive a variety of requests. For example, as in Fig. 9 and Fig. 10, the trigger request input area 74 has input fields for a plurality of trigger requests. The user enters a request into each of the plurality of input fields. The trigger request input area 74 also has a logical expression input field ("OR" in Fig. 6 and Fig. 9). The user enters a logical expression in the Logical Expression input field. For example, if Fig. 6 and Fig. 9, the user enters OR, the CPU 206 determines that the trigger request is satisfied if any of the entered requirements are met. For example, if the user enters AND, the CPU 206 determines that the trigger request is satisfied if all of the entered requirements are met.

[0043] In addition, the user can also select a request to be activated from among the plurality of requests entered by the user. The trigger request input area 74 has a checkbox. The CPU 206 determines whether the trigger request is satisfied or not based only on the request whose checkbox was checked by the user, in combination with a logical expression.

[0044] In addition, the conditional request can also receive multiple requests. Furthermore, when multiple requests are received, the conditional request can receive the input of a logical expression.

[0045] The action and the reverse action can each receive the plurality of requests. Furthermore, the action and the reverse action can each select a request to activate from the plurality of input requests.

[0046] In the example described above, the CPU 206 receives the trigger request, the action, or the reverse action from the user. If in the macro editing screen 71 of Fig. 9 If the user first selects the Reverse Action tab in the action input area 76, the CPU 206 can copy an entered action to the reverse action. However, the CPU 206 changes the reverse action, which only differs in value (to the right of "=" in Fig. 9 and Fig. 10).

[0047] As described above, the audio mixer 1 according to this embodiment can provide a more convenient acoustic device setting method that can collectively set a fixed progression when a certain requirement is met and a fixed progression when the requirement is no longer met. For example, although the Fig. 13 and the action shown in Fig. 14 can be received as two different macros, respectively, the audio mixer 1 according to this embodiment can set, with respect to a trigger request (the ON switch of the fader of the first input channel is ON), both an action when the trigger request is met and a reverse action when the trigger request is not met. This can provide a new user experience for the user because the user can collectively set a progression when the trigger request is met and a progression when the trigger request is not met with respect to a single trigger request.

[0048] Fig. Figure 15 is a flowchart illustrating the progression of the acoustic device setting process when an ON / OFF selection of the AutoSync function is received. The same reference numerals are used for the same progression as in Fig. 7, although a repeated description is omitted here.

[0049] The CPU 206 first receives an ON / OFF selection of the AutoSync function (S30). The AutoSync function is a function for matching an action to be performed by a trigger request with a state of an acoustic device. Fig. Figure 16 shows an example of the macro editing screen 71 when the AudioSync ON / OFF selection is received. The macro editing screen 71 of Fig. 16 further includes an AutoSync function ON / OFF switch 78, which is a physical control device for receiving ON / OFF of the AutoSync function, on the activation switch 75. The user actuates the AutoSync function ON / OFF switch 78, which is a physical control device, and inputs a selection of ON / OFF of the AutoSync function. The activation switch 75 is a first physical control device that receives an actuation for activating an action-executing progression, the AutoSync function ON / OFF switch 78 is a second physical control device that receives an ON / OFF of the AutoSync function, and the first physical control device and the second physical control device are installed in close proximity to each other.

[0050] Then, the CPU 206 receives an operation (an operation for activating the macro main) for activating the action-executing progression when a trigger request is met (S31). The CPU 206 activates the macro main when the ON operation of the activation switch 75 is received or the ON operation of the execution switch ("EXEC" in the figure) of the action input section 76 is received.

[0051] The CPU 206 receives the actuation from S31 to S30. In other words, the ON / OFF selection of the AutoSync function for synchronizing the action to be performed by a trigger request with the state of an acoustic device prior to the actuation is received for activating the macro main.

[0052] Then, the CPU 206 determines whether the AutoSync function is ON or not when the macro main is enabled (S32). The CPU 206 determines whether the trigger request is met or not when the AutoSync function is ON (S21), and executes the corresponding action (S22) or the reverse action (S23). In short, when the AutoSync function is ON, the CPU 206 executes the corresponding action when the trigger request is met, and executes the corresponding reverse action when the trigger request is not met.

[0053] On the other hand, the CPU 206 does nothing when activating the Macro Main if the AutoSync function is OFF (NO in S32).

[0054] Fig. Figure 17 is a front view showing an example of a state of Audio Mixer 1 before activating the Macro Main. In the example of Fig. 17, the audio mixer 1 is in a state where the ON switch of the fader of the first input channel is OFF and the display color of number 1 of bank A in the BD button of the user definitions is blue.

[0055] However, if in the macro editing screen 71 of Fig. 16 When the ON switch of the first input channel fader is turned on, the display color of number 1 of Bank A in the BD button of the user definition is changed to blue, which is set for the macro main. In other words, when the ON switch of the first input channel fader is turned off, the user desires such a progression that the display color of number 1 of Bank A in the BD button of the user definition is changed to a color other than blue.

[0056] In such a state, if the user performs the operation to activate the macro main while the AutoSync function is OFF (or no AutoSync function is provided), hypothetically, even if the trigger request is not met, in the BD button of the user definitions, the display color of the number 1 of bank A is still blue, so the user's intention does not match the state of the audio mixer 1.

[0057] Fig. Figure 18 is a front view of the audio mixer 1 when the AutoSync function is ON. If the user performs the operation to activate the Macro Main while the AutoSync function is ON, the CPU 206 performs a reverse action. For example, if the reverse action as shown in Fig. 10 is a progression for changing the display color of number 1 of bank A in the BD key of the user definitions to red, the CPU 206 changes the display color of number 1 of bank A in the BD key to red as shown in Fig. 18. As a result, in the BD button in the user definitions, the display color of number 1 of bank A is changed to a color other than blue, so that the user's intention corresponds to the state of audio mixer 1.

[0058] It should be noted that in the above-described embodiment, when the AutoSync function is ON, the CPU 206 matches the action performed by the trigger request with the state of the acoustic device by executing the reverse action. However, the CPU 206 may also match an action performed by a trigger request with the state of the acoustic device by executing a progression other than the reverse action. For example, even if the reverse action is not set, the CPU 206 may change the display color of number 1 of bank A in the BD button to red. In this case, too, in the BD button in the user definitions, the display color of number 1 of bank A is changed to a color other than blue, so that the user's intention corresponds to the state of the audio mixer 1.In any case, the CPU 206 matches the action with the state of the acoustic device not by changing the trigger request, but by changing the state of the acoustic device to match the trigger request.

[0059] This allows Audio Mixer 1, when the AutoSync function is ON, to synchronize the trigger request action with the state of a device, thus avoiding any unpleasant experience for the user.

[0060] The above description of various embodiments is to be understood in all respects as exemplary and does not limit the present invention. The scope of the invention is not defined by the above exemplary embodiments, but rather by the following claims. The embodiments described herein may be modified in various ways without thereby departing from the scope of the invention. List of reference symbols 1 audio mixer 25 Control panel area 27 Canal section 51 Custom Key Area 71 Macro editing screen 72 Administrative number display 73 Macro name input area 74 Trigger request input area 75 activation switches 76 Action input area 77 Conditional request input area 78 AutoSync function ON / OFF switch 171 buses 172 Waveform bus 201 ad 202 Operator 203 Audio I / O 204 Signal processor 205 Network interface 206 CPU 207 Flash memory 208 RAM 301 input patch 302 input channel 303 Stereo bus 304 mixed bus 305 Output channel 306 Output patch 350 Input Signal Processor 353 Transmit level adjustment circuit QUOTES CONTAINED IN THE DESCRIPTION

[0000] This list of documents submitted by the applicant was generated automatically and is included solely for the convenience of the reader. This list is not part of the German patent or utility model application. The DPMA assumes no liability for any errors or omissions. Cited non-patent literature

[0000] Avid VENUE | S6L System” [online], accessed on June 16, 2023, at<URL: https: / / resources.avid.com / SupportFiles / VENUE / VENUE_S6L_System_Guide_v7.0.1.pdf>

[0002]

Claims

[1] A sound device comprising: an acoustic device, and a control device configured to: Receiving a trigger request, Receiving a condition request, Receiving an action corresponding to the trigger request, Associating the trigger request with the action, and associating a macro main that shows the associated trigger request and the action with the condition request, and Determine that the condition requirement is met and perform the action when the trigger requirement is met. [2] The sound device according to claim 1, wherein the control device is further configured to: Receiving a reverse action that is performed if the trigger request is not met, Associating the trigger request with the reverse action, and Check that the condition requirement is met and then perform the reverse action if the trigger requirement is not met. [3] The sound device of claim 1, wherein the trigger request corresponds to a state of a physical controller configured to designate sound processing for inputting, mixing, or outputting an audio signal. [4] The sound device according to any one of claims 1 to 3, wherein the controller is further configured to receive the trigger request, the action, and the condition request from a user. [5] An acoustic device setting method comprising: Receiving a trigger request, Receiving a condition request Receiving an action corresponding to the trigger request, Associating the trigger request with the action, and associating a macro main that shows the associated trigger request and the action with the condition request, and Determine that the condition requirement is met and perform the action when the trigger requirement is met. [6] The acoustic device setting method according to claim 5, further comprising: Receiving a reverse action to be performed if the trigger request is not met, Associating the trigger request with the reverse action, and associating a macro main showing the associated trigger request and the reverse action with the condition request, and Check that the condition requirement is met and then perform the reverse action if the trigger requirement is not met. [7] The acoustic device setting method according to claim 5, wherein the trigger request corresponds to a state of a physical control device for designating sound processing for inputting, mixing, or outputting an audio signal. [8] The acoustic device setting method according to any one of claims 5 to 7, wherein the trigger request, the action and the condition request are received from a user. [9] An acoustic device setting method according to any one of claims 5 to 7, further comprising: Receiving an actuation for activating a progression that performs the action when the trigger request is met, and Receiving an ON / OFF selection of an AutoSync function that compares the action performed by the trigger request with a state of an acoustic device before receiving the actuation to activate progression. [10] A program that, when executed, causes an acoustic device setting device to: Receiving a trigger request, Receiving a condition request, Receiving an action corresponding to the trigger request, Associating the trigger request with the action, and associating a macro main that shows the associated trigger request and the action with the condition request, and Determine that the condition requirement is met and perform the action when the trigger requirement is met.

Images