Skip to content

3.0.0 macOS: Universal Binary (M1 + Intel), codesigned, sandboxed
Compare
Choose a tag to compare
@Birch-san Birch-san released this 03 Jan 18:13
· 37 commits to master since this release
3.0.0.macOS
7e3995a
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

Updated to fluidsynth from (probably?) v2.0.5 to v2.2.4 (fixes sustain pedal bug #30).

Universal Binary built for M1 + Intel Macs.
Targets macOS 12.0 Monterey (I would've targeted older, but limited by the OS which the dependencies were targeted against).

Codesigned (fixes #27); you no longer need to override your system's quarantine settings to run the plugin.

Enabled app sandbox and hardened runtime. This should futureproof it a bit.

Upgraded JUCE from (probably?) v5.4.3 to v6.1.4.

Rewrote build system with JUCE 6's new CMake support (#32) (to improve the build system's ability to support other platforms and OSes), and statically-linked the binary (to make distribution + installation easier).
This actually required contributing a bug fix + feature to CMake itself.

AUv3 now supported, confirmed working in Garageband. This should future-proof us a bit, since AU is already deprecated.

Release contains:

AU/juicysfplugin.component
AUv3/juicysfplugin.appex
Standalone/juicysfplugin.app
VST/juicysfplugin.vst
VST3/juicysfplugin.vst3

Breaking changes

If you are upgrading from a previous version of juicysfplugin, and have used juicysfplugin on an existing project in your DAW: you may find that the soundfont file you've chosen is forgotten, and you must select it again.
This is because we now rely on security-scoped bookmarks instead of filepaths, to work inside the constraints of the App Sandbox (necessary for AUv3 support, and makes juicysfplugin work without a quarantine exclusion).

Regarding Windows

No Windows release yet. The new CMake build system will make it easier (no installer will be needed, since static linking will enable us to put all the dependencies into a single-file binary). But will still need to create a development environment with all the dependencies for x86 and x64, in a format that pkg-config can work with (e.g. MinGW64).

Assets 3
Loading