My current music setup is a Raspberry Pi 3 with a HifiBerry DAC+ audio card as my music player. It works perfectly, except for one annoying thing. The new HifiBerry DAC+ makes an audible click or poping sound when changing the sampling rate. I have a lot of recordings in higher resolution than CD-quality of 16-bit 44kHz, so it’s jarring when it happens. I like to play my music loud which exacerbates the problem. But there’s an easy solution, and at the same time, you can get better sound quality overall. Here’s how to fix the problem.
Make your Single Board Computer shine with DietPi
My wild guess is that most people get a small Linux computer, like the Raspberry Pi, BeagleBone, Banana Pi or Orange Pi for a specific task. Unfortunately, most distributions are chock-full of software, with everything installed per default. But if you want to set up a lean single board computer for a specific task, you’re out of luck. Thankfully there is a Linux distribution, DietPi, that aims to fix that problem.
I needed a cheap heatsink for my Raspberry Pi 3 that I use as a music player/server. To maximize performance, I wanted to overclock the computer for faster searching and handling of all my music. I’ve managed to overclock my central Stratum-1 NTP server to 1350MHz without any problems, but the dinky little aluminum heatsink was way to anemic, so I found a very cheap DIY solution to my problem. With this heatsink, I can run the Raspberry Pi 3 at 1.5GHz all day at full tilt without any issues!
The results are in:
I’ve been very busy with different projects, and one of them requires a custom enclosure. So I thought it would be an excellent excuse to learn Fusion 360. When the Raspberry Pi 3 came out, I did some overclocking experiments. But I settled with just passive cooling with some small aluminum heatsinks. But after seeing some tests done with a more massive copper heatsink combined with a cooling fan, I decided that I wanted to build a case with a silent fan with enough room for a large heatsink. I need it for my NTP server at ntp.jacken.se to get better performance.
After becoming a full-fledged time-nut (I’m compiling a new Linux kernel on my second NTP server as we speak), I have started to use the statistics that I usually install on a server just to keep a check on it. Sure, when installing something like MRTG, it’s great to see if something is clogging the system, but mostly, it’s unused. But when working with an NTP server a lot of factors start to make a difference. The temperature of the processor (the whole computer actually, mostly due to crystal drift), the load of the CPU’s, etc.