# iCouldPlay shot changes: separate screen positions, eyelines and the scene axis

Language: en
Canonical: [iCouldPlay shot changes: separate screen positions, eyelines and the scene axis](<https://allluckly.cn/en/guides/icouldplay-shot-axis-screen-position-continuity/>)
中文：[中文 HTML](<https://allluckly.cn/guides/icouldplay-shot-axis-screen-position-continuity/>)
English: [English HTML](<https://allluckly.cn/en/guides/icouldplay-shot-axis-screen-position-continuity/>)
Published: 2026-11-09T00:00:00+08:00
Modified: 2026-11-09T09:37:10+08:00
Author: Bison

Record character identity and screen position across cuts using self-made cards, applying the scene-axis concept without assuming real movement from one reverse shot.

English translation of the [Chinese original](<https://allluckly.cn/guides/icouldplay-shot-axis-screen-position-continuity/>), translated on 2026-11-09. Original publication dates, attribution, code and version notes are retained.

A dialogue can cut from a wide view to individual close-ups, shifting screen position without changing the participants’ real placement. Screen sides, eyelines and camera side are distinct relationships. Use two self-made character cards, A and B, and record the sequence shot by shot in iCouldPlay. No face recognition or 3D camera recovery is required, and the axis guideline is not a physical law that every film must follow.

## Give character identity a stable reference

Use red card A and blue card B as characters, facing one another with simple arrows. Film a shared wide view and two close-ups, recording placement and camera side in production notes. Paper cards avoid private conversations. Keep A and B readable rather than relying on color alone. An existing clip without a shared reference leaves scene relationships uncertain; clothing color alone does not prove that people in separate shots are identical.

## Identify shots on the first normal playback

Play the complete clip normally and identify visible cuts into the wide view, A close-up and B close-up. A pause does not create a shot. Record within-shot camera movement separately from cuts. Approximate player positions and content landmarks suffice; exact frame cuts or edit timecodes are unnecessary. If dissolves, jumps or obstructions make boundaries unclear, keep candidate intervals rather than forcing shot numbers onto every frame. A buffering pause is not an editorial cut.

## Record screen position and eyeline for each shot

Pause on a stable image in each shot and record A’s screen side, arrow direction and whether B is visible. Left consistently means the viewer’s screen-left, not the character’s left-hand side. A close-up showing one card does not reveal the other card’s position from empty off-screen space. If an arrow is cropped, mark it unseen instead of importing production knowledge. Complete visible observations before interpreting spatial continuity.

## Use the shared wide view to define an illustrative axis

On paper, connect A to B as the exercise’s scene axis and place documented camera positions on its two sides. The [Columbia Film Language Glossary axis explanation](<https://filmglossary.ccnmtl.columbia.edu/term/180-degree-rule/>) describes how same-side shooting helps preserve screen relationships across cuts. This sketch uses your production record, not exact camera recovery from unfamiliar footage. Character movement, continuous camera crossing or a new establishing view can alter the relation; the axis is not a permanent line fixed to the room.

## Check identity across same-side close-ups

Compare close-ups documented as shot from the same side. Check whether the arrows form an intelligible facing relationship, then return to the wide view to identify the cards. Characters need not occupy identical pixel coordinates; framing and looking room can differ. Record the available cues rather than equating easy comprehension with compliance with every cinematic convention. Incorrect arrows or a flipped card are production problems, not discrepancies to conceal with axis theory.

## List possible explanations for a side reversal

If you have a shot from the opposite side, compare its screen relationships with the same-side example while retaining documented camera placement. In real films, reversed screen sides can also arise from movement, mirroring, a different scene or mistaken identity. One reverse shot cannot prove an axis crossing. Separate visible change from established cause; your documented sample alone can directly establish its camera side. A disorienting relation is not automatically an error, since storytelling and other references may explain it.

## Look for reorientation in neighboring shots

Replay from before the uncertain cut and look for a shared wide view, a visible movement path or a camera move that re-establishes space. Two paused screenshots can omit the continuous explanation, so do not rely on them alone. Missing context remains missing; do not invent intervening actions. An external sketch can use solid lines for observed relations and question marks for uncertainty, but this personal convention is not an authentic production floor plan.

## Check cropping, mirroring and display conditions

Use readable source text and shared references to consider mirroring rather than assigning every reversal to camera crossing. If fill cropping hides a card, an available fit control may restore frame edges, but it cannot reveal someone absent from the source. Keep orientation and source fixed for one comparison, then restore settings. Suspected processing without production evidence remains an open question; do not search for an invented automatic spatial-correction button.

## Conclude visible and production evidence separately

Keep shot order, card identity, screen sides, arrow directions, shared references, known camera sides and unknown relationships. Compare sides in your documented example while restricting unfamiliar-film conclusions to available evidence. Restore the viewing position and preserve original shots and notes. The task uses ordinary playback and paper sketches, not automatic camera estimation, production grading or claimed frame-level physical-device validation. Success means traceable relationships and clearly labeled inference.

## Related tutorials and sources

[Check mirror references](<https://allluckly.cn/en/guides/icouldplay-mirrored-recording-direction-evidence/>), [Observe dissolve transitions](<https://allluckly.cn/en/guides/icouldplay-dissolve-transition-two-scene-evidence/>).

Checked on November 9, 2026 against the [official iCouldPlay App Store listing](<https://apps.apple.com/cn/app/id6755653178>) and [Apple public lookup](<https://itunes.apple.com/lookup?id=6755653178&country=cn>): version 1.1.1, requiring iOS / iPadOS 15.0 or later. The public 1.1.1 release notes list Kodi, OpenList / AList and S3-compatible storage, with improvements to source switching and captions after seeking. The tasks use this public scope and existing playback capabilities. Check controls in your installed version. Self-made samples, manual records and external file preparation are workflows, not newly promised automatic features. No physical-device or private-server test is claimed.