Not too much of an issue since am sort of hard-coding the recording
command in my python code, but, seems like if you run through the amixer
command, which might try to bring up a GUI dialogue, then you can do
things like specify the default device, etc., but, like said, not too
much of an issue since, among other things, my python code sort of
offers longer, more detailed commands to then be executed in
succession/combination, using the subprocess.call() function.
Stay well
Jacob Kruger
Blind Biker
Skype: BlindZA
"Resistance is futile, but, acceptance is versatile..."
On 2016-11-21 10:30 PM, Zachary Kline wrote:
As an alternative, couldn’t you set up a .asoundrc file to specify the default recording device? I don’t know much about the syntax for such things, but in theory that would avoid having to do so every time.
I know the syntax is documented somewhere, probably on the Alsa web site.
On Nov 21, 2016, at 12:21 PM, Gregory Nowak <greg@xxxxxxxxx> wrote:
On the rpi2, if you use arecord without specifying an input device, it
tries to record through the rpi2's sound card, which is of course not
possible, and results in the error message you posted. You need to
specifically give arecord the device to use for capturing from.
Greg
On Mon, Nov 21, 2016 at 04:31:32PM +0200, Jacob Kruger wrote:
Will try that first command, but, if run arecord -l, it does show
the USB adapter as an input device.
Thanks
--
Free domains: http://www.eu.org/ or mail dns-manager@xxxxxx
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
_______________________________________________
Speakup mailing list
Speakup@xxxxxxxxxxxxxxxxx
http://linux-speakup.org/cgi-bin/mailman/listinfo/speakup
