{"id":4443,"date":"2026-04-18T12:56:01","date_gmt":"2026-04-18T12:56:01","guid":{"rendered":"https:\/\/mostlyawesome.de\/cms\/?p=4443"},"modified":"2026-04-27T13:57:46","modified_gmt":"2026-04-27T13:57:46","slug":"ltc-timecode-on-no-budget-no-problem","status":"publish","type":"post","link":"https:\/\/mostlyawesome.de\/cms\/ltc-timecode-on-no-budget-no-problem\/","title":{"rendered":"LTC Timecode on no budget? No problem…"},"content":{"rendered":"\n
\"\"<\/figure>\n\n\n\n

<\/p>\n\n\n\n

Anyone who’s worked a real production set knows the feeling. You’ve got a camera rolling, a boom op sweating, a director losing their mind, and somewhere in the chaos, audio and picture are slowly drifting apart. <\/p>\n\n\n\n

The fix? Timecode.<\/strong> The problem? A decent LTC generator will cost you more than your entire craft services budget.<\/p>\n\n\n\n

Traditional timecode hardware is priced like it’s 1987 and the only people buying it are broadcast networks with bottomless expense accounts. For indie filmmakers, doc crews, guerrilla productions, or anyone working under an executive producer with a particular talent for slashing budgets \u2014 that gear might as well live on the moon.<\/p>\n\n\n\n

“What if the timecode generator was already in your pocket?”<\/strong><\/p>\n\n\n\n

That’s the question we kept asking ourselves. And after a lot of late nights and probably too much coffee, we have an answer: it is.<\/strong> <\/p>\n\n\n\n

We built an Android app that turns two smartphones and a 5GHz Wi-Fi connection into a fully functional timecode sync system; one device generates, one device receives, and LTC gets jammed to your audio line. <\/p>\n\n\n\n

That’s it. That’s the whole rig.<\/p>\n\n\n\n

The app is a single install that can act as either the master generator<\/strong> or the slave receiver<\/strong>, no second separate app to manage, no complicated pairing rituals, no subscriptions. <\/p>\n\n\n\n

Both devices share a common 5GHz network, sync up, and timecode starts flowing. From there you can feed LTC directly into your audio recorder or mixer’s line input and treat it exactly like any hardware generator you’d have rented for three times your day rate.<\/p>\n\n\n\n

Right now the app supports 24fps, 25fps, and 29.97\/30fps<\/strong> \u2014 covering the most common frame rates you’ll run into on film, narrative, and broadcast work. It’s a working prototype, which means it does the job and does it reliably, and it also means we’re actively building on top of it. More frame rates, better UI, tighter sync tolerance \u2014 it’s all on the roadmap.<\/p>\n\n\n\n

We’re not trying to replace a high-end sync box for a Netflix production. We’re trying to make sure the crew shooting their feature on weekends, the doc team chasing a story with whatever’s in the van, or the commercial unit that just had half their gear budget pulled \u2014 all of them can still roll with proper timecode.<\/strong> Because good sync shouldn’t be a privilege reserved for people with deep pockets.<\/p>\n\n\n\n

Patience is one way to deal with drift in post. A timecode generator is another. Now you’ve got no excuse.<\/p>\n\n\n\n

Want to try it?<\/strong> -> Click here<\/a><\/p>\n\n\n\n

<\/div>\n\n\n\n

Edit: We’re about to shoot a little demo on how it works. Please be patient for maybe a couple of days<\/strong><\/p>\n\n\n\n

<\/p>\n","protected":false},"excerpt":{"rendered":"

Anyone who’s worked a real production set knows the feeling. You’ve got a camera rolling, a boom op sweating, a director losing their mind, and somewhere in the chaos, audio and picture are slowly drifting apart. The fix? Timecode. The problem? A decent LTC generator will cost you more than your entire craft services budget. Traditional timecode […]<\/p>\n","protected":false},"author":10,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"pgc_sgb_lightbox_settings":"","_jetpack_memberships_contains_paid_content":false,"footnotes":""},"categories":[13,32],"tags":[],"class_list":["post-4443","post","type-post","status-publish","format-standard","hentry","category-blog","category-news"],"aioseo_notices":[],"jetpack_featured_media_url":"","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/mostlyawesome.de\/cms\/wp-json\/wp\/v2\/posts\/4443","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mostlyawesome.de\/cms\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mostlyawesome.de\/cms\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mostlyawesome.de\/cms\/wp-json\/wp\/v2\/users\/10"}],"replies":[{"embeddable":true,"href":"https:\/\/mostlyawesome.de\/cms\/wp-json\/wp\/v2\/comments?post=4443"}],"version-history":[{"count":6,"href":"https:\/\/mostlyawesome.de\/cms\/wp-json\/wp\/v2\/posts\/4443\/revisions"}],"predecessor-version":[{"id":4467,"href":"https:\/\/mostlyawesome.de\/cms\/wp-json\/wp\/v2\/posts\/4443\/revisions\/4467"}],"wp:attachment":[{"href":"https:\/\/mostlyawesome.de\/cms\/wp-json\/wp\/v2\/media?parent=4443"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mostlyawesome.de\/cms\/wp-json\/wp\/v2\/categories?post=4443"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mostlyawesome.de\/cms\/wp-json\/wp\/v2\/tags?post=4443"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}