Just wanting a clarification here, so that I understand correctly.
In testing out the Audio Device plugin a bit further, I noticed something that I wasn’t expecting, leading to this question: is the Audio Device plugin intended to serve all three Chains, or just the one the plugin is located in? (I wound up putting the plugin in Chain 2, but could still hear its audio coming from Chain 1 when I muted Chains 2 and 3. When I muted the plugin, I got the dry guitar audio from my main MG3 audio device in all three Chains.
And here is a critical related question; I think I already know the answer to this, but again am looking for clarity. IIRC, the way MG3 works is that “in the beginning” the Tracker takes the input from the primary audio device (as specified in Settings), does its tracking magic on that signal, and then sends both the resultant package of MIDI data, and the thru audio from the primary audio device, to all three Chains. Each Chain then can replace the thru guitar audio with the audio output of an Instrument that uses the MIDI package data to produce sounds; otherwise, the thru guitar audio remains and is sent to the Master bus from that Chain.
Do I have that right?
And if so, is it fair to say that the new Audio Device plugin essentially serves as a replacement of that thru audio, coming from another source, at the point of sending the MIDI package and a “guitar” audio signal to all three Chains? The result being a perfectly clean signal for MG3 to track against, but possibly a dirty and/or wet alternate signal to serve as a starting point for audio effects in the Chain?
I have to confess, I hope I’ve got that right, because if that’s the case, that’s truly awesome. It still seems a little bit weird because you have to house the plugin in a slot in one of the Chains, but it affects all three Chains as if it belonged properly to the Tracker and not just the Chain it’s housed in.
Anyway, please correct/educate me if I’ve got any of this wrong.
My observations on signal path behaviour (both expected and unexpected) in MG3:
Using the MG3 Hex tracker with 3 empty chains (it needs 6 inputs to function);
Using the regular MG3 tracker (it needs min. 1/max. 2 input(s) to work, and if you formerly had multiple audio channels selected under the hex tracker you must reconfigure input channles in audio settings for the regular tracker).
Hex Only: The default direct audio heard on any chain is the hex combo (6 channels = aggregated hex signal);
Regular Only: The default direct audio heard on any chain is the selected input device…any mono signal or stereo signal. i.e. if you select 1+2 both signals reach the tracker.
Regular Only: If the pitch received is not in the tracker’s range, the original signal is heard but no MIDI can be generated;
– When you mute channels with no Audio Device modules in place the channels mute correctly;
– When added, the Audio Device module receives audio from either ch. 1 or 2 (but not both) of the audio device selected in the module;
– If an Audio Device module is instantiated, the selected audio device in that module will be heard at the master chain even if the channels are muted (*I think this is a bug). The module’s output signal does not, however, feed all chains;
– MG3 cannot find the inputs when you select “main audio device” in the module (*I think this is a bug);
– If you select “No Input” under the main audio settings for the input device, you can still add an Audio Device module to a chain for an audio source, but it will only feed another audio device, as it cannot be used to generate MIDI;
– If an Audio Device module is instantiated, the selected audio device in that module will be heard at the master chain even if the channels are muted (*I think this is a bug). The module’s output signal does not, however, feed all chains;
– MG3 cannot find the inputs when you select “main audio device” in the module (*I think this is a bug).
Simply put, it’s not quite cooked yet. To my way of thinking, regardless of the tracker, the Audio Device module should simply be a device for routing another signal into the grid.
The primary use case would be if you wanted to have your hex config plus add another guitar D.I. to the mix. Mainly because the aggregate hex signal can sound a bit sh*tty (to my ears) for feeding an amp sim.
– It should only feed the chain with the module;
– It should not be heard at the master chain if the original chain is muted;
– It should also allow stereo input if you want to route in another processor or full main stereo signal path from your BOSS hex compatible device (or something else);
– It should allow selection of any adjacent pair of channels in your setup i.e. 1/2, 3/4, 5/6, etc.
Documentation is in progress but the software is too so the written content is not at a point where it’s ready to go live yet.
