[pulseaudio-discuss] No audio output from Zoom
I have a pair of Panasonic RT-HP 161 headphones. They're plugged in the rear panel audio out jack on the desktop running Slackware64-14.2. The headphones produce stereo sound from web-hosted applications: e.g., YouTube and news site videos. But, using either the zoom-linux desktop application or a zoom test meeting on the web browser there's no audio output. pavucontrol shows the speakers as line out, but the headphone as unplugged. Advice needed. Rich
Re: [pulseaudio-discuss] Need help resolving audio recording/playback issues
On Wed, 16 Feb 2022, Sean Greenslade wrote: - The preamp gain knob on the Scarlett is set high enough. Dynamic mics can have pretty weak signals. On mine, I need to pretty much max out the preamp to get signals strong enough to light up the green ring. Sean, I turned the Scarlett Solo mic gain to maximum and the pre-amp green ring flickers when I speak. So this part's resolved; I must have turned down the gain without noticing. With audio-recorder started pavucontrol shows it present in the Recording tab, but the VU bar doesn't move when I speak into the microphone. Accepting that pulse audio is not the issue and that what I don't know about audio on linux would fill Wikipedia, could you suggest where I look to find why audio-recorder saves an 86 Kb .mp3 file but pavucontrol doesn't show my voice being recorded since nothing comes from the speakers when mplayer processes that file? Is it hardware? Software? Configuration? A missing component? I've no idea where to start diagnosing the problem. Thanks again, Rich
Re: [pulseaudio-discuss] Need help resolving audio recording/playback issues
On Wed, 16 Feb 2022, Sean Greenslade wrote: On the Scarlett USB interfaces, the green/red LED ring around the input gain knob is driven directly by the hardware. Pulseaudio has no influence over this. So if you're not seeing any signal there, the issue is in hardware. Make sure: - The XLR cable is OK and fully seated into the plugs on both ends. - The switch on the side of the mic is on. It needs to be on to feed output to the XLR jack. - The preamp gain knob on the Scarlett is set high enough. Dynamic mics can have pretty weak signals. On mine, I need to pretty much max out the preamp to get signals strong enough to light up the green ring. Sean, Thanks very much. I probably had the gain too low. Stay well, Rich
[pulseaudio-discuss] Need help resolving audio recording/playback issues
Something(s) changed here and I don't know enough about linux audio to fix the problems. Environment: Slackware64-14.2. Audio-Technica AT2005USB, Scarlett Solo Gen 3. The latter two are connected by an XLR cable. All worked fine until a few days ago. Now pavucontrol Configuration tab sees the Scarlett Solo USB connected to the desktop, and the Input Devices tab shows three options: Front Microphone (unplugged, although that's where the Scarlett Solo is connected), Rear Microphone (plugged in, and the only one to show the vu bar responding to noise as well as flickering when there's no microphone connected or turned on), and Line In (unplugged). Earlier today, using audio-recorder (version 2.2.3) and connecting the Audio-Technica AT2005USB with the USB cable I successfully made a test voice recording that mplayer sent to the Creative Pebble speakers. I could not repeat this later in the morning. While audio-recorder wrote a 327K file, aplay, mplayer, and vlc don't produce what I recorded in the .mp3 file. Using a new Cable Masters XLR cable I'm still not seeing the Scarlett Solo input LED ring flicker when I speak. The AT2005 microphone does work ... at least it did earlier today with the USB cable. As an aside, audacity is no longer working for me. When I press the red 'record' button the status bar shows 'Recording Paused' and I have not found how to unpause it on an audacity menu or my web searches. That's why I'm using audio-recorder. I need to produce podcasts and video tutorials to market my professional services consultancy so I appreciate all the help I can get here to understand what failed and learn how to fix everything so it Just Works ... as it did in the past. Thanks in advance, Rich
Re: [pulseaudio-discuss] No audio output; same setup worked before [RESOLVED]
On Mon, 15 Feb 2021, Sean Greenslade wrote: I'm not familiar with vokoscreenNG, but from a quick look at its github page, it seems like it has native pulseaudio support. I would suggest going through its settings and verifying that the correct audio input device is selected before starting a recording. You can also verify that it is indeed respecting your source selection by checking the "Recording" tab of pavucontrol during a recording session. Sean, Thank you. It's likely that I missed one or more of those steps. Today I won't. Regards, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] No audio output; same setup worked before [RESOLVED]
On Mon, 15 Feb 2021, Sean Greenslade wrote: For the record, I would be very surprised if your version of pavucontrol had anything to do with these issues. In your other email, you show this output from your pacat record attempt: Sean, I didn't think it did, but I saw nothing else that changed. $ pacat -v -r --file-format=wav /tmp/sounds.wav Opening a recording stream with sample specification 's16le 2ch 44100Hz' and channel map 'front-left,front-right'. Connection established. Stream successfully created. Buffer metrics: maxlength=4194304, fragsize=352800 Using sample spec 's16le 2ch 44100Hz', channel map 'front-left,front-right'. Connected to device alsa_output.pci-_0a_00.3.analog-stereo.monitor (index: 0, suspended: no). Notice the last line, where it reports the source it has attached to is the alsa output monitor source. This was recording the _output_ of your built-in sound card, hence why you heard nothing upon playback. I didn't know how to interpret that line. Now I do. Pacat / parec will respect the fallback selection as the default recording source if you don't supply one explicitly, so that will most likely be what made the difference between your tests. Ah! There is no sound.wav here in any partition or directory. I was using vokoscreenNG to record sound while the webcam captured me speaking. When I played the video with vlc there was no sound. But, ffprobe showed the output file had both video and audio streams. Have you a suggestion how I can ensure my videos also produce audio output when played and I've specified a .mp4 output for the recording? Thanks again, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] No audio output; same setup worked before [RESOLVED]
On Sun, 14 Feb 2021, Rich Shepard wrote: Aha! I found the problem, at least with audacity. Audacity has a drop down combobox with output options. The default is, "HD-Audio Generic: ALC1220 digital (HW:1,1)" and there's no speaker output. And, when I change the output to "HD-Audio Generic: ALC1220 digital (HW:1,0)" the same test recoding is heard from the speakers. Sean, et al.: Now I've resolved the issue with direct recording and playback using pacat. Two things changed since when I logged out yesterday: 1) I had downgraded pavucontrol from version 4.0 (which is in Slackware-current) to version 3.0 (which is the default in Slackware-14.2) and 2) I logged off the desktop and logged back in this morning. I created a recording: $ pacat -v -r --file-format=wav direct-pacat-recording.wav Opening a recording stream with sample specification 's16le 2ch 44100Hz' and channel map 'front-left,front-right'. Connection established. Stream successfully created. Buffer metrics: maxlength=4194304, fragsize=352800 Using sample spec 's16le 2ch 44100Hz', channel map 'front-left,front-right'. Connected to device alsa_input.usb-Focusrite_Scarlett_Solo_USB_Y7R5BX40493137-00.analog-stereo (index: 25, suspended: no). and played it back to the external speakers: $ pacat -v -p --file-format=wav direct-pacat-recording.wav Opening a playback stream with sample specification 's16le 2ch 44100Hz' and channel map 'front-left,front-right'. Connection established. Stream successfully created. Buffer metrics: maxlength=4194304, tlength=352800, prebuf=349276, minreq=3528 Using sample spec 's16le 2ch 44100Hz', channel map 'front-left,front-right'. Connected to device alsa_output.pci-_0a_00.3.analog-stereo (index: 20, suspended: no). Stream started. Stream underrun. Playback stream drained.y: 100160 usec. Draining connection to server. (when I stopped it) So there must be something (perhaps in pulseaudio or alsa) that's different in the soon-to-be Slackware-15.0 that is not supported in Slackware-14.2. But, since I first faced this problem with the default pavucontrol-3.0 I honestly don't know why it stopped working then started again. Stay well, all, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] No audio output; same setup worked before
On Sun, 14 Feb 2021, Rich Shepard wrote: I tried a test file with audacity. It recorded but no sound when playing back (screenshot attached.) Sean, Aha! I found the problem, at least with audacity. Audacity has a drop down combobox with output options. The default is, "HD-Audio Generic: ALC1220 digital (HW:1,1)" and there's no speaker output. And, when I change the output to "HD-Audio Generic: ALC1220 digital (HW:1,0)" the same test recoding is heard from the speakers. When I look at pavucontrol's Configure tab I don't see options with ALC1220 or HW:1,x. It seems that it's pavucontrol's output option that needs changing. How do I determine which will work? Regards, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] No audio output; same setup worked before
On Sat, 13 Feb 2021, Sean Greenslade wrote: OK, all of this suggests that the file did not record correctly. And after some experimentation myself, it seems like this is a known bug: Sean, I tried a test file with audacity. It recorded but no sound when playing back (screenshot attached.) I'm really puzzled. Regards, Rich___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] No audio output; same setup worked before
On Sat, 13 Feb 2021, Sean Greenslade wrote: OK, all of this suggests that the file did not record correctly. And after some experimentation myself, it seems like this is a known bug: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/822 Sean, What's the difference between parec and pacat? The former looks like the eqivalent to parecord or paca -r. Oh. When I started having issues I upgraded pavucontrol from -3.0 to -4.0. The last time the AT2500 worked as expected was with 3.0 installed. It seems like the wav format does work, so give this variant a try: $ pacat -v -r --file-format=wav /tmp/sounds.wav and $ pacat -v -p --file-format=wav /tmp/sounds.wav So I tried these with 4.0 and still no sound. $ pacat -v -r --file-format=wav /tmp/sounds.wav Opening a recording stream with sample specification 's16le 2ch 44100Hz' and channel map 'front-left,front-right'. Connection established. Stream successfully created. Buffer metrics: maxlength=4194304, fragsize=352800 Using sample spec 's16le 2ch 44100Hz', channel map 'front-left,front-right'. Connected to device alsa_output.pci-_0a_00.3.analog-stereo.monitor (index: 0, suspended: no). and $ pacat -v -p --file-format=wav /tmp/sounds.wav Opening a playback stream with sample specification 's16le 2ch 44100Hz' and channel map 'front-left,front-right'. Connection established. Stream successfully created. Buffer metrics: maxlength=4194304, tlength=352800, prebuf=349276, minreq=3528 Using sample spec 's16le 2ch 44100Hz', channel map 'front-left,front-right'. Connected to device alsa_output.pci-_0a_00.3.analog-stereo (index: 0, suspended: no). Stream started. Then I restored version 3.0 and saw the same results. I have some music files in .wav format. I just played one (pavucontrol version 3.0) using 'pacat -v -p --file-format=wav s-and-g.wav'. pavucontrol's Playback tab's VU meter moved as the song came out of the speakers. Darn! What else can I do to find why what's recorded by the mic won't play? My Scarlett solo is an older gen, so it doesn't have an "air" switch. I was curious what that was, so here's what their docs have to say: Lol, it's just a fixed EQ curve. This should not be the cause of your issues, though feel free to use it if you like the tone it produces. Yes, I have the Gen3 since I bought it mid-last year. I looked up 'air' in the manual and saw it would really not apply to speech but would to music. Regards, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] No audio output; same setup worked before
On Sat, 13 Feb 2021, Sean Greenslade wrote: Not sure what "papac" is. Do you mean "pacat"? Yes. Are you referring to the Kodi project's PAPlayer, or did you use "paplay"? What happens if you try paplay? What are the error messages you get, if any? No, 'paplay': $ paplay test-recording.flac Failed to open audio file. But, $ pacat -p test-recording.flac no sound. Also, can you open the generated .flac file with an audio editor to see if the audio actually got recorded in the first place? Ah, nope. Audacity can't find content and 'ffprobe' returns, $ ffprobe -hide_banner test-recording.flac [flac @ 0xc60d60] Format flac detected only with low score of 1, misdetection possible! [flac @ 0xc60d60] Could not find codec parameters for stream 0 (Audio: flac, 0 channels): unspecified sample format Consider increasing the value for the 'analyzeduration' and 'probesize' options Input #0, flac, from 'test-recording.flac': Duration: N/A, bitrate: N/A Stream #0:0: Audio: flac, 0 channels On a different file (created yesterday): $ ffprobe -hide_banner test-mic.wav Input #0, wav, from 'test-mic.wav': Duration: 00:00:16.00, bitrate: 64 kb/s Stream #0:0: Audio: pcm_u8 ([1][0][0][0] / 0x0001), 8000 Hz, 1 channels, u8, 64 kb/ and $ pacat -p test-mic.wav produced two clicks from the speaker. Found one potential issue: the Focusrite had the 'Air' button pressed under the input volumn knob. Turned that off. Now when I speak into the mic the green ring light around the volumn knob fluctuates as does the pavucontrol VU meter. But, still no output from the speakers. The file size is 4727960 bytes so it does have content. Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] No audio output; same setup worked before
On Sat, 13 Feb 2021, Rich Shepard wrote: Just downloaded 3.0.8 (released within past two weeks) from GitHub. Needs a patch to load so I'll stick with 3.0.7 for the time being. Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] No audio output; same setup worked before
On Sat, 13 Feb 2021, Alexander E. Patrakov wrote: Now that you mention vokoscreenNG... there was a bugfix release, 3.0.7, which mentions in its changelog that it fixes detection of recording devices. It was caused by incompatibility of the old code with GStreamer 1.16.x. Could you please make sure that you have at least that version? Alexander, I'm now running 3.0.7 (there's a patch to 3.0.8 from Arch Linux but since I don't maintain the vokoscreenNG SlackBuilds.org package I'll use 3.0.7 until the new maintainer submits 3.0.8. Thanks, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] No audio output; same setup worked before
On Fri, 12 Feb 2021, Sean Greenslade wrote: I would suggest using the "parecord" and "paplay" utilities, which are meant to directly interact with Pulse. Sean, After reading the pacat man page, and checking that pavucontrol shows the AT2500 as the input device and the external speakers [HD Audio Generic Analog Stereo; Port is line out (plugged in)] I spoke to the mic and watched the 'Recording' tab VU meter change as I spoke. I used 'papac -r .flac' for the recording. I didn't try 'parecord ...'. Then I switched to the pavucontrol 'Playback' tab showing Applications. When I ran 'papac -p .flac' that tab showed the application but there was no VU meter response. Running 'paplayer .flac' the file couldn't be opened. I must still be missing something and I'm not seeing it. Regards, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] No audio output; same setup worked before
On Sat, 13 Feb 2021, Rich Shepard wrote: Interesting. I have 3.0.4 (and will upgrade today) which worked well for me last year. (It did recognize and use the AT mic.) Just downloaded 3.0.8 (released within past two weeks) from GitHub. Thanks, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] No audio output; same setup worked before
On Sat, 13 Feb 2021, Alexander E. Patrakov wrote: Now that you mention vokoscreenNG... there was a bugfix release, 3.0.7, which mentions in its changelog that it fixes detection of recording devices. It was caused by incompatibility of the old code with GStreamer 1.16.x. Could you please make sure that you have at least that version? Alexander, Interesting. I have 3.0.4 (and will upgrade today) which worked well for me last year. (It did recognize and use the AT mic.) Thanks! Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] No audio output; same setup worked before
On Fri, 12 Feb 2021, Sean Greenslade wrote: I'm a little confused by this description. As far as I know, the ATR2500-USB only supports USB connection, not XLR. I'll assume you meant you have a different XLR microphone plugged in to your Focusrite interface. Sean, No, the AT2500USB has both USB-C and XLR ports. It also has a mini-phone jack for a headphone. I see you referencing "arecord" and "aplay", both of which are ALSA utilities. While those should work (assuming you have the pulseaudio-alsa package installed), they are a little harder to to make behave nicely in Pulseaudio due to the limitations of the ALSA APIs that Pulse has to emulate. I would suggest using the "parecord" and "paplay" utilities, which are meant to directly interact with Pulse. I had no idea that 'parecord' and 'paplay' existed; all references to audio on linux that I've seen use the ALSA tools. I'll record another test using the PA tools. These utilities let you specify a recording or playback device directly, or you can leave it unspecified and they should default to the fallback device (as selected by the check marks in the Output Devices and Input Devices tabs of Pavucontrol). I'll experiment. Note that you can check the recording source of a currently-recording app in Pavucontrol just the same way you can check the playback sink of a currently-playing app. I understand this. The recording source is the microphone and me speaking. I can ramble a bit while watching that pavucontrol tab. So I would recommend checking the "Recording" tab of Pavucontrol while recording to make sure that your app is indeed recording from the source you want, and that the VU meter is showing appropriate response. The pavucontrol input devices tab's VU meter does show the mic working; I'll see what the recording tab shows. You can also visually check the produced WAV file with an editor like Audacity to be sure that the audio is making its way into the file. ffprobe showed an audio stream; I'll test with audacity next. What puzzles me is that I have the AT2500 and Focusrite set up as before when I recorded slide shows using vokoscreenNG. My test using vokoscreenNG and my webcam produced a file that ffprobe confirmed has both video and audio streams, but no audio came from the speakers (which do work). More testing today. Thanks for the lesson about ALSA and PA and the suggestion to check mic response in the Recording tab. Regards, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] No audio output; same setup worked before
Before getting the USB headsets working (thank you very much!) I used my AudioTechnica AT2500USB condenser microphone to record the audio portion of videos. Today I decided to again use it for recording and leave the headsets for online, virtual meetings. So I set up the AT again. The AT mic is connected via XLR to a Focusrite Scarlett Solo pre-amp. The Focusrite is connected via USB to a front panel port on the desktop's case. I configured pavucontrol so it sees the webcam and the AT mic as inputs; the audio device is seen as Scarlett Solo USB (rather than AudioTechnica AT2500USB) and the Input Devices tab shows that same device name with the vu meter responding to microphone input. A test file created with arecord shows the audio stream: $ ffprobe -hide_banner test-mic.wav Input #0, wav, from 'test-mic.wav': Duration: 00:00:16.00, bitrate: 64 kb/s Stream #0:0: Audio: pcm_u8 ([1][0][0][0] / 0x0001), 8000 Hz, 1 channels, u8, 64 kb/s The Output Devices tab has only one device: HD Audio Generic Analog Stereo with the Port Line Out (Plugged In). The external speakers are turned on and I hear clicks when I adjust the volume on pavucontrol, but no sound when I play 'test-mic.wav' with aplay. I've looked at pavucontrol tabs and don't see why I'm not hearing that audio stream. What have I missed? Wrong arecord parameters? Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] USB-connected headsets: no sound
On Sun, 7 Feb 2021, Sean Greenslade wrote: I'm glad you were able to get it working. Sean, That makes two of us. :-) I realized why I missed your comment. All other multi-choice comboboxes on the other tabs have the arrow indicator that there's a list of choices there. The one on the playback tab doesn't have that indicator so I thought there was no reason to click on the widget. The lack of consistency caught me. Interestingly, there's a commit in the pavucontrol master that changes the button->radiolist behavior to a standard drop-down selector: https://gitlab.freedesktop.org/pulseaudio/pavucontrol/-/commit/ae278b8643cf1089f66df18713c8154208d9a505 It just hasn't made its way into a release I look forward to seeing that. Thanks again and stay well, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] USB-connected headsets: no sound
On Sun, 7 Feb 2021, Rich Shepard wrote: Now, while there is sound delivered to the headset it comes from only one side. I have the channels locked (the vu meter has two bars, one for Front Left the other for Front Right. I'm assuming that's a hardware defect. Fixed. I needed to play with the individual sound levels to discover that one ear was more sensitive than the other. By lowering the output levels I learned how to adjust both so sound comes from both ... and that is when both are at the same output level. Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] USB-connected headsets: no sound
On Thu, 4 Feb 2021, Sean Greenslade wrote: Under the "Output Devices" tab, some of the outputs may have a "Port" dropdown selector. ... The "Logitach H5703 Stereo Analog Stereo" device is the important one, and it should be left on its default port selection of "Headphones." Also verify that the device is not muted, and that the volume slider is at a reasonable position. Sean, Yes, it has the port of Headphones, is unmulted, and has the volume slider at 100% Under the "Playback" tab, there will be a list of programs currently playing sound. Audacious is running and a song is playing. Now, next to the title of each application, there is an unlabeled dropdown box that shows which sound device the application is currently playing to. Find the actively-playing application and switch its dropdown to the "Logitach H5703 Stereo Analog Stereo" option. Well! The last time I lookat at the 'Playback' tab I missed your point that the dropdown box being unmarked meant there wasn't the usual triangle common to comboboxes. I didn't click on it becuase the symbol wasn't there. Just now I did and, sure enough, there was another option there: the Logitech headphones. I'm so used to GUI widgets being self-explanatory that I didn't try clicking on what appeared to be a label widget. I apologize for not groking what you wrote. Now, while there is sound delivered to the headset it comes from only one side. I have the channels locked (the vu meter has two bars, one for Front Left the other for Front Right. I'm assuming that's a hardware defect. Thanks very much for your patient help. Best regards, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] USB-connected headsets: no sound
On Thu, 4 Feb 2021, Sean Greenslade wrote: There are two places in pavucontrol where you will need to verify things. Sean, I did a lot of poking in the system. Here's the relevant lines in dmesg: # dmesg [4721657.287134] usb 1-11: new full-speed USB device number 49 using xhci_hcd [4721657.877083] usb 1-11: New USB device found, idVendor=046d, idProduct=0a56, bcdDevice= 1.03 [4721657.877086] usb 1-11: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [4721657.877088] usb 1-11: Product: Logitech H570e Stereo [4721657.877089] usb 1-11: Manufacturer: Logitech Inc [4721657.877091] usb 1-11: SerialNumber: [4721658.041812] usb 1-11: Warning! Unlikely big volume range (=4125), cval->res is probably wrong. [4721658.041816] usb 1-11: [11] FU [Sidetone Playback Volume] ch = 1, val = 0/4125/1 [4721658.180916] input: Logitech Inc Logitech H570e Stereo Consumer Control as /devices/pci:00/:00:01.3/:01:00.0/usb1/1-11/1-11:1.3/0003:046D:0A56.0014/input/input 53 [4721658.233326] input: Logitech Inc Logitech H570e Stereo as /devices/pci:00/:00:01.3/:01:00.0/usb1/1-11/1-11:1.3/0003:046D:0A56.0014/input/input 54 [4721658.233482] hid-generic 0003:046D:0A56.0014: input,hiddev96,hidraw1: USB HID v1.11 Device [Logitech Inc Logitech H570e Stereo] on usb-:01:00.0-11/input3 When I entered the Warning! in duckduckgo I found a 7-year-old thread on a red hat forum. There I learned about the 'pactl list' command. Running that here poured out a lot of output. The sections on the Logitech headset are in the attached gzipped text file. I don't understand why but I see what's probably the underlying cause. I hope that your expertise can translate it to explain what I need to do about the suspended and other non-working parts. Regards, Rich pactl-list.txt.gz Description: GNU Zip compressed data ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] USB-connected headsets: no sound
On Wed, 3 Feb 2021, Sean Greenslade wrote: The menu I was referring to is attached to each of the clients. In your screenshot, it's the box that says "HD-Audio Generic Analog Stereo". Click that and change it to "Logitech H570e Stereo Analog Stereo". Sean, Thanks for correcting me. When I change the upper port it displays "Headset (unplugged)" while the headset is plugged in. The lower port sill shows "Logitach H5703 Stereo Analog Stereo" with the port remaining "Headphones". Your system theme makes it a little hard to tell, but yes, the one that is in the darkened state is the selected one. As I mentioned, this won't directly affect existing streams, it simply sets the "fallback" device that is selected if a new client appears and doesn't explicitly specify which sound card it wants to send audio to. Unfortuately, changing the upper port to read "Headset (unplugged)" did not make a difference; still no audio output. Regards, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
Re: [pulseaudio-discuss] USB-connected headsets: no sound
On Tue, 2 Feb 2021, Sean Greenslade wrote: By default, new sound devices don't take over existing streams. In pavucontrol under the playback tab, there should be a dropdown menu for each client listing which card it is currently sending audio to. Try starting a sound playback and switching its dropdown to the USB device. Sean, Thanks for the quick response. I started a .mp3 using Audacious and pavucontrol's Playback tab shows Applications (see attached screenshot.) Under the "output devices" tab, there is a checkmark button next to the sound devices. This lets you specify which device is the default. It won't force existing streams over to it, however, and it won't prevent some clients from remembering their previous soundcard, so you may still need to manually move some clients over to the new soundcard. There are two devices shown, including the headphones. The checkmark box has 2 states represented by light grey and lighter grey (see attached screenshot). Both tooltips say the active checkmark is to 'Set for fallback.' By trial-and-error I think the darker grey is the active state (it is for the mute button.) Regardless, no sound is heard with any combination of checkmark button states for the two output devices. If you have more ideas please share them with me and I'll report the results. Stay well, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
[pulseaudio-discuss] USB-connected headsets: no sound
I have an issue and hope someone here can help me resolve it. Short version: USB-connected headsets have no audible output. Long version: I run Slackware-14.2/x86_64 with pulseaudio-9.0-x86_64-1 on a desktop workstation using an Asus Prime X470 Pro motherboard. I have three headsets and external speakers on this desktop. The speakers and the Yamaha CM500 headset are analog and connect via the audio green and red phone sockets; the Logitech H570e and Mpow HC headsets are digital (at least they connect via a USB port). Audio from any source is heard from the analog speakers and the Yamaha headphones. No sound is heard from any source using the digital headphones. pavucontrol recognizes the digital headsets and both microphones work when selected as input devices; the vu meter fluctuates as I speak. But no sound is heard from any source. With the Logitech connected to a USB3.x port on the desktop's case pavucontrol's output devices tab sees 'Logitech H5703 Stereo Analog Stereo and the port is Headphones. In the configuration tab the profile choices for the Logitech are: Analog Stereo Duplex (the default), Analog Stereo Output, Analog Stereo Input, and Off. With the Mpow headset connected pavucontrol configuration has its profile as Analog Stereo Output + Analog Mono Input. The output devices tab uses the only available port: Analog Output. How can I identify the source of this problem and fix it? TIA, Rich ___ pulseaudio-discuss mailing list pulseaudio-discuss@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/pulseaudio-discuss
