1. IMPORTANT:
    We launched a new online community and this space is now closed. This community will be available as a read-only resources until further notice.
    JOIN US HERE

Massive X "Auto-Scale" problem in Live 10

Discussion in 'MASSIVE + MASSIVE X' started by SLG-1, Jan 25, 2021.

  1. SLG-1

    SLG-1 New Member

    Messages:
    5
    Hey guys, I am having a problem with the scaling of Massive X's GUI in Ableton Live 10.1.30 on Windows 10 (3840 x 2160 display, Intel(R) HD Graphics 630 / NVIDIA GeForce GTX 1050).

    When I load it up with the "Auto-Scale Plug-In Window" option on, Massive X looks as you'd expect -- pixelated -- because Live automatically scales it up to prevent it from rendering too small on a 4K screen. But this auto-scaling causes a drop in resolution. Everything functions correctly otherwise.

    What I do for all my other plugins is I set the "Auto-Scale Plug-In Window" option to off which causes them to look small initially but I then scale them up to a nice and crisp 200% using the plugins' built-in scaling settings. This works with all my u-he and Xfer plugins out of the box.

    Massive X, however, gets cropped (see screenshot below) and the mouse has some kind of offset where the clicks do not happen under the cursor. In other words, it doesn't work, so I am stuck with either the pixelated UI or with the broken UI.
    [​IMG] [​IMG]

    Anyone else running Massive X on Live? Any similar issues? Any ideas for a fix?

    Peace.
     

    Attached Files:

    Last edited: Jan 25, 2021
  2. Jeremy @ NI

    Jeremy @ NI Support Team NI Team

    Messages:
    1,339
    Hey SLG-1,
    Could you get in touch with us and report your issue through this typeform ?
    https://support.native-instruments.com/hc/en-us/articles/360009382457
     
  3. SLG-1

    SLG-1 New Member

    Messages:
    5
    Hi Jeremy, thank you for helping out.
    I actually opened a ticket via the Typeform earlier today.
    Will you be able to locate it or do you need me to re-submit it via the link in your post?
     
  4. Jeremy @ NI

    Jeremy @ NI Support Team NI Team

    Messages:
    1,339
    Hey SLG-1,
    Please send me the request number by private message (start a conversation).
     
  5. SLG-1

    SLG-1 New Member

    Messages:
    5
    Updating this thread with some new info.
    1. Support replied that this was a bug on their end. No solution or workaround has been offered for the moment.

    2. Massive X has the same exact problem when running inside of Ableton Live 11 Suite Beta.

    3. Massive X has a sharp beautiful interface when running inside of Steinberg Cubase 11 Elements.
     
  6. wjoyce

    wjoyce Member

    Messages:
    42
    Did you get any resolution SLG-1? I've just upgraded to KU13 and getting similar behaviour within Studio One Pro 5.2.1.

    4K main monitor, FHD secondary. NVIDIA 1050 Ti.
     

    Attached Files:

    • Like Like x 1
  7. spotter

    spotter New Member

    Messages:
    1
    I am having the same issue with VST plugins from the Komplete Ultimate 13 suite and Studio One Pro 5.2.1.64495
    Most of the VSTs are not displaying the entire UI regardless of whether they scale for a main 4k display.
    moving them over (dragging) to a secondary 1080 display doesn't help - in fact the window will pad out wider intermittantly until it is wider than both monitors with no way to reset the sizing.... considering I just upgraded to Ultimate 13 and Studio One V5... frustrated beyond belief... since I can't use the NI VSTs properly...

    EDIT: I have uploaded a webm of the dragging vst from screen to screen issue - not positive its NI only on this one but it also shows how the VST does not display its interface correctly in Studio 1 v5

    https://webm.red/EP7o
     
    Last edited: Jun 5, 2021
    • Like Like x 1
  8. SLG-1

    SLG-1 New Member

    Messages:
    5
    I ended up selling Massive X for reasons unrelated to this (although the scaling issue didn't help its case), so my conclusion was that it looked great in Cubase but not in Live. I didn't explore beyond this. I hope you find a solution!