I dunno, I think at this point that I fell down a rabbit hole with this one.
At this point I'll just go with the release build, b373, seems to be working fine, although it is not as forgiving as Mixcraft 7 as far as freeing up resources before it starts.
There may be something in that, I don't know, I don't know enough about how Windows manages resources, but I used to start Mixcraft and work in it, leaving whatever other programs running, and then shut them down if I got any hiccups (which I rarely did). With Mixcraft 8, I need to have things "quiet on the set" before I start a session, and then it's okay.
Of course I will keep an eye on it as I continue to use it. The different buffers in the .dll did not seem to have much of an effect, I will say that.
If you can't reproduce it, it ain't a bug.
It's a great release; I freaking LOVE the nested submixes, being able to select multiple tracks and have their controls move in unison, the verbose Undo/Redo (actually that feature alone may be worth the upgrade price!), etc. Simple as it is, the ability to plant a marker with a single keystroke is great, especially for video work, where I may have someone in the band over my shoulder telling me that it should fade right....THERE.
If Anorax hasn't experienced any more of these symptoms, I will close the bug report as not reproducible....