04-08-2020, 10:59 PM
(04-08-2020, 07:02 PM)Frank Wrote:(04-07-2020, 02:30 PM)tatoringo Wrote:(04-06-2020, 11:28 PM)Frank Wrote:(04-06-2020, 05:59 PM)tatoringo Wrote: Thanks Frank, I was able to follow your instructions, but so far no audio out...This is the part of my boot/config.txt that is not #'d out. But I don't think that's it. Go to /home/pi/.openauto/config/openauto_system.ini In that file's audio section look for 'mixername' It should be edited to read (without the quotes) "mixername=Digital" where "Digital" is the name of the sound control you selected in the earlier step. If you selected "Analog" or something else, then identify it in the "mixername"
I am not testing the audio in OAP, since I assumed it will just work once the audio was coming out of plain raspbian (I am exiting OAP every time to test for audio)
alsamixer is showing all the HiFiberry controls as if it sees it and the card shows as "snd_rpi_hifiberry_dacplus"
my /boot/config.txt is as follows:
-------------------------------
dtoverlay=pi3-disable-bt
disable_splash=1
[pi4]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
dtoverlay=hifiberry-dacplus
[all]
--------------------------------
does it match yours?
---- part of my openauto_system.ini file ---
[Audio]
MusicAudioChannelEnabled=true
SpeechAudioChannelEnabled=true
SplashFilePath=
RingtoneFilePath=file:///home/pi/Downloads/telephone-ring-02.wav
VolumeStep=1
MixerName=Digital <<<<<<<<<<<<<<<<<<< LOOK FOR THIS
Autoplay=false
MediaStorageMusicVolumeLevel=100
----- end of part of openauto_system.ini file ----
boot/config.txt:
-------------------
# Enable audio (loads snd_bcm2835)
dtparam=audio=off
dtoverlay=pi3-disable-bt
disable_splash=1
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
[all]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
gpu_mem=256
start_x=1
-----------------
(04-06-2020, 11:04 PM)Chrisfromwa Wrote: I had a HIFI Berry at first too, it would sometimes work then other times it wouldn't.
I finally gave up and just got a USB soundcard, and haven't had any issues since.
I really wanted the HIFI Berry to work, since it was supposed to be a better quality. But the headaches were just too much.
Yeah, some of the headaches were setting up the configuration for the HAT. Some, I think, were oap software related during that time we were moving through the versions pretty quickly. After being successful with the configuration of my pi 4 and OAP 6.1, my hifiberry amp2 sounds really nice and presents no problems. Too, I like having the added advantage of piping all power I need through the DAC. I did a direct wire into it of 12V DC. It will take anything from 12 to 18 volts. Then it powers the screen, and pi4 with no power brownouts. But you are right. You can lose yout mind when trying to configure it to OAP and the PI.
Thanks Frank, I agree with you (about the power), and also, I don't want to have a separate amp to power speakers. And also there is the fact that I have an extra USB port and a more tidy setup.
I did about the "Digital" and that gave me the volume control from the OAP user interface, thanks... but still no audio from the speakers
aren't you using this line "dtoverlay=hifiberry-dacplus" in your "boot/config.txt" file?
How do you have the rpi to identify the Amp2 if not?
do you have a "/etc/asound.conf" file? if so, could you share it?
could I see what is inside your "/home/pi/.asoundrc" file?
I tried to get a OAP 5.0 image to test it with the RPI 4 (since I had it working with a RPI 3 but I erased the V5.0 image I had due to the update to v6.0 excitement ) but had no luck with the software team...
Anyways, I will keep trying with what I have and your help
QUESTION: How did you install V6.1? I ask because there is no "etc/asound.conf" in V6.1 All config files were moved to /home/pi/.openauto/config/ ... I answered my own question. Going back to the original post, I see you have OAP 7.0. I'm still sitting at 6.1 but getting 7.0 later today or tomorrow.
Before going any further, check your equalizer settings. The default is minus 10db across the board. When I first plugged my AMP2 in, I had no sound because of the equilizer settings. Change it to PLUS 10db across the board, for now, just to see if you now get sound. Afterwards, you can reset equilizer to your liking.
MY /BOOT/CONFIG.TXT (parts not #'d out)
# Enable audio (loads snd_bcm2835)
dtparam=audio=off
dtoverlay=pi3-disable-bt
disable_splash=1
[pi4]
# Enable DRM VC4 V3D driver on top of the dispmanx display stack
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
[all]
dtoverlay=vc4-fkms-v3d
max_framebuffers=2
gpu_mem=256
start_x=1
---------------------
/Home/Pi/.asoundrc file:
pcm.!default {
type asym
playback.pcm {
type plug
slave.pcm "output"
}
capture.pcm {
type plug
slave.pcm "input"
}
}
pcm.output {
type hw
card 0
}
ctl.!default {
type hw
card 0
}
pcm.input {
type hw
card 0
}
--------------------
SSH into your Pi and run "aplay -l" without the quotes ... it should list the hifiberry amp2.
To your question, I did a fresh install of OAP 6.1, the "etc/asound.conf" got it from the HiFiberry page in how to configure the RPI: https://www.hifiberry.com/docs/software/...ux-3-18-x/
...along with the:
dtoverlay=hifiberry-dacplus
line in the "/boot/config.txt" I was asking you aboutBut, I am assuming now that the "etc/asound.conf" is not being taken into account because the "/home/pi/.asoundrc" file exists...
...by the way, my "/home/pi/.asoundrc" is exactly the same as yours
I tried not adding the line
dtoverlay=hifiberry-dacplus
to the "/boot/config.txt" since you dont have it, but once I restart I get an error message when try the set the "snd_rpi_hifiberry_daclus (Alsa mixer)" as "Default" :Once I add the
dtoverlay=hifiberry-dacplus
I get he following in "alsamixer"what tells me that the Amp2 is being recognized (nothing in mute and volume all the way up), but I am still not getting audio...
did you configure something in pulse?
how did you upgrade? have you tried from-scratch install of 6.1?