MIDI Guitar 3 Hex and audio chains

1) Video Tutorial Request
Except for LoFiLeiF, is there anyone at JamOrigin making MG3 / HEX usage tutorials?

  1. Current MG3HEX STANDALONE has 3 Audio CHAINS on the UI, Will it be possible to get all 8?
    Chnl 1 +2 = Guitar Pickup
    Chnl 3 - 8 = Strings 1-6
  • examples:
    MG3HEX - Cello,sax,etc. Mod “not available in this version”
    what version are these MODs available..?
    MG3HEX - Auto Bassist how exactly to set it up..?
    Auto Bassist added to the chain and now add a bass vst to the same chain..?

DAW + HARDWARE

  • Fender Studio Pro 8.2
  • MOTU Ultralite mk3
    IN (1) = DI
    IN (3) = D
    IN (4) = A
    IN (5) = B
    IN (6) = G
    IN (7) = B
    IN (8) = e

RESOURCE

Please let us know for what purpose you want 6/8 channels?

Was hoping to use MG3HEX as a standalone and each string would have its own CHAIN
I understand how this is setup in a DAW where each string has its own Channel + Effects + Pan

As far as tutorials, simple, concise “How to use Auto Bass” type tutorials.
LoFiLeiF is awesome and very d e e p, just looking for quick setup and reference vids for the basic new features and MODs,
~ Thanks

We need more info.

Are you using standalone or a DAW?

How do you connect your HEX to the audio interface? Direct cable or USB from a Roland floor model?

What exactly are you trying to achieve?

You should be able to run 8 channels to your DAW already no?

I make videos on MG3 Standard/Hex, but I’ve been too busy with developing my own plug-ins/applications lately to have any time to make videos for my own products let alone MG3. And hardly anybody watches them anyway! :sweat_smile:

I’d refer to the three available plug-in loading spaces as “three chains” (rather than channels). Each supports audio and MIDI.

I’m not sure what you mean by “will it be possible to get all 8?” As you already pointed out, 3-8 are necessary to feed MG3’s hex engine. You configure these audio inputs in MG3’s audio settings. DAW setup rests on each DAW’s available systems.

Channels 1/2 are available for either D.I. guitar if you configure your device for that or to send a stereo mix from your BOSS device. Please note, it’s actually only mono at the moment, but @JamO indicated to me that this could be rectified in a future version. Or (on macOS) you can use my Audio Inception plugin to work around that current limitation.

1 Like

Some modules process 6 channels. You can see a H symbol at the module if it output hex audio to the next module. At some point it’s all mixed down to stereo.
Please let us know for what purpose you want 6/8 channels?

1 Like

It would be good to have Hex expanded to 7 and 8 channels to support 7 and 8 string guitars.

2 Likes

If you really want to get maximum string separation per chain, on macOS, you can duplicate MG3 standalone and run two instances in parallel.

Do you know whether there is any “Octaphonic” pickup from the shelf? I know there are some for 7 strings but I never saw one for 8 strings.

That isn’t the concept of MG3 Hex. Individual strings and chains have no fixed or selectable relation. There is a “workaround” using string filters as a first module in a chain. If you want a bass VST only on the low E and maybe the A string, use one chain for that. Insert the “String Filter” module first, allow the E and A string passing through, below the filter insert a Bass VST.

I only know of 7 string options, but not to say 8 string options are around the corner as those instruments become more popular. I have a 7 string and have thought it would be nice to have individual string control with MG3. But really happy with my 6 string guitars and 4 and 5 string basses for now. Will be putting together a 6 b standard baritone hex right after the new year for some different tunings.

1 Like

I guess 6 (or 8) Chains would solve this, each running a different string. It’s a reasonable request, and I’ll keep it in mind. There is some work on a new UI underway, and it would be easy to fit it in, but it’s not a promise.

2 Likes

It’s a ‘reasonable request’ you say…?
Good to know…! also, promises are dumb.

At least one more chain would be useful as I often would like to add one more instrument (chain one is natural hex guitar, 2 soft inst, 3 soft inst, 4 would be nice). But I can see how some folks might like a chain for each string and a seventh for the traditional pickups. More important than another chain for me, is a Bus! I have many plugins that won’t process in the hex chain, but they work if I put them in the master. Unfortunately I may not want that plugin effecting the sum of all chains. So, if we had Bus that we could send to before the master, then I could send my hex guitar summed signal to that bus and make use of all my non-hex supporting plugins for guitar. Then the bus could route to the master.

i haven’t tested, but i’m pretty sure many of my plug-ins which do not work on chains 1/2/3 in the latest version used to work on the previous one.

my experience matches yours, these plugins do work on the master, but that is limiting.

rather than adding a bus, i would prefer restoring the functionality to the previous state.

in terms of hex processing there are things i would like to accomplish which are not feasible with the current string routing options. these include hex fuzz, and @prehm 's nifty synth trick.

these can be made to work in a daw, but i would like someday to be able to use them in an mg3hex standalone setup.

adding an option to ‘flow’ chain 1 into the top of chain 2 would be an way to achieve this.

1 Like

I don’t think mine functioned in hex before. Only in regular MG3. But, if something there is a coding fix to make them function in the chain, then that would be ideal.

Flowing one chain to another is an interesting idea, but I think a bus would be more useful. You could send varying amounts of signal from any chain to a bus with what every you want in it.

1 Like

Can you give a concrete example of this, just so im sure I understand?

1 Like

Here’s a screen shot to help clarify.

Chain 1 has just the hex guitar signal. Chain 2 has a Korg Module software instrument. Chain 3 has Blue Mango software instrument. I want to use my JAMP acoustic model plugin and an acoustic amp plugin, and sometimes the THU amp plugin, on the natural guitar hex signal in Chain 1, but they don’t work in Chain 1. They do work in the master section. Unfortunately, placing them in the master means the plugins will also affect the software instruments, this may be undesirable. If there was a bus next to the master, I could assign the output of Chain 1 to the bus and place the plugins there (assuming the bus is a sum of the hex signal). Then send the bus output to the master, leaving the instruments in Chain 2 and 3 unaffected.

1 Like

The bus idea makes sense, but the crucial part is that it must be a stereo bus fed by a summed version of chain 1—not a 6-channel hex bus. If those non-hex plugins are failing because they only accept mono/stereo, putting them on a bus that still carries per-string channels probably won’t fix it. A post-sum send from chain 1 to a stereo bus, then bus to master, would preserve chains 2/3 while letting JAMP/THU run. Chain-flow alone may still hit the same plugin-format issue.

Hi Laura,

Have you personally tested MIDI Guitar 3 Hex to reach these conclusions?

Also, have you personally tested JAMP or TH-U in a hex chain and confirmed that their failure is specifically related to the channel configuration?