hurricane wrote: ↑
25 Feb 2019
A. we're just taking our time and getting things right
B. fuck, this is harder than we thought and we're having lots of issues and we can't release it yet.
I've worked in IT, so in my experience the answer is the big fat B
It's option A.
As the CDM-article hinted at/explained, it was required to re-write big parts of Reason in an effort to behave as VSTs expected buffer sizes to behave. From obvious parts like the VST integration itself to less obvious things like the count-in or send fx. This means there's a lot of areas to test, so we're taking our time to make sure it works well. Of course we also want to involve VST developers in this testing.
neilprivate wrote: ↑
26 Feb 2019
I’m sure their intentions are to release something worth the wait. As for how long that takes... could be a massive struggle. IMHO, in giving in to the huge demand for VST integration they created a nightmare. So many things are now out of their hands. I wouldn’t want to be on the dev team, but at least their management haven’t thrown them under a bus with a pointless date. This is the first time I’ve regretted giving up the hardware, maybe it will never work as intended again.
Yeah, regarding a date I think this is key: saying a date before we know that date will hold for sure is unfair to both developers and you—which I learned the hard way with the previous announcement. But don't worry, we're making great progress!
I wouldn't call the integration a nightmare at all, but it's definitely a different set of demands for the application as different plug-ins can behave quite differently. As for "working as intended", I'm not quite sure what you mean but our goal in general is of course that Reason should work really, really well. Allowing VSTs to use bigger buffer sizes and thus run as intended is one thing, but it's not like we'll stop working on Reason after that.