Video based on "Flesh paths" by Alessandro Amaducci
Remixed by Steffest
Mute Audio - Pause video - Clear screen
Steffest Digitale Pulptuur

I did a new "paint job" on an Amiga case. (Normally they are white)

Custom Amiga 1200 case

I am totally in love :-)

The case is one from in "CD32 grey".
I also pre-ordered the matching keycaps like 2 lifetimes ago - but they still have to deliver, always a lurking issue with these kickstarters.
Anyway - I decided to do a DIY.
I posted it on some forums and got surprisingly many reactions asking how I did the keycaps.
Super easy actually, but here it goes.
I used iDye Poly. It's a dye that bonds with most plastics but - luckily - it doesn't bond with the little protective cover that is on the letter of the keycaps on Amiga 1200 models.
This result in the original key-color shining through as a small border around the lettering, making sure the letter is still readable.
Rather a funky effect!
Before dying, make sure you're keys are super clean and evenly coloured. I even brighted mine a bit with hydrogen peroxide.
The instructions that come with iDye Poly are meant for dying fabrics. They tell you to use boiling water, but whatever you do: DO NOT BOIL YOUR KEYCAPS!
They will warp and bend, making them unusable. (believe me, I know from experience :-/ )
I used water of about 50 °C.
Add the dye, add the color intensifier that comes with the dye.
Stir, pop in keys.
I use a 1 liter transparent plastic bottle with a wide opening. That way you can close it and give it a good shake, making sure all keys are subdued in the dye.
I used the "silver gray" color for the gray keys. The dye works pretty fast and I only left them in for about 2 minutes.
The black keys I left soaking for a few hours (in the color "black") and that was a mistake.
After some time, the dye builds up to a sticky goo, making the keys a bit smudgy.
I evened them out with some acetone rubbing but still they are not a sharp as they should be.
I finished them of with a few layers of matte varnish for the gray keys and high-gloss for the blacks.
I knew upfront this would make them dust-magnets but hey ... looking as cool as that is hard work!

then the finishing touch: I designed a custom badge with the vampire logo in CD32 theme and asked the "BadgeMan" to print it.
Cherry on the pie! 

I did one before - a 600 model.
There I did the complete case and painted the keys black.
I applied some Amiga-specific keyboard stickers made by iComp.
Custom Amiga 600 case

Also nice!


A new version of BassoonTracker is out!
BassoonTracker is your online old-skool music tracker supporting .MOD and .XM files
Most notable new features in version 0.4.0: Midi support, full undo/redo in pattern editor and sample editor, tons of usability improvements and ... Ladies and Gentlemen: WE HAVE NIBBLES !
Full release notes on
Tracker on
Source Code on

a picture called eerstemarathon.jpg (click to enlarge)
Exact 1 jaar geleden - vandaag - deed ik mijn eerste loopje (ooit)
De volle 2 kilometer.
En wonder boven wonder: dat was kei plezant.
Een paar dagen later het eerste loopje op Strava - want anders schijnt dat niet te tellen.
Toen kwam Corona en werden mijn loopjes zowat de enige reden dat ik nog buiten kwam.
Vandaag - exact 1 jaar later - was de dag TE mooi om binnen te zitten en liep ik mijn eerste marathon.
OK... ik heb dat zwaar onderschat. Die laatste 10 kilometer waren loodzwaar.
Ik heb een paar keer moeten wandelen en ik deed er zowat een half uur langer over dan gepland
Maar nu staat er op zijn minst een richt-tijd op het scorebord om te verbeteren! Dat ga ik nog eens doen! (maar niet de eerste 2 maanden denk ik)

Presenting a new (small) project.


Kiss Catalog


It's an insanely simple Catalog System to keep track of your collections.

Some context

People who know me know I'm a bit of a collector.
Ok, some call it "hoarder" but I call it collector.
The difference between a collector and a hoarder is that the former knows what he has and keeps everything in good shape.
Still ... my retro computer collection is growing towards a point where I don't know exactly what I have anymore, or - more frequently - where I put it.
Questions like "I know I have this Amiga accelerator card, but ... where the heck is it?" need answers.

There's a ton of software already out there to help with that but I wanted something super-super-simple and with some very specific features.
As experience taught me: If it's too hard to maintain, it won't be.


  • Simple simple simple to maintain
  • Accessible from anywhere (which in my case always translates to "web based")
  • Everything should be searchable/browsable to quickly locate an item or to quickly show some overviews

When you start googling or asking around you get responses like. "Oh, an SQL database is what you need" or "There's an app for that, I use Collectorz or Numento"
No, no, no, nonono - been there done that. This is not my first attempt at cataloguing.
All other attempts stranded in

  • OR complex systems that took forever to maintain 
  • OR external platforms that ceased to exist...  

Did I mention it should be simple?
So: no database, no third party software, no fancy stuff.
Plain files and folders, plain JPG and .TXT files.

The concept:

You structure your collection in folders. Each folder can contain files and subfolders that further describe your item. Info is stored in plain text files. Images are stored in .jpg or .png. Any other file you add is just regarded as "file".
Then, a script is run that pulls all these files into data-structure.
This .json file is used to display a webinterface with browse and search features.
When you edit/add content from the webinterface, the local files are changed.
The "database" is always being generated from the local files. This means your data is your data: it lives in your folder as plain text files, completely outside Kiss-catalog.
If you stop using Kiss-catalog and delete it from your system, your hard cataloguing-work is not lost.

The main info file is called "info.txt"
The main image of an item is called "main.jpg"

If you want to display your collection on the web, simply put all your static files on a webhost.
No database or serverside processing needed.

That's it!

Everything runs

  • BOTH locally and remote 
  • BOTH as a static website and a somewhat full-featured dynamic Content-Management System.

There's a small demo collection at  (read only)
Still starting to populate it, first I have to FIND all stuff :-) 

And of course: Open Source and everything.
It's made for personal use, but you're free to give it a go. Feature requests are welcome.
It runs one Node but if that doesn't ring any bells there are also pre-compiled binaries for Windows, Mac and Linux

Kiss Catalog


These "design" decisions have some drawbacks:


  • Flat file "databases" only go that far, if your collections is reaching like a 100.000 items, Kiss-catalog is not for you
  • Because everything is generated from your local files, this might get slow with large collections. Also there's no image processing (yet) so all images are displayed "as is" : if you fill everything with 4K images, loading will be slow.
  • If I ever want to add features like "private files or folders" or whatever - I will probably have to settle for some naming scheme.
  • Likewise for "calculated" fields like prices etc. some convention will be necessary. 


The Philosophy

I've been pondering the last few months (years?) over something I call "sustainable software"
It's probably not a new concept but that's what I call it in my head. 
Basically it means that a developer should write software that is as simple as possible for the job.
Not because simplicity is a goal in itself, but because simple software lasts longer.
It's easier to maintain, consumes less resources, runs faster, ...

Developers should write software to last.
It's all too easy to quickly throw something together using the funky libraries and frameworks that today are considered "modern". Before you know it you're lugging along a staggering dependency tree and rely on a multitude of online services to get your thing built/compiled/deployed.

Yes, you're the cool kid on the block, but how will it look in a few years? Will it still build/compile/deploy?
If it's a fairly simple web-app, do you really need that 2 MB javascript package, 7000 lines of CSS and 4MB initial page load? Maybe ...

In this project "sustainable software" means:

  • no exotic or platform dependent file formats. plain text RULEZ
  • no external (web)platforms: it's the only way to make sure your data is still there in a few years time.
  • no code dependencies. again: it's the only way to make sure your system still runs in a few years time.
  • platform independent. everything should run on - and be maintainable from - whatever device you use. 

 Anyway - that's food for maybe another blog post - don't get me started on frontend builds that pull in ONE MILLION packages and takes 20 minutes and 8gig to build ... 

For now: Happy Cataloguing!


The past years I have been slowly tinkering on various Amiga Projects.
Mostly in JavaScript, mostly to unlock various parts of the huge Amiga ecosystem: parsing ancient filesystems and fileformats, reading and writing Amiga files with new tools, ...

Slowly all these various tidbits are coming together in the big plan: to break the Amiga out of it's emulated container and to seamlessly integrate in a modern OS.

That modern OS is platform independent. It runs on everything and it is accessible from everywhere.
For me, this translated to an OS that is web based. It runs in your browser and it lives in the cloud.

There have been many approaches to such an OS, some of them - like FriendUP - clearly have their roots in the Amiga system.
One of the most interesting ones is Amibian.js. It's also inspired by the Amiga and it runs in javaScript: Node.js on the backend, browser in front.

I've been talking with Jon - the creator of Amibian.js.
It's a HUGELY ambitious project, ranging from custom compilers in various programming languages to a recreation of an Amiga-like OS, complete with compatible system library calls and more.

When doing a modern Amiga inspired OS, one of the big questions is how you handle legacy software.
The Amiga has an old but super mature ecosystem of programs but sadly all that software doesn't run anymore on modern systems.
The solution is to emulate that old hardware so you can still run all that old software.
The most used Amiga Emulator is WinUAE, a glorious and ultra-advanced piece of code.
Rupert Hausberger did the daunting task of porting it to javascript.

The drawback of emulating an Amiga is that it is a contained black-box system that has no knowledge of the larger system it's running on. WinUAE handles this quite elegantly by allowing a shared filesystem, but in your browser there's no such thing.

This is where I stepped in: an emulated boxed Amiga running in your browser is cool, but wouldn't it be even cooler to break it open?
You could use Amiga software to seamless edit/play your local files,
or launch modern non-Amiga tools from within the Amiga,
or compile a program for Amiga with today's tools and launch it directly on an emulated 68k CPU
or ....

All this directly available on whatever system you use and wherever you are.

In the end, the underlying technicalities shouldn't matter.
It shouldn't matter what OS a program was written for, or where your files are exactly, or even who's physical machine you are using. Just launch your space and mold it to your liking.

Amibian.js already tries to break the barriers between the browser and your local system.
Browser or native? It shouldn't matter.

I will gladly help and try to break the barriers between the emulated environments and the native ones:
Emulated or native? It shouldn't matter.
The top video is a first demo of the progress. It shows various aspects of building such a system.
Most notably a shared filesytem so both systems (emulated and native) can access the same files.

Everything you see is running in the browser.
The (emulated) Amiga is on the right, the host system is on the left.
We're still doing babysteps: trying out stuff and laying the foundation for the bigger plan.

The concept is always the same: a seamless integration where it doesn't matter anymore where your files are or on what platform your program is running on.


During the past months I have been tinkering along on Bassoontracker - My browser based Retro Music Tool.
Today, it's ready for a next big release: Version 0.3.0 is out!

The most important feature is full FastTracker 2 compatibility. Yeah baby!

Fasttracker II was a music creation tool for DOS, released back in 1994 and it became THE standard for a long time for tracker based music.
1994 was also the year that Commodore went belly up, pulling the Amiga with them, so a lot of Amiga musicians made the jump to PC around that time, finding Fasttracker 2 as a perfect successor to Protracker.

Fasttracker is quite a bit more complex then a simple "sequencer". It added proper "Attack Decay Sustain Release" to instruments making them sound far more natural  and supported 16 bit samples, a huge step up in quality.
Up to 32 channels are supported, 128 instruments, 2 concurrent channel effects and much much more ...
That was fun to implement!

Other big changes are:

  • Dropbox integration: Load and save files directly from/to your Dropbox
  • Enhanced Sample editor: Slice and transform your samples directly inside BassoonTracker
  • Enhanced Pattern editing: use ranges and cut/copy/paste for quick editing
  • Export your song to .wav or .mp3
  • LOTS of fancy UI updates

And all that still in plain old javascript with ZERO dependencies.

BassoonTracker Sample Editor

During the years many thousands of music tracks have been made and you can access them all through the build-in Modarchive and browsers. (Which now have been expanded to include FastTracker .xm files too)

The playback engine has gone through extensive compatibility testing but if you find a module that doesn't sound the way it should: drop me line.

More info and full source code on Github
Or check out the live demo on

So .. after 25 year there's a new update for the Classic Amiga Operating System.
yes, that's right: TWENTYFIVE YEARS after AmigaOS 3.1, there's now Amiga OS 3.1.4
That's nothing less then a small miracle.
25 years in computer land is like 12 gazillion years in normal time.

Recently there a big revival for Amiga computers with a lot of very interessing projects being done by enthusiasts - new software - new hardware ... the works!
The 'Official companies" are still plotting along - if they take a short break from suing each other, that is - but the most interesting ones are pure community projects, created out of pure love for the platform.

A VERY interesting one is the Terrible Fire 328 : an expansion card for the CD32 with extra ram, video out and an IDE interface, usually used to attach a bootable CF card.

Long story short: the TF328 transforms the CD32 in the coolest of all Amiga's.

But .... that new Workbench 3.1.4 still looks a little dull.

Amiga Workbench 3.1.4

On the left is the default installation (4 colors) - Mason did create some new icons and after some copy commands it looks likt the picture on the right.
Already much better.
However ... the CD32 looks like this:


That mundane light gray and blue theme is really much too mundane for it's black and red looks.

The challenge is that this is a machine from 1993 and it's doesn't have the super fast graphic cards of today with millions of colors on 4K displays.
Allthough the Workbench can display up to 256 colors at the same time, that mode is too slow to be practical and it's more sane to only use 16 or 32 colors on a resolution of 640 on 480 pixels.
The even bigger challenge is that these colors are shared amongst all applications so each application has to adapt its colors to the ones available.
You can lock some colors (for examples for your icons) - and the other free colors can be free asigned - or battled for - by other applications.

So ...
I made a custom WorkBench theme - especially for the CD32.


16 colors (and Copper Demon for the window gradients)
Made for square pixel screen modes (Pal hires laced e.g.)

This is the Palette:

Although it's possible to run this in a 16 color WorkBench, it's recommended to use at least a 32 color screenmode.
That way you can also set the MUI colors and still have some pens left for other programs.

Color Locker and Border Blanker recommended!


  • First made in Photoshop,
  • then color-reduced with (the super awesome)
  • then cleaned up and re-dithered by hand back in Photoshop
  • then cut out the icons and saved as NewIcons with Personal Paint on the Amiga

Everything is downloadable from here.

Some extra wallpapers and a description how to install are also there.

That was fun!

Presenting a new project:

Bassoon Tracker!

It's a Browser based old-school Amiga Music Tracker in plain old javascript.

Bassoon Tracker

If you have ever heard of Protracker or Fasttracker, then you know the drill,
if not, then you are probably too young :-)

Check it out at

Tracker music originated way back in 1987 on the Amiga computer.
This was an era where PC's only made bleep sounds.
Even as the Atari could produce some funky chip sounds, then there was this all-singing-all-dancing Amiga machine that could produce 4 channel wave-audio.
Ok, it was still 8-bit sound, but suddenly everybody could access a digital music creation tool for an affordable price where previously you would have to spend a fortune on hardware samplers and midi interfaces to get the same possibilities.
My first sampler I soldered myself: You could plug it into the parallel port of the Amiga to "record" analog audio signals into 8-bit samples. It produced very low quality samples, but ohh... the wonder of it all!

It also was en era where user interface design was non existent so yes: the interface is a bit ... "special" :-)

Bassoon Tracker Sample Editor

Tracker programs where made by developers for developers: You don't enter notes on a musical bar, you enter notes as numbers in a grid with your computer keyboard and you apply effects by entering even more numbers.
All in hexadecimal of course, as plain decimal number are for pussies.

I especially like the format because you sort of get the sheet-music AND the instruments together with the song.
If you hear a cool piece and go like "Wow, how did they do that?" you can jump right in and examine what samples are used and what effects are applied.
It's like an open-source music format where you can do a "view source" to see exactly how it's done and fiddle with it, much as you can do with any website or web application.

Just like much of my early javascript and css knowledge was build by inspecting the source of other applications, much of my early musical knowledge was build inspecting mod files on the Amiga.

The golden age of the Amiga is long gone, but the tracker format lives on. There have been countless spin-offs and remakes.
Even in modern audio software like Renoise, Radium and Sunvox the tracker spirit is present.
And of course there's openMPT: It doesn't have a cool and snazzy interface but it's the most compatible and complete true tracker around.

Remember: these are not just mp3 files you hear, the music is reproduced using samples that are played and manipulated in sequence in real-time.
This is why mod files in general are quite small, making them perfect for (early) games and other projects where file size is important.
Even the super popular Unity game platform still has support for tracker formats

Playing mod files in a browser is nothing new, but still I wanted to create my own tracker for the following reasons:

  • I wanted to research Web-Audio, especially real time audio manipulation.
  • I wanted a real tracker where you can open, edit and save mod files, not just a player.
  • It should perform well on mobile browsers.
    Most mod players don't work that well on mobile browsers.
    They tend to implement a very low level way of handling audio, doing the resampling and mixing all in the javascript layer, maybe because the code is ported or recompiled from other platforms.
    I took a high-level Web-Audio approach which makes it perform really well on mobile browsers. Even if the UI slows down, the music should never stutter.
  • I wanted to build a SCALABLE cool retro user interface.
    Most old-school trackers have a fixed size user interface.
    I wanted a pixel-retro interface that scales with the screen.
    You could call it "responsive design" but then for HTML canvas :-)
    That's a pretty cool feature even if I say so myself!
  • I wanted to have a decent music playback engine to be able to build upon: a drum-sequencer? a midi-player? real-time online collaboration? all rather straightforward once the main playback engine is in place.

Anyway - here are some examples!

Even more?
The ModArchive hosts thousands of tracker songs and they have an API so you can directly access them from within Bassoon Tracker.

The source files are available on GitHub.

Have fun, and if you think of any cool feature you're missing: let me know!

a picture called verderspoelen.jpg (click to enlarge)

Hoe blind kun je zijn?

Erg blind, zo blijkt.
Peter Quaghebeur (Vroeger VTM baas en nu baas van SBS: Vier en Vijf) staat in het Vlaamse Parlement te jammeren dat de inkomsten van zijn bedrijf kelderen
De Vlaming kijkt immers meer en meer "uitgesteld" en spoelt dan vlotjes de reclame door. hoe ongehoord!
Als er niets verandert is zijn bedrijf over 2 jaar dood.

Wacht wacht wacht, is dat diezelfde Peter Quaghebeur die vorig jaar tegen de uitgevers wereld "Pas je aan of sterf!" stond te roepen?
Ja dus!

Euhm ... ok ... pas je dan aan, hé!
SBS is een commercieel bedrijf.
Neem nu eender welk commercieel bedrijf dat zegt "Oei oei oei, mijn business model werkt niet meer, mijn klanten lusten mijn product niet meer waardoor mijn inkomsten dalen" Dan is het antwoord toch ALTIJD "ja, verzin dan iets anders wat je klanten wel lusten" ...

Als je product niet gesmaakt wordt, gaat je bedrijf op den duur kopje onder.
Dat is zo, en dat is goed, want dat zorgt voor innovatie.
Dat zorgt voor een constante drang - nee: verplichting - om jezelf steeds opnieuw in vraag te stellen en om je product te verbeteren.

Waarom staat die meneer Quaghebeur dan in het parlement te piepen?
Medialaan, die andere grote zuil, stelt als mogelijke oplossing "ondoorspoelbare advertenties" voor.
Dat is onder het motto van "oh ja, laten we ons product NOG irritanter maken, dat gaat vast goed werken"

Op dezelfde dag laat Netflix fijntjes weten dat ze 400 banen extra creëren in Amsterdam. Hun totale investering in Europese producties bedraagt al 1.75 mijard.
Dat gaat lekker blijkbaar, daar bij Netflix. En dat allemaal zonder reclame tussen hun aanbod!

Gebruikers betalen voor comfort, voor het wegnemen van wrijvingen en frustratie.
En dan komen ze met "ondoorspoelbare reclame" ... ja man ...#schud-meewarig-met-het-hoofd#

Ik denk dat wij een tamelijk doorsnee gezin zijn.
De kinderen kijken Netflix en Youtube - daar hebben ze meer dan genoeg aan.
De digicorder blijft meestal gewoon uit, nog af en toe een programma van Jani of Tom Waes; die zijn leuk.
Altijd uitgesteld, enkel de koers is live. (en het songfestival uiteraard!)
Nooit naar VTM, niet omdat het slechte programma's zijn maar omdat je daar bij Telenet de reclame niet kan doorspoelen als je uitgesteld kijkt.

Ja, er is en Stievie, maar dat is slechts met omwegen op het grote scherm te krijgen, veel te veel gedoe.

Wordt eens wakker, Peter,  en doe je ogen open. Verwijt anderen niet in de tweede versnelling te blijven steken als je zelf niet veel hoger schakelt.
Dump desnoods Telenet en Proximus en ga rechtstreeks naar de klant, geef je klanten wat ze willen en als het lekker is betalen we daar voor.
Dump die reclameblokken en zoek andere manieren, desnoods via product placement in je programma's of via commerciele randactiviteiten.
Trek uitgesteld kijken op naar 1 maand, 1 jaar of eeuwig tegen extra betaling. Technisch is er geen enkele drempel.

Geef SD gratis weg en reken aan voor HD of 4K.

Er is een overaanbod aan entertainment.
Met een beetje moeite is alles gratis te vinden.
Nogmaals: gebruikers betalen voor comfort, het wegnemen van irritatie en een fijne, persoonlijke ervaring.
Een Vlaamse zender met goede content, zonder reclame, liefst met persoonlijke aanbevelingen in plaats van lineair, gemakkelijk consumeerbaar op elk scherm? Yep, daar wil ik gerust voor betalen. Laat maar weten als je mijn centen wil hebben.

Komaan man, je kan het!

a picture called ragdace.png (click to enlarge)

Na veel stoereventenpraat van "we zouden eens een bandje moeten beginnen" is het er van gekomen:

Rag Dace!

Bram mept op de drums en doet enthousiast.
Stef pluk wat aan de basgitaar en doet wat met knoppekes.

Zingen? Ja, dat ook hé, in het schoon Antwerps en al.

Wat we missen aan techniek en talent, maken we dubbel goed met speelplezier en de bijhorende Antwerpse charme.

En we geven zelfs ons eerste optreden: voor het goede doel!
In het kader van een ALS benefiet kunt ge naar onze kapriolen komen kijken en luisteren op vrijdagavond 21 april, Wolffaertshof Baron van Ertbornstraat 7, 2630 Aartselaar
Zie da ge op tijd zijt, want na ons komt de ECHTE band van de avond: The Armstrongs.

Wil je bij dit NU al legendarische optreden zijn?
Da kan hé mannekes: 
Kaarten zijn hierzo te verkrijgen: (of gewoon bij ons)

Alle opbrengsten gaan integraal naar het goede doel.
Zie daggeder zij!

Meer info op

Op zondag 27 november deden we mee met het Belgisch Kampioenschap Powertool dragracing.
Ow Yeah!

Het concept is simpel: Je neemt een elektrisch handgereedschap en je vormt dat om tot iets dat zich kan voortbewegen. Je hebt een baan van 20 meter en een start/stop knop. Je racet met 2 tegen elkaar en wie als eerste de finish bereikt is gewonnen.
What can possibly go wrong? :-)

We begonnen met een bandschuurmachine. Dat schiet al aardig vooruit als je dat niet vasthoudt, maar is ook wel wat saai en voor de hand liggend. Dat kan beter!
Een oud kinderfietsje met in plaats van trappers een stevige slijpschijf. Dat werkt, maar de motor van de slijpschijf levert duidelijk veel te weinig vermogen: na een paar meter smeult de plastic behuizing er net niet af.
Daar dienen tandwielen voor natuurlijk!
Wegens gebrek aan reuze-fietstandwielen tekenen we een T78 tandwiel (met 78 tanden dus) en nog een paar kleintjes.
Bram heeft connecties en kan het rap laten uitlaseren uit 3mm staalplaat. Handig, zo'n Bram-gerief in de buurt.
Wat mep- , slijp- en laswerken verder is ons Frankenstein geval klaar.

Van de 19 ingeschreven ploegen verschijnen er 16 met een rijdklaar vehikel aan de start.
Goed om te zien dat de funfactor en teamspirit overheerst.
ATV en de VRT zijn present, de kinderen worden geïnterviewed door Karrewiet. Plezant.
Na een paar gewonnen races komen we onze meerderen tegen en begint ons ding ook al wat uit elkaar te vallen.
De rubberen groeven van de schuurband zijn spiegelglad geworden, ons steunwieltje is door de wrijvingshitte vastgesmolten aan zijn as en door een iets te harde botsing met de finish breekt uiteindelijk de as van de slijpschijf af.

Toch een 5de plek. Niet slecht!

De overwinning gaat uiteindelijk terecht naar het dodelijk efficiënte "Atelier Vilvoorde".
Mijn persoonlijke favoriet is toch wel team "LaDa" die alles ge-3D-print en uitgelasered hebben. Schoon gerief, maar door de harde finish-botsingen breken hun verbindingen en grondplaat door en stranden ze in de finale.

Yep! Dat was een plezant projectje met plezante vrienden en zonen - dat mag nog!
Dikke merci aan Anthony voor de organisatie.

I totally love my Sonos system.
The Sonos players are expensive but they are worth every penny and i haven't regretted any of my Sonos purchases for a minute.

There's one thing missing though ... hardware buttons!
Even as a smartphone or tablet to control your appliances is perfect (remember 2009?), sometimes you just don't have your smartphone ready at hand and you find yourself hunting for your smartphone to control your Sonos.

Yes, each Sonos has some hardware buttons, but they are only used to play/pause the current song, or to adjust the volume of that particular player.

Enter D.I.Y.
I'm a big fan of old tube-based radio's. If they are not too far gone they get repaired, otherwise they just look cool.
One particular little radio-bugger was beyond salvation and received another purpose: controlling the Sonos with some presets, volume and play/pause with its old-school tactile click-clack buttons.

The final contraption looks like this:
Sonoscontroller main

very incognito. looks like a radio, no?

On the inside the buttons are wired to a little Arduino.
When you press a button or turn the volume knob, one of the digital or analog inputs of the Arduino is activated, allowing you to define a resulting action in software.

Sonoscontroller hardwarebuttons


There's a little WiShield attached to the Arduino allowing it to communicate over wifi with other devices.
Although it's possible to talk to the Sonos devices directly using the UPnP protocol, it's easier to use a some sort of middleware like the excellent Sonos Http Client by Jimmy Shimizu .

Sonoscontroller arduino


The WiShield is rather old in terms of IT-gadget-age and its libraries are not compatible with the current generation of Arduino IDE.
I had to patch them a little to make them work on Arduino 1.x and up. You can find my fork here.

The little Arduino sketch that controls everything is also on my GitHub.

A little status led completes the setup, giving some feedback on your actions.

Sonoscontroller colors

With the radio buttons i can now activate the 5 presets we use the most, change the volume of the grouped sonos speakers and pause/play everything.
The presets are currently 3 radio stations (Studio Brussel, Radio 1, Radio Nostalgie), the Spotify favourite list (starred tracks) and a random Spotify playlist.

Due to some wonderful coincident the labels of the buttons also EXACTLY match the preset they trigger:

Sonoscontroller button map

How convenient!

The concept is a bit hard to explain to people who don't have a wireless speaker system.
Most of the time they just stare blankly and go
"Uhm ... so you've build a radio that you can use to ehm ... turn on the radio? ... Ok ... cool ..."

Just like software controllers as Ableton Live end up up creating matching hardware controllers with LOTS of buttons, let's hope this is the start of a trend.
There's nothing like the feeling of pressing a big chunky button down and make it go *CLACK* , far more satisfying than using the non-tactile buttons of a touchscreen controller ... .

Hmm, I still have this thing somewhere in my garage ... what still needs controlling?


Read more