You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be convenient if the AudioSource supported the ability to perform an initial setup, so that all required properties, such as the equalizerFilter and other filters, could be configured immediately after loading. This would simplify the use of the AudioSource API, as the creation and configuration of the sound could be encapsulated in a single initialization phase.
Do you mean that could be convenient to set parameters before playing and get back the SoundHandle to pass for example to band(soundHandle: newHandle)? Yes, that is a doubt I got in the other issue. I must see if it is feasible because the SoLoud C++ lib needs the handle to set a parameter and this is because you can set a parameter value to a plying sound (handle) and another one to another handle of the same AudioSource.
Better for now if you make your own AudioSource manager to play and set the desired effects, ie: final Map<String, MyAudioSourceManager> cache= {};
I'll leave this issue open for further investigation, thanks.
It would be convenient to set filters for the AudioSource during application initialization, allowing the use of preconfigured sounds later without needing to return to the configuration phase.
The band(soundHandle: newHandle) function could remain as it is -> the modification of parameters for a specific playback of an AudioSource.
Description
It would be convenient if the AudioSource supported the ability to perform an initial setup, so that all required properties, such as the equalizerFilter and other filters, could be configured immediately after loading. This would simplify the use of the AudioSource API, as the creation and configuration of the sound could be encapsulated in a single initialization phase.
Here is simple example:
Requirements
Additional Context
Add any other context or screenshots about the feature request go here.
The text was updated successfully, but these errors were encountered: