Known Problems

dmxprog: error while loading shared libraries: cannot open shared object file: No such file or directory

1. Ensure libncurses5 to be installed
2. Create sys link to libncurses:

sudo ln -s /lib64/ /lib64/

The DMX4ALL interface takes random values (or full-on) when using a start script

This does not seem to be a problem of the lindmxd. The same problem occurs if the computer is returning from standby, so I guess the Interface gets some data it should not get by the driver. The server is not aimed to zero the memory on start-up, because the Interface has it’s own memory and is able to hold the values – even if the client application crashes. Restarting lindmxd in this case should allow to continue work as if nothing happened.
Since version 0.1.2 there is a start-up option ‚-z‘ or ‚–zero‘ to set all channels to zero while initializing.

Zuletzt aktualisiert: 11. März 2015