What are you trying to calculate? There may be more elegant approaches, but I use text functions to identify numbers such as "hours" and multiply that number by the number of frames in an hour, followed by calculations for minutes, seconds and frames. This provides a total frame count and you can go from there.
(Left ( Start ; 2 )*86400)+(Middle ( Start ; 4 ; 2 )*1440)+(Middle ( Start ; 7 ; 2 )*24)+Middle ( Start ; 10 ; 2 )
I'm trying to calculate duration of a clip with a start time and and end time. (sorry I wasn't clear)
You might want to store start and stop times in time fields and store the frame counts separately in number fields.
Then the calculation StopTimeField - StartTimeField will give you the duration in seconds.
You can then define a calculation field to concatentate (glue together) your time and frame data into the format you show for reporting purposes.
If you're only going to be calculating for film (and in North America) 24 frames will do. I would advise, since you're building this anyway, to allow for the possibility of calculating video formats as well: 30fps, 29.97 fps etc. with and without pull-down, drop and non-drop. It sounds complicated but if you can do it for 24fps you can create the other schemes as well. Also do a search on the web for "tcfilemaker" and you'll find a timecode oriented solution that may give you some ideas.
If the time amount represented by FF is milliseconds (thousands of a second), then you could input the frames per second in a separate field, according to the applicable film speed, and multiple that field by the FF number. If FF = 75, then ClipPerSecond x FF/100 (24x75/100 = 18 frames).
could I suggest that the next version of filemaker to read the universal character to indicate frames per second -> ;##
(after the seconds characters)
1. Filemaker is a general development environment - not an industry-specific application.
2. Timecode is not time, and has no place in a time field.
3. Converting timecode to frames and back is merely a matter of calculation; for all frame rates except 29.97df the calculation is rather trivial - see: