Support

HELP DESK — TIMECODEEDITOR, KEPT RUNNING

SCOPETimeCodeEditor
REPLIESwhen I can
TRACKINGnone
Contact, updates, and answers to the questions that come up most with TimeCodeEditor.

01 Get help

Report a bug or request a feature

The feedback board takes bug reports, feature requests, and questions — post it once and I read every one.

Open the feedback board →

Email me directly

For anything private — or something you'd rather not post publicly — just drop me a line.

contact@lucesumbrarum.com →

Updates

TimeCodeEditor updates itself via Sparkle — it checks the release feed and offers new versions in-app. You can also re-download the latest notarized DMG from the homepage at any time; installing over the old copy keeps your settings.

02 Requirements & installation

What you need

TimeCodeEditor needs macOS 14.0 Sonoma or later and runs natively on Apple Silicon. It is not a Universal binary, so it does not run on Intel Macs. No account, no admin rights.

Installing

Open the DMG and drag TimeCodeEditor into Applications — the app is notarized by Apple, so it launches without warnings.

03 Common questions

Will this change my original footage?

No. Every correction is written as a new file into a folder you choose, using a naming pattern you control. Your source files are read but never written to, moved, or renamed.

Does correcting the timecode hurt quality?

No — nothing is re-encoded. The correction is an ffmpeg stream copy (-c copy), so the video and audio in the new file are bit-for-bit identical to the original. Only the timecode differs, and it finishes at copy speed rather than render speed.

A file shows no timecode at all.

Then the camera never wrote one — TimeCodeEditor reads the embedded tmcd track, and not every camera or format records one. You can still stamp a timecode onto the file yourself: set a manual value, or use the file's creation time.

Is 29.97 drop-frame handled properly?

Yes. The SMPTE math covers 23.98, 24, 25, 29.97, 30 and 60 fps in both drop-frame and non-drop, so NTSC rates land on the correct frame instead of drifting. Drop-frame display can be overridden per file if a clip is flagged wrongly.

How do I know the new timecode actually stuck?

Each job is re-read after it's written and sealed ✓ / ⚠ / ✗. Pick how hard it checks with the verify level — off, quick, stream-integrity, or deep.

Something else is wrong.

Write to contact@lucesumbrarum.com with the app version (TimeCodeEditor → About), the camera or format the file came from, and its frame rate — that's usually enough to reproduce it.

Manufacturer. Luces Umbrarum — a one-person studio building small native Mac apps. Back to TimeCodeEditor.