SOLVED: A valuable lesson has been learned by me. Even though it worked in 3.3.2b2, don't let that be an assumption that it works in 3.3.2RC. As I struggled with this issue, others of you solved your problems by changing out the microphone that aplay detected as a sound card. Oh nooo, that's not my problem. My mic worked well in 3.3.2RC. So I ignored your suggestions and plowed ahead until I ran out of options. So this morning, with no other options on the table, I unplugged my mic and the sound came on! LOL My new mic will be here tomorrow! And I promise to try to listen to y'all better! :-)
UPDATE: I made contacts with Hifiberry and Pulsesaudio. Hifiberry asked if OAP has a profile for the Hifiberry dacplus. I responded that I didn't think so and asked for follow on advise. Pulseaudio advised that there is a bug in the ALSA file and they have attempted communicating same to ALSA. In the attached script, you can see the ALSA issue. Midprocess, ALSA crashes and an error flag says to contact ALSA development team.
I think we could have Hifiberry running well with an equipment profile and ALSA repaired.
=========================================
OAP=3.3.2RC
Pi= Raspberry Pi 3B+
HAT= HifiBerry AMP2
Power = 12VDC into HAT
Microphone=USB mic that works ... Tested: If I say "OK Google," the Google indicator loads.
Config= In: /boot/config.txt added: dtparm=audio=off, dtoverlay=hifiberry-dacplus
Results:
1. There IS NO sound output in OAP.
2. There IS wonderful sound in Pi through the VLC Media Player if I change audio output to "Built-in Audio Stereo"
3. Pulseaudio Volume Control: Output Device tab lists only one output device: "headphones". The hifiberry-dacplus is not listed as an option.
4. kern.log lists this "attempted" message a dozen times:
snd-rpi-hifiberry-dacplus socound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
Then, this message is listed:
snd-rpi-hifiberry-dacplus socound: pcm512x-hifi <-> 3f203000.i2s mapping ok
Then, this is listed 7x (I don't know if it's related)
pcm512x 1-004d: No SCLK, using BCLK: -2
5. Thinking system could not find the HAT, I attempted to force the hifiberry device by editing /etc/pulse/default.pa
I added this line to the bottom of the file: set-default-sink snd-rpi-hifiberry-dacplus
After reboot, system log shows that this force attempt failed because device was not found. This means that either it did not work or I used an incorrect device name (which is probable).
6. pulseaudio command to list all available sinks [pacmd list-sinks] fails to list the hifiberry-dacplus
7. pulseaudio command to list all available output devices [pacmd list-source-outputs] shows only the usb-audio on card 1.
8. Yet aplay lists TWO cards - Card 0 is hifiberry-dac+ at device 0 and Card 1 is USB Audio at device 0
9. pulseaudio command to force list a specific card (card 0 for hifiberry) [cmixer -c$0 -l] produces results that zero is an invalid card number.
10. One other thought: do the permission levels join up? Do us base users have sufficient permissions to see and use pulseaudio? That would explain how it could "be there" and "not be there" at the same time.
11. UPDATE: I shut down pulseaudio from the terminal and restarted it in scripting mode allowing the capture of each step in the startup process. While only a neophyte in all of this, it appears to me that there are configuration files missing in alsa, alsa-mix,etc for the hifiberry. Thus, it gets passed over in the initialization. But thats an uneducated guess. I have appended the file. Turns out to be too big of a file. So now see output1.txt and output2.txt
So for now, I'm left with it running on the Pi but not in OAP. Anyone have any other ideas?
UPDATE: I made contacts with Hifiberry and Pulsesaudio. Hifiberry asked if OAP has a profile for the Hifiberry dacplus. I responded that I didn't think so and asked for follow on advise. Pulseaudio advised that there is a bug in the ALSA file and they have attempted communicating same to ALSA. In the attached script, you can see the ALSA issue. Midprocess, ALSA crashes and an error flag says to contact ALSA development team.
I think we could have Hifiberry running well with an equipment profile and ALSA repaired.
=========================================
OAP=3.3.2RC
Pi= Raspberry Pi 3B+
HAT= HifiBerry AMP2
Power = 12VDC into HAT
Microphone=USB mic that works ... Tested: If I say "OK Google," the Google indicator loads.
Config= In: /boot/config.txt added: dtparm=audio=off, dtoverlay=hifiberry-dacplus
Results:
1. There IS NO sound output in OAP.
2. There IS wonderful sound in Pi through the VLC Media Player if I change audio output to "Built-in Audio Stereo"
3. Pulseaudio Volume Control: Output Device tab lists only one output device: "headphones". The hifiberry-dacplus is not listed as an option.
4. kern.log lists this "attempted" message a dozen times:
snd-rpi-hifiberry-dacplus socound: ASoC: CODEC DAI pcm512x-hifi not registered - will retry
Then, this message is listed:
snd-rpi-hifiberry-dacplus socound: pcm512x-hifi <-> 3f203000.i2s mapping ok
Then, this is listed 7x (I don't know if it's related)
pcm512x 1-004d: No SCLK, using BCLK: -2
5. Thinking system could not find the HAT, I attempted to force the hifiberry device by editing /etc/pulse/default.pa
I added this line to the bottom of the file: set-default-sink snd-rpi-hifiberry-dacplus
After reboot, system log shows that this force attempt failed because device was not found. This means that either it did not work or I used an incorrect device name (which is probable).
6. pulseaudio command to list all available sinks [pacmd list-sinks] fails to list the hifiberry-dacplus
7. pulseaudio command to list all available output devices [pacmd list-source-outputs] shows only the usb-audio on card 1.
8. Yet aplay lists TWO cards - Card 0 is hifiberry-dac+ at device 0 and Card 1 is USB Audio at device 0
9. pulseaudio command to force list a specific card (card 0 for hifiberry) [cmixer -c$0 -l] produces results that zero is an invalid card number.
10. One other thought: do the permission levels join up? Do us base users have sufficient permissions to see and use pulseaudio? That would explain how it could "be there" and "not be there" at the same time.
11. UPDATE: I shut down pulseaudio from the terminal and restarted it in scripting mode allowing the capture of each step in the startup process. While only a neophyte in all of this, it appears to me that there are configuration files missing in alsa, alsa-mix,etc for the hifiberry. Thus, it gets passed over in the initialization. But thats an uneducated guess. I have appended the file. Turns out to be too big of a file. So now see output1.txt and output2.txt
So for now, I'm left with it running on the Pi but not in OAP. Anyone have any other ideas?