MG3 support for 7-string guitars and lower tunings

Hello,

I have been enjoying MG3 greatly, it functions so much nicer than the GR-55 and Graphtech Floyd Rose system I put together some time ago. The tracking and capabilities had me hooked as soon as I started tweaking things, so I went ahead and purchased the lifetime license due to this.

But there is one main issue, which is a big deal to me; Not being able to use my lower registers with it. I tune down 1 whole step, and use 7 and 6 string guitars. This means that my entire lower register on the 7 string is unavailable and I’m missing the low open and first fret notes (D and Eb) on the 6 string, due to this.

6 string tuning: DGCFAD
7 string tuning: ADGCFAD

Would be very nice to have this available in MG3 please.
Thanks

2 Likes

MG3 is still in beta and does not yet support notes lower than E2. MG2 can be configured for Drop D tuning for a 6 string. I think, but don’t know for sure, that your license should also work for MG2, so I suggest giving it a try. As far as support for a 7 string, someone else will need to speak to that.

1 Like

Now everything depends on if you are looking for a MIDI Guitar software that is retunable to altered tunings, or if you are looking for a software that can deal with your guitars being in altered tunings. Those are two very different things of course.

To begin with, let’s make this very important distinction between the retuning capabilities in MG3 and MGHex:

MG3 uses your incoming (single stream of audio from your guitar’s standard magnetic pickups for its MIDI conversion. It listens to, and analyses one source of audio: distilling and extracting from this everything you get in (standard) MG3 MIDI/MPE. Up to six (simultaneous) pitches polyphony with accompanying individual pitchbend, brightness, pressure and strike messages for each and every pitch registered. What is NOT extracted is information about which string these pitches are played on.

MGHEX use the six (6) audio streams from a hexaphonic/divided PU system (think of a hexaphonic pickup as having six microphones - one for each string), and can that way create unique MIDI/MPE messages for six dedicated MIDI channels. There is no specific message telling us what string is being used here either, but it is conveyed by the MIDI channel distribution. If we use the analysed AUDIO stream from the high E string going into the hexaphonic Pickup (high E microphone) to create MIDI that we send out on MIDI channel 2, and uniquely pair each string with a MIDI Channel, we get something like implicit information about “what strings we are using” sent to our instruments. But there isn’t any actual MIDI messages telling us this. We can only infer this from what channel is being used.

We know that the standard MG3 tracker send out information on multple MIDI channels 2-7 according to a principle where the first note is sent on Ch2, a second simultaneously ringing note (interval) is sent on Ch 3, and if a three note chord is played , channels 2,3 and 4 will be in use (and so on for any added notes) A full six string chord will use channels 2-7.
Why can’t we order them to implicitly convey this information about which string they are played on, now? Because there is no such information.

Now to the questions about retuning:

With MGHEX there is of course every possibility to retune whatever is sent out on the channels at a 1) Tracker level, 2) Chain level or 3) Instrument level because we have this strict one-to-one relation between string and channel.

I often retune my Kontakt or UVI Falcon sounds by loading six instances of an instrument and simply retune it on a per channel basis. Here is an example where I went for a very odd Joni Mitchell (Black Crow) tuning using some synth in Falcon:

So if you are not necessarily looking for the feeling you get from the strings with a particular altered tuning, many (six string) tunings are already avalible. But, of cousre, you have to set them up yourself, avaiting their inclusion in the MGHEX MIDI Machine tool box.

But seven string tunings then? Well, If we have a divided 7 string PU it wouldn’t be much of a problem in theory, I guess. Even though we know that tracking is notoriosly harder with the lower frequncy pitches, we are still talking about a monophonic tracker. So if it works for bass it should work for a seventh string as well. But it calls for a revamp of the existing MGHEX tracker to incorporate also these fringe examples, and I can’t see how that comes very high on the priority list right now.

It is way more likely that a seven stringed guitar is going to get access to MIDI/MPE via the standard MG3 tracker with support for extended range, and then you can tune your guitar to whatever you feel like (within reason).

Personally I like the idea of retuning the software though. I would want to play the same instrument but be able to call up the occasional alternate tuning to easier play some Holdsworth, Gambale or Joni stuff, and then go back to being my old boring self again in standard.

3 Likes

Hey LoFiLeif, thanks for the info! Also I watched your YT vids on configuring MG3, it was very informative, much appreciated!

I’ll add a little more about my use case, to try to narrow down the scope:

I’m using MG3 with audio input only, from Cubase Pro or Ableton Live.
I’m not using a hex pickup, just using the audio signal.

My instruments are all tuned the same, 1 whole step down, across all strings (straight tuning, no drop). I do-not need to change my tuning on the guitars or in the software.

The 7 string guitars are tuned exactly like the 6 string, only with the additional low A string added; Typically this is a B1, such as on on 5 strings basses, but I’m tuned down 1 whole step so it’s an A1 for me.

So the notes that are not-available from my 7 string guitars to MG3 are: A1, A#1, B1, C2, C#2, D2, D#2

And the notes that are not-available from my 6 string guitars to MG3 are: D2, D#2

I can live without them of course, but since there’s a place to request features, here is this request!

Thanks again

1 Like

HI

Glad you found some of my stuff useful!

I really can’t do much to help you at this point. I just wanted to shine a light on what is possible today (retuning six strings with the MGHEX tracker output), and be clear as to why this work with MGHEX as opposed to standard MG3. Anything beyond that, like support for lower tuned instruments and so on, you will have to wait for Jamorigin to actually facilitate in the software in any coming update. I don’t have any info on when this could be, I am afraid.

Fingers crossed it is not too far off :crossed_fingers:

2 Likes

Ditto to this request. In truth it’d be nice to have a user specified number of strings (for 8-strings, 9-strings, and up).

1 Like

The 6-string limitation of guitar-to-midi is what has held me back from bothering with it for years now. I’ve played 8-string guitar since the mid-90s, when you mostly had to get them custom-made. Nowadays they’re commonplace. Basically what I heard from everyone I asked is the reason all the guitar-to-MIDI stuff is limited to six strings is because everyone uses a Roland standard and that’s what Roland decided the limit would be a few decades ago when guitar-to-MIDI was new. Makes sense to some degree if you have a specialized pickup and preamp with one per string doing the work, but if it’s all done in software, you’d think the limit could be ignored. Of course, the low frequency problem is always going to be an issue, but that applies regardless of whether you use multiple pickups and preamps or none at all.

In any case, MIDI to me is not a performance tool so much as a composition and transcription tool, so all I really care about is getting all the note information out of the guitar to the software I’m using to transcribe or compose. But I can do that manually just as I’ve always done, so until any guitar-to-MIDI “solution” lets you work with at least 8 strings, there’s no point in bothering with convoluted workarounds like installing two MIDI preamps and so on.

this is a physics problem and it doesn’t matter if it is boss or jamo or whoever writing the code. note detection below D2 just takes too much time.

the limit is not the number of strings. if your 8 strings were all tuned to D2 or above they would all be detected. the limit is on the pitch range.

the only solution i see as practical for notes below D2 is laser pitch detection.

1 Like

I also play a 7 string( no hex). It would be very awesome to make use of them all with MG3.