This is a JavaScript module that provides a Timecode class with properties and methods to work with SMPTE timecode.
npm install --save timecode-bossconst Timecode = require('timecode-boss');
let tc = new Timecode('01:10:25:13', 29.97);
tc.toString(); // '01:10:25;13'
tc.hours; // 1
tc.minutes; // 10
tc.seconds; // 25
tc.frames ; // 13
let laterTc = tc.add('00:04:59:28');
laterTc.toString(); // '01:15:25;13'This constructs a Timecode instance named tc from a string representation ('01:10:25:13'), with a framerate of 29.97. On creation, each field of the timecode string is stored in the properties hours, minutes, seconds, and frames. Calling toString() joins those fields with a separator.
tc.add() returns a new timecode, starting from the original tc instance and adding a timecode of '00:04:59:28'. The result is assigned to laterTC and the original tc object is not mutated.
Tests are run using Mocha, and code coverage is tested with Istanbul's command-line interface, nyc.
Babel is used to transpile to ES5 and uglify-js is used to minify the source for use in the browser.
git clone https://github.com/bradcordeiro/timecode-boss
cd timecode-bossThis package uses SemVer for versioning. Version 1.0.0 was kind of written in a vacuum, once I started using it to build an actual web application, I realized how many useless or poorly-thought out methods it had, and renamed, added, and deleted many from the public interface, leading to a rapid increase to versions 2, 3, and 4.
Test files live alongside implementation files.
Tests are mostly written to ensure accurate arithmetic given different framerates. Expected values were written using Avid Media Composer's built-in timecode calculator to verify correct values.
Tests are run with Mocha:
npm install -g mocha
npm testTo check test coverage:
npm install -g nyc
npm run test-coverageIf you encounter incorrect math being performed and would like to submit a pull request to add a test for it without including a patch to fix the problem, that would be very welcome and I'll do my best to work out the bug. Or just a bug report is great.
I try to maintain 100% test coverage, but don't require all pull requests to maintain that number. I'm happy to write some tests, but please try to include tests for major funcionality you change or add.
This module was written according to the Airbnb Javascript Style Guide . eslint was used to stay consistent. An .eslintrc.json file is included in source control. The Airbnb guide wasn't chosen for any grand reason, I just like it.
| Property | Type | Description |
|---|---|---|
| hours | Number | A number representing the hours field |
| minutes | Number | A number representing the minutes field |
| seconds | Number | A number representing the seconds field |
| frames | Number | A number representing the frames field |
| frameRate | Number | A Number representing the playback speed of the Timecode. Though any frame rate should work here, only common broadcast frame rates are tested (23.98, 24, 25, 29.97, 30, 50, 59.94, and 60). |
| Method | Argument Type | Return Type | Description |
|---|---|---|---|
| isValidTimecodeString(str) | String | Boolean | Returns true if the string can be parsed into a Timecode |
| compare(a, b) | Timecode, Timecode | Number | Compare function matching the signature of compareFn of Array.sort(compareFn). Returns -1 if a is before b, 1 if a is after b, or 0 if they are equal |
| exactFrameRate(frameRate) | Number | Number | Floating-point framerates are determined by a fraction (e.g. 29.97 is 30000/1001). Passing a floating-point framerate argument near a supported framerate here returns the exact calculation of that fraction. |
| Method | Arguments |
|---|---|
| new Timecode() | (timecode, frameRate) |
Constructs a Timecode object. All fields default to 0 if the constructor is called with no arguments, and frameRate defaults to 29.97 if that argument is not passed.
The first parameter of the Constructor accepts:
- Another Timecode instance
- A string in the format "00:00:00:00"
- A JavaScript Object with one or more of the properties hours, minutes, seconds, or frames. Any missing properties will be set to 0.
- A Number representing the frame count
- A Date instance
The second parameter is a frame rate.
| Method | Argument Type | Return Type |
|---|---|---|
| setHours(hours) | Number | Timecode (this) |
| setMinutes(minutes) | Number | Timecode (this) |
| setSeconds(seconds) | Number | Timecode (this) |
| setFrames(frames) | Number | Timecode (this) |
There are also setters for each individual field. The Timecode object is returned, allowing these methods to be chained. Calling these methods with a type that cannot be coerced to an integer will throw a TypeError, and float types will be truncated to an integer.
If an argument overflows a field, the next larger field will be incremented accordingly. For example, calling setMinutes(72) will set the minutes to 12, and increment the hours field by 1. Setting the hours above 24 will overflow the hours and they will be recalculated starting from 0.
| Method | Argument Type | Return Type |
|---|---|---|
| isBefore(tc) | Timecode | Boolean |
| isAfter(tc) | Timecode | Boolean |
| isSame(tc) | Timecode | Boolean |
| isBetween(tc) | Timecode | Boolean |
Compare this Timecode to another timecode passed as an argument.
| Method | Argument Type | Return Type |
|---|---|---|
| add(addend) | Timecode, String, Number, Object, or Date | Timecode |
| subtract(subtrahend) | Timecode, String, Number, Object, or Date | Timecode |
Adds the addend to or subtracts the subtrahend from the calling Timecode, and returns a new Timecode. Any of the types available to use in the Timecode constructor above are available to use as arguments to these methods. If an addend or subtrahend has a different framerate than the calling object, the addend will be converted to the calling object's frame rate (see Frame Rate Conversion below).
| Method | Argument Type | Return Type |
|---|---|---|
| pulldown(frameRate, [start]) | Number, Any | Timecode |
| pullup(frameRate, [start]) | Number, Any | Timecode |
Return a new Timecode object based on the calling object converted to the frame rate passed as an argument, where the conversion would result in frames being added for the new framerate. This is useful for, for example, a converting a 23.98 timecode to a 29.97 drop-frame timecode using a 3:2 pulldown. The first argument is the framerate to convert to, and the second argument is an optional start time of the sequence being pulled down, which affects the output. The second argument can be any type accepted by the Timecode object constructor.
pullup() is an alias of pulldown().
| Method | Argument Type | Return Type | Description |
|---|---|---|---|
| milliseconds() | Number | Returns floating-point milliseconds representing the frames field only. | |
| fractionalSeconds() | Number | Returns floating-point seconds, with frames converted to milliseconds and added to seconds. Useful for interacting programs that use fractions of a second rather than frames (e.g. ffmpeg). | |
| isDropFrame() | Boolean | Returns true if the Timecode object is being calculated in drop-frame mode (29.97 or 59.94). | |
| toString() | String | Returns a string in the format 'hh:mm:ss:ff'. Colons are used as a field separator, though the final separator will be a semi-colon for drop-frame. | |
| toSRTString(realTime) | Boolean | String | Returns a string in the format 'hh:mm:ss,iii...' where 'iii...' are milliseconds rather than frames, the format used for SRT subtitles. SRT subtitles use real time, not timecode, and timecodes in some framerates do not match real time. If the optional argument is true the result will be in real time. |
| toObject() | Object | Returns an plain JavaScript object with the Timecode's hours, minutes, seconds, frames, and frameRate properties, but no class methods attached. |
Released under the MIT License.