You'll soon have all sort of self proclaimed product specialist, amazing developers with no real product in their portfolio or just trolls calling you names. Asking nicely, politely or even just remotely debating also does not mean anything. The fact you have 20 years of experience with how other stuff is working outside their bubble means nothing to them.
My impression is that they are far below 16 years or something.Īs soon as you question or ask or point out some issue regarding inner working of Reason they will attack you, call you names and tell you it's your fault. Spikey some people are like completely crazy here on this forum. However, we recommend using this command sparingly or simply keeping it on the original setting. This setting is not saved between sessions.Ĭhanging this setting is a trade-off between different priorities, for example GUI performance, RAM-intensive operations, audio playback and so on-so try it and see if it improves your performance. This is done by using the following shortcuts in Reason: Users can manually override this by assigning more "audio worker" threads. Reason uses quite a strict and safe multi-core implementation that does not sacrifice stability of the program, and this is why the DSP load can differ from other DAWs. One thing you could try from Reasons perspective is to increase the number of audio worker threads and see if it makes any difference. We're currently investigating why this happens. We've had reports of the UAD VSTs taxing Reason's DSP heavily, but we also have users that can run these plugins without any major problem. I've had a response from Propellerhead on the UAD issue, I'm not sure that I understand it to be honest so I thought I'd post it here in case someone with a deeper technical knowledge can translate
As for a possible solution I outline that as well - but from this interaction I can only deduce that you‘re not actually interested in knowing what the issue is. I mean you could just as well complain that UAD doesn‘t support 64 samples properly, right? As for the other questions, I think I answered them, if you still don‘t see why Reason uses 64 samples ask somebody who can explain my explanation to you. BTW was any of this in the fine print before we upgraded and forked over our hard earned $$$ ? I'm betting no.īTW- I was able to turn the sample rate to 64 and it did get rid of the "your computer is too slow" message, but then the VST with the UAD plugin sounded like warmed-over crapola. It could be that you have "nailed" their mindset on this. So you are suggesting that anyone running a UAD audio interface needs to use another DAW/Host other than Reason because Reason's design is not now nor will ever be compatible? Wow, I'm saying now that Propellerhead might not agree with this due to the loss of revenue for them (there is a LOT of UAD interfaces out there), but that's just me. And yes, I STRONGLY recommend using UAD plugins with another DAW, a system where the audio is routed through Firewire or PCI to a DSP chip and then back into the DAW doesn‘t fit the Reason paradigm.
0 kommentar(er)
