Plugins built on Macos show assertion failure: Failed to create NanoVG context

wolf-plugins / wolf-shaper

Waveshaper plugin with a spline-based graph editor (LV2, VST, and CLAP)

https://wolf-plugins.github.io/wolf-shaper/

GNU General Public License v3.0

219 stars 20 forks source link

Plugins built on Macos show assertion failure: Failed to create NanoVG context #176

Open Alpha21016 opened 2 months ago

Alpha21016 commented 2 months ago

Hi I try to build wolf-shaper plugin (CLAP and VST3) on both WIN and MACOS. The plugins built on WIN work well but the plugins built on MACOS show this assertion failure when loading in DAW software: "Failed to create NanoVG context, expect a black screen, condition "fContext != nullptr" in file src/NanoVG.cpp, line 332" It seems like the initiation of NanoVG context failed but I don't know why. Both of the CLAP and VST3 plugins show nothing on the GUI window. I have tested in Bitwig studio and Logic Pro, all failed. My compile command is "BUILD_VST3=true BUILD_CLAP=true make"

pdesaulniers commented 2 months ago

Hello! Do the official binary releases have the same issue, or is it specific to your builds? https://github.com/wolf-plugins/wolf-shaper/releases

Alpha21016 commented 2 months ago

Hello! Do the official binary releases have the same issue, or is it specific to your builds? https://github.com/wolf-plugins/wolf-shaper/releases

Only my builds. Official releases all fine. My macos version is Sonoma (Macbook Pro M1Pro), wolf-shaper code version is the latest. I try to trace the code and find the function "nvgCreateGL2" returns 0x0 in NanoVG.cpp, line 209. So I wonder if there is something wrong with the DFP framework.

pdesaulniers commented 2 months ago

I don't own a Mac, so it's a bit difficult for me to debug this!

With that said, I did update DPF since last release. The latest release uses this commit: https://github.com/DISTRHO/DPF/commits/a4c83bfdc925db48f272e66a006a6630625c3e20/

Here are a few things you could try:

You could try updating DPF and see if that fixes the issue.
```
cd dpf
git pull
git submodule update --init --recursive
```
If it doesn't, I think you could also try reverting DPF to commit a4c83bf (including submodules) and see if that fixes the issue. If it does, then perhaps you could git bisect to find which commit introduced the bug in DPF.
If reverting to commit a4c83bf doesn't fix the issue either, then the issue is either on Wolf Shaper's side, or there's something about your system configuration that might be causing the issue...