I am absolutely struggling trying to get MG3 anywhere close to the tracking of even the el cheapo 60 dollar amazon Mooer E7 synth pedal. If I set the gate high enough to get rid of stray notes, the highs don’t play at all. I really don’t get it. What am I missing here?
Do those tracker things in setup actually change anything? Would I have better luck with MIDI Guitar 2?
For guitars with conventional magnetic or piezo pickups, only one tracker can be used: “Midi Guitar 3” (the first one in the settings menu). With proper playing technique, it’s not necessary to turn the gate control all the way up. You’ll find several posts on this topic in this forum.
MG3 is a better choice than MG2 for getting started with pitch-to-MIDI conversion.
Needless to mention that the guitar setup must be as good as possible (intonation, string spacing, PU position, neck shape).
Playing technique shouldn’t need to be so much more accurate than with a cheapo 60 dollar pedal. Digging around the forum, I saw a bit about needing a bright signal, so I tried a highpass filter before the plugin and that seems to be helping quite a bit! I’ll keep messing with it. I’d like to map the mono vs poly mode to a widget in Gig Performer, do you know which of the unnamed parameters that might be?
The “unnamed parameters” are tied to the controller slots in MG3’s MIDI Patchbay. You can tie the tracking type selector (MG3 Expressive, Monophonic, MG2 no bends) to one of these controller slots/parameters.
please provide a description of your equipment and signal path.
generally there should be no need for any pre-processing effects.
extra/unwanted notes can result from a number of inputs: string height too low, untrimmed string ends/undampened strings beyond the nut, grounding issues/pickup hum, incorrect intonation.
mg3 is the ferrari. to drive it does require much more attention to detail than to use the volkswagon. it will reward you in the same way.
a clue that something is not optimal is the need to turn the gate up. that should almost never be required.
These are a variety of guitars with either EMG 707s pickups or Duncan Blackouts, into a Focusrite 4i4 with the input calibrated the same way as on my all hardware based pedalboard to reach a nominal -18dBFS on my DAW’s meter, using a buzzer to excite the pickups in a repeatable manner
In this case, gig performer is the software hosting MG2 and MG3 now feeding Korg Wavestate Native. Very very low level signals (-52ish dBFS) often trigger notes I didn’t want to hit, while much higher signals (even sometimes up to -22dBFS) do not trigger wanted notes. None of this happens with the el cheapo synth pedal from amazon, even when I use it as an insert effect with the 4i4’s output 3 going to the synth pedal’s input, and the synth pedal output returning on the 4i4 channel 4 in. That’s three converter hits and all the associated issues, and that still tracks fine, meanwhile this extremely clean signal struggles with an inconsistent threshold to trigger.
I get that, but I am happy with the Geo Metro’s performance, and which I could get that from a piece of software costing twice as much
The fourth to last note here is triggering a sound from the high e string, even though the note you hear in the raw audio is the correct one from the b string. I suspect its because there is the tiniest touch from my pinky there (-58dBFS) compared to the actual note at -18.9dBFS
Where can I learn more about this strike filter? This may be exactly what I need. One thing about the mooer pedal is that no matter what it has a slightly slow attack, like a minimum of around 19 milliseconds (not talking about latency, but the ramp to full volume) and maybe that is a factor in making it seem like it triggers fewer wrong notes. Is that what the strike filter does?
I’m creating an entirely computer based live pedalboard. There are lots of things MG3 can do that this Mooer pedal can’t like switching presets thru snapshots/variations
Ok, not sure how its different than the gate but in MG3 tools/strike filter is helping. The strike filter in essentials/midi output has absolutely no discernable effect on the action, but the standalone strike filter placed before it sure does! I saw something in the forum in an early build of MG1 or 2 about a minimum time between notes filter or similar, but don’t think I see one in MG3. Also, is there any sort of ADSR control that can be applied to the MIDI output?
I gave the measurements that exist in the wave file, and the false trigger is more than 30dB quieter than the actual wanted note, with the perceptual coding of an mp3, that difference could drop to 6dB or even lower.
I tried to read up and watch some videos on MPE. My synth plugin (Korg Wavestate native) doesn’t seem to respond when I use MPE mode. Is it something I really want to use for what I’m doing? I just do some small synth lines in a Dio tribute band since we don’t have a keyboard player yet