Bug: Pro Tools does not accept text input in JUCE plug-ins

A tester reported that with Pro Tools 2025.12.0 it’s impossible to type into our plug-in’s TextEditor boxes. I managed to reproduce it on Windows 10 using Pro Tools Ultimate; the tester is on macOS 26. It did not happen with the version of Pro Tools I had installed earlier (which was Pro Tools Intro) but unfortunately I did not write down the version number.

How to reproduce: Create a project, add a plug-in into one of the insert slots, open the plug-in window, save the session, exit Pro Tools. Then re-open Pro Tools. It should open the plug-in window again. Open a text field and try typing into it. The text field has focus, the cursor blinks, but no text input happens. Close the plug-in window and reopen it, now the text field works just fine. It also works fine when the plug-in window is initially closed when the project loads.

I tried two of our plug-ins, one using JUCE 8 and the other using JUCE 7, and it happened for both. I have also verified this with various JUCE-based plug-ins from other manufacturers too (Music Hack’s Master Plan, Klevgrand’s Walls) so it’s not just our own plug-in. Plug-ins that are not written in JUCE do not seem to suffer from this issue (I only tried one of the Kiloheart’s plug-ins, kHs Gain) and neither do the built-in Pro Tools plug-ins. Klevgrand’s Rum also worked fine, even though that is written in JUCE, but this might be an older JUCE version.

Any ideas?

Additional data point: I just tried with Pro Tools Ultimate 2025.12.0 on macOS 14 (Sonoma) and there this issue doesn’t happen for me.

Thanks for the report, I just checked Klevgrand’s Rum and interestingly that does appear to be using JUCE.

I’ve been trying to reproduce this but so far I’ve been unsuccessful. including with Musik Hack Master Plan.

My setup
Pro Tools Developer/Ultimate 2025.12.0
macOS 26.0.1/26.2
Xcode 26.1.0/26.2.0
Apple M2 Max (MBP)

If there is anything else you find or can share I’m happy to take a look (although I’ll be out at NAMM most of next week).

Thanks for looking into this, Anthony. I have personally only been able to reproduce this on Windows 10. I’ve tried Mac too but it works as expected for me there. I did not try on Windows 11.

OK I have to admit I haven’t tried Windows yet I was trying macOS while I was looking at another issue reported there too.

1 Like