I am using hex midi guitar with bluecat patchwork on protools on a windows 11 computer. Different settings like dynamics, input gain, gate etc.. are all not storing per plugin instance. I’m not sure what else is stored globally and not per instance. Like if I have 2 plugin instances of midi guitar 3 and change the dynamics knob or input gain or gate knob to a value then go to other instance (may need inactivate and reactivate of instance) and then the values change on the instance I didn’t want to change. Even if I am on a different midi guitar patch name etc..
Is this bug planning to be fixed? So when I inactivate one blue cat and activate the other the settings transfer over (it seems to store the settings at inactivate or something). The exact key strokes for me is open two MG hex instances, tweak the gate knob, inactivate that blue cat instance, inactivate the other instance of blue cat then reactivate both and you will see the 2nd instance that was never touched gets its gate updated.
This is also similar to the issue where the “Ask for 1” vs “ask for 8” inputs is stored globally not per plugin instance. And somewhat similar to the duophonic defaulting back on the bass tracker issue which @JamO said is fixed in an upcoming update. Hopefully all these issues get fixed in that update
Seems to be something to do with this file– it updates the second I inactivate a plugin instance (that appears to be the trigger to update the file with the new gate etc… parameters). Then next time I open an instance of mg3 hex (only hex has this issue I think…), it grabs those parameters from this file.
Seems to be only a hex tracker issue but not 100% sure. It appears updating say the gate on the midi bass tracker does update the gate value on the midiguitar3 text file but when opening up new midi bass patches it doesn’t take these values. The issue appears to be that hex tracker always grabs these values instead of maintaining it’s own values per plugin
Yes. This is a bit confusing. The tracker settings are global. That’s was a decision made in order for people to easily change guitar, interface, input gain without re-saving all the patches.
We have been discussing to generalize this with some kind of tracker/guitar presets. I think that should work for you as well.
With the presets option that would probably resolve it yeah— would maybe still prefer the ability to tweak the settings per plugin instance instead of relying on stored presets. I guess I could have a different preset for each possible gate number but that doesn’t seem practical. The gate for me is set depending on what type of music I’m playing (lead, chords etc…). The issue is I may record an audio clip in protools and really like how it sounds as I perform it then when I want to play it back the next day it won’t sound the same because the gate is set differently. Even only a few notches on the gate setting can change how the guitar gets picked up and I would need for the plugin to always perform the same as it did when I recorded it. I think a key requirement for plugins is that they don’t ever automatically change settings on you so you can always listen back to how something sounds consistently.
Maybe a config option for “global tracker values” vs “per plugin instance tracker values”
Gate also depends on just my exact guitar settings and volume and what I’m playing and how loud I play the guitar and the VST patch’s reactiveness to quiet notes etc…. For me I tweak gate almost every time I load a vst to dial in the settings. So I would prefer this to be per plugin instance not a preset option. Like for example say I dial in the gain staging for a guitar chain where I blend guitar and midi guitar signal then I want to add midi guitar, I wouldn’t want to adjust the guitar volume to react well on midi guitar because my gain staging is already dialed in— I would just want to adjust the gate.
I suppose one work around is to never use the midi guitar gate and put a separate gate plugin before midi guitar. If I use my own gate plugin for hex I assume it would need to be one gate per string to match the functionality of the native gate
Another gap that I probably can’t do a work around (Like the gate and gain) is I like tweaking the dynamics knob per patch as well— different VSTs react differently and I would want that stored per plugin instance.
Can I use the dynamics midi machine instead of the dynamics knob on hex tracker? Or is that different? Do you think that we will eventually be able to store these settings per plugin? If so when do you think this would be doable by?
Just an FYI— my top issues right now for MG3 are:
This issue of hex tracker settings being global
VSTs hosted inside not storing coordinates of where plugins are stored — after exiting daw and getting back in they revert to default location
Bass duophonic issue where it reverts to duophonic
Bug that was mentioned in another ticket where clicking save in protools exits out of the window do the VST instrument running in midi guitar (happens on metaplugin and bluecat patchwork in protools)
