Support

CutNotes 0.12.1 · iPhone · iOS 17 or later

Something not working, or not behaving as you expected? Mail support@cutnotes.co.uk — or use Send feedback in the app's About screen, which fills in the version and device for you.

The quickest possible start

• New session. Set the frame rate to match the edit.
• Press play as the cut starts rolling — or skip that and long-press play to read the timecode with the camera instead.
• Tap when you spot something. Hold for a range. Hold the mic to speak it.
• Share these notes… when you are done. Send the CutNotes log to the editor; export Subtitles (.srt) if the cut is yours.

The camera won't lock onto my timecode

The message under the box tells you which problem it is, and they have different fixes:

Dashes, and no message

It cannot read any text at all. Move closer, steady the phone, and check the timecode is not too small in the frame or washed out by a bright monitor.

"Reading … — not a timecode"

It can read your screen but the box is over the wrong thing. Most editors show several timecode-shaped numbers at once — position, duration, in/out. Put the box over the one that counts up.

"Frames up to 40 — that timeline is not 25 fps"

The session's frame rate and the timeline's disagree — a 50 fps timeline counts frames to 49, which a 25 fps session cannot produce. Turn on Ignore frames at the bottom of the scanner. It reads the seconds instead, accurate to about a second.

"That looks like drop-frame timecode"

CutNotes does not use drop-frame. Switch the edit's display to non-drop.

A timecode shows but it never commits

It is reading fine but refusing to trust it. It needs the number to advance steadily for a second and a half, so make sure the picture is actually playing at normal speed — a scrub or a jog will never lock, deliberately.

My notes are in the wrong place

Nothing is lost, and nothing needs re-logging. Every note is stored as a moment, not as a timecode, so moving the clock re-times the whole list.

• Adjust start timecode if you started late or typed the wrong start — it moves every note.
• Resync to timecode if you have drifted part-way through — it leaves earlier notes alone.
• Read timecode with camera does either for you.

Everyone's notes are slightly out of step

Expected, and fixable. Each viewer starts their own clock by hand, so someone who pressed play ten seconds late has every note ten seconds out.

Long-press their session and choose Conform to another session…, then pick yours as the reference. Their notes are re-timed onto your clock using the moment each was actually tapped. No network is involved, and it works just as well for someone who watched remotely and emailed the file days later.

If you know in advance that somebody else is holding the sync, have them use the With editor clock — no clock to start, and nothing to get wrong.

Things it deliberately does not do

• Drop-frame timecode. Notes need to be right to the second, not to the frame. Frames are shown for a familiar format, not for frame accuracy.
• Mac. CutNotes is an iPhone app. It is not supported on macOS and should not be installed there.
• Sync your notes anywhere. There is no cloud and no account — see Privacy. Sessions are plain files in the Files app, so they can always be recovered by hand.

Beta builds expire

A TestFlight build stops working 90 days after it is uploaded. If the app refuses to open, open TestFlight and update it.

Get in touch

Bugs, requests, or a board you have built that others should have: support@cutnotes.co.uk. Beta feedback is read and acted on — most of what is in the app came from people saying what was missing.