velipso
commented
7 years ago Here are some ideas -- I haven't tried these, this is just off the top of my head. Give these a try and see what helps and what is acceptable.
You can reduce the oversampling by changing reverb.h:
#define SF_REVERB_OF 4Try 1 to disable oversampling entirely, or 2 or 3 to just perform less oversampling.
Or you can start commenting out sections of the algorithm inside the sf_reverb_process function in reverb.c:
for (int i = 0; i < size; i++){
// early reflection
// ...
// oversample the single input into multiple outputs
// ...
// for each oversampled sample...
for (int i2 = 0; i2 < rv->oversampleL.factor; i2++){
// dc cut
// ...
// noise
// ...
// diffusion
// ...
// cross fade
// ...
// bass boost
// ...
// dampening
// ...
// update cross fade bass boost delay
// ...
//
float D1 = ...
// delay stuff...
osL[i2] = ... final oversampled output
osR[i2] = ... final oversampled output
}
// ...reverse oversample
output[i] = (sf_sample_st){ outL, outR };
}In particular, the the following regions might be good candidates for commenting out:
- dc cut
- noise
- diffusion
- cross fade
- bass boost
- dampening
- update cross fade bass boost delay
Don't be intimidated by the formulas and what they're doing. Just try things and see. Most sections don't rely on the previous sections, and everything is mostly just stepping forwards modifying the sample one stage at a time. Just follow the variables.
cuinjune
neevek
Hi, first of all Thank you so much for your amazing works. I tried using your reverb and it works well and sounds very good. But it seems like it is pretty heavy in terms of CPU usage. I wonder if you have any suggestion to reduce it's CPU usage other than reducing the channel to mono. Thanks!