Hi gang. I’ve been running some experiments in iOS with Audiobus (which is another story in itself, and I think I’m about to switch to AUM because of it) and one thing I have noticed is that MG3 doesn’t seem to save the unique “state” of either the duophonic bass tracker or the duophonic cello tracker.
For example, I can use an instance of MG3 with the bass tracker, make it monophonic, and adjust the gain and gate as necessary, and until I reload the MG3 plugin (either with an MG3 internal patch change or with an Audiobus “load preset” action), those values seem to work just as I’d think they would. But, as soon as that MG3 instance loads its next preset/patch, that bass tracker always seems to revert to the state I started it with: duophonic, 0dB input gain, value 14 on the gate. Ditto with the cello tracker, whose “noise floor” value always reverts to its 50%-ish default value.
Actually, I’m beginning to suspect that the trackers may actually share the input gain and gate values, in some way. In trying to run an atomic, simple test to make sure what I’m writing here is accurate to what I’m seeing (I tend to run into these oddities when doing something much more complex, which isn’t the best way to troubleshoot), I confirmed that the bass and cello trackers kept returning to the same values I changed them from–but… when I started dinking with the polyphonic guitar tracker settings too (I’m not set up for Hex yet), suddenly I saw that the input gain and gate values I’d set in the guitar tracker (which do seem to persist for that tracker), would then follow the bass and cello trackers too…at least kinda. The cello’s “noise floor” would always return to 50% and the bass tracker would always return to duophonic, but those input gain and gate values look…somehow linked to me.
I haven’t figured it all out yet, there seems to be more to it than just that, but I figured this is the right point to ask the question: what’s happening here, and what is intended?