Matthias Geier

This has been fixed in #834.

Thanks for reporting this! > the time is literally `0.0` which is `falsy` [breaking this check](https://github.com/spatialaudio/python-sounddevice/blob/master/sounddevice.py#L1077). This is intentional, because [the docs](https://www.portaudio.com/docs/v19-doxydocs/portaudio_8h.html#a2b3fb60e6949f37f7f134105ff425749) state: "The stream's current time in seconds, or...

> This seems to work but PortAudio literature states that opening multiple OutputStreams is not a good idea. Yes, this is normally not recommended. I would try to use a...

Thanks for reporting this. I don't have access to a Windows system, so I tried it with GitHub Actions (https://github.com/mgeier/python-sounddevice/actions/runs/15259522483), but I couldn't reproduce the problem. #61, #166 might be...

Thanks for bringing this up! There is hardly any documentation for "blocking" streams: https://python-sounddevice.readthedocs.io/en/0.5.1/usage.html#blocking-read-write-streams That's because I have never used them and I don't even know whether the blocking behavior...

> Are you willing to accept PRs on this issue? Yes, definitely!

For reference, this is the same question on SO: https://stackoverflow.com/q/78146705/ There is some talk about threading vs. `asyncio` ... I would like to point out that when you are using...

> Could you explain how the sensor-handling code could be moved to the `with stream` block? This is totally untested, but I thought about something like this: ```python with stream:...

> So you said the callback is done in another thread, so that means I can't use `asyncio.queue`? Will there not be a problem with using a normal queue if...

You will never get the sensor and the sound card synchronized (unless you have some kind of hardware-level synchronization like word clock, which I assume you don't), so you should...