LV2 on Windows: resource problems for the UI about sfizz-ui

[jpcima]

Custom fonts paths are available only for msvc builds running on Windows 10.
In older Windows and in MinGW, install the fonts in the system directory.
Our installer does this automatically.

[paulfd]

Ok so that's because I just copied the LV2 directory without installing. I'll try later. Oct 23, 2020 19:04:20 JP Cimalando <[email protected]>:

…

Custom fonts paths are available only for msvc builds running on Windows 10. In older Windows and in MinGW, install the fonts in the system directory. Our installer does this automatically. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub[#71], or unsubscribe[https://github.com/notifications/unsubscribe-auth/ADUFWQPWCCIKVPI4DII3MXDSMGZPVANCNFSM4S4YYCDA]. [https://github.com/notifications/beacon/ADUFWQJRTG5DNDVZBTSR2HDSMGZPVA5CNFSM4S4YYCDKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFKSRQ3Y.gif]

[redtide]

AFAIK most of our packages have no installer

[paulfd]

Custom fonts paths are available only for msvc builds running on Windows 10.
In older Windows and in MinGW, install the fonts in the system directory.
Our installer does this automatically.

However this was with msvc on windows 10 so we may yet have a problem :D

[jpcima]

It's available since some particular revision of windows sdk.
Check if this part of code gets compiled in your environment.
https://github.com/sfztools/vstgui/blob/055cbcc9ae858f0b07d5d86c205a1111e2fba7a4/vstgui/lib/platform/win32/direct2d/d2dfont.cpp#L35

[jpcima]

The problem is as follows:

• Under Windows, we are using this as a resource path: <lv2-bundle-path>\Contents\Resources\
• The LV2 bundle path is provided as an argument to the instantiate call
  The LV2 specification has to say: "Path to the LV2 bundle which contains this plugin binary."
• However, what we get is not the bundle path of sfizz.lv2, it's the subdirectory which contains the DLL instead.

It seems like an anomaly of Ardour or Lilv. For now I can implement a workaround to this.