Blank/White Screen after plugin was closed and opened again

Audio Plugins
21

the second patch also works with a release build but still doesn’t solve the debug build issue. i tried removing the WebViewComponents and it made no difference. i’m going to spend some time narrowing this down and will update here when i’ve found a reproducible case.

22

hi @reuk - i checked in the juce 8 release and this fix isn’t included. is there a plan to add it in?

3 Likes
23

Hi @reuk, this is also affecting me. Any update on including a fix in the JUCE codebase?

Best wishes, Pete

24

Hi @modosc,

Did you by any chance figure-out a solution to this…?! :slight_smile:

Best wishes, Pete

25

NB auv3-blank-v2.patch above works for me with JUCE 7, testing with both Ableton and Logic on macOS Intel (yet to try on ARM).

Best wishes, Pete

26

i shipped the above patch and the issue is resolved for customers. it still doesn’t work in debug mode for one of my projects but i never traced down the underlying cause.

also - ableton closed my support ticket as fixed more than a year after i opened it :man_shrugging:.

1 Like
27

Thanks @modosc !

I’ve also verified the patch to my satisfaction. And have an open ticket on this subject with Ableton - I’ve pointed them to this forum thread :man_shrugging:

Best wishes, Pete

28

@reuk I just faced this issue with 8.0.9 and the patch v2 worked for me. Why don’t you include this fix in the latest JUCE?

29

I’ve just had a report on this with plugins built with 8.0.6. I’m not using any web view components and the UIs are very simple, i.e. derived from the generic editor. :roll_eyes: I’ll report back if the plugin client patch fixes my issue.

30

I just had another look at this. Here’s my test environment:

  • Xcode 26.0.1
  • macOS 15.7.1
  • Live 12.3b13

Here are the steps I took:

  • Create a new AUv3 using the template in Xcode:
    • File → New → Project…
    • Multiplatform → Audio Unit Extension App
    • Fill out the fields in the wizard to create a new effect plugin with a UI
  • Build and run the plugin to verify that it works.
    • The default-generated project includes a standalone target that displays the plugin UI, which contains a single gain slider.
    • I verified that the AUv3 can be added to a track in GarageBand, and displays the gain slider as expected, even when toggling the UI visibility.
    • SImilarly, the plugin displays correctly in the JUCE AudioPluginHost, and the UI can be opened/closed without issues.
  • Open Live, add the new AUv3 to a track, then close and reopen its UI using the toggle button in the rack at the bottom of the screen.
    • The plugin editor window remains blank when it is reopened.

out

Given that a non-JUCE plugin displays incorrectly in Live, I think there may be a bug on Live’s side. I’ll send them a bug report and update this thread if they’re able to confirm the issue.

31

Ah that’s cool @reuk - thanks for looking at this again. This was on my TODO list, but I was really nervous rolling out that patch to (checks notes…) over 25 plugins… :grimacing:

Seems like a pretty solid case it’s a Live issue. Hopefully they’ll admit, err… I mean confirm :slight_smile:

32

I got a reply from Ableton saying that they’re unable to repro the issue using the steps I described above. However, I’ve tested the steps on two separate machines, Arm and Intel, running macOS 15.7.1 and 26.1 beta 3 respectively, and I see the faulty behaviour in both cases.

In order to find the common link between environments where this bug manifests, please could you try following those steps and check whether the plugin editor fails to show up for the Xcode template AUv3 project? Please also include the following:

  • macOS version
  • architecture (Arm/Intel)
  • Live version
  • Xcode version
  • is System Integrity Protection enabled or disabled
33

Bumping this thread - it’d be helpful to get some more data points so that Ableton can track down this issue.

34

Hi. I’m still getting reports of this issue on Live 11 and 12 with Tahoe 26.5.

Any update on this please? Thanks.

I’m on JUCE 8.0.6

35

We’ve not heard anything, no. Given that the issue appeared to be on Live’s side, I’d recommend contacting Ableton directly, including as much information as possible. You should also quote ticket L12-BUG-4626, which is the bug I reported previously.

1 Like
36

Many thanks for the update and the ticket ref, I’ll give them a nudge and update here with any news.