Bar 017
Where it goes

What sponsorship pays for

01

Test controllers

Mapping a controller properly means having one on the desk. Funding buys the hardware the generic maps are checked against.

02

Release work

Packaging, signing and testing builds for each platform as the port to Windows and macOS begins.

03

Hardware checks

Time to run the listening and latency checks that are still open on real audio interfaces.

Bar 033
How to give

Ways to give

Every option goes to the same place: test hardware and release work.

GitHub Sponsors

Monthly or one-off, through your GitHub account.

Open Collective

For companies and venues that need an invoice.

Lend hardware

Have a controller we don't support? Lending one is as useful as funding.

Bar 049
Contribute

Not ready to give? Contribute instead.

Feature requests, code and controller maps all help the project.

How to get involved