Audio Tools: a C++ library the index calls C, and the drivers live in another repository
Audio Tools (a powerful Audio library for Microcontrollers and the Desktop)
At a glance
- What is it?
- Audio Tools is a header-only C++ library that turns audio processing into composition of stream objects, on the model of the Arduino Print and Stream classes, delivered as an Arduino library, an ESP-IDF component and a CMake project. Reading its own page closely shows the language index reporting C, four build systems in one tree, a badge row where three of five links point at the repository itself, releases titled by month with one month skipped and the newest shipped a month after its own name, and the hardware driver layer sitting in a separate project linked only from a badge.
- Who is it for?
- Audio Tools suits someone who already has a board and a codec and wants a composable audio pipeline rather than one monolithic playback call, because the source, sink and transform objects are interchangeable and the loop body really is one line. It does not suit someone who wants a single dependency that can drive a speaker, because the driver layer is a separate repository and the page mentions it only in a badge.
- Can I use it commercially?
- Yes, with conditions. GPL-3.0 is a copyleft licence: if you distribute software that includes it, you must release that software's source code under the same licence. Running it internally without distributing it does not trigger that obligation.
- Is it still maintained?
- Yes. The repository last received commits 6 days ago.
- What is it written in?
- Mainly C, according to GitHub's language statistics.
Answers come from the project's GitHub data, last synced on November 15, 2026, and from our analysis. They are not legal advice.
Star history
- pschatzmann/arduino-audio-tools2,421 ★ · +31
| Repository | 2026-09-29 | 2026-11-15 |
|---|---|---|
| pschatzmann/arduino-audio-tools | 2.4k | 2.4k |
31 Stars in the last 47 days, measured from the daily GitHub snapshot. Compare with other projects
Editorial analysis
The language index reports C for a C++ library
The page describes the project in its own first line as header-only C++ classes, and every example in the file is fenced as C++ and uses constructors, default arguments and scoped types. The hosting site records the repository's primary language as C. The gap is easy to explain and still worth stating, because it is the sort of mismatch that filters a library out of a search. A design that imitates a duck-typed print-and-stream interface, where objects are wired by type and configured through a struct, is happy to compile as either language, and the tree contains the kind of build metadata that a C indexer weights heavily: a make-based component file, a component manifest, a CMake file, a library properties file and a documentation generator configuration. Add a submodules file and a native test directory, and the indexer has plenty of non-C++ evidence to weigh against the C++ sources. The practical note for anyone choosing a library by language is that this one is C++ and behaves like it, and the C flag tells you about the packaging more than the code.
One header-only library, four build systems
The tree carries the build metadata for four different toolchains at once. A library properties file registers it with the Arduino library manager, which is the route the first badge points at. A component manifest registers it as a component for a microcontroller vendor's build system, and alongside that sits a make-based component file, which is the older generation of the same ecosystem's build integration. A CMake file, with its own separate native test directory, covers building on a desktop. And a documentation generator configuration produces the class reference hosted on a project pages site. The one-line example the page gives is therefore not a single command but a choice, and the page does not actually make the choice: it says the functionality provides the glue that makes different audio processing components and libraries work together, points at a wiki page listing optional libraries, and notes that depending on the example you may need to install some of them. Three of the fifteen capability bullets are really about this choice, covering communication, digital signal processing library integration, and running a sketch on a desktop.
The hardware drivers are a separate project, mentioned only in a badge
The first five badges are the only place the project's dependencies are visible, and they are worth reading as a list rather than as decoration. One links to the Arduino library reference. One links to a separate repository, an audio driver project by the same author. One links back to this repository. One links directly to this repository's CMake file. And one links to the GNU General Public License page. So the badge row that should carry a build status, a version and a licence badge instead carries three self-referential links, and the one piece of genuinely important information on the page, that the drivers live elsewhere, is a bare link in the middle of them. That matters more than the badge convention. This library is header-only and it contains sources, sinks, encoders, decoders, effects, filters, converters, buffers, generators and players, and none of those is a driver. The class that turns a serial peripheral into an output stream lives in the other project. A reader who installs only this and follows the worked example, which instantiates a digital output stream and calls begin on it, will not get audio out of a board without adding the second repository.
The whole pipeline is three stack objects and a one-line loop
The design philosophy is stated as following the Arduino conventions, and the mechanism is that Arduino's print and stream classes have been extended to audio. Audio data is read from a source and written to a sink, every component gets begin and end, and the pieces compose because they share an interface rather than a base class you must name. The worked example shows the consequence:
MemoryStream music(StarWars30_raw, StarWars30_raw_len);
I2SStream i2s; // Output to I2S
StreamCopy copier(i2s, music); // copies sound into i2s
...
void loop(){
copier.copy();
}Three objects constructed on the stack, a copier that binds the other two by type, and a loop body of one call. The sample itself is a generated header providing the raw bytes and a length symbol, so the audio lives in the sketch's flash rather than on storage. Configuration follows the same shape: each stream exposes a configuration struct, a call returns a default proposal the page says will usually just work, and you override the fields you care about before passing it to begin. The page's own demonstration that the abstraction holds is a one-line swap of the output class for an analog one, which converts the same pipeline from digital to analog output with no other change.
Logging is a runtime call, and getting rid of it is a header edit
The logging section is short and unusually candid about why it matters on this hardware. The library has a built-in logger, defaults to the warning level, and writes to the serial port. You raise it at runtime with one call:
AudioToolsLogger.begin(Serial, AudioToolsLogLevel::Debug);with four named levels from debug to error, and any object derived from the print class accepted as the destination, so the log can go to a file or a network stream using the same interface the rest of the library already relies on. Then comes the part that matters on a microcontroller. Turning logging off is not a build option or a constructor argument. It is a preprocessor define in the library's configuration header:
#define USE_AUDIO_LOGGING falseand the stated reason is to decrease memory usage. So a user who wants the debug output out of their build has to edit a header inside the library, which is a thing a build system would normally do for you and a thing a header-only library cannot. It is a small decision, correctly reasoned and plainly stated, and it is the same class of manual step as a static-versus-shared define in a native library.
Releases are titled by month, one month is missing, and the newest is late
The three most recent release titles are month names rather than descriptions of what changed: an August 2026 release, a June 2026 release and a May 2026 release, against patch tags one point two point four through six. Read as a sequence, they tell you two things. There is no July release, so a month went by with nothing. And the August release was published on the second of September, a month after the month in its own title, while the May and June releases were both published inside the months they name. So the naming is a calendar, not a changelog, and it is a calendar with a gap and a late entry. That is a coherent choice for a library whose releases are regular enough to name by month, and it is a poor choice for anyone trying to answer what a given version does. The tree does hold a changelog-adjacent artefact and a documentation generator configuration, and the wiki carries an introduction and an examples page, so the narrative is there; it is just not on the release.
Fifteen capability bullets, a video player, and a note frequency table
The list of what the library provides runs to fifteen bullets, each linking either into the wiki or into a class page on the generated documentation. It covers sources and sinks, encoders and decoders for three named formats plus others, an audio player and a video player, audio input and output over USB, integration with external signal processing libraries, communication over a wire or wirelessly, sound generators, sound effects with four named examples, a three-band equaliser, converters, filters, musical notes with their frequencies, buffer implementations feeding a queue, a repeating timer for sampling at exact times, and building the same sketch for three desktop operating systems. Two entries in that list are worth flagging for a library with this name. A video player is in scope, which is a deliberate widening rather than a stray. And a table of musical note frequencies is shipped in the header, which on a microcontroller is a real cost in flash for a data structure rather than an algorithm. Neither is wrong. Both are the kind of thing you discover after choosing the library rather than before.
The page names three desktop systems, one of which is spelled the old way
The desktop integration bullet says the same sketches can be built to run on Linux, Windows and a third operating system whose name on the page is the spelling that was current before a rebranding several years ago. It is the only stale word in an otherwise current document, and it is in the bullet a user reads when deciding whether this works on their machine. It is a small thing, but it is a useful signal about the maintenance profile: the code is actively worked on, with a commit in the last few days and a release most weeks, while the prose is corrected opportunistically. The same applies to a typo in the same paragraph, where the sentence about needing extra libraries misspells the word, and to a phrase in the configuration paragraph that uses a possessive where an article belongs. None of these would justify a section on its own. Together, with the release titles and the badge row, they describe a project whose engineering is current and whose documentation is maintained in whatever gap a contributor happens to notice.
Editorial conclusion
Audio Tools suits someone who already has a board and a codec and wants a composable audio pipeline rather than one monolithic playback call, because the source, sink and transform objects are interchangeable and the loop body really is one line. It does not suit someone who wants a single dependency that can drive a speaker, because the driver layer is a separate repository and the page mentions it only in a badge. Before you start, check which driver project your board needs and add it deliberately, because nothing in the main list of capabilities tells you the hardware layer is elsewhere. If you are picking a version, note that the release titles are month names rather than change descriptions, one month has no release at all, and the newest tag is titled for the month before it shipped. And if you are on a microcontroller with tight memory, read the logging section before anything else, since turning the log off is an edit to a configuration header rather than a build option.
Frequently asked questions
how to install arduino audio tools
The library is header-only C++ registered with the Arduino library manager, and the page's badge points at the Arduino library reference for that route. It also ships component metadata for a microcontroller vendor's build system, in both a modern manifest and an older make-based file, plus a CMake project for desktop builds. The page gives no single install command and defers to a wiki page on optional libraries.
Can I play audio with an Arduino?
The worked example does exactly that, streaming a sample held in flash to a digital output stream at a stated sample rate, channel count and bit depth, with the loop body reduced to a single copy call. The page also notes that swapping the output class for an analog one gives analog output instead, with no other change to the pipeline.
Does arduino-audio-tools include the hardware drivers?
No. This project is header-only and provides sources, sinks, encoders, decoders, effects, filters, converters, buffers, generators and players. The driver layer that turns a peripheral into an output stream is a separate repository by the same author, linked from the badge row at the top of the page rather than from the capability list or the install section.
What audio formats does arduino-audio-tools decode?
The page names MP3, AAC, WAV and FLAC among the formats supported by its encoders and decoders, and says the list is not exhaustive, with the per-class detail in the generated documentation. The decoders are composed through the library's encoded-audio stream class rather than used directly.
How do I turn off logging in arduino-audio-tools?
Two levels exist. At runtime you can set the level with a single call on the logger, choosing debug, info, warning or error and any object derived from the print class as the destination. To remove logging entirely and reduce memory use, the page says to define the logging switch to false in the library's configuration header, which is a source edit rather than a build option.
Official sources
Add this badge to your README
If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.
[](https://hysenlabs.com/projects/pschatzmann-arduino-audio-tools)Star history chart for your README
[](https://hysenlabs.com/projects/pschatzmann-arduino-audio-tools)Was this useful?