If at any stage I want to check anything against the official PT GUI I just switch the Pi to boot into its GUI version, VNC onto it from my workstation and fire up PT this time without the 'headless' argument. Once checks done I revert to the CLI boot. This seems to cover all bases for me. I.

So if you stay CLI and try to open Pianoteq you reproduce the same problem? If so, then it's not as I speculated a missing library, but a runtime configuration instead. It would be very good to know which one is the case.

Thanks

Many thanks for getting back. I checked those three packages and they are already installed (latest version) on the RP OS lite build (basically Debian 12).

I'm not a fan of the PT GUI, for various reasons, but when I've tried to suggest there are problems with it before (in this forum) I've been shot down by the faithful. Dissent not welcome then. Oh well.

My approach is to use a GUI of my own design, fire up a PT instance and communicate with it using its JSON RPC server facility (as the webapp you link to does). But I run my GUI locally on the RP using DRI and a touchscreen. This works fine but it's nice to be able to fire up the 'official' GUI from time to time (during development) to check on various parameters, rather than just trying to tweak the config file manually, not least because I can't find any documentation on this file. As I say, this used to work fine, but doesn't any more. It's a shame that a standard Linux facility seems to be broken with this particular binary.

Best, Ian.

Last year I installed Pianoteq on a Raspberry Pi 4 running the 64-bit Raspberry Pi OS 'lite' (just CLI, no GUI). I was able to start it by connecting to the Pi from an Ubuntu workstation over ssh with X11 forwarding.

I've just tried again on a new installation - latest version of the RP OS and Pianoteq - but this time I got this: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory. I managed to fix this by installing the libgl1 package and now I get a Pianoteq window on my workstation but I can't interact with it - mouse and keyboard have no effect.

X11 forwarding is working in general - I can run other GUI programs on the Pi and interact with them on my workstation, but not Pianoteq.

Anyone got any ideas?

Thanks, Ian.

For Pianoteq to work correctly, you need X11 to be correctly installed. In particular, Pianoteq needs

* libX11
* libXau
* libXdmcp

Also, very sadly, all music related programs follow the very unfortunate idea started by that pile of <censored> that is called kontakt of not using standard GUI but custom images and custom interations. As such, a test with other X11 programs is only going to help debugging your setup marginally, but I digress...

Given the minimal install without X11, I am sure your OS install is missing some obscure X11 parts to save space and hence Pianoteq malfunctions. I suggest that you start making sure the above three packages are included in your install. Note that in most Debian/Ubuntu distros you will be encounter this problem complicating your sleuthing: https://askubuntu.com/questions/481/how...des-a-file

Alternatively you can control it via a webapp such as https://github.com/robert-rc2i/ptq-client-webapp

Hope this helps

I've just tried again on a new installation - latest version of the RP OS and Pianoteq - but this time I got this: error while loading shared libraries: libGL.so.1: cannot open shared object file: No such file or directory. I managed to fix this by installing the libgl1 package and now I get a Pianoteq window on my workstation but I can't interact with it - mouse and keyboard have no effect.

X11 forwarding is working in general - I can run other GUI programs on the Pi and interact with them on my workstation, but not Pianoteq.

Anyone got any ideas?

Thanks, Ian.