Hello,
The bug I've encountered is one of unexplained behavior that can cause timing inaccuracies. I was attempting to set cue to have a follow time of 81.5 seconds for a dance piece. You get a syntax error attempting to type a decimal after typing `cue 100 follow 1:21`. If you instead type `cue 100 follow 81.5 [ENTER]`, it displays that cue 100 has a follow time of 1:22, and it appeared to in fact be half a second longer than what I desired. I was able to fix this by having a buffer cue so that I had one with a 40 second follow and the one after a 41.5 second follow.
I understand it is a minor bug with a workaround, but since it was semi-silent I figured it might come up for others and mess up their workflow. I imagine it might also happen for other places you enter a time but I haven't checked that.
Thanks,
Tom