-
-
Notifications
You must be signed in to change notification settings - Fork 3
Expose OpenAL-defined reverb efx #62
Comments
I'm wondering that whether |
@9a24f0: oops, sorry it's in |
I'm even more confused rn... |
The user should be able to use, e.g. EFX_REVERB_PRESET_GENERIC as their reverb configuration. Is it clear to you now? |
Not yet... |
It's the Effect.reverb_properties thing. BTW notice the odd docstring of the other property (sorry didn't catch that during revision). |
Which docstring? I've read through docstrings in Effect and don't see anything strange to me... |
You have to be kidding me: Effect.chorus_properties
At this point, I think I need to clarify that I'm not your mentor, but your collaborator. You can't keep the mindset of awaiting me to tell you how to do something---you have all the resources in your hands, do research, experiment, try this try that, etc. EFXEAXREVERBPROPERTIES is a struct, and the pre-defined presets are memories. All you have to do is |
This issue is a follow-up of GH-24 (and thus GH-58).
Per private is discussion, we discovered that Effect is intended to load pre-defined effects, hence the unusual size of the parameter that the class' methods take, or at least that's true for reverb effects, which are defined in
efx-presets.h
by OpenAL (which is copied to alure for convenience purposes).@9a24f0, if you want, you can take up this issue, otherwise I can do it myself. The task is simply declare the reverbs and adjust the Effect's method to take simpler input.
The text was updated successfully, but these errors were encountered: