Exactly. Changing the code relating to the locked sample buffer for one part but not for the other
is not rewriting the engine in my book. They are not rewriting the engine.
Exactly. Changing the code relating to the locked sample buffer for one part but not for the other
It's not like it's some small piece of code in one place. It is probably through every facet of the audio engine, and needs possibly a full rewrite. The time they have spent is a proof of that.RandyEspoda wrote: ↑22 Feb 2019Exactly. Changing the code relating to the locked sample buffer for one part but not for the other
is not rewriting the engine in my book. They are not rewriting the engine.
Totally agree with this, I am using Ctrl + S in an obsessive compulsive way, it doesn't cost anything to click that combination so I do every couple of minutes.guitfnky wrote: ↑22 Feb 2019just seeing someone mention working for two hours in a session without even considering saving stresses me out. I mean, I get that Reason is fairly stable, but that’s only a small piece of the rationale for frequent saves. what if there’s a power outage? what if some other hardware component decides to fail at an inopportune moment? what if a driver issue crops up unexpectedly? there are thousands of reasons a program—or your computer—might stop working.
kind of baffling that anyone with more than a couple of years using computers still hasn’t learned that lesson. not really trying to be snarky as I’m probably coming across, but I just don’t get it. it’s not like saving takes a lot of time. literally a two-button keystroke.
I agree, if sometimes a "rewrite" in sense of modernize or reorganize or refactor might be usefull, as long it is not a throw away rather than a migration(-strategy)...If Props would throw away what has grown over the last 20 years just to start from scratch, this would be fail.Ad0 wrote: ↑22 Feb 2019
I just imagine that this problem propagates through the whole engine
It's not like it's some small piece of code in one place. It is probably through every facet of the audio engine, and needs possibly a full rewrite. The time they have spent is a proof of that.RandyEspoda wrote: ↑22 Feb 2019Exactly. Changing the code relating to the locked sample buffer for one part but not for the other
is not rewriting the engine in my book. They are not rewriting the engine.
Thanks for staying on topic.
the only reason I think they’d delay 11 would be if it’s ready to go before the 10.3 patch. they certainly can’t release 11 first, but I don’t think it’d have a huge impact on a major release date, otherwise.
I also wonder if they're spending time trying to pre-empt individual vst issues? If it does go to public beta it will get tested against a vast number of vsts and maybe they are spending time testing as many of those as they can to make the beta run smoother??? Just a thought.
Of course it's pretty obvious they underestimated the process and likely indeed it would be nested
The migration method would be most likely 'if' they would take it to that extent,Loque wrote: ↑22 Feb 2019
I agree, if sometimes a "rewrite" in sense of modernize or reorganize or refactor might be usefull, as long it is not a throw away rather than a migration(-strategy)...If Props would throw away what has grown over the last 20 years just to start from scratch, this would be fail.
Just look at MS with Windows...they migrated it over around 10 years...ok, might be a bad example, because they better had thrown it away
If they can allow putting unused tracks into idle in a 1-button click way, then that would fix a whole lot of problematic projects I have. The problem is that even tracks I keep in the project in case I would eventually like to use it (i e template projects), consumes DSP.BananaSkins wrote: ↑23 Feb 2019Adding VST support so late down the line has opened up a whole ‘Cans Of Worms’ for Props! I honestly don’t think we will have a stable working Reason with VST support until 2020...until then track freeze might be thrown into the mix to keep frustrated Reason users happy. IMHO
I'm OK with this, but only if they make the upgrade to 11 free (for V10 owners) or PWYW.
That would cause such a massive shit storm on the internet.
Mattias only said that the wasn't sure whether RE performance improvements were involved in the work they were doing months ago. I expect that this position was not well received by many people. This was back when they were aiming for Q4 2018.RandyEspoda wrote: ↑22 Feb 2019Exactly. Changing the code relating to the locked sample buffer for one part but not for the other
is not rewriting the engine in my book. They are not rewriting the engine.
Most complaints I've seen come from people using fruity hardware OS or who have to rewire.
Users browsing this forum: No registered users and 24 guests