Cubase 10.5.20 Maintenance Update

Cubase
81

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

82

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 …

83

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.

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!

84

At this point you just lost all credibility.

85

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:

86

I use that functionality all the time. if Steinberg/Yamaha are not able to fix this in 10.5 and will leave it on a TODO list for 11.0.x, then 11.0.x should be a free update to 10.5.x users.

87

I don’t care who you are, it’s nonsense. It would not even be possible to perform basic regression testing of an app the size of Cubase in 3 Days.

88

It’s only Windows issue, no such problem on MAC

89

Hi,

Could you use Microsoft ProcDump utility to generate a DMP file and share it here, please?

I would prefer to make a new thread for this one (you can send me the link via PM then), please.

90

You should focus that the problem is only related to plug-ins, not all program windows, interfaces

This does not require a long time to program it, but it seems that the company wants to bring the money in a stupid way
I am ready to volunteer and help the company solve the problem

Because if a free update does not come to us with a solution to the problem, we will not upgrade

91

I think the users are a bit right in their anger here Matthias, this was a feature promised in cubase 10, and it will be (hopefully) delivered in cubase 11 two years later. What is the reason for this? how can you boldy advertise a feature that will not be delivered in TWO YEARS, and expect your users to keep giving you their hard earned money,

If you can´t deliver it, don´t tease us, and we can decide if we want to jump ship or not. It shows an giant lack of communication (been hammering this for ages and I thought you´ve had improved) and I believe it´s borderline deceitful on steinberg´s part.

Don´t get me wrong I love Cubase and depend on it for my income, but I have been uprgrading for years, foolishly waiting for a working hdpi solution.

92

It is not only plugins, I have 2 monitors with different dpi / scaling and Cubase does all sort of really weird and annoying things, all the time!.
The main menu sometimes gets so small that’s impossible to read, and the selected menu underneath the mouse is all messed up and impossible to select the right thing.
Same for some floating windows such as transport and colors, they resize to tiny windows and also don’t react properly to the mouse when dragging.
Moving things from one window to another, usually ends in unexpected behavior.

Expression maps are broken from day one on 10.5 and wasted countless hours already.
Lately i’ve even noticed that problems occur even when exporting, so i have to keep re-listening and re-exporting until Cubase decides to play all the articulations the right way.

Lately, for the first time in years, I also started looking for a different option, and that’s really a pity, because i really, really love Cubase :frowning:

93

Two years, they solve the problem if they had planned to travel to the moon would have been faster

But if they come to us with free temporary solutions, they calm us down a little and then they have an excuse to sell version 11 while resolving all problems.

94

I trust that Steinberg have heard our cries and are working the problem as I type.

95

With much respect but something tells me that solving hanging on exit issue wasn’t on radar for 10.5**.20** and the DMP files wont get any further with it (in other words you have plenty of dmp files) or on the other hand issue is so vast that isn’t easy to track what causing it. I wouldn’t say its plugin specific since for some users same plugins doesn’t trigger hanging issue and for some does. Particular in my case its system specific.
-On windows 1511 All works without hangings
-On Windows 1909 ArtsAcoustic Reverb, xfer OTT, Reveal Spire (all latest versions) causing hangings.
Same machine (my signature) with latest drivers, Cubase 10.5.20, Reaper(works without hangings)

After 15 years with cubase we all develop some sort of feelings for the issues and for some of them we find workaround on our own, but this smells me like the way how cubase handle graphics which lets be honest Steinberg has lot of things to do and fix in this department.

Here are details from Dump hour ago and the trigger of hanging is Spire.

Loading unloaded module list
................................................................
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for KERNELBASE.dll - 
ntdll!NtWaitForSingleObject+0x14:
00007ffd`66b3c144 c3              ret
0:000> !analyze
*******************************************************************************
*                                                                             *
*                        Exception Analysis                                   *
*                                                                             *
*******************************************************************************

Use !analyze -v to get detailed debugging information.

*** ERROR: Symbol file could not be found.  Defaulted to export symbols for D3D10Warp.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for d3d11.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for d2d1.dll - 
*** WARNING: Unable to verify checksum for Spire-1.1.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for Spire-1.1.dll - 
*** WARNING: Unable to verify checksum for VSTPlugManager.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for VSTPlugManager.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for user32.dll - 
*** ERROR: Module load completed but symbols could not be loaded for Cubase10.5.exe
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for kernel32.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ole32.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for combase.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for CoreMessaging.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for inputhost.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for win32u.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for SYNSOACC.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for nvwgf2umx.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for mediaservice.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for BC PatchWork VST3.vst3 - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for videoengine.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for hdspasio_64.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for wdmaud.drv - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for nvoglv64.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for videoengine.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for Cubase Plug-in Set.vst3 - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for GdiPlus.dll - 
*** WARNING: Unable to verify checksum for ElastiquePitchV2.vst3
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ElastiquePitchV2.vst3 - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for Sampler Track.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for msvcp140.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for Kontakt.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for ucrtbase.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for netbios.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for Groove Agent SE.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for baios.dll - 
*** WARNING: Unable to verify checksum for MODO BASS.vst3
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for MODO BASS.vst3 - 
*** WARNING: Unable to verify checksum for MelodyneCore-5.0.1.003.dll
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for MelodyneCore-5.0.1.003.dll - 
*** ERROR: Symbol file could not be found.  Defaulted to export symbols for twinapi.appcore.dll - 
GetUrlPageData2 (WinHttp) failed: 12029.
Probably caused by : D3D10Warp.dll ( d3d10warp!Ordinal199+2f89ad )

Followup:     MachineOwner

I am back and camping on 10.5**.12** cause of mediabay “issue” that is introduced in .20

96

Hi,

From my point of view, I can see clear relation of Windows version & plug-in.

How can Cubase affect one of these? Both of them are 3rd party. Or am I missing your point?

97

With Cubase 10 we had to make the decision whether to hold back the HiDPI support for both platforms, or release it in a first iteration with limited support on Windows 10. And that is how we advertised it: full HiDPI support on macOS, but only limited support on Windows 10. There was a link to a knowledge base article with the limitations since day one. We tried to make it a transparent as possible, but we didn’t want to hold back the HiDPI support for macOS users.

I understand the frustration of some of you who have already invested in 4k monitors and we are sorry that this takes time. It is really a complex topic and not a matter of a few lines of code.

98

Seems to be working fine in my humble hobbyist setup. I still have crashes (Cubase freezes for a few seconds, then quits) when browsing through presets on 3rd-party plugins. Notably Arturia V-Collection and anything by IK Multimedia, which started to happen since .12
Also still getting the black cursor.

99

Cubase seems to randomly crash once a day since I updated to 10.5.20 - always been pretty stable before.

100

Please bring this back. It really speeds up changing of grid values.

This is the second thing your team removed for consistency that really slows down workflow- the first one was the decimation of the right click menu (we have to travel to the main top menu to use some of the command like range and glue).