I run win 10 with 16 gb ram i5. i have used 2.2.1 on Sonar and now on Reaper . Ive tried using 3 on both but it wont open the standalone and both DAWs crashed trying to open it. Ive tried various versions to no avail.I have no problems with Kontakt or any other big apps on either DAW. Theres nothing wrong with my PC and i have all the needed MS exe for VST GUI. I keep reading about how everyone loves what it does and they have the same setup .When ive had problems like this it usually meant the app is corrupted somehow.
it sounds like you’ve covered the likely problems.
if you suspect corruption it would make sense to download the latest beta again and reinstall. the posted file is not corrupt, as so many of us have used it successfully.
your log files may offer information as to why mg3 won’t run.
look in AppData\Roaming\JamOrigin.
also scanning your event viewer can be helpful.
latest beta download:
https://jamosapien.com/t/download-midi-guitar-midi-bass-midi-cello-3-0-63-beta/8557
the only thing i see is something about thunderbolt USB driver error. I have Focusrite Saffire 6 USB and that was logged as fine .I have found that thunderbolt relates to win 11 . my PC isnt compatable with it .But that shouldnt make any difference . I have the same OS and Hardware and Drivers as anyone of the many testing it out …Ive been trying to get it to work for the last 8 months on and off … Update … found dell driver. Ill let you know what happens… new update it finally installed after trying different ways . that error disappeared but it still crashed . and the text states crash , then lists 8 exceptions midi mini being one of them . whatever that is . unhandledexception is another exception listed. 2.2.1 lists all the irs and sfzs then oks the audio and plugins 3 gets stuck just as it tries to register something in midi mini . crash, exceptions. im giving up … its not worth the freaking hassle. fck it.
The problem isn’t MIDI guitar 3, it’s the fact that firewire audio interfaces are not supported by the later win 10 releases (beyond win 10 built 1809) and win 11 anymore. As good as the Focusrite Saffire was it’s time to get a new interface. I have a fully functioning Yamaha N12 mixer and a Mackie ONYX 400F that I can’t use anymore due to the same reason!
I understand that , BUT, My Saffire is just USB and Midi , thats it. No Firewire . the Errors are being caused by something called Midi mini something , at least thats what the log looks like .Ive compared the 2.2.1 and 3 logs . Apparrently its something associated with a plugin ??? its hard to tell , im not fluent in script . i could be totally wrong . i know it isnt a firewire issue , i have none .
‘midi mini something’ is unfortunately not helpful. it is most effective to copy and paste the exact errors you find in the log.
usually a problem plug in will not crash mg2/3 except when loaded into a patch.
i don’t think you can rule firewire out as a problem yet, if you have a firewire audio driver installed it may be causing your problems, even though you have no firewire devices attached.
There is no Firewire driver in the USB driver supplied for Saffire USB , Heres the log that states the MIDI MINI exception .this does not occur when 2.2.1 ok the plugins section . .MIDI Guitar 3.0.63
Initializing platform
Initializing plugin formats
Offbeat Engine is ready
User Directory: C:\Users\user1\AppData\Roaming\JamOrigin
Setup Offbeat Engine
Loading Patch Settings and MIDI Control
Preparing to play: 44100/256
Offbeat Engine processing 44100
Number of audio channels: 1/1
No internet for downloading: serverinfo.txt
Loading Patch: MIDI GUITAR MINI
Crash:
Loading MIDI MINI patch
0: VSTPluginMain + 0xfcfd5
1: VSTPluginMain + 0x418fd2
2: VSTPluginMain + 0xfd3ba
3: UnhandledExceptionFilter + 0x1e7
4: memset + 0x1218
5: _C_specific_handler + 0x96
6: _chkstk + 0x11f
7: RtlRaiseException + 0x484
8: KiUserExceptionDispatcher + 0x2e
Have you tried to startup with internet connectivity?
Make sure the “serverinfo.txt” file is located in directory as shown below:
Yep , internet connect does nothing .I have serverinfo txt document. And i uninstalled the Focusrite newer driver. There was a Thunderbolt driver in the install i found . i can use Steinberg ASIO,it seems to work , using the 1.9 usb driver . Im at the point that ill not even bother with the app until i get win11 on a new tower . screw it ,not worth the hassle . Im working on projects and i dont need this crap . Im going to reinstall my focusrite drivers and just put all this frustrating crap behind me …thanks …im done here
Seems you’ve already given up but this is an unusual issue and made me wonder what could be happening.
Note, “MIDI mini” is related to the Windows system and “MIDI Guitar MINI” is a built-in preset in MG3. I am not a frequent Windows user, but I’m guessing that the MIDI Guitar MINI (built-in preset) is corrupted or confused about the MIDI Output port it has assigned to it. Is this a possibility?
My first step would be to try and remove all MG3 from the AppData folder and reinstall. Also have a close look at any MIDI port config. Has anything been renamed or had a number added to it?