Please post your questions and feedback here.
Date
Votes
141 comments
-
Chrisburrc Hello,
i just updated my Raspberry Pi to the last hifiberryOS (20201202), in Github it says that it now has the drivers for the AMP100, but when I restart by Raspberry Pi, I still have no sound, I have to run the following command and then I have sound:
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/valueWhat is meant by "Amp 100 driver"? Is that the expected behavior?
-
Douglas Gardner @Chrisburrc I'm not with HiFi Berry so you may want to wait for their reply. It could be that the config file still shows dacplus. Here are some instructions that were given to me earlier in this thread to make sure that the amp100 overlay was being used at boot time:
mount -o remount,rw /boot
then 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
You may want to take a look at config.txt before attempting to do anything to see what dtoverlay is set to. If it's not set to, "hifiberry-amp100", then that's probably why the gpio pins are not being set correctly at boot time.
-
Manuel Wernli Hi HifiBerry team and all other supportive users
Many thanks for your fast reply. It's a good point you mention. I might be too much influenced by my old setup. However, my subjective perception is as follows:
Bass(old amplifier) > Bass(Amp-100, no adjustment) >> Bass(Amp-100, room correction).
-
Douglas Gardner Which of the traces is the old amp and setup? If that red graph is your original set up then you have the bass cranked way up and major drop outs between 1kHz and 4kHz and again at 7kHz. That's a lot of variation to EQ out. I'd suggest playing with speaker placement a bit more before asking this much from an EQ. It looks like the EQ did exactly what it's supposed to.
If the red is original and that's what you like then anything approaching flat response is going to sound very thin to you. Maybe take a look at some of the online threads on using REW to EQ that also talk about speaker placement. I can't imagine that you'll be able to EQ all of that away without running into digital clipping problems or other undesirables. This is just my viewpoint.
Room EQ is cool feature. I'll have to play with that. I use it in Roon and am excited that I can do it on the Amp100 so it is applied to all of the inputs and not just Roon's.
-
Manuel Wernli Hi Douglas
Thanks for your hints and explanations. I have no measurement of the old amp. The red line is what was measured with the amp-100, the green line shows the EQ correction (if I understand it correctly) and the white line what the result should be
However, I will need to try also different speaker positions (as you suggested)..
Setting up Roon is planned as a next step...
Regards
-
HiFiBerry team Chrisburrc: Douglas Gardener is right. Your system is probably still using the DAC+ driver as it won't be recofnigured if a card is detected (even if it's using the wrong driver)
Manuel Wernli: Yes, this looks looks a massive peak in bass in your original setup. Room EQ will try to remove it and flatten the frequency response. According to the graphs it did it quite good. However, if you are used to this, the sound will now sound thin. I'm not saying a flat frequency response is the only right way for every user. Especially if you often listen at lower levels, a bit more bass can be benefitial. However, 10db-15db is really a lot.
I would first start experimenting with speaker placements, but also do some additional equalisation in the frequency range of 50-300 Hz. Try a single EQ and play around with the bandwidth and volume change a bit. In the end it's a matter of personal preferences.
I would be careful with the range <100Hz as this is where the room acoustics matters most. -
Douglas Gardner Following up on the problems I'm having with SPDIF input. Checking if other beta testers are having this problem or just unique to me. Is any of the SPDIF stuff controlled by firmware? I've been playing around with a lot of the beta features and wondering if the write DSP setting to firmware capabilities could have messed something up. This isn't a priority feature for me at the moment but I do want to have all of the functionality working that should be working.
-
HiFiBerry team I'm just testing and tuning a new DSP profile. I will definitely work.
I guess, there are very few users that use the SPDIF input today (as there are also only few beta testers) -
HiFiBerry team Douglas Gardner: Try the new V13 version that is working now here in the office:
dsptoolkit install-profile https://raw.githubusercontent.com/hifiberry/hifiberry-os/development/buildroot/package/dspp
rofiles/dsp-addon-96-13.xmlIf it's not directly working after the installation, just do a full restart of the system (that's just easier than restarting all parts ;-)
I'll do another test at home with my second system that uses SPDIF for TV audio input. -
Douglas Gardner Close but not quite on the SPDIF input. I am able to get sound but have the following problems:
1) Music seems to be all out of the right channel (think I have R/L swapped in the sound settings so it might be L channel if you not swapped in your system)
2) Left channel has intermittent static.
3) When switching back to streaming from Roon the music pauses after about 4 seconds. This is the problem that I mentioned earlier in the thread that when SPDIF is connected the system will stop playback after a few seconds if there is a pause in music playing of about 4 seconds or more.
Good news is that music is coming out with SPDIF input and it's probably DSP board settings need to be adjusted.
-
HiFiBerry team The pause issue is something I can work on. However, the left/right problem is something I can't see here and I have no idea why there should be static on one channel. Did you restart the system?
-
Douglas Gardner Yes I did restart but that unleashed several iterations of weirdness that I think I've just managed to overcome. The good news is that SPDIF input seems to be working fine for me now. Given the chain of attempts I listed below I'm guessing that I had some software or DSP compatibility issues from various versions of the OS. I may try to burn a fresh install with v1202 on a new sim card to make sure I have a clean and stable base going forward.
Here are some notes from the adventure:
Restarting must have left some remnants of the DSP because I only have audio coming out of the right speaker. I reinstalled DSP add-on v12 from the web controller and still only had right speaker audio. I rebooted and again only right side audio. Tried rolling back to prior OS version but lost all audio channel controls under Sound/Channels. Did software update to OS v1202 but still no audio control. I had audio but no control of it from the web panel and I noticed that the DSP program was now showing as Unknown. I unchecked the box to only run known DSP programs and did a restart. After restart DSP add-on shows version 12 and SPDIF input is working.
I also don't have the problem anymore with playback stalling if I haven't played anything for a while. I've tested SPDIF in, out, and normal Roon playback. All seem to be working great right now.
-
Douglas Gardner Spoke too soon on the playback stalling but everything else seems to be working fine. I'll let you know how things go after burning a fresh SIM with the latest OS.
-
Douglas Gardner I've re-edited this entire post. In the prior version I described in detail my unsuccessful steps to recreate a SIM that had all channels A, B, C, D and working SPDIF. I have since been able to create a working SIM.
It looks like the SPDIF clock generator is not part of OS v1202. When I etched a new SIM with OS v1202 the SPDIF clock generator is not running and the DSP add on profile shows as Unkown; not sure why.
I manually installed DSP add on program version 12 and rebooted a couple of times. After that I had channel controls for A and B but no controls for C and D. Then I manually started the SPDIF clock generator and loaded DSP add-on version 13 and rebooted. Often times, maybe every time I made a change to DSP add-on program, I had to reboot twice for the Amp 100 to show up in Roon agin.
SPDIF input works now and so do all of the other functions. As mentioned in prior post, playback stops after a few seconds if there's a lengthy pause but I think you know how to fix that. I can now reproduce a fully functioning OS SIM.
-
HiFiBerry team The spdifclockgenerator is part of HiFiBerryOS, it's just not running by default. You have to enable it on a fresh installation. That's normal as there is no UI integration today. This will come in the next release.
If you install a DSP program that is not bundled with HiFiBerryOS, it will be shown as "unknown program" as HiFiBerryOS just doesn't know it. That's normal. You can copy the file to /opt/beocreate/beo-dsp-programs to have it shown as a known program.
-
Douglas Gardner Thanks for the reply. I'm confused as to why a fresh OS install and system setup would show that the DSP program is "Unkown". To the best of my recollection and according to my notes I didn't install any DSP program when I etched these new SIMs. On the original SIM I did install DSP add-on v13 but not on these SIMs.
I thought that the OS would configure on install with the DSP program for that OS build. I used Etcher to create a new SIM using OS v1202 and a new SIM using OS v1102. Both showed the DSP as "Unknown" after setting up the system. Not sure what I may have done wrong with the fresh SIMs. I don't think I understand the DSP add-on configuration and installation process. Can you help educate me or point me to where I can learn how to use those settings and manage different add-on profiles?
Next step for me is to install this in a chassis. Will share some pictures if it looks decent. Thanks for you help with this.
-
HiFiBerry team HiFiBerryOS comes with some DSP profiles included.It compared the program running on the DSP with the profiles it knows. There is no problem with an unknown DSP profile, it simply means that the systems doesn't know it. Nothing wrong with it.
If you have additional DSP profiles, you can copy these to /opt/beocreate/beo-dsp-programs. Then, the system will not display these as "unknown" anymore.
-
HiFiBerry team Douglas Gardner: I think, we found the root cause for the pause problem in Roon. This requires some fixes in different places. Therefore, I'll create an experimental release in the next week that will include these fixes.
-
Douglas Gardner Thanks HiFiBerry team. I'll give it a try when it's ready.
-
Jake G Is there availability to download the amp100 driver for import to another OS? I'm able to output audio after running the reset script with Moode running the dacplus driver, but, naturally, I'm not able to make this occur on reboot currently.
I'll probably end up trying out the HifiBerryOS anyways, but I have Snapcast already set up on Moode.
-
HiFiBerry team No yet. We're still testing it and we want to make sure that it doesn't have negative impact on other cards before merging it into the official kernel.
If you want to build you own kernel, that's possible, that's the commit-ID we're using:
https://github.com/hifiberry/hifiberry-os/blob/65290bd9e1e61e498861d4c373947fc9c73f13ab/configs/hifiberryos-gui#L506 -
Douglas Gardner In my configuration I noticed that Left and Right output channels seem to be swapped depending which outputs I'm using in order to get the correct R/L audio going to the correct speaker. Looking at Sounds/Channels/Advanced my setup reads as follows:
Primary Speaker (A: Left), (B: Right), (C:Right), (D:Left)
It seems that Speaker right/left is swapped for either the standard output or SPDIF output. I don't recall the default channel assignment for channels A and B but I'm pretty sure I have my right speaker connected to the R output of the board. I would have expected C and D to map the same as A and B such that if I had A set to Left in order to get left audio to left speaker then I would need to set C the same to get the same result. It's easy to configure the correct audio channel to the correct speaker but wanted to flag this.
The speaker terminals on the board are labeled Right and Left but I don't see any indication of + - on each terminal post/screw connector to ensure speakers are connected in phase. What is the correct mapping on each terminal post?
Editing this post on January 17, 2021 to update and correct:
Channel mapping is correct and not swapped per above in this post. I believe I had my Left/Right speaker cable swapped. Channels now read as expected A=Right (amp out), B=Left (amp out), C=Right (optical out), D=Left (optical out).
The board does have silk screened markings for + and - for the amplifier outputs. They are just hard to see; very small and inconspicuous.
-
Jeff Dereniwski I'm new to the hifiberry products and stumbled across this amp during my research. Is it possible to expand on the what power amp chip this board is using?
-
Steve Chan FWIW, I was told on another forum that the board has 3 TPA3128D2 chips, which puts into the same general category as the popular TPA3116/TPA3118 chip.
-
Thomas I think its an TPA 3220 - 60W Stereo / 110W Peak
-
Thomas Is it possible that the release 20201213 is causing a lower output level in comparison to the previous releases? I first thought the amplifier is broken after the update but I had to increase the Volume nearly to the maximum to listen at normal level. I use a 19v Power supply and have 4 Ohm Loudspeaker.
-
HiFiBerry team Do you use the DSP add-on?
-
Thomas I forgot to mention, yes I have the dsp add on with software version 13 in place.
-
HiFiBerry team This might be a DSP volume problem. From command line, try the following
dsptoolkit get-volume -
Thomas japp, looks like:
# dsptoolkit get-volume
Profile doesn't support volume control
#
Please sign in to leave a comment.