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
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
>
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
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
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:
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:
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.)
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
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':
> $
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
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
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
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
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
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
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
сб, 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
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
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
>
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
20 matches
Mail list logo
