Uploaded February 2025 | Updated September 2026, 6 hours ago
Attendees: Marek Walaszek, Wojtek Pilwinsli, Kacper Tymiński, Jay Pocknell, Haim Kairy, Athan Billias
Notes
Bettermaker added sysex commands from their plugin for most events. Updated plugin can be downloaded here
Haim released a working version of the speech server that accepts the above sysex commands and converts them to speech. The server runs in a browser window and can be run locally without the need for an internet connection. The server is developed with js, html and css. No package installation or prerequisites needed.
It would be great to add a “clipping” alert of input level from the BM plugin, since this is a real-life use-case that can be helpful for all users, not exclusively for visually impaired, which demonstrates how inclusive design improves the user experience for everyone.
Sam and Haim should start working on demoing voice commands for controlling the vSPE. We don’t have to go crazy with this and support full functionality, but rather focus on a few commands (even one) that we can get to work reliably to demonstrate the concept of voice control.
Demoing at NAMM: Haim should reach out to Andrew and Lawrence to finalize how much room we need and how everything will be displayed. Marek can provide an iMac for the demo, along with a vSPE.
We should create a 1-2 minute video that showcases this demo. We can start by editing a google doc with ideas for a script. We can start with this (suggestion only). Feel free to add your comments and edits in the doc. Here's a link to the doc
There’s an opportunity to demo in AES Warsaw and soundcheck. Athan and Marek should open a dedicated discussion on this.
Attendees: Marek Walaszek, Wojtek Pilwinsli, Kacper Tymiński, Jay Pocknell, Haim Kairy, Athan Billias
Notes
Bettermaker added sysex commands from their plugin for most events. Updated plugin can be downloaded here
Haim released a working version of the speech server that accepts the above sysex commands and converts them to speech. The server runs in a browser window and can be run locally without the need for an internet connection. The server is developed with js, html and css. No package installation or prerequisites needed.
It would be great to add a “clipping” alert of input level from the BM plugin, since this is a real-life use-case that can be helpful for all users, not exclusively for visually impaired, which demonstrates how inclusive design improves the user experience for everyone.
Sam and Haim should start working on demoing voice commands for controlling the vSPE. We don’t have to go crazy with this and support full functionality, but rather focus on a few commands (even one) that we can get to work reliably to demonstrate the concept of voice control.
Demoing at NAMM: Haim should reach out to Andrew and Lawrence to finalize how much room we need and how everything will be displayed. Marek can provide an iMac for the demo, along with a vSPE.
We should create a 1-2 minute video that showcases this demo. We can start by editing a google doc with ideas for a script. We can start with this (suggestion only). Feel free to add your comments and edits in the doc. Here's a link to the doc
There’s an opportunity to demo in AES Warsaw and soundcheck. Athan and Marek should open a dedicated discussion on this.
![Audio Developers Conference Music Accessibility Standard Presention
As the audio industry seeks to improve diversity within its workforce, and the music industry seeks to widen the diversity of artists creating music, it is essential that the inclusion becomes woven into the design of the tools available.
But what do terms such as accessibility and inclusive design actually mean?
How might you begin to adopt inclusive design practices so that your software becomes accessible to a wider audience?
What are some of the big-name audio companies doing to support accessibility and how can you learn from their experience?
How can companies take practical steps, together, to act on a shared desire for a more inclusive industry?
These are the kind of questions that this workshop seeks to answer.
Workshop outline
The format of the workshop will be as follows:
1. Introductions and updates from panellists, sharing insight into their companies recent and future work on accessibility (45 mins).
2. Pre-recorded updates shining a light on other accessibility-related projects from across the industry (20 mins).
3. An overview of accessible GUI design in JUCE (30 mins) – Harry Morley (Focusrite). Harry will:
Tour the Focusrite Control 2 software to introduce the common accessibility-related terminology.
Share his experience of working on Focusrite’s Scarlett and Vocaster software, using the JUCE toolkit to make this software accessible to screen reader users.
Explain key concepts such as screen reader focus and keyboard focus, control grouping, and focus priority order.
Share useful learnings and tips for working with JUCE, and other things to be aware of.
Suggest approaches to testing accessibility directly, working with visually impaired beta testers, and collaborating with the user community.
[10-minute break]
4. Panel discussion: a collaborative approach to inclusive design in audio products (30 mins).
How do we make the most of the shared desire for an industry that is more inclusive to disabled engineers and artists?
A look into the MIDI Association’s proposed ‘Music Accessibility Standard’ so far, and more.
5. Roundtable discussion in response to audience Q&A. Attendees can contribute in person, or via Zoom Q&A or Discord. If you encounter barriers to accessing these platforms, please send questions to: contact@soundwithoutsight.org
Panellists
Speaking in person
Jay Pocknell (RNIB)
Harry Morley (Focusrite)
Tom Poole (JUCE)
Adil Ghanty (Native Instruments)
Scott Chesworth (Freelance Accessibility Consultant and Trainer)
Martin Keary (Muse Group)
Arvid Johnsson (Softube)
Joining remotely
Athan Billias (MIDI Association)
Adi Dickens (Ableton) Audio Developers Conference Music Accessibility Standard Presention](https://i.ytimg.com/vi/z9YUxYfU2Mg/mqdefault.jpg)



