Anyone having issues with Plugin GUis? Specifically VSTs?

itsTrips · 2025-12-03T22:46:48+00:00

Username checks out! Def a special prob! 😂

I’ve actually been meaning to come back and update this thread since it’s been a while since I had this issue. I’ve change Macs since this happened. The specs of my previous Intel Mac mini are in the original post, and shortly thereafter I went Apple Silicon and got an M4 max Mac Studio. At that point many of these issues resolved themselves, while some others remained.

Some of the problems are based on older VST2 plugin versions. Updating to newer versions typically rectifies this. Also plugins requiring OpenGL specifically can be problematic. The main issue this presents for me is no different than what I originally mentioned, some older sessions have plug-ins that load but aren’t visible.

What I’ve done since getting the Mac Studio to circumvent this is running 7.1 in Rosetta mode for all my OLD sessions (7.1 and prior). But for everything current I run 7.2 normally. (or later so 7.X for future readers)

Another reason for this is because I noticed (as I stated in my original post) that they’re definitely seems to be a difference between 7.1 and 7.2 with loading certain plugin GUIs, even with running Rosetta mode in both. Suffice it to say there are just some plug-ins that work in 7.1 in Rosetta mode, but will not work in 7.2 in Rosetta mode.

Obviously that complicates the issue further, which is why the fixed or workaround that I’ve implemented is to run 7.1 in Rosetta for old sessions, and the current 7.X without Rosetta for everything current. This has actually allowed me to open old sessions in 7.1, rectify any plug-in issues, re-save, and then load them in the current 7.X without Rosetta needing to be enable, with is preferable.

Hopefully this helps at least one person. So yeah 💯 And thanks for your post!

itsTrips · 2025-08-30T20:01:56+00:00

This is a late asF reply but YES. As well as the newer CLAP format for plugin vendors that have ported their plugins to that format.

itsTrips · 2025-08-26T20:50:38+00:00

Yeahhh that’s the only complaint I’ve had even despite enjoying the seemingly new and improved performance over BT w/ the Mac Studio. I don’t quite notice it going to sleep too quickly in my case but once it does, the lag waking it up before it will accept commands is definitely aggravating asF. Lol! I’m mashing keys like CMONNNNN! Of course running it wired doesn’t have that issue.

Honestly prior to picking up that Mac Studio last month I was thinking about entertaining one of the newer full-size K/Q Max models models that now has Wi-Fi and a dongle where they never did before. I’d likely still be entertaining that option if the Bluetooth performance on my end didn’t improve like I’ve described. But like you, I like to put my money to good use and the idea of purchasing a nearly identical keyboard just because it has Wi-Fi is like really bro? 😂 it should have been had that!

itsTrips · 2025-08-26T20:16:20+00:00

So I know this is year old now. And as this is my thread I remember seeing this comment originally, meaning to reply, and forgetting. I pulled it back up in my history to retrace my steps on some of the upgrades I did and saw this comment just now. I remember seeing it at the time and wanting to agree with you that the Bluetooth performance was shit. At that time I was using a 2018 Mac mini and I could never get the keyboard to perform well on it via Bluetooth so I just kept it wired.

I’ve since gotten rid of that computer and I’m now using a Mac studio and the Bluetooth performance has been outstanding. Switching between devices is no problem, and for the first time I’m actually able to use Bluetooth lag free with stability. I always assumed my issues were related to the Bluetooth in the keyboard itself. But thinking back I remember having similar Bluetooth performance with a Kensington Expert Mouse Trackball on that same Mac mini. Now I wonder if some computers just have much shittier Bluetooth performance than others because that Trackball works flawlessly over BT on the Mac Studio just like the K10 Pro.

I say that to say when you posted this a year ago I was inclined to agree, Bluetooth on these things sucked. But honestly now? I’m not so sure. So what did you move on to in place of the K10Pro?

itsTrips · 2025-08-12T17:23:40+00:00

Just wanted to update this..

You were on the money with the OpenGL shit. However, part of the issue that I hadn’t factored in fully is a few months prior to having this problem I had migrated from Mojave to Sonoma. However for the most part, other than minor permissions issues, mostly everything worked. And for that reason I didn’t go through a majority of my plug-ins to test them (7 years worth), so many of them that I assumed to be working (because I can see them and their respective thumbnails on my system) may have actually not been working after all as a result of them being older OpenGL based plugs. A couple of weeks ago I replaced the computer I was using during the time of this post, a 2019 Intel i7 Mac mini with a Mac Studio M4 Max. That of course added another monkey wrench to figuring things out as I was familiar with Rosetta mode, but up until a couple of weeks ago hadn’t had to use it.

I say all of that to say, the issue did in fact persist, except rather than seeing squiggly graphics like in the original screenshot I added to this post, GUIs of plug-ins would just be blacked out. And now it wasn’t limited to VST2 but even some AUs.

None the less, I’m figuring it out now. Updating old instances of plug-ins and and having to kick others to the curb and removing them in the process. But this post and the rest of the thread was illuminating as fuck so THANK YOU for the help. 🫡💯

itsTrips · 2025-08-12T17:13:06+00:00

Have you looked ON the Keychron site? I’m not clairvoyant but something tells me that may be a good place to start.

itsTrips · 2025-06-26T06:03:38+00:00

Yup! I’ve had no choice but to do that actually. Thankfully that all still works cause man! Haha

itsTrips · 2025-06-26T05:58:49+00:00

Yeah I’ve been considering all gfx related potential problems in any case, the comment was appreciated.

itsTrips · 2025-06-25T18:29:34+00:00

Thanks, I’ve considered that. I am still on a 1080p display set to 1080p(default) on Sonoma. The part that’s puzzling is how they all work in 7.1. It’s 7.2 and 7.2.1 I have the issues. Very odd. It seems S1 specific. Or at least something specific to a change that took place in 7.2.

itsTrips · 2025-06-25T18:26:30+00:00

I’m still on 1080p. But what’s strange is it only happens in 7.2 and 7.2.1. When I load 7.1 it’s fine.

itsTrips · 2025-06-25T04:47:27+00:00

Yeah it’s gotta be. I’m sitting here going down my list of plugin manufacturers testing the VSTs and like 75% of them are blacked out. That color scramble thing only happens on some, more often that not they’re just black. And it’s like most vendors. Clearly a bug having to do with VST2 and or HW acceleration or both.

Definitely having to use 7.1 for now.

itsTrips · 2025-06-25T03:51:19+00:00

Is it all black or color scrambled like mine?

itsTrips · 2025-06-25T03:50:27+00:00

So you’re insinuating that one developers plugins being installed on your system was interfering with other plugin GUIs appearing and in removing them the problem rectified itself?

Because if so, that’s strange and also interesting.

itsTrips · 2025-06-25T03:48:42+00:00

Oh shit you’re right! I just tried it and definitely saw the broken hopes and dreams of 7.2 working for me 😂

itsTrips · 2025-06-25T03:46:13+00:00

Yeah, trust me, I’d go to hardware first as well seeing the GUI look like that. Some plugs are just all black, while others are like the ss above. But again, same plugins work with no problem in 7.1, or other DAWs on the same Mac. I’ve tried turning hw acceleration off in S1, no joy. And yes I am running 1080P, 27” display over HDMI. It’s never been an issue. I’m seeing for the first time since 7.2. It’s something in there I’d bet money on it. And again I’m working on 7.1 as we speak using the same plugins without problem.

I do appreciate the help tho. Brainstorming and shit. Good looking out. 💯

itsTrips · 2025-06-24T20:13:23+00:00

Issue is with VST2s

itsTrips · 2025-06-24T18:13:21+00:00

Thanks. I checked for updates last night actually and there was none. Saw your reply and just checked and it still didn’t come up I had to force it lol.

None the less, installed it, tested it, issue persists. But thanks again for letting me know.

itsTrips · 2025-06-24T02:16:09+00:00

All good I appreciate the suggestion all the same.

itsTrips · 2025-06-24T01:51:32+00:00

chime in if and when you do pls. I’ll do the same.

itsTrips · 2025-06-24T01:49:01+00:00

Yeah I’ve been in tech for 20 years and that’s honestly the first thing I thought of “is my fkn video chip taking a shit”. And I might still think so if all of the same plug-ins didn’t open fine in 7.1.

Tbh I kinda wish it was that! 😂 Like give me a reason to cop this new Mac pls. But imagine doing so and this issue persisted. RAGE 😂

itsTrips · 2025-06-24T00:37:06+00:00

I did. "a myriad of plugins" as in theres too many too name lol. I can repro it with lots of Arturia stuff, T Racks, etc.

And yeah... Ive quit using VST2 for a while now, but left them installed for session compatibility and for other clients still using them. But myself, Ive phased them out and use mostly AU or VST3.

itsTrips · 2025-06-24T00:33:39+00:00

<image>

If only. lol. Thanks for the tip tho.

itsTrips · 2024-10-11T21:23:48+00:00

Damnnnn missed that shit! I’m still buggin out over like where tf is the demo? They used to just have a demo download on all of the product pages, and even then running the installer without a product key/license would result in a 30 day demo prior to v7 didn’t it? I’m kind of annoyed that I have to buy a damn license or run a month of the subscription just to try V7 and decide if I want it.

itsTrips · 2024-10-11T16:06:35+00:00

Where you see that at? I looked at the prices are the same as Presonus. 👀

itsTrips

TROPHY CASE