View Single Post
Old 07-09-2012, 07:58 AM   #44
twobob
( ͡° ͜ʖ ͡°){ʇlnɐɟ ƃǝs}Týr
twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.twobob ought to be getting tired of karma fortunes by now.
 
twobob's Avatar
 
Posts: 6,586
Karma: 6299993
Join Date: Jun 2012
Location: uti gratia usura (Yao ying da ying; Mo ying da yieng)
Device: PW-WIFI|K5-3G+WIFI| K4|K3-3G|DXG|K2| Rooted Nook Touch
getting some visuals with arecord to check mic

so.... Let's see if we can get a nice recording dialog going to easily test our input actually does something.

A visual readout would be nice so we shall check it with the arecord -vv -fcd /somewhere/safe/and/useful/blah.wav (optionally set the duration with -d in integers as seconds like: -d 30)



The ##############+'s at the bottom (in the image callout) will dynamically go up and down according to the input level.

What if it doesn't go up and down?
Assuming you didn't edit any files on the device to do with alsa config, since the alsa config is pre-setup on these devices for you, the microphone is broken. Highly unlikely to happen IMHO though.

Also note that devices have differing sound support, if yours has none for example this will not work

Last edited by twobob; 07-09-2012 at 11:09 AM. Reason: screenie
twobob is offline   Reply With Quote