Plugin UIs are cropped in Komplete Kontrol (KBDSW-8050)

mulbur · 2025-03-07T16:00:05+00:00

There was an error rendering this rich post.

Hi,

my issue is related to Komplete Kontrol 3.4.0 in Cubase 14 on Windows 11.

The UI of plugins opened in Komplete Kontrol is cropped. I observed this for plugins from U-He, AAS, Arturia. Check the right side and the lower end:

Now the same plugin without the Komplete Kontrol container. This is how it should look.

This happens when i have set Windows Display Scaling to 125% and enable HiDPI is in Cubase.

I am quite sure that this worked well until the last update of Komplete Kontrol. The current situation renders Komplete Kontrol quite useless.

Does anybody know if this is a new issue with Komplete Kontrol 3.4.0?

Find more posts tagged with

Komplete Kontrol SW

Accepted answers

Jeremy_NI

Yes, this issue should be fixed with the last update of Komplete Kontrol 3.5.0, please update in Native Access.

All comments

PoorFellow

https://community.native-instruments.com/discussion/43177/plugin-uis-are-cropped-in-komplete-kontrol

This happens when i have set Windows Display Scaling to 125% and enable HiDPI is in Cubase.

At which resolution ? Using which AAS and Arturia plugins ? Example screenshot would be nice (I'd love to have U-He Diva and other U-He but I have none)

I could test things at my resolution if I had something to compare with.

mulbur

Resolution: 5120 x 2160

Here are some more example screenshots. Left side is the Komplete Kontrol version, right side the plugin without KK wrapper. I realized that in many cases its also impossible to move knobs by mouse in the KK version.
All Arturia plugins are effected.

PoorFellow

https://community.native-instruments.com/discussion/comment/215184#Comment_215184

Resolution: 5120 x 2160

Windows Display Scaling to 125% and enable HiDPI is in Cubase.

That might help explain the problem , as far as I can see then that is 5K resolution at %125 scaling.

I am sorry I do not have the computer equipment to even begin to compare with that. Perhaps someone else that has 4K - 5K monitor could help compare ?

Alas then the only thing I myself can suggest is that you should contact N.I. Komplete Kontrol Support and share your findings with them.

In case that you need guidance contacting support : Please read : how to get support !

Vocalpoint

"Resolution: 5120 x 2160"

All the products you are displaying are designed for 1920x1080. Especially Komplete Kontrol.

Any other "scaling" or different resolutions will cause what you are seeing.

mulbur

I can report that i am using the described system setup and software since a long time. The described problems only occurs since the latest KK update.

Its important to note that i have written: "This happens when i have set Windows Display Scaling to 125% and enable HiDPI is in Cubase."
With scaling set to 100% or HiDPI support disabled in Cubase the cropping does not happen.
But this is not an option, since with 100% scaling is not suited for the 5120 x 2160 resolution and not enabling HiDPI in Cubase leads to blurry fonts and pixel graphics for everything.

Are you saying that everyone how is using a display with a higher resolution than 1920x1080 can´t use Komplete Kontrol because essential parts of the UI are not showing?

Vocalpoint

https://community.native-instruments.com/discussion/comment/215215#Comment_215215

Scaling and resolutions and how they behave are unique to each user, their DAW, their OS and lets' do not forget video drivers, their computer, graphics card and on and on.

I have no idea how/why you are seeing what you are seeing but I do know - if Windows is set to standard HD, Cubase will run in Standard HD, your plugins will be in Standard HD and NO scaling is being interjected - all your products will display correctly.

Now - I understand you will not like that (considering your farout resolution over there) but none of these products are specifically designed for 4K/5K or whatever K. They are designed for 1920x1080.

I understand that you (and many others) may have been able to jimmy things into place given your unique combo of stuff over there - but I am simply providing the facts (and system requirements).

That said - you can accept the design specs or don't but if you want to avoid hassles - 1920x1080 is the standard baseline.

JesterMgee

https://community.native-instruments.com/discussion/comment/215213#Comment_215213

I do love your apparent distain for anyone using anything that pushes monitor technology beyond 2009…. Guessing you are not a game developer, video editor or macOS user if you are stuck using 1080.

Resolution of a monitor has zero bearing on how software will display, only that a high resolution on a small size monitor results in things displaying much smaller (science). The DPI/Scale setting is what causes the issue as it has to try inflate the size of applications artificially and this is not always done correctly over all elements of an application, happens with numerous applications which is why some applications have better self scaling options than the overall OS scaling of Windows

Sadly for the OP, if setting a scale increase causes these issues, you will likely have to submit a bug report to NI. Scaling works fine with most DAWs and plugins themselves but the handling of scaling plugins within a loader like KK is not always done well. It is one of those things with high DPI monitors tho, not all technology has caught up perfectly. I run a 3440 resolution monitor however it is not high DPI and so I do not increase any scaling, never an issue as I would expect, it is just a larger desktop size.

Vocalpoint

"I do love your apparent distain for anyone using anything that pushes monitor technology beyond 2009…. Guessing you are not a game developer, video editor or macOS user if you are stuck using 1080"

Well - to be clear - it is most definitely not distain. Just trying to suggest a solution by a simple return to standard baselines.

But none of the products discussed are supported under a resolution of 5120x2160. Those are the facts, or this thread would not exist.

The OP can make up his own mind - get busy working or stay busy hacking around with display issues.

JesterMgee

1080 may have been the standard 15 years ago, but standards are not hard set rules and things evolve.

Companies need to keep up with the changes and work to address these kinds of issues as many systems that come out now offer better than 1080 displays and anyone working in most professional media environments are certainly not using the limitations of a 1080 display. That is almost like saying 15 years ago "who is running anything more than 1024x768". companies need to begin working towards compatibility rather than playing usual catch-up down the road.

The issue is a scaling problem, due to ill designed software that does not correctly factor in the scale, it is a software issue that could be addressed…. if it is reported by users. This is why we should encourage rather than suggesting the OP is somehow outside the norms of reality for working on a larger monitor. Issues would likely be addressed faster if more people actually spoke up and demanded fixes rather than just accept limitations.

Vocalpoint

"Companies need to keep up with the changes and work to address these kinds of issues as many systems that come out now offer better than 1080 displays and anyone working in most professional media environments are certainly not using the limitations of a 1080 display"

Companies will only ever "keep up with the changes" when they can profit from it. They will not build beautiful fully scalable 4K interfaces for 4.2% or 6.8% or 9.1% of the worlds computing population with a fancy 4K monitor. There is no money in for them when the other 90+% of users do not (and will not) use 4K and don't care.

You are advocating for a battle here that cannot come from just one vendor here or there - this change has to come from a worldwide collection of hardware and software makers. Standards only become standards - when EVERYONE buys in.

Just like when we jumped from 800x600 to Standard HD - the globe embraced it, the display makers embraced it and the software industry embraced it. Everyone wins.

But for anything beyond Standard HD - with what feels like 15 years behind us now - it seems like nobody cares - and that's because for most companies, developers, hardware makers AND first and foremost - the customer buying this stuff - standard HD is still good enough.

And - I am certainly not disagreeing with you. "Evolution" in this space would be wonderful if the world actually got it in gear and embraced this technology. But until it does - on a very large scale (no pun intended) - the only true answer to these endless posts about "why does my display looks wonky" - is to run in Standard HD

TROND

Same problem here. Cubase 14 running Komplete Kontrol scales down the plugin rendering it useless. Resolution 7680x2160 with 125% scale. This is clearly a bug, not a question about what standard this and that VP is talking about.

TROND

Screen Shot 2025-03-31 at 02.27.46.602 PM.png

Komplete Kontrol in Cubase 14 with 7680x2160 resolution with 125% scale in windows.

TROND

Kontakt is working fine by the way, but not Komplete Kontrol.

TROND

Maybe the programmer/s on Komplete Kontrol's UI should ask the programmer/s on Kontakt how to fix it?

Vocalpoint

https://community.native-instruments.com/discussion/comment/219203#Comment_219203

I would bet money this works fine in 1920x1080 - with NO scaling.

Quick links

Unanswered questions