MRX7
ccherpion
Posts: 6
Hello,
I have some issues with programming an MRX7 with MUSE Automator.
We do not understand how this duet module is working with a MUSE controler.
We are not able to use the level and the mute, even with an Event or to Send a command.
Thank you for your help.
Regards,
0
Answers
I had a first look into it.
The module manual brings the first confusion, as it shows sample NetLinx code lines that don't match to the command syntax in the command list.... But well, this may be a copy-and-paste mistake.
Regarding the commands itself, the NetLinx code shows
SEND_COMMAND vdvYamahaMRX7,"'AUDIOPROCADD-1,1:S'" // state
This would mean it is the 1st object (so netLinx Port 1 on the Duet Device) to control, with address 1 and type state, which for NetLinx will be provided on channels 26/199. (Similar to type "L", that in NetLinx will be provided to Level 33)
But looking deeper into Muse/Automator, the module offers no channels and levels, but only a "state" and "level" parameter (and a lot of other parameters). So that type definition "S" may not be required for Muse, but maybe the module will not accept the command without it....
I don't have a MRX7 on hand, but I will try to do a little Automator sample (also to get more practice with Automator) I think it may work.
Thank you for your feedback.
We are installing the system for our client today.
I hope we will find the solution.
Let me know when you try it.
Best regards,
I gave a try, as far as possible...
Attached the flow to import. It's .txt, because other formats are not allowed to post.
So either change the file back to .json, or copy the content to clipboard, to import to Automator
I named the Module Instance "MRX7", see screenshot.
So it is required to rename yours, to get it correct into the flow.
Like said, little confusion between Manual and NetLinx code (see comment in node "Confusing AUDIOPROCADD-"), "best guess" as I don't have that unit for testing.
Good luck
Hi Marc,
I tried your flow but except the "state" function, nothing else is working.
The "state" function is not working as it should be. He put the fader at 0 dB.
Do you have any idea ?
Thank you.
Best regards,
I believe this may go deeper into how Muse is working...
Muse will import the module descriptor ("what functions does the module support") at the moment the instance is created on the webpage of the MU controller. This is also why you have to define the number of inputs and outputs there, so the descriptor can provide the required number of component instances for control.
But at this point, the channels and levels that are created by the AUDIOPROCADD command later, are not available yet, and so they are not provided by the descriptor. The "reinit" of the module may restart the module and so provide the channels and levels "on NetLinx level", but it will not recreate the Module descriptor that Muse needs to provide functions, and so none of these dynamically created channels and levels are accessible by Muse.
Otherwise the descriptor more or less provides the standard parameters of the Duet class "Audio Processor", which includes parameters "state" and "level", and which are provided and I used in the flow.
But by the behavior seen now, I assume theses parameters are not functionally within the Duet module, and so have no effect...
Comparing the Duet "Audio Processor" class commands with the module manual, only very few commands are implemented into the module, including state and value are not implemented.
I don't think that there is any workaround possible, even not on Muse scripting level (as also the scriptings are based on the descriptor of the module, and if there is no channel or level available, it can't be set or get).
So this may have to be fixed/added to the Duet module by Harman's ITG team...