On Wed, Apr 29, 2020 at 8:25 AM Peter Humphrey <pe...@prh.myzen.co.uk>
wrote:
>
> On Wednesday, 29 April 2020 10:15:09 BST Peter Humphrey wrote:
>
> > I'm still puzzled at why creating an asound.conf enabled - phonon? - to
pick
> > the right device. Alsa is not installed here, apart from alsa-lib; no
> > applications.
>
> Well, that was a hostage to fortune. Today, after a reboot and power
cycle for
> maintenance work, I'm back to having no sound.
>
> I suspected the devices of having been detected in the wrong order, but
/proc/
> asound/cards seemed to be pointing to the right one. Besides, it seemed
> unlikely that a USB device would be found and set up before the device in
the
> display controller.
>
> Next was to blacklist all the intel* modules and reboot again. Just the
one
> card found now, the USB device. Still no sound.
>
> Have I to go the PulseAudio route after all?
>
> --
> Regards,
> Peter.

Sorry for your problems. I thought we were done with this also.

No, I don't think you should add pulseaudio. It might be a good solution in
the end, if you want to have both the USB and HDMI sound paths or you just
want more visibility when you are using multiple sound application. (If you
ever do) However if you just want USB then blacklist snd_hda_intel and you
should have only 1 sound card, the USB device which is my understanding of
where you are now.

This seems to vary from USB to USB device but does alsamixer give you any
control over the device? Possibly the volume is just off?

You can determine which card (if any in your case) is being fed audio by
watching different versions of the info file:

cat /proc/asound/card1/pcm0p/info

That path name can vary a bit with multiple cards in the system but it you
only have one it's hopefully pretty close.

When audio is not playing the last line should tell you you have a
subdevice available. When audio plays the subdevice being used becomes
unavailable. In your case I'd be interested in whether the audio is getting
to the USB device or going someplace else?

Again, sorry for your problems.

Mark

Reply via email to