Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

LV2 on Windows: resource problems for the UI #71

Closed
paulfd opened this issue Oct 23, 2020 · 6 comments · Fixed by sfztools/sfizz#524
Closed

LV2 on Windows: resource problems for the UI #71

paulfd opened this issue Oct 23, 2020 · 6 comments · Fixed by sfztools/sfizz#524

Comments

@paulfd
Copy link
Member

paulfd commented Oct 23, 2020

image

This is in Mixbus 6.1 and Ardour 6.3.

@jpcima
Copy link
Contributor

jpcima commented Oct 23, 2020

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
Copy link
Member Author

paulfd commented Oct 23, 2020 via email

@redtide
Copy link
Member

redtide commented Oct 23, 2020

AFAIK most of our packages have no installer

@paulfd
Copy link
Member Author

paulfd commented Oct 23, 2020

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
Copy link
Contributor

jpcima commented Oct 23, 2020

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
Copy link
Contributor

jpcima commented Oct 24, 2020

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.

Capture du 2020-10-24 05-05-17

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants