Compare the evidence chain
Ask what source evidence is captured, how the operator inspects it, which adjustments are review-only, and how the final image is exported or shared.
The comparison method
Before choosing a vendor, compare the race-day decision itself: what evidence the operator can trust, how the team recovers from imperfect capture, and what support turns a camera into a working finish-line system.
Method
Use these five questions before diving into vendor pages. They keep the conversation focused on buying fit instead of isolated specifications.
Ask what source evidence is captured, how the operator inspects it, which adjustments are review-only, and how the final image is exported or shared.
Ask what happens if a trigger is missed, capture starts late, the image is dark, power drops, or evidence needs to be recovered after the event.
Ask how many screens, stations, operators, races, cameras, approvals, and exports the team can manage without slowing the result.
Separate camera body, software, licenses, accessories, delivery, onboarding, first-event support, and future product scope before comparing prices.
Ask what the vendor will help you prove before the first real race day: finish-line angle, light, connections, operator practice, and evidence export.
Lion Timing: TCXO timing with optional GPS timing: local clock stability plus satellite time anchoring for setups where start and finish need a shared time reference.
Buyer question: Ask how the start moment reaches the finish clock, how cable or radio delay is handled, and whether GPS/GNSS timing is built in, optional, or external.
Lion Timing: In development: calculator lets buyers enter finish-line speed and see matched line rate, millimeters per line, and when 5,000 lines/s gives quality headroom.
Buyer question: Ask each vendor how they recommend scan rate for your sport, speed, distance, and lighting.
Lion Timing: RAW-first/source data recording with JPEG export for sharing and review.
Buyer question: Ask whether the original sensor data is recorded, accessible, and separate from review/export images.
Lion Timing: Sensor-agnostic architecture: the sensor is selected for the job, while capture, timing, RAW evidence, backup, and workflow are designed as the platform.
Buyer question: Ask whether the architecture is fixed around one sensor, or can adapt as sensor technology improves. Compare the whole evidence chain, not only the sensor or pixel count on the spec sheet.
Compare product maturity, supported sports, image evidence, vertical resolution, line rate, low-light handling, timing source, trigger inputs, setup, recovery, export workflow, scoreboard/results outputs, operator training, support model, package scope, and approval requirements.
Line-rate questions
Line rate is about matching the finish-line speed, not winning a spec-sheet contest. Use these questions for every vendor, including Lion Timing.
Ask whether the advertised rate is real optical exposure or software-generated/interpolated lines.
Ask what the image looks like at the advertised maximum under realistic light.
Ask how the vendor recommends scan rate for your sport, speed, distance, and lighting.
Ask about line resolution and image quality, not just scan rate.
Ask for an unedited image from realistic evening or difficult light.
Use the right page
This main-domain Buyer Comparison Guide is the commercial starting point. Academy pages support education, but buying comparisons should begin here with criteria before vendor names.
Use this when you want to understand established ecosystems, newer systems, and elite-event benchmark systems.
Decision toolBuyer criteria matrixUse this when you are preparing vendor questions or comparing exact model, license, accessory, and support fit.
Search entranceAlternative search pagesUse these pages when you arrive through a specific alternative query, then return here for the full buying method.
Buyer questions
These questions are intentionally vendor-neutral. Use the matrix for the detailed table, and use the systems map to understand where each vendor category fits.
Compare product maturity, supported sports, image evidence, vertical resolution, line rate, low-light handling, timing source, trigger inputs, setup/alignment, backup/recovery, export workflow, scoreboard/results outputs, operator training, support model, total cost/package scope, and approval requirements.
Start with criteria. Alternative research is useful after you know what your finish line, operator team, and approval workflow actually need.
Lion Timing is worth evaluating when the team wants clear finish-line evidence, direct support, pricing clarity, and a practical setup conversation. Exact technical fit should still be verified in a demo.
No. Line rate is about matching object speed, not winning a spec-sheet number. Higher rates reduce exposure time and cost light. For racing speeds, 5,000 lines/s gives practical headroom, especially when moderate oversampling and aspect correction are used. The better comparison is the evidence image: ask what is optical, what is interpolated, and what the image looks like in realistic light.
Every system looks good in ideal daylight. Ask for dusk, floodlight, indoor, or difficult-light examples that match your event. Also ask what line rate was used, whether the image is unedited, and what happens when gain is needed.
The zero test fires the start gun on the finish line. The trigger defines 0.000, and the muzzle flash appears optically on the finish line at the same instant. In the image, the first flame should read 0.000. It is a vendor-neutral way to check timing alignment on site instead of relying only on brochure claims.
Avoid unsupported competitor claims, unconfirmed technical numbers, and headline prices without package scope. Ask for the exact model, license, accessory, support, and delivery plan.