Hey bro. Were you using MPE? Because mine always crashes too but only when i use MPE mode
1 Like
No, Iām using MIDI 1.0 Legacy. Sample Tank doesnāt like MPE, and Iām running 8 instruments each assigned to a specific midi channel, so I need to use MIDI 1.0 Legacy.
So, running MG3HEX standalone or as a VST in Gig Performer at idle, not playing anything, just loaded and open at home, it will run for hours and not crash. But it crashed again last night under gig conditions in what has become the normal pattern. I usually run with at least 2 and sometimes 3 SampleTank instruments playing at all times, it crashes at around an hour of use and if I open it again it cannot find the GP-10 driver so I have to restart the machine. CoreTemp does show some critical temps, but never reaches TjMax temp of 212F. I think highest Iāve seen is 197F. The pattern continues 
I have a gist. I fixed my crashing problem. Iām not sure if it will help you but maybe, just maybe its the sample rate. Because my pc runs hot on 128 and then crashes. But on 256, it doesnt crash anymore:)
However thats sacrificing low latency though. But its still playable at least. I just wish JamO can find a way for MG3 to not use cpu power. I canāt even record with MG3 without it freezing.
1 Like
I play MG3 live at my church btw. So far iāve tried it with equator 2 and 4 instances of zenology on seperate tracks. I run MG3 in standalone mode with loopmidi sending midi out to studio one. I think thatās the best method for a windows user:)
But to prevent crashes, i really think itās the samplerate being 128 that causes it. My computer is a modern one so it will handle it better than others
1 Like
My buffer is set at 128. I donāt like 256 it has too much latency. I was hoping I could use 64 buffer but itās glitchy. My computer is modern, i9 processor with 64GB RAM and a Terrabyte HD. Iām really thinking itās a heat issue with the crashes. Iāve ordered some fans and Iām trying to reposition the computer. Weāll see if that helps.
Curious ā what temperature is your CPU reaching when you experience these crashes?
Core Temp was showing 194 deg F. Iām also curious about cores and threads. The PC is Core i9-13900H, 14 Cores and 20 threads . Yet MG3 never shows more than 2 Cores running.
supposedly 1) your cpuās upper temp limit is 212f and 2) cpu temp monitors provide useful info, but the temperature is actually derived and not measured.
so, it could be that your cpu is bumping up against the upper temp limit.
as there are a lot of mg3 users who havenāt encountered this issue i am leaning towards sampletank as the primary suspect. a search for āsampletank crashesā does find a lot of results naming a lot of daws/environments.
in a somewhat similar situation but with a different product i was able to bring cpu levels down by reducing the number of samples played simultaneously.
did you ever run latencymon? it might provide some useful info.
1 Like
Agree the more sampled instruments being run, the hotter Iām sure it gets. I have not run latencymon. Is this the software you are refering to? Resplendence Software - Free Downloads
As far as a lot of MG3 users who haventā encountered this: Are they HEX users, are they on PC rather than Mac, and are they using it in live gig situation for for 3 hours a night? I donāt see many actually in my situation.
Really at a loss as to whatās causing these sudden crashes.
Working on the idea that it was heat, I installed spacers under the pc for airflow, then installed a fan to blow air in from one side, and a fan to suck air out of the space where itās installed. Last night, the case never got hot, and I made it through a one hour set without a crash, but half way through the next set it crashed. I have tweaked the control panel settings for music (best performance, no power reductions, no USB power downs when not in use, etcā¦). This guide recommends turning off HyperThreading in BIOS , I wonder if that would help or hurt MG3 hex? Optimize your sound card and audio software settings
thatās the latencymon i meant. it wonāt fix anything but it may provide info as to the likeliest offenders.
iām running mg3hex in studio for hours and hours without any lockups or freezes.
in terms of hyperthreading, mg3hex itself is really not a resource-hungry application, so i doubt youāll notice a performance difference, but i also doubt itāll help the situation.
as the pc lives close to the floor, is it possible the air vents are blocked by dust?
do you have a desktop pc you could experiment with? if so, iād load everything exactly as it is on the mini pc, leave it running to see if it also hangs.
also the windows eventviewer may contain some clues.
It lives close to the floor only during the gigs, but the vents are clear and with the additional fans Iāve added, itās running cool. I have let it run all day (like 8-10 hours at home), occasionally playing something through it, and it doesnāt crash. But thatās not the same as playing solidly through it for 3 hours on a gig. Crashes seem to occur after an hour of solid performing with MG3Hex driving 2-3 instruments in one SampleTank VST. The crash happens always happen like this: I hear a midi note is stuck, I look at the display and its showing the desktop (program has is closed). If I was running MG3Hex standalone it is closed. If I was running it as VST in Gig Performer then it is closed. The driver for the GP-10 is no longer showing as active and I have to restart the computer to get the driver back before I can run MG3Hex again. So perhaps the problem is some conflict with the GP-10 driver? Are you using a GP-10 in your set up?
@erol, Iāve been following this thread with interest. Disclaimer, Iām not an avid ST4 user and Iām also macOS only.
Here are some more ideas after scanning over this evergrowing thread again. Apologies if Iāve doubled up on anything:
- Have you tried running SampleTank 4 as a standalone application rather than as a VST?
- Have you run a search on possible causes for ST4 crashing itself or a DAW?
- Have you run a search on possible GP-10 driver issues in Windows (insert version)?
- Is the GP-10 connected to a USB hub or directly to the computerās USB ports?
- Is your mini PC running on mains or battery power?
- Did you collect any crash data from GP5?
1 Like
to me this implicates the gp-10 driver. if it was sampletank crashing then mg3 standalone would probably remain operational.
this means though that youāre sharing the gp-10 as an audio interface between mg3 and gig performer? i could see that being problematic.
iām running mg3hex on a zoom l8 mixer. the zoom provides input only, for output i am using a second interface.
can you experiment with a second interface? rather than playing for hours, you could use the looper to keep the system active.
1 Like
GP10 on Mac. M1 Studio with macOS 14.x.x
Definitely not stable. I did the usual session with GP10, 2h of playing (at home) and sound design. In the middle if my run GP10 started acting crazy. Then Tone Studio Crashed and I had to switch GP10 off and on to show it again as a unit.
1 Like
Is your GP-10ās buffer set at standard?
I donāt use the GP-10 often these days but I donāt recall having massive issues with it losing connection even over long periods of connection except with a faulty USB hub.
Possible problem with sample rate mismatch? System audio vs application audio?
1 Like
I mentioned in my video about setting up the GP-10 with MIDI Guutar 3 that it hijacks the system audio.
1 Like
Thanks for the suggestions.
Is your GP-10ās buffer set at standard?
*128buffer set in GP-10 driver control panel and in MG3Hex.
Possible problem with sample rate mismatch? System audio vs application audio?
- This is something that bothers me. The GP-10 only shows 44.1kHz as an option in itās driver control panel. Yet I know many VST instruments are 48kHz and 24 bit etcā¦ I assumed MG3Hex must do some kind of a conversion with all the VSTs? I donāt see any setting to adjust.