iCouldPlay same-name imports: distinguish skipped files and separate versions

Two files called video one can contain completely different recordings. No additional iCouldPlay card does not establish that the new content replaced the old file. Test two of your own clips, then use clear version names and verify playback. Work with copies instead of uncertain overwrite experiments on unique family footage.

Prepare unmistakably different samples

Choose a clip opening with a red object and another with a blue object, recording durations and sizes. Confirm both play elsewhere. Make the distinction obvious in the first seconds so identity does not depend on artwork, generated numbers or memory.

Retain originals in separate known folders and give test copies matching filenames. Do not overwrite an original to create the collision or delete the old app entry first. Preserve a clear before-state and keep original locations and counts understandable throughout.

Import and identify the first clip

Import the red clip, wait, inspect duration and open it. Record display name, source and a middle scene, then leave normally. Any incorrectly matched artwork remains a metadata difference; actual pictures and source establish identity.

Reopen the first clip before proceeding. Import one at a time to avoid confusing aggregate counts with name handling. Confirm the file provider supplied actual local data first; a visible placeholder and an import collision are different problems.

Observe what the second import actually did

Select the blue sample and inspect completion, success counts and library changes. Name collisions may skip an existing file; do not assume an overwrite prompt, automatic renaming or replacement. If no card appears, open the original entry and compare its actual colour with the retained originals.

A completion summary does not establish independent preservation of every selected file. Record unchanged counts without deleting the old entry to experiment. Clear copy identity is the next step; deletion can affect local data and is unsuitable for guessing overwrite behaviour.

Give an external copy an understandable name

Leave originals intact and rename the blue copy with date, subject and version, distinguishing the two demonstrations. Keep the genuine extension. Names identify files without converting codecs, changing quality or repairing damaged data.

Use sequence numbers for separate takes and clear original or short-edit labels for cuts. Random suffixes alone are difficult to interpret later when pairing subtitles or restoring sources. Confirm you renamed a copy, open it and import that clearly identified file.

Open both entries and compare

Check opening, middle and ending in both samples, ruling out two names playing the same content. Compare duration too. Display names, metadata titles and filenames can differ, particularly after automatic matching, so card count alone is insufficient.

Leave and reopen both, observing their individual locations. Similar subjects and artwork do not prove shared identity or progress across paths. Renaming does not promise progress migration; record a scene first if you need to find the corresponding location in a new copy.

Identify cleanup scope before removing tests

Confirm independently retained originals and read current removal prompts. An operation can affect metadata or imported local files; do not infer scope from a button label. Test only clearly disposable copies and check the other still plays, avoiding bulk selection of similar names.

Two purposeful versions need not be reduced to one card. Different cuts, camera angles and repairs can remain useful. Compare size and retention purpose for space management rather than equating similar names or artwork with redundant files.

Record your import convention

Keep original and import-copy names, subject, date and primary version in an inventory. Compare new same-name content before naming it independently or postponing import. Reuse these two self-made samples after an update rather than reprocessing your full collection to discover changed behaviour.

Completion means known destinations for both colours, a recorded reason for any skipped import and recoverable originals. For real edits, identify subtitle counterparts and the scene from which to continue. Names, artwork and counts are clues; expected playable content is the result.

Related tutorials and sources

Continue with Local import basics, Metadata correction.

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.