close

Вход

Забыли?

вход по аккаунту

?

DESCRIPTION JP2008017085

код для вставкиСкачать
Patent Translate
Powered by EPO and Google
Notice
This translation is machine-generated. It cannot be guaranteed that it is intelligible, accurate,
complete, reliable or fit for specific purposes. Critical decisions, such as commercially relevant or
financial decisions, should not be based on machine-translation output.
DESCRIPTION JP2008017085
The present invention relates to an acoustic system configuration in which, when a plurality of
mixer engines are combined to configure a mixer system, even if a plurality of groups are
configured with arbitrary mixer engines, the entire configuration of the plurality of groups can be
viewed on one screen. It aims at providing a display editing device. SOLUTION: The configuration
of the plurality of acoustic signal processing devices in an acoustic signal processing system in
which a plurality of acoustic signal processing devices that process acoustic signals according to
a designated signal processing configuration are mutually connected via a network is displayed
on a screen. A sound system configuration display / editing apparatus for displaying and editing,
wherein a plurality of sound signal processing devices are defined in advance as devices in one
zone, and the devices in the one zone are divided into a plurality of device groups. Define it. And
while showing the structure of the apparatus in one zone by one screen, the structure of the
apparatus of the several device group which comprises the zone is displayed in the one screen.
[Selected figure] Figure 13
Sound system configuration display editing device
[0001]
The present invention relates to an audio system configuration display / editing apparatus for
displaying on a screen and editing the configuration of an audio system which operates
cooperatively by combining a plurality of apparatuses for processing audio signals.
[0002]
10-04-2019
1
Conventionally, the acoustic signal processing unit is configured using a processor (for example,
a digital signal processor (DSP)) operable according to a program, and a mixer configuration
(signal processing) edited using an external PC (personal computer) An acoustic signal
processing apparatus is known that is capable of processing an acoustic signal based on the
configuration).
Such an acoustic signal processing apparatus is referred to as a "mixer engine" in the present
application. The mixer engine internally stores the signal processing configuration edited and
transferred by the PC, and can independently process the acoustic signal based on the stored
signal processing configuration. Also, a large scale mixer system can be configured by combining
a plurality of mixer engines. The mixer engine described in Non-Patent Document 1 introduces
the concept of "zone" in order to operate a plurality of mixer engines cooperatively. Further,
Patent Document 1 discloses an acoustic signal processing system in which a plurality of mixer
engines are freely combined to configure a zone, and cooperative operation is realized in zone
units.
[0003]
Here, the zones will be described in detail. FIG. 18 shows an example in which three mixer
engines are used to configure a single zone. The PC 1801 and the three mixer engines 1803 to
1805 are mutually connected by the switching hub 1802. The three mixer engines 1803-1805
constitute one zone 1806. In a zone, there is always one device called a zone master, and the
other devices are slaves. For example, in FIG. 18A, the mixer engine 1803 is a zone master, and
the mixer engines 1804 and 1805 are slaves. The slaves 1804 and 1805 can be controlled by
control from the zone master 1803. Also, by giving an instruction from the PC 1801 to the zone
master 1803, it is possible to control all devices in the zone.
[0004]
FIG. 18B shows an example in which a plurality of zones are set. Three mixer engines 1821 to
1823 are connected to the switching hub 1813 to constitute a zone 1820. Similarly, zones 1830
are configured in mixer engines 1831 and 1832 and zones 1840 are configured in mixer engines
1841 to 1843, respectively. As described above, one zone master exists in each zone. The
switching hubs 1813 to 1815 are connected to the router 1812, and the PC 1811 is connected
to the router 1812.
10-04-2019
2
[0005]
In FIGS. 18A and 18B, only the connection relationship of the control system of the mixer system
is illustrated. Although not shown here, in reality, connection lines for transmitting acoustic
signals are connected between the mixer engines, and there are also input lines of acoustic
signals input from a microphone or the like, and output lines to amplifiers, speakers or the like.
[0006]
Although the zones described above can be defined in any manner, here, a plurality of devices
provided with IP addresses constituting the same domain constitute one zone. Specifically,
devices having the same class C address network address are included in the same zone.
Therefore, one zone consists of at most 256 devices, and the connection between the zones
needs to be through a router (eg 1812 in FIG. 18B).
[0007]
By setting the zones as described above, devices in one zone can be operated cooperatively. For
example, when one scene is specified and recalled from any mixer engine included in the zone, a
scene recalled collectively is set to all the mixer engines in the zone. A scene is a combination of
configuration and preset parameters. Configuration refers to a combination of components for
constructing a desired mixer system. A component is a component that is a component that
performs signal processing, etc. For example, components of an audio processor such as a mixer,
a compressor, an effect, and a crossover, an operator such as a fader, a switch, a pan, and a
meter, and a display are prepared. ing. The user executes a predetermined mixer control program
on the PC to display a mixer editing screen, selects and arranges an arbitrary component on the
screen, draws a connection between the terminals of each component, and enters an acoustic
signal. Output relationships can be defined to create the desired mixer configuration
configuration. The created configuration is compiled (converted into information that can be
interpreted by the mixer engine) and then transferred from the PC to the mixer engine. The mixer
engine calls the configuration on the current memory and executes it to realize the mixer having
the mixer configuration defined in the configuration. The preset parameters are a set of
parameter data in each component of the mixer configuration described above.
10-04-2019
3
[0008]
Moreover, control of the mixer system can be performed in zone units by control from the PC.
For example, when specifying a zone 1820 from the PC 1811 in FIG. 18B and instructing a scene
recall, the mixer engines 1821 to 1823 in the zone 1820 call and set the configuration and
preset parameters of the instructed scene. As zones are completely independently controlled, the
indication for one zone does not affect other zones. Further, since the instruction to the zone is
an instruction to all the devices in the zone, when the instruction to the zone is given, the control
operation according to the instruction is executed on all the devices in the zone.
[0009]
When a plurality of mixer engines are combined to form a mixer system as described above, a
zone configuration screen showing the entire configuration is displayed to allow the user to view
the zone configuration so that the connection relationship of each mixer engine can be viewed.
There are devices which have a function capable of connecting various devices on a screen and
creating a screen representing the entire configuration (for example, see Non-Patent Document
2).
[0010]
FIG. 19 shows a display example of the zone configuration screen of each of the three zones of
FIG. 18 (b).
On the main screen 1900, the zone configuration screen 1901 of zone 1 (zone 1820 of FIG. 18
(b), the zone configuration screen 1902 of zone 2 (zone 1830 of FIG. 18 (b)), and zone 3 (FIG.
Zone 1840 of the zone 1840) is displayed. JP, 2005-252686, "DIGITAL MIXING ENGINE
DME64N / 24N instruction manual", Yamaha Corporation, page 11, 2001 "DME Designer
Version 1.1 instruction manual", Yamaha corporation, 2004, pages 203-207
[0011]
As described above, in the related art, since devices are linked in zone units, when a
configuration screen as shown in FIG. 19 is displayed, it has to be displayed in a window for each
zone. That is, it was not possible to display the configuration of a plurality of zones together in
10-04-2019
4
one window. However, depending on the setting method of the user, there is a case where one
audio system is constructed in a plurality of zones, and in such a case, there is a demand to
overlook the entire plurality of zones in one screen. The prior art has not been able to meet such
a demand.
[0012]
According to the present invention, when a plurality of mixer engines are combined to configure
a mixer system, even when a plurality of groups are configured with arbitrary mixer engines, the
entire configuration of the plurality of groups can be collectively viewed on one screen. An object
of the present invention is to provide an audio system configuration display / editing apparatus.
[0013]
In order to achieve the above object, the present invention relates to a plurality of acoustic signal
processing devices in an acoustic signal processing system in which a plurality of acoustic signal
processing devices that process acoustic signals according to a specified signal processing
configuration are interconnected via a network. A sound system configuration display / editing
apparatus for displaying and editing the structure of the present invention on a screen, wherein
the plurality of sound signal processing devices are defined in advance as devices in one zone,
and devices in the one zone are defined. Furthermore, a plurality of device groups are defined by
grouping.
And while showing the structure of the apparatus in one zone by one screen, the structure of the
apparatus of the several device group which comprises the zone is displayed in the one screen.
[0014]
The display of the device configuration of the plurality of device groups may be displayed in a
color designated for each device group. Also, when addition of a display element of a new device
is instructed, the new device group is made to specify whether the device belongs to any of
existing device groups or to a new device group. When designated as belonging, the device group
name may be input.
[0015]
10-04-2019
5
According to the present invention, when combining a plurality of mixer engines to configure a
mixer system, even if a plurality of groups are configured with arbitrary mixer engines, the whole
is one zone, and a plurality of device groups in the zone Because of this, the entire configuration
of these multiple device groups can be viewed together on one screen. In particular, since the
color is displayed in a designated color for each device group, even when devices arranged at
distant positions belong to the same device group, this can be recognized at a glance.
Furthermore, when it is instructed to add a display element of a new device, it is made to specify
whether the device belongs to any of the existing device groups or to a new device group, and to
the new device group When the device group is designated as belonging, the device group name
is input, so that each device is surely bound by any device group and a display having a
configuration that is easy to view as a whole is realized.
[0016]
An embodiment of the present invention will be described below with reference to the drawings.
[0017]
In the mixer system (acoustic signal processing system) of the present embodiment, the concept
of the device group is newly introduced below the zone.
In the prior art, only the zone is the interlocking unit of equipment, but in the mixer engine of
this embodiment, the minimum interlocking unit is the device group. A zone is composed of a
plurality of device groups, and device groups in the same zone can communicate with each other.
In addition, in a specific scene, it is possible to make settings such that specific devices in a
device group are not interlocked, and thereby it is possible to set the minimum interlocking unit
to any number of the devices constituting the device group It is. There is always one device called
a group master in the device group, and the other devices are slaves.
[0018]
A group master in a device group knows information of other device groups in the same zone. It
is not necessary to know all the devices in other device groups, as long as the information of the
group master is known. This is because, in any device group, when performing some control
10-04-2019
6
operation, the group master gives an instruction to a slave controlled by itself. A table in which
information on all the masters is described is called a master table, and all the masters share the
table to enable interlocking of devices between device groups.
[0019]
In particular, in the present embodiment, a scene master table, which is a master table for a
scene, will be described as an example. That is, for scenes, a scene table for each device group
(referred to as a "device group scene table") is prepared, and significant scenes ("device group
scenes") are registered in the device groups registered in each device group scene table. A
combination of the called (in other words, a combination of IDs for specifying a device group
scene of each device group, and called “scene link”) is prepared. A table in which this scene
link is registered is a scene master table. The scene link registered in the scene master table can
be set so as not to recall a specific device group scene. Further, in the device group scene
registered in the device group scene table, it is possible to set that scene recall is not performed
for a specific device. These tables will be described in detail later.
[0020]
FIG. 1A shows an example of the configuration of a single device group. Three mixer engines 103
to 105 are connected via the switching hub 102 to constitute one device group 106. The PC 101
is connected to the hub 102.
[0021]
FIG. 1 (b) shows an example in which a plurality of device groups are configured in a single zone.
The device group 120 includes three mixer engines 121 to 123, the device group 130 includes
two mixer engines 131 and 132, and the device group 140 includes three mixer engines 141 to
143. The eight mixer engines 121 to 123, 131, 132, and 141 to 143 are connected to the
switching hub 112, and the PC 112 is connected to the hub 112. As described in the background
art section, although the equipment having the same network address of the class C address is
included in the same zone, in FIG. 1 (b), eight mixer engines constitute a single zone. Therefore,
these mixer engines can be connected to each other by the switching hub 112. There is no need
to use expensive routers, and they can be interconnected at the hub, resulting in an overall cost
reduction.
10-04-2019
7
[0022]
As described above, the minimum interlocking unit is one device group, and a plurality of device
groups constitute one zone. Also, since the zone is a unit similar to the zone of the prior art, if it
is operated in zone units, a plurality of device groups can be interlocked. One group master is
present in one device group. Communication between group masters of a plurality of device
groups enables communication with other interlocking units without crossing a zone. At the time
of system startup, communication for initialization is performed between devices, and all devices
in a device group share information on which device in that device group is a group master and
which device is a slave Further, it is assumed that the group master of each device group shares
information of which device is the group master for all device groups present in the zone.
[0023]
FIG. 2 shows a hardware configuration of each mixer engine of FIG. The mixer engine includes a
CPU (central processing unit) 201, a random access memory (RAM) 202, a flash ROM (read only
memory) 203, an operation element 204, a detection circuit 205, a display unit 206, a display
circuit 207, an external device 208, and communication. An interface (I / F) 209, an external
device 210, an audio I / F 211, and a communication bus 212 are provided.
[0024]
The CPU 201 is a processing device that controls the operation of the entire mixer engine. The
RAM 202 is a volatile memory that loads a program to be executed by the CPU 201 and secures
various buffer areas. The flash ROM 203 is a rewritable non-volatile memory, and stores various
types of information such as a scene table described later. The operators 204 are various
operators such as buttons and wheels provided on the external panel of the mixer engine. The
detection circuit 205 detects the operation of the operation element 204 and sends the detection
result to the CPU 201. The display unit 206 is a display for displaying various information
provided on the external panel of the mixer engine. The display circuit 207 receives display
instructions from the CPU 201 and sends display data to the display unit 206 for display. A
communication interface (I / F) 209 is an interface of a LAN (local area network) for connecting
to the external device 208. Each mixer engine is connected to the hub 102 in FIG. 1A, and each
mixer engine is connected to the hub 112 in FIG. 1B, but this is connected to the hub by the
10-04-2019
8
communication I / F 209 is there. The audio I / F 211 is an interface for connecting to the
external device 210. Although only the connection relationship of the control system is
illustrated in FIG. 1 and the connection relationship for transmitting the acoustic signal is
omitted, in actuality, a connection line for exchanging the acoustic signal between the mixer
engines and the like is connected, / F 211 is an interface for transmitting such an acoustic signal.
In addition to the components shown in FIG. 2, the mixer engine is provided with a DSP for
processing an acoustic signal, but is omitted here.
[0025]
The hardware configuration of the PCs 101 and 111 in FIG. 1 is the same as that shown in FIG. If
the configuration of FIG. 2 is regarded as the configuration of the PC 101 or 111, the audio I / F
211 is unnecessary if the PC does not process audio signals. Also, the flash ROM may be a
normal ROM, and usually an auxiliary storage device such as a hard disk is connected. The
operator 204 is a keyboard and a mouse, and the display unit 206 is a display of a PC, so the
display is a larger display than the display of the mixer engine.
[0026]
The scene table will be described with reference to FIG. FIGS. 3C and 3D show examples of scene
tables in a conventional mixer system. For example, FIG. 3 (c) is a scene table of zone 1820 of
FIG. 18 (b), and FIG. 3 (d) is a scene table of zone 1840 of FIG. 18 (b). The scene table of FIG. 3C
is created by executing a predetermined mixer control program on the PC 1811. The scene table
is transferred from the PC 1811 to each of the mixer engines 1821 to 1823 in the zone 1820,
and the flash of each mixer engine 1821 to 1823 is generated. It is stored in the ROM 203. For
example, in the operation in any of the mixer engines in the zone 1820 or in the operation after
designating the zone 1820 from the PC 1811, a scene No. Assuming that 001 is recalled, the
table in FIG. 3C is referred to by each of the mixer engines 1821 to 1823, Config01 is read out,
the mixer configuration of each mixer engine is set, and the mixer engine 1821 which is a zone
master The Preset 001 is read out in the mixer engine 1822 which is the slave 1 and the preset
002 is read out in the mixer engine 1823 which is the slave 2, and set as parameters. Note that
Config01 and Config02 are file names of configuration files that are entity data of a combination
of components and connection relationships, and the configuration file that is the entity data is
created in advance by the mixer control program on the PC 1811 and each mixer engine 18211823 Has been transferred to The same is true for preset files such as Preset 001.
10-04-2019
9
[0027]
FIG. 3 (d) is also similar to the scene table of FIG. 3 (c). However, FIG. 3 (c) is a table of zone 1820
and FIG. 3 (d) is a table of zone 1840. Even the content is generally different. The file names of
the configuration and the preset are the same in FIG. 3D and FIG. 3C, but the contents of the file
are generally different.
[0028]
In contrast to such a conventional scene table, the mixer engine of this embodiment has a scene
table as shown in FIGS. 3 (a) and 3 (b).
[0029]
FIG. 3A shows a scene table (device group scene table) in a device group for performing scene
recall linked in device group units.
This table has the same configuration as the conventional zone-based scene table shown in FIGS.
3C and 3D, and the description of FIGS. 3C and 3D can also be made by replacing "zone" with
"device group" For example, it is applied as it is. However, although the preset file corresponding
to each mixer engine is always specified in the scene table of the prior art, there is no
specification of the preset file in the device group scene table of FIG. There is a part being done.
これは、そのシーンNo. When is recalled, it means that the configuration and preset are not
recalled (that is, they are kept at the current state) for the mixer engine whose preset column is "".
[0030]
Since such a device group scene table is stored in all mixer engines in the device group, the
operation in any mixer engine in the device group or the operation after designating the device
group from the PC Scene No. Is designated and a recall instruction is issued, a scene recall is
performed with all mixer engines in the device group linked (but excluding mixer engines
designated by "-" in the table). Each mixer engine may store the device group scene table of the
device group to which the own device belongs, and does not need to store the device group scene
table of another device group.
10-04-2019
10
[0031]
FIG. 3B shows a scene table (scene master table) for performing scene recall linked in zone units.
Scene link No. (Scene Link No.) Scene No. to be recalled for each device group corresponding to
The scene link which is a combination of is registered. Such a scene master table is created, for
example, by executing a predetermined mixer control program on the PC 111 of FIG. 1B,
transferred from the PC 111 to each group master of all device groups, and each device via the
group master. It is also transferred to all slaves in the group, and as a result, stored in the flash
ROM 203 of all mixer engines in the zone. The scene link No. 1 is operated by an operation on an
arbitrary mixer engine in a single zone in FIG. 1 (b) or by an operation after designating a zone
from the PC 111. Is designated and a scene recall of a zone is instructed, the group master of
each device group is the scene link No. Scene No. designated as own group by scene link of Is
acquired with reference to the device group scene table, and the acquired scene may be recalled
within the own device group. As a result, interlocked scene recall is performed on all device
groups in the zone.
[0032]
In the scene link registered in the scene master table, the scene No. is registered. There is a
portion in which is not described but "-" is described. これは、そのシーンリンクがリコールされ
たときに、シーンリンクNo. Means that the recall is not performed (i.e., it is kept at the
current state) for the device group in which "-" is not described. Thereby, interlocked scene recall
can be realized for any device group in the zone.
[0033]
Next, an operation procedure for instructing a scene recall in each mixer engine of the mixer
system of the present embodiment will be described.
[0034]
FIG. 4A shows the appearance of the external panel (a part) of the mixer engine of this
embodiment.
10-04-2019
11
On the external panel 400, a liquid crystal display (LCD) 401 corresponding to the display unit
206, a wheel 402 corresponding to the operating element 204, a scene button 403, an enter
button 404, and a cancel button 405 are provided. When the scene button 403 is pressed, a
menu 411 shown in FIG. 4B is displayed on the LCD 401. A menu 411 is a menu for selecting
whether a scene to be recalled is a scene of a zone or a scene of a device group. A zone scene is
any scene link registered in the scene master table of FIG. 3 (b). The scene of the device group is
any scene registered in the device group scene table of FIG. 3A (the device group to which the
mixer engine for which the scene button 403 has been pressed belongs). When the wheel 402 is
operated to select either a zone or a device group in the menu 411 and the enter button 404 is
pressed, a menu as shown in FIG. 4C is displayed. This menu 412 is a menu of a list of scene
links registered in the scene master table of FIG. 3B when a zone is selected in the menu 411,
and a diagram when a device group is selected in the menu 411. It is a menu of the list of the
scene registered into the device group scene table of 3 (a). By selecting one scene or scene link
from the menu 412 and pressing the enter button 404, the scene or scene link is recalled.
Although a list of scenes or scene links is named in the menu 412, it is assumed that the user can
arbitrarily assign a name.
[0035]
FIG. 5 shows the processing procedure of the group master and the slave in the case of
performing a scene recall in the device group from the group master of a certain device group
(when the device group is selected in the menu of FIG. 4B). In step 501, the group master
receives a recall instruction by the UI (user interface) operation described in FIG. 4 or receives a
scene recall command transmitted from the PC 101. At step 502, all slaves of the own device
group are notified of a scene recall instruction operated or received. Thereafter, at step 503, a
scene recall is performed in the own machine. The slave of the device group receives a scene
recall instruction at step 511. At step 512, the designated scene is recalled.
[0036]
FIG. 6 shows the processing procedure of the group master and the slave when the scene recall
in the device group is performed from the slave of a certain device group (when the device group
is selected in the menu of FIG. 4B). In step 611, the slave receives a recall instruction by the UI
operation described with reference to FIG. 4 or receives a scene recall command transmitted
from the PC 101. At step 612, the group master is notified of the scene recall instruction. The
group master receives the notification at step 601, and notifies all slaves of the own device group
10-04-2019
12
of an instruction for the scene recall at step 602. Thereafter, in step 603, the group master
recalls the scene instructed by the own device. On the other hand, the slaves (all slaves of the
device group) receive the scene recall instruction from the group master in step 613, and recall
the scene instructed in the own device in step 614.
[0037]
FIG. 7 shows the processing of the group master and the slave in the case of performing scene
recall within a zone from the group master of a certain device group when there are multiple
device groups (when a zone is selected in the menu of FIG. 4B). Show the procedure. In step 701,
the group master of a certain device group 700 receives a recall instruction by the UI operation
described in FIG. 4 or receives a scene recall command transmitted from the PC 101. At step
702, the group master of the other device group is notified of a scene recall instruction to be
executed by the group master. The subsequent processes of steps 703, 704, 711, and 712 are
the same as the processes of steps 502, 503, 511, and 512 in FIG. 5, respectively.
[0038]
The group master of the other device group 720 notified of step 702 receives an instruction of
the scene recall in step 721. The subsequent processes of steps 722, 723, 731, and 732 are the
same processes as those of steps 502, 503, 511, and 512 in FIG. 5, respectively.
[0039]
FIG. 8 shows the processing procedure of group masters and slaves when a scene recall is
performed from a slave of a device group when there are multiple device groups (when a zone is
selected in the menu of FIG. 4B). Indicates In step 811, the slave of a device group 800 receives a
recall instruction by the UI operation described in FIG. 4 or receives a scene recall command
transmitted from the PC 101. In step 612, the instruction of the scene recall is notified to the
group master of the own device group. The group master receives an instruction of the scene
recall in step 801. The subsequent processing in steps 802, 803, 804, 813, 814 in the device
group 800 is the same processing as steps 702, 703, 704, 711, 712 in FIG. Also, the processing
of steps 821, 822, 823, 831, 832 in the other device group 820 is the same processing as the
steps 721, 722, 723, 731, 732 of FIG.
10-04-2019
13
[0040]
As can be seen from FIGS. 5 to 8, in this embodiment, control in the device group is performed in
the procedure of first notifying an instruction to the group master and notifying the slaves in the
group of the instruction from the group master. It is like that.
[0041]
FIG. 9 shows a processing procedure of scene recall in each mixer engine.
This process is executed in steps 503 and 512 in FIG. 5, steps 603 and 614 in FIG. 6, steps 704,
712, 723 and 732 in FIG. 7, and steps 804, 814, 823 and 832 in FIG. It is a process.
[0042]
In step 901, it is determined whether the mixer configuration (config) currently set in the mixer
engine is the same as the configuration registered in the scene to be recalled. If not, in step 902,
configuration information of the scene to be recalled is read from the device group scene table
(FIG. 3A) in the own machine. Next, in step 903, the components are arranged according to the
configuration information, and in step 904, the components are connected according to the
configuration information, and the process proceeds to step 905. Specifically, the processing of
steps 903 and 904 is processing of loading a microprogram that performs acoustic signal
processing according to the configuration information to the DSP of the own device. If it is
determined in step 901 that the configuration is the same, the process proceeds to step 905 as it
is. At step 905, preset information of the scene to be recalled is read from the device group scene
table. At step 906, the parameter value of the component is set according to the preset
information, and the process ends.
[0043]
FIG. 10 shows the procedure of the scene switching routine by the UI operation described in FIG.
This process is activated when the scene button 403 in FIG. 4A is pressed, and is performed in
step 501 of FIG. 5, step 611 of FIG. 6, step 701 of FIG. 7, and step 811 of FIG. It is a process
where execution is started. The same processing is performed when receiving a scene recall
10-04-2019
14
command from a PC (however, information instructed by the command is used instead of the
user's selection operation).
[0044]
In step 1001, it is determined whether the target to switch the scene is the entire zone or only
the own device group. When a zone is selected in the menu 411 of FIG. 4B and the enter button
404 is pressed, the process proceeds to step 1002. When a device group is selected in the menu
411 and the enter button 404 is pressed, the process proceeds to step 1005. .
[0045]
In step 1002, the scene table of the zone (the scene master table described in FIG. 3B) is
acquired, and a list of the scene links is displayed as in the menu 412 of FIG. 4C. In step 1003,
the selected scene number (to be exact the scene link number), ie, the scene number selected by
the user from the menu 412 and the enter button 404 pressed is acquired. In step 1004, the
scene information to be recalled is acquired, and the process proceeds to step 1008. Thus, the
scene numbers to be recalled in each device group. Was acquired.
[0046]
In step 1005, the scene table of the own device group (the device group scene table described in
FIG. 3A) is acquired, and a list of the scenes is displayed as shown in a menu 412 of FIG. 4C. In
step 1006, the selected scene number, ie, the scene number selected by the user from the menu
412 and the enter button 404 is pressed is acquired. In step 1007, the scene information to be
recalled is acquired, and the process proceeds to step 1008. Thus, the scene No. to be recalled in
the own device group. Was acquired.
[0047]
In step 1008, it is determined whether or not the own machine is a group master, and when it is
a group master, after scene recall (processing in FIG. 11) in step 1009, the process ends. If the
own machine is a slave, the device master of the own group is notified in step 1010, and the
10-04-2019
15
process ends. The notification of step 1010 corresponds to step 612 of FIG. 6 and step 812 of
FIG.
[0048]
FIG. 11 shows a detailed processing procedure of step 1009 of FIG. In step 1101, it is determined
whether the scene recall is performed for the entire zone or only for the own device group. When
it is the whole zone (that is, when it passes through the steps 1002 to 1004 in FIG. 10), the scene
master is notified to the group master of the other device group at step 1102 No. Is acquired, the
scene number of the device group to be recalled in the device group is the group master of each
device group. In step 1103, the scene No. to be recalled from the scene master table by the own
device group. (Actually, in step 1004, scene No. to be recalled in each device group. Of the scene
No. to be recalled in the own device group from among them. ), Go to step 1104. If it is
determined in step 1101 that only the own device group is present (ie, the steps 1005 to 1007 in
FIG. 10 have been reached), the process proceeds directly to step 1104. At step 1104, a slave of
the own device group is notified of a scene recall. This is the scene No. to be recalled in the own
device group. Is acquired, so the scene No. To indicate a recall. In step 1105, it is determined
whether there is a scene (config and preset) to be recalled. If so, the scene of the player is
recalled in step 1106, and the process ends. If there is no scene to recall, the process ends. At
step 1106, the process of FIG. 9 is performed.
[0049]
The notification in step 1102 corresponds to step 702 in FIG. 7 and step 802 in FIG. The
notification in step 1104 corresponds to step 502 in FIG. 5, step 602 in FIG. 6, steps 703 and
722 in FIG. 7, and steps 803 and 822 in FIG. Note that the group master of the other device
group (the group master of group 720 in FIG. 7 or the group master of group 820 in FIG. 8) that
has received the notification of step 1102 executes the processing of FIG. It is a thing.
[0050]
FIG. 12 shows a scene recall routine in the slave of the device group. This process is a process
executed by the slave notified of step 1104 of FIG. 11, and is step 512 of FIG. 5, step 614 of FIG.
6, steps 712 and 732 of FIG. 7, and step 814 of FIG. 832 is to be executed. First, in step 1201, it
is determined whether there is a scene to be recalled. If there is, in step 1202 the scene of the
10-04-2019
16
player is recalled and the process ends. If not, the process ends.
[0051]
Next, the display editing function of the zone configuration in the mixer system of the present
embodiment will be described. In the mixer system of the present embodiment, although control
of a plurality of mixer engines can be performed from the PC 101, 111 shown in FIG. 1, the
mixer control program executed by the PC 101, 111 for the control has a zone configuration. It
has a display editing function. This is a function that allows the user to arbitrarily arrange blocks
representing mixer engines on the screen, draw connections indicating the connection
relationship between them, and thus make it possible to overlook the configuration of the mixer
system as a whole at a glance. In particular, in the present embodiment, since the concept of the
device group as described above is introduced, the device on the display is devised so that it can
be known at a glance which device group the mixer engine disposed on the screen belongs to.
ing. In the following, the display editing function of the zone configuration with such display
device will be described.
[0052]
FIG. 13 is a screen example showing the configuration of the mixer system as described in FIG. 1
on the PC. In the main screen 1300, a window 1301 of a toolkit and a window 1303 of an editing
screen (hereinafter referred to as a CAD screen) are displayed. The CAD screen 1303 displays
each device configuration in one zone, and here, device groups 1331 to 1333 are displayed. The
user can select a mixer engine from the toolkit 1301 and drag and drop it on the screen 1303 to
place it. In addition, elements other than the mixer engine can be similarly arranged on the
screen 1303, and connections can be drawn arbitrarily to create and edit a configuration
diagram of the mixer system as a whole. When a mixer engine is newly placed by dragging and
dropping on the CAD screen 1303, it can be called to be included in a specified device group, or
a new device group can be defined and called into it. In particular, the mixer engine blocks
belonging to the same device group are normally displayed in the same color except when an
operation to change the color is performed by specifying the displayed element. This has the
advantage that mixer engines belonging to the same device group can be easily identified even if
they are displayed at remote locations.
[0053]
10-04-2019
17
FIG. 14A shows a dialog box that pops up and displayed when the mixer engine is newly dragged
and dropped on the CAD screen 1303 of FIG. The user turns on one of the radio buttons 1401
and 1402 to select whether the mixer engine that has been dragged and dropped belongs to an
existing device group or a new device group. If it is desired to belong to an existing device group,
the radio button 1401 is turned on, one of the existing device groups is selected by the list box
1403, and an OK button 1406 is turned on. As a result, a new mixer engine is displayed on the
CAD screen 1303 in the color already assigned to the selected device group.
[0054]
If the mixer engine to be newly added is to belong to a new device group, turn on the radio
button 1402, enter an arbitrary name in the device group name input area 1404, and turn on the
select color button 1405. After designating the color of the device group to be newly added, the
OK button 1406 is turned on. As a result, a new device group is displayed in the CAD screen
1303, a new mixer engine is displayed in the device group, and the color is made the color
designated by the user. When the cancel button 1407 is turned on, the addition of the mixer
engine is canceled.
[0055]
FIG. 14B shows a dialog box for changing the display color of the device group. When a display
element of an arbitrary device is selected from the CAD screen of FIG. 13 and a predetermined
operation such as a right click of a mouse is performed, a dialog box of FIG. 14B is displayed.
When it is desired to change the display color of only the selected device, the radio button 1411
is turned on, the select color button 1413 is turned on, and the color to be changed is designated.
When it is desired to change the colors of all the devices in the device group to which the
selected device belongs, the radio button 1412 is turned on, the select color button 1413 is
turned on, and the color to be changed is designated.
[0056]
FIG. 15 shows processing when an operation of adding the first machine on the CAD screen is
performed. When a single mixer engine is not displayed on the CAD screen, this process is
executed when a new mixer engine is added by drag and drop. At step 1501, the user is made to
10-04-2019
18
specify the color to be drawn on the CAD screen. At step 1502, the added new mixer engine is set
as a group master. At step 1503, the mixer engine is drawn on the CAD screen with the
designated color, and the process is ended.
[0057]
FIG. 16 shows processing when an operation of adding the second and subsequent units is
performed on the CAD screen. At this time, first, the dialog box of FIG. 14A is displayed. In step
1601, it is determined whether to newly create a device group. This is because it is determined in
the dialog box of FIG. 14A which of the radio buttons 1401 and 1402 is turned on. When a
device group is newly created, the mixer engine to be added is set as a group master in step
1602, and the color to be drawn on the CAD screen is specified in step 1603. In step 1606, the
color is drawn on the CAD screen. If a new group is not to be created, the device group to which
the mixer engine is to be added is selected in step 1604, and in step 1605 the drawing color of
the group master is set as the color to be drawn on the CAD screen.
[0058]
FIG. 17 shows a processing procedure when the display color of the device on the CAD screen is
changed later. The dialog box of FIG. 14 (b) is displayed by a predetermined operation.
Thereafter, in step 1701, the color to be drawn on the CAD screen is designated. In step 1702, it
is determined whether it is selected to change all the display colors of the devices in the device
group to which the selected mixer engine belongs. In the case of changing all, in step 1703, the
display colors of all the devices in the device group are changed. If the display color of only the
selected device is to be changed, only the display color of the device is changed in step 1704.
After steps 1703 and 1704, drawing is made on the CAD screen in step 1705, and the process
ends.
[0059]
Diagram showing configuration example of device group Hardware configuration diagram of
mixer engine Configuration diagram of scene table Diagram of external view of mixer engine
(partly) and diagram of menu Processing procedure of group master and slave when scene recall
is performed ( The figure which shows the part 1) The process sequence of the group master and
slave when doing a scene recall. The figure which shows the process sequence of the group
master and slave when doing a scene recall when the scene recall is performed. Figure showing
the processing procedure (4) of the group master and the slave in the case flowchart showing the
10-04-2019
19
processing procedure of the scene recall flowchart showing the procedure of the scene switching
routine by the UI operation flowchart showing the detailed processing procedure of step 1009 in
the device group Scene recall routine Flowchart showing the configuration of the mixer system
Processing when the operation to add the first machine on the CAD screen of the dialog box
popped up when the mixer engine is newly dragged and dropped on the CAD screen Flowchart
showing processing when the operation to add the second and subsequent units on the CAD
screen is performed Flowchart showing processing procedure when changing the display color of
the device on the CAD screen later Figure showing an example of using a single zone Figure
showing a display example of the zone configuration screen
Explanation of sign
[0060]
101…PC、102…スイッチングハブ、103∼105…ミキサエンジン、106…デバイ
スグループ106。
10-04-2019
20
Документ
Категория
Без категории
Просмотров
0
Размер файла
35 Кб
Теги
description, jp2008017085
1/--страниц
Пожаловаться на содержимое документа