Lockups with plugins on multi-screen configuration

Cubase
,
#1

I am having significant issues with plugins and Cubase freezing for a range of plugins when used on a multi-screen configuration. Cubase Pro 10.0.20 on Windows 10 Pro x64 (1903) with nVidia GTX 1650 graphics connected to Dell P2314T MultiTouch 1080p (DisplayPort) monitor set as primary and Dell U3417W UltraWide 3440x1440 (DisplayPort) set as secondary monitor. With 100% scaling on the 1080p and either 100% or 125% scaling on the UltraWide secondary monitor, I face the following problem with Arturia V Collection 7 (and previous ones, since their scalable UI was introduced) as well as the MasteringTheMix plugins LEVELS and REFERENCE:

  1. Add/open VST on primary monitor - all ok

  2. Move to secondary monitor - all still ok

  3. Move back to primary monitor - all still ok

  4. Close on primary monitor - all ok

  5. Reopen and retest - all ok.

  6. Add/open on primary monitor - ok

  7. Move to secondary monitor - ok

  8. CLOSE on secondary monitor - appears to be ok

  9. Open again, opens with blank edit area - moving to primary monitor does not help

  10. Try to close, it freezes Cubase completely, needing the process to be killed! Because it is killed, no crash dump log available.

  11. After restarting Cubase, try to add/open again, and now it tries to open on second monitor with problems as per step 9.

  12. Only way then is to kill Cubase, disable extended screen mode, launch to get it back on primary screen, and then close it in that mode.

Have been working with both Arturia and MasteringTheMix but have not been able to get it resolved with them. The issue does not occur on REAPER, but does (but without the issue of having to kill the process) in Cakewalk/SONAR Platinum. Not tested in others, but seems to be something to do with the initial drawing process when on the secondary screen. As its more than just one plugin manufacturer, is this something Steinberg can/should be looking at?

Interestingly, MasteringTheMix use OpenGL in their plugins - not sure about Arturia, but I suspect they might also be doing the same. Have also had issues with Cherry Audio’s Voltage Modular when it is configured to use OpenGL - so there appears to be a conflict going on between OpenGL in Cubase and the plugins.

#2

An update after some further research - looks like Waves plugins, which also apparently use OpenGL, seem to also suffer from the same issue. And just also tested a new plugin from MasteringTheMix that is NOT OpenGL based (BASSROOM) and which works fine… so all things pointing to this being an issue with OpenGL based plugins on multi-screen monitors (maybe specific to the Intel and nVidia drivers as have not tested with an AMD GPU) when instantiated from Cubase.

#3

Sorry for bringing up such an old thread, but I’m having exactly the same problem, and it’s driving me nuts. Did you ever find a solution to the problem?
I have the same graphics card as well.

#4

This is happening to me as well, EXACTLY as stated, in my case I can confirm also happening with Nugen plugins.
I do believe it might not be Cubase’s fault, because when testing the standalone versions of Nugen plugins, it still happens. With Waves plugins instead, the standalone versions seem to be working fine.
The odd thing is that before reinstalling Windows, everything was working perfectly fine. It’s like an update of Windows broke this function? Why isn’t this happening to everybody?

#5

Maybe this is my issue? I have 4 monitors (just added the 4th) have gui problems on my control room inserts. I will try disconnecting. Monitors 1 by 1 and see if that helps my problem

#6

I, and another studio owner I know are both having this issue. New build AMD based system (12 core 3900x processor, Asus motherboard and GPU Nvidia card). Was there ever a resolution to this?

#7

Hi guys, I just created an account here to post a possible solution. I had the exact same problem with other DAWs (I am not a Cubase user) and found this thread about it. But I also found another one:
https://discuss.cakewalk.com/index.php?/topic/4083-solved-major-freezinghanging-issues-with-an-interesting-cause-and-no-obvious-solution-any-ideas/page/3/
There is the solution posted, that “Nahimic” needs to be uninstalled. In that thread only MSI boards are talked about, but it can be part of other onboard audio drivers AFAIK. I also had that software on my machine and after uninstalling it everything is fine. Maybe that helps!

#8

Hey guys, same issue here. Experienced the issue just now with a new plugin I bought (Gullfoss) and I’ve reported it back to the vendor hoping they can shed some light on this.

I have a 4-screen setup where a few plugins freezes when the UI is opened up on a non-primary monitor. This does not seem to be HW related though. My build is a Asus MB with i9 CPU and Nvidia RTX 3080 GPU (also reproduced on a GTX 970 card) and people are reporting the issue with all kinds of HW setups.

Funny part is; I’ve seen the exact same behaviour with Native Instruments download client (Native Access) (Cubase was not running). So, to me it doesn’t seem to be related to Cubase either. I don’t know, but to me things are pointing to the library used to render the UI and is independent on HW except for multiscreen setup. Whether this is OpenGL or something else, I have no idea.
I know this wasn’t very helpful but perhaps could point someone in the right direction.