Recently updated to the latest software version on my Orb, have noticed that occassionally when editing fade times (including beamshape, intensity and position fades) that the edit doesn't save and when I come back to the cue a few minutes later it has reverted to the old fade time.
My process would go something like this:
Running the cue stack in a dress rehearsal say, and decide to change the timing of the position fade between LX 29 and 30 after seeing it 'live'.
Click on the position fade box, change the time from 3 seconds to 6.
Click away from the box to highlight next cue (LX 31)
At this stage position fade reads as it should at 6 seconds on LX30
20 minutes later when we go back and run that scene again I notice that LX 30 position fade reads 3 seconds. Annoying.
This has happened about a dozen times in the last couple of weeks.
Also tied in with that is a similar thing where I may update the position fade again, re-run the cue and despite position fade being 6 seconds the fixtures quite visibly are still taking only 3 seconds and it's not until I save the show by entering and exiting set-up that the cue runs as it should.
These are annoying little bugs which I'm fairly sure aren't due to something I'm doing differently to how I did it before the software update, I appreciate it's hard to replicate the situation as well as it seems to be fairly randomly occurring with the desk behaving itself the bulk of the time.
Is it worth me reinstalling the OS?