The latest newsletter: LINK
2 Likes
MIDI Guitar 3 hasn’t been released to the public yet–still in private beta.
1 Like
Not so private though. Link for Mac at:
https://www.jamorigin.com/beta/
and for Windowsversion, copy the zip file link i the top post
4 Likes
Welcome, @LoFiLeif ! I’ve been following you on the Jam Origin forum for a long time. You make useful, interesting videos and provide some excellent suggestions/help.
If you are not familiar with Gig Performer, I highly recommend that you spend a little time with GP. I’ve used several other plugin hosts in the past, but have been on GP since v2. It was better than the alternatives back then. Now, it’s just mind-blowing.
See you back at JO.
3 Likes
Welcome to this community forum! 
1 Like
Hey guys! Thanks for making me feel welcome here as well! 
@themaartian I am not completely unfamiliar with GP, but I still have a bunch to learn of course. It is a great complement to MG3 to be able to open up two instances and shift between rackspaces and variations that way, compared to just browsing through the presets in MG3 in standalone mode. I did a little video on this a couple of days ago. https://youtu.be/mIjo7gI7UZw
7 Likes
Great video!
I created a separate thread here: [video] Blurring the line between Acoustic and MIDI with Gig Performer and MIDI Guitar 3
4 Likes
You may find this absurd, but I would like to use MIDI Guitar 3, but it doesn’t fit into my workflow. I have two monitors and I have always open Guitar Pro, Gig Performer and the Apollo Console. I have tried to use MIDI Guitar stand alone and as a second instance, because my main Gig Performer instance has a very high latency. Both solutions work technically, but at the end of the day I don’t want to have too many open windows. I think in an ideal world every plugin in Gig Performer should have its own latency settings, but it seems that this is not how things work…
Don’t forget that MG3 is only in Beta version and far from being finalised.
It will be some time before a stable version is available.
Don’t hesitate to post any problems you encounter on the forum jamosapien.com to help development progress.
I use Midi Guitar in 95% of my GP projects and I never have a MG window opened when I’m playing except for editing, like any other plugin or application.
Thank you for your advice. It is just that I want to keep things simple and it is very convenient, when you got only one instance of Gig Performer. So you just have everything under one hood. I need very high buffer settings. So I have a very high latency. So the only solution would be to use MIDI Guitar stand alone or in a second instance. And this is adding another level of complexity, but this is just me being stupid maybe 
I also want to keep things as simple as possible and I play with a single instance of GP and no other application.
But being a guitarist, the priority is the Midi Guitar plugin, a good amp plugin and then the rest, trying to have rackspaces with enough headroom for both audio and cpu.
And because I’m wise, clever and not too greedy, I manage to do it. 
The only two Midi Guitar functions I use are MIDI conversion and Deep Expressor, and if the MG3 plugin is too greedy, I’ll stick with MG2 (I haven’t tested it yet because the plugin version isn’t yet available for Windows).
2 Likes
That’s actually clever 
1 Like
Hi.
I wonder if anyone here who has tried MG3 (beta) with GP has noticed a difference in tracking/response between the scenario of using standalone MG3 (and routing the MIDI into GP via virtual ports) and using plugin MG3 inside of GP?
I have noticed a distinct difference here so far.
I know that there are multiple points in the signal chain(s) that one needs to be aware of for best performance, and I have watched LoFiLeif’s excellent video which covers the subject ( https://www.youtube.com/watch?v=x_OUNKdIE20 ).
So, I’m really just interested in the experiences of others here - differences observed, or not?
Thanks.
I tested MG3’s “midi guitar mini” patch in both scenarios, using loopMIDI for the standalone version. No difference in terms of latency, tracking accuracy or dynamic.
Configuration: Windows 11 pro 23H2, GP5, MG3.
4 Likes
Gig Performer can be seen in this video:
22:05
1 Like
I’ve been using Midi Guitar 3 beta for a while now, a year or so, off and on, and lately a lot, and yes for me a game changer workflow is using the MG3 vst3 inside GP5. HOSTING THE PLUGIN INSIDE MG3!!
This revelation is from the standpoint of using the Stand Alone MG3 beta, latest feeding a midi output, then inside GP5 wiring I would assign a midi inblock of MG3 Output to a vst3 usually Ominisphere 3 for me, while this works, for me the tracking is light years better letting MG3 host the plugin likely AU of Omnisphere 3.
Now the issue for GUI handling becomes somewhat difficult as the tradeoff, I can assing a widget in GP5 to open the GUI of MG3 but afaik there is no way other than a Keyboard Maestro click mouse here sort of KM link in order to open the Omnisphere plugin window which is hosted inside MG3’s beta vst3, another issue with this workaround is you also have to open/close the MG3 GUI to see the plugin OMNI3 GUI, so for one screen MAcbook pro guitar setup it’s a bit cumbersome, but worth it for the improved tracking, minimizing midi glitchiness.
Sounds confusing but illustrating this would be cool, however it would take me a while, just adding my two cents to this issue, TLDR: I use MG3 vst3 to host the plugins as I find I get much tighter tracking from playing guitar into MG3 Omnisphere in this case.
2023 Macbook M2Pro 16Gb Ram, Sequoia 15.7.3 Motu Uttralite FW only audio interface, H2 Midi Pro and a Melo Audio Midi commander with an EFX MkII looping swticher that also sends midi.
EDIT: I think I see the error in my setup: if MG3 is sending to omni as a plugin block then like the DAW setup video shows the audio buffer should be set to 128 samples, just checked and mine was set to 512 samples , hmm pays to watch this video. ooh I think I learned that if MG3 is sending to omni as a plugin block then like the DAW setup video shows the audio buffer should be set to 128 samples, just checked and mine was set to 512 samples , hmm pays to watch this video. d mine was set to 512 samples , hmm pays to watch this video.