Very useful answer, thanks.
That explains why I observe no sound in a chain with no MIDI when MG3HEX enabled. 1&2 are not used. So if you want to mix your guitar sound from GP10 (processed) you need to use the GP audio output into a separate audio card even if this occasionally can produce ground loops (an USB Ground loop isolation might help here). Right?
@kimyo is it your idea to emulate different possibilities of antares-engine in mg3 and to edit the guitar tone itself with e.g. microtone manipulations in real time?
I donāt know if such an engine would be a new rabbit hole for @JamO, but it would open up very far-reaching possibilities for original tone manipulation.
In Live 12, just send GP-10 Ch. 1/2 to another audio strip. Done
My bad my badā¦
I was referring to the standalone mode but sure knowing meā¦ this last information is very useful as well !
Yeah. Rabbit holes is what I do! I got you all covered with tuningā¦
With MG3Hex itās trivial and with MG3 vanilla its good enough for some purposes at least
But itās for another product/add-on (codenamed Deep Amp). I have more to say on this later.
In Live: if youāre USB 1/2 is sending a D.I.-type signal you can route it also to āTrack Inā.
In MG3 standalone: selecting GP-10 as the audio device (along with the hex pickup option in the audio settings) USB Ch. 1/2 will become the D.I. source when in non-hex tracker mode.
EDIT: Be aware of the setting for CONFIG under HEX TRACKER.
When using the technology of an elastic audio engine, there might also be additional possibilities within MG3 that could go beyond the manipulation of the audio guitar tone like in DEEP AMP, e.g. to a further parameter extraction of string play in MG3 in general. More later
Many thanks @Vaultnaemsae for the time spent helping me solve my problem!
I hadnāt thought of using a plugin like the āBlue-Cat connectorā.
With the latest version 5 of Gig performer, an equivalent plugin, but easier to use, was introduced: āGP Relayerā.
So, everything works wonderfully, no more drop-out with the two threads generated by MG3!
Small neophyte question for @JamO: would it make sense to have one thread per chain in GP3, so 3 threads in this case?
Nevertheless, with these 2 threads, I already have excellent results.
Here is a small example made very quickly (too quickly for the guitar performance), but itās just to have an idea of the sound result:
Wow, if you can get MG3 Hex to do auto string tune like my ATG-1. l then I could get rid of that behemoth. I would miss the great acoustic models it has, but Iāve become addicted to playing a guitar that is always perfectly in tune all the way up the neck. If I change string gauges I donāt really have to worry about adjusting the bridge intonation, the ATG-1 will keeps me in tune.
PLEASE make this a reality!
I would echo this. Some matrix to alternate tune the strings would be wonderful.
You can do it with string filter and then a transpose but as we only have 3 chains itās currently limited.
Looking further afield per string modulation and other alterations beyond transposition are positively mind blowing.
I do not know if 6 chains are possible ā some GUI rewrite and organisation would be needed as a minimum? But this would open up huge possibilities.
I am aware that many people here in the forum want to run MG3Hex in standalone mode and want as many routing options as possible.
But if I send the Hex PU signals to a DAW via e.g. SY-1000 or GM-800, I already have countless options. The raw signals of each individual string can be sent to different instances of MG3 VST. With macros (send on/off) you can enable or disable strings or entire MIDI instrument tracks (mute/unmute). You can host other VSTs in MG3 or use the MIDI output to feed instrument tracks. The possibilities are already āendlessā. For the MIDI tracks you can alter the pitch etc. also via CC controlled footswitch.
On top of it you can run MG3Hex parallel in standalone mode and either use the network tracker or the Hex tracker output as input in the DAW.
Itās pure fun to experiment with MG3 and MG3Hex!
You are correct, for the past few weeks thatās how I used MG3 to do split string.
The new 3.0.53 update with midi channel per string make setting up so much easier and also reduces strain on computer running less instances of MG3.
Also running ample VSTi inside MG3 gives max. reduced latency which does seem a little more responsive.
The convenience of having it under one MG3 hood would be really useful and time saving.
I fully agree to that!
@jamo iām having trouble registering mg3hex on a second system.
i input my email address and then mg3 asks for the code. it doesnāt like the code which worked on the first system and the site isnāt emailing me another. this happens with both standalone and vst.
It will send you a new code for the new machine. You cant use the previous code from the old machine.
iāve tried a few more times. also allowed mg3 to have internet access via the firewall.
thereās nothing in my spam folder. i suspect the request for the code is not getting through to your server.
iām very sorry, it was the wrong email address. all is good.
Instructions unclear. I have to pay USD 150 to use the beta test guitar hex? Iām actually be interested in the cello tracker. I have a 4-string bass with piezo pickups on each bridge.
you can use the hex beta without purchasing, but it pops up a reminder which pauses output until you click on it.
you might be interested in the piccolo bass technique described elsewhere on the forum. it reduces latency by using lighter gauge strings tuned up an octave.