Speaking personally, I've been using 0.6
since at least late-2018; and started doing so because I wanted to create a plugin to provide functionality I desired and - considering that the internals are substantially different between the two versions - didn't want to end up having to vastly rewrite it when 0.6
was eventually promoted to master
.
I transitioned to using 0.6
fairly quickly, so don't have much experience with 0.5
to compare with; however I do sometimes "revert" briefly so as to aid the debugging of issues raised by other users, and find that of the two the UI of 0.6
is better. Certainly less monochromatic! I also don't think 0.6
(in its current state, anyway) is any more prone to crashing than 0.5
is; and 0.6
is certainly better featured.
It is worth noting that quite a few of the issues raised and feature requests made against 0.5
over the past couple of years can be resolved by using 0.6
instead (which is where the lack of cross-compatibility with regards to show-files is unfortunate).
That said: 0.6
is the current edge of development of the software; so there is some level of inherent instability in the fact that the code changes every so often - sometimes causing config files to be reset to defaults, and sometimes breakage in functionality. (Though this can be mitigated by only updating to the latest 0.6
state when safe: e.g. at the start of rehearsals, and not right before a performance...)
linux-show-player --log debug
and post the output?