VSTs started viewing improperly in Maschine 3 software.

Maxray · 2024-12-12T01:54:32+00:00

There was an error rendering this rich post.

Has anyone else started having this issue with VST windows? This just started happening a few days ago, does anyone have a fix? I modified/repaired all my Microsoft Visual C++ Redistributables to attempt a fix, so that's not it?! My computer is an AMD model if that has any bearing?!

Also, it's occurring with VST2s and VST3s, alike.

This is with Byome, Triad and Hybrid EQ, but it's happening with most of them..

Find more posts tagged with

Comments

PK The DJ

What resolution is your screen, and are you using scaling in your OS? If so, what's the scaling set to?

D-One

https://community.native-instruments.com/discussion/comment/197167#Comment_197167

Having that info is good to have but…. Does it matter?

Is Maschine 3 only supposed to work on a specific set of Resolution/Scaling when Maschine 2 was not? If so it should be stated in the requirements…

Matthew_NI

It might matter quite a bit.

It looks like some of those plug-ins are either resizing incorrectly, reporting their size incorrectly, or we are interpreting something incorrectly. All of this could be related to screen resolution and OS scaling.

Sunborn

https://community.native-instruments.com/discussion/39874/vsts-started-viewing-improperly-in-maschine-3-software

Yes this is a 100% scale/resolution issue, not a Maschine issue.

For example, 2 of the mentioned plugins, Byome and Triad they are successfully resized from inside Maschine, no matter how small or big you made them, the Maschine windows adapts instantly.

So, my guess is that @Maxray has an increased scale and probably not a standard one (such as 125%) and the above plugins can not handle that scaling.

By the way, since the vast majority of plugins and other software has native resizing (from 50% to 200% or more), Windows scaling has become a really unnecessary thing, even a problematic one on some cases.

Maxray

I am pretty confident it is not a resolution issue, as the plugins open correctly in multiple other programs, as shown in the images below. It seems to only be happening in Maschine 3 SW. I attempted redownloading all the Waves plugins to test that theory, but it did not provide any correction, unfortunately.

I'm not sure when started it?! The only updates I've done since it started were with Komplete Kontrol, UVI, Arturia (which are working fine), Softube and most recently Waves reinstallment. I'm sure none of those are directly affecting Maschine, as Komplete Kontrol has it's own AppData folder and the others work fine in other hosts, as you can see in Cubase, Ableton and Reason below.

I made sure i used the same 3 plugins as example in each host, but it's all of the Waves, UVI, Universal Audio, Fabfilter, Eventide, Plugin Alliance, etc. Arturia seems to be fine for some reason?!

It's also important for me to note, that they open fine in the hardware, just the software windows are showing bad displays. I'm working on a project right now and require access to the plugins directly from the software, which is when I noticed the issue and tested multiple plugins at that time to find many were behaving this way.

Maxray

I readjusted the resolutions through Windows and AMD Adrenaline to test your theory, but it made no change. I also rescanned the libraries in full to no avail. There must be an issue with how Maschine 3 is interpreting the codex?! Repairing the Visual C++ Redistributables seemed like the proper fix, but had no effect?!

Also, I work mainly from the hardware, so I'm not exactly sure when it started, but it couldn't be more than a 4 days.

Maxray

My current resolution settings are at 3840 X 2160 (Recommended) @ 150%.

Oh, btw…. I set all the plugins to a resolution of 100%, while in standalone and in Ableton just to be sure.

Milkman

This goes back years, and maschine versions. I havent updated (and wont be) to maschine3, Im on windows10 with default scaling options (150% recommended/default) on a 32" 4k screen, and plugins very regularly look wrong inside maschine. This is essentially identical behavior (large white space, wrong borders, etc). I have no idea why this wouldnt be fixed by now. Ive worked around the issue long ago by, lol, working around maschine.

I use numerous DAWs and plugins which host other plugins, and not one of them does this. Occasionally Bitwig 5.2.x draws a distorted border around a plugin that has been resized or it cuts off part of it, then I click the border and it fixes itself. Not maschine though, for all the years Ive been using it.

Maxray

I usually don't have this problem, it just started randomly. Do you all think I should write up a support ticket?

darkwaves

https://community.native-instruments.com/discussion/comment/197218#Comment_197218

To be fair: if maschine 3 is the only program that doesn't handle the scaling properly; it's kind of strange to say it's not a maschine issue.

If OP can show the display works properly when scaled to 100% instead of 150% AND it works properly in ableton, cubase and (probably) maschine 2 at 150%; but maschine 3 goes all wacky at 150% - that's a maschine 3 issue.

IMO of course.

Sunborn

https://community.native-instruments.com/discussion/comment/197375#Comment_197375

It is a Maschine issue (bug) if the same thing is happening to many users.
If it is happening only to 1-2, then it is usually something else (surely, not always).

Judging from my own experience (and all other Maschine users i know) i never had such issues, neither with older versions neither with Maschine 3. So, from my part, i have no evidence to say that this is a Maschine issue.

But, i must say, i do not use those "monster" resolutions, ever. I use a "normal" screen 1920 x 1080 at it's 100%… and the vast majority of users are using this resolution too (check statistics here and here )… i keep the huge screen for movies only (for us "old schoolers" who made music in the 90's and 00's, those screens looks unnatural… i tried hard, really, but i can not get used on them!) 😉

Anyway, the OP's resolution is the 3840×2160 (4K UHD) which is very ok and not really huge. However i am still confident that this issue has to do with resolutions / scaling.

For example:

Is it possible that at some point the OP changed something on the compatibility tab of the .exe file?
Or, on the other hand, maybe playing with these setting can fix the issue?

Maxray

So, I've been doing some more testing and I found an error!

The AMD Adrenaline firmware/software had done an automatic update from 24.10.1 to 24.12.1… this is the performance controller firmware/software for my graphics card.

Evidently, when changes were made to their codex in the last update, it affected how Maschine 3 SW translates that data. I believe there must be some kind of translation issue happening on a code level that's affecting the way Maschine tables the GUI for external plugins. I was able to reconstruct a basic, normal window @ 2560 x 1400 @100%, after turning off all my regular display enhancement controls and resetting to basic Windows output. Though, the windows still have issues in Maschine SW, and are not completely formative or accurately translated to borders properly, and though corrective for most, some plugins are still out of whack. My system doesn't use Java, so that's out of the question.

Also, I have been using my preferred scaling of 3840 x 2160, because I use a Samsung 45" HD TV as a monitor, and that is the recommended value from Adrenaline and Windows 11 both, just to clear the room of any disinformation from my side. I noticed this is an argument in the thread, which has no bearing on the actual issue. It doesn't make sense for me to use a lower scaling on this size monitor with a 6800XT graphics card, they both can handle the load. Also, I have always ran Maschine 2 & 3 this way and it was never an issue till the recent update. Lowering my resolution down to 2560 x 1400 actually creates more of an issue with everything else in the OS GUI, and doesn't solve the actual problem, which is a firmware/software/handshake issue.

I haven't found the rollback firmware on AMD yet, but I was pretty tired last night after testing and delayed it for today. I will rollback to 24.10.1 and see if that helps. I'll report here to you all and let you know the status at that time.

Sunborn, I just want to show you the results of the DPI scaling changes, even from Windows 11 directly it produces those results, as the image I provided below will show. As you all can see in the image below, whether @ 3840 or 2560 the windows GUI behavior will alter, but there's always a window issue, and the problems not corrected. In the image below, you can see that the Plugin Alliance GUI's are fitting and the Waves GUIs are still off @3480, even when I switch to 2560.

It's a scaling issue, but it's not at the Firmware or OS level (in that everything else functions properly with the update), it's at the application level. It could be some minor "parity" value in the way Maschine 3 outputs the translated code? Idk?! It's very confusing! No matter, eventually I'll have to retune my Adrenaline performance controls for other features on my system, so the problem isn't solved yet. I'll report back with an update when I reinstall Firmware 24.10.1!

Thank you for all your help guys!

Maxray

Alright, so this is the status!

I apologize about the delay, I was super busy yesterday…

I have rolled back to the 24.10.1 firmware! I have my screen resolution back @ 3480 x 2160 150% again. All screen enhancements on Adrenaline remain off, at Default Windows. This is where I stand…

All of the Plugin Alliance windows are running normal again, Waves and some other products VST3s continue to have issues (as you can see in the image below with Saturn and Metafilter [Right]), but all of the VST2s are showing properly (as you can see with the Metafilter on the left).

So, during the firmware update to 24.12.1 there must have been a string change that altered the behavior between Maschine 3 SW and Adrenaline, which remained on system during the rollback?! Another key point that I should mention here, which could help identify the problem…. Metafilter's VST3, on the right, doesn't stay pinned, and requires me to reopen the plugin window, anytime I click anywhere else. The other plugins stay pinned, including the Saturn VST3, which is not formative to the window, shown below.

I have been able to work at lower resolutions on 24.12.1, so I've been able to continue my project. I think I will remain on the 24.10.1 Arenaline firmware version, until NI can identify and fix the issue. As all my other host programs work equally as well in 24.10.1 as they do in 24.12.1, so that's not a bother! I can utilize the VST2s on my system in the meantime and forego the issue till it's addressed. I'm going to start a support ticket!

Thank you all for your patience and help, I really appreciate the response!

D-One

https://community.native-instruments.com/discussion/comment/197216#Comment_197216

If the plugs are reporting their size incorrectly then how came they load fine in other hosts with the same scaling/res?

Is the expectation here that users cannot use whatever scaling and res they like? Im so confused by those statements…

Maxray

I went ahead and reinstalled Adrenaline 24.12.1…. plugins started having the same problem on 24.10.1, despite the resolution. So, there was no point in not updating my graphics card firmware anyway at this point.

Also, I noticed in the windows, there is no corner resize marker to change the actual window size…

Quick links

Unanswered questions