michael.edwards

Hello, I'm using gigaverb~ 1.0test5 in Max/MSP 4.6.3 on a MacBook. I 

have a pretty heavy patch that's been working fine with your external 

for a while now (many thanks for it by the way). I develop on a PC 

(using gigaverb~ 1.0test3) but sometimes perform on a Mac--I like to 

I changed reverb parameters recently and this had no effect on the PC 

but when I switched over to the Mac my CPU started hitting 100% after a 

while of no sound output. It was a real head-scratcher because I'd 

changed quite a lot of the patch on the PC so couldn't isolate the 

problem on the Mac for quite a while. I'm now pretty certain that it's 

the new gigaverb~ parameters that are causing the CPU overload. To 

reiterate, it only happens when the patch isn't outputting any sound 

roomsize 15, damping 0.18, revtime 1.24, bandwidth 0.95, early -15, tail 

But these parameters cause the CPU overload:

roomsize 25, damping 0.68, revtime 2, bandwidth 0.4, early -15, tail 

I can work around it of course, but just thought you might like to 

know--could be a bug, or perhaps I'm missing something?

All the best and thanks again for the external,

Michael Edwards Tel. Office: (+44) (0)131 650 2431

Music Technology Email: michael.edwards@ed.ac.uk

MSc in Digital Composition and Performance

Hello, I'm using gigaverb~ 1.0test5 in Max/MSP 4.6.3 on a MacBook.  I 
have a pretty heavy patch that's been working fine with your external 
for a while now (many thanks for it by the way).  I develop on a PC 
(using gigaverb~ 1.0test3) but sometimes perform on a Mac--I like to 
confuse the hardware snobs ;)

I changed reverb parameters recently and this had no effect on the PC 
but when I switched over to the Mac my CPU started hitting 100% after a 
while of no sound output.  It was a real head-scratcher because I'd 
changed quite a lot of the patch on the PC so couldn't isolate the 
problem on the Mac for quite a while.  I'm now pretty certain that it's 
the new gigaverb~ parameters that are causing the CPU overload.  To 
reiterate, it only happens when the patch isn't outputting any sound 
(but the dac is on of course).

roomsize 15, damping 0.18, revtime 1.24, bandwidth 0.95, early -15, tail 
-17, dry -7

roomsize 25, damping 0.68, revtime 2, bandwidth 0.4, early -15, tail 
-11, dry -25

I can work around it of course, but just thought you might like to 
know--could be a bug, or perhaps I'm missing something?

Michael Edwards                  Tel. Office: (+44) (0)131 650 2431
Music Technology                 Email: michael.edwards@ed.ac.uk
The University of Edinburgh
Programme Director
MSc in Digital Composition and Performance
http://www.ace.ed.ac.uk/Postgraduate/dcp
http://uofe.michael-edwards.org/

gigaverb-cpu-overload

I too am a grateful gigaverb~ fan - I've used it on several performances, G4 Powerbook (2004) with no problems, Max 4.5 and 4.6. Right now I'm running it on Max 5.0.1, with a 2008 MacBook Pro. I've left the audio on with no sound output to test your problem, and the CPU is staying within the normal range for this patch (actually, it's more efficient now than in my previous setup).

My settings move around during performance, but I start with roomsize 150, damping .4, revtime 10, bandwidth .5, early -26, tail -20, dry -.5. I've left your settings on for about half an hour, and the CPU is still happy.

gigaverb~ cpu overload