-
Notifications
You must be signed in to change notification settings - Fork 90
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
Issues with running Linux ALSA stream #72
Comments
@niclashoyer I have a suspicion that the non-blocking stream also underruns at first, however in the non-blocking example portaudio represents this as a To fix this I might see if we can also map the overflow/underflow return value to an Option (like in the non-blocking example), because it's not really an error - it should probably be expected in cpu intensive situations, so it could be nicer for the user to optionally handle it rather than having to match on the Err variant for it. |
|
Ahhh flip! I think we're close though... Could you check the Thanks for the help! I'm busy with conrod atm but will be back to help on this tomorrow 👍 |
It seems to be Conrod looks really nice. I'd like to check out piston really soon, it looks very interesting. |
Unfortunately #77 does not fix the blocking example for me, maybe we should reopen this. Example output:
On about 1 in 5 runs I get a different message, maybe this is helpful:
Full logs in this gist. |
I'm still learning a lot too! Thanks so much for testing, it's been a huge help :) Take 3: Hopefully #78 is the right fix! |
@mitchmindtree yes the blocking example is now working 👍 |
Woohoo! 🎉 |
@niclashoyer has been running into issues with rust-portaudio on Linux. The blocking stream immediately underruns and breaks from the loop, while the non-blocking stream shows some warning messages however seems to run fine. Perhaps we are missing some platform specific ALSA implementation? @jeremyletang any ideas? Do you test on linux?
blocking.rs output
non_blocking.rs output
Original issue was raised here.
The text was updated successfully, but these errors were encountered: