Symptoms
The live preview is fine, but some captured photos are absent after card import. This guide addresses the specific difference between what still works and what fails. It uses a controlled comparison instead of a general reset: Check the in-app capture counter and compare card contents with a single new photo in the camera. The goal is to restore the documented behavior while retaining the original data and configuration.
- Primary symptom: The live preview is fine, but some captured photos are absent after card import.
- Baseline measurement: Check the in-app capture counter and compare card contents with a single new photo in the camera.
- Normal path to preserve: The final recorded file or captured frame, not only the preview, meets the requirement.
Why It Happens
A preview shows that at least one part of the imaging pipeline is alive; codecs, card writing, output ports and imported metadata are separate stages. Trust the saved sample and its measured properties.
Three plausible explanations should be checked in sequence; none is proven merely because it is common on similar devices.
- Wrong storage destination. Treat this as a testable explanation for the observed difference; compare against the stated baseline rather than assuming it is the cause.
- Incomplete write. This may affect the specific step that fails while leaving the comparison case intact.
- Card or reader fault. If the first two possibilities are excluded, use the deeper diagnostic described below to check this layer.
Before Making Changes
Do not format a card containing missing originals or fly while storage warnings persist.
A successful live preview or camera indicator does not guarantee the final saved file contains the expected data. Always check the recording or export itself.
Take a screenshot or short written note of the original values. If the test needs a file, export, print or recording, create a disposable sample or work on a duplicate; do not replace an irreplaceable original. Do not alter shared or managed equipment without appropriate permission.
Problem-Specific Diagnosis
The table separates observations, interpretations and next actions. Start at the top and stop as soon as the expected outcome is restored.
| Test | What it distinguishes | Next action |
|---|---|---|
| Check the in-app capture counter and compare card contents with a single new photo in the camera. | Whether the failure is tied to the original condition or also affects the control. A difference supports investigating wrong storage destination. | Stop recording properly, power down and read the card through a compatible reader before changing formats. |
| Check the setting or route involved in: Stop recording properly, power down and read the card through a compatible reader before changing formats. | If only the affected path improves, incomplete write is worth inspecting next. | Restore previous settings if the expected result does not change. |
| Compare internal storage versus SD selection, file-system health, card write speed and folder structure. | A second-layer difference can support investigating card or reader fault without treating it as certain. | Use vendor-specific guidance or authorized service for the isolated layer. |
| A new test photo appears on the intended storage and opens on a computer. | A stable result after normal reconnection is more persuasive than a transient indicator. | Retain the working configuration and document the observed pass condition. |
A useful negative result is not wasted effort. If the first comparison does not isolate the fault, note exactly which variable stayed unchanged. This prevents moving from a narrow symptom to a factory reset without evidence.
Choose Your Fix: Beginner or Advanced
Beginner is a reversible first route; Advanced investigates different components when the baseline comparison and first correction do not explain the issue. You do not need to perform both paths if the first one fixes the problem.
Step-by-Step Troubleshooting
Choose the reversible Beginner route or the deeper Advanced route based on your comparison.
Capture a baseline for photo & video equipment
The live preview is fine, but some captured photos are absent after card import. Check the in-app capture counter and compare card contents with a single new photo in the camera. Record the exact result and one comparison that behaves normally. Note the device, app or model involved; a simple before/after note is enough.
Preserve the working configuration
Do not format a card containing missing originals or fly while storage warnings persist. Keep a copy of any file, job profile, schedule or setting that could be affected. A successful live preview or camera indicator does not guarantee the final saved file contains the expected data. Always check the recording or export itself.
Apply the least disruptive correction
Stop recording properly, power down and read the card through a compatible reader before changing formats. Do only this specific adjustment for the first trial. Do not erase data, reset the full device or rewrite unrelated settings to chase a local symptom.
Repeat the original practical test
A new test photo appears on the intended storage and opens on a computer. Reproduce the same comparison described in the first step. If the result is unchanged, undo the last reversible adjustment and proceed to the Advanced route rather than repeating resets.
Separate three plausible causes
Investigate wrong storage destination, incomplete write and card or reader fault as independent hypotheses. Check the in-app capture counter and compare card contents with a single new photo in the camera. The failure following one path is stronger evidence than a generic status icon.
Inspect the second technical layer
Compare internal storage versus SD selection, file-system health, card write speed and folder structure. Record exact supported option names, event times and physical observations. Do not change hardware settings or permissions until a controlled comparison identifies the relevant layer.
Cross-check against a working control
Test the unaffected condition again without applying the beginner correction a second time. Ask whether the evidence points to incomplete write rather than wrong storage destination; use one known-good cable, file, profile, network or environment only where safe and available.
Escalate with evidence and a rollback plan
If this remains unresolved, record the two test outcomes, model and supported firmware/software versions, and the observed difference. Do not format a card containing missing originals or fly while storage warnings persist. Share a redacted summary with authorized support rather than changing unrelated components.
Common Mistakes to Avoid
- Treating wrong storage destination as a proven cause without comparing the failing condition.
- Repeating stop recording properly, power down and read the card through a compatible reader before changing formats while ignoring evidence pointing to a separate technical layer.
- Changing several independent controls together and then losing track of which change mattered.
- Skipping this precaution: Do not format a card containing missing originals or fly while storage warnings persist
How to Verify the Fix
A new test photo appears on the intended storage and opens on a computer.
Perform the same practical check again after a normal restart, reconnection or next scheduled cycle, as appropriate for this device. Confirm that the original unaffected function still works and that the correction did not introduce a new problem.
If the result cannot be reproduced reliably, retain the notes and classify the problem as intermittent rather than declaring a permanent fix.
If the Problem Continues
Move to the deeper test only after the first correction has been measured: Compare internal storage versus SD selection, file-system health, card write speed and folder structure.
Provide authorized support with the exact symptom, model identifier, relevant software or firmware information, timestamps, first comparison and actual final result. Do not upload passwords, QR codes, account tokens, student records, private recordings or personal location details.
A limitation documented for the device or service may require a supported alternate workflow; a damaged component, hazardous appliance or account-policy restriction needs professional or administrator assistance rather than an improvised bypass.
Prevent Recurrence
Save a note of the working configuration and keep original source files, profiles and service permissions available for recovery. Repeat the same short comparison after major changes to firmware, installed applications, cable routing, profiles, schedules or storage.
For this problem the most useful periodic check is the actual outcome: A new test photo appears on the intended storage and opens on a computer.
Frequently Asked Questions
Why does this happen if another related function still works?
Because wrong storage destination, incomplete write and card or reader fault affect different stages. Check the in-app capture counter and compare card contents with a single new photo in the camera. That comparison is more useful than a broad “connected” or “ready” indicator.
What is the safest first change?
Stop recording properly, power down and read the card through a compatible reader before changing formats. Do not format a card containing missing originals or fly while storage warnings persist. This first action is limited in scope; it is not permission to remove protections, overwrite original files or reset every setting.
How do I know I fixed the actual problem?
A new test photo appears on the intended storage and opens on a computer. Reproduce the original failing situation and repeat the check. If the result returns only briefly, keep the evidence and investigate the deeper layer: Compare internal storage versus SD selection, file-system health, card write speed and folder structure.
Solution Checklist
Use the checklist to distinguish a tested correction from a change that merely hid the symptom.