Well now, that post differs from your original request enough to almost call it a different subject.
But know this... In general, I wont disagree with much of what you wrote, nor several other recent threads in the forum.
I have no interest in slagging on Acoustica, I like Mixcraft and as a long time user feel they have been good to me. But at the same time, I wont deny fact.
I accept that there are many possible reasons for some reported issues. And would point out that some people are successfully running some of the titles mentioned here as causing trouble. So there may be more than one thing going on.
But the experiences I have had, people I collaborate with have had and are often reported here, strike a similar tone (no pun intended.)
An abbreviation of my own experience would allow that many some of these problems are far from new. In the period of MX 5-8 I considered that some of the issues were "economy class" plug ins, both user supplied and included. So I began to migrate to upper tier products. It did seem to help, but the jury may still be out on some of that.
But some of the bundled plug-ins are certainly pretty dated.
Then when 64 bit MX became a thing, and many current third party plug-ins had already migrated in that direction, I did too. I felt maybe some issues I experienced were due to projects mixing 32 and 64 bit plug-ins so I tried going all 64 bit. Again, I think it helped with some things, but not all.
The plug in industry hype behind vst3 caused some optimism but reality for me is that in most cases, they were problematic in MX, and since the hype never really seemed to unfold into anything substantial functionally, I just avoided them when possible. But the plug in producers seem to be migrating to it anyway, so that could be a growing issue.
Acoustica seemed to be trying to whack-a-mole vst3 compatibility issues on a case by case basis for a while, but that was probably mostly a hopeless time-suck for them.
I accept that many plug-ins are buggy. Some vst3 issues may also be programming related.
But just as others have said... Over the last two years or so I have had the eye opening experience of running the same projects with the same plug-ins in other hosts and having not just less problems, but in many cases NONE of the same problems experienced in Mixcraft. Which is especially annoying as I, as others, really prefer the familiarity and work flow of Mixcraft. I want it to work for me.
But entirely too frequently, I experience spontaneous program closure. No warning, no explanation, just poof. Gone. Then there is the occasional lock requiring a user forced closure. Less frequent, but enough to be annoying. Then there is the infrequent, but extremely troubling momentary lock, followed by an audio explosion that I truly fear could damage gear or hearing. Often enough to have developed the instinct to suddenly rip off my headphones when I anticipate it may be coming.
So I dont lack sympathy for these and other comments. I am actually surprised that among all the feature requests for colors and other seemingly trivial tweaks, including some I myself have requested version after version, even before this extended suggestion thread (note, first reply here but far from my first on the subject) havent had a lot more frequent requests for improvements in stability, reliability and plug in compatibility.
There has also been a growing discussion on some issues of MIDI routing. This is outside of my own area of use or interest and I have to admit I dont even understand some of what people are requesting.
But I suspect somehow that some of the issue with this might be that a fix is not only complex, but might break the backwards compatibility ethos that Acoustica has always embraced for Mixcraft. Like I said, guessing. I may be way off base.
In looking at a recent thread it occurred to me that maybe a solution could be the creation of a MIDI routing plug-in designed specifically to work within Mixcraft. Just a thought.
It also occurs to me that at some point, developing a modern feature rich DAW is likely to break the backwards compatibility anyway, and in order to move forward, that may have to be accepted at some point.
Again, guessing. Dunno.
Some are using the term "falling behind" and I wont deny feeling that too. Looked at another way, some competitors products have certainly leapt ahead.
I look forward to the next version with an open mind and high hopes that it isnt just another small incremental improvement.
Its time to go big Acoustica. I am hopeful that is the reason behind the delay.
