This technical guide is published by AIGLAS, a UK smart-glasses brand. It includes one link to our website.
First-person video from everyday smart glasses is easy to capture and surprisingly easy to mishandle later. Clips arrive with uneven names, mixed frame rates, rotating phone uploads, and metadata that does not always survive the first copy. If you treat the phone gallery as the archive, you will lose the original file, the timestamps, or both.
This article is a repeatable, command-line workflow for people who want a technical trail: copy footage off the device, inspect what you actually have, make a working transcode without destroying the original, and keep a short log of what changed. The examples use ffmpeg, ffprobe, and a small Bash script on Linux or macOS. Nothing here assumes a particular product's undocumented internals. It is the same hygiene I want when I review a day's clips.
What you need
-
ffmpegandffprobeon your PATH. On Debian or Ubuntu:sudo apt install ffmpeg. On macOS with Homebrew:brew install ffmpeg. - A working copy of the day's clips in one folder. If the companion app stores files inside an app container, export or copy them first. Do not run destructive commands against the only copy.
- A place for the archive that is not the phone.
Check the tools:
ffmpeg -version | head -n 1 ffprobe -version | head -n 1 Create a clean workspace. I use a date folder and keep originals read-only once they are copied.
DAY=2026-11-17 mkdir -p "$HOME/footage/$DAY"/{inbox,originals,work,logs} Copy from the export location into inbox, then make a second copy into originals before you touch anything. If a copy fails, stop and fix the disk or cable. Do not transcode from a half-copied file.
# Adjust the source path to wherever the phone or glasses export landed SRC="$HOME/Downloads/glasses-export" rsync -av --progress "$SRC"/ "$HOME/footage/$DAY/inbox/" rsync -av --progress "$HOME/footage/$DAY/inbox/" "$HOME/footage/$DAY/originals/" chmod a-w "$HOME/footage/$DAY/originals/"* chmod a-w is a simple seatbelt. It will not protect you from sudo or a later overwrite of the folder, but it does stop a tired ffmpeg -y from writing onto the original filename in that directory.
Inspect before you convert
A wearable clip can look like an ordinary MP4 and still differ in timebase, rotation, audio sample rate, or colour range. Guessing from the filename is how people ship a 90-degree video to a client. Ask ffprobe first.
ffprobe -hide_banner -show_format -show_streams -of json \ "$HOME/footage/$DAY/originals/clip001.mp4" \ | tee "$HOME/footage/$DAY/logs/clip001.ffprobe.json" If you prefer a compact human summary:
ffprobe -hide_banner -v error \ -show_entries format=filename,duration,size,bit_rate:stream=index,codec_name,codec_type,width,height,avg_frame_rate,r_frame_rate,pix_fmt,sample_rate,channels,rotation,tags \ -of default=noprint_wrappers=1 \ "$HOME/footage/$DAY/originals/clip001.mp4" Write down four things for each clip, or have the script do it:
- Duration and file size. A two-second file that claims to be 200 MB is usually a bad copy.
- Video codec, width, height, and frame rate. Mixed 25 fps and 30 fps days are common.
- Audio codec, sample rate, and channel count. Some clips are silent; some are AAC stereo with a noisy wind track.
- Rotation tags. Some players honour
rotateordisplaymatrix; some ignore them. If a clip plays upright on the phone and sideways in the browser, the tag is the first place to look.
To print rotation-related tags specifically:
ffprobe -v error -select_streams v:0 \ -show_entries stream_tags=rotate:stream_side_data=rotation \ -of default=noprint_wrappers=1 \ "$HOME/footage/$DAY/originals/clip001.mp4" If ffprobe errors on a file, quarantine it. Do not include it in a batch transcode until you know whether the container is truncated.
Build a working file, keep the original
The working file is what you watch, trim, or upload. The original stays untouched. I transcode to H.264 + AAC in an MP4, because that combination still opens in almost every review tool I use. This is a review proxy, not an archival format. The archive is the original.
A conservative command:
IN="$HOME/footage/$DAY/originals/clip001.mp4" OUT="$HOME/footage/$DAY/work/clip001.review.mp4" ffmpeg -n -i "$IN" \ -map 0:v:0 -map 0:a? \ -c:v libx264 -preset medium -crf 20 -pix_fmt yuv420p \ -movflags +faststart \ -c:a aac -b:a 160k \ "$OUT" Notes on the flags:
-
-nrefuses to overwrite an existing output. If you need to re-run, delete the old proxy first. This is safer than-yin a loop. -
-map 0:a?includes audio if it exists and does not fail if the clip is silent. -
-movflags +faststartmoves the moov atom to the front so a browser can start playback before the file is fully downloaded. -
-crf 20is a quality target, not a bitrate cap. Raise the number if the proxies are too large; lower it only if you see obvious compression on fine text or foliage.
If the source is already a well-behaved H.264 MP4 and you only need faststart, you can remux without re-encoding:
ffmpeg -n -i "$IN" -map 0 -c copy -movflags +faststart \ "$HOME/footage/$DAY/work/clip001.faststart.mp4" Use remux when inspection shows a codec you already accept and no rotation correction is required. Use the transcode when you need a consistent review format across a mixed day.
Fix rotation in the working file, not the original
If ffprobe reports a 90-degree tag and your review player shows a sideways picture, bake the rotation into the working file. Leave the original alone.
ffmpeg -n -i "$IN" \ -vf "transpose=1" \ -c:v libx264 -preset medium -crf 20 -pix_fmt yuv420p \ -c:a aac -b:a 160k -movflags +faststart \ "$HOME/footage/$DAY/work/clip001.rotated.mp4" transpose=1 is 90 degrees clockwise. transpose=2 is 90 degrees counter-clockwise. Confirm with one clip before you apply it to a folder. After the transcode, the working file should play upright even in players that ignore metadata rotation.
A small batch script
The script below walks every MP4 in originals, writes a probe log, and creates a review proxy if one does not already exist. Save it as make-review-proxies.sh.
#!/usr/bin/env bash set -euo pipefail DAY="${1:?usage: $0 YYYY-MM-DD}" ROOT="$HOME/footage/$DAY" ORIG="$ROOT/originals" WORK="$ROOT/work" LOG="$ROOT/logs" mkdir -p "$WORK" "$LOG" shopt -s nullglob for IN in "$ORIG"/*.mp4 "$ORIG"/*.MP4; do base="$(basename "${IN%.*}")" OUT="$WORK/${base}.review.mp4" ffprobe -hide_banner -show_format -show_streams -of json "$IN" \ > "$LOG/${base}.ffprobe.json" if [[ -e "$OUT" ]]; then echo "skip existing $OUT" continue fi echo "proxy $IN -> $OUT" ffmpeg -n -i "$IN" \ -map 0:v:0 -map 0:a? \ -c:v libx264 -preset medium -crf 20 -pix_fmt yuv420p \ -movflags +faststart \ -c:a aac -b:a 160k \ "$OUT" done Make it executable and run it with the date folder name:
chmod +x make-review-proxies.sh ./make-review-proxies.sh 2026-11-17 If one file fails, set -e stops the script. That is intentional. Read the last ffprobe log, move the bad source into a quarantine folder, and run the script again. The existing proxies are skipped.
Check the result, then trim only the proxy
Compare duration, at least, so a failed encode does not sneak through:
orig_d=$(ffprobe -v error -show_entries format=duration -of csv=p=0 "$IN") work_d=$(ffprobe -v error -show_entries format=duration -of csv=p=0 "$OUT") echo "$orig_d $work_d" A difference of a fraction of a second can be normal at the container level. A difference of several seconds is not. If the proxy is much shorter, the encode likely stopped early.
When you want a short section for review, cut the proxy, not the original. A stream-copy cut at a keyframe is fast:
ffmpeg -n -ss 00:00:08 -to 00:00:22 -i "$OUT" -c copy \ "$WORK/clip001.review.excerpt.mp4" If the cut is ugly (a freeze at the start, or audio that leads the picture), do a precise re-encode of that excerpt from the proxy or, if you need maximum quality for a short excerpt, from the original into a new working file. Still do not overwrite the file in originals.
Keep a one-line log
A simple CSV is enough to reconstruct what you did later.
echo "file,duration_s,width,height,codec,note" \ > "$HOME/footage/$DAY/logs/index.csv" for IN in "$HOME/footage/$DAY/originals"/*.mp4; do ffprobe -v error -of csv=p=0 \ -select_streams v:0 \ -show_entries format=filename,duration:stream=width,height,codec_name \ "$IN" >> "$HOME/footage/$DAY/logs/index.csv" done Add a note column by hand for clips you quarantined, rotated, or rejected. Future you will not remember why clip014 was skipped.
What not to do
Do not run a “compress everything” preset over the only copy on the phone. Do not rename originals in a way that drops their export order until you have a log. Do not assume every MP4 from a wearable has audio. Do not treat a silent encode error in a long && chain as success.
If you later publish a clip, review the proxy first for bystanders, private screens, and audio you did not intend to keep. Technical hygiene and ordinary care are the same job: know what is in the file before you move it.
Closing
The useful part of this workflow is not a particular CRF value. It is the order: copy, inspect, transcode to a working file, log the result, and leave the original intact. Once that order is a habit, a day’s first-person footage is something you can reason about instead of a folder of names you no longer trust.
If you want to see the kind of everyday smart glasses we build this practice around at AIGLAS, the official site is https://aiglas.co.uk/.

