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, Feb 15, 2021 at 04:41:49PM -0800, Rich Shepard wrote: > 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? 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 ___ 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 Mon, Feb 15, 2021 at 09:55:28AM -0800, Rich Shepard wrote: > 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. 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: > $ 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. 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. --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 [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, 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
Re: [pulseaudio-discuss] No audio output; same setup worked before
On Fri, Feb 12, 2021 at 12:14:00PM -0800, Rich Shepard wrote: > 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'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. > 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? 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. 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). 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. 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. 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. --Sean ___ 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
