Hey folks,

Thank you all for the support so far. I did it. Now it is working.

It's a shame to admit but It was the capture sound level that was too
low. I used alsamixer and entered in the capture tab (F4) and put all
the inputs in the highest level.

Regards,

On Tue, May 20, 2014 at 7:17 PM, John Syn <[email protected]> wrote:
>
> From: Eric Fort <[email protected]>
> Reply-To: <[email protected]>
> Date: Tuesday, May 20, 2014 at 2:13 PM
> To: beagleboard <[email protected]>
> Subject: Re: [beagleboard] Beaglebone Audio Cape Rev B audio Input
>
> in my use of audio and this card from the console I found alasmixer much
> easier to use.  I just went through and set all the levels to 100% and it
> works well.  Try using alsamixer it should get things fixed up in an easy
> and intuitive way.  F1 and the man page cover the controls.
>
> This is true, and if you run alsamixer in a SSH session, it looks much
> better than in a tty console like minicom.
>
> Regards,
> John
>
>
>
> Eric
>
>
> On Tue, May 20, 2014 at 3:40 AM, Raphael Philipe <[email protected]> wrote:
>>
>> It seems that I messed with the amixer parameters. Now I can not even
>> hear from the speaker test. Is there a way of reseting alsa
>> parameters, not only the general audio volume?
>>
>> I saw something like
>> alsactl restore -P
>> and removing '/var/lib/alsa/asound.state
>> but it didn't work for parameters specifically to the DA830 EVM.
>>
>> Why the audio cape is recognized as a DA830 EVM?
>>
>> I suspect that the audio input is not working due to one of that
>> parameters.
>>
>> Regards, Raphael.
>>
>> On Sun, May 18, 2014 at 8:22 PM, John Syn <[email protected]> wrote:
>> >
>> > From: Raphael Philipe <[email protected]>
>> > Reply-To: <[email protected]>
>> > Date: Sunday, May 18, 2014 at 3:30 PM
>> > To: <[email protected]>
>> > Subject: [beagleboard] Beaglebone Audio Cape Rev B audio Input
>> >
>> >
>> > Hi
>> >
>> > I've acquired an Audio Cape Rev B
>> > http://elinux.org/CircuitCo:Audio_Cape_RevB for my Beaglebone Black.
>> >
>> > Following the instructions I was able to make it work. The audio
>> > playback is
>> > working pretty well. However, I cannot test the audio input. I saw that
>> > it
>> > is a line level input (line in), so it cannot be connected to a regular
>> > microphone.
>> >
>> > I want to test it through an echo scheme. I will produce some sound
>> > through
>> > q source (connected to the line in input of the cape) and check the
>> > response
>> > in the audio output, through an earphone.
>> >
>> > I tried to connect the cape line in to the earphone output of an old
>> > cellphone through a male male jack cable (I saw in some forums that the
>> > line
>> > level is similar to the earphone output of some appliances, apart from
>> > the
>> > impedance difference.). Unfortunately, it didn't work.
>> >
>> > The interesting thing is that when the cable is connected to the cape
>> > audio
>> > input and the other connector is unplluged, I can hear the noise from
>> > static, similar to an unplugged to the amplifier electric guitar .
>> >
>> > Can someone suggest me a simple form to test the audio input?
>> >
>> > I don’t have the Audio Cape, but I do have a TLV320AIC3106EVM connected
>> > to
>> > my BBB and it works fine. You may want to try the following command:
>> >
>> > arecord -r 44100 -c 1 -f S16_LE -t wav -vv -d 25 example.wav
>> >
>> > This will show you a bar graph in the terminal so you can see the input
>> > levels. I would just connect the output from you phone to the line input
>> > of
>> > your audio cape. In another terminal, run amixer to adjust the input
>> > levels.
>> >
>> > Regards,
>> > John
>> >
>> >
>> > Regards.
>> >
>> > --
>> > For more options, visit http://beagleboard.org/discuss
>> > ---
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "BeagleBoard" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an
>> > email to [email protected].
>> > For more options, visit https://groups.google.com/d/optout.
>> >
>> > --
>> > For more options, visit http://beagleboard.org/discuss
>> > ---
>> > You received this message because you are subscribed to the Google
>> > Groups
>> > "BeagleBoard" group.
>> > To unsubscribe from this group and stop receiving emails from it, send
>> > an
>> > email to [email protected].
>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> For more options, visit http://beagleboard.org/discuss
>> ---
>> You received this message because you are subscribed to the Google Groups
>> "BeagleBoard" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected].
>> For more options, visit https://groups.google.com/d/optout.
>
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.
>
> --
> For more options, visit http://beagleboard.org/discuss
> ---
> You received this message because you are subscribed to the Google Groups
> "BeagleBoard" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to [email protected].
> For more options, visit https://groups.google.com/d/optout.

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to