Times Oddity

Hi Richard -

This is by design and it's been this way since the beginning. Sorry for the confusion.

Thanks much -

Sarah

Follow up question then: Why is it designed this way? I could see myself needing a higher resolution than seconds when syncing fades and waits to music for instance.

Follow up question then: Why is it designed this way? I could see myself needing a higher resolution than seconds when syncing fades and waits to music for instance.

Basically because if you want higher time resolution for long times, you're almost certainly trying to do something in a difficult way that's going to bite you later.

For example, to sync a cuelist to music:

If you use Waits, the moment you change any of them, you also need to update the timing of all of the following cues/steps or they go out of sync.

If you use Timecode instead, this gives every step an 'absolute' time and so altering the timing of any individual step has no effect on any of the other steps.

- If your music player doesn't provide an actual timecode source, then you can use the internal timecode clock and manually start/stop it as required
(Onscreen via the Timecode Dock, by Macro or assigned to a Master Key.)

Timecode can also be programmed by starting the clock and "learning" the values:

1. Turn on {Learn}
2. Start the track and the clock
3. Hit [Go] as and when required
4. Turn off {Learn} - done!