You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"PortAudio is not supported on this operating system/architecture"
"Sound library: Didn't find any output devices with the default driver, trying PortAudio..."
pavucontrol works fine, but processing never appears as an application.
Update: Running the portable version instead of the snap doesn't error.
Luke2642
changed the title
Sound / Audio doesn't work in Processing.org on Ubuntu 22.04
Sound / Audio doesn't work in Processing 4.4.1 using snap on Ubuntu 22.04
May 7, 2025
Uh oh!
There was an error while loading. Please reload this page.
Most appropriate sub-area of Processing 4?
Build process, IO
Processing version
4.4.1
Operating system
Ubuntu 22.04
Steps to reproduce this
I'm no expert but I think I've found why the sound won't work, despite pulseaudio, alsa and lib java audio etc all working perfectly on my computer.
In the terminal, run "snap connections processing":
Interface Plug Slot Notes
desktop processing:desktop :desktop -
desktop-legacy processing:desktop-legacy :desktop-legacy -
home processing:home :home -
network processing:network :network -
opengl processing:opengl :opengl -
wayland processing:wayland :wayland -
x11 processing:x11 :x11 -
There is nothing for audio. Thus, when you add the sound library, it can't escape the snap environment and always fails to play or detect the mic.
snippet
Additional context
"PortAudio is not supported on this operating system/architecture"
"Sound library: Didn't find any output devices with the default driver, trying PortAudio..."
pavucontrol works fine, but processing never appears as an application.
During the debug process I've also run:
sudo apt install portaudio19-dev libportaudio2 libasound-dev
sudo apt install libpulse-java
sudo apt install pulseaudio-utils
pulseaudio --start
And restarted etc, no change.
Would you like to work on the issue?
no
The text was updated successfully, but these errors were encountered: