Timecode Calculator / Comparator

fifou

Thanks a lot Mark for your work and explanations.
Everything works fine...

mark

So it's all good then???? If so then maybe just edit your post to remove the mention of the problem so that other readers aren't confused.

Best Wishes,

Mark

fifou

Mark,
I've made two user actors based on yours.

TimeCode Trigger : All-in-one actor to simply send trigger at specific TimeCode.
But I have a strange behaviour with Timecode Comparator : when my TimeCode to trigger is set to 00:00:00:00 and the movie's running, it sends randoms triggers !? It doesn't happens with every movie but you can try by sliding the position of the movieplayer while playing too..
TimeCode Jump : All-in-one actor to jump to a specific TimeCode.

Note that these actors need your update of the logical calculator.
Do I have to send a bug report about this logical calc or is it already corrected for the future f26 release ?

Nevertheless, I'm afraid of a community's confusion about names between Timecode comparator / calculator
and TimeCode Trigger / Jump, because they aren't "speaking" the same timecode.
Maybe should I call them TC Trigger & TC Jump ?

Advice anyone ?

Thank you Mark for your devotion and sorry for my English (I'm not sure to be precise or clear enough everytime)
Cheers
Philippe
0c040d-timecode-trigger-1.0.iua 611bb7-timecode-jump-1.0.iua

magicdominik

This is exactly what I was looking for! Thank you for posting!

mark

Dear Fifou,

Regarding this question: "But I have a strange behaviour with Timecode Comparator : when my TimeCode to trigger is set to 00:00:00:00 and the movie's running, it sends randoms triggers !? It doesn't happens with every movie but you can try by sliding the position of the movieplayer while playing too."

There is a situation when the output of the Calculator called "Remaining Frames" can briefly be a negative value -- this leads to all kinds of confusion for the Logical Calculators, and this is what is causing the multiple triggers. To fix this, you need to insert a Pass Value actor and, to be safe, a Float to Int actor too. See the picture so to understand what I mean.

I have updated my original Timecode User Actors to include this fix. I'll leave it to you to do the same with your User Actors.

Best Wishes,

Mark

primaldivine

@Mark @Michel @Fifou
I am tracking down the latest versions of all these various timecode based Timer Tools and Timer Trigger User actors etc, since some users have been finding old threads and trying to work with buggy versions.
When you have time is it possible to upload your latest versions of these? Then I'll start a new thread that will be easier to direct people to look in one place for them and put your names so folks know the authors of these fabulous user actors.
thanks
pd

Michel

@primaldevine Mine should be up to date. I only leave one version online, delete the old one and replace it with the new one with the date I updated it. So as soon as I hear that someone has a problem I will check and fix if necessary. Best Michel

primaldivine

ok, great, thanks Michel.

fifou

I'll try to do this next week..

Best
Philippe

Woland

@mark

I apologize for the thread necromancy, but I have a question for you.

I downloaded your user actors and @fifou 's user actors as well.

Just to clarify, am I putting a Pass Value actor and a Float to Integer actor after _each_ Calculator actor named "Remaining Frames", or just after the final one in the series that is connected to the "frames" User Output?

Thanks very much to both of you,

Woland

Woland

[Edit] I was looking at @fifou 's User Actors first, I see @mark 's already have the Pass Value and Float to Integer actors added on the last "Remaining Frames" Calculator actor.

Attached is the edited version of @fifou 's TimeCode Trigger 1.0 User Actor.

Best,

Woland

19b743-timecode-trigger-1.1.iua