Rui Nuno Capela

the gmsynth.lv2 package from archlinux.org is really something: it explicitly patches the x42's upstream source code to exclude the bundled fluidsynth static code in favor to system shared libraries... (can't...

the _standard version_ has this means (shared memory) to detect whether another instance is already up and running and if it is relinquish control to it and bail out. upstream...

https://github.com/rncbc/qpwgraph/blob/0a56c93651a250ae162b1d32a73d8b7022702a00/src/qpwgraph.cpp#L147-L270

port-groups aren't planned; though you may multi-select several, even non-contiguous, ports in either side and (dis)connect them as in a group.

seems to me that a QString::fromUtf8() is needed in: https://github.com/rncbc/qsynth/blob/936bedbb579ecb522c20f6988455f10c2d7a4bbd/src/qsynthSetupForm.cpp#L166-L167 like this? ```C++ (pData->pListItem)->setText(iCol++, QString::fromUtf8(pszCurrent)); (pData->pListItem)->setText(iCol++, QString::fromUtf8(pszDefault));

so it maybe a fluid_settings/windows blunder? does https://github.com/rncbc/qsynth/commit/1ec61bf behave any better?

I now see that, perhaps my change will only work properly if `WideCharToMultiByte` would be called with `CP_UTF8`, instead of CP_ACP (on fluid_wasapi.c) :S at least qsynth is now prepared;...

yeah right, but what if you change it to CP_UTF8 in fluidsynth's fluid_wasapi.c ?

most of those commands are available from the native d-bus interface (cf. Setup > Misc > Other > Enable D-Bus Interface). eg. usage: `dbus-send --system / org.rncbc.qjackctl.`{`start`|`stop`|`reset`|`quit`|...} ps. as matter...

`active-patchbay` and `preset` commands need an argument of type string eg. `dbus-send --system / org.rncbc.qjackctl.active-patchbay string:/path/to/patchbay.xml`