JUCE 9.0.3 released with a public Wayland preview branch

News and Announcements
1

This post is taken from the JUCE email newsletter.

To get these delivered to your email inbox, sign up here: https://juce.com/newsletter/

Wayland Preview Branch Available

We’re excited to announce that a preview of native Wayland support for JUCE is now available on a new public wayland branch of the JUCE repository.

If you develop standalone applications, audio software, or embedded Linux products, please give this branch a try.

For more information about the current state of the new Wayland implementation, please see the corresponding thread on the JUCE forum:

https://forum.juce.com/t/wayland-public-preview-branch

JUCE 9.0.3

A new minor version of JUCE is out, with some new features!

Opus Audio Codec

JUCE can now read and write Opus audio files that use up to 8 channels with the Vorbis channel ordering.

WebP Image Format

JUCE can now read and write static WebP images.

Platform Updates

  • Updated Windows MIDI Services support to the in-box preview 7 API

Notable fixes

  • Fixed multiple Linux ALSA sample rate and channel issues
  • Fixed Windows window placement and focus issues
  • Fixed cancelling blocking network requests on macOS
  • Fixed some OpenGLFrameBuffer issues
  • Allowed recursive scanning for LV2 plug-ins
6 Likes
2

Apologies if this the wrong place for feedback, but I’ve just updated to JUCE 9 since this release (I decided to wait until we were a couple versions deep into 9.0.x before taking the plunge).

I’m not sure if this is really a concern but I’ve noticed a change in how JUCE 9 exports AUv3 plists:

...
       <key>NSExtensionAttributes</key>
       <dict>
+        <key>AudioComponentBundle</key>
+        <string></string>
         <key>AudioComponents</key>
         <array>
          <dict>
            <key>name</key>
            <string>My plug-in name</string>
            <key>description</key>
            <string>Fx|Resynthesizer</string>
            <key>factoryFunction</key>
            <string>MyPluginAUFactoryAUv3</string>
            <key>manufacturer</key>
            <string>foo</string>
            <key>type</key>
            <string>aumf</string>
            <key>subtype</key>
            <string>bar</string>
            <key>version</key>
            <integer>65542</integer>
            <key>sandboxSafe</key>
            <true/>
            <key>tags</key>
            <array>
              <string>Effects</string>
            </array>
          </dict>
        </array>

(to be specific, this is Builds/iOS/Info-AUv3_AppExtension.plist)

Happy to provide any other info, but just figured I’d flag.

It’s possible that this is a no-op, but my research says that it’s not guaranteed to be safe for in-flight apps.

3

We’ve reverted that change for Projucer builds.

Thank you for reporting!