A stereo reverb effect based on reverb.lsp by Roger Dannenberg (included in the standalone version of Nyquist).
This implementation is a stereo effect, though it may also be used on mono recordings.
When applied to a 2 channel mono recording it can produce a stereo reverb which simulates a mono source in a three dimensional space.
Parameters:
Reverberation time: [0.1 to 10 seconds. Default = 2.5 seconds]
Short reverb times simulate small room reflections. Use longer reverb time to simulate larger spaces.
High frequency damping: [0 to 100%. Default = 50%]
Low values create a hard reverb suitable for producing small “bathroom” type reverbs. Higher values produce a softer reverb suitable for simulating large spaces such as Cathedrals.
Low cut filter: [0 to 1000 Hz. Default = 200 Hz]
Reduces the amount of bass frequencies in the reverb, simulating bass absorption. Helps to avoid producing a muddy effect.
Stereo Width: [0 to 100%. Default 40%]
At zero the effect processes each channel separately. Higher values introduce reflections between left and right channels.
Reverb mix proportion: [0 to 100%. Default 40%]
At zero there is no effect (Dry). At 100% only the processed reverb signal (Wet) is produced. reverb1.ny (4.65 KB)
I presume that you mean “does it sound natural?”
Give it a try and let me know. It’s a very small download and you can delete it if you don’t like it.
I’d recommend trying it with the default settings before you start twiddling. To revert back to the default settings, restart Audacity.
Could you be more specific.
The Audacity version number can be found in “Help menu > About Audacity”
How long is the selection that you are applying the effect to?
Are you applying it to one or more tracks?
Are you applying it to mono or stereo tracks?
What is the exact error message?
What settings are you using in the effect?
Do other Nyquist effects work? (for example “Cross Fade In”)
I presume that you mean that the error message was: “Nyquist did not return audio”.
I’m curious why this is not working for you.
Could you try it again, but instead of pressing the “OK” button, press the “Debug” button.
After the initial error message there will be a “debug window” which will hopefully have details of what has gone wrong.
Could you copy all of the text from the debug window and paste it into you reply.
Thanks, that explains the problem.
You are using an old version of Audacity - probably version 1.2.6 - certainly not 1.3.13
You can check the Audacity version in “Help menu > About Audacity”.
I would highly recommend that you upgrade to version 1.3.13 as it is considerably better than the old 1.2.x version.
You can get it here: http://audacityteam.org/download/
If you have already Audacity 1.3.13 installed you may need to uninstall the old 1.2 version and reinstall 1.3.13 so that your links and file associations launch the correct version.
As far as I’m aware there will not be an Audacity 1.4. The version number will be jumping up to 2.0.
As for when that will happen, I really hope it will be soon - we’ve all been waiting a very long time for it.
What’s got better in Audacity since 1.3.7?
Here’s a partial list:
Much better VST support (including a graphical interface for most effects)
New Mixer board
New Screenshot tools
New SoundFinder plug-in
New Notch filter
New Equalization curves can now be saved
Much improved ALSA, PulseAudio and Jack support (Linux)
Improved screen reader support
Improved hardware support
Faster Equalization
Improved Noise Removal
Improved Truncate Silence
Improved Click Track
Much better Nyquist support
Improved Plot Spectrum
Improved Contrast Analysis tool
Improved Compressor
Improved Export Multiple
Improved Timer Record
Improved Automatic Crash Recovery
Mute, solo, gain, pan and track height saved in projects
More audio file formats supported
Proper support for copying/pasting label-with-audio
and a lot of bug fixes.
Oh, yes, and this reverb plug-in works in 1.3.13
Regarding your solo / mute problem, it’s likely to a simple issue but it will be easier to deal with if you start a new topic. Off the top of my head, check the settings in “Edit menu > Preferences > Tracks”.
Steve, I’ve only tried it a few times, but I think you’ve got a good one! Nice, clean sound - the “troubles” I had all turned out to be due to, er, well, let’s put it this way: Feeding a bad sound into a reverb runs the risk of multiplying the badness.
One suggestion which may be beyond the capabilities of a Nyquist plug-in: Presets! One of the reasons I like using the Anwida reverb is their nice, wide-range set of presets. I used the “Instant Reverb Settings” from the GVerb Wiki page, and that really helped to show the possibilities which your easier-to-use plug-in. Is there any way at all to have a drop-down list which controls the various sliders?
Yes that’s a common “feature” of reverb. If there is a click or pop in the original track, then the click will be reverberated and sound a lot more prominent. Similarly background noise, clipping distortion and any other “badness” will be reverberated along with the music.
I was hoping that someone might ask that - you’ve landed yourself with a little job (of course you are under no obligation, but since you asked …)
Yes Nyquist plug-ins can have presets (see for example Channel Mixer) but unfortunately “user presets” are not supported. The other limitation is that when a preset is selected, there is no visual feedback to the other controls - they do not (and cannot) automatically move.
So what is possible is to have a list of “factory presets” which provide 1 click solutions, and an option to use the sliders instead of the presets. For example:
Use Sliders
Big Hall
Small Hall
Vocal Reverb 1
Vocal Reverb 2
Cathedral
…
The first setting enables the sliders. All other settings disable and override the slider settings.
It is also possible to code it so that clicking the “Debug” button rather than the “OK” button will pop up a “debug” window, showing what settings have been used (see the “Channel Mixer” effect for an example of how this works).
So all we need is for SOMEONE to suggest a list of settings. (this is where you can jump in and volunteer, but also open to anyone else that wants to help )
I’ll not be available to work on this for the next couple of weeks, but after that I can go through the suggestions and code a list of presets from the suggestions.
Suggested setting need to be in the form:
Preset Name: (preferably not more than about 14 characters as the menu box is not resizeable) Reverb time: (seconds) HF damp: (%) Low cut: (Hz) Width: (%) Mix: (%)
So an example could be:
Massive Bright 10 0 400 50 50
Sadly, this is not the first time my big mouth has gotten me into a new task! At any rate, here’s version 1p (the P is for Presets!), inspired by the code in Channel Mixer, containing the following presets:
2.5 50 200 40 20 Basic (default)
0.4 33.3 1000 15 25 Light and Bright
0.2 10 800 0 60 Small and Harsh
3 0 200 40 20 Medium Hall
6.67 80 120 50 50 Long and Mild
10 0 200 90 80 Cathedral
(Note that it’s easier to parse if you put the name at the end, rather than the beginning) The Debug button shows the settings used, just like Channel Mixer. I’m not all that enthusiastic about these presets - I welcome improvements and/or alternatives! reverb1p.ny (5.89 KB)
Congratulations with your adaptation. The only problem that I see with it is that the debug output shows the INPUT values, not the “values that were applied” (the values that are actually applied may not be the same as the input values if values outside the valid ranges are entered).
To show the actual values that were applied,
(format T "Reverb Time:~a sec ~%HF Damping:~a %~%Low cut:~a Hz ~%Width:~a %~%Mix:~a %~%n"
time damping low-cut width mix)
needs to go after the block of code that limits values to valid ranges.
I’d probably use a different (more relevant) name for the preset list, such as “presetlist”
So the new block of code would be something like:
;; Create list of values from selected preset or from the slider values
(setq presetlist
(case preset
(1 (list 2.5 50 200 40 20)) ; Basic (default)
(2 (list 0.4 33.3 1000 15 25)) ; Light and Bright
(3 (list 0.2 10 800 0 60)) ; Small and Harsh
(4 (list 3 0 200 40 20)) ; Medium Hall
(5 (list 6.67 80 120 50 50)) ; Long and Mild
(6 (list 10 0 200 90 80)) ; Cathedral
(T (list time damping low-cut width mix))))
;copy channel to vars, limit values to valid range, convert %-ages to Fractions
(setq time (max 0.1 (nth 0 presetlist)))
(setq damping (max 0 (min 1 (/ (nth 1 presetlist) 100.0))))
(setq low-cut (max 0 (min (/ *sound-srate* 2.0) (nth 2 presetlist))))
(setq width (max 0 (min 1 (/ (nth 3 presetlist) 100.0))))
(setq mix (max 0 (min 1 (/ (nth 4 presetlist) 100.0))))
; Print settings to debug window
(format T "Settings Used:~%Reverb Time:~a seconds ~%HF Damping:~a %~%Low cut:~a Hz ~%Width:~a %~%Mix:~a %~%n"
time damping low-cut width mix)
It would probably also be helpful if the debug output displayed the preset name (if used).
This could be done by setting another variable or list element to the appropriate string value.
For example:
;; Create list of values from selected preset or from the slider values
(setq presetlist
(case preset
(1 (list "Preset Basic" 2.5 50 200 40 20)) ; Basic (default)
(2 (list "Preset Light and Bright" 0.4 33.3 1000 15 25)) ; Light and Bright
...
...
(6 (list "Preset Cathedral" 10 0 200 90 80)) ; Cathedral
(T (list "Custom Settings" time damping low-cut width mix))))
Very good point… but it’s even more complicated than that! Because you’re now doing the right thing by reporting the actual values, you need to do the right thing by reporting the percentages as 0-to-100, not 0-to-1.0, right? In other words, show the user the values which go in the input boxes! Sadly, this means breaking apart the lines which I so elegantly joined together.
;; EXAMPLE
;One-Line Method: (setq mix (max 0 (min 1 (/ (nth 4 presetlist) 100.0))))
;Multi-Line Method: check for min/max
(setq mix (max 0 (min 100 (nth 4 presetlist) )))
;... then report via Debug (code not shown)
;... then convert percentage to fraction
(setq mix (/ mix 100.0))
Hmm, that’s a little confusing… At any rate, it was Report-Check-Convert, but it’s now Check-Report-Convert.
I’d probably use a different (more relevant) name for the preset list, such as “presetlist”
Good point - I got lazy, and copied the name from Channel Mixer!
It would probably also be helpful if the debug output displayed the preset name (if used).
Yes, I like this concept. I believe I have all of these ideas plugged in (so to speak), and here is the new version. (Sorry, I’m not board-savvy enough to know how to overwrite or delete previous versions.) reverb1p.ny (6.14 KB)
It still bugs me that Audacity can remember the settings a preset used, but can’t pass along those settings to the Nyquist code. E.g, apply this plug-in’s Cathedral settings, then bring up this plug-in again. The drop-down says “Cathedral,” and if you click “Debug,” it correctly shows those remembered values. However, there’s no way to use those remembered values for the sliders!
Hi!
I would like to do something regarding reverb plug-in. What was I thinking is exactly what you did (added preset), so now I need something new. Any ideas, what can be add? I would really appreciate it.
My first choice is reverb, but I am also interested in improving or adding something new in other classic effects.
Thank you.
With this reverb effect I think that we could still do an improved selection of presets.
What is needed for this is for people to use the effect on a range of different material and make their suggestions for what they would like as the presets.
It is usual for reverb effects to have presets such as:
small room (bright)
small room (warm)
Medium room (bright)
Medium room (warm)
Large room (bright)
Large room (warm)
Vocal reverb I
Vocal reverb II
Concert Hall
Cathedral
Grand Canyon
Concrete Tunnel
I think that about 12 presets is as many as we would want without the list being too long.
whbjr has written the main code part for adding the reverb presets. What we need now is the actual settings to put into that framework.
So what settings do you think produce (for example) a nice vocal reverb effect?
I like them! I have to admit, I think the difference between “Concert Hall” and “Cathedral” is pretty small (to my ears), but I definitely think you’re on the right track.
Is there any possibility to make presets work without using debug? There is no way to change controls by choosing preset?
I’m not sure I understand this - once the presets are included in the Nyquist file, you don’t need to use “debug” at all - just select them from the drop-down list. Or, you can enter new values using the sliders and/or boxes - still no need to Debug. Are you finding that things do not work without Debug?
Thank you!
Everything works fine, I just wanted to see controls change automatically on the values from preset list, but I suppose that is not possible.
I’m sending new version. Preset list is longer (10). Please check it out and let me know what you think. reverb2.ny (6.55 KB)
“Small room (warm)” does almost nothing, to my ears. That’s fascinating to me - looking at the values you used for Small/Medium/Large rooms, I see how they scale nicely, but once they’ve scaled back to this preset… nothing.
“Concert Hall” and “Cathedral” are quite similar - but, to tell you the truth, when I go back and listen to the values I gave for those two settings, they were pretty similar, too! But I have to ask - Why did you change from what I had?
I’ll be the first to admit, many of the reverb parameters are a bit mysterious to me…
I tried using reverb preset for different kinds of sound (guitar, noise, vocal, speech), and I find it good for some and bad for others. So, I changed values to make it more universal and I also tried to make it sound more natural.
Please let me know what you think.
I will, also, send folders with different types of sounds and their reverb with different preset. You can see which preset I used by the name of file. They are too big (over 2MB), so I will send them in next posts.
“Small room (warm)” does almost nothing, to my ears. That’s fascinating to me - looking at the values you used for Small/Medium/Large rooms, I see how they scale nicely, but once they’ve scaled back to this preset… nothing.
I think that is normal. Recording is usually happening in the small rooms, so the diference shouldn’t be big. But if you have to much reverb it can be reduced with small room.
“Concert Hall” and “Cathedral” are quite similar - but, to tell you the truth, when I go back and listen to the values I gave for those two settings, they were pretty similar, too! But I have to ask - Why did you change from what I had?
I think that now is better and you can see difference. reverb3.ny (6.57 KB)
(of course you are under no obligation, but since you asked …)
)