The more I dig into MTurboReverb, the more questions I have. That's mostly a good thing:
1) # appears to break all expressions. For instance, how would I do the equivalent of {2*#}?
2) The manual mentions for STW module that "c" can be used for the input coefficient in that module. Is this the case for all variables in all modules? In other words, if I want to randomize only the time for an allpass diffuser, would that be a(1;c)?
3) Is there a way to limit the range of a specific variable in a specific module? For instance, is it possible to limit the range of "x" in the algorithm below to a range between 5 and 10 without globally impacting the decay coefficients for the fdn module that contains it?
fdn[ #[a(1;x) ; fl ; fh ] ]
4) What do "Up (4 sets)" and related options in the delay order sliders mean?
5) Video tut mentions a general shape to mimic natural sound decay, but visual looks like a static snapshot EQ/filter graph without frequencies or amounts listed, and description that follows is about general diffusion. Is there a particular rule of thumb if one wanted to create this sort of idealized natural decay? Would it involve both the dampening and eq/filter section?
6) In the same algorithm mentioned in Q3, if X is zero, everything is fine, but if it's any non-zero number, the CPU usage doubles. This seems like an outsized impact since it's that basic delay is the simplest part of the whole algorithm. Even tripling the complexity has less of an impact. Is there some other way of specifying a non-zero delay that does not double CPU usage?
7) I've noticed some stranger thigngs watching the CPU meter that I'm just trying to understand. The following is a prime example. Which of the two would you assume uses more CPU?
xfdn[ #[ fa ; fl ; fh ] ]
2a ; xfdn[ #[ fa ; fl ; fh ] ]
Well, since they're the exact same algorithm except that the second one adds two additional modules, I would naturally assume the second one uses more cpu. I've run this a few times, though,and actually the first uses significantly more. Very significantly. Not quite double, but more than a 50% increase. I have no idea why.
MTurboReverb: Even more questions
-
- KVRist
- Topic Starter
- 452 posts since 21 Jul, 2018
One more: I've found some algorithms I like, but they're crippling my cpu with higher complexity values, and I can't run as many variations of them as I would like. I'm wondering if they can be properly converted into impulses for use in convolution reverb. I f I do not have modulation enabled in any of the LR or ER panels, and am only running a single LR engine with:
rp [ #fa ; #fl ; #fa ; #fh ]
Then since modulation is disalbed and there are no modulating submodules, does that mean I can exactly capture this reverb in the form of an impulse response to load into a convolution reverb? Would that also properly capture the high and low pass, high and low damping, EQ, and dynamics panels? If so, is there something else I need to know about the getting the stereo imaging to correctly convey the input/output width or other settings?
I thought I remembered seeing something about how to capture an impulse response in one of the tuts or something, but not finding it now, and only info i see on "generate impulse" is that it generates one... but nothing about capturing the response. Do I need other software to capture it? A Melda process isn't coming up in searches for how to record your own IR's, and most sets of directions assume your'e recording outboard or physical space. None that I've seen mention recording from an itb algorithmic reverb unit. I'm hoping there's a way to do this that gets the timing exactly right and doesn't have to be hand cut to match the predelay settings, etc.
rp [ #fa ; #fl ; #fa ; #fh ]
Then since modulation is disalbed and there are no modulating submodules, does that mean I can exactly capture this reverb in the form of an impulse response to load into a convolution reverb? Would that also properly capture the high and low pass, high and low damping, EQ, and dynamics panels? If so, is there something else I need to know about the getting the stereo imaging to correctly convey the input/output width or other settings?
I thought I remembered seeing something about how to capture an impulse response in one of the tuts or something, but not finding it now, and only info i see on "generate impulse" is that it generates one... but nothing about capturing the response. Do I need other software to capture it? A Melda process isn't coming up in searches for how to record your own IR's, and most sets of directions assume your'e recording outboard or physical space. None that I've seen mention recording from an itb algorithmic reverb unit. I'm hoping there's a way to do this that gets the timing exactly right and doesn't have to be hand cut to match the predelay settings, etc.