close

Вход

Забыли?

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

?

DESCRIPTION JP2014093624

код для вставкиСкачать
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 JP2014093624
Abstract: A management software process controls a plurality of music software processes and a
plurality of controllers to operate as one music system. SOLUTION: A management session is
established between GM1 and DAW processes of DAW3, DAW5 and DAW7 on the network and
controllers of M1, F2 and F3, respectively. Also, control sessions are established between the
DAW 3 process and the M 1 and F 2 and between the DAW 7 process and the F 3, respectively.
Thereby, GM1 can manage collectively the control session between the DAW process which
comprises one music system, and a controller via a management session for exclusive use.
[Selected figure] Figure 4
Music system management method
[0001]
According to the present invention, a management software process started by one computer, a
plurality of music software processes started by a plurality of computers connected to the
computer via a network, and a plurality of controllers connected to the network The present
invention relates to a music system management method that controls a music system to operate
as one music system.
[0002]
2. Description of the Related Art Conventionally, it has been known to use a computer to perform
sound processing operations such as recording, editing and mixing of performance data.
11-04-2019
1
The computer is a general-purpose computer such as a PC (personal computer) and includes
various hardware devices such as an audio interface and MIDI I / F (Musical Instrument Digital
Interface), and music software is installed. Application software called DAW (Digital Audio
Workstation) is known as conventional music software installed on a PC. The PC in which the
DAW process is activated functions as a music processing device, and can perform music
processing such as performance of music according to performance data, recording /
reproduction of audio signals, editing, mixing, and the like.
[0003]
The music software features of DAW that run on a PC are complete, and installing music
software on a PC will allow individuals to easily create music. On the other hand, since the
functions of music software have become abundant, when performing all operations and
parameter settings for music software (DAW) processes started on a PC with a mouse or PC
keyboard, the operations are complicated. It has become to. Therefore, in the field of advanced
music production, a physical controller for operating the music software process is connected to
a PC on which music software has been installed, and operations such as knobs, sliders, and
buttons provided in this physical controller An operation and parameter setting are performed
when recording / reproducing, editing, and mixing performance data and audio data using a child
(see Patent Document 1).
[0004]
There is also known a music system in which a plurality of PCs having music software installed
thereon are connected to a network, and a controller that controls music software processes
activated in each PC is connected on a network. In this music system, a process (management
software process) for managing the connection between the controller and the DAW process is
started on each PC together with the DAW process. Then, the music software process to be
controlled by the controller is switched according to the operation of the connection switching
switch on the operation panel of the controller (see Non-Patent Document 1).
[0005]
JP, 2011-59232, A
11-04-2019
2
[0006]
Mc Mix User Operation Guide Manual (Japanese), P. 11-18, P. 38-42, [online], [April 3, 2012
search], Internet <http://connect.euphonix.com/documents /MC_Mix_User_Guide_rB_Jap.pdf>
[0007]
In the conventional music system, when the music software process is started on a plurality of
PCs, an independent management software process is started for each PC, so that another music
software process remotely controlled by one controller is different music In order to switch to
the software process, communication is performed between multiple management software
processes of multiple PCs, and since multiple management software must be linked and switched,
it takes time to switch music software processes. There was a problem.
Therefore, according to the present invention, a management software process started by one
computer comprises a plurality of music software processes started by a plurality of computers
connected to the computer via a network, and a plurality of music software processes connected
to the network An object of the present invention is to provide a music system management
method capable of switching music software processes at high speed by controlling a controller
and operating as one music system.
[0008]
In order to achieve the above object, according to a music system management method of claim
1 of the present invention, a plurality of management software processes started by one
computer are started by a plurality of computers connected via a network. And a plurality of
controllers connected to the network to operate as a single music system, the management
software process comprising, from a user, the plurality of music software It communicates with
the music software process and controller accepted in the first process via the network and a
first process for accepting a desired music software process and controller selection from the
process and the plurality of controllers. , Said music software process and controller and said
management software A second step of establishing a management session for performing
management communication among the processes on the network, and a third step of receiving
from the user a selection of one music software process to be controlled for each controller And
communicate with each controller and one music software process received in the third step
through the management session to open the current control session of the controller and to
execute the controller on the network. And a fourth step of establishing a new control session for
performing control communication between the one music software process, and in response to
an operation of each controller by the user, the controller communicates with the controller. The
11-04-2019
3
music software process for which a control session has been established is remoulded through
the control session. It is the most important feature that bets control.
[0009]
Further, in the music system management method according to claim 2 of the present invention,
a plurality of management software processes are started by the plurality of computers on the
network, and the plurality of music software processes and the plurality of controllers are
respectively the plurality of The management session can be established only with any one
management software process among the management software processes, and any one
management software process among the plurality of management software processes, and the
management software One music system is constructed by the music software process and the
controller in which a management session is established between the processes, and as a result, a
plurality of music systems corresponding to a plurality of management software processes are
constructed on the network. It is characterized by
[0010]
Furthermore, in the music system management method according to claim 3 of the present
invention, in the music system management method according to claim 2, each of the plurality of
management software processes further includes a management software process different from
the management software process. And a fifth step of temporarily establishing an interrupt
session for performing interrupt communication with a music software process or controller for
which a management session has already been established. It communicates with the music
software process or controller in which the interruption session has been established, opens the
interruption session, and manages between the music software process and the controller and
the management software process on the network. And a sixth step of establishing a
management session for communication. It is characterized.
[0011]
Furthermore, in the music system management method according to claim 4 of the present
invention, in the music system management method according to claim 2, each of the plurality of
management software processes is further management software different from the management
software process. A seventh step of temporarily establishing an interrupt session for performing
interrupt communication with a music software process or a controller for which a management
session has already been established between the process and the interrupt session Sending an
information to the music software process or controller in which the interruption session has
been established, or an eighth process of obtaining information from the music software process
or controller. .
11-04-2019
4
[0012]
Furthermore, in the music system management method according to claim 5 of the present
invention, in the music system management method according to claim 1, each control session
established in a music software process started by a certain computer is established by the same
computer. It is characterized by being established using a port number which is not used in the
management session and other control sessions.
[0013]
In the music system management method according to claim 1 of the present invention, one
management software collectively controls a control session between a music software process
forming one music system and a controller through a dedicated management session. Since
management is performed, switching of music software processes to be controlled by each
controller can be performed with good response.
Further, in the music system management method according to claim 2 of the present invention,
the plurality of music systems are processed on the one network by activating the plurality of
management software processes by the plurality of computers connected to the one network. It
can be built.
Furthermore, in the music system management method according to claim 3 of the present
invention, a management software process of a music system can be incorporated into the music
system by intercepting music software processes or controllers of other music systems.
Furthermore, in the music system management method according to claim 4 of the present
invention, a management software process of one music system interferes with the operation of
the other music system with a music software process or a controller of another music system.
Information can be transmitted directly without
Furthermore, in the music system management method according to claim 5 of the present
invention, since a control session is established using different port numbers for each
combination of music software process and controller, control communication is performed more
efficiently. be able to.
11-04-2019
5
For this reason, conditional branching in reception processing can be reduced.
[0014]
It is a block diagram which shows the hardware constitutions of the music system to which the
music system management method of the Example of this invention was applied.
It is a figure which shows the example of a setting of the work group in the music system
management method of the Example of this invention. It is a figure which shows the group
manager screen in the music system management method of the Example of this invention. It is a
figure which shows the session established in the music system management method of the
Example of this invention. It is a figure which shows the panel structure of the fader controller in
the music system management method of the Example of this invention. It is a figure which
shows the panel structure of the main controller in the music system management method of the
Example of this invention. It is a block diagram which shows the hardware constitutions of PC in
the music system management method of the Example of this invention. It is a figure which
shows the function structure of the DAW process in the music system management method of
the Example of this invention. It is a block diagram which shows the hardware constitutions of UI
device in the music system management method of the Example of this invention. It is a figure
which shows the structure of the Ethernet frame in the music system management method of the
Example of this invention. It is a flowchart of HB production | generation transmission processing
in the music system management method of the Example of this invention. It is a flowchart of HB
reception processing in the music system management method of the Example of this invention.
It is a flowchart of the main process in the music system management method of the Example of
this invention. It is a sequence diagram which shows the session establishment procedure in the
music system management method of the Example of this invention, a data transmission
procedure, and an open procedure. It is a flowchart of the member addition process in the music
system management method of the Example of this invention. It is a flowchart of HB error
processing in the music system management method of the Example of this invention. It is a
flowchart of the process performed with UI device and group manager, when the selection button
of DAW is operated in the music system management method of the Example of this invention. It
is a flowchart of the process performed with UI device and DAW when the parameter operation
element is operated in the music system management method of the Example of this invention.
[0015]
11-04-2019
6
A block diagram showing the configuration of a music system to which the music system
management method of the embodiment of the present invention is applied is shown in FIG. The
music system 1 includes an Ethernet (registered trademark) network 2, and the network 2
includes seven personal computers (PCs) PC 1, PC 2, PC 3, PC 4, PC 5, PC 5, PC 6, PC 7, and 8.
One UI (User Interface) device M1, F1, F2, F3, F4, M2, M3, and F5 are connected. Ethernet is the
name of a network technology standard for LAN (Local Area Network). When seven PCs and
eight UI devices connected to the network 2 are newly connected to the network 2, they are
mutually connected from a Dynamic Host Configuration Protocol (DHCP) server already
connected to the network 2. Are assigned different IP addresses. In this case, a dedicated DHCP
server may be provided, or one PC or UI device may play the role of a DHCP server. The fixed IP
address may be set in advance to seven PCs and eight UI devices. Management software process
and / or music software (DAW) process is started on OS (Operating System) in 7 personal
computers, GM1 management software process is started on PC1, and DAW process of DAW1 is
on PC2. It is started, the management software process of GM2 in PC3 and the DAW process of
DAW2 are started, the two DAW processes of DAW3 and DAW4 are started in PC4, the two DAW
processes of DAW5 and DAW6 are started in PC6, and it is in PC7 DAW7 DAW process has been
started. The PC on which the DAW process is activated can execute music processing such as
recording / reproduction, editing, mixing and the like of MIDI events and audio signals. In this
specification, a set of multiple processes that causes a PC to function in cooperation as a single
DAW (Digital Audio Workstation) is referred to as a "DAW process", and a single music in
cooperation. A set of multiple processes that perform the function as a system management
apparatus is called "management software process". Further, UI devices M1, F1, F2, F3, F4, M2,
M3 and F5 are physical controllers provided with a knob, fader, button, etc. operated by the user,
and M1, M2, M3 are main controllers, F1. , F2, F3, F4, and F5 are fader controllers.
Each UI device, each DAW process, and each management software process in the music system
1 shown in FIG. 1 is assigned a unique ID for identifying the UI device or process. This unique ID
does not change due to the start or stop of the UI device or process. Therefore, when a UI device
or process is discovered on the network by a heartbeat packet described later, it is possible to
determine whether the same UI device or process is in the HB list described later using the
unique ID.
[0016]
In the DAW process, the user can create an arbitrary number of MIDI tracks for recording MIDI
events, audio tracks for recording audio signals, and buses for mixing audio signals for each
music file called a project. It is being done. The audio track can selectively record an audio signal
11-04-2019
7
input from one of one or more input ports / channels provided in the DAW process for each
audio track, and an output of an audio signal reproduced on the audio track First, any one of a
plurality of output ports / channels provided in the DAW process can be selected. Then, each
time the user creates an audio track, the display of the corresponding channel strip is added to
the mixer screen. In the channel strip of the mixer screen, parameters of various channels are
adjusted, and the details of the audio channel will be described later with reference to FIG.
[0017]
The GM1 management software process started on PC1 and the GM2 management software
process started on PC3 manage the workgroups set for each, and workgroups exist on network 2
Can register a DAW process or UI device. An example of setting a work group is shown in FIG. 2,
and in the example of setting shown in FIG. 2, DAW processes of DAW3, DAW5, DAW7 and UI
devices of M1, F2, F3 are registered in work group WG1. In the work group WG2, DAW
processes of DAW2 and DAW6 and UI devices of M3, F4, and F5 are registered, and DAW1,
DAW4 and M2, F1 are not registered in any work group. The GM1 management software process
manages work group WG1, and the GM2 management software process manages work group
WG2. Note that work group management will be performed by the PC that is executing the work
process's management software process. Then, the DAW process and the UI device included in
one work group operate as one music system. That is, in the case shown in FIG. 2, the first music
system consisting of WG1 and the second music system consisting of WG2 operate
independently. Each music system can perform music processing such as recording /
reproduction, editing, mixing, and the like of input MIDI events and audio signals. Note that in
work group management, management of communication between members, which are DAWs
and UI devices constituting the work group, and management of addition or deletion of members
are performed, but the details will be described later.
[0018]
Here, a panel configuration of the fader controller 10 indicated by F1, F2, F3, F4, and F5 is
shown in FIG. As shown in FIG. 5, the panel of the fader controller 10 is provided with a ch strip
portion 20a composed of a plurality of ch strips, for example, eight, and a control portion 20b.
One ch strip of the mixer screen is assigned to each ch strip of the ch strip unit 20a, and an
operator for instructing adjustment of the assigned ch strip is provided. The operator is a fader
21 and a plurality of knobs 23 etc., and the ch name of the operation target assigned to the ch
strip can be displayed on the ch name display unit 22. Then, the level of the ch of the operation
target can be adjusted by operating the fader 21, and the predetermined parameter of the ch of
11-04-2019
8
the operation target can be adjusted by operating the knob 23.
[0019]
Further, in the control unit 20b, there are provided a first operator 24, a second operator 25, and
a selection button 26, which are a group of operators for performing an operation that can not
be performed by the ch strip unit 20a. The first operating element 24 is an operating element for
switching the type of parameter to be assigned to the knob 23 in the channel strip section 20a,
and the second operating element 25 is for switching the operation target channel to be assigned
to each channel strip of the channel strip section 20a. Is an operator of. Further, the selection
button 26 is a selection button for switching the DAW process to be controlled, and the control
object is switched to the DAW process assigned to “a” by pressing the button 26 a in which
“a” is written. The control object can be switched to the DAW process assigned to "b" by
pressing the button 26b in which "b" is written, and the control object is changed to "c" by
pressing the button 26c in which "c" is written. Switch to the assigned DAW process. As
described above, when the selection buttons 26a to 26c are operated to select one DAW process
corresponding to the selected button operated as a control target, the UI device and the selected
DAW process are executed. A control session is established between the same PC. Further, among
the selection buttons 26a to 26c, the selection button corresponding to the DAW process for
which the control session is established lights up, and the selection button corresponding to the
DAW process not established for the control session goes out. Thus, the user can confirm the
DAW process currently controlled by the UI device by confirming the on / off state of the
selection buttons 26a to 26c. When each DAW process is added to a work group, the DAW
process is not assigned to the DAW process existing at that time, and among “a”, “b” and
“c”. , One is assigned.
[0020]
Next, FIG. 6 shows a panel configuration of the main controller 11 indicated by M1, M2, and M3.
The main controller 11 is a controller that performs control of transport, control of detailed
parameters of each channel, etc. As shown in FIG. 6, the channel strip portion is not provided on
the panel of the main controller 11 . A panel of the main controller 11 is provided with a
plurality of operators such as knobs and buttons for controlling transport and controlling
detailed parameters of each channel. Typically, a plurality of controls for performing various
operations on the main screen of the DAW process are arranged on the panel. That is, "a plurality
of buttons for opening various pop-up screens for controlling detailed parameters of the DAW
process", "an operation element for changing the position of the time cursor indicating the
11-04-2019
9
current time on the track", "start of recording / Stop, Controls for instructing playback start /
stop, "Operators for setting values to parameters of cursor position", "Operators for storing /
recalling parameter set to library, etc." It is done. Moreover, the selection button 31 for switching
the DAW process to be controlled is provided, and the control object is switched to the DAW
process assigned to "a" by pressing the button 31a on which "a" is written. The control object can
be switched to the DAW process assigned to "b" by pressing the button 31b with "b" written, and
the control object with "c" by pressing the button 31c with "c" written Switch to the assigned
DAW process. Further, various settings in the DAW process to be controlled can be adjusted
using the channel strip section 20a of the fader controller 10 and the operation elements of the
control section 20b and the operation elements of the main controller 11. In this case, control is
performed by sending control information according to the amount of operation of the operator
to the DAW process (PC) to be controlled.
[0021]
The setting of the work group as shown in FIG. 2 can be performed on the group manager (GM)
screen 3 shown in FIG. This GM screen is displayed on the display device of the PC on which the
management software (GM) process is activated. The example of the GM screen 3 shown in FIG. 3
is displayed on the display device of the PC 1 on which the GM1 process is activated. In the GM
screen 3, a column 3a of "Workgroup" displays UI devices and DAW processes that are members
registered in the work group of WG1 managed by the GM1 process and exist on the network 2.
Also, in the “Outside” column 3 b, DAW processes and UI devices that are not registered in the
WG 1 but exist on the network 2 are displayed. Here, among the names displayed in the column
3a and the column 3b, the names "Conobase", "Anotool", "Orando", "CTH", and "FDH" are model
names of each DAW process or UI device. , And is displayed corresponding to a model ID
included in an HB message described later received from the DAW process or UI device. Also, the
roles “DAW A”, “DAW B”, and “DAW C” are the first DAW (“a”), the second DAW
(“b”), and the third DAW of the work group for the DAW process. The assignment of the role
of the DAW (“c”) of FIG. 4 shows the assignment of the role of the first main controller of the
work group to the main controller 11 by the role “MU”. “FU 1” and “FU 2” indicate
assignment of roles of the first and second fader controllers of the work group to the fader
controller 10. Note that these “roles” are CPU processes of the management software process,
and are “roles” assigned when the DAW process or UI device is registered as a new member in
the work group.
[0022]
11-04-2019
10
In this case, even if they are registered in another work group, if they exist on the network 2,
they are displayed in the "Outside" column 3b. In the case of illustration, DAW process named
“Conobase (PC2)” “Anotools (PC4)” “Orando (PC3)” “Conobase (PC6)” and “CTH
(M2)” “CTH (M3)” “FDH (F3) “FDH (F4)” and “FDH (F5)” UI devices exist on the
network 2 and are displayed in the “Outside” column 3b. Furthermore, the left arrow button
3c is a button for adding a member to a work group (in this case, WG1), and WG1 is selected by
selecting the member to be added in the "Outside" column 3b and clicking the left arrow button
3c. The selected member will be added to. In this case, the added member is deleted from the
"Outside" column 3b and displayed in the "Workgroup" column 3a. The right arrow button 3d is
a button for deleting a member registered in WG1, and the member selected by selecting the
member to be deleted in the "Workgroup" column 3a and clicking the right arrow button 3d It
will be removed from WG1. In this case, the deleted member is deleted from the "Workgroup"
column 3a and displayed in the "Outside" column 3b.
[0023]
In the music system management method according to the present invention, a management
session for communicating between the management software process and each member is
always established in a work group operating as a music system managed by the management
software process. There is. Also, in the work group managed by the management software
process, an interrupt session is temporarily established when the management software process
and the member communicate temporarily. An aspect of establishing a management session and
an interruption session in a work group is shown in FIG. 4 (a). As shown in FIG. 4A, in the WG1
operating as a music system managed by GM1, the GM1 operates as a server of a management
session as a client of DAW3, DAW5, DAW7 respectively. There are six management sessions
shown in solid lines between the DAW process and the M1, F2, and F3 UI devices. Furthermore,
GM1 temporarily establishes an interrupt session as needed with other DAW processes or UI
devices operating as a server. Also, in WG2 operating as a music system different from WG1
managed by GM2, GM2 acts as a server of the management session as a client of DAW2 and
DAW6, respectively, as a client of the management session, and F4 , M3 and F5 are established
with five management sessions shown by solid lines. Furthermore, the GM 2 temporarily
establishes an interrupt session as needed with other DAW processes or UI devices operating as a
server. Here, “establish a session” in the music system 1 according to the present invention
refers to “establishing a session” in the network 2 from a PC or UI device executing a
management software process serving as a client and executing a UI device or DAW process
serving as a server Establish a logical communication path (TCP connection) to the PC, and
assign the established path to a session (data exchange) between the client and the server. There
are three types of sessions, “management session”, “interrupt session”, and “control
session”, and data exchange is performed according to the session type. Also, "release a session"
11-04-2019
11
in the music system 1 according to the present invention means to release a communication path
(TCP connection) assigned to the session.
[0024]
A management session is established with a new member when GM1 or GM2 receives the first
heartbeat packet described later from a member of its work group after a management software
process is started on the PC. Is established with its members when it joins a workgroup. Also,
although the management session continues to be established while the music system is in
operation, when a member is removed from the work group, the management session with the
member is released. For example, when adding DAW 2 to WG 1, the management session
between the DAW 2 process and GM 2 is opened, and the management session is established
between GM 1 and the DAW 2 process. Furthermore, when M2 is added to WG2, there is no
management session to be released because M2 is not registered in any work group, and a
management session is established between GM2 and M2. Note that each server receives a
management session connection instruction from any client when there is no established
management session, and when there is no established interruption session, any server receives
an interruption session connection instruction. When received from a client, a connectiondirected session is established, but each server receives a management session connection
instruction from any client when there is an established management session, and an established
interrupt When there is a session and an interrupt session connection instruction is received
from any client, the connection instruction is rejected. Also, when a plurality of DAW processes
are activated on one PC, the DAW processes stand by at different port numbers. In this case,
since a plurality of PCs and a plurality of UI devices on the network 2 can be identified by the IP
address assigned to each, each management software process is a pair (socket) of the other
party's IP address and port number Any one DAW process or UI device can be identified.
[0025]
In addition, when the left arrow button 3c is operated on the GM screen 3 described above, an
interrupt session is temporarily established with a new member server (DAW process or UI
device). For example, as indicated by a broken line in FIG. 4A, an interrupt session is established
between the GM1 and DAW2 processes, and an interrupt session is established between GM2
and M2. Using the established interrupt session, the client (GM) negotiates with the new member
server and releases the interrupt session when the negotiation is completed. Here, when the
negotiation is established, a management session is established with the server, and the server is
added as a new member, but when the negotiation is not established, a management session is
11-04-2019
12
established with the server. And the server is not added as a new member. Specific conditions
under which the negotiation is established will be described with reference to step S46 of the
member addition process (FIG. 15) described later. Furthermore, when the □ in any “Identify”
column in the “Workgroup” column 3 a or the “Outside” column 3 b is clicked on the GM
screen 3 described above, the DAW process corresponding to the “Identify” column □
Alternatively, an interrupt session is temporarily established with the UI device. Then, a
confirmation message is sent to the DAW process or UI device for which the interruption session
is established by the interruption session, and the user that the DAW process or UI device that
received the confirmation message is the DAW process or UI device itself Notify Notification
methods include, for example, flashing at least one window under the control of the DAW
process, changing the brightness and color of at least one lamp on the window of the DAW
process, and the panel of the UI device, and flashing. Can be notified by
[0026]
Furthermore, in the music system management method according to the present invention, a
control session for establishing communication between the DAW process in the work group and
the UI device that controls the DAW process is always established. The aspect of establishment of
the control session in a workgroup is shown in FIG.4 (b). As shown in FIG. 4B, in WG1 which
operates as a music system managed by GM1, UI devices of clients M1, F2 and F3 are either one
of DAW3, DAW5 and DAW7 as servers. A control session is established with one DAW process,
and each DAW process has a control session established with any number of UI devices.
Specifically, the DAW 3 process establishes a control session as shown by the solid line between
M 1 and F 2 and allows the user to operate the DAW 3 process through the control session by
operating M 1 and F 2. It can be remotely controlled. Also, the control session is established
between the DAW 7 process and F 3 as shown by the solid line, and the user can remotely
control the operation of the DAW 7 process through the control session when the user operates F
3. Furthermore, in WG2 that operates as a music system managed by GM2, the UI devices of
clients F4, M3 and F5 have control sessions with any one DAW process of DAW2 and DAW6 as
servers. Once established, each DAW process has a control session established with any number
of UI devices. Specifically, a control session is established between the DAW 2 process and F 5 as
shown by the solid line, and the user remotely controls the operation of the DAW 2 process
through the control session by operating the F 5. Can. Also, the DAW 6 process remotely controls
the operation of the DAW 6 process through the control session when the control session is
established as shown by the solid line between F 4 and M 3 and the user manipulates F 4 and M
3. be able to.
[0027]
11-04-2019
13
When a plurality of DAW processes are activated in one PC, each DAW process uses a unique
port number in that PC. Thus, the PC can determine to which DAW process the control packet is
to be passed based on the port number of the received control packet. In the control session,
when an operation element for operating a parameter is operated in the client UI device, the
parameter corresponding to the operation is operated in the DAW process which is a server in
which the control session is established with the UI device. Become so. Since the DAW processes
of DAW1 and DAW4 and the UI devices of M2 and F1 are not registered in any work group, none
of the management session, the interrupt session and the control session have been established.
However, the DAW process and the UI device are in a standby state (Listen state) of each session,
and when receiving a session connection instruction, the instructed session can be established.
[0028]
Next, the hardware configuration of the personal computer (PC) of PC1 to PC7 shown in FIG. 1 is
shown in FIG. As shown in FIG. 7, the PC is a general-purpose computer, and has a CPU (Central
Processing Unit) 40 that executes an OS such as Windows (registered trademark), and a BIOS
(Basic Input / Output System) that is executed at power on. Etc., and a ROM · RAM 41 consisting
of a RAM (Random Access Memory) in which a work area of the CPU 40 and various data etc. are
stored. Further, the non-volatile memory 42 is a rewritable non-volatile memory such as a flash
memory in which software such as management software or DAW software executed by the CPU
40 is stored. Furthermore, to the PC, an operation IO 45 to which an operation Device 46 such as
a keyboard and a mouse is connected, a display IO 47 to which one or more displays 48 are
connected, and an Audio Device 44 such as a microphone, a CD player, a recorder, headphones,
and an amplifier. And an Audio IO 43 to which the Furthermore, an Ethernet network adapter
NIO 49 to which a LAN cable is connected is provided. Each unit is connected to the CPU bus 50,
and the NIO 49 is connected to the network 2. Also, on the OS executed by the CPU 40, DAW
processes such as Cubase (registered trademark), Nuendo (registered trademark), Protools,
Sonar, etc. can be started. Also, on the PC OS, a management software process (GM) can be
activated.
[0029]
Next, FIG. 8 shows an example of the functional configuration of the DAW process activated by
the PC. The DAW process is a process started on an OS such as Windows in a PC, and has a
function to perform recording, mixing, mixdown, and the like of an acoustic signal. Then, a track
11-04-2019
14
screen is opened on the display 48 of the PC, and the recording of the acoustic signal to each of
the plurality of tracks and the reproduction of the acoustic signal of each recorded track are
controlled by the GUI (Graphical User Interface) of the track screen. Can. In addition, a mixer
screen is opened on the display 48 of the PC, and each input ch, each track ch, each bus ch, and
each output ch can be controlled by the GUI of the mixer screen. Each one input (Input) of the
plurality of inputs (Inputs) to which the audio signal shown in FIG. 8 is input receives the audio
signal from the outside through one input port of Audio IO 43, and the audio signal is input on
the input channel Control the frequency characteristic, the amplitude characteristic, etc. of the
signal to be supplied to one track or bus. Also, each one track (Track) of the plurality of tracks
(Tracks) for recording / reproducing the sound signal shown in FIG. 8 receives the sound signal
from one input or bus and records in synchronization with the time code. In this case, the
adjustment of the characteristics of the audio signal to be recorded is performed at the input or
the bus. Then, the recorded audio signal is reproduced in synchronization with the time code, and
the frequency characteristics, amplitude characteristics, and the like of the audio signal are
controlled by the track ch and supplied to one bus or output. The time code indicates the current
position (current time) on the time axis of various recording and playback functions, and is a
common time for all the tracks of one project.
[0030]
Further, each one bus of the plurality of busses mixing the audio signals shown in FIG. 8 receives
and mixes the audio signals from one or more inputs or tracks. In this case, the adjustment of the
characteristics of the acoustic signal to be mixed is performed at each input or track. Then, the
frequency characteristic, the amplitude characteristic, and the like of the sound signal of the
mixing result are controlled by the bus ch and supplied to one track or output. Furthermore, each
one output of the plurality of Outputs that output the acoustic signals shown in FIG. 8 receives
and mixes the acoustic signals from one or more tracks or buses. Then, the audio signal of the
mixing result is output to the outside via the output port 1 of the Audio IO 43 by controlling the
frequency characteristic, the amplitude characteristic and the like of the acoustic signal on the
output channel.
[0031]
Next, a block diagram showing the hardware configuration of the UI device 4 is shown in FIG.
The UI device 4 is a fader controller 10 or a main controller 11 which is a physical controller,
and both controllers have the same hardware configuration. The UI device 4 has a CPU (Central
Processing Unit) 51 that executes an OS such as Windows (registered trademark) as shown in
11-04-2019
15
FIG. 9, and software such as BIOS (Basic Input / Output System) executed at power on. And a
ROM · RAM 52 including a RAM (Random Access Memory) in which a work area of the CPU 51
and various data are stored. In addition, the non-volatile Mem. 53 is executed by the CPU 51 as
described later “HB generation and transmission process” (see FIG. 11), “main process” (see
FIG. 13), “B press process” and “process of the UI device” This is a rewritable non-volatile
memory such as a flash memory in which a controller program such as the “P operation
process” and “display update process” programs (see FIG. 18) and the like are stored (see
FIG. 17). Further, the UI device 4 is provided with an operation element 54 such as a knob, a
fader, and a button, a display 55 such as a liquid crystal, and an NIO 56 which is an Ethernet
network adapter to which a LAN cable is connected. Each unit is connected to the CPU bus 57,
and the NIO 56 is connected to the network 2. A plurality of UI devices including a fader
controller (F1, F2, F3,...) 10 and a main controller (M1, M2,...) 11 are connected to the network 2.
In addition, one music system configured in one work group can include up to one main
controller and up to three fader controllers.
[0032]
Next, configurations of Ethernet frames transmitted in a management session, an interrupt
session, and a control session are shown in FIGS. FIG. 10 (a) shows the configuration of an
Ethernet frame (TCP) when TCP (Transmission Control Protocol) is used as the transport layer
protocol, and FIG. 10 (b) shows UDP (User Datagram Protocol) as the transport layer protocol.
Configuration of Ethernet frame (UDP) when using. The Ethernet frame (TCP) shown in FIG. 10A
is composed of a 14-byte EN (Ethernet) header, a 20-byte IP (Internet Protocol) header, a 20-byte
TCP header, and a data body. . The EN header indicates a preamble indicating the beginning of a
frame, a transmission destination MAC address, a transmission source MAC address, and protocol
information of a network layer above Ethernet (data link layer) (in this case, it indicates the
Internet Protocol (IP)). , Size and so on. In addition, IP header detects version, header length,
service type, packet length, identifier, protocol information of upper transport layer of IP
(network layer) (in this case, TCP or UDP), data error of the header For this purpose, it is
composed of a checksum, a source IP address, a destination IP address and the like. Furthermore,
the TCP header includes a transmission source port number, a transmission destination port
number, a sequence number, an ACK number, various flags such as ACK, SYN, and FIN, a window
size, and a checksum for detecting data errors of the header. ing. In TCP, a "sequence number" is
defined that indicates the byte position of the first byte data to be included in the current TCP
packet when the entire data to be transmitted is regarded as a byte data string, and data is
determined based on the sequence number. Alignment and window control are performed. The
ACK number is information indicating to which byte position in the same byte data string the
data has been aligned by a series of TCP packets already received.
11-04-2019
16
[0033]
The data body transmitted in the Ethernet frame (TCP) is one of a management packet, a control
packet, and an interrupt packet, and is composed of a header and a message. The management
packet is transmitted in the management session, and comprises a management header, a
management message, and a CRC code (Cyclic Redundancy Check) for error detection. A control
packet is transmitted in the control session, and the control header, control message, and CRC.
The interrupt packet is transmitted in an interrupt session, and is composed of an interrupt
header, an interrupt message and a CRC code. Based on the data in the header portion of the data
body, it is determined whether the data body is a management / control / interrupt packet.
[0034]
The Ethernet frame (UDP) shown in FIG. 10B is composed of a 14-byte EN (Ethernet) header, a
20-byte IP (Internet Protocol) header, an 8-byte UDP header, and a data body. . Since the EN
header and the IP header are as described above, the description thereof is omitted. The UDP
header is composed of a transmission source port number, a transmission destination port
number, a size, a checksum for detecting a data error of the header, and the like. The data body
transmitted in the Ethernet frame (UDP) is a heartbeat (HB) packet, and the HB packet is
composed of an HB header, an HB message, and a CRC code. Based on the data in the HB header
portion of the data body, it can be determined that the data body is an HB packet. The HB
message is a model ID that identifies the type and version of the UI device or DAW, a unique ID
that identifies each UI device or DAW process, a system ID (synonymous with workgroup ID),
management, interrupt, and control sessions. And a standby port number and the like.
[0035]
TCP is a connection type protocol that starts communication for the first time when there is a
response from the other party of communication, and a session is established before data
transfer. In addition, TCP has various functions such as three-way handshake, acknowledgment,
flow control, and congestion control in order to more reliably deliver data (segments) to the other
party. For this TCP, UDP is a protocol for transferring data without establishing a session, and
does not have the functions of the TCP described above. For this reason, UDP has low reliability
but high transfer speed, and is suitable for one-to-many communication such as multicast and
broadcast.
11-04-2019
17
[0036]
The HB packet is multicast at predetermined intervals so that all the UI devices and DAW
processes on the network 2 reach all the management software processes (GM) on the network
2. Here, FIG. 11 shows a flowchart of the HB generation and transmission process executed by
the CPU 51 and the CPU 40 executing the DAW process in all UI devices on the network 2 at
predetermined intervals, and the HB generation and transmission process will be described.
Either the CPU 51 in the UI device on the network 2 or the CPU 40 of the PC executing the DAW
process determines that the timing to execute the HB generation transmission process has been
reached and the CPU 51 or the CPU 40 executes the HB generation transmission process When it
is started, the above-described HB message including its own information is created, and an HB
packet in which an HB header is added to this HB message is generated in step S10. Next, an
Ethernet frame (UDP) in which the created HB packet is encapsulated is created and multicast in
step S11, and the HB generation transmission process ends. The destination IP address of the IP
header in the Ethernet frame (UDP) in the case of multicasting is the IP address of the multicast
group configured by a plurality of PCs on which the management software process (GM) is
operating, and the transmission of the UDP header The destination port number is one port
number common to all systems, all UI devices, and all DAW processes.
[0037]
When each management software process (GM) receives an Ethernet frame (UDP) in which an HB
packet is encapsulated, the CPU 40 of the PC executing each management software process (GM)
is stored in the ROM / RAM 41. The list is updated with the information of the HB message sent
from each UI device or each DAW process and its reception time. As a result, in the HB list, the
latest reception time, the IP address of the source UI device or DAW process, the model ID
described in the HB message, the unique ID, and the system ID for all received HB messages. , A
status flag, a standby port number and the like are stored. Since unnecessary HB packets are not
transmitted to each UI device, the processing load of each UI device can be reduced by that
amount. However, instead of multicasting, an Ethernet frame (UDP) in which an HB message is
encapsulated may be broadcasted. Here, when the management software process (GM) receives
the Ethernet frame (UDP) in which the HB packet is encapsulated, a flowchart of the HB
reception process executed by the CPU 40 executing the management software process (GM) is
shown. The HB reception process will be described with reference to FIG. When a PC receives an
Ethernet frame (UDP) in which an HB packet transmitted from any UI device and DAW process
on the network 2 is encapsulated, the CPU 40 of the PC transmits the HB as a part of the
11-04-2019
18
management software process (GM) The reception process is started, and it is determined in step
S20 whether the UI device or the DAW process specified by the HB message in the received
Ethernet frame (UDP) already exists in the stored HB list. This determination is made by detecting
a unique ID match between the HB message and the HB list. If it is determined in step S20 that
the stored HB list already exists, the process proceeds to step S21, and the HB list The existing
data update process of updating the reception time to the time when the Ethernet frame (UDP)
was received this time or updating the existing data of the HB list with the latest data by the
received HB message is performed, and the HB reception process ends .
[0038]
If it is determined in step S20 that the file does not exist in the stored HB list, the process
branches to step S22, and the UI device or DAW specified in the HB message in the received
Ethernet frame (UDP) is branched to the HB list. Add and store process information as new data.
The information additionally stored is written by the management software process (GM) when
establishing the management session, when the HB packet is received, the model ID (model,
version) described in the HB message, the unique ID, The information includes a system ID
(workgroup ID), a communication status flag indicating whether each session is established or
released, and a standby port number. In the HB list stored in the ROM / RAM 41 of the PC that is
executing the management software process (GM), while the HB packet is periodically received
from the UI device and the DAW process, information on the HB packet Is held. When the
process of step S22 is completed, it is determined in step S23 whether the unique ID described in
the HB message in the received Ethernet frame (UDP) already exists in the G list. The G list stored
in the ROM / RAM 41 of the PC executing the management software process (GM) includes UI
devices and DAWs registered in the music system (workgroup) managed by the management
software process (GM) If it is determined that the unique ID is at least stored in the G list, it is
confirmed that the user is a member of the music system, and the process proceeds to step S24.
[0039]
In step S24, the system ID (workgroup ID) described in the HB message in the received Ethernet
frame (UDP) is identical to the system ID of the music system (workgroup) managed by the
management software process (GM). It is determined whether or not you If it is determined in
step S24 that the system ID matches, the newly discovered UI device or DAW process is the UI
device or DAW process participating in the system, and the UI that has transmitted the HB
message It is confirmed that the device or the DAW process recognizes that it is a member of the
music system. Therefore, the process proceeds to step S25, and (1) processing of establishing a
11-04-2019
19
management session, and (2) initialization processing of a control session are executed. In the
process of establishing a management session, a management session is established with the port
of the standby port number among the information added to the HB list in step S22. In this case,
if the communication status flag of the information added to the HB list is “flag indicating
establishment of management session”, error processing (warning to the user is performed
instead of processing of establishing a management session). Etc.). At this time, if the GM screen
3 is displayed, the UI device or the DAW process for which the control session is established is
displayed in the column 3a in step S25 because the UI device or the DAW process participates in
the work group.
[0040]
Also, the control session initialization process is executed only when a new UI device or DAW
process is found on the network 2, and using the management session established in (1), the
control session is performed with the UI device or DAW process. Control session is established.
Although the details of this process will be described later, first, a "waiting request" is transmitted
to the DAW process, and then, an "establishment request" is transmitted to the UI device. Here, a
predetermined control session may be set, or information of the immediately preceding control
session may be stored and set (reproduced). Here, “predetermined control session” means a
control session with a predetermined counterpart DAW process, and an example of the
predetermined counterpart DAW process is one of a plurality of DAW processes. It may be the
second DAW process or the DAW process of the order corresponding to the number of the UI
device (a serial number assigned to each UI device when a plurality of same UI devices are
connected). In this case, information on each DAW process found based on the HB packet is
stored in the current memory of the management software process (GM) together with a serial
number assigned by the management software process (GM). This number is a "role" assigned
when the DAW process or UI device is registered as a new member in the work group in the CPU
process of the above-mentioned management software process (GM). Also, “preceding control
session” means a control session with a partner DAW process for which the control session was
established (now released) with the UI device immediately before. In this case, the information
specifying the partner DAW process is in the G list stored in the management software process
(GM).
[0041]
If it is determined in step S23 that it does not exist in the G list, or if it is determined that the
system IDs do not match in step S24, it is not participating in any music system (work group), or
11-04-2019
20
This is the case of a UI device or DAW process participating in another music system (work
group). For this reason, since the UI device or the DAW process that has transmitted the HB
message can not confirm it as a member of the music system (work group) managed by the
management software process (GM), the HB reception processing ends. At this time, if the GM
screen 3 is displayed, the UI device or the DAW process which can not be confirmed as a member
is displayed in the field 3 b. When the process of step S25 ends, the HB reception process ends. If
the system ID does not match in step S24 in the HB reception process, the process is ended
without doing anything, but it is indicated to the user that a UI device or DAW process having a
different system ID has been found. Also, a warning is issued, and an instruction to insert the UI
device or the DAW process from the user into the system is received, and a process similar to the
member addition process (see FIG. 15) described later is performed according to the instruction.
The UI device or the DAW process may be reincorporated into the system.
[0042]
Next, FIG. 13 shows a flowchart of the main process started when the UI device is powered on or
the DAW process is activated in the PC, and the main process will be described. When the UI
device or the DAW process is activated, main processing is started in the CPU 51 of the activated
UI device and the CPU 40 of the PC executing the DAW process, and initialization processing is
performed in step S30. In the initialization process, initialization of the work memory and the
previous setting contents are read and set. When the DAW process is activated, the project is
read, and the GM screen 3 shown in FIG. 3 is displayed on the display 48. Next, in step S31, one
standby port number is determined, and the port with that port number is placed in a state (listen
state) to stand by for "management session" and "interrupt session". In this case, the
communication frequency of "management session" and "interrupt session" is not higher than
that of "control session", so ports with the same standby port number are used, but the standby
port numbers are mutually exchanged. It may be different. In that case, if both standby port
numbers are described in the HB packet, any management software process (GM) has different
port numbers for "management session" and "interrupt session" based on the HB packet. It can be
established using two ports.
[0043]
A plurality of applications such as a plurality of DAW processes can be simultaneously launched
in one PC by PC1 to PC7, and different port numbers can be set to the respective applications.
Therefore, when a plurality of DAW processes are activated by the PC, different standby port
numbers are determined among the plurality of DAW processes, and a standby communication
11-04-2019
21
path for each DAW process is prepared. On the other hand, since only the controller software is
launched on the UI device, there is no restriction on the standby port number determined by the
UI device, and an arbitrary standby port number can be determined. For example, it can be a
predetermined port number common to all UI devices.
[0044]
When the process of step S31 ends, the process proceeds to the processes of steps S32 to S34.
However, the processes of steps S32 to S34 are event-driven processes, and when the user does
not operate the operation, the process waits. Event processing is performed when the user
performs an operation on the control. That is, detection of an event is performed in step S32, and
it is determined whether there is an event or not in step S33. If it is determined in step S33 that
there is no event, the process returns to step S32, and the process of step S32 and step S33 is
repeatedly performed, so the process is in the standby state. Then, when the user operates any of
the controls provided on the UI device or any of the controls displayed on the display of the PC
by the DAW process, there is an event for the controls in step S33. Is detected and the process
proceeds to step S34, and a process corresponding to the detected event, that is, the operation
content of the operation element is performed in step S34. In addition, progress of the current
time of the DAW, time-up of the timer, operation of the mouse connected to the PC as the
operation Device 46, data reception from other devices, data reception from other processes in
the same device, etc. At the same time, an event is detected in step S33, and a process
corresponding to the detected event is performed in step S34.
[0045]
Next, the procedure of session establishment, data transfer, and release common to the
management session, control session, and interrupt session will be described using FIG. The
establishment of logical paths in this procedure conforms to the standard connection
establishment, data transfer, and release procedures in TCP. In the case of establishing each
session described above, an Ethernet frame (SYN (connection instruction) flag in the TCP packet
is set to “1” to the host B, which is a client in the listen state) TCP) is sent over the network 2.
The destination IP address in this Ethernet frame (TCP) is the IP address assigned to the host B,
and the port number is set to the standby port number of the host B. If the session to be
established is a management session or an interrupt session, host A (client) is a PC executing a
management software process (GM), and host B (server) executes a UI device or DAW process It
is a PC that is doing. The host A transmits a SYN (connection instruction) using the IP address of
the host B stored in the HB list and the standby port number. The transmission of the SYN
11-04-2019
22
(connection instruction) is performed by transmitting an Ethernet frame (TCP) with the SYN flag
set to "1". When the session to be established is a control session, host A (client) is a UI device,
and host B (server) is a PC executing a DAW process. Which host A and which host B are
connected is under the management of the management software process (GM), and the host A is
instructed by the CPU 40 executing the management software process (GM) with an IP address
and standby port number Send SYN (connection indication) using.
[0046]
The host B, which has received the Ethernet frame (TCP) with the SYN flag set to “1”
transmitted from the host A, establishes the connection in response to the connection instruction
from the host A and establishes the session from the host B. The Ethernet frame (TCP) in which
the required SYN flag and ACK flag are set to “1” is transmitted to the host A via the network
2. The host A responds to this and establishes a connection, and transmits an Ethernet frame
(TCP) with an ACK flag set to “1” to the host B via the network 2. This establishes a session.
The method of establishing this session is called a 3-way handshake. When a session is
established (ESTBLISHED), host A can send data to host B, and host B can send data to host A
using this session. Since the amount of data that can be sent in Ethernet frame (TCP) is a
predetermined amount, data is generally divided into a plurality of pieces and transmitted. The
state of transmitting data thus divided is shown in the sequence diagram as a “DATA”
sequence from host A to host B. As illustrated, when the host B normally receives the data
divided into two, the host B transmits to the host A an Ethernet frame (TCP) in which the ACK
flag is set to “1”. Also, in the sequence diagram, when the host A normally receives the data
divided into two shown by the “DATA” sequence from host B to host A, the host A has ACK flag
“1”. Send the Ethernet frame (TCP) to host B.
[0047]
Then, when releasing the established session, the Ethernet frame (TCP) in which the FIN
(disconnect instruction) flag is set to “1” is transmitted to the other host via the network 2. In
the case shown, the host A transmits to the host B via the network 2 an Ethernet frame (TCP) in
which the FIN (disconnect instruction) flag is set to “1” to the host B. The host B, which has
received the Ethernet frame (TCP) with the FIN flag set to “1” transmitted from the host A,
performs connection release in response to the disconnection instruction from the host A and
releases the session from the host B. The Ethernet frame (TCP) in which the FIN flag and the ACK
flag to be requested are set to “1” is transmitted to the host A via the network 2. In response
to this, the host A releases the connection, and transmits an Ethernet frame (TCP) in which the
11-04-2019
23
ACK flag is set to “1” to the host B via the network 2. This opens the session. As a result, the
session in the host B changes from the established state (ESTBLISHED) to the waiting state
(Listen).
[0048]
In the session establishment sequence, a session should be established if an ACK does not return
within a predetermined time, or if an ACK (NACK: Negative ACKnowledgement) indicating that
the server is not in a standby state is transmitted. I can not Also, when there is no access to each
session for a predetermined time or more, the timer times out and the session is automatically
released. Therefore, in the embodiment of the music system management method according to
the present invention, with regard to the management session and the control session, dummy
data (KeepAlive packet) for continuing the session immediately before the time when the data
transmission is not performed Is supposed to send. This allows, once established, management
and control sessions to continue until the music system is shut down.
[0049]
The management software process (GM) displays the GM screen 3 shown in FIG. 3 on the display
48 of the PC based on the data of the HB list. Since the HB list is updated each time the HB
reception process of FIG. 12 is executed, the GM screen 3 displays the latest UI devices and DAW
processes present on the network 2. In the "Outside" column 3b of the GM screen 3, the user
selects a desired UI device or DAW process (hereinafter referred to as "target D") and operates
the left arrow button 3c ("(") When the selection of the target D is accepted, the CPU 40 of the PC
executing the management software process GM executes the member addition processing of the
flowchart shown in FIG. This member addition process will be described below. In addition,
general users of the system can not perform the operations of “Add ())” and “Delete (→)” on
the GM screen 3 shown in FIG. 3 and operations permitted only by the system administrator is
there. In the GM screen 3, when the left arrow button 3c ("に お い て") is operated, the CPU 40
of the PC executing the management software process GM starts member addition processing
and executes the management software process (GM) The HB list stored in the ROM / RAM 41 of
the PC is referred to in step S40, and the information described in the HB message of the object
D selected in the "Outside" column 3b of the GM screen 3 is read. Then, it is determined in step
S41 whether there is any other system ID that is not the music system (work group) managed by
the management software process executing the member addition process in the HB message of
the target D. .
11-04-2019
24
[0050]
If it is determined in step S41 that there is no other system ID, the object D is not registered in
any music system (work group), so the process proceeds to step S42 and the management
session with the object D is performed. And write the system ID of the music system managed by
the management software process to the target D through the management session. Next, in step
S43, initialization processing of the control session is performed. When this initial setting process
is performed, a control session is established between the UI device controlling the object D or
the DAW process controlled by the object D using the management session established in step
S42. Then, in step S44, the target D selected in the "Outside" column 3b on the GM screen 3 is
erased, and the target D is displayed in the "Workgroup" column 3a. Thus, the member addition
process ends.
[0051]
If it is determined in step S41 that there is another system ID, that is, if the UI device or the DAW
process participates in another system, the target D is another management software process
(GM ' Since the management session is established between the management software process
and the management software process, the process branches to step S45, and the interrupt
session with the object D is read out, and the HB read out. Establish with the standby port
number described in the list. In this case, if the target D is in an interrupt session with another
management software process (GM '), the end is waited for. However, if the waiting time can be
too long, the user is warned accordingly. Then, in step S46, negotiation is performed with the
target D as a member using the established interruption session. Then, when the negotiation is
established, in order to remove the target D from the music system (work group) currently being
a member, the target D uses the existing management session to execute the other management
software process (GM ' And the other management software process (GM ') releases the
management session in response to the release request. The negotiation here is established and
registered, for example, when the user who has logged on to the management software process
(GM) is registered (has authority) to another management software process (GM '). If it does not,
it may be set to be unsatisfied. Alternatively, the negotiation may be established if the setting of
“prohibit preemption” is not performed on the target D, and may not be established if the
setting is performed. Alternatively, as described above, since users who can execute the member
addition process are limited to the administrator, the negotiation may be unconditionally
(necessarily) established regarding step S46. Next, the interrupt session established in step S45 is
released in step S47. When the process of releasing the interrupt session is completed, in step
S48, it is determined whether the management session requested to the other management
11-04-2019
25
software process (GM ') has been released. Here, with reference to the flag indicating the status
of the management session of the target D, when it is determined that the management session is
released, the above-described processing of steps S42 to S44 is performed, and the member
addition processing is executed. The target D is added to the members of the music system
managed by the management software process (GM). If it is determined in step S48 that the
management session is not released, the target D is still a member of the music system managed
by another management software process (GM '), and the target D is a member. Since it can not
be added, the process proceeds to step S49 to warn the user by, for example, displaying on the
display 48 of the PC that it can not be intercepted.
When the process of step S44 or step S49 ends, the member addition process ends. A plurality of
targets D may be simultaneously selected and added on the GM screen 3. In this case, the abovedescribed process is performed for each of the plurality of selected objects D.
[0052]
The management software process (GM) monitors the reception time of the HB message in the
stored HB list, and when the reception time has not been updated and a predetermined time or
more has elapsed, that is, the UI having data in the HB list An HB executed by the CPU 40 of a PC
executing a management software process (GM) when an HB packet from a device or a DAW
process (hereinafter referred to as "target D") can not be received for a predetermined time or
more. A flowchart of the error processing is shown in FIG. 16 and the HB error processing will be
described. The management software process (GM) is detected when it is detected that the
elapsed time from the reception time exceeds a predetermined time for any of the objects D
among the objects D in the HB list stored in the management software process (GM). The CPU 40
of the PC that is executing H) starts HB error processing, and accesses the target D using a
management session in step S50. In this access, for example, an Ethernet frame (TCP) of an
empty data body is transmitted to the target D. Then, it is checked whether the Ethernet frame
(TCP) whose ACK flag is “1” is returned from the object D. When the Ethernet frame (TCP) is
returned, the target D is present in the music system (work group) managed by the management
software process (GM), so the target is selected in step S51. It is determined that D is present,
and the process branches to step S54. In step S54, the reception time from the target D in the HB
list is updated to the current time, and the HB error processing ends.
[0053]
11-04-2019
26
Further, when there is no reply of the Ethernet frame (TCP) from the target D, the target D does
not exist in the music system (work group) managed by the management software process (GM).
In this case, it is determined in step S51 that the subject D is not present, and the process
proceeds to step S52, and the subject D is deleted from the HB list stored in the management
software process (GM). Then, the target D is deleted from the "Workgroup" column 3a on the GM
screen 3 in step S53. This completes the HB error processing. By the processes of steps S23 to
S25 and step S53 described above, only the UI devices and DAW processes whose existence is
currently confirmed by the reception of the HB message are displayed in the columns 3a and 3b,
and the HB message is displayed. UI devices and DAW processes that have not arrived are
controlled not to be displayed.
[0054]
In the music system control method according to the present invention, when the selection
button for selecting the DAW process controlled by the UI device is operated on the UI device,
management software for managing the UI device and the music system of which the UI device is
a member A series of processes are performed in the process (GM) so that the selected DAW
process can be controlled by the UI device. At this time, the process performed when the B
(button) is pressed by the CPU 51 in the UI device and the management software process (GM)
for managing the music system of which the UI device is a member A flowchart of the pressing
reception process is shown in FIG. 17, and a series of processes will be described. When one of
the selection buttons 26 is operated in the fader controller 10 which is a UI device, or when any
one of the selection buttons 31 is operated in the main controller 11, the CPU 51 in the UI device
in which the selection button is operated A process at the time of pressing B is started, and
information on which DAW process has been selected by operating the selection button uses a
management session to manage the music system of which the UI device is a member (GM
software process (GM In step S60). As a result, the processing at the time of pressing B ends, and
when the management software process (GM) managing the music system of which the UI device
is a member receives the above information, the selection of the DAW process is accepted, and
the management is performed. The CPU 40 of the PC executing the soft process (GM) starts the B
press reception process.
[0055]
When the B press reception process is started, it is determined whether the selected DAW
process is the same as the DAW process of the other end of the current control session
established in the UI device. Here, since it is not necessary to change the current setting if it is
11-04-2019
27
determined that they are the same, the B press reception process is ended, and when it is
determined that they are not the same, the process proceeds to step S62. In step S62, the PC
executing the management software process (GM) transmits a release request of the current
control session to the UI device using the management session. The UI device that has received
the release request of the current control session transmits a disconnection instruction (FIN) to
the PC executing the DAW process of the connection destination using the control session,
whereby, as shown in FIG. The control session is released according to the procedure shown.
Then, the UI device that has confirmed the release transmits a release response notifying that the
control session has been released to the PC executing the management software process (GM)
using the management session (step S66). . In response to this, the PC executing the management
software process (GM) uses a management session to the PC executing the DAW process selected
in the UI device for a new control session. The standby request is transmitted (step S63). In step
S67, not only is this port number determined as the standby port number, but also the server
operation using that port number is started. That is, the PC executing the DAW process receives
the standby request, determines an unused port number in the PC as the standby port number,
and serves as a server at the port indicated by the standby port number. The standby operation
of the control session is started, and a standby response in which the standby port number is
entered is transmitted to the PC executing the management software process (GM) using the
management session.
[0056]
The PC (management software process (GM)) that has received this standby response sends to
the UI device the IP address of the PC executing the DAW process and the standby port described
in the standby response. The control session establishment request including the information of
the number is transmitted through the management session (step S64). The UI device that has
received the establishment request transmits a control session connection indication (SYN) to the
port with the same port number of the PC of the IP address described therein, whereby the
diagram of FIG. According to the procedure shown in 14, a control session between the PC and
the DAW process is established. Then, the UI device that has confirmed the establishment
transmits an establishment response notifying that the control session has been established to
the PC executing the management software process (GM) using the management session (step
S68). Here, if all the processes in steps S66 to S68 are successful and a control session between
the UI device and the selected DAW process is established, the management software process
(GM) is in charge of the UI device. A lighting request of the operated selection button is
transmitted through the management session (step S65). The UI device that has received the
lighting request turns off the selection button that was on before the selection, turns on the
selected selection button, and indicates that the selected selection button is turned on.
Management software process (GM) (Step S69). In the management software process (GM), it is
11-04-2019
28
confirmed that there is a response indicating that the selection button has been turned on, and
the B pressing reception process is ended. If any one of the processes in steps S66 to S68 fails,
an error display indicating the occurrence of an error is performed on the display device of the
PC executing the management software process (GM).
[0057]
As described above, the UI device is connected to one of the DAW processes via the control
session, and a series of processing is performed by operating the controls provided on the UI
device, and the parameters of the DAW process are processed. Can operate. At this time, the
flowchart of P (parameter) operation processing and display update processing performed by the
CPU 51 in the UI device and P operation reception processing performed by the CPU 40 of the
PC executing the DAW process controlled by the UI device are shown. This series of processes is
described with reference to FIG. When one of the operators provided in the UI device is operated,
the CPU 51 of the UI device starts the P operation processing, and the P (parameter) operation of
the operator operated using the control session in step S70. The UI device sends an event to the
DAW process using a control session. As a result, although the P operation process is completed,
the CPU 40 of the PC executing the DAW process that has received the P operation event starts
the P operation reception process, and the corresponding parameter value is changed to the P
operation event in step S71. Change accordingly. Next, in step S72, display data corresponding to
the change result of the parameter value is transmitted to the UI device using the control session.
As a result, although the P operation reception process is ended, the CPU 51 of the UI device
having received the display data starts the display update process, and the value of the
parameter is displayed based on the display data in step S73, When the operated operator is a
button, the LED is lit, or when the parameter is at the fader level, the fader 21 is driven. Thus, the
display update process ends. Note that, as target parameters that can be manipulated in the UI
device, opening or closing of various screens displayed on the display 48 of the PC on which the
DAW process has been started, and setting of the position of the acoustic data on the time axis
regarding the track Recording start and stop, playback start and stop, etc. For the mixer screen,
parameter settings for each input channel, each track channel, each bus channel, each output
channel, and for each channel, the fader value , On / off, send level value, equalizer setting,
compressor setting, etc. Furthermore, it is taken as the operation of the setting of the plug-in
effect inserted in each ch.
[0058]
In the music system management method according to the present invention described above,
11-04-2019
29
the management software process first establishes a management connection between the
selected music software process and the controller on the network. Then, through the
management connection, a control connection is established between each controller and the
desired music software process. Then, remote control of the music software process by the
controller is performed via the control connection. In the music system management method
according to the present invention, the GM screen 3 shown in FIG. 3 is displayed so as to identify
to which music system the UI device or the DAW process belonging to another music system can
be identified. It is also good. Also, although the music system described above is a system
configured by the DAW process and the UI device, the music system management according to
the present invention is a system by the mixer engine and the UI device, a system by the sound
source device and the UI device, etc. The method may be applied. In that case, the management
software process (GM) may be started by a separately prepared PC, or may be started by the
mixer engine or the CPU of the sound source device. Also, the user can remotely control the
mixer engine, the sound source device and the like with the UI device. In the music system
management method according to the present invention, whether the type of each session is a
management session or a control session depends on the management software process, the
DAW (music software) process, and the UI device (controller), respectively. It distinguishes for
each session established for itself, and when transmitting a packet through a session, it forms
and transmits a packet according to the type of the session. In the music system management
method according to the present invention, all sessions are all TCP connections, and the
difference in type here is the difference in flowing packets. Further, in the music system
management method according to the present invention, the network technology standard is not
limited to Ethernet, and other network technology standards can be adopted. In this case, the
data configuration of the frame or packet according to the adopted network technology standard
is adopted. Furthermore, the panel configuration of the controller is an example, and the
operating element may be a rotary encoder or the like, or a desired type of operating element or
the like may be disposed at an arbitrary position. Furthermore, the controller may be replaced
with a physical operator, and may be an operator of a UI screen displayed on the display, for
example, a tablet terminal installed with controller software may be used as the controller.
Furthermore, the hardware configuration of the PC or UI device is an example, and is not limited
to the illustrated configuration.
[0059]
1 Music System, 2 Network, 3 GM Screen, 3a "Workgroup" Column, 3b "Outside" Column, 3c Left
Arrow Button, 3d Right Arrow Button, 4 UI Device, 10 Fader Controller, 11 Main Controller, 20a
Strip Section , 20b control unit, 21 fader, 22 ch name display unit, 23 knob, 24 first operator, 25
second operator, 26 selection button, 26a to 26c button, 31 selection button, 31a to 31c button,
40 CPU, DESCRIPTION OF SYMBOLS 41 ROM.RAM, 42 Nonvolatile Mem., 43 Audio IO, 44 Audio
11-04-2019
30
Device, 45 Operation IO, 46 Operation Device, 47 Display IO, 48 Display, 49 NIO, 50 CPU Bus,
51 CPU, 52 ROM. RAM, 53 Nonvolatile Mem., 54 controls, 55 indicators, 56 NIO, 57 buses, DAW
music Shift, GM management software process, PC1~PC7 PC, M1~M3 main controller, F1~F5
fader controller
11-04-2019
31
Документ
Категория
Без категории
Просмотров
0
Размер файла
56 Кб
Теги
description, jp2014093624
1/--страниц
Пожаловаться на содержимое документа