We have implemented aftertouch (you have to enable it, it is left of screen, under bends), but most synths ignore this completely or are tremendously vague about it.
The easiest way to get this going, especially when playing monophonically, is to convert this aftertouch into a CC value. Most synths have mechanisms to bind CC’s to knobs in the interface, and a few cc’s have standard meanings. CC7 is always volume, CC1 is always mod. CC2 is mostly filter cutoff. CC64 is hold (all notes reverberate)
These are the most common CC’s, whether or not your synth supports them, is completely at the will of the synth’s designer.
For MG, CC1(mod), CC2 (breath control/cutoff) and CC7 (volume) are the most valueable.
Aftertouch2CC.lua (2.0 KB) This midimachine will work only if aftertouch is enabled! CC - chooses the CC to generate Method - average takes the average of the sounding notes, peak takes the loudest strings. Subtle difference, mostly not very noticeable.
I’m looking for a midi machine that will change incoming CC# to different CC#. I have a controller that sends on CC85 and I want it transformed to CC7 to control modulation in a SampleTank VST instrument. I thought AftertouchCC might work, and placed it in the MidiMachine folder, but it does not show up in the list. I’m on Win 11 using MG3HEX beta. How can I make it show up?
Great idea! My set up is a bit different, but it works. I’m actually send cc 86 from my controller to cc1 in the Sample Tank. The SampleTank instrument is a piano/strings where the mod wheel controls the string volume. Unfortunately it is in reverse, so when the fader is down it turns the string volume up. Do you know of a way to invert the cc values so it goes the other direction? I can’t see any setting in SampleTank, so I’m thinking another midi machine? I previously had Strings on a separate instrument in the middle chain, but that was a high load on the CPU. By using the single Piano/String instrument it has lessened the CPU load.
Have you tried the MODULATOR Invert function? You can put a MODULATOR after your MIDI device, and connect the output from the MIDI device to the handles of the MODULATOR.
Now my next issue is with the 3 fader controller. Every time I change patches, the MidiGuitar 3 faders all default back Zero, even though I have not moved the hardware faders. Is there a way to get them to remain in place when switching patches.
If I just connect my pedal from the patchbay directly to the invert handle, and save that to a patch, it works fine to recall.
But if I connect via the MIDI device, the position of the pedal is ignored on recall. MG3 doesn’t recognize the position of my pedal or your faders.
Not sure if @JamO knows about this already (so now he does), but in the mean time I would suggest you use the CCs in the patchbay to map diectly to the MODULATORS invert handles.
Well that is what Beta Testing is for, we find these things
I’ll have to think about it and reroute things. The reason I wasn’t going from the main patchbay is because GP-10 is assigned there and it doesn’t send all those midi cc. I’ll keep plodding along and I should be able to try the rig on gig pretty soon. Thanks for all you do!
Doesn’t seem to be a good work around for “Return to Zero” issue.
I have 3 controllers.
*Sparrow 3 fader assigned to Volume of each chain.
*USB midi converter from my ATG-1 assigned to Patch Changes.
*GP-10 which sends CC11 from the expression pedal assigned to Master MG3 volume.
The master midi bay can be set to “Any Controller” and will recognize everything except the GP-10. So the Sparrow faders will hold value on patch change if attached that way. But then I have to use the GP-10 as “Midi Device” in a chain and so it defaults back to Zero on patch change.
Hopefully this behavior can be changed in the next update?
I belive the GP10 CC/PC messages are deliberately excluded from the patchbay input at this point so that any changing GP10 presets wouldn’t affect the patches in MG3. I am not sure, but that might be a temporary solution too.
Or, did you actually use the GP10 CC11 via the patchbay at any time before?
The defaulting back to zero behaviour with the MIDI device is obviously something to be adressed though.
Yes, I used GP-10 in the patchbay before, it sends cc 11 and patch up down. Interestingly now that I’m running the faders through the main patchbay, I discovered the built in “Invert” button, so I no longer need the modulation midi machine to do the inversion. Little cleaner set up this way
I’m getting close to gig ready. Still in the process of testing for the best sounds with the best tracking. Once I’m satisfied with my patches (sound, tracking and control), I can assemble all the hardware components (MiniPC, 8 inch display, ATG-1, GP-10, TC-Helicon Harmonizer) into one portable (but heavy) pedalboard. I have a bit of work to do, but I expect to have it done in a week. I may actually replace the GP-10 in favor of a one rack space interface. I have ordered a cable from BREAKOUT CABLES
that breaks the 13-pin into 6 lines. I’m thinking PreSonus 1824c or Focusrite18i20. Focusrite had better reviews, but PreSonus is significantly smaller (important for live use). If I go with the rack unit it would look similar to my current setup with my AXON 100mk2.
