search

DISTRHO / Cardinal

Virtual modular synthesizer plugin
https://cardinal.kx.studio/
GNU General Public License v3.0
2.18k stars 149 forks source link

Nightly version is showing up black on new instances. #373

Closed scotttswan closed 1 year ago

scotttswan commented 1 year ago

when loading a previous project with a Cardinal instance it loads fine but if i add a new Cardinal instrument/fx it loads up with just a black screen.

Tested on both Reaper and Bitwig.

dBiz commented 1 year ago

Yep, black screen also here in Cubase 11 and FL, on windows 10

dBiz commented 1 year ago

I've tried resizing the window and it works ;) image

scotttswan commented 1 year ago

Yeah Resizing makes it appear but the initial load bug is still there.

falkTX commented 1 year ago

please try with the latest nightly, thanks

dBiz commented 1 year ago

Same, I've to resize it ;) but is not a big deal!

falkTX commented 1 year ago

it is, if the first thing a user sees is a black screen they just assume it is not working.

I am unable to reproduce though, so I need details on what your system and host is. maybe related to non-integer desktop scale factor/zoom ?

dBiz commented 1 year ago

I'm trying this on Cubase 11 and FL ( both the latest version available ), on Windows 10. Both VST3 and VST2 do the same thing, On Cubase seems some plugins have OpenGL issues .... here's what I Found https://helpcenter.steinberg.de/hc/en-us/articles/360017509919-Cubase-11-Using-DPI-unaware-plug-ins-on-Windows

falkTX commented 1 year ago

Cardinal is high-dpi-aware, so the link details do not matter here. seems issues are only on Windows from what I can tell..

scotttswan commented 1 year ago

it could be that in "updated" over the stable release rather than installed from fresh? i'll check again.

fotisandstuff commented 1 year ago

it could be that in "updated" over the stable release rather than installed from fresh? i'll check again.

I made a fresh install of the nightly d5e6f50a and the problem persists. Windows 10 x64, Reaper.

falkTX commented 1 year ago

I was able to replicate the issue, pushed a fix. Please try with https://github.com/DISTRHO/Cardinal/actions/runs/3048050382 once it becomes available.

dBiz commented 1 year ago

Now it works ;)

fotisandstuff commented 1 year ago

Nope, still happens. The weird thing is that it happens the second time I load an instance.

falkTX commented 1 year ago

Nope, still happens. The weird thing is that it happens the second time I load an instance.

knowing what the issue was, I find it almost impossible for the issue to still be happening. double-check that you installed the new build please.

falkTX commented 1 year ago

just tested the nightly/action/CI builds with a known broken setup and can confirm it does work.

scotttswan commented 1 year ago

can confirm its now working. in latest bitwig

fotisandstuff commented 1 year ago

Nope, still happens. The weird thing is that it happens the second time I load an instance.

knowing what the issue was, I find it almost impossible for the issue to still be happening. double-check that you installed the new build please.

Whoops, you're right. It was my fault. I had accidentally re-installed the previous build. It's all good now, thanks a lot!!!