I used MG3 HEX without problem for weeks in Studio One 7.3 on Windows 10 until very recently. Now, I get Studio One to crash whenever I try to use MG3 inside a session or as I close the session. I presume the problem is linked with MG3 vst3 because other sessions without the plugin are fine and no crash.
As a test, I created a new session, one track and just MG3 vst3 alone, I got a crash while playing with the plugin or again, while closing. If I reopen Studio One with VST3 disabled (MG3 only plugin), no more crashes. Might just be something else With Studio One, but that’s what I have as a clue for now. There seems to be some odd corruption developed between MG3 and Studio One.
I tried to reboot of course. I uninstalled MG3 and Studio One with Wise Program Uninstaller and reinstalled them. Same problem. System looks functional.
I would appreciate any guidance on how to resolve this. I have no more ideas.
I don’t experience crashes using MG2 vst2. But the problem here is, and I don’t understand, why I can not set the HEX inputs as easily as in the vst3 version. That would be a simple fix.
My track presets are made of one MG3 instance along with the instrument.
I was having no problems running MG3 vst3 inside a session before. But I will try again the stand alone/LoopMIDI version. I just liked the way I can recall a MG3 setup with the instrument in one go in the session.
Thanks for replying. I tried to analyze the .dmp crash file with Windng. I have no idea why but it is always referring to some stuff from another session that is working good. I checked the date and hour on the actual .dmp file for the session that just crashed and I can’t get relevant details . I am baffled. I did get an update of Windows recently but I think problems developed after. I will check the interface drivers but I doubt it is the problem as other sessions are running smooth.
Come to think of it. This is wild supposition but I reported a couple weeks ago getting a new and strange message from the MG3 plugin What to do with this message?
and just realized that I did not get this message recently and it coincides with the crashes. Not implying anything but this is just a strange occurrence.
Well, I am not sure what I’m doing is right or not. When I got my Hex pickup/interface, initially I could not get any input from MG3 HEX in Studio One. It was puzzling. A couple users on this forum provided some hints and I ended setting the audio track input as Surround 7.1 (hard pan all channels - that eliminates the dry sound from the guitar). That worked.
Now, I tried again to use MG3 vst2 and it looks like vst2 does not allow this for some reason.
If anyone has a better understanding than I do re the inputs, please, let me know.
Well, even the Standalone version is crashing. No instrument, just MG3 in HEX mode. Playing with inputs gets the program to quit / crash. I rebooted, reinstalled MG3, interface drivers (Presonus Studio 1824c). Is there a file that needs to be discarded perhaps (cache, settings etc) ? I mean MG3 was working fine with that interface and I don’t think I changed anything.
Analysis the dump file (via perplexity for more readable text formatting), if that can pinpoint to something :
I vaguely recall some previous crash report with many-channel interfaces on Windows.
Are you using some kind of hex breakout box/cable to the Presonus interface?
I may have to get one of these interfaces to reproduce it.
There was another report of the VST3 (but not the VST) being mistaken for a surround processor in another DAW (GigPerformer I think), and it did some obscure channel mapping, so that might be an issue also with the MG3 VST3 reporting its a surround professors, or maybe the DAWs just think 8 channels is always for surround.
I’ll look into all of this.
Btw, there are two ways that you can run the hex audio from the DAW, in audio settings: 1) either the standard way of using the audio from the DAW, or 2) by opening a dedicated interface directly in the plugin. Did you try both?
Thanks for looking into this. Yes, I have an homemade break out box and it worked perfect for weeks with the surround inputs. Suddenly, something changed and I wish to know what. It feels like some kind of corruption. Any clue on what is that ntdll.dll file (failing module) ?
If you think it’s feasible, send me an installer and I could test the app on my interface.
The ntdll.dll is a core part of windows. It doesn’t tell me much, but most likely this has to do with the audio driver.
No nothing can suddenly change. Do you use the same interface for both input and output? Can I get you to paste a screenshot of MGs audio settings window?
Could this be the issue? If you are using the DAW’s audio routing for the various string inputs (as opposed to selecting the input device in MG3 Hex directly), you should change it to 8 input channels, as shown below.
