Created attachment 71800 [details] PA log I was hoping to update PA to 3.0 in Guacamayo (guacamayo-project.org), but there is some issue in interacting with USB speakers. I am attaching a log from the point when the QSB speakers are plugged in, but I suspect the problem is at/around linne 416: pulseaudio[1067]: [pulseaudio] module-device-restore.c: Could not set format on sink alsa_output.usb-SoundScience-TRLQ_QSB-00-QSB.analog-stereo This issue does not exist with PA 1.1 or 2.1 (though 2.1 is unusable because of bug 46350).
The log suggests the device was detected. I still need to figure out where the error you mention comes from, but it does not appear to be critical. What specific issue are you seeing?
The USB device should become the default device (I have the switch-on-connect module loaded), but the playback continues into the built-in alsa.
(would be good if you could back up ~/.pulse before further testing, assuming you've been using the same home directory since 1.x) So the first question is - does playback to the USB device work? If yes, does that mean your problem is that it is not being remembered as the default device when migrating from 1.1 to 3.0?
(In reply to comment #3) > (would be good if you could back up ~/.pulse before further testing, > assuming you've been using the same home directory since 1.x) This is a freshly built image on a media appliance, so there are no 1.x artefacts left behind; however, with 3.0, there is no .pulse directory at all (there is one on an image with PA 1.1) PA is started as a daemon, 'pulseaudio --start -D --exit-idle-time=-1' > So the first question is - does playback to the USB device work? If yes, > does that mean your problem is that it is not being remembered as the > default device when migrating from 1.1 to 3.0? If I start gst playback and do 'pactl list sinks' I see two devices: #0 is an onboard alsa, #1 are the usb speakers, but *both* of these devices say they are suspended, even though the sound is coming out of the #0 device. Is there some way to switch the default device using pactl (or to disable a device completely)?
Okay, if you've got a fresh setup, my backup instructions don't matter (and your .pulse is probably now in ~/.config/pulse). Next, if you could attach the output of 'pactl list' when you are playing your stream, that would be useful. And finally, you can set the default device using 'pacmd set-default-sink' and you can effectively "disable" an ALSA device by setting its card profile to 'off' (pacmd set-card-profile).
Created attachment 71860 [details] pactl list dump while playing The dump of 'pactl list' during playback is attached. If I disable the on board alsa by setting it's profile to off then there is no sound at all.
(In reply to comment #6) > Created attachment 71860 [details] > pactl list dump while playing > > The dump of 'pactl list' during playback is attached. If I disable the on > board alsa by setting it's profile to off then there is no sound at all. That's because you'll see your USB device is also set to the off profile. It should've defaulted to the 'output:analog-stereo' profile. You can switch it back with pacmd again.
(In reply to comment #7) > That's because you'll see your USB device is also set to the off profile. Not it is not: Active Profile: output:analog-stereo
erf, my bad. BTW, you say that something is playing during the pactl list? There is no corresponding Sink Input entry there. Perhaps something's going directly out via ALSA?
Yes, I think you might be right; has anything changed between 2.x and 3.x that would impact on gstreamer (not) talking to PA?
Should not be. What's the output of: gst-launch-0.10 audiotestsrc ! pulsesink --gst-debug=pulse*:3 (1.0 instead of 0.10 if you're using gst 1.0, of course)
Thanks Arun. I have tracked it down to gst-plugins-good not rebuilding properly (due to same stale la files), so got that working. However, I am hitting the long standing bug 46350, which makes 3.0 unusable, so will have to keep Guacamayo on 1.1 until that is resolved.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.