Re: [Alsa-user] Class-2 compliant USB device (RODECaster Pro) unable to retrieve number of sample rates

2020-12-17 Thread Stuart Longland 

On 27/6/20 1:39 am, Ralf Mardorf wrote:

On Fri, 26 Jun 2020 14:02:37 +0100, James Conroy-Finn wrote:

pulseaudio

Hi,

I can't comment on the RØDECaste Pro. However, at least for
troubleshooting consider to disable or remove pulseaudio.


Whilst I too, have a love-hate relationship with PulseAudio, I think we 
can do better support than simply `grep -qiF pulseaudio && echo "disable 
or remove pulseaudio"`.


With the exception of Bluetooth audio devices (which this is not), 
PulseAudio appears to use ALSA as its "back-end" to talk to local audio 
hardware.



On 26/6/20 11:02 pm, James Conroy-Finn wrote:

 kernel: hid-generic 0003:19F7:0011.0009: hiddev1,hidraw7: USB HID v1.10 
Device [RODE Microphones RODECaster Pro] on usb-:00:14.0-9.4.2/input0
 kernel: usb 2-9.4.2: parse_audio_format_rates_v2v3(): unable to retrieve 
number of sample rates (clock 1)
 kernel: usb 2-9.4.2: parse_audio_format_rates_v2v3(): unable to retrieve 
number of sample rates (clock 1)


Unless those messages are generated by `pulseaudio.ko` I think we can 
safely conclude these are in fact, ALSA kernel driver messages.

--
Stuart Longland (aka Redhatter, VK4MSL)

I haven't lost my mind...
  ...it's backed up on a tape somewhere.


___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Re: [Alsa-user] Class-2 compliant USB device (RODECaster Pro) unable to retrieve number of sample rates

2020-06-26 Thread Ralf Mardorf 
On Fri, 26 Jun 2020 14:02:37 +0100, James Conroy-Finn wrote:
>pulseaudio

Hi,

I can't comment on the RØDECaste Pro. However, at least for
troubleshooting consider to disable or remove pulseaudio.
Test with plain ALSA and/or the jack soundserver.

All my Linux machines are using plain ALSA or jack on demand.
I install empty dummy pulseaudio packages, to fulfil potential
dependencies against the pulseaudio package. For my needs pulseaudio
makes no sense at all.

I don't know how good or bad pulseaudio nowadays is, but if an issue
happens and it is involved, a troubleshooting step should be to get
rid of pulseaudio, to see if the issue remains.

Just that pulseaudio output mentions an ALSA issue, not necessarily
means that pulseaudio isn't the actual culprit.

Regards,
Ralf


___
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user