This article explains how to resolve Aura processing errors caused by incorrectly named or non-sequential video files used for colorization.
Error message
Processing Failed: FrameExtraction validation: Non-contiguous video files. Files should be named GS01..., GS02..., GS03... etc. (or GH or GX).
Processing Failed: FrameExtraction validation: Unsupported video file name(s). File name should start with GS, GH, or GX, followed by 6 digits.


Why this occurs
Aura requires video files used in the colorization process to retain their original filenames as they came directly from the camera. If the files have been renamed, Aura may not correctly match them with the corresponding scan data, resulting in failed or mismatched processing.
This can happen when files are renamed during data transfer, reorganization, or upload. The original filenames (for example, GS010123.360, GS020123.360) are essential for Aura to establish accurate synchronization and file mapping.
Cause: renamed or mismatched video files
Aura relies on GoPro's original file naming convention to correctly sequence and align video files with scan data. If the files are renamed, either accidentally or during transfer, Aura may be unable to associate them correctly with the scan, which can lead to issues such as frame extraction errors, sync mismatches, or complete failure of the colorization process.
Resolution
There are two options to resolve this issue:
Restore the original GoPro filenames. This is the most reliable approach. Files should match the original names exactly as they came off the camera (for example, GS010123.360, GH020123.MP4, GX030456.360).
Manually rename the files using GoPro's expected structure. If the original names are not available, rename the files using a format that Aura can interpret. The goal is to clearly signal the sequence of the video segments and their relationship to the capture session.
If restoring the originals is not possible, follow the procedure below to manually rename the files.
GoPro file naming convention
GoPro video files follow this general naming format:
[Camera Identifier][Chapter Number][Clip Number].[File Extension]
Example: GS010123.360
Camera identifier (GS, GH, or GX)
Indicates video type and encoding:
GH = H.264 codec (standard).
GX = H.265/HEVC codec.
GS = Typically used for 360-degree GoPro Max video.
Aura recognizes all three prefixes.
Chapter number (01, 02, 03)
Each recording is split into 4 GB segments.
The chapter number indicates the file's position in that session.
For example, GH010123 is the first segment, GH020123 is the second, and so on.
Clip number (0123)
Represents a single recording session, from the moment Record is pressed until stopped.
All segments from the same session share the same clip number.
Example
A single recording session that spans multiple files might include:
GS010123.360 is the first file of clip 0123.
GS020123.360 is the second file of the same clip.
GS030123.360 is the third file of the same clip.
All files belong to clip 0123 and should be kept in sequence.
Step 1: Determine the correct sequence
Watch each video to determine the correct sequence.
Use visual cues (such as start/stop motions, lighting, or scene progression) to identify the chronological order in which the videos were captured.
Step 2: Rename the video files
Rename each file using the correct structure:
Use GS, GH, or GX as the prefix (depending on the original video type).
Assign a chapter number (01, 02, 03, etc.) based on the order determined in Step 1.
Choose a clip number (for example, 0123) and keep it consistent across all segments from the same recording session.
Use the .360 file extension if the video was captured using a 360-degree camera.
Double-check that the files are in the correct sequence and that names follow the format [Camera Identifier][Chapter Number][Clip Number].[File Extension].
Can this data still be processed?
Yes, provided all video files are present and complete, the data can still be processed by following the steps above. This includes restoring the original filenames or renaming the files using a format that Aura can ingest.
Related documentation and support
For assistance, contact the regional Emesent partner or the Emesent Client Support team.
