Not sure, if it is only a GUI issue, or if it is actually not outputting a clock, but a set receiving clock from another set does not show any cursor running after metaseq received state from peer.
Problem is that metaseq-segmenter doesn't update the range_length for sets that are not selected, thus the cursor is only shown when the set is selected.
Not sure, if it is only a GUI issue, or if it is actually not outputting a clock, but a set receiving clock from another set does not show any cursor running after metaseq received state from peer.