normen wrote: ↑14 Feb 2018
Theo.M wrote: ↑13 Feb 2018
but reason did not perform great with rack extensions either. Reason's performance shone up to the rack extension addition.. Before that, you could run hundreds of the built in devices (and still can i presume, of those particular devices).
One thing I have been trying to explain for an eternity though, is that reason falls apart quicker than other DAWs.. It simply can not access the same percentage of your total cpu across it's multithreading before crackling as other daws can. This is irrespective of whether you use vst/RE/ or just built in devices. The built in devices like thor et al, simply take longer to get you there because they are SO light on dsp, especially on modern i7's. BUT, reason still falls apart at about the same percentage of cpu usage, it's just that RE's and vsts will get it there way quicker.
It's not the answer to say if you want to use a lot of vsti's don't use reason.. reason is a fully fledged DAW with advanced features and midi, and is targeted at composers IMHO.. the answer should be that props improve it...
I did test 9 demo to load and export some old songs' midi, and the pdc was awful. I don't know if ten is any different. All i know is that the pdc has no visual compensation from the time i tested it, so the playhead cursor was not in time with the music. I hope this gets improved too.
I think it's time for props to stop adding features and buckle down on the plugin performance and pdc engine and just refine it like crazy.. that's what I would do if i was them anyway.. and there is no reason why they can't add a playback buffer for non armed vsti tracks that aren't in complex modular configurations.. to improve performance.. just for straight vsti's that have the vsti and normal insert effects.. they could mimic the way other daw's do it for those tracks.
Yeah well. You can fish the answers to those questions and statements from my post history. You keep dragging in the kitchen sink and I‘m really not interested discussing all of those boring topics again. A hint for the technical questions might be „DSP load is not CPU load“.
Did anyone check what buffer size this wrapper runs the plugs at please?
No it seems you don't understand the difference between cpu and dsp load and keep trying to pile that back on me.
You are always nasty and condescending and a huge part of why I had muted you, but i unmuted you as it had been ages, tried to be nice to you, responded politely, and you have been your usual high almighty self. Such a nasty person.
Don't worry, this is literally, the absolute last time in my entire life, whatever of it is left, that I will ever see another thing you write, nor speak to you ever again.
To others who are interested:
When i am talking about CPU load, i am talking about the real cpu load using istat or activity monitor.
When REASON'S dsp bar is full and crackling is occurring, in my machine it is only about 250% of total 8 core load, which has a maximum of 800%.
DSP meters in DAW's *ARE* a very useful indication.. for example, Cubase's meter is an asio meter, NOT a cpu meter.
But you will find, that if that meter is full, Cubase has issues. Just like when Reason's dsp meter is full, reason can not play back without clicks and pops.
The difference is, which Normen can't comprehend (or he does and his incessant hatred of me is just that strong that he always has to be difficult about it)., is that when reason's dsp meter is full, the REAL CPU usage of the computer, is about half of other DAWs.. it simply can't as efficiently access all the power.. When cubase's asio meter is full, the real cpu being used is almost 600% of the 800%. Vs 250 ish percent with reason.
This is exactly where j bridge and vienna come in.
Logic gets to 600, PT to 700 percent. Nothing load balances like PT.. Anyway it's very simple, i installed the 10 demo and nothing has changed even on my modern macbook pro.. a totally different computer to when i previously used reason. You can see in the logical core usage monitor (of which there are 8, 4 real cores), that they are all hovering about 35 to 40% when reason will no longer play back, at any buffer size, and it's own dsp meter is full.
With Pro tools, They are all above 85%, some even hit 92% *real* usage..Pro tools takes the cpu to 90+ degrees, reason keeps it cool. Reason is not effectively using the processing power of the computer. To do a comparison i tested instances of ozone 7 as well as my VI polyphony test. Reason can do 4 tracks of the Vi that pro tools does 16 of, and ozone instances spread across 32 audio tracks are 2.9x higher in PT.
So? Who cares how the other DAWs do it, they do it. I was merely suggesting that props take a look at options, like they did with PDC, for their customers.
Anyway, see you all in a year, it's been interesting.. Good luck to all. I really only came in here mentioning solutions as i was simply trying to help those with performance issues.