Isolating CAVA instances about cavalcade HOT 4 OPEN

be multi-user friendly (using a common FIFO under /tmp isn't really

Why it isn't? You can manually edit ~/.config/cavalcade/cava.ini and set individual file for every user. I can add unique file name auto generation per user on first launch if manual editing is really problem.

or ideally multi-process friendly, like the FIFO being placed under /run/cavalcade/$PID for example.

Not sure it's that easy, current GUI part was not designed for multi-process.

Also, two cava instances after manually killing can be really problem, I should rethink about it. But it doesn't seems like multi-user matter.

from cavalcade.

Also, two cava instances after manually killing can be really problem,

At least trapping SIGTERM to kill cava with cavalcade should partly solve the problem.

from cavalcade.

Also, concerning the FIFO, can't you open a FD pipe so that cava communicates with cavalcade entirely internally? (os.pipe(), os.fork(), os.execve() basically forking to call cava with the pipe pre-made, a la C language). It would solve the instance problem since cava would be killed by a broken pipe when cavalcade stops.

from cavalcade.

I'll take a look what can be done.

from cavalcade.