Cubase 10.5.20 Maintenance Update

[Ehabmxd]

@Quietly

@Outsounder

Steinberg want to sell you the same thing twice or three times. Chase 10 with 4k support, Cubase 10.5 with 4k support and next it will be Chase 11 with 4k support and lots of new bugs. for lots of money. Everybody should write to their local trading standards office and complain rather than write to steinberg, they’re not bothered.

I couldn´t agree more but I have the feeling its Yamaha that´s not bothered because if they were they would have ordered someone to sort it by now. Unless of course it is impossible to do so in which case they should be honest enough to say so.

I totally agree with you
I am shocked by all this ignorance
I have previous experience in programming, solving the issue does not require much time

And if you got errors with them during programming
Microsoft has programmed Windows 10 from scratch
It is an integrated computer system, not a program

The solution should be completed as soon as possible, even if it is temporary, because this is a basic requirement and not an Extra Feature

[garymusic]

I just updated from 10.5.0 to 10.5.20 and seems to be working ok so far on Macbook Pro running OS 10.14.6. That was not my experience with 10.5.12. I’ll report if there are any issues I come up with.

[VHProductions]

No hiDPI for Windows versions yet I see.
Over 20 years of dedication to your company and I am realizing maybe further dedication to you may be a mistake.
It’s time to take a serious look at Studio One.

[Martin.Jirsak]

@Pablo1980

I am having a problem where the cursor always go back to a measure of it´s choosing after stopping playback, no matter where I start playback, it always go back to that measure. I closed cubase and restarted and it chose another measure to lock on to. Strange

Hi,

Could you try in Cubase Safe Start Mode [Disable preferences], please? Just to confirm or disprove it’s a preferences issue.

[Martin.Jirsak]

@Aurosonic

Please fix Cubase hangs on quit when using heavily buffered plugins like Acustica Audio Nebula and Acqua. All other DAWs manage it easily.

Hi,

Are you on Mac or Windows, please?

[Martin.Jirsak]

@atlanta

All was well until i tried to install 10.5.2…now I’m;

…unable to get a clean install of 10.5.20, using late-2012 i7 MBP & Catalina 10.15.5…
…program Initializing: be comes unresponsive while scanning vst3 plugins…
…am unable to load 10.0.6, 10.5.0 as well…same scenario…
…properly installs if i choose to load only Steinberg plugins…

I am back to 9.5!
any suggestions are welcomed…

BTW - UAD LUNA WORKS JUST FINE!!

Hi,

Cubase 10.0 and Cubase 10.5 are independent applications, they event don’t share the preferences. So it’s hard to imagine Cubase 10.5 installation would affect Cubase 10.0.

What eLCC version do you use, please?

[Martin.Jirsak]

@beerbong

PS. Is text supposed to look like this in the Connections window?

https://i.ibb.co/93KMp7N/whitetext.jpg

Hi,

This is broken since Cubase 10.5.0. It’s known and already many times reported issue. Thank you.

[djgraver]

Does this bug exist in 10.5 ? https://steinberg.net/forums/viewtopic.php?f=286&t=190347
Its very important fix for my work

[Matthias_Quellmann]

@ca-booter

No thanks here…Just installed it and immediatly got CPU overload while playing a heavy mixproject which played just fine yesterday.
Around 85-90% CPU load, but now in the red so dropouts.
Two (FW and USB) interfaces, both same results.
Now I can’t play this mix anymore.
What happened?
nothing changed on my computer or settings since yesterday, only todays update of Cubase.
Tried the “suspend vst3”, because that was the only difference I read, but no advantage.

[EDIT]: I disabled HT in the Bios and now I have more headroom on the CPU.
I did test with or without HT very often in the past, never noticed any difference so I let it enabled. But now is HAS to be disabled otherwise I can’t play my larger projects anymore.
So there must be a defintive change in the 10.5.20 update concerning this.
But I’m glad I can work again…

Hi there,

Our QA is on it and will check if they can reproduce the issue.

Thanks for the report,
Matthias

[Matthias_Quellmann]

@Orestis

Thank you guys for the new update, checking it right now, looks promising !!

But please someone can give me an answer to this :
Grid Type and Quantize Preset Menu Options don’t change anymore with the MOUSE WHEEL ???
https://www.steinberg.net/forums/viewtopic.php?f=283&t=189853

Thank you in advance, but it is one of the most important workflow options!!!

Hi,

This change was intentional to improve the consistency of these type drop down selections. I will talk to the team about your feedback.

Thanks,
Matthias

[Matthias_Quellmann]

@Quietly

HiDPI Scaling still not resolved and according to you that was high priority. Clearly not high enough, very disappointing.

We are still working on it. It’s not a quick win and the scaling needs a lot of testing and refinement though. Unfortunately there won’t be any improvement before Cubase 11.

[Matthias_Quellmann]

@Pablo1980

I am having a problem where the cursor always go back to a measure of it´s choosing after stopping playback, no matter where I start playback, it always go back to that measure. I closed cubase and restarted and it chose another measure to lock on to. Strange

It seems like a hick-up in the prefs. Have you tried to delete your preferences?

[JBuck]

@Matthias Quellmann

@Orestis

Thank you guys for the new update, checking it right now, looks promising !!

But please someone can give me an answer to this :
Grid Type and Quantize Preset Menu Options don’t change anymore with the MOUSE WHEEL ???
https://www.steinberg.net/forums/viewtopic.php?f=283&t=189853

Thank you in advance, but it is one of the most important workflow options!!!

Hi,

This change was intentional to improve the consistency of these type drop down selections. I will talk to the team about your feedback.

Thanks,
Matthias

I’m not believing what I am reading right now. Anyone ever heard the saying “IF IT ISN’T BROKEN DON’T FIX IT”?

[Outsounder]

@Matthias Quellmann

@Quietly

HiDPI Scaling still not resolved and according to you that was high priority. Clearly not high enough, very disappointing.

We are still working on it. It’s not a quick win and the scaling needs a lot of testing and refinement though. Unfortunately there won’t be any improvement before Cubase 11.

Huh! But we’ve already bought it as it was advertised 18 months ago! Does that mean that cubase 11 will be a free upgrade for people who’ve already bought Cubase 10 HiDPI when it was releasd? And what about eucon? 4-1/2 years down the line and still no update!

[BaseCu]

@Matthias Quellmann

@Orestis

Thank you guys for the new update, checking it right now, looks promising !!

But please someone can give me an answer to this :
Grid Type and Quantize Preset Menu Options don’t change anymore with the MOUSE WHEEL ???
https://www.steinberg.net/forums/viewtopic.php?f=283&t=189853

Thank you in advance, but it is one of the most important workflow options!!!

Hi,

This change was intentional to improve the consistency of these type drop down selections. I will talk to the team about your feedback.

Thanks,
Matthias

Please bring this functionality back as an option. I use it numerous times during each session, so much so that I rolled back to the previous version.

[Orestis]

@Matthias Quellmann

@Orestis

Thank you guys for the new update, checking it right now, looks promising !!

But please someone can give me an answer to this :
Grid Type and Quantize Preset Menu Options don’t change anymore with the MOUSE WHEEL ???
https://www.steinberg.net/forums/viewtopic.php?f=283&t=189853

Thank you in advance, but it is one of the most important workflow options!!!

Hi,

This change was intentional to improve the consistency of these type drop down selections. I will talk to the team about your feedback.

Thanks,
Matthias

Thank you Matthias for your answer, really appreciate it and looking forward to it

[Ehabmxd]

@Matthias Quellmann

@Quietly

HiDPI Scaling still not resolved and according to you that was high priority. Clearly not high enough, very disappointing.

We are still working on it. It’s not a quick win and the scaling needs a lot of testing and refinement though. Unfortunately, there won’t be any improvement before Cubase 11.

First, all the respect to u. I appreciate that you work hard, but I hope that you are joking because in this way you will lose your customers.
Do you expect customers to upgrade to Cubase 11 after we were tricked in10?
how will we work with this long period? We cannot run any additional components that are supposed to bring to us a free temporary solution


I expect that everyone will move to Studio one it in the future, just as you lost clients before, you will lose more.
u can’t spend more to solve this .? u can’t work more time to Programming .?
forgive me …

[valkolton]

@Matthias Quellmann

@Quietly

HiDPI Scaling still not resolved and according to you that was high priority. Clearly not high enough, very disappointing.

We are still working on it. It’s not a quick win and the scaling needs a lot of testing and refinement though. Unfortunately there won’t be any improvement before Cubase 11.

Thanks there is a small light at the end of this tunnel…

HOWEVER - I know engineers may say this is not quick, but as a CEO of engineers and a former programmer myself, this fix for HiDPI support of plugin windows is only a few dozen lines of code and a couple monitors for one coder. MAYBE another pair of eyes to help test all edge cases. I guarantee I could fix this issue in 3 days MAXIMUM.


Taking 2+ years to fix this for Nuendo/Cubase with potentially thousands of users complaining and ~10x+ not complaining but experiencing issues is driving everybody crazy. It damages reputation and sales during trial periods considerably.

Look at Windows API docs on DPI:

a simple function process like this is needed:

FUNCTION OnEditVSTInstrument or OnWindowMoved
GET MONITOR DPI (multi monitors)
ADJUST DPI
TEST

protected virtual void OnDpiChanged(DpiScale oldDpi, DpiScale newDpi)

Here is the latest Windows per monitor HIDPI API docs. Most of the HiDPI API for Windows was last modified in 2018.

https://github.com/microsoft/WPF-Samples/blob/master/PerMonitorDPI/readme.md

AND TESTING:

After you have updated your application to become per-monitor DPI aware, it is important to validate your application properly responds to DPI changes in a mixed-DPI environment. Some specifics to test include:

Moving application windows back and forth between displays of different DPI values
Starting your application on displays of different DPI values
Changing the scale factor for your monitor while the application is running
Changing the display that you use as the primary display, signing out of Windows, then re-testing your application after signing back in. This is particularly useful in finding code that uses hard-coded sizes/dimensions.

THAT’S IT!

[RichardTownsend]

@valkolton

As a former pro programmer, I guarantee I could fix this issue in 3 days MAXIMUM

At this point you just lost all credibility.

[valkolton]

@RichardTownsend

@valkolton

As a former pro programmer, I guarantee I could fix this issue in 3 days MAXIMUM

At this point you just lost all credibility.

Really? You think scaling DPI on Windows opening and moving is hard?! I am currently the CEO of a company developing AR/VR applications using Windows/Unreal/Unity; before that I was a Microsoft certified programmer and database specialist and coded from when I was 7-25 years old. I was also the founder and CEO of a company I sold to Roland. Google me.

Sheesh.

Why don’t you read the Windows API examples how to do this, it is quite simple:

https://github.com/microsoft/WPF-Samples/blob/master/PerMonitorDPI/readme.md