We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
At the moment sound context is always automatically created within SoundLibrary
When context is created it is bound with sound hardware, so it always consumes resources.
There may be situations when hardware is blocked at the moment SoundLibrary being created.
My personal real cases:
autoInitialize
SoundLibrary.rebuildContext()
The text was updated successfully, but these errors were encountered:
How about adding methods PIXI.sound.destroy() & PIXI.sound.init() so that the library can be re-initialized (i.e., recreate the sound context)?
PIXI.sound.destroy()
PIXI.sound.init()
Sorry, something went wrong.
@bigtimebuddy that's good!
No branches or pull requests
Status
At the moment sound context is always automatically created within SoundLibrary
Why it is not good
When context is created it is bound with sound hardware, so it always consumes resources.
There may be situations when hardware is blocked at the moment SoundLibrary being created.
My personal real cases:
Proposal
autoInitialize
– self-explanatory.SoundLibrary.rebuildContext()
– or similar, this will provide users ability to recover from any hardware interruptions.The text was updated successfully, but these errors were encountered: