If you have a built-in Preset Performance that does this - it would be good to start there. Let us know which preset (specific Preset Performance name) does this (that you recall by using Live Set) then the reason why this happens can be applied to that specific Performance.

[quotePost id=111626]Hi forum members.

I've recently upgraded from my trusty moxf to an modx. I'm currently using it also as an audio interface with a macbook and ableton in a hybrid setup, where I fire off loops and mix plugins with internal sounds.
This has worked fine previously with moxf, though the modx does show some strange behaviour.
My whole main Usb monitor mix signal occasionally pans right when changing performances in my Live Set. Somehow the panning corrects itself back to center when the same performance is pressed again via touchscreen. It's super strange. I could limit this problem to specific performances, but by the love of god cant explain myself why it does that.
First thought was that its maybe sending some weird cc signal, but thats not the case, I've checked on my DAW, signal is centered.

Is it bug?
Have anyone of you encountered a similar problem?

Modx firmware is 2.5.1 connected with an MBP 10.14.5 mojave[/quotePost]I doubt that it’s a bug. It sounds very much like MIDI commands are being routed through your system improperly — that is, it sounds like a MIDI Setup error.

The MODX is a multiple port MIDI device via USB (if you are using the MODX via USB-MIDI)
Port 1 - concerns the MODX Tone Generator itself. In/Out
Port 2 - is to be used for bi-directional Remote Control messaging for DAW/plug-ins, etc., on the computer. Using the MODX front panel to address DAW functions. (Must be kept discreet).
Port 3 - is reserved for an external device via the 5-pin MIDI Ports. Midi data bypasses MODX entirely - works as interface for an external device.

If you have inadvertently merged Ports 1 and 2, you might get strange behavior due to MIDI messages traveling between your gear.

Not really enough information to decipher the exact issue.

From what you have stated: Since the issue straightens itself out when you initiate the command message from the MODX itself — this is a clear indicator things are fine with the programming done at your MODX. The error is before this point.

Since it is impossible for the MODX to receive a command and simultaneously send a different command (— if that is what you are attempting, that usually doesn’t work—)… check the messages being sent at the origin. In MIDI (1.0 at least) a device is a Master or a Slave (it can’t be both). If you attempt to have a device act in response to an incoming message (act as a ‘slave’) it cannot (usually) generate a simultaneous message (act as a ‘master) to another device. (Not without a sequencer that can reSend a message after getting a command to Start).

This would explain why when you actually SEND the commands by operating the MODX front panel, it works.

If you were to send a Note (middle “C”) into the MODX, it will not simultaneously be able to send out middle C or any other Note, unless, of course, you actually operate the MODX keyboard. Typically, you would Thru the original message from source to that other device.

Likewise you cannot send a message to the MODX and then have the MODX execute a function that would normally require your physical touch.

What to try: Setup a situation where your Source (presumably Ableton) is addressing each ‘slave’ device directly. You can do so by utilizing the Yamaha Steinberg USB Driver’s Port #3 — to send data THRU the MODX. Data assigned to MIDI Port 3 in your computer will be fed Out via the 5-pin MIDI Port on the MODX back panel… without impacting the MODX tone engine.

[quotePost id=118838]SPAM/VIRUS - beware - the Synthadmin reply above has a hidden link at the start of the second line.
[/quotePost]

Yamaha's software skills are first rate.

They've clearly banned/blocked this user, but left the post up, and added their admin name to the post... because we all know their software skillz are such that that's the posts we should avoid?