Re: Intro, and, first question

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Ok, got it sorted - was playing around with amixer set commands, but, after a couple of tries, switching microphone between sockets on USB audio adapter, and, making sure everything was properly inserted, etc., it does now record the audio input from the microphone.


So, to try put this on-topic, yes, it had nothing to do with speakUp...<smile>


On a side note, relating to speakUp, one other thing is since am trying to handle this using just a USB numpad plugged in, since the keys there get used by speakUp, I seem to need to hold in numlock key while then typing in a sort of menu option, like 1, before hitting enter, but, that's a minor thing that will just need to be explained to guys.


Stay well


Jacob Kruger
Blind Biker
Skype: BlindZA
"Resistance is futile, but, acceptance is versatile..."

On 2016-11-22 12:43 AM, Jacob Kruger wrote:
Thanks, Greg.


Have actually just found out that specifying device 1 works.


Oddly enough, if I run the arecord -l command, it only shows device 1, but, suppose that's since it's offering input, but, had thus not realised there was also a device 0 that just wasn't showing up.


In other words, the following command does now run through, but, with one more minor issue that will explain below:

arecord -D plughw:1 -f dat testing.wav


The issue have now come across is that it's most likely recording at a really low volume, or else will need to double check recording with different microphones hooked up to the USB audio adapter, since when I then copied the output file to my main PC, and, boosted it's volume using audacity, I just picked up some crackles, but, no actual voice input, but, will try it out with a different microphone now.


Main thing is it didn't bring up that error message, and, ran through, producing the output .wav file, etc.


Thanks, again


Jacob Kruger
Blind Biker
Skype: BlindZA
"Resistance is futile, but, acceptance is versatile..."

On 2016-11-21 10:21 PM, Gregory Nowak 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




[Index of Archives]     [Linux for the Blind]     [Fedora Discussioin]     [Linux Kernel]     [Yosemite News]     [Big List of Linux Books]
  Powered by Linux