Trail Maker Sequence Creation Workflow
Any user can create a Sequence. Here's how...

Overview

Sequences are created like so;
  1. 1.
    User defines sequence information
  2. 2.
    User defines camera and mode used
  3. 3.
    User defines processing settings
  4. 4.
    User defines input file
  5. 5.
    App processes input to process final imagery
Steps 1-3 can be defined in the UI or via a config file the CLI.

0. User defines app config

In config screen, user can set:
  • Authenticate to Explorer
    • if already authenticated OAuth token stored
  • Exiftool path
  • Ffmpeg path
  • Imagemagick path

1. User defines sequence information

The following sequence processing settings:
  • Sequence Name. Required
    • options: minimum of 5 characters and maximum of 30 characters. Characters allowed: a-z, 1-9, and '-'
  • Sequence description. Optional
    • options: Max 280 chars. No special chars.
  • Sequence transport type. Required
    • options (see transport type table)
      • parent (e.g. water)
      • child (e.g boat)
  • tags. Optional.
    • options. Max 30 chars. A-Z,1-9,and "-".

Transport types

Parent
Parent
Icon
Air
Air
Snow
AcUnit
Water
Water
Earth
Grass
Child
Child
Parent
Icon
BASE Jump
Air
Paragliding
Glider
Air
Send
Hang Glide
Air
Send
Parachute
Air
Paragliding
Paraglide
Air
Paragliding
Wingsuit
Air
Send
Bicycle
Earth
PedalBike
Bicycle (electric)
Earth
ElectricBike
Rollerskate
Earth
​
Scooter
Earth
​
Scooter (electric)
Earth
ElectricScooter
Skateboard
Earth
Skateboarding
Walk
Earth
DirectionsWalk
Rock Climbing
Earth
​
Wheelchair
Earth
AccessibleForward
Ski
Snow
DownhillSkiing
Snowboard
Snow
Snowboarding
Snowshoe
Snow
Snowshoeing
Ice Skating
Snow
IceSkating
Canoe
Water
Kayaking
​

2. User defines camera and mode used

Define Camera and Mode

Below are the variations of GoPro cameras and modes supported.
Note, the validation step refers to validations carried out on the input file.
  • MAX
    • timelapse photo mode
      • 360 mode
        • validation: mode=photo+equirectangular
        • cli value
      • HERO mode
        • validation: mode=photo+hero
    • video mode (inc. timewarp)
      • 360 mode
        • content stitched
          • validation: mode=video+equirectangular
        • content unstitched
          • validation: mode=video+eac
      • HERO mode
        • validation: mode=video+hero
  • Fusion
    • timelapse photo mode
      • 360 mode
        • content stitched
          • validation: mode=mode+equirectangular
        • content unstitched
          • validation: mode=photo+fisheye
      • HERO mode
        • validation: mode=photo+hero
    • video mode
      • 360 mode
        • content stitched
        • validation: mode=video+equirectangular
        • content unstitched
          • validation: mode=video+fisheye
      • HERO mode:
        • validation: mode=video+hero
  • HERO 5 (and newer)
    • timelapse photo mode
      • validation: mode=photo+hero
    • video mode (inc. timewarp)
      • validation: mode=video+hero

3. User defines processing settings

Define Processing Settings

The processing settings presented to the user depend on the camera and mode selected, as shown below.
The following sequence processing settings:
  • Output frame rate
    • description: how many frames ffmpeg should extract from the video, per second
    • options: 0.1, 0.2, 0.5, 1.0, 2.0, 5.0
    • default: 0.5
    • cameras(modes): all(video mode)
  • Output Image Spacing
    • description: the minimum spacing (in meters) between photos. This is a useful setting for spacing out images close together (or in same place) to reduce amount of output images
    • options: 0.5, 1.0, 2.0, 3.0, 4.0, 5.0, 10.0
    • default: null (no minumum spacing)
    • cameras(modes): all(all)
  • Timelapse Time Warp Mode Used
    • description: needed if the video was shot in Timelapse Time Warp mode. This setting ensures GPS positioning is properly adjusted to account for acceleration in video speed used in Timewarp mode.
    • options: true / false
      • If true; options; 2x, 5x, 10x, 15x, 30x
    • default: false
    • cameras(modes): all(video mode)
  • Output Image Quality
    • description: defines the jpg quality setting (q:v) to be used in ffmpeg command (if 1 selected, output is png, so q:v not used)
    • options: 1, 2, 3, 4, 5, 6
    • default: 1
    • cameras(modes): all(video mode)
  • Add Nadir (360 mode) / Watermark (HERO mode) to Images
    • descriptions: adds the selected nadir to 360 images or watermark in bottom left hand corner for HERO images
    • options: true / false
      • If true; options;
        • Export image copies: Only nadir copies, Raw and nadir copies (inc. copy of images without nadir)
        • Size (as percentage of image height): 8-20 (in 1.0 increments)
        • Nadir Image: Trek View logo; Upload own logo (Must be a .png file. Dimensions must be square. Minimum size allowed is 500px x 500px)
    • default: false
    • cameras(modes): all(all)

Define Local Settings

Frame Maker ships with some default dependencies. These paths are automatically defined. In some cases user might want to modify them, and in such cases a user can optionally specify their own install paths for;
  • ffmpeg path
  • exiftool path
  • imagemagick path
  • image output directory

4. User defines input file

User can add the appropriate file for camera and mode used.
Image or video metadata is validated against the camera and mode selected.

Purpose of validations

Validations are done to ensure images and videos can be processed correctly.
Other validations (e.g video length) are carried out to ensure there are enough images for the sequence to process correctly.

Validation error types

Files validation can result in 2 types of errors:
  1. 1.
    Non-critical errors (soft errors): user can continue if they accept the warning (e.g. some files will be removed)
  2. 2.
    Critical errors: these cannot be rectified. A user will see the error message, and be forced to go back and re-select files to account for the error condition before being able to continue.
Validations are run in two parts. First all the soft validations (if applicable) are run. If user continues, then all hard validations are run. All validations are run so that user can see all the errors in the file(s) they are attempting to upload (and thus are able fix as needed).

Validations

Validations are run in the order shown
Of course, only validations applicable for the mode selected by a user are run. 2 examples;
  • If a user selects video>360>stitched: only video equirectangular validations are applied
  • If a user selects photo>hero: only photo hero validations are applied
The selection tree at the top of the page shows the validations for each mode (note, whilst camera is listed there, the camera selected has no impact on the validation, only the mode selected by user affects the validation. This is because, as you can see, some cameras share the same modes.)

5. App processes input to process final imagery

Once validations have passed, app will process imagery and output in specified output directory.

6. Upload of files to Explorer starts

​
If you want to understand what happens during processing in detail, take a look at the developer docs: