TimeCode Generator app icon
U.S. App Store

TimeCode Generator App Reviews

The TimeCode Generator app recently received 5 positive reviews on iPhone, iPad, and Android devices, and 1 negative reviews. Users in the United States have given TimeCode Generator app an average rating of 3.62 out of 5 stars, based on a total of 13 ratings since its release on Jan 23 by Haute Technique BV. Can you share your positive or negative thoughts about TimeCode Generator?

Ratings and Reviews
Rated 3.60 out of 5

13 global ratings

5 Star
20%
4 Star
20%
3 Star
40%
2 Star
20%

Explore global reviews of the TimeCode Generator app: Spain, France.

5 Positive User Reviews for TimeCode Generator

MIDI timecode is only Full Frame

For whatever reason, they chose to implement only the Full Frame MTC messages, rather than sending Quarter Frame messages. This might explain why some hardware doesn’t work with it — if that hardware is expecting Quarter Frame messages it won’t work.

Works for generating timecode

But I really wish you could have it use the Mac's clock instead of all zeros or hand setting the time.

Missing Crucial Feature For Me

This would be 100% what I'm looking for if it could capture the timecode at the press of a button so i can copy/paste it into another app. Another bonus would be the ability to take an input source. Otherwise, would be perfect for my needs.

Portrait orientation. Funny noise?

Happy to find one that works in a portrait orientation. I am looking for that. Disappointed at the loud shutter / film gate noise? Can I turn that off? Also has an annoying feature. Beware the stop button, you will lose the sync with your camera’s TC.

1 Negative User Reviews for TimeCode Generator

No backgrounding, low signal level

The signal level is too low, even with maxed out volume and no negative gain in the settings. BMPCC4k refuses to lock on. Also will not run in the background. My use cases for this included having the phone mounted on camera as a teleprompter with time code generated on the same phone. I’d have to run this separately on a second iOS device to do what I need here.