Symptoms
A captured time-lapse appears accelerated beyond the intended speed in an editing project. This guide addresses that particular contrast, not every fault that can occur with the product or service.
- Observable failure: A captured time-lapse appears accelerated beyond the intended speed in an editing project.
- Control test: Compare source metadata frame rate with project interpretation and export fps.
- A confirmed correction must meet this outcome: Playback duration matches the intended interval and frame rate.
Write down the exact sequence that reproduces the failure and the moment it stops. Intermittent failures are easiest to isolate when the same short test is repeated before and after one change.
Why It Happens
Camera originals, live previews and low-resolution caches are different files. Flight safety and recording integrity should not be put at risk merely to correct a transfer or playback issue.
The important distinction is whether source recorded as video sequence or editor interprets frame rate incorrectly explains the observed difference. Speed ramp already applied remains another plausible explanation until the comparison rules it out.
Three competing explanations
- Source recorded as video sequence.
- Editor interprets frame rate incorrectly.
- Speed ramp already applied.
These are hypotheses. Do not infer a hardware defect, account restriction or network outage from one status indicator alone. A result that supports source recorded as video sequence does not automatically exclude editor interprets frame rate incorrectly; the comparison needs to separate them.
Before Making Changes
Do not alter flight-critical controls for a media problem and preserve the original card or flight log until the copy is verified. Do not overwrite the original camera file.
Preserve the current state: note the affected product or account, current mode and time of the failed attempt. If settings will be changed, photograph or write down their original values. Keep copies of any unique files or evidence before overwriting anything.
Use a non-sensitive sample whenever possible. If the issue involves a shared device, building system, workplace account or regulated equipment, obtain the appropriate owner or administrator permission first. Stop if the test would compromise security, electrical protection, access or an animal's welfare.
Problem-Specific Diagnosis
Run this discriminating test before restarting or resetting the entire system: Compare source metadata frame rate with project interpretation and export fps. Compare the observed result against the three paths below.
| Observation or suspected layer | Interpretation | Next controlled check |
|---|---|---|
| Source recorded as video sequence | If the failing state changes under the comparison, source recorded as video sequence is plausible. This is not yet proof. | Repeat with that one factor changed, then return to baseline. |
| Editor interprets frame rate incorrectly | If the first change has no effect but a supported configuration differs, editor interprets frame rate incorrectly moves higher on the list. | Inspect the relevant option or documented behavior without clearing unrelated settings. |
| Speed ramp already applied | If both earlier paths are contradicted, investigate whether speed ramp already applied accounts for the timing or device-specific result. | Collect an event timestamp or status report for qualified support. |
Now apply the least-disruptive change that corresponds to the evidence: Reset clip speed on a duplicate timeline and match documented source fps. Avoid treating all three hypotheses at once; simultaneous changes erase the diagnostic value of the test.
Step-by-Step Troubleshooting
Begin with reversible comparisons. Use Advanced only if the evidence points to a deeper problem.
Verify the affected workflow
A captured time-lapse appears accelerated beyond the intended speed in an editing project. Write down where it happens, its most recent time and the state displayed by the product. Do not treat a nearby working feature as proof the whole path is healthy.
Run the safe comparison
Compare source metadata frame rate with project interpretation and export fps. Use the same device, account and operating conditions where practical. Note what remains unchanged so the comparison is meaningful.
Try the smallest safe intervention
Reset clip speed on a duplicate timeline and match documented source fps. Make one adjustment at a time and preserve the previous value so it can be restored if the result becomes worse.
Confirm the real outcome
Playback duration matches the intended interval and frame rate. Repeat the complete user-facing operation and then make sure unrelated protections and functions still work. If the result is inconsistent, restore the previous setting and continue diagnosis.
Separate the three suspected layers
Assess evidence for source recorded as video sequence, editor interprets frame rate incorrectly and speed ramp already applied separately. A positive result for one path is not evidence for every path. Preserve before-and-after observations, including timestamps.
Check the responsible subsystem
Inspect time-base metadata and sequence interpretation separately before transcoding. Gather only logs and supported diagnostic views that apply to this exact scenario; do not change service-wide policy or hardware wiring.
Validate the unaffected path
Revisit the comparison: Compare source metadata frame rate with project interpretation and export fps. If the first suspected cause is not supported, compare the behavior predicted by editor interprets frame rate incorrectly with the behavior predicted by speed ramp already applied. Keep the first correction reversible.
Commit or escalate with evidence
Confirm: Playback duration matches the intended interval and frame rate. If that cannot be reproduced, restore the original safe configuration and send sanitized observations to the aircraft or action-camera manufacturer. Safety boundary: Do not overwrite the original camera file.
Solution Checklist
Solution Checklist
Common Mistakes to Avoid
- Assuming source recorded as video sequence is proven simply because the visible symptom matches this page.
- Changing multiple accounts, rules, connections or device settings before running the control: Compare source metadata frame rate with project interpretation and export fps.
- Skipping this safety boundary: Do not overwrite the original camera file.
- Resetting, formatting, deleting credentials or replacing hardware without a confirmed backup, a supported recovery path and evidence that the step is necessary.
A setting that makes one symptom disappear is not always the correct permanent configuration. If it disables another essential function, revert it and investigate the underlying dependency rather than leaving an unsafe workaround in place.
How to Verify the Fix
The primary pass condition is specific: Playback duration matches the intended interval and frame rate. Repeat the original workflow, not a loosely related shortcut, and confirm both the previously failing behavior and an unaffected comparison still work.
- Record the before-and-after state in the same location, account and operating mode.
- Repeat the original comparison: Compare source metadata frame rate with project interpretation and export fps.
- Check the stated pass result: Playback duration matches the intended interval and frame rate.
- Confirm that normal security, notification, storage or physical safety protections remain enabled.
If the result works only once or disappears after reopening the app, reconnecting the accessory or waiting for the next scheduled event, treat the issue as intermittent instead of fixed. Keep the event time and what changed between attempts.
If the Problem Continues
If the safe correction does not work, move to a focused deeper investigation: Inspect time-base metadata and sequence interpretation separately before transcoding. This is a different path from the first settings check; use it only if the device or service supports the required diagnostics.
When escalating to the aircraft or action-camera manufacturer, provide the exact symptom, result of the control test, changes already tried, time of occurrence and any non-sensitive error or status data. Explain whether source recorded as video sequence, editor interprets frame rate incorrectly and speed ramp already applied were supported or contradicted by evidence.
Do not share account recovery codes, private documents, live access tokens, sensitive location histories or full recordings merely to prove the problem. Redact or summarize identifiers before opening a public support request.
Prevent Recurrence
Keep a short reference note with the working configuration and the successful check: Playback duration matches the intended interval and frame rate. After an app update, firmware change, network migration or scheduled clock change, run the same short test before depending on the function again.
Watch for the condition that originally made the failure visible: A captured time-lapse appears accelerated beyond the intended speed in an editing project. Where practical, retain an alternative approved way to perform the essential task so that one device, cloud service or interface does not become a single point of failure.
FAQ
How can I tell whether source recorded as video sequence is responsible?
Run the controlled comparison: Compare source metadata frame rate with project interpretation and export fps. A change that specifically affects the failing layer supports this hypothesis, but repeat it before changing permanent settings.
What if the real cause is editor interprets frame rate incorrectly rather than source recorded as video sequence?
Do not repeat the initial correction blindly. Check the supported diagnostic path: Inspect time-base metadata and sequence interpretation separately before transcoding. Keep the earlier working configuration recorded so you can reverse the test.
When is this particular issue resolved?
The decisive result is: Playback duration matches the intended interval and frame rate. If it fails after the normal workflow is repeated, document whether speed ramp already applied still explains the remaining behavior and escalate with non-sensitive observations.