Understanding the MTX Universal Driver Control Targets

Understanding the MTX Universal Driver Control Targets

The following information outlines how the MTX Universal Driver interacts with the Yamaha MTX3 or MTX5-D audio processors. 

Primary Control Targets

The MTX Universal driver uses the following for primary control targets in the Control4 system
  1. Channel Input Level and Mute
  2. Matrix Cross Point Level and Mute 
  3. Zone Master Level and Mute
  4. Router Output Channel Level and Mute
  5. Matrix Output (volume only)
  6. DCA Input Volume Groups A-H
  7. DCA Input Mute Groups A-H
  8. DCA Output Volume Groups A-H
  9. DCA Output Mute Groups A-H 
On the block diagram (MTX3) below you can see where these control targets exists in relation to other functions of the processor. The MTX5-D includes a larger 24-channel* mixer and 8 additional zone outputs, however the block diagram is generally the same. 

* The purpose of the statement above is to simply explain to the casual reader that one device is just bigger than the other and has more stuff. 5 is larger than 3, after all.

Stereo Inputs and Outputs

The introduction of mono channel inputs present design and programming challenges for the installer. Consider the following statements:
  1. The MTX Universal Driver allows for the use of mono input devices, such as microphones, summed stereo devices that use a single channel of audio, and regular stereo devices.
  2. The MTX Editor allows the installer to customize the system with even-odd channel pairing for stereo inputs and stereo outputs for any given installation.
  3. A Control4 system has no concept of mono or summed stereo audio and all audio must be routed with standard stereo AV bindings. 
To better understand how to handle this collision of features inside the Control4 ecosystem please review the [MTX Universal Stereo Input and Output Programming Guide].

Control Target 1: Channel Input Level and Mute

These controls are the "mixer" controls one would think of when using a standard mixer. This is the Global Level that is sent to all Matrix Inputs. These control points cannot be used by Control4 Director and require some custom configuration or the Mixer UI Driver to control properly.

Pro Tip: With the MTX3/5-D it is recommended to install the system and get the channel inputs in a state where the gain is properly set, processing is active, and the levels are set. There is typically no reason to adjust the global volume level for any device and the Matrix Sends can achieve a custom "sub-mix" on a per-zone basis. The flexibility of the MTX processor allows for many installation applications and this suggestion may not always be applicable.

Control Target 2: Matrix Send Levels and Mute

The matrix is the heart of the MTX system and what enables us to use it as a simple, "standard audio matrix" in the Control4 system. These control points are used to emulate a standard audio matrix by enabling and disabling matrix sends at the matrix crosspoint. 
  1. Director will enable and disable one Matrix Send input per zone and has no support for two sources being on at the same time in the same zone
  2. The driver has a "Configure Matrix" button in the Action tab that will pre-configure the matrix for Control4 programming. This button executes a series of commands that disables all sends in each zone and sets the zone outputs to 75%. This really should only be used once when configuring the system for the first time. [see MTX Universal Driver Getting Started Guide]


Control Target 3: Zone Outputs 

The Zone output controls are exactly what you would expect them to be, volume and mute control for the zone. These operate exactly how you imagine in the Control4 ecosystem. If a Zone Output is set as a stereo output it is recommended to only use the odd output binding in Control4 as the room's audio end-point. See the [MTX Universal Stereo Input and Output Programming Guide] to better understand how this driver handles mono and stereo outputs.

Control Target 4: Matrix Output

This control target will allow for the control of the Matrix Output Volume. A Mute command is not supported for this control target. 

Control Target 5: Router Output Level and Mute

This control target enables direct control over the MTX output levels and mute after the router. This could be very useful in some situations where multiple zones outputs of the Matrix make up a larger zone. For example, four patio zones are all "Outdoor" zones that require a single volume control and mute. This also can be handy if using a stereo zone with mono subwoofer zone.

Control Target 6 & 7: DCA Input Groups

This control target will allow for support of DCA Input Volume and Output Mute groups A-H. DCA groups allow for a flexible group volume and mute control over over multiple channels in one operation. A common use of this control would be to group all microphones in the room under one volume control slider.

Control Target 8 & 9: DCA Zone Output Groups

This control target will allow for support of DCA Zone Output Volume and Output Mute groups A-H. DCA groups allow for a flexible group volume an mute control over over multiple channels in one operation. The function is similar to the Output Channel Level and Mute control target above and may cover some of the use cases above, however, it operates somewhat differently within the system and it may be up to the discretion of the installer as to which one would best apply to the system. This control target also works well when controlling a room which may have more than one zone output from the matrix for a stereo pair and subwoofer.

Configuring advanced configurations are outside of the scope of this driver, however, they are regularly covered in Yamaha's manufacturer training courses.  

Controls not targeted by the MTX Universal Driver

The philosophy behind this driver is substantially different than a normal Control4 driver. We believe the MTX processor is great at what it does, and the Control4 processor is great at what it does. However, the MTX doesn't control AV, and Control4 doesn't mix audio sources. To that end, this driver is purposefully designed to keep the two systems separated just enough that they both can do what they do best. Ideally, the MTX processor can take commands from the Control4 system and Control4 can react to changes made on the MTX. This allows for unparalleled flexibility in system design and easy of use for the end user. 

With that in mind, we have purposefully designed integration for only the control targets listed on this page. If you have a suggestion or use case for additional control targets please fill out a support ticket and we will review the request.