-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
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
Simple non-async WavReader #19
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a request for a simple WavReader that does not load Async.
It's related to the same problem as this issue:
#18
The existing WavReader does load Async but it doesn't tell you when it's finished.
So you can't know it's safe to do things downstream like init the buffer or play.
The purpose of a simple non-async WavReader would be to that you can safely put it in your own Async or Reactive context knowing it will block that context until it completes the read.
Then you can keep it in a reactive stream for further processing. (Which may not necessarily be playing the audio, maybe you want to do some other data processing like peak analysis)
The existing AudioPlayer already covers the simple usecase of playing audio.
I think WavReader & buffer system should enable advanced use like reactive.
The text was updated successfully, but these errors were encountered: