I have a icecast2/darkice server set up to stream input on the line-in on the sound card. So the stream is playing whatever is coming into the line-in on the sound card. The problem is that if I start darkice before I log in, I can't get any audio. The darkice stream works fine, I get no sound on my computer speakers. So then I can't log in at the console because orca cannot speak. Even if I log in remotely, I can't play sound files. There is no error message, I just get nothing. If I kill darkice, then everything returns to normal. I can start orca at the login screen and log in. Then if I restart darkice, everything continues to work. In otherwords, if I start darkice before accessing the sound device as a regular user, darkice seems to take over the entire device, even output. If I access the sound card before I start darkice, everything is fine. It must be some kind of permissions problem but darned if I can figure out what. I'm running Ubuntu noble/24.04.
On 27/11/24 12:50, John G. Heim via Blind-sysadmins wrote:
In otherwords, if I start darkice before accessing the sound device as a regular user, darkice seems to take over the entire device, even output. If I access the sound card before I start darkice, everything is fine.
Assuming that Pipewire is configured, as it probably is by default, then it typically runs within your user session. If you're running an audio application before you log in, it may claim the audio device before Pipewire has a chance to start as part of your login session and to take control of the sound device. You may need to look at Pipewire configurations. This isn't an area that I'm familiar with, so I can't offer specifics.
participants (2)
-
Jason J.G. White
-
John G. Heim