Elk Audio OS 0.6.0 beta available to download!

Dear Elkers,
we are (finally!) ready to release the first public image:

Elk Audio OS beta 0.6.0

To get started, just download the .bz2 file in the Github repository and follow the instructions here.

This is a development version of the system that includes several tools like compilers, editors, etc. to make it easier to work directly on the board. In the upcoming weeks, we’ll release a stripped-down production image that has fewer features but is more optimized for live usage.

Elk Audio OS includes an easy-to-use update system, so you won’t have to reflash the whole SD card when we’ll deploy further updates.

Many thanks to the closed beta testers who helped us spot several issues in the previous builds!

And to everyone, apologies for the long wait. Fixing the major issues on the distribution (SD card and WiFi stability) was more challenging than we initially thought. Despite its massive user base, the system stack on the Broadcom SOC on the Pi is definitely not one of the easiest to work with.
The amount of possible combinations between 32/64 bit, GPU acceleration, Kernel versions, etc. makes the whole process very time-consuming.

Compared to the previous closed beta releases, we had to switch back from 64bit to 32bit and drop HW GPU acceleration for the time being. At least, we made sure that performance is almost as good with the 32bit distro and that HDMI is usable for the initial network setup.

For those of you that are building their own C++ applications, you will have to replace the SDK with the new 32bit one here.

We also updated the documentation to reflect the changes and we are updating right now all the Elk Community plugin binaries.

Please, let us know about any issue that you might experience, this is still a beta so we expect several to be found. Post on the forum for general Q&A and use the Github Issue page for reporting issues.

Happy hacking!

The Elk development team


Thanks Elk team!
wifi now works like charm between reboots :slight_smile:
long live to elk_system_utils as well!


Hi again,

I was trying to install new toolchain for cross-compilation from macOS but I’m having some problems in the install step. It used to work fine with the precious SDK. I opened this GH issue: https://github.com/elk-audio/elkpi-sdk/issues/3

Also I opened a PR with small suggestions to update the macOS instructions, feel free to approve or reject at your will: https://github.com/elk-audio/elkpi-sdk/pull/2

Hi @frederic,
thanks for the PR.

I think it’s just a permission issue, we usually install the SDK in a system-wide path where root permission are required anyway… can you try to run it as root?

Hmmm It did not seem to work. I also answered in GH issue. Where should we continue the conversation to avoid duplicating messages?

Better to keep it on Github, we’ll look into it and try to replicate it, thanks for the report!

after update of toolchain it works fine, thanks!


Hi Elk team!

I had a question regarding target architecture - is the switch to 32bit permanent/semi-permanent(forseeable future) or is there a 64bit release of the image in the works? Would like to know to inform some of my design decisions and I’m sure others would too.

Loving elk so far, thanks

1 Like

Hi @drnfckdrn,
going back to 64bit on the RPi3 is a possibility but it is also time taken away from working on the RPi 4 (which we haven’t started yet).

Obviously the priority goes to any bug fixing / issue on the Pi3 but soon we’ll have to decide if we want to spend our time on implementing extra features on the RPi3 (like 64bit support or GPU acceleration) or shoot straight for the RPi4. Maybe preparing a poll here on the forum to ask you guys what you’d prefer, too.

Either way, the next architecture would be 64bit, if this helps you at the moment.

Thanks for the reasoning behind the decision (or process anyways) @Stefano . I’d look forward to a poll out of curiosity but given your answer probably best to just develop w/ both in mind. Cheers!

1 Like