Created attachment 60009 [details] pulseaudio -vvvvv log of starting pulseaudio, plugging in Sonica Theater and unplugging it When I plug in the USB Sonica Theater and Pulseaudio recognized instead of the bailing out with "usb_set_interface failed" message I get the following situation regarding volume acording to alsamixer: - left channel: 0 - right channel: 79 Expected results: Both channels at 79 or something like that. I reported this on Pulseaudio mailing list already: [pulseaudio-discuss] usb sound card: PCM has 8 channels, thats too much & cannot submit datapipe for urb 0 I think its due to: > Nov 19 21:47:05 merkaba pulseaudio[1666]: [pulseaudio] alsa-mixer.c: > Volume element PCM has 8 channels. That's too much! I can't handle > that! Nov 19 21:47:05 merkaba kernel: [ 53.498439] cannot submit > datapipe for urb 0, error -28: not enough bandwidth As Tanu Kaskinen requested I now did a pulseaudio -vvvvv log that I will attach. The sound card involved is: martin@shambhala:~> lsusb Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 003: ID 0763:2007 Midiman M-Audio Sonica Theater (lsusb-v I will attach as well). Thanks, Martin
Created attachment 60010 [details] lsusb -v with the Sonica Theater sound card attached
This is on a ThinkPad T42 with: martin@shambhala:~> apt-show-versions | egrep "(gstreamer|pulseaudio|phonon)" gstreamer0.10-alsa/wheezy uptodate 0.10.36-1 gstreamer0.10-ffmpeg/wheezy uptodate 0.10.13-2 gstreamer0.10-fluendo-mp3/wheezy uptodate 0.10.15.debian-1 gstreamer0.10-gconf/wheezy uptodate 0.10.31-1 gstreamer0.10-gnomevfs/wheezy uptodate 0.10.36-1 gstreamer0.10-nice/wheezy uptodate 0.1.1-2 gstreamer0.10-plugins-bad/wheezy uptodate 0.10.23-1 gstreamer0.10-plugins-base/wheezy uptodate 0.10.36-1 gstreamer0.10-plugins-good/wheezy uptodate 0.10.31-1 gstreamer0.10-plugins-ugly/wheezy uptodate 0.10.19-1 gstreamer0.10-pulseaudio/wheezy uptodate 0.10.31-1 gstreamer0.10-x/wheezy uptodate 0.10.36-1 libgstreamer-plugins-bad0.10-0/wheezy uptodate 0.10.23-1 libgstreamer-plugins-base0.10-0/wheezy uptodate 0.10.36-1 libgstreamer0.10-0/wheezy uptodate 0.10.36-1 libphonon4/wheezy uptodate 4:4.6.0.0-1 phonon/wheezy uptodate 4:4.6.0.0-1 phonon-backend-gstreamer/wheezy uptodate 4:4.6.0.0-1 phonon-backend-vlc/wheezy uptodate 0.5.0-1 pulseaudio/wheezy uptodate 1.1-3+b1 pulseaudio-module-x11/wheezy uptodate 1.1-3+b1 pulseaudio-utils/wheezy uptodate 1.1-3+b1 But it happens on my Amarok-T23 and my work T520 as well.
I have now for the first time see this without Pulseaudio. On the T23 after plugging back the Sonica Theater to it. But at least it doesn´t seem to show up after suspend/resume cycle or reboot. So this actually might be an ALSA issue or at least related to an ALSA issue. Can you tell more from the logs?
It might also be a bug that Phonon, its gstreamer backend or gstreamer itself shares with PulseAudio. I remember that I had a time where I never had this issue: AFAIR that was with the Xine backend of Phonon which is now deprecated and removed from Debian Testing. alsamixer -c1 sees the following channels: - PCM front: two volume controls (left/right) - this is the one relevant for me - PCM back: two volume controls - PCM middle: one volume control - PCM bass: one volume control - PCM sides: two volume controls without any additional ALSA configuration that is. I only use stereo. But officially it is a 7.1 surround card, but my receiver only handles stereo. And I correct a wrong left volume setting via alsamixer as well, thus it seems to work in ALSA.
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/369.
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.