I am running MG3 within protools inside of metaplugin. It works well but one gap is that say I run one instance where I set the audio devices section to “Ask DAW to give it 1 input channel” then I have another instance that I want to be hex and “Ask DAW for 8 input channels” when I reopen the session or disable plugins and reenable the plugins revert to whatever I last set one of my many instances of MG3 to be either 8 or 1 channels. The tracker still stays on hex or bass or guitar or w/e but the inputs revert to 1 or 8.
Any ideas? Or is this a known bug. I would be glad to provide a video or screenshots if that helps.
I need both the 1 input and the 8 channel because I use the 1 input for midi bass. Maybe I can use HEX guitar instead on the bottom string for bass but that is not ideal. Or maybe I can use the VST version for one and VST3 version for the other but I think they share this parameter for 8 vs 1 input. Any tricks on this?
Also one more issue is there seems to be some kind of issue where if I leave mg3 window open my protools slows down super slow where each click just in normal protools like record arming a track is super delayed. When I exit mg3 window everything speeds up again (plugin still running in background).
i have run into similar issues in ableton when running two instances, one inside and one standalone.
if metaplugin works like bluecat patchwork then a possible solution would be to have two separate metaplugin presets, one for hex, the other for midibass.
alternately, can you plug your bass into input #7?
I tried input 7 and it didn’t seem to pick it up. Should the 7th input of the 8 theoretically be the input for a mono midi guitar or midi bass tracker with hex input?
I am on windows 11. I can try saving a preset in meta plugin and see if the helps it not revert— but I would modify it and all modifications like plugins etc store correct when I save protools sessions… the only thing that reverts is the ask for 1 vs 8 inputs setting. I’ll try that tomorrow and report back. I am using a universal audio Apollo 8.
using channel 7 is a workaround, midibass would normally use input1. and it looks like the apollo only has 4 preamps, which is probably why you weren’t getting audio.
what type of instruments are you controlling from the bass?
I am using external preamps etc… so I am getting audio on that input—-so if I route my input to input 7 on an instance of midi bass that is asking for 8 inputs it should grab the audio? Or it needs to be input 1 on a one input midi bass instance?
I am controlling mostly uvi falcon and Arturia plugins. Using non mpe
i sent you down a dead end path, i think. i can’t think of how to separate out track 7 for midi bass.
if it was track 3, for instance, you could use string mute and send only audio from 3 back out to protools for use with midibass. or even load midibass as a vst within mg3hex.
i’ll experiment and see if i can get it to work.
i have not experienced the lag you describe. does it also occur when mg3 standard is loaded on a protools track without metaplugin?
are you mixing your bass sound in with the synths? uvi/arturia presets would probably be more responsive (lower latency) when triggered by guitar.
once you get this solved take a look at @prehm ‘s bass trick, it is the lowest latency option and is a lot of fun to play:
Am I right that you use a breakout cable into your Apollo interface? In this case you can select “Channel 1-6” in MG3Hex instead of “Channel 1-8 (Hex Pickups)”. This leaves you with 2 possible channels for single PU instruments.
I have used MG3 as standalone into Pro Tools with no issues for over 2 years. Maybe I’m just old, but not sure why you wouldn’t just use MG3 standalone and treat it like any other hardware controller.
I need multiple instances because I sometimes have more than one instance in one recording chain. Like sometimes I have midi guitar hex along with an instance of midi gutiar on my vocal chain converting vocals to midi. Also, I am building a big protools template that I can just go to a memory location and pull up different complex chains so having to revert all the settings on midi guitar (gate etc..) each time is too much work.
Also, doesn’t standalone passing midi to protools have more latency? Low latency is important for me
I use a subsix pickup into a neve 1073opx connected via adat to the apollo 8. I am not sure what you mean, the only options that midi guitar 3 offers is “ask daw for 8 inputs” or “ask daw for 1 input”
@kimyo does MG3hex standalone using midi caster mode have more latency? What do you mean run midibass on its own track? The settings would still revert to look for 8 vs 1 inputs- right? The issue persists globally if you have a plugin looking for a single input vs the 8 they always revert to the most recent 8 vs 1
“i have not experienced the lag you describe. does it also occur when mg3 standard is loaded on a protools track without metaplugin?” — regarding this, I cannot run midi guitar 3 not inside of metaplugin on a protools track (AAX not offered).
“are you mixing your bass sound in with the synths? uvi/arturia presets would probably be more responsive (lower latency) when triggered by guitar.”——-regarding this, yes I am blending DI bass and midi bass sound together–it sounds great.
