Closed jrigg closed 6 years ago
Think I found the problem. Starting the plugin from an xterm shows this message:
libGL error: failed to open drm device: Permission denied libGL error: failed to load driver: r600
This is probably because I'm not using systemd, so I had to use xserver-xorg-legacy which is a SUID wrapper to allow to start X with root permissions. Obviously some permissions are not being granted. I'll close the issue while I look into it as it appears to be a Debian bug which probably affects anything with an OpenGL GUI.
Problem solved by adding user to video group. Sorry for the noise.
I've just ugraded from Debian 8 to 9 and I've noticed the CPU load of the JACK versions of the plugins has greatly increased. ZaMultiCompX2 was around 32% CPU on Debian 8, but over 120% on Debian 9 on the same hardware with the same signal and settings. This is with latest git code on Debian 9, and I also tried the same git snapshot (May 2017) that I used on Debian 8 on the Debian 9 system. The problem was the same.
The LADSPA version of ZaMultiCompX2 hosted in non-mixer uses about 12% CPU with the same settings. The JACK version takes a few seconds to show the GUI on startup on Deb9 but it starts almost instantaneously on Deb8. The other plugins show similar symptoms.
System is Athlon IIx4 2.5GHz with RS780 onboard graphics (Radeon HD3200).
Other GUI-based plugins like the LSP ones actually have a slightly lower load on Debian 9 than on 8. So far the problem appears to be specific to zam-plugins.