In the plugin version there is now “general settings” which has two settings:
Force Multithreading. For systems which run hot on the CPU.
Ask DAW to give MG plugins 8 input channels. For hexaphonic hardware. The MG3 plugin cannot really do anything else than kindly ask its host to use 8 input channels. Eventually, some hosts who dont support this, may add support for it.
Yet another attempt to harden the plugin loading to hopefully load the remaining troublesome plugins (Spectrasonics)
Thanks for the update, looking forward to testing it.
Small request for the next update is to process notes below E2. Everything I play on guitar is in some form of drop tuning, so it would be much appreciated to have that ability. I know its on the roadmap, I’m just impatient
Just downloaded 3.0.54. I’m still getting the JX10 AM Synth problem where it can’t load it if I made select a patch from inside the synth and save as a new patch.
Sorry , pics didn’t transfer clear, doing this on my phone
Hi, I am new registered user of MIDI GUITAR, and I find it amazing! My congratulations to the developers of this software, is worth every cent.
I hope this is the place to post some things that I observed during the (short) beta testing that I have had so far in the past couple of days.
My knowledge of MIDI is almost zero, so I am not even sure that this is a problem, but I was monitoring the midi flow from MIDI GUITAR in my DAW for other reasons; I put the guitar in its stand after some playing and I found that there was a steady flow of midi (caused by remaining vibration of the guitar strings). This was happening even when the output of the guitar was way below the Noise Gate threshold. The MIDI messages showing up in the DAW were labelled as Type:AFT (aftertouch I guess).
It was not a high stream of data to be concerned about, maybe 20-30 messages per second I estimate…but anyway I thought it was a good idea to report because I think that the noise gate should be cutting off that unnecesary flow to the DAW once the threshold has been reached and maybe is something that the developers want to look at. Apart of the AFT messages there was no other midi or MPE messages, so it is unnoticed unless you are monitoring ther whole flow like I was.
Not Kontakt 7 is supposed to “see” MG3, but in MG3 you can insert K7 as a plugin in the standalone version. In a DAW there are various ways to send MIDI from MG3 to a VST track.
Hi, I’m a complete newbie using MIDI guitar and I was using 3.0.48 beta with MainStage having different patches on it with different Arturia instruments for switching and playing with them in the same concert, I updated to this beta and I noticed that only one patch with Midi Guitar gives output but not the rest (the plug in itself receives the signal but there isn’t sound and even if I duplicate the working patch the dupe won’t work). I was wondering if something changed or if it is an error of some sort. My first reaction was to downgrade to 0.48 but the download link isn’t working anymore ;'( Thank you!!
Just a small idea. Can we have an UNDO option in MG3?
Or maybe rename some buttons.
I keep setting up presets and I keep hitting NEW instead of SAVE.
I don’t know why it’s confusing me but I did it at least 10 times by now.
I just got the HEX, it’s fantastic.
PS it’s 30 minutes later and I just did it again.
In my mind SAVE means overwrite the current preset.
NEW means save the current creation as a new preset.
Make sure your volume levels are set for the individual chains in the mixer section.
I speak from experience having spent many minutes trying to figure out why I couldn’t hear any sound only to realize I had made adjustments to hear one chain over another.