Re: [pulseaudio-discuss] No audio output; same setup worked before
On Sat, Feb 13, 2021 at 01:25:22PM -0800, Rich Shepard wrote: > On Sat, 13 Feb 2021, Sean Greenslade wrote: > > 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 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 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 > 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. 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: >> An important feature of all 3rd Generation Scarlett interfaces is >> Focusrite’s exclusive AIR function. Individually selectable on all >> mic input channels, AIR subtly modifies the preamp’s frequency >> response to model the sonic characteristics of our classic >> transformer-based ISA microphone preamps. When recording with good >> quality microphones, you will notice an enhanced clarity and >> definition in the important mid to high frequency range, just where it >> is most needed for vocals and many acoustic instruments. 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. --Sean ___ 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, Feb 13, 2021 at 11:45:07AM -0800, Rich Shepard wrote: > 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 ...'. Not sure what "papac" is. Do you mean "pacat"? > 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. 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? Also, can you open the generated .flac file with an audio editor to see if the audio actually got recorded in the first place? --Sean ___ 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
сб, 13 февр. 2021 г. в 18:47, Rich Shepard : > 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. 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 E. Patrakov CV: http://u.pc.cd/wT8otalK ___ 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
