Audio-Reactive Visualizer Software Compared: Synesthesia vs modV vs Tawny AV

What is Synesthesia and who is it built for?

Synesthesia is a closed, commercial VJ app built around a curated, MIDI-mappable scene library. It ships 80 built-in scenes plus 20+ free community ones, and an in-app marketplace where artists sell more, so you can be running quality visuals within minutes of installing it instead of building a set from scratch.

Every control surface in the app maps to MIDI and OSC. Assign a fader to a scene parameter and you're driving it live from a nanoKONTROL2, or whatever you've got, in seconds. No patching required. Audio analysis runs through Synesthesia's own algorithms, translating beat, energy, and frequency bands into scene motion automatically, so scenes react out of the box without you routing a single signal.

Scenes are written as GLSL pixel shaders. Import them from Shadertoy or the ISF format, or write your own in the app's built-in live-coding editor if you want something fully custom. Video, logos, and webcam feeds drop into the same effect chain as the generated scenes, and output routes through Syphon or Spout on macOS, or NDI over the network to other software, a projector, an LED wall, or a livestream encoder.

The tradeoff is access. Synesthesia runs on macOS and Windows, licensed per seat through the app's own store, and there's no source to inspect or modify. You're buying a finished instrument, not a starting point.

What is modV and how does its open-source model change things?

modV is a modular audio visualization environment built on web technologies, and it's free. The whole project is MIT-licensed and open source, maintained by a small team on GitHub with 495 stars, 31 forks, and 593+ commits on the main branch. No purchase, no per-seat license, no marketplace gatekeeping what you can build.

It runs on Windows, macOS, and Linux (Debian and Ubuntu need the libndi4 package), and since the core is JavaScript and WebGL, there's a browser-based mode too. Under the hood: Vue.js for the interface, Electron for the desktop shell, WebGL and Canvas for rendering, and the Web Audio API, via the Meyda library, for audio feature extraction like RMS level and spectral bands.

Visuals get built by chaining "modules" (2D canvas modules, ISF shaders, or raw WebGL/GLSL shaders) into a signal-flow graph, and any parameter in that graph can bind to an audio feature or a MIDI controller. None of that needs code. modV's own workshop curriculum runs beginner to intermediate across five sections, and the GUI alone covers interface navigation, module composition, audio binding, blending, and live performance setup with MIDI.

Coding only enters the picture if you want to write a custom module — JavaScript for 2D modules, GLSL/ISF for shader ones. The project's wiki specifically recommends ISF over raw WebGL for custom shader work, because its structured parameter format gives modV better debugging information to surface when something breaks. NDI input and output is built in for routing video between machines. And because there's no official scene marketplace, the community trades modules through the wiki and Discord instead, which also means there's no vendor support line if something goes wrong mid-set.

What is Tawny AV and what does buying source access get you?

Tawny AV is a live audio-visual tool built by a single developer, Leon Stansfield, generating procedural visuals from microphone input in real time and detecting beats to trigger scene events. Its modular scene system mixes two rendering approaches in the same tool: GPU-accelerated GLSL fragment shaders for smooth, high-framerate visuals, and CPU-based simulations, like cellular automata, for effects that don't map cleanly onto a shader.

Buying it includes access to its source code, which puts Tawny AV closer to a hackable starting point than a finished touring product. Scenes, color palettes, and background images are all user-editable directly in the files you get.

That access comes with real gaps, though. Tawny AV currently ships for Windows and Linux only — no macOS build. There's no documented MIDI or OSC control surface, so scene parameters aren't mappable to a hardware controller the way they are in Synesthesia or modV. No built-in scene marketplace or NDI-style network routing either. The listing is upfront that the tool is under active, single-developer development and not yet feature-complete, which is the right expectation to bring into a purchase.

Synesthesia vs modV vs Tawny AV: platform, licensing, and control compared

Two contrasts matter more than the rest of the row-by-row detail. Source access splits modV and Tawny AV from Synesthesia: both give you something to open up and modify, Synesthesia doesn't. Control surface splits Synesthesia and modV from Tawny AV: both map to MIDI/OSC out of the box; Tawny AV currently documents none of that, which matters a lot if your set leans on a hardware controller.

Which audio-reactive visualizer should you pick?

Pick Synesthesia if the gig is tomorrow and you want a curated scene library plus reliable MIDI mapping without building anything yourself. You're paying for polish and a working control surface on day one.

Pick modV if you want a free, cross-platform, inspectable tool you can extend with your own modules without spending anything. The GUI covers most live-performance needs on its own; JavaScript or GLSL only come up if you push further.

Pick Tawny AV if you want a cheap, hackable, GLSL-and-simulation playground and don't mind an unfinished tool with no MIDI surface yet. It suits someone who wants to read and rewrite the scenes, not someone who needs a controller-driven rig this weekend.

None of the three do dither, halftone, or ASCII-style pixel processing natively. That's not a reason to rule any of them out — it's a separate layer that sits downstream of whichever one you pick.

Can you run kott's effects on top of Synesthesia, modV, or Tawny AV output?

Yes, as a second stage, not a replacement. Each of these tools generates the audio-reactive motion; kott sits downstream and applies a pixel-level treatment to whatever comes out of them. Route a visualizer's output over Syphon, Spout, or NDI, depending on which tool you're running, into a second layer for that treatment before it hits the projector or the stream encoder.

A halftone pass reads very differently on generative motion than on a static photo, so it's worth testing before a show rather than during one. Try it on a recorded clip first: run it through kott's halftone effect. The same goes for a dither pass — kott's riso-style dither treatment can flatten a busy shader scene into something with more contrast and less noise on a cheap projector.

This isn't a claim that kott replaces the audio-reactive engine in any of the three tools above. It's a treatment layer that sits after them in the chain, for anyone who wants the visual language of dither, halftone, or glitch on top of live audio-reactive motion.

Frequently Asked Questions

Is Synesthesia, modV, or Tawny AV free?

modV is free and open source under the MIT license. Synesthesia is a paid commercial app with a per-seat license and an in-app scene marketplace on top. Tawny AV is a paid one-time purchase that includes its source code, built and maintained by a single developer.

Which audio-reactive visualizer works on macOS?

Synesthesia and modV both run on macOS (modV also covers Windows, Linux, and a browser mode). Tawny AV currently ships for Windows and Linux only, with no macOS build.

Do these tools support MIDI control for live shows?

Synesthesia and modV both expose MIDI and OSC mappable controls, so a nanoKONTROL2 or similar controller can drive scene parameters live. Tawny AV doesn't document a MIDI or OSC control surface as of its current build.

Do I need to code to use modV or Tawny AV?

No, not for basic use. modV's GUI lets you chain and bind modules to audio features with no coding; JavaScript or GLSL/ISF only comes into play if you're writing a custom module. Tawny AV leans more hands-on: customizing it means editing shader and scene files directly, since that's what buying the source gets you.

Can I combine kott's dither or glitch effects with these visualizers?

Yes. None of the three tools compared here do dither, halftone, or ASCII-style pixel effects natively, so a common live setup is to route a visualizer's output (via Syphon, Spout, or NDI, depending on the tool) into a second layer for that treatment before it hits the projector or stream encoder.

Conclusion

The real choice here isn't which tool is best. It's which tradeoff fits your rig: curated-and-controllable with Synesthesia, free-and-inspectable with modV, or cheap-and-hackable with Tawny AV. All three turn audio into motion. None of them touch dither, halftone, or pixel-sort. Want to see what that layer looks like stacked on top of live visuals? Load a glitch effect in the free kott studio preview and route a clip through it.