-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> aplay calls the ALSA API in the obvious way, just like
> speaker-test, so I'm not sure why one works and one does not. I
> suspect there might be a bug in the ALSA framework.
>
Do you have an idea how to find and fix this bug? I would reall
Hauke Westemeier wrote:
> the people of HifiBerry told me (see linked thread) that there is no
> "THE driver" and therefore I can not provide its source code.
Well, the source code files appear to be:
sound/soc/bcm/hifiberry_dacplus.c
sound/soc/bcm/bcm2835-i2s.c
sound/soc/codecs/pcm512x.c
As far
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
the people of HifiBerry told me (see linked thread) that there is no
"THE driver" and therefore I can not provide its source code.
What I know that
speaker-test -t wav -c 2
and
mplayer -ao alsa:device=hw=1.0 /usr/share/sounds/alsa/Front_Right.wa
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I just read in
https://www.hifiberry.com/guides/configuring-linux-3-18-x/
"Note that aplayer won’t convert files that are in a format that is
not natively supported from our drivers. (e.g. mono files or different
sample rates)."
which seems to b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>>> Where can I find the source code of the driver?
>>
>> Which driver?
>
> Whatever driver you're using. See /proc/asound/modules.
> (I'm asking because it does not appear to be part of the official
> Linus Linux kernel.)
>
cat /proc/asound/modu
Hauke Westemeier wrote:
>> Are there any error messages in the system log?
>
> [38928.967567] pcm512x 1-004d: No SCLK, using BCLK: -2
> is added to
> /var/log/syslog
> According to
> https://support.hifiberry.com/hc/en-us/community/posts/201847081-No-SCLK-using-BCLK-2
> this is normal.
> Are ther
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Are there any error messages in the system log?
Every time I run
aplay /usr/share/sounds/alsa/Front_Center.wav
(and get the error)
[38928.967567] pcm512x 1-004d: No SCLK, using BCLK: -2
is added to
/var/log/syslog
According to
https://support
Hauke Westemeier wrote:
> aplay -v -D plug:stereoonly /usr/share/sounds/alsa/Front_Center.wav
> Playing WAVE '/usr/share/sounds/alsa/Front_Center.wav' : Signed 16 bit Little
> Endian, Rate 48000 Hz, Mono
> Plug PCM: Route conversion PCM (sformat=S16_LE)
> Transformation table:
> 0 <- 0
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
>
> Please try putting this into your ~/.asoundrc:
>
> pcm.stereoonly { type hw card 0 channels 2 }
>
> and then running "aplay -v -D plug:stereoonly
> /.../Front_Center.wav". Does it work? Does it expand the file to
> two channels?
>
I did so
Hauke Westemeier wrote:
>> "Front Right" is the name of the channel. There could be other
>> channels such as "Side Right", "Back Right"; and the channel in
>> the front would be called "Center".
>
> So although the file is called Front_Right.wav aplay should play it on
> both of my channels the s
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> "Front Right" is the name of the channel. There could be other
> channels such as "Side Right", "Back Right"; and the channel in
> the front would be called "Center".
So although the file is called Front_Right.wav aplay should play it on
both o
Hauke Westemeier wrote:
> /usr/share/sounds/alsa/Front_Right.wav
> how can it actually have front and right information in just one channel?
"Front Right" is the name of the channel. There could be other channels
such as "Side Right", "Back Right"; and the channel in the front would
be called "Ce
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was away at the weekend, therefore I can only reply today.
> Try running this program:
>
http://download.atmark-techno.com/misc/demos/usb-audio-a500-howto/hw_params.c
> Does it report one channel?
./hw_params
PLAYBACK
Device: hw:0 (type:
Hauke Westemeier wrote:
> The differences to the values prompted in the error of
> aplay /usr/share/sounds/alsa/Front_Right.wav
> seem to be the number of channels and period_size and buffer_size.
> If I just run speaker test with one channel (default)
> speaker-test -t wav
> I also get a simil
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The content of
/proc/asound/card0/pcm0p/sub0/hw_params
is just "closed". This is as expected as the HifiBerry card is card1,
its parameters given in
/proc/asound/card1/pcm0p/sub0/hw_params
are
access: RW_INTERLEAVED
format: S16_LE
subformat: STD
cha
Hauke Westemeier wrote:
> aplay -D plughw:1,0 /usr/share/sounds/alsa/Front_Right.wav
>
> gives
>
> Playing WAVE '/usr/share/sounds/alsa/Front_Right.wav' : Signed 16 bit Little
> Endian, Rate 48000 Hz, Mono
> aplay: set_params:1297: Unable to install hw params:
> ...
>
> So the same like if I just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
aplay -D plughw:1,0 /usr/share/sounds/alsa/Front_Right.wav
gives
Playing WAVE '/usr/share/sounds/alsa/Front_Right.wav' : Signed 16 bit
Little Endian, Rate 48000 Hz, Mono
aplay: set_params:1297: Unable to install hw params:
ACCESS: RW_INTERLEA
Hauke Westemeier wrote:
> If I run
> speaker-test -t wav -c 2
> everything works fine and I can hear the voice.
>
> aplay /usr/share/sounds/alsa/Front_Right.wav
> Playing WAVE '/usr/share/sounds/alsa/Front_Right.wav' : Signed 16 bit Little
> Endian, Rate 48000 Hz, Mono
> aplay: set_params:1297:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I have a Raspberry Pi 2 Model B running on Raspbian Jessie.
My sound card is a HiFiBerry DAC+.
It seems to be detected by alsa:
aplay -l
List of PLAYBACK Hardware Devices
card 0: ALSA [bcm2835 ALSA], device 0: bcm2835 ALSA [bcm2835 ALS
19 matches
Mail list logo
