please remove this blocking message, I don’t need it to be realtime in my case, but I just can’t use it
thanks
Which DAW is that?
I guess we can make it optional to use large buffers, but we still need to warn all those who accidentally have a setup with large buffers.
1 Like
Yes. In the plugin version the buffer latency is irrelevant in a mixing situation. A simple warning regarding real-time latency could suffice.
Thanks.
Hi,
Thank you for including me in the beta test
I’d like to let you know that everything displays perfectly with automatic scaling on my 8K monitor with an RTX 3060
Thanks
(tiny) feature request: on settings like the bend range in midi output, both left and right click increment the value. why not have the right-click decrement the value?
i always seem to click once too often.
i try to avoid the mouse wheel or dragging, both are terrible for my wrist.
first world problems, i know.
2 Likes
Hey there,
Apologies if there is a shared solution already, I looked around.
With MIDI Guitar 3 I cannot escape the buffer flag upon loading the VST. I am using Cubase 14 Pro. I have changed buffer to 128 and restart my machine - still flagged, even with a brand new project. Same occurrence with 256 and a restart + new project.
Please advise when you have a moment, I’m very eager to rip my guitar with MIDI Guitar 3 + Serum 2!
Much appreciated 
1 Like
Found a solution. I kept trying after my previous message.
What worked:
- Studio → Audio Connections → changed from my usual Audio Device SSL ASIO, to ‘Not Connected’, then back to SSL. And it worked!
Maybe there’s something specific with Cubase 14 or SSL…
I DID initially have it at 512. But my issue was with MIDI Guitar 3 not being able to then recognize that I had adjusted it.
…now I’m off to have some fun with it 
Cheers!
1 Like
Hey I didn’t update my beta app since a long time, like since 3.0.5 something I guess, when there wasn’t a warning about the cpu and or audio interface. I play everyday, I mainly use it to play a virtual saxophone with my left hand tapping. (While I accompany me with my right hand on piano) The thing is now I get this warning all the time, and I’m really sad to see this, because sometimes there are notes that are not being picked up, like long sustained notes above the 12 fret, and it saddens me, the ammount of satisfaction I get from this setup is beyond what I get out of playing normal guitar. What are the recommended hardware specs to run this software smoothly? I kinda don’t have money right now to buy a new computer anytime soon, can I uninstall this version and use a previous one that used to run more smoothly?
This depends very much on the VSTs you intend to use and therefore a general advice is difficult. If I were you I would try the latest version of MG3 since I don’t think that the first few versions were less consuming in terms of CPU power. Keep your 3.0.50 download to go back in case you are not happier with 3.0.61
https://jamosapien.com/t/download-midi-guitar-midi-bass-midi-cello-3-0-61-beta/8557
PS: I still have a copy of 3.0.49 and also 3.0.50 I could share with you in case it’s necessary.
1 Like
If I recall correctly, there shouldn’t be any tracking difference in these versions… other than the input gain control. Did you try to bump up input gain?
Another issue could be you are running single threaded and overrun the CPU - set it to force multithreading in audio device settings.
Does this help?
1 Like
Here is a video where I’m tapping my guitar with my left hand only uninterrupted long notes, so you can see how it doesn’t behave as expected (MG playing these notes uninterrupted), as you can see the CPU meter doesn’t show any high intensive cpu processing, this behavior wasn’t present before. At this point I just want to believe I am the one setting up the saxophone vst (SWAM Tenor Sax) “wrong” so it has this weird behavior.
I must remind the developers that I’m beyond grateful for letting us humans go beyond the physical limitations of traditional musical instruments, 加油！
Thank you so much for your support, I’ll let you know!
Nevermind I think it was about how the aftertouch being the parameter controlling the expression parameter of the plugin was giving me this unwanted behaviour, now with this correction I got it working fine!
1 Like
Hi.
Working with MG3 3.0.61, under Win11 on new HP laptop -
I am experiencing (seemingly) random crashes when changing patches from foot controllers. (Line 6 FBV Express MkII, or Behringer FCB 1010 (with UNO mod)).
I don’t see a MIDI Monitor available inside MG3. Am I missing it?
If there is not one, I think this is much needed. AFAIK, I’m sending in a very clean MIDI stream, just PCs.
However, downloaded it. Not anywhere can we see what the requirements are for Windows 10, (or MAC for that matter) or if it works at all on Windows 10. PLEASE! it’s not enough to list all the features, and to download it and test it and only then we detect that it doesn’t work. You must state at least CPU cores, and speed, minimum RAM as well as minimum hard disk. And of course minimum operating system and version.
I thought I could set it at 512 buffer size to test non-crackling sounds anyway, however at great latency but it didn’t let me pass through that phase anyway. So this will be a big no-no for me even if it gets a full release, non-beta. And the GUI !? What have you guys been smokin’? At least MG 2 was resizeable with just drag the mouse at one of the corners.
The latest version 3.0.63 has some performance improvements. The MG3/MPE tracker is more demanding than MG2, but you can select the MG2 tracker inside MG3 if you have a very old computer.
We collect data on computers that doesn’t cut it, so please let us know what kind of computer you have. These days GHz doesn’t say much on Intel/AMD CPUs, but you probably need 4 cores if you have an old system. Please mind, often performance hiccups is not because the CPU overload, but rather Windows DPC latency or driver issues.
It should resize the window.
if your issue is crackly sound then:
- if running a laptop, test it with latencymon.
- make sure your audio interface is connected directly to a usb port, no hubs.
- completely disable cpu power saving
- disable any unneeded services, turn off wifi,
- verify that you are using the most up to date asio driver
the limits you’re experiencing are not related to mg3. i’ve had it running on a 10 year old 4 core desktop without issue. however, i have never been able to eliminate crackly audio on certain laptops. this applies to ALL audio software running on the laptop, not just mg3.
the ui is resizable.
1 Like
Hi this is a good idea i test Beta Midi Guitar 3.0.60 and i play with eletric-violin acoustic and is not perfect because when play a vst stradivari violin for native instrument on kontakt the note is too long not stop when finish use the bow on the strings
more realist but when play a string LA pley toghether String RE in midi note
maybe correct the note on and note off
i have a question play violin eletric-Acoustic is best on play eletric violin because have a problem for resonance string and have a resonance midi note
Thanks for work i wait best update for correct violin sound on midi sound
are you using the cello/violin tracker?
you may need to adjust the gain setting. also ensure that you are getting good levels on the audio interface.
a non-chambered electric violin will probably be the best choice.
if you post an audio sample others will be able to help you improve the tracking.
Yes I use violin tracker, the gain is 0 and in my recording study the all optimization for record and for session…
Because is a recording study
OK I pubblic audio for example but this tracker is good maybe only when use the bow capture not always but capire two note midi…
Probably the violin electro acustic have a resonance acustic?
Because the sound not stop when remove the bow on the string