--- Sean McEnroe <[EMAIL PROTECTED]> wrote:
> The amp circuit on some HD audio chips (Nvidia) is
> notorious for low
> power audio recording even with 20dB power boost. A
> powered microphone
> is required to do recording as The on board preamp
> circuit is
> insufficient. Venu can you borrow a powered
> Microphone and try test
> again ? Otehr option is to run Windows and see if it
> works w/o powered
> microphone.
Powered Microphone, yet to be tried.
>
> Let's back up a bit. Does audioplay work using the
> sample file say
> space.au ok on the internal speaker ? I want to make
> sure that the audio
Yes, it does.
> codec is working at least for output. Also, are you
> sure the mic jack is
> in the correct slot (what color is the inside of the
> jack port red or
> green or white ?)
The audio input has three ports:
Black: MIC-IN
Green: LINE-IN
Red: CD-IN
The following I have tried with default options does
work, MIC is working fine with "line" port.
Microphone testing:
---------------
a. mic connected to LINE-IN *did work*
# audiorecord -p line -t 20 lineoutputfile.au
# audioplay lineoutputfile.au
b. mic connected to MIC-IN didnot work
# audiorecord -p mic -t 30 testmic_0.au
# audioplay testmic_0.au
c. mic connected to CD-IN didnot work
# audiorecord -p internal-cd -t 30 testmiccd.au
# audioplay testmiccd.au
CD testing:
--------
a. CD connected to CD-IN did *work*
# audiorecord -p internal-cd -t 30 testcd.au
# audioplay testcd.au
b. CD connected to LINE-IN did *work*
# audiorecord -p line -t 30 testcdline.au
# audioplay testcdline.au
c. CD connected to MIC-IN didnot work
(audiorecord hung: couldnot Ctrl-C or kill -9
didnot work)
# audiorecord -p mic -t 30 test-cd-using-mic-in.au
^C
Thanks,
Venu.
>
> -Sean
>
> also check test is to run windows on same platformOn
> 2008å¹´10æ17æ¥
> 18:16, Garrett D'Amore wrote:
> > Venu Chennupati wrote:
> >> Hi Sean,
> >>
> >> I have Intel HD audio controller(0x8086,
> 0x811b), by trying the
> >> suggested
> >> commands I am not able to all kinds of sounds.
> Not able to hear my
> >> voice, but able to
> >> hear knoking microphose and air blow sounds are
> audiable through the
> >> speaker while
> >> recording.
> >>
> >
> > Two thoughts:
> >
> > 1) Make sure you use a decent quality microphone.
> > 2) (This is for Sun audio folks) Perhaps the 20dB
> micboost needs to be
> > enabled?
> >
> > -- Garrett
> >> Thanks,
> >> Venu.
> >>
> >> Sean McEnroe wrote:
> >>
> >>> Hi Venu:
> >>>
> >>> Garrett is right.
> >>>
> >>> For best results use
> >>> audiorecord -v 80 -b 50 -m 80 -p mic -c 2 -s
> 48000 -e linear -t 60
> >>> micoutputfile
> >>>
> >>> then use audioplay -v 80 -b 50 -p speaker
> micoutputfile
> >>> to listen to your recording.
> >>>
> >>>
> >>> This will record stereo 48KHz (not 44.1Khz)
> nicely for 60 seconds on
> >>> most SUN HW as default is only uLAW 8Khz mono.
> Results go into
> >>> micoutputfile which defaults to a .au file. the
> -e linear uses PCM
> >>> Pulse Code Modulation recording. Most SUN audio
> chips support 48Khz
> >>> as their native sampling frequency.
> >>> man audiorecord for other file options.
> >>>
> >>> PS
> >>> audiorecord assumes audio device is /dev/audio
> if yo want a different
> >>> audio device use the -dev switch to specify.b
> Also, the -m is to
> >>> listen (monitor) your recording on the monitor
> speaker (usually the
> >>> internal speaker) omit if you do not wish to
> monitor.
> >>>
> >>>
> >>> -Sean McEnroe
> >>>
> >>> On 2008å¹´10æ16æ¥ 19:10, Garrett D'Amore
> wrote:
> >>>
> >>>> Try the CLI tool "audiorecord". I find it
> works pretty well.
> >>>>
> >>>> -- Garrett
> >>>>
> >>>> Venu Chennupati wrote:
> >>>>
> >>>>> Any idea on how to test audio using
> microphone. My question is
> >>>>> generic,
> >>>>> not specifc to to the pci8086,7270.
> >>>>>
> >>>>> On neveda build 100, I tried to record using
> "Sound recorder" tool
> >>>>> available under
> >>>>> All Applications/Sound & Video. Record from
> input is availabe as
> >>>>> 'Gain' and 'Screen'
> >>>>> I tried to record using input 'Gain' and
> played back. Nothing
> >>>>> making sense heard.
> >>>>>
> >>>>> Also I tried "cat test.oga > /dev/audio" (
> test.oga is recorded
> >>>>> file using above method)
> >>>>>
> >>>>> I hear noice from audio output. Is there any
> better way to test
> >>>>> audio input working?
> >>>>>
> >>>>>
> >>>>> ---
> >>>>> # prtconf -D | grep audio
> >>>>> pci8086,7270, instance #0 (driver
> name: audiohd)
> >>>>>
> >>>>>
> >>>>> pci8086,7270, instance #0
> >>>>> System software properties:
> >>>>> name='play-interrupts'
> type=int items=1
> >>>>> value=000000af
> >>>>> name='record-interrupts'
> type=int items=1
> >>>>> value=000000af
> >>>>> Driver properties:
> >>>>> name='fm-errcb-capable'
> type=boolean dev=none
> >>>>> name='fm-ereport-capable'
> type=boolean dev=none
> >>>>> Hardware properties:
> >>>>> name='pci-msi-capid-pointer'
> type=int items=1
> >>>>> value=00000060
> >>>>> name='acpi-namespace'
> type=string items=1
> >>>>> value='\_SB_.PCI0.HDEF'
> >>>>> name='assigned-addresses'
> type=int items=5
> >>>>>
> value=8300d810.00000000.fdff4000.00000000.00004000
> >>>>> name='reg' type=int items=10
> >>>>>
> >>>>>
>
value=0000d800.00000000.00000000.00000000.00000000.0300d810.
> >>>>> 00000000.00000000.00000000.00004000
> >>>>> name='compatible' type=string
> items=13
> >>>>> @
> >>>>> @
> >>>>>
> value='pciex8086,811b.8086.7270.6' +
> >>>>> 'pciex8086,811b.8086.72
> >>>>> 70' + 'pciex8086,811b.6' + 'pciex8086,811b' +
> 'pciexclass,040300' +
> >>>>> 'pciexclass,
> >>>>> 0403' + 'pci8086,811b.8086.7270.6' +
> 'pci8086,811b.8086.7270' +
> >>>>> 'pci8086,7270' +
> >>>>> 'pci8086,811b.6' + 'pci8086,811b' +
> 'pciclass,040300' +
> >>>>> 'pciclass,0403'
> >>>>> name='model' type=string
> items=1
> >>>>> value='Mixed Mode device'
> >>>>> name='power-consumption'
> type=int items=2
> >>>>> value=00000001.00000001
> >>>>> name='devsel-speed' type=int
> items=1
> >>>>> value=00000000
> >>>>> name='interrupts' type=int
> items=1
> >>>>> value=00000001
> >>>>> name='subsystem-vendor-id'
> type=int items=1
> >>>>> value=00008086
> >>>>> name='subsystem-id' type=int
> items=1
> >>>>> value=00007270
> >>>>> name='unit-address'
> type=string items=1
> >>>>> value='1b'
> >>>>> name='class-code' type=int
> items=1
>
=== message truncated ===
_______________________________________________
driver-discuss mailing list
[email protected]
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
