Please post your questions and feedback here.
Date
Votes
141 comments
-
HiFiBerry team There is still some initialisation missing in the driver of the Amp100. We'll integrate the required fixes in the next version of HiFiBerryOS. They will also be integrated directly into the Linux kernel, but we require a bit more testing with this.
As a workaround, just copy/paste the following code to your Linux command line (you need to be root!)
echo 17 >/sys/class/gpio/export
echo 4 >/sys/class/gpio/export
echo out >/sys/class/gpio/gpio17/direction
echo out >/sys/class/gpio/gpio4/direction
echo 1 >/sys/class/gpio/gpio4/value
echo 0 >/sys/class/gpio/gpio17/value
echo 1 >/sys/class/gpio/gpio17/value
echo 0 >/sys/class/gpio/gpio4/value -
Douglas Gardner Thanks for posting this. I just received my Amp100 today. Just hit up this site to figure out why I wasn't getting any sound and looking for some test pointers. The steps above worked great. I've got sound! Some very nice sound! I'll add the DSP board back in and see how that goes.
You're a day saver!
-Doug
P.S. Don't forget to, "dsptoolkit write-reg 0xf146 1", if you're using the DSP board.
-
Douglas Gardner I'm still wondering if there's some sound changes when I use the DSP board. I wouldn't think that there should be but it seems that way to me. I don't have any tools measure but my subjective impression is that's the case. This after doing, "dsptoolkit write-reg 0xf146 1", with each reboot. My preference is the sound of the Amp100 without the DSP board. Same as I found with the DAC 2 HD.
Thanks again for the tips on the Amp 100. Really enjoying the sound I'm getting. I can see a clear path to a powered speaker build using this.
-
HiFiBerry team In general, there should be sound changes if you use a DSP. Otherwise it would be a waste of money - wouldn't it ;-)
However, even without processing the signal isn't simply passed, but it needs to run through several processing stages. Therefore, tiny changes in the sound are possible. -
Douglas Gardner Point well taken but I would have expected it to sound different only if I was using settings to modify the audio. Otherwise I'd expect it to not be messing with the bits or for the messing about to not be audible at the sample rate it's running at. To me the audio sounds worse with the DSP board. Like it's slightly too bright. That's using the, "optimal", setting in Sound tab Advanced settings which I'm guessing wasn't intended to make audible changes.
Maybe I'm wrong about that or maybe my expectations aren't where they should be. Perhaps I have sight bias going from my experimenting before getting the tip on the register setting. For now I either don't have confidence or competency with the DSP board and I'm not seeing a clear path to get over the hump.
Apologies for digressing from the topic of this thread. I am really impressed with the Amp100. Last night I had it driving a pair of two way monitors. Today I have it feeding a pair of Dynaudio Confidence C2 speakers. Impressive performance. I'm quite happy with this all-in-one streamer/dac/amp solution.
-
HiFiBerry team The easiest way to start with sound adjustments is to add a single filter and play around with it. However, if your speakers sound exactly as you think they should, there's no need for adjustments.
It's often important to listen to adjustments for a longer time as they will sound differently and this might sound "worse" if you didn't miss something specifically before.
Often adjusting the low frequencies is easiest to test and will show some improvements as this is where the speaker interacts with the room most extremely. -
Douglas Gardner I'm using the DSP board and raspi 4. What are the steps to enable the toslink input signal path so that the Amp100 can receive digital in through toslink? I've successfully used the toslink output but not the input.
-
HiFiBerry team Douglas Gardner: This is not yet ready in the DSP add-on DSP profile, but I'll see that we can have to ready soon. Just working on the new driver now. This should be ready soon.
-
HiFiBerry team New HiFiBerryOS experimental release is available with the improved driver. You can try using
/opt/hifiberry/bin/update --experimental -
HiFiBerry team Douglas Gardner: The root cause of this problem has been identified. It's basically an design limitation that does not allow SPDIF playback if nothing is playing on the Pi. We need to create some workaround for this that can be integrated into HiFiBerryOS.
-
Douglas Gardner Thanks for the update. I'll give it a go.
-
Douglas Gardner I gave it a try and was able to install the updated OS from the command line but wasn't able to get the SPDIF input working. The DSP program showed as "unkown" in the Sound tab. I was able to play from the pi from Roon by enabling the unknown DSP program but sounded a bit off. I didn't have any of the channel controls that were available in the prior OS build.
The OS rollback function worked so I was able to restore to the prior OS version with no problems. I take it that your comment above, "We need to create some workaround for this that can be integrated into HiFiBerryOS", means that some additional work needs to be done in addition to the experimental OS version. No need to rush; I'll stand by until the next stable OS release.
For now just knowing that the optical input will work in the future is enough for me. I'm making some decisions on a chassis build and wasn't sure if that input is expected to work.
-
HiFiBerry team @Douglas: The new release only added the Amp100 driver. The SPDIFG input will need some additional software that isn't yet ready.
-
Jake G Is there a particular power supply the HifiBerry team is targeting or using to achieve the actual 100W output of the AMP100 at a decent price point? Seems like, after a quick online search (looking at $80+ with shipping), I can find limited numbers of consumer-accessible PSU @ 30V (rather than the typical next step of 36V from 24V) meeting the power specification. Otherwise, the potential is, in essence, wasted by limiting to 24V (~60W normal output per the datasheet).
-
Douglas Gardner Is there a mechanical drawing or template showing the placement and dimensions of all of the connectors on the board and with the raspi (raspi 4) installed? Something that would be suitable for use in making cutouts for a chassis plate with openings for power, SPDIF in/out, raspi ethernet and USB? I'd like to try fabricate a chassis and thinking about 3-d printing a back plate to match with the side of the board that has those connectors.
-
HiFiBerry team There is no drawing, but you can use the Beocreate 3D model:
https://www.hifiberry.com/docs/hardware/3d-models-of-hifiberry-boards/
The Amp100 is a bit longer, but the connectors are in the same position. -
Steve Chan The Amp100 looks cool! What class D chipset does it use?
-
HiFiBerry team Douglas Gardner: You might try the latest experimental. If you're not using Snapcast, it should be fine ;-)
Once you booted, you can enable the SPDIF monitor via command line:systemctl enable --now spdifclockgen -
Douglas Gardner I gave it a shot but no luck. The latest experimental version loaded and I was able to run, "systemctl enable --now spdifclockgen", but no sound to the speakers with the SPDIF input. I don't see the green led light on the DSP board like I do during normal play from Roon if that's relevant. I'm not sure what the expected behavior is with the SPDIF input or how to control it so not sure how to approach debugging.
I noticed that playback stalls after about 4 seconds with the first tack I play from Roon. It happens when playing the first track or after a pausing playback for more than about 5 seconds.
I still had to do the manual gpio settings from the top of this Amp100 thread to get sound. Just making you aware that it isn't in the latest experimental build. I didn't have to do the manual, "dsptoolkit write-reg 0xf146 1", for the DSP board. That seems to be resolved.
-
HiFiBerry team As your system is already configured, it probably didn't re-configure the board for the Amp100. Try the following:
mount -o remount,rw /bootthen edit /boot/config.txt (via either nano or vi) and remove the dtoverlay=dacplus line.
After booting (and automatic reboot, it should configure something like
dtoverlay=hifiberry-amp100
and the MUTE control should work
About SPDIF: What's the output of
journalctl -u spdifclockgen -
Douglas Gardner Removed the dcplus overlay and am seeing hifiberry-amp100 now.
Output of journalctl -u spdifclockgen:
-- Logs begin at Sat 2020-09-12 08:16:33 EDT, end at Mon 2020-11-30 15:35:50 EST. --
Nov 30 15:31:19 hifiberryos systemd[1]: Started SPDIF clock generator.
Nov 30 15:31:55 hifiberryos spdifclockgen[713]: INFO: root - received USR1, stopping music playback
Nov 30 15:34:41 hifiberryos spdifclockgen[713]: INFO: root - received USR1, stopping music playback--
I see the Optical Input volume limit controls now.
Adding in that I do see a green led light on the board by one of the electrolytic caps when I plug in my optical cable. Looks like it's doing something with optical but not sure where the sound is going.
-
HiFiBerry team So, everything working as expected?
-
Douglas Gardner No output from the amp to the speakers. I see a green led light by one of the electrolytics but I don't have any sound. Not sure where it's going. Sliding the optical volume limit up and down isn't doing anything. I don't see specific MUTE selection for optical; just the slider.
-
Douglas Gardner Wanted to call out separately the problem that I mentioned above with playback stopping that seems to be related to optical input.
This happens anytime I start playing music from Roon after a pause of about 5 seconds. When I pause playback and wait about 4 seconds I see the green led by the electrolytic turn off and quickly back on. If that happens then when I restart playback from Roon the track will stop after a few seconds. If I hit play again quickly then the track and subsequent tracks will play without problem provided I don't have a pause of 5 seconds.
I disconnected the optical input and that resolved this pausing problem.
-
HiFiBerry team That's basically how it works. If nothing is playing on the Pi and there's a signal from the SPDIF input, it'll switch to this input.
However, I don't really know why you don't hear something coming on from TOSLink. Please try the following:
- stop all players on the Pi
- connect TOSLink
- start
journalctl -f -u spdifclockgen
- stop playback from an external source and send the logs.
BTW: To disable the SPDIF input, just stop spdifclockgen
systemctl stop spdifclockgen
(we'll add this to the sources menu, but first it has to work correctly ;-) -
Douglas Gardner I think I did the steps you mentioned and still no sound. Exactly what I did is as follows:
Start Optical input debug steps:
14:23 local: Rebooted HiFiBerryOS
14:24 local: Began playing through SPDIF input - no sound from speakers
journalctl -u spdifclockgen:
-- Logs begin at Sat 2020-09-12 08:16:33 EDT, end at Tue 2020-12-01 14:24:33 EST. --
Dec 01 14:23:32 hifiberryos systemd[1]: Started SPDIF clock generator.
14:26 local: stopped playback
14:27 local: disconnected SPDIF input
journalctl -u spdifclockgen returned same line as above.END Debug Steps
After the steps above I went back into Sources and disabled everything that I could. The only two that can't be disabled are Radio and Music. Did a reboot and had the same behavior as above; no sound.
I've used two different SPDIF input sources, a Squeezebox Touch and a Meridian 508 CD player. The SPDIF cable shows light so it's working and I used the same cable to validate the SPDIF output.
I'm seeing the green led turn on by the electrolytic when I connect the SPDIF but I'm not seeing the green LED on the DSP board when trying to play through the SPDIF input.
-
HiFiBerry team Interesting. Looks like it detects SPDIF input, but doesn't send it to the output. I'm not yet sure why this happens as I don't see it here. We'll have a look, but it probably will take some time to figure what's wrong in your setup.
-
Douglas Gardner Yep; interesting. Let me know if you want me to perform any other tests. My electronic diagnostic tools are limited to a volt meter. I've got time to play with this if there are any software diagnostics or if it makes sense to burn a new OS image to start fresh.
-
Manuel Wernli Dear HiFiBerry team
I have the amp100 now running for about a week and am happy to be able to replace a big old amplifier with a small and up-to-date device. However, I would like to make the following comments:- The connection between the Hifiberry 24V/180W power supply and the amp-100 board seems not to be very stable. The slightest touch of the cable powers the raspberry off. When I plug in the male connector to the amp-100, it is quite sensitive to find a position where it makes contact. I assume that the male plug of the powersupply does not make good contact.
- First the hifiberryos 20201101 was installed and I used the commands you posted above to make the amp-100 work. Today I downloaded 20201201 from your website and flashed it via computer to the SD card. In the web GUI it says, that not the newest version is installed and 20201202 is available.
- I tried to use the hifiberryos room correction (in version 20201101). After applying the suggested settings, there is almost no bass. I tried to make measurements at different positions and heights in the room, but the effect was the same.
Regards,
Manuel
My setup:
HiFiBerry measurement microphone
HiFiBerry 24V/180W power supply
-
HiFiBerry team "Almost no bass" is something you might feel if your setup had way toop much bass before - which we see regularly. Can you share a screen shot of the frequency response before the correction?
Please sign in to leave a comment.