If you feed tc2 with the number 1 the result will be formatted as timecode. Value for tc2 is ignored and is best left blank. * '2tc' : will convert tc1, here given as frames, to timecode. tc2 in this case should be target framerate as an integer. * 'conv' : will convert tc1 to the framerate given as tc2. tc2 in this case should be an int or float, NOT HH:MM:SS:FF.

tc2 in this case is the multiplier as an integer or float, NOT HH:MM:SS:FF. tc2 in this case is the divisor as an integer or float, NOT HH:MM:SS:FF. You must type '' around the dropframe framerates. * supported framerates: Any integer frame rate such as 24, 25, 30, 60. When converting between framerates with 'conv' this is the new target framerate, e.g. For all other operations integer or float, e.g. String or cell/range reference for addition and subtraction, e.g. * tc1 = The first timecode, always a string or cell/range reference. * Takes two timecodes, framerate and an operation as input. * Works with both manually entered data and cell references. David based his work on Andrew Duncan's math. * Drop frame support with the help of David Heidelberger's blog. * User have to have some sense since with the input we're not throwing errors for all odd cases possible. No support for obscure non even frame rates (yet). Heavily inspired by Nuke/Hiero Timecode Calculator Panel v1 by Matt Brealey. * Simple timecode calculator for gDocs spreadshet. Turned out it's not that easily achieved though and might require It's next on the list and it'll be part of a major rewrite where you should also be able to do calculations on spread out cells. Sadly, with my lack of skills and experience it probably means that I have to re-do alot of the script. With inter-column I mean that it should be possible to add tc's from one single column, A1:A5, in one operation. I still haven't gotten inter-column math to work. In the 'validate_frame_ranges' sheet you can see that it drop frames when it should for 29.97df and 59.94df. Works as a good validation for you as well, so that you can see that it works and what it does. I've added some sheets at the bottom with auto validation's so that I more ealisy can test the script. Use the drop frame framerates in calculations with '29.97df' and '59.94df' or with cell reference.

=) There is support for 23.976 calculations though. During this process i've learnt that there is no such thing as 23.976 drop frame so that has ben dropped, no pun intented. Sometimes a script can error out for no apparent reason, reloading normally helps.Ģ9.97 and 59.94 drop frame support implemented. If it's related to this limitation try to work with ranges instead, examples below. This is important to have in mind and if you see a lot of '#ERROR!' cells, hover over them to see what the issue is. There's a built-in limitation in gDocs for how many times a script can be called per second. If that doesn't work, write something in the comments. Make a copy of this document to your own gDocs/gDrive, once there you can edit it and access the script in the script editor. If there's a bug and it needs update, all these instances would have to be manually updated. You will have to manually copy and paste this script into all documents you want to use it in. You will find the script in 'Apps Script' under the 'Extenions'-menu. I encourage you to come with feedback such as feature requests, bugs or other stuffs. Disclaimer: Im no expert in this and I created it since I needed it myself.

Timecode calculator excel scott taylor