Viewing and controls
Organise personal recordings in iCouldPlay with dates and events
Create a date-and-event inventory for personal recordings and verify their real content after scanning.
On this page
Personal trips and family clips may lack film artwork, and automatic matches can misidentify them. Dates, events and segment relationships are often better references. Inventory a small set outside the app, then import and verify in iCouldPlay without assuming facial recognition or automatic date albums.
Retain originals and reliable dates
Choose samples and record actual or approximate capture dates and events. Modification dates can change during copying; do not invent precision for tidy sorting. Keep private inventories under your own management.
Inspect opening and ending to distinguish event segments, accidental takes, short cuts and camera angles. Similar names and sizes do not establish duplicates. Identify content before renaming copies, preserving unique originals and their locations.
Name viewing copies clearly
Use consistent date order, event names and segment numbers with genuine extensions. Mark uncertain dates and distinguish intended viewing order from capture order, particularly edited material. Retain original-to-edit relationships for later retrieval.
Keep names concise and detailed private context in the external list. Test three names before expanding. Random suffixes alone are less useful, and renaming does not repair orientation, alter content or guarantee transferred progress.
Import small batches and verify scenes
Use a verified file or Photos route, then open entries against events and segment numbers. Completion counts can differ through collisions or existing items. For missing clips, inspect actual download, name identity and browsing scope before deleting and restarting a batch.
Artwork and synopsis are metadata; personal content identity rests on pictures, duration and source. Use actual correction controls where available, without promising universal rematching. Retain a clear inventory instead of assigning a film title merely to obtain attractive posters.
Build an event sequence
List opening, main activity and ending externally with filenames and scene anchors. Use actual sorting or browsing capabilities without assuming similar names create an automatic continuous album. Manually verify three segments and their editions first.
Check portrait and landscape framing separately. Original footage and a short recap can both be useful, as can multiple angles. Verify sound in personal narration and actual beginning, middle and ending rather than relying on thumbnails.
Keep sources and progress understandable
Identify the primary viewing route and original locations across phone, NAS and edits. Matching names across sources do not promise shared progress, and path changes may change identity. Record scenes and times before using another route rather than copying a percentage.
For similar continue-watching cards, inspect source and duration before clearing history. Completed shorts and ongoing long recordings can appear differently, without disappearance proving file deletion. Retain a local reference to separate data availability, metadata and watching state.
Verify by retrieving originals
Choose three displayed clips and find their external originals using names and inventory, comparing pictures and duration. Before cleanup, distinguish irreplaceable footage from reproducible copies and inspect deletion scope; card removal can affect local files.
Completion means reliable or explicitly uncertain dates, clear events and traceable copy relationships. Apply the same modest batch routine to new footage. App access and your external personal context complement each other without inaccurate film artwork replacing known real events.
Related tutorials and sources
Continue with Photos import, Same-name copy checks.
Checked on October 27, 2026 through Apple's public lookup: iCouldPlay 1.1.0 requires iOS / iPadOS 13.0 or later. Feature scope follows the official App Store listing. This article describes a workflow and checks, without treating development-only controls as verified public features or claiming step-by-step physical-device or private-server testing. Follow the options in your installed version.