Login

Nebula 3 Reverb weird behaviour with reaper

Tips & tricks, working results, technical support

Nebula 3 Reverb weird behaviour with reaper

Postby machineareves » Fri Jul 23, 2010 10:46 am

Hi,

I was trying to know how many instances of nebula (1.3.412) I could load on my system (Win 7 64, intel Q8400, 4gb Ram) and I noticed some weird behaviour :

With reaper (3.651) I can load about 30 instances of nebula 3 before hearing any crackles on audio but if I use nebula 3 reverb I can't go above 15 (with the same program loaded of course). The cpu meter on the windows task manager is around 40%, the total cpu meter in Reaper shows 40% to but the FX cpu meter shows 100%.

With Cubase 5.5 I can load about 26 with either Nebula or Nebula reverb without any problem (wich is also not really normal as I thought nebula reverb was lighter on the cpu).

I tryed to use nebula free to see if core II would solve the problem but it does the same thing.
I also tryed with Reaper x64 : the same

Do somebody have an explanation for this behaviour ?
machineareves
User Level 0
User Level 0
 
Posts: 2
Joined: Thu Apr 08, 2010 10:23 am

Re: Nebula 3 Reverb weird behaviour with reaper

Postby fuseburn » Fri Jul 23, 2010 3:08 pm

Increase your anticipative FX buffer size in Reaper. Mine's around 1500 ms (default 200 ms)
User avatar
fuseburn
User Level X
User Level X
 
Posts: 133
Joined: Mon Apr 05, 2010 6:19 pm

Re: Nebula 3 Reverb weird behaviour with reaper

Postby giancarlo » Fri Jul 23, 2010 3:09 pm

are you using nebula 32 bits or nebula 64 bits?
Reverb version is ligher, but the length parameter for FFT kernels is settled to an higher value, which means higher quality but higher cpu load. Check that you are running in GHOST mode.
User avatar
giancarlo
Founder
Founder
 
Posts: 9160
Joined: Mon Sep 21, 2009 10:40 pm
Location: Italy

Re: Nebula 3 Reverb weird behaviour with reaper

Postby machineareves » Sat Jul 24, 2010 11:09 am

Thank you Giancarlo, you solved my problem.
I turned the GHOST mode on and everything went back in line (30 Nebula Reverb instances).
Thank you Fuseburn for trying to help but changing the anticipative FX buffer from 200ms to 1500ms didn't change anything.
machineareves
User Level 0
User Level 0
 
Posts: 2
Joined: Thu Apr 08, 2010 10:23 am


Return to Working with Nebula

Who is online

Users browsing this forum: No registered users and 5 guests