VSTs started viewing improperly in Maschine 3 software.

2»

Comments

  • Martin_NI
    Martin_NI Product Team Posts: 25 mod

    Hey @Maxray,

    Thanks for all the info, I just wanted to confirm you have done the following when running Maschine 3 in Ableton Live
    https://support.native-instruments.com/hc/en-us/articles/22776526691101-Using-Maschine-3-in-HiDPI-mode-in-a-DAW-Windows

    This does not solve the issue in standalone, but if you have not configured Ableton Live to run Maschine 3 as a HiDPI plugin, plugin hosting in Maschine on Windows will experience the issues you mentioned.

  • Maxray
    Maxray Member Posts: 124 Advisor

    I'm not having any issues running Maschine in Ableton, the issue is happening in Maschine 3 SW alone. Cubase, Ableton and Reason are all running fine.

    It's happening with multiple plugins, but with all the Waves plugins for sure. It's the way Maschine 3 is translating the code for the windows is what's causing the issue. I'm not sure why, but it's only happening on the Maschine side?!

  • Maxray
    Maxray Member Posts: 124 Advisor

    Yes, I have tried that HiDPI option, it wasn't successful!

  • Maxray
    Maxray Member Posts: 124 Advisor

    Also Michael, I have met 3 others on the community that are having the same issue. I bookmarked their pages on my account, and notified them to go ahead fill out a support ticket.

    My system is the Alienware R10, with AMD Ryzen 5950 processor and AMD 6800 XT graphics, so I use the Adrenaline firmware for my graphics driver. I'm not sure what systems the others have?!

  • Sunborn
    Sunborn NKS User Library Mod Posts: 3,298 mod

    I have seen those other posts and noticed that they all talking about Waves mostly, so it might be a Waves problem, especially for the older plugins.

    Did you tried to experiment with the Waves resizing from within Maschine? Like this:

    For example, if your display resolution is at 150% maybe try the 75% size in Waves, (always from within Maschine) and if you find a correct value, use the "apply as default to all" option.

    Just an idea, but it might be useful…

  • Maxray
    Maxray Member Posts: 124 Advisor

    Yeah, Sunborn, that's the first thing I did! I wanted to make sure all the Waves and other vendors plugins matched in all hosts. It was important in evaluating cross platform.

  • olafmol
    olafmol Member Posts: 215 Pro
    edited December 2024

    I would approach this from a very "simple" angle: check how other VST hosts are displaying the plugins. If they display them correctly, file a bug with NI, and let them fix it, as in that case it's clearly an implementation issue/bug with Maschine. Don't waste your time debugging their ****** HiDPI/scaling implementation ;)

  • argyre planitia
    argyre planitia Member Posts: 20 Newcomer

    Hi - I have the same problem with Melda plugins. Not with Youlean Loudness Meter, Arturia Pigments, Valhalla (Room/Reverb), TDR Nova… Only Melda. VCV Rack (plugin version) behaves a bit better, but seems to loose the resize areas in the corner/edge of the window too.

    Maschine Software is 3.0.1. Most recent. Maschine used stand-alone, not as a plugin.

    Tested Blue Cat's Patchwork as a VST host with Melda Equalizer - no problem.

    Furthermore, ALL plugin windows try to escape from my screen. After re-opening a project, I have to bring them back to their original positions.

  • argyre planitia
    argyre planitia Member Posts: 20 Newcomer

    Seems, we have to threads about this:

    https://community.native-instruments.com/discussion/32099/has-anyone-had-problems-with-the-resolution-of-vst-plugins-inside-maschine

  • Maxray
    Maxray Member Posts: 124 Advisor

    Yes, and this thread has been shortened significantly, there was much more communication and image evidence initially.

  • Maxray
    Maxray Member Posts: 124 Advisor

    So, here is where I'm at…

    I have redownloaded Maschine 2 SW. I couldn't wait any longer, it's been almost 2 months and I have projects waiting. All of my plugin windows are working fine in Maschine 2, I'll just have to copy the workflow from Maschine 3 over. It may take some time, but at least it's operational!

    I was notified that they could not recreate the issue on their systems. They are keeping the bug open as an issue in their system cue and it is marked as "unresolved"!

    For now and the unforeseeable future, I will be using Maschine 2 solely, until they can run tests and resolve the issue. Hopefully, they find a fix soon, if not, I'll try running Maschine 3 again in June.

    Below is an image of some of the plugins running as VST3s in Maschine 2 SW, which is proof that they work fine in that software version, for those of you whom have been dealing with this issue.

  • Maxray
    Maxray Member Posts: 124 Advisor
    edited January 25

    Yes, we tried that earlier, if you look at the middle and bottom of page one of the thread. That's when we started looking at graphics drivers. We had scaled all the plugins to 100% default when we started testing to eliminate any issues Windows DPI could be having displaying the items.

    Also, if you look at the images closer, you'll notice that the corner drag markers are missing because the plugin windows are actually corrupted. Which is what brought us to the conclusion that it's code/string issue.

  • DynaMaltee
    DynaMaltee Member Posts: 18 Member

    thx for reply 😎

  • PoorFellow
    PoorFellow Moderator Posts: 5,459 mod
    edited January 25

    I only found this thread now (I do not have a Maschine and only got the Maschine 3 software very recently) , and the Byome (VST2?)(is not VST3) also resize wrong and has a lot of white around on my computer and actually lock up the Maschine 3 software interface so that I have to shut down/force quit the Maschine 3 software to get out of the situation . With Triad I can get out of since the white area does not fill whole screen. I don't think that I have the Hybrid EQ so can not test with that.

    My resolution is 2560X1440 , and scaling is set at 175% (Default apparently is %200) , And I am using intel i7 CPU and NVIDIA GTX960 display adapter

  • Maxray
    Maxray Member Posts: 124 Advisor

    Yes, many of my VST2s are having that behavior as well, but I used VST3 as an example because all of my VST3s are having that behavior. That is also what the other people are saying, and they aren't just reporting the same with all of their VST3s, they are also reporting that they are different platforms, which is why I eliminated my AMD graphics drivers as the culprit. It's happening on Intel, Nvidia and Mac OS products as well.

Back To Top