Apple hates this. If you have an old .ipa file of the fixed version, you can sideload using libimobiledevice or a jailed developer certificate. This is advanced, but it keeps the 32-bit audio engine alive on an iPhone 6S running iOS 14.
Recent updates introduced high-density UI scaling, Cloud storage integration, newer synthesizers, and support for the newer AAudio API.
Have you fixed your setup with an older version? Share your build number and device in the comments below—let’s build a community compatibility table for legacy Audio Evolution users. audio+evolution+mobile+studio+old+version+fixed
A "fixed" old version often refers to a build that is hardcoded to work with specific USB audio interfaces. Modern updates sometimes break compatibility with niche audio interfaces (e.g., specific Roland or Behringer models). Users find that an older version (e.g., version 5.0.4) "fixes" the connection issues present in version 6.1.
Historically, versions in the v3 to v5 range are often cited by users as the most stable. During this period, the app focused exclusively on the core DAW functionality: Apple hates this
These versions relied heavily on the OpenSL ES audio API. While older, OpenSL ES is notoriously reliable on older Android devices (Android 5.0 through 9.0). For users with older tablets or phones—often repurposed as dedicated studio machines—these versions provide the lowest latency and least amount of audio dropouts.
Does the old version have the shiny new synth engine? No. Does it have the fancy channel strips? No. Have you fixed your setup with an older version
But here is what works:
When the community says the “old version fixed” their workflow, they aren’t talking about new features. They are talking about the restoration of core functionality that v5.0 broke. Specifically, the builds between v4.2.0 and v4.6.5 are celebrated for fixing: