D2
Keith
Dear Keith, Something old and something new:
#1 On the subject of timecode, my needs for auto-entry timecode is not that
urgent. But what would be handy and seems not as complicated is to have
event triggering to happen based on a list of time code numbers manually
entered. A line from this list could look like this "TC057A=01:55:13:29".
This means that event #57 will trigger at SMPTE time code 01:55:13:29 (the
"A" represents the first trigger of an event, other letters could be for
other triggers within one event as in stop/starting an anim). When script
is running you could manually advance to event #57 and wait for the
trigger. I don't know midi very well so I don't know how SMPTE #'s match
but I guess a conversion formula could be written. It is very important
though that SMPTE #'s are written as they are read from the time code
reader for easy and accurate typing (using a colon between
"hours:minutes:seconds:frames" is not necessary though). If more advanced
entry and triggering of time code would be possible then that would be
great. I'll gladly suggest a direction if we reach that stage.
#2 I have the ability in my script to go to any other event by hitting 3
numbers (ex: 0,5,7 means go to event #57) before hitting the trigger key.
Hitting letters or just two numbers will be ignored and the trigger key
will activate the event that is next in line. If I hit 3 keys that give me
a number that is higher than my last event, the program will abort because
the event label doesn't exist. I have a way of checking for this, but I
want to have the ability to type in other choices (ex: different
transitions) and it is hard to write script each time to protect from
illegal goto's. Is there any way a goto command that leads to a nonexistent
label could just be ignored until a legal label is typed in?
Thanks again for your clear responses, regards Richard