Plugin not using monospaced fonts

[escuta]

Thanks for giving yabridge a shot!

• I read through both the troubleshooting and the known issues sections, and my issue wasn't listed there

Problem description

The fonts displayed in the Windows VST3 plugin "K2x00 Remote" are incorrect making the edit window of the plugin difficult to read (and often unusable).

What did you expect to happen?

In Windows, I understand that the plugin uses the default monospaced font. Someone from a K2x00 forum posted the attached image:

The edit window of the plugin should look like this (a screen shot on Windows 11):

What actually happened?

Instead of a monospaced font being used, the plugin opens Arial and Tahoma

$ lsof -c yabridge | grep ttf
yabridge- 126502 me mem       REG               8,19   951868 155058589 /usr/share/fonts/TTF/tahoma.ttf
yabridge- 126502 me mem       REG               8,19   364676 155212055 /home/me/.wine/drive_c/windows/Fonts/arial.ttf

The resulting edit window has a compromised layout, such as the following:

Operating system

Arch Linux

How did you install yabridge?

Pacman

yabridge version

5.1.1-1

yabridgectl version

5.1.1

Wine version

wine-9.20-1

Plugin

K2x00 Remote (a Kurzweil synthesiser editor)

Plugin type

VST3

Plugin architecture

64-bit

Host

wine-9.20-1

Desktop environment or WM

Xfce

GPU model

No response

GPU drivers and kernel

No response

Debug log

yabridge.log.gz

Anything else?

Other than the font problem, the K2x00 Remote plugin works as it should.

[relaborn]

This might sound silly or potentially obvious to you but do you have a monospace font installed that windows might recognize? Font problems are often solvable by installing the required fonts directly within the wine prefix if adding system fonts doesn't work.

Does /home/me/.wine/drive_c/windows/Fonts/ contain any monospace fonts?
In a wine prefix I haven't changed the fonts on the default monospace font is Courier New. Liberation fonts on your system should cover that or Courier New in your prefix.