You won't be testing performance improvements in the first phase, you'll be testing whether the code changes have introduced new bugs or not. Then when the non-logging version will be released (after the bugs discovered during the first phase have been quashed), you will be able to effectively test the performance.guitfnky wrote: ↑15 Mar 2019so if the logging slows things down, how are performance improvements made apparent?
not trying to get in the weeds; just genuinely curious (been wondering about it for weeks, and I’d assumed the logging thing would be turned off or handled differently, somehow). is the logging-related slowness clearly different than VST performance? (so as a user, I’d be able to see something and say, ‘oh, that’s just because of logging’.)
or is that just covered in the beta testing instructions?
I’ve only been involved in one Reason beta, and opted to leave that for others because of the logging, so forgive my ignorance...
Something tells me that the performance improvements are such that they will compensate for the logging sluggishness anyway, and that the logging version will perform exactly like 10.2 or even a little better. We'll see...
Edit: what Mattias said.