[ANSWERED] Timecode Comparator

[thorsj]

I'm trying to get cues to trigger from timecode (to match edits) but I can't get the timecode comparator to trigger. I have no problem using float to integer from timecode on a regular comparator. Is there a trick to getting the timecode comparator to work without rounding to integer?

Thank you!

J

[thorsj]

I think the real question is: is there a way to trigger a value from non-integer timecode (so you can cue by frames and not just even seconds)... the value trigger only seems willing to accept integers.

[thorsj]

maybe i'm answering my own questions: timecode comparator doesn't output trigger with EQ value but seems to work with GE... interesting.

[mark_m]

@thorsj

I have found that EQ in the comparator actor can be erratic in its behavious: the exact equal value moment is fleeting. I always use GE now.

[Kathmandale]

@thorsj as @mark_m say's this is definitely the case. To be honest, even with the standard 'non-timecode' comparators I think in nearly every scenario with a quickly changing value, GE (or LE) is more reliable. With = you only get a fraction of a second for the stars to align, GE gives you a big safety net.

[Aidan]

@mark_m I noted the same and also use GE.