CPU ISSUES USING REN AS A PLUG IN

Does anyone else get issues with cpu when using the ren as a plug in with daw?

I use it with Cubase for my beats, I load may be a 3 keyboards worth of drum sounds and a bass program and have Cubase doing its thing and it sometimes clicks and pops and maxes out, I go to the ren in the instruments and turn the plug in off and the cpu drops by half.

This seems strange as the ren isn't meant to use cpu is it? even if it does it should not chew so much up for such minimal usages.

I have a 6 core computer with 16gb ram so there are no computer issues. I know the ren doesn not use multicore yet which is a shame but still I find the cpu excessive.

im interested to see how others get on ?

It is only 32 bit and can only use 4 gigs of ram and access to one core. So rite now until 1.4 with 64 bit and hopefully multicore you will have the pops and clicks with that much running. This has been my biggest problem. I load 4 or more plugins into the Ren and crack snapple pop.

Yeah it's the same curse Maschine owners have to live with. They gave us 64 bit but no multicore support I can touch 24GB of RAM but only 1/8 of my CPU's are utilized.

After like 3 quality plugins are up it's like ASIO/Core audio meters hitting 40-75%. Essentially from a cpu standpoint it's doing no better than the Pentium 4 I used in 2005, which in 2013 is a little frustrating.

64 bit computing and multi core CPU's are coming up on being a decade old. I feel we've spotted software vendors enough time to get into the present.

Of course we have things like DAW track freezes and early stem bouncing, but to see 1/8th or 1/6th, or 1/4th of your computer's brain actually be of use to you is getting old.

So sadly until updates the Ren will act as though you have a single core @ whatever the max speed step value of your Pentium is and about 3.5GB of RAM max.

If you get no multicore support in 1.4 the software will use the 16GB (minus OS used RAM) but it will still see it as a single core at whatever max stepped clock speed is.

Just wanted to go full detail on what Jimmorgan79 stated.

NIKFAR wrote:I use it with Cubase for my beats, I load may be a 3 keyboards worth of drum sounds and a bass program and have Cubase doing its thing and it sometimes clicks and pops and maxes out, I go to the ren in the instruments and turn the plug in off and the cpu drops by half.

This seems strange as the ren isn't meant to use cpu is it? even if it does it should not chew so much up for such minimal usages.

Have you tried increasing the audio interface buffer size?

Lower buffer settings give less latency, but use more processing power.

Increase buffer size until clicks and pops go away.

Not strange that the MPC Software uses the CPU, as it is software, which runs on the computer CPU.

Metatron72 wrote:64 bit computing and multi core CPU's are coming up on being a decade old. I feel we've spotted software vendors enough time to get into the present.

I find it bizarre that the MPC Software was not coded at 64 bit and multi-processor right from the start.

SimonInAustralia wrote:I find it bizarre that the MPC Software was not coded at 64 bit and multi-processir right from the start.

Yeah if I recall the NAMM 2012 video implied it would be 64 bit at launch. Being that they were starting from scratch I'm not sure why they dropped 32 bit only at launch, aside from the clock ran out.

It's not particularly harder to code from the ground up compiling 64 bit applications, it's actually building an app strictly 32 bit first and then re-coding it at 64 bit that's the hard thing. (See Maschine's long delay for 64 bit support, Ableton dragging their feet for years and so on).

The re-coding difficulty lies in the larger data chunks of data 64 bit "bites" off operationally and the larger memory address spaces that this all goes down in with your RAM. Why we see a minority of 64 bit apps with the still hindering lack of multi core support is beyond me.

On the other hand you have firms like Cakewalk who have been fully immersed in 64 bit since 2005 when XP Pro was the only 64 bit option.

So I assume they just didn't have time to finish both 32 and 64 bit revs and just dropped the 32 bit one to get out the gate in the release window that they painted themselves into a corner on. They must have done the overall architecture in a way that 64 bit support can be added without having to re-write the whole app. (Or a re-compiling that is near the level of a full re-write).

Resample Sample ... Thats the MPC made for.

SimonInAustralia wrote:

NIKFAR wrote:I use it with Cubase for my beats, I load may be a 3 keyboards worth of drum sounds and a bass program and have Cubase doing its thing and it sometimes clicks and pops and maxes out, I go to the ren in the instruments and turn the plug in off and the cpu drops by half.

This seems strange as the ren isn't meant to use cpu is it? even if it does it should not chew so much up for such minimal usages.

Have you tried increasing the audio interface buffer size?

Lower buffer settings give less latency, but use more processing power.

Increase buffer size until clicks and pops go away.

Not strange that the MPC Software uses the CPU, as it is software, which runs on the computer CPU.

Metatron72 wrote:64 bit computing and multi core CPU's are coming up on being a decade old. I feel we've spotted software vendors enough time to get into the present.

I find it bizarre that the MPC Software was not coded at 64 bit and multi-processor right from the start.

hi yeah I did all these with no really change, I have a really powerfull computer and it seemed to to be as good as my earlier quad with much less ram which made me concerned.

So after lots of digging I lead to me check all my drivers on my computer. I used a program called dpc latency checker which shows any spikes in your cpu and if there are any you know there is a driver issue. I had loads of red spikes. so through going through all my drivers and disabling them I found that my asus wireless pcie card was causing huge cpu spikes. I disabled it and now ive got huge amounts of cpu left with no issues.

I still await being able to use multicore but im happy now for now.

Yeah DPC checker is handy as hell for PC users. Fist thing I install on any off the shelf PC I have to deal with.

Glad you got the spikes down with the one driver's procedure calls, but if you need to trim down the spikes even more I highly recommend the tweak charts on this page -

http://www.blackviper.com/service-confi ... gurations/

The way the charts are written it's easy to determine what services your particular setup can bear to have changed. And there's stuff in there that is just smart for a Windows user in general.

For example disable "Remote Desktop", it's only for a remote person or tech support to take over your desktop to help you, think old Dell support and all that. In most cases you're gonna do that once and likely never so why waste clock cycles and letting it poll your CPU for nothing? Plus it's a potential backdoor exploit for malware.

So I use the chart to determine which ones I need for my usage and get back more clock cycles for DAW stuff.

One other thing, you might want to manually update all your drivers. It's a pain to go to all the sites but often times especially in network card driver conflict, the newer drivers may very well have fixed it. The built in driver search in Windows does not work very well, so I suggest going to sites and doing manual updates if newer revs of drivers are available.