I am not very sure if this is a bug, but I was using Touch Osc to change patches in Mainstage with MG3 3.0.55 ver and it was working fine… But now in the new version when I change patches from Touch Osc the patches changes and shows the correct name in Mainstage but the sound is of either different patch or Default MG3 mini patch is selected by default. This is happening to only those patches in which I have used MG3. Other patches are switching and sounding fine.
In the same concert as far as I am switching the patches with my Line6 FBV 3 pedal everything is fine but as soon as i touch the Touch osc interface on my tablet the patches seems to be mixed up… Same patch name with different instrument or DI sound.
Is there anyone else using Touch Osc with MG3.??
I don’t use TouchOSC with MIDI Guitar 3 (MG3) and Mainstage 3 (MS3) specifically, and I’m no expert on MS3, but I’ve briefly tested them together. I’m also not exactly sure what role TouchOSC plays in your setup. Maybe this will give you some ideas for troubleshooting.
Basic TEST: In my concert I have a global audio track hosting MG3 with the “MIDI Guitar MINI” preset – it has a guitar signal as input. Then, I have six presets. Some MS3 presets/patches are instruments driven by MIDI from the MG3 global track while some have unique instances of MG3 loaded to emulate your setup. All six presets load correctly when receiving MIDI PC messages from an external MIDI controller. I’m not experiencing any unusual behaviour with MG3 changing from preset to preset.
Since you have an issue, it is probably something in your TouchOSC template or maybe something to do with how you have things configured in MS3. I’d suggest checking traffic from TouchOSC with a MIDI Monitor.
On a fundamental level, MS3 generally wants PC messages to selct concerts/sets/patches. I’m guessing maybe your PCs are getting passed through to MG3 and confusing things – doubling up…perhaps?
Have you closely inspected your TouchOSC template to make sure there are no issues?
I’m also thinking that if the preset structure in MG3 changed at all since MG3 version 3.0.55, then maybe your preset numbers could be out of sync with your original MS3 set, though that should only matter if you are passing through messages to change MG3’s presets inside the hosted plugin rather than having an instance per MS3 preset.
I hope you can find something useful here.
Update : I have programmed touch osc layout to change presets as type -program change by numbers (0-127) . Initially it was changing the presets according to Program numbers of Mainstage but after the update i lately noticed the presets are changing according to my saved patches in MG3 serial wise. For example if i select 3rd preset on touch osc the preset is changing but not the 3rd listed Program (preset) in mainstage but the 3rd saved patch in MG3. Infact as soon as i touch the screen interface of TouchOsc all the presets are reset according to MG3’s patch list regardless of the names and preset list in mainstage.
Btw thanks for the reply @Vaultnaemsae, as per your question “what role Touchosc plays in my setup” is i use it to change patches in live scenario on my Android Tablet and phone both. That way i have full control on patch changes with just a touch on my tablet mounted on a stand. I am attaching some screen shots of my TouchOsc layout for reference.
I was playing with this a little.
In my recent tests I’ve confirmed that the MG3 Audio Unit receives and responds to MIDI PCs globally. That means the plugin will detect any PC message and a preset change will be executed – if there is a preset available at the given index. This is dependent on your user prest configuration and how many presets you have.
VST2/3 are different again in the way they handle MIDI PC, but you don’t have those plugins as an option in Mainstage 3/Logic Pro under normal circumstances.
There is no way to decativate this in MG3 and, anyway, I’m not sure it’s a bad thing in all cases. I suspect there is a way to block PCs getting through to MG3 within Mainstage 3.
This is based on me testing in Ableton Live 12 (using the MG3 Audio Unit). I can’t use Mainstage at the moment – another story – but I am quite sure that it is the reason for your problems.