-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Stopping playback of source or sink connected to audiofilters.Filter
causes device to become unresponsive
#9778
Comments
audiodelays.Echo
with multiple audio effectsaudiodelays.Echo
causes device to become unresponsive
I've just tested this scenario but with using two |
audiodelays.Echo
causes device to become unresponsiveaudiofilters.Filter
causes device to become unresponsive
If you haven't found it yet, this sounds like get_buffer is still being called and not finding a sample so calling random memory. |
I've closely compared import audiodelays
import audiofilters
properties = {
"sample_rate": 48000,
"bits_per_sample": 16,
"channel_count": 2,
}
effect1 = audiofilters.Filter(**properties)
effect2 = audiodelays.Echo(**properties)
effect2.play(effect1) |
I'm not at my computer at the moment so I won't be able to push a PR out until this evening, but I believe I found the issue. The I'm not sure why exactly this causes the odd audio playback. I'll make sure to test the results when I am able. |
Fix has been implemented in #9787. The solution was rather simple and all examples now function correctly. |
CircuitPython version
Code/REPL
Behavior
The echo effect is heard for a moment at around half speed, then output audio suffers terrible distortion and the device requires hard reset. USB device (/dev/ttyACM0) is not recognized.
Description
No response
Additional information
I've tested this in a slightly different scenario where
audiodelays.Echo
precedesaudiofilters.Filter
, and this error does not happen ifaudiodelays.Echo
is stopped first. Ifaudiofilters.Filter
is stopped, the error described above occurs.The text was updated successfully, but these errors were encountered: