Closed moonshaadow closed 2 years ago
It's due to two things: 1) How the backend is built, where every cue it's an independent GStreamer pipeline, with its own output 2) GStreamer doing what you described every time a pipeline is stopped/started
It does behave in the same way with other outputs (e.g. PulseAudio)
Describe the bug [Jack] Not really a bug, but I noticed a change in the client behavior. Former versions of LiSP were creating a client each time a cue was played, and the client was removed each time the cue was stopped. Now the client is not removed when cue is stopped, but when cue is played again, just before creating the client again. My question is : why to disconnect and reconnect (or remove and re-create, I don't really know) the client each time the play is triggered ? Can't we keep the client opened ?
To Reproduce
Linux Show Player version:
OS Version