MIDI Guitar 3.0.60 beta update is out! (now also on Windows)

BETA TESTING
43

Windows version 3.0.61, finally out too… but once again, it may be rushed and I haven’t yet had time to validate it.

4 Likes
44

Just FYI, MG3 3.0.61(Windows), when using the MIDI Guitar MINI preset, default MIDI Output state is “No MIDI output” but MIDI transmits anyway. I’m using loopMIDI and there is activity showing on the loopMIDI port even though it isn’t selected as the output destination.

I think MIDI out “on” should be the default state for this preset, so it could just be considered that the port is not displaying correctly.

{4E0381AB-93C1-4C34-BC8D-6BD1B8878A20}
{4E0381AB-93C1-4C34-BC8D-6BD1B8878A20}1255×1307 149 KB

1 Like
45

The same is true for MG3Hex 3.0.61. Once switched between “No MIDI Output” and “Any Available Output”, no MIDI data is sent when “No MIDI Output” is then selected again. It’s just that the GUI shows the wrong “label” for its actual status when initializing after adding it to a chain.

1 Like
46

It may be of interest that MG3 wont register a loopMIDI port as an output port if the name doesn’t begin with “loopMIDI.”

I tried to create a loopMIDI port named “MG3” but MG3 would not have it! However, it accepts “loopMIDI MG3” – no problem.

47

I’ve noticed that the “footswitch” button on the midi output module sends midi whether it’s on or off.

48

@Greq True, I can confirm that.

49

That works here:

image
image1562×789 167 KB

50

Right, it is working. Not sure where I went wrong.

But try to change that name to “MIDI Guitar 3” in loopMIDI config and watch what happens.

51

Using Mac Beta .61, and can’t see the Deep Expressor and Sweetspot modules when building a new patch. Where can I find them?

52

Audio effects > Jam Origin > …

image
image1661×1018 213 KB

Make sure you have: “Showing all modules and plugins” selected

53

That is funny! Very strange that this doesn’t show up in the list!

1 Like
54

On a clean install of the .61 beta on M4 Mac on Sequoia. Also VST3 version of plugins don’t show up–just AUs. The only way I can use these audio effects (deep expressor and sweetspot) is from an existing patch that already contains them.

55

Is there a case for choosing a VST3 over an AU plugin on Mac, or plugins that doesnt have an AU?

56

No big deal, I just thought the VST3s showed up before.

What happened to the Deep Expressor and Sweetspot in the audio effects list?

57

Dont they show up in the list? Please see the screenshot 5 posts above.

58

I reinstalled, did the initial plugin scan that shows up on first launch and they now show up in the list. All is well now. Thank you,

59

CC curves is a great addition but not as flexible as I imagined it.

Here is what I currently use a FREE plugin called midiCurve:
midiCurve1
Note that unlike the one in MG3 in this instance the output never goes to max (127) but rather follows the curve as I drew it. (PS OK, now I see there is a way to limit the max, GREAT)
I can also change the CC output number and some other options.

I can also draw crazy curves like this if I wish:
midiCurve2

Bottom line is that I have full control.

Not complaining but it is a wish.

2 Likes
60

some other control curve examples posted here previously:

image

61

The only cases I can think of where having VST2/3 may be useful over Audio Units (AU):

  1. when the AU version of a plugin has problems not present in the VST2/3 version (though I haven’t experienced this kind of problem for a good while);
  2. when transfering an MG3 preset built with a specific plugin format between macOS and Windows (or vice versa) – though I haven’t tested this yet (but it’s on my to-do list).
1 Like
62

Yes, ok. Let’s add more general envelopes.
You can already pass the CC envelope through the Modulations module and create (another kind of) very complex envelopes.

1 Like