This Github has a project that attempts to install sounddevice and use it within Python3
The Dockerfile and other associated files suffice to create an image that downloads into my Rpi.
The goal is to be able to import sounddevice into Python3 and execute various commands.
After much fiddling, the image loads and if I start Python3 from the Balena-cloud terminal window, the Rpi runs sounddevice examples. Great.
But, if I try to directly execute a python3 script via python3 playFile.py or ./playFile the Rpi fails play the wav file (via the Rpi output jack).
My question is: Why should it run if the code is pasted into python3 via the balena-cloud terminal window but not run when invoked via python3 followed by the script name or ./ followed by the script name.
Hi @val the issue you have here is that sd.play() allows script execution to continue whilst the audio plays in the background.
From the sound device playback docs ( Usage — python-sounddevice, version 0.3.14 ):
This function returns immediately but continues playing the audio signal in the background.
In your application, when you run the script file, the python interpreter runs the sd.play() method, but then continues executing, gets to the end of the file and exits the process. On the other hand, when you copy and paste your code into the python3 REPL, the process doesn’t exit and you stay in the active python process, so the audio continues to play.
You can use the sd.wait() method to block the python interpreter until playback is finished.
I sent a PR to your GitHub repository showing how this would work in your application Wait for audio to finish playing before exiting script by LucianBuzzo · Pull Request #1 · veirs/sounddevice · GitHub
I tried this locally on a test device and it worked great!
Let me know if this fixes your issue