
Luckly I caught a young sales assistant on a busy day and got a refund. I just bought aother 8 gig of ram before christmas but that made no difference what so ever.

You say worst case senario buy a cpu what is the best case senario! I dont want to but new kit that doesnt guarantee a fix for me. The only results I can analyze show max 30 percent cpu and max 70 percent ram usage but as I read its down to how fast your chip can do the maths and if it cant possibly do the maths then it wont even try to calculate the sum hence no display of overused cpu power.
Reason audio loopback software#
What I think might help is a decent piece of software that shows where my system is lacking. The price of some seriously good advice may save you a pile of cash spent on a sub-optimal system that doesn't really fit your specific requirements.Ĭhrischrischris wrote:Yeah I had one of them intel chips two years ago but it blew up on me! I find the fx is much more powerful than that one anyways. The internal DSP cards are great on a PC but you are back to contolling them much like any other VST, that is either via Rewire or a convoluted audio loopback setup if you want to use the plug-ins alongside Reason.īasically if you are planning to spend that kind of money on a PC based solution I'd suggest talking your requirements through with a specialist builder like ADK or booking a consultation with someone like Jim Roseberry at Purrrfect Audio.
Reason audio loopback drivers#
UAD Apollo Duo and Solo drivers don't exist for Windows even if you have a Thunderbolt equipped PC.įor the Apollo and Apollo 16 cards check out the support page before thinking about a UAD interface on a PC especially with regard to a qualified firewire add-on card. ProTools supports AAX plugins which contain the code for both the DSP system and the CPU and thus can switch them between the DSP box and the CPU.

The plugins are programmed and compiled for an Intel CPU and simply won't run on the DSP hardware. Normen wrote:You can't just plug in a DSP processor to a computer and make it run the native plugins, that doesn't work with any system. But of course you can measure and compensate that with the VMG-01 RE
Reason audio loopback full#
You can also directly record the processed signal, just as if you'd have a real compressor on the analog side before your audio interface input.įor using Apollo in Reason it would work pretty much exactly as it would if you'd connect real hardware to your multichannel audio interfaces inputs and outputs, so you always get the full roundtrip latency for this solution. ProTools supports AAX plugins which contain the code for both the DSP system and the CPU and thus can switch them between the DSP box and the CPU.Īnd yes, with a DSP based system like the Apollo you can listen to the input latency-free, similar to your audio cards input mixer but you can put the (DSP-based) plugins of the DSP system on the monitor mix without adding any latency.

You can't just plug in a DSP processor to a computer and make it run the native plugins, that doesn't work with any system.
