Identify repeated shots in iCouldPlay: separate presentations from original events

An action appearing twice may replay one shot or show two performances; counting visible actions alone cannot decide. Watch a permitted original example in iCouldPlay and separate within-file presentations, your review passes and original occurrences. The exercise uses source records and visible clues, not automatic deduplication, person recognition or proof of an unedited film. Original event count in unknown footage may remain unknown.

Plan one-source and two-source comparisons

Plan one roughly2s paper-flip recording A1 and an independently recorded B1, keeping originals separately. Labels are production records and visible cards, not private identities. Version A repeats A1 twice for roughly4s; version B joins A1 then B1, also roughly4s. Optional external editing is not an iCouldPlay feature. Without production, retain paper sequences as untested. Similar actions and duration do not make the versions one file. Planned filming must not be reported as two completed recordings.

Use separate fields for three kinds of count

Version A presents the action twice in-file from the one known A1 recording event; version B presents twice from separate A1/B1 events. Watching A three times yields six observed presentations, while its structure remains two segments and source event one. Record within-file count, review-pass count and source-event count separately:2×3=6 is not six real occurrences. These counts apply to produced, documented paper samples. Without a source ledger for unknown footage, leave original events unresolved, neither equating two presentations with two events nor resemblance with one.

Log both presentation anchors during normal play

Open the identified version and play beginning to end, logging cards, initial paper state and background at first start, join and second start. Find segments by content, not caption or player-item numbers treated as event IDs. With whole-second time, use around2s plus pre/post-flip states rather than an exact cut frame. Separate another automatically continued file before counting; a queue is not an internal edit. Use manual notes without hidden shot-splitting or frame-step controls, and do not infer replay from one pause.

Check bundles of replay clues, not one feature

Compare card, small corner mark, hand-entry direction and changing background shadows across A1 presentations. Several matches support a repeated-source candidate, but unfamiliar footage may use similar retakes or processing. Certainty for your version A comes from retained A1 and edit-order records, not absolute visual authentication. A replay caption is creator annotation, not verified provenance. Cropping, colour changes or slow motion can alter the same source, so difference does not necessarily mean a new event. Log matches, differences and invisible features, not one pixel or line as final proof.

Require provenance for two independent recordings

For version B, match A1/B1 with originals, production records and independent labels, each with its own clear pre-flip state. Slightly repositioning B1’s card aids recognition but alone proves neither discontinuity nor absence of processing. Relabelling A1 does not create a recorded B1. Two camera views of one performance are not automatically two events. Distinguish multiple views, crops and independently repeated performances; keep unknowns as candidates. Separate production facts from viewing inference. Unfilmed A1/B1 remain planned labels and conclusions must be conditional.

Replay does not alter within-file structure

Return with available seek controls and play between segment anchors, separately logging review-pass number. If a loop setting exists, inspect its actual state rather than assuming a universal control; manual return also works. An end-to-start return may be looping or reopening, not an added in-file segment. Restore optional captions after clearing marks; burned-in labels remain. Keep version, speed and display fixed rather than changing views while comparing tiny details. Describe pauses, buffering and replay separately, not interchangeably.

Do not turn repetition into deception or non-occurrence

Repetition can emphasise teaching, replay sport or structure narrative; detecting a candidate establishes neither malice nor that the action never occurred. Three repeats are also not three independent event records. Write known A1 copied twice or suspected repetition requiring provenance, not an authentication verdict from unresolved editing. Similar frames cannot guarantee an unedited, uncomposited film or forensic suitability. Event-count verification needs original records with provenance; ordinary viewing offers limited clues, not professional authentication or an automatic forensic feature here.

Reopen and verify all three count fields

Reopen the same version and verify two segment anchors, review-pass log and source account. Restate the conditions for A’s two presentations/one source event and B’s two/two. In a paper-only exercise these remain planned relations and playback stays untested. Keep originals, edited copies and first notes. Start a new record for a changed file rather than reusing counts. Another reader should distinguish review passes, within-file appearances and supported occurrences, retaining unknowns. New footage needs new identity/provenance, not this two-segment explanation imposed on every repetition.

Related tutorials and sources

iCouldPlay repeating actions: define cycles with the same reference state; iCouldPlay reversed footage: separate file playback order from the original event order.

Sources checked on 11 November 2026: the official iCouldPlay App Store listing and Apple Lookup show version 1.1.1, requiring iOS / iPadOS 15.0 or later. This workflow uses ordinary playback and manual records through controls actually present. External editing and sample creation are not newly promised iCouldPlay features. Confirm capabilities against installed version, engine and source. Examples and plans are not step-by-step device tests or guarantees about every device.

Concept reference: BFI’s Look Again film-education guide recommends repeated viewing, identifying shot changes and comparing screen with story time. A1/B1 and the copy comparison are original plans. The source supports an editing-reading framework, not source authenticity or event-count certification.