What setup do top SwingVision power-users actually use?

By Akshay Sarode · · Workflow

From the r/10s 'do you record everything?' thread: real tripod heights, battery routines, naming conventions, and Wi-Fi rules from heavy users.

The r/10s thread "SwingVision users — do you record everything?" is one of the most useful real-workflow documents in the tennis-AI internet. Comments from users who've been through hundreds of sessions reveal a pattern: the people getting the most out of SwingVision (and any tennis AI tool, AceSense included) aren't the ones recording every minute. They're the ones with a system. Specific tripod heights, deliberate battery routines, strict file naming, and a rule about which sessions are worth uploading. This post pulls those patterns out, attributes them to the thread, and translates them to a workflow you can copy whether you're on SwingVision today or any tennis-AI app.

TL;DR

  • Don't record everything. Pick 1–3 sessions a week.
  • Tripod at 8–10 feet, dead center behind baseline, locked tight.
  • Phone airplane mode + Wi-Fi, 1080p (not 4K), screen brightness ~50%.
  • Power bank velcroed to tripod leg if you go past 60 minutes.
  • Strict naming: YYYY-MM-DD_opponent_court.mp4.
  • Upload at home over Wi-Fi, never courtside on cellular.

Rule 1: don't record everything

The most upvoted comments in the r/10s thread all converge on this: recording every match becomes its own job, and review-time scales linearly with footage. One user described accumulating 60+ hours of unwatched match video before realizing the system was broken.

The working pattern:

  • One match per week. Your highest-stakes match. Almost always recorded.
  • One drill session per week. Targeting one weakness. 20–40 minutes is enough.
  • Optional practice set. When you remember and the court has a good mounting point.

That's it. Three videos a week, max, for active power-users. Two is more sustainable.

This applies one-for-one to AceSense. Less footage, reviewed properly, beats more footage that piles up.

Rule 2: tripod placement is non-negotiable

The single biggest cause of bad analysis (any app) is bad camera placement. The thread's consensus, which matches what we see in AceSense uploads:

  • Position: centered on the court, behind one baseline. Not in the corner. Not at the net post.
  • Height: 8–10 feet. Higher is better for ball tracking. The fence is 10 feet — mount on top of it.
  • Distance: 5–10 feet behind the baseline if you have the room. Don't push the camera against the fence — you'll lose the front of the near service box.
  • Angle: tilted slightly down so the far baseline is in the upper third of the frame, not at the very top. This keeps both baselines in shot.
  • Stability: locked. A windy day with a flexible tripod kills shot detection and bounce localization.

If the court has no fence (clay clubs, public parks), a tall tripod or monopod works — see our equipment guide for filming a tennis match.

Rule 3: phone settings before you press record

Phone behavior on the court is where most "the app didn't pick up half my shots" complaints come from. The setup that works:

  • Airplane mode ON, Wi-Fi OFF (or on if you have court Wi-Fi). Eliminates random notifications, calls, and silent radio activity that drain battery and can interrupt recording.
  • Do Not Disturb ON. Belt and braces.
  • Resolution: 1080p at 30 fps. Not 4K. The AI doesn't get smarter from 4K; the file just gets four times bigger and harder to upload. SwingVision's docs, AceSense's docs, and PB Vision's docs all converge on 1080p.
  • Screen brightness 50%. Saves battery. You're not staring at the screen anyway.
  • Auto-lock disabled. Sometimes the camera app handles this; sometimes it doesn't.
  • Storage check. A 90-minute 1080p video is roughly 4–6 GB. Make sure you have it.

Rule 4: battery management

Two viable patterns, both surfaced repeatedly in the thread:

Pattern A — power bank on tripod. Velcro a 10,000 mAh power bank to a tripod leg. Short USB-C cable to the phone. You can record for 4+ hours.

Pattern B — single battery, optimized. Modern flagship phones (iPhone 13 and up, Pixel 6 and up, Samsung S22 and up) will record a 90-minute match at 1080p with around 25–35% drain if the rest of the settings above are right. If you start at 80% and the match goes 2 hours, you're cutting it close.

Don't trust pattern B if you're recording back-to-back sessions.

Rule 5: a naming convention you can stick to for years

Three years from now you'll want to find "the match where I first beat Marco." If your filenames are IMG_4738.MOV, you won't. The convention that works:

2026-02-14_marco_clayhall_set2.mp4
  • Date first — sorts correctly in any file browser.
  • Opponent or session type — searchable.
  • Court / location — surface and lighting affect AI accuracy; you'll want to compare like-for-like.
  • Set or session number — disambiguates when you record twice in a day.

Power-users in the thread mentioned spreadsheets tracking match → file mapping. That's overkill. The filename is the spreadsheet if you write it correctly.

For AceSense specifically: the filename you upload becomes part of the session metadata, and the admin/result paths are derived from session IDs, so a clean filename is also a clean record.

Rule 6: upload at home, over Wi-Fi

Courtside cellular uploads of a 5 GB video are slow, expensive, and prone to interruption. The reliable pattern:

  1. End the recording.
  2. Pack up the tripod.
  3. Drive home.
  4. Plug phone in, open the app over home Wi-Fi, queue the upload.
  5. Walk away.

Both SwingVision and AceSense let you queue uploads in the background. AceSense uses Firebase Storage with a chunked-upload pattern, so a dropped Wi-Fi connection mid-upload resumes cleanly — but starting on Wi-Fi is still the right call.

Rule 7: review within 48 hours, or it doesn't happen

The thread mentioned this in passing and our own usage data confirms it: if you don't open the analyzed report within 48 hours of upload, you almost never will. The match memory fades. The drill you were testing fades. Block 20 minutes within two days of any session you record. Otherwise the whole pipeline is a hobby.

Bonus: things power-users stopped doing

A few habits the thread agreed were not worth the effort:

  • Recording warmups. No useful data. Skip the first 5 minutes.
  • Recording every changeover. AI ignores them, but file size doesn't.
  • Hand-correcting every misclassified shot. SwingVision lets you re-label shots. After about 30 corrections per match you stop. AceSense's accuracy methodology goes into where the misclassifications actually come from.
  • 4K everywhere. Already covered, but worth repeating.

Translating to AceSense

The recording side is identical. Where AceSense diverges:

  • Upload goes to Firebase (region: europe-west1).
  • Analysis runs on RunPod GPU and returns a PDF coaching report with shot-by-shot annotations.
  • No Apple Watch dependency, so the watch-on-wrist part of SwingVision's setup goes away.

If you've built a SwingVision workflow on iOS and you want to add Android players or remove the watch, the recording rules transfer. Just point the upload at AceSense.

Source

The base thread for this post: r/10s "SwingVision users - do you record everything?". It's worth reading the full comments — there are some specific phone-mount product recommendations we didn't cover here.

Related reading