러닝 기록을 영상으로 남기는 법

What a picture adds to the numbers

After a run, the figures on your wrist fade quickly. A 5:12 pace and an average heart rate of 152 are accurate, but they do not tell you which streets you took or where it got hard. Replaying the route as video lets you check where the climb was and where you sped up, and it is easier to show a friend. This article covers preparation, privacy and sharing habits that work with any tool, then walks through making a video with RunVue.

The data a video needs

The minimum is a time-ordered list of position points; heart rate and elevation add more to display. Data usually arrives by one of three routes.

GPX is a light-weight XML format for exchanging GPS data (waypoints, routes and tracks) between applications. It is a plain text file with latitude, longitude and time listed in order, which makes it easy to inspect and edit, but it also means the exact positions and times travel with it, which matters for the privacy section below.

GPS accuracy pitfalls

Smartphone GPS is reasonably accurate under open sky, but accuracy worsens near buildings, bridges and trees because of signal blockage and reflections (multipath). In a video it shows up as:

• A jumpy start. Leaving before the signal settles draws the first tens of metres wrongly. Wait under open sky until it locks.
• Tall buildings, tunnels, underpasses. The route shifts a block or cuts through buildings. Road matching in a video tool helps but is not perfect.
• Pause and resume. A straight line can appear between the stop and restart points.
• Battery saver. Lower update frequency rounds off corners.
• Indoor or treadmill runs. No route, so nothing to render.

No editor can fully rescue poor source GPS. If a video looks odd, inspect the raw route on a map before blaming the app.

Privacy: handle the start and end

A run video carries more specific location than a photo. A full route can hint at where you live and when you move. A loop that starts and ends at your door shows your door.

• Move the start and finish. Starting from a nearby park or a different street is the surest fix.
• Use a tool that can hide route ends. Some services mask the start and end; check first whether yours does.
• Narrow the audience. Post only non-identifying courses publicly; send home-area courses to friends.
• Do not post in real time. Posting during or right after a run says you are there now. Wait.
• Check for place names and signs in the video, including map labels and the closing text.
• Share an edited GPX, not the original. It holds exact coordinates and times; trim the start and end first.
• Heart rate and calories are health data too. Think before adding them to a public video.

Choosing format and length

Phone-first social video is vertical (9:16), and RunVue produces 9:16 video. Exact resolution and length rules change, so check each platform's help page right before uploading. One verified fact: YouTube's help describes Shorts as short videos up to 3 minutes long. I do not assert figures for other services here.

Shorter is more likely to be watched to the end. A one-hour run does not need a one-hour video; variable speed that skips straight sections and slows on the interesting parts works well. There are three viewpoints. Sky view shows the shape of the whole course (a heart-shaped route, say); a chase third-person view keeps a sense of direction; first-person is immersive but can cause motion sickness if it runs long, so keep it short. For overlays, pace, distance and time, and a minimap are plenty.

Making one with RunVue

RunVue, made by SETLOG, is an iPhone app that turns an already-recorded outdoor run into a short 3D replay. It does not measure runs itself, so your watch or another running app must record first.

Step 1. Pick a run or import a file

On first launch it asks for read access to workouts in the health app. Per the app's documentation it reads only what the video needs (workouts, routes, heart rate) and does not collect date of birth or weight. Choose a run from the list, or import a GPX or FIT file via the share sheet or Files for devices that do not write routes to the health app. With no runs yet you can try the sample run. A run marked as having a route is eligible for a route video.

Step 2. Set options and make a preview

On the remix screen choose camera, HUD language, music and units, then make the preview. Free use includes the Navi camera, a 1x summary video and the pace and heart-rate waveform; speeds from 2x to 60x, the Cinematic and Calm camera presets, and camera height and zoom are subscription (Pro) features per the app. If iOS Reduce Motion is on, the Calm preset is free. Video length is fixed at 22, 27 or 32 seconds depending on distance, and rendering happens on the device, so older phones take longer. Keep the app in front and plugged in while it renders.

Step 3. Check the result and keep it

The video opens in a chase third-person view, switches to first person at highlight sections, and ends in sky view with the whole course and a summary. Finished videos collect in the library; save to Photos or send through the share sheet.

Last check before sharing

A RunVue video shows the full route from start to finish. There is no route-masking feature, and the app gives a notice about home exposure just before sharing. So the methods in the privacy section, moving the start point and narrowing the audience, are up to you.

RunVue's limits, honestly

• It does not record runs. It imports from the health app or GPX and FIT files only. For live coaching, use another app.
• No route hiding. You manage who sees home-area courses.
• The watermark and map credit are always present, free or Pro. The OpenStreetMap credit is included at the start and end of the video under the data licence.
• Map detail varies by region. It is OpenStreetMap-based; where building heights are missing, it draws an average height.
• It may need a connection while map tiles download; the route itself is designed to stay on the device.
• Android. This description is for iPhone. Availability and features on Android may differ; check the Google Play listing.
• Some camera and speed options need a subscription.

Full usage is in the RunVue guide; for in-run pace coaching see the IntervalRunner guide.

From recording to posting: a checklist

Once you have made one, the order becomes second nature, but at first each step has something to miss. Walk through this sequence.

1. Before the run. Pick outdoor run in the workout app and confirm location permission is allowed. Wait under open sky until the signal locks.
2. Right after. Save the workout and confirm the route reached the health app. Watch sync can take a while.
3. Before making. Scan the route on a map for jumps, and decide here whether the start and end are near home.
4. After making. Watch the whole video and check that place names, streets near home and heart rate are fine to make public.
5. Posting. Choose the audience and, where possible, post some hours after the run.

With this order, when a video looks wrong it is easy to tell whether the cause is data or tool. Collecting videos of the same course at intervals also lets you compare seasons and pace at a glance. But repeatedly publishing the same course makes it clearer that it is your daily route, so the more a local loop repeats, the narrower the audience should be.

Common mistakes

• Starting before GPS locks, so the first stretch is a straight line
• Posting a route from your home publicly
• Packing in so many stats the video is unreadable
• Stringing together long first-person scenes that make viewers queasy
• Sharing a raw GPX file without editing

Sources and further reading

1. TopoGrafix, GPX: the GPS Exchange Format (https://www.topografix.com/gpx.asp)
2. YouTube Help, YouTube Shorts (up to 3 minutes) (https://support.google.com/youtube/answer/10059070)
3. RunVue guide (app features per project documentation and the App Store description)

FAQ