A good technical question can save hours of back-and-forth. You do not need to be an expert, but a few details make it much easier for other members to reproduce the problem and give a useful answer.
Include the source
- Camera make and model
- Resolution and frame rate
- HDR, HLG, Log or standard profile
- Whether telemetry/GPS is embedded or external
- Whether the file was converted, remuxed or downloaded from another service
Include the editing environment
- Editor name and version
- Windows/macOS and basic hardware if performance is involved
- GPU model when decoding, rendering or Vulkan/CUDA/OpenCL behavior is relevant
- Any plugin or external telemetry utility used in the workflow
Describe what you expected and what actually happened
“GPS is broken” is difficult to diagnose. “The speed overlay is correct at the beginning but about four seconds late after ten minutes” immediately suggests a different class of problem than a constant four-second offset.
For color questions, describe whether the source looks wrong in the editor, only after export, or only after uploading to a platform. For performance questions, say whether the slowdown is decoding, scrubbing, effect preview, proxy generation or final rendering.
Preserve the original media
If metadata, HDR flags or unusual codecs are involved, keep the untouched source. A converted sample may remove the very information needed to diagnose the issue.
Use screenshots carefully
A screenshot of an error message is useful. A screenshot of a washed-out image is less useful without source/profile/export information. If you can legally share a short sample file, say so; do not upload private location data without checking what metadata it contains.
One problem per topic
If possible, keep one main technical issue per thread. A topic that simultaneously asks about GPS drift, HDR conversion, slow proxies and YouTube bitrate becomes difficult to answer and difficult for future readers to find.
Suggested title format: Camera + problem + editor. Example: “GoPro HERO13 GPS overlay drifts after trimming in [Editor]”.
Action Video Lab is intended to be a practical technical community. Clear problem reports help both the person asking and everyone who finds the topic later through search.
Action Video Lab Editorial Team