I just saw this: https://gearspace.com/board/new-product-alert/1422096-introducing-juce-8-a.html

But no mention on the site, neither on the git repo. Looks like webview is the main thing.
Is there an updated changelog yet somewhere?



fwiw, the direct2d branch has its readme updated to state JUCE 8 technical preview. I’m certainly extremely curious about the rest though.

Seems everybody else knows it…

Why are we still here? :wink:

1 Like

I guess it was announced at NAMM, that’s why there’s no notice here yet.
Anyway, what worries me that the main features announced with JUCE 8 are not audio related.
I feel that JUCE is shifting away from being an audio framework, towards becoming something else.


What audio-related features would you like to see, out of interest?

Maybe it’s less about shifting away from audio, and instead giving attention to some large pieces of work relating to UI.


I actually feel the opposite - if JUCE was purely an audio framework, we’d already have the easy ability to make plugins with other UI systems, like webviews.

I’m also not sure JUCE ever was just an audio framework - I’d take a guess that the largest appeal to most people is actually that it handles all of the non-audio related things - wrapping the plugin for various formats, handling the message loop, parameter systems, etc.


The features of JUCE 8 were discussed before, and there are opposing views. That will always be the case.

What sadens me is that there is nobody in the JUCE team interested to update their very own community. Just copy the same press release as a minimum here would have felt a little less abandoned.

But it just echoes the silence that is felt here for a while already.


Complaining will not make the team change

But sometimes it feels good :slight_smile:


Not complaining guarantees the team won’t change, and least there is a chance if people do complain, especially pro license holders.


Yeah enterprises bought the webviews basically, we will all be standardised to frontend developers

I wonder if the most required FR is coming :slight_smile:

  • sample accurate parameter updates, for example.
  • or like an overhaul of certain dsp classes, maybe a dedicated dsp2 namespace where everything is rewritten and improved with added features, just like they rewrote lookAndFeel in the past until it got really good.
  • a much better performing FFT class to prevent everyone from having to figure out which 3rd party library works best

true, tho


A couple of things would really help us plugin devs:

  1. Working pinch-to-zoom in Windows using the trackpad on our laptops.
  2. Implementing CompareActiveChunk in the AAX wrapper, with a call in the Processor component to handle it.
1 Like

That PR piece was something that was rolled into a larger package to go out with other NAMM news. It was intended to be a brief overview of the things that will be in JUCE 8, rather than a formal announcement of the release. The way press releases work is a little complex and it ended up being positioned as a release announcement in news outlets that picked the story up. Apologies for any confusion there.

We’ll do a much more thorough, developer-focused, dive into all of the JUCE 8 features once we’re also in a position to announce things like an expected release date and pricing. We’re currently deep in the weeds getting “unicode support”* ready, but once this is done we’ll put it onto a juce8 preview branch, alongside the other features, and we’ll do a proper announcement.

* “Unicode support” doesn’t really convey the complexity of the task, but we need something short to refer to it.


Thanks for chiming in Tom!

Thank you Tom for the clarification.
Assuming you’re in NAMM I guess it’s more tricky to be promptive in general.

To clarify, this is for the existing backends right?

(Since WebViews would actually get those out of the box…)



WebViews get all of that as part of their built-in renderers, but there are people who want access to a wider range of languages in their existing JUCE apps.

Apologies again for the poor communication of this. We’ll follow up with a much more interesting update in a few weeks.


What audio-related features would you like to see, out of interest?

MIDI 2.0 Device and MIDI 2.0 UMP support.

I actually went to the JUCE booth at NAMM (Saji (@saji8k) on Threads) and they told me that MIDI 2.0 device and ump support would be in the first public preview of Juce 8 that they said was coming in Q1 of this year. MIDI 2.0 is suspiciously missing from the press release in the OP so that is cause for concern.

We’re going to wait for Windows before we add device support to JUCE. Delivering something now that we then might have to reconfigure to conform to how things work in Windows would be double the work for the JUCE team, and disruptive to everyone already using the new functionality. (Nov 2023)

Pete Brown from Microsoft gave a public demo of Cubase on Windows recording from a Roland MIDI 2.0 keyboard already available on the market using the Windows MIDI Service API code available on Github. You can see a video of it here: Saji (@saji8k) on Threads . I also was able to try out Windows multi-client support myself on a side demo at the MIDI booth.

I would counter that now is the best time to deliver something. If you do encounter missing features or issues in the Windows API, compared to the already final macOS/iOS/Android/Linux MIDI 2.0 APIs, you can get these fixed now by Pete and his team, before the code is frozen and deployed to a billion Windows devices.