[RFC] Support for different reverb engines #1771
Replies: 2 comments
-
|
Hi, A default reverb engine shouldn't cause any distorion, ever. So my vote goes to either dattorro or Lexverb. Probably the latter given that it's faster. |
Beta Was this translation helpful? Give feedback.
-
|
I understand your point. Now that I had a few weeks hiatus, I came back to this and did a new rehearsal test. Given the current default settings, lexverb sound much less "busy" than FDN. So people will recognize there's a difference when switching to lexverb. For Datorro I'm not sure if they would, it's quite rich by default. You can also make lexverb more busy, by tweaking the reverb.width param, yet, all the reverb engines respond differently to those four parameters. @es20490446e You have shown interest in tweaking fluidsynth's reverb before. Would you be interested in trying the 2 new engines lexverb and datorro and provide feedback? |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Originally brought up on our mailing list 4 years ago, I have now implemented support for selecting different reverb engines in fluidsynth.
Check out the related PullRequest #1760 or the new reverb overview with audio samples in the API docs.
The different engines can be selected via the newly added string-setting
synth.reverb.engine, values are"fdn","free","lex","dat".Feedback on the newly added engines, their response to the four reverb settings, audio rehearsals, etc., is highly welcome! Also pls. share your thoughts about whether any of those new engines should become the default reverb engine in fluidsynth.
For those who want to give it a try, precompiled binaries are available here:
multi-reverb-supportbranch yourself.Beta Was this translation helpful? Give feedback.
All reactions