We’ve been developing new control interfaces for Sonic Pixels – alternative ways to trigger the devices using the Open Sound Control (OSC) based messaging protocol Andrew Robinson, project lead of CodeBug, developed as part of updating the original hardware – a BBC Micro:bit, MP3 player module and 5V audio amplifier mounted on a custom-designed PCB – with a custom micro-controller board based on his CodeBug Connect.
While James Medd overhauled the Python/JavaScript/MaxMSP middleware on a Raspberry Pi and iPad Pro interface – and it works well enough – we’ve realised that the control system needs to more flexible and accessible – to fit more easily with sonic artists’ existing workflows rather than require learning and applying a new and unknown interface and arrangement approach.
We subsequently worked with Sonic Pixels @ Barton Arcade contributing artist Jaydev Mistry to work up an alternative interface using the more physical and tactile Novation Launchpad Mk2 with openFrameworks middleware on a MacBook Pro. A demo video of ‘work in progress’ below:
We also invited audiovisual artist Joe Beedles to play with the system – and he created his own control interface in MaxMSP. A short video of Joe testing his interface with his own sound palette loaded onto the units below:
While these are just experiments – it’s shown that Sonic Pixels can be controlled in a number of different ways. So a useful next stage development could be to develop a residency programme for selected artists where they get the chance with support from a small technical team to work with the system intensively to develop their own personal control system and interface using the Sonic Pixels messaging protocol. We can then share these custom interfaces as a ‘suite’ of ways to control the system.