Dystopian Waves now supplies all six featured macOS tools as AU and VST3 plug-ins, but only three also include standalone applications. Arche, Noesis, and Wah Pedal can run outside a host. Drox II, Drox II Pro, and Spectral Wobbler remain plug-in or Max for Live choices.
Those labels are not interchangeable packaging. Your DAW decides which formats it can load, how generated MIDI leaves a plug-in, and whether a collaborator can reopen the same instance on Windows. Installing every available build can make the browser messier without making a session safer.
The practical value of Dystopian Waves’ new cross-platform plug-in lineup depends on matching one build to the session’s future. Pick for host compatibility first, MIDI routing second, and portability third. Claims that one format automatically sounds better or uses less processing power should not drive the choice.
Ableton Live on macOS accepts AU and VST3, but its own guidance says there is no universally correct format. One practical difference matters sharply for Arche and Noesis. Live does not receive direct MIDI output from AU plug-ins, while VST3 supports it, making VST3 the safer conventional plug-in choice when generated notes must reach another instrument track.
That limitation matters less for audio effects. Drox II, Drox II Pro, Spectral Wobbler, and Wah Pedal process sound rather than supplying the chord or bass MIDI that another instrument needs. In those cases, choose the format that matches the rest of the project and keep it consistent.
VST3 also helps when a Live, Cubase, REAPER, or Studio One project may travel between Mac and Windows. AU is confined to Apple platforms, while the Dystopian Waves VST3 builds exist on both operating systems. Portability still requires the same product and compatible version on the second machine, but using the same format removes one obvious point of failure.
For Arche and Noesis, a MIDI-generating Ableton device workflow avoids the AU output limitation and keeps note generation inside Live’s native device environment. Arche’s published compatibility includes Live 11.3 or later, Live 12, and Push 3. That makes the Max for Live build attractive when the project will remain entirely inside that ecosystem.
The trade-off appears when the session leaves Ableton. A collaborator needs a compatible Live setup and the relevant device, while a rendered audio track or exported MIDI clip carries fewer dependencies. Commit important generated notes to clips before delivery instead of assuming the recipient can reconstruct the device state.
Audio effects present a simpler choice. Use the Max for Live edition when Live-specific control and device-chain behavior matter, but prefer VST3 when the same effect chain must be recreated in another compatible DAW. Saving a preset does not turn a Max for Live device into a portable VST3 instance.
The remaining products have no listed standalone build, which fits their role as insert effects. Drox II needs incoming audio to glitch or stutter, while Spectral Wobbler needs material whose frequency content it can modulate. Running those processes inside the host preserves tempo, routing, and project recall.
Installation location becomes relevant when one build appears, and another does not. Audio Units normally live in the macOS Components folder, while VST3 plug-ins use the dedicated VST3 folder. Live can enable or disable each source separately, and Logic provides a Plug-in Manager for validating or rescanning Audio Units.
Do not replace an existing project’s format casually. Ableton recommends using the same format for every instance of a given plug-in within one Set, and AU and VST3 versions are stored as different plug-in identities. A newly installed VST3 copy will not automatically repair a project that is looking for its missing AU instance.
Those labels are not interchangeable packaging. Your DAW decides which formats it can load, how generated MIDI leaves a plug-in, and whether a collaborator can reopen the same instance on Windows. Installing every available build can make the browser messier without making a session safer.
The practical value of Dystopian Waves’ new cross-platform plug-in lineup depends on matching one build to the session’s future. Pick for host compatibility first, MIDI routing second, and portability third. Claims that one format automatically sounds better or uses less processing power should not drive the choice.
AU belongs in Logic while VST3 travels farther
Logic Pro for Mac works with Audio Units and Audio Unit Extensions, so the AU build is the relevant Dystopian Waves installation there. A VST3 file sitting in its normal macOS folder will not appear as a usable Logic plug-in. Installing the AU component avoids a fruitless rescan for a format the host does not support.Ableton Live on macOS accepts AU and VST3, but its own guidance says there is no universally correct format. One practical difference matters sharply for Arche and Noesis. Live does not receive direct MIDI output from AU plug-ins, while VST3 supports it, making VST3 the safer conventional plug-in choice when generated notes must reach another instrument track.
That limitation matters less for audio effects. Drox II, Drox II Pro, Spectral Wobbler, and Wah Pedal process sound rather than supplying the chord or bass MIDI that another instrument needs. In those cases, choose the format that matches the rest of the project and keep it consistent.
VST3 also helps when a Live, Cubase, REAPER, or Studio One project may travel between Mac and Windows. AU is confined to Apple platforms, while the Dystopian Waves VST3 builds exist on both operating systems. Portability still requires the same product and compatible version on the second machine, but using the same format removes one obvious point of failure.
Max for Live gives Ableton tighter MIDI control
Ableton users have another route for every product in this release group. Max for Live versions operate as Live devices rather than general plug-ins, so they fit Live’s routing, mapping, and device-chain model closely. They will not open in Logic or another DAW merely because that DAW runs on the same Mac.For Arche and Noesis, a MIDI-generating Ableton device workflow avoids the AU output limitation and keeps note generation inside Live’s native device environment. Arche’s published compatibility includes Live 11.3 or later, Live 12, and Push 3. That makes the Max for Live build attractive when the project will remain entirely inside that ecosystem.
The trade-off appears when the session leaves Ableton. A collaborator needs a compatible Live setup and the relevant device, while a rendered audio track or exported MIDI clip carries fewer dependencies. Commit important generated notes to clips before delivery instead of assuming the recipient can reconstruct the device state.
Audio effects present a simpler choice. Use the Max for Live edition when Live-specific control and device-chain behavior matter, but prefer VST3 when the same effect chain must be recreated in another compatible DAW. Saving a preset does not turn a Max for Live device into a portable VST3 instance.
Standalone builds solve sketching rather than recall
Standalone Arche and Noesis can support idea generation without opening a full DAW, while standalone Wah Pedal can provide an independent effects environment. That convenience does not make the application interchangeable with a plug-in saved inside a project. A standalone preset, MIDI export, or recorded result must still be moved into the session deliberately.The remaining products have no listed standalone build, which fits their role as insert effects. Drox II needs incoming audio to glitch or stutter, while Spectral Wobbler needs material whose frequency content it can modulate. Running those processes inside the host preserves tempo, routing, and project recall.
Installation location becomes relevant when one build appears, and another does not. Audio Units normally live in the macOS Components folder, while VST3 plug-ins use the dedicated VST3 folder. Live can enable or disable each source separately, and Logic provides a Plug-in Manager for validating or rescanning Audio Units.
Do not replace an existing project’s format casually. Ableton recommends using the same format for every instance of a given plug-in within one Set, and AU and VST3 versions are stored as different plug-in identities. A newly installed VST3 copy will not automatically repair a project that is looking for its missing AU instance.
