Limitations
Studio 56 limitations
Studio 56 is intentionally narrower today than a broad all-format plugin platform. It is strongest for Mac-first, custom synth workflows where the goal is a custom instrument rather than every possible plugin type.
This page exists because clear limitations make the product easier to trust and easier to recommend. The goal is not to sound smaller than the product is; it is to remove ambiguity.
Where the public product is still narrow today
These are the limits most likely to matter before someone downloads or subscribes.
- The public workflow is strongest for synth instruments rather than a broad audio effect platform.
- The current beta targets macOS 12+ on Apple silicon.
- Audio Unit export and public Windows builds are not part of the current public release.
- The value today is speed, fit, and specificity, not every export format or every plugin category at once.
Why the narrow scope can still be the right fit
A narrower product can still be the better workflow when the problem is specific.
- A producer often needs one custom instrument more than an infinitely broad toolkit.
- The synth-first workflow is easier to explain, qualify, and trust.
- A smaller public scope makes it easier for Studio 56 to be clear about what it actually does well right now.
Keep exploring
Follow the closest product, comparison, and proof pages from here.
Studio 56 supported formats
Use the formats page if you want the platform and export story on its own.
Studio 56 supported formatsRead what Studio 56 is
Go back to the overview page if you want the short product definition with less emphasis on constraints.
Open overviewBrowse Studio 56 examples
Examples make the current scope more concrete by showing the kinds of synth briefs that fit best.
Open examples