The upshot is you're going FAR out of your way to be corrct here and we're actually talking about two entirely different things.JiggeryPokery wrote: ↑10 Aug 2017Sorry, SA. That's just not true. There is at least one that's definitely worth mentioning. But you know, NDA and all that prevents a detailed discussion.
But the short version: graphics and custom displays.
I suggest you compare the draw rate of Proton with its basic GUI custom display lines to that of, say, Serum, which is vastly more complex. There's no lag manipulating the GUI in Serum.
But hit the mod page display button on Proton for the first time after instancing (subsequent redraws do seem a bit faster, probably because it's not initialised until it's first called) and you can see Reason struggling to draw basic boxes: it's not drawn instantly, it probably takes a good quarter second, and bare in mind I'm on an 8-Core Ryzen with a Geforce 1070 so I'm sure it's going to be very noticeable for users on some older machines. (There may have been a workaround (other than not using that many boxes ) that would have made Proton's draw a bit faster that we suspect is not in place, but it's hard to tell). And we've tested this ourselves.
Reason's graphics are so far behind what is possible in a dedicated VST it's not funny. We've been working on one of—quite possibly the most—complex draws of any RE yet published, and it's been painful, and very difficult to test in the SDK's logging version of Reason, so that we have to upload everything to the server to test it in Reason Actual, just to stand a chance of giving it a proper test. The last SDK update was useful in that it [redacted#1] but then bizarrely didn't [redacted#2] to actually allow [redacted#1] to be as useful as it should be. And also passing data from the custom display code to the C++ code or vice versa forces a lot of compromise and loss of functionality.
The upshot: you're wrong. 100%. Sorry.
Did you just point out the graphical differences, bud? That's great. I'm talking about functionality.
And no, I'm not wrong in the slightest = EQ VST's behave and have "workflow" just like EQ RE's. Stop trying to mince words into a disagreement. I'm not trying to argue, but you're talking about something completely different than I am all in effort to end it with "you're wrong".
I'm not. The two formats aren't drastically different in terms of usability, workflow, or functionality. If you want to point out graphical GUI differences...LOL....go ahead.