Timing Suggestion

Interesting idea but scenes aren't objects, they're parameters of a cue which is used for labelling and navigation purposes. It would require quite a change to allow something like this.

I suppose you could note the clock time of the [Go] of every cue, disregard the ones that aren't marked as scene-beginners, and then do a bit of maths on the remaining cues?

This was posted yesterday on fb.  Could this be your workaround for now?
 
Just wanted to pass on a trick I found very useful on the show I just programmed. It was a quiet and atmospheric piece primarily lit with a small number of very noisy ETC Revolutions, which were always either in use of marking for an imminent cue. Obviously, we wanted to make most of the marks as long as possible to minimize noise. So during our first preview, I created a macro to enable internal timecode and put the desk into learn events on the first called cue, and another macro to disable it on the last called cue. This gave us a list of when each cue was run as called by the DSM. From this list of timecodes, we could derive the time between each cue, and thereby choose the longest possible mark time for our noisy movers. Will definitely use again in the future!