[pulseaudio-discuss] No audio output from Zoom

2023-04-14 Thread Rich Shepard
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

Re: [pulseaudio-discuss] Need help resolving audio recording/playback issues

2022-02-16 Thread Rich Shepard
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

Re: [pulseaudio-discuss] Need help resolving audio recording/playback issues

2022-02-16 Thread Rich Shepard
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

[pulseaudio-discuss] Need help resolving audio recording/playback issues

2022-02-08 Thread Rich Shepard
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

Re: [pulseaudio-discuss] No audio output; same setup worked before [RESOLVED]

2021-02-16 Thread Rich Shepard
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

Re: [pulseaudio-discuss] No audio output; same setup worked before [RESOLVED]

2021-02-15 Thread Rich Shepard
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

Re: [pulseaudio-discuss] No audio output; same setup worked before [RESOLVED]

2021-02-15 Thread Rich Shepard
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 "H

Re: [pulseaudio-discuss] No audio output; same setup worked before

2021-02-14 Thread Rich Shepard
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 Ge

Re: [pulseaudio-discuss] No audio output; same setup worked before

2021-02-14 Thread Rich Shepard
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.)

Re: [pulseaudio-discuss] No audio output; same setup worked before

2021-02-14 Thread Rich Shepard
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

Re: [pulseaudio-discuss] No audio output; same setup worked before

2021-02-13 Thread Rich Shepard
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

Re: [pulseaudio-discuss] No audio output; same setup worked before

2021-02-13 Thread Rich Shepard
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

Re: [pulseaudio-discuss] No audio output; same setup worked before

2021-02-13 Thread Rich Shepard
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

Re: [pulseaudio-discuss] No audio output; same setup worked before

2021-02-13 Thread Rich Shepard
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

Re: [pulseaudio-discuss] No audio output; same setup worked before

2021-02-13 Thread Rich Shepard
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

Re: [pulseaudio-discuss] No audio output; same setup worked before

2021-02-13 Thread Rich Shepard
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

Re: [pulseaudio-discuss] No audio output; same setup worked before

2021-02-13 Thread Rich Shepard
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

[pulseaudio-discuss] No audio output; same setup worked before

2021-02-12 Thread Rich Shepard
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

Re: [pulseaudio-discuss] USB-connected headsets: no sound

2021-02-07 Thread Rich Shepard
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

Re: [pulseaudio-discuss] USB-connected headsets: no sound

2021-02-07 Thread Rich Shepard
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

Re: [pulseaudio-discuss] USB-connected headsets: no sound

2021-02-07 Thread Rich Shepard
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

Re: [pulseaudio-discuss] USB-connected headsets: no sound

2021-02-05 Thread Rich Shepard
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

Re: [pulseaudio-discuss] USB-connected headsets: no sound

2021-02-03 Thread Rich Shepard
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

Re: [pulseaudio-discuss] USB-connected headsets: no sound

2021-02-03 Thread Rich Shepard
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

[pulseaudio-discuss] USB-connected headsets: no sound

2021-02-02 Thread Rich Shepard
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