Advertisement
Set:RampStep:Attack=<0-1000> // default 20
Set:RampStep:CompensationLevel=<0-1000> // default 250
Set:RampStep:Decay=<0-1000> // default 20
Set:RampStep:DigitalGain=<0-1000> // default 20
Set:RampStep:Effect=<0-1000> // default 20
Set:RampStep:EQ:Freq=<0-1000> // default 20
Set:RampStep:EQ:Gain=<0-1000> // default 20
Set:RampStep:EQ:Q=<0-1000> // default 20
Set:RampStep:Gain =<0-1000> // default 20
Set:RampStep:Hold=<0-1000> // default 20
Set:RampStep:Knee=<0-1000> // default 20
Set:RampStep:Range=<0-1000> // default 20
Set:RampStep:Ratio=<0-1000> // default 20
Set:RampStep:Release=<0-1000> // default 20
Set:RampStep:ResponseTime=<0-1000> // default 20
Set:RampStep:Threshold=<0-1000> // default 20
Set:RampStep:Volume=<0-1000> // default 20
There are no ramping commands in the raw MTX5-D protocol. This COMM module tracks the status of
each parameter and sends a discrete command to raise or lower the value by these increments. If you
want larger steps for these commands, you could send this in when the module comes online.
Set:StatusSyncInterval =<msec> // default 250
When the control port comes online, the module begins a timeline to scan the status of all tracked features
on the MTX5-D. This adjusts the polling interval of this timeline, in case your processor requires more
headroom to run other events.
SCPMode:Encoding=<UTF|ASCII>
SCPMode:KeepAlive=<Interval in msec>
SCPMode:Resolution=1000
SCPMode:Value=<1:Normalized|0:Raw>
These are used by the module to set preferred protocol values. AMX Programmers should not change
these values – that could cause the module to stop working properly.
DevInfo?
DevInfo:DeviceID=<String>
DevInfo:DeviceName=<String>
DevInfo:ParameterSetVersion=<String>
DevInfo:ProductName=<String>
DevInfo:SerialNumber=<String>
DevInfo:FirmwareVersion=<String>
DevStatus:Clock?
DevStatus:Clock=<0 (unlocked)|1 (locked)|2 (not scanned)>,<44.1kHz|48kHz>
AMX Control Module for: MTX5-D Matrix Processor Rev.1
Set-Up/Debug Commands
7
Advertisement
