SOFTWARE AND APP

The software and app use the same rider, vehicle, setup and run workflow. Read the available controls before following a procedure.

Use "Home" to manage runs, vehicles, leverage curves and laps. Open a run to read charts and notes; open "Device" to configure a connected acquisition unit and download its recordings.

This manual quotes the shared control labels. Menu commands give a direct route to tools; on a touch interface, use the corresponding visible control or action menu.

Local recordings are stored in the managed run library. Vehicle settings and dated setups belong to rider profiles; the reusable lap and leverage libraries are shared across profiles on this installation.

1. 01
   Open the website’s "Software & app" page and download the build offered for your platform.
2. 02
   Run the installer and follow the platform’s installation prompts.
3. 03
   Open BYB and sign in with your BYB account.
4. 04
   Create or select a rider profile — The rider profile.

The account identifies the person using BYB Cloud. A rider profile identifies whose sessions are stored in the library: a professional’s account can contain several riders.

After a successful sign-in, local work can continue offline using the saved account access. Reconnect to refresh account and cloud status; an unavailable allowance is shown as an em dash, not as a confirmed zero.

Use these shortcuts to return to the detailed procedures without repeating device instructions.

The connected unit’s identity and status appear on "Device". Use Send the rider and vehicle for rider and vehicle, Configure the connected device for acquisition settings, Live data and SAG for response/SAG checks and Download into the run library for recordings.

Find recordings under the correct rider on "Home". Use Find, import and organise runs for imports and filtering, I cannot find my runs after downloading for routing problems and Correct a run’s assignments to correct assignments.

Open a run to access analysis views. Use Cursor, zoom and shared selection to choose the interval, Calibration of recorded runs to check references and Summary and run setup to preserve session context.

Use "Help" → "User manuals…" to open the relevant manual, or "Show the guided tour" for the introductory workflow. Hardware buttons, mounting, calibration captures and LED meanings belong in that product manual; unresolved problems go to Contact support.

Use the library’s export command when transferring a run — Export a portable BYB run. Reimporting the same recording is handled by the library’s duplicate checks; renaming a file is not a way to create a new measurement.

Add a day note beside the dated run group to record conditions and session context once. Use the individual run’s "Setup" for information that applies only to that recording.

A manual library entry can record a session without an acquisition file. Its "MANUAL" badge distinguishes it from measured recordings; adding notes does not create channels, GPS data or lap times.

Day notes travel with the relevant runs when sharing a day. Review them before sending a session to another account — Share a run or session.

Use "Apply" where a settings page offers draft changes; some controls take effect immediately. Metric/imperial display preferences change presentation, while input fields retain their stated units unless they provide their own unit selector.

Library deletion and device deletion are separate actions. Check the run’s menu: "Delete locally (keep in cloud)" and "Remove from cloud (keep on this computer)" state which copy will remain.

Use the library’s "Trash" view for recoverable local deletions and review its controls before permanently removing entries. Deleting a rider profile is a wider operation; back it up first — Back up a rider profile.

A rider profile owns that rider’s run library, vehicles and setup history. Selecting a profile changes which rider’s sessions you are browsing; it does not move recordings from another profile. Send the intended rider to the acquisition unit before the session so downloads can reach the correct library — Send the rider and vehicle.

1. 01
   Use "Add a profile" on "Home", or "Profile" → "New Profile…".
2. 02
   Enter a recognisable rider name and complete the rider details you need.
3. 03
   Save the profile and select it before adding vehicles or preparing a session.

Weight, height and rider level provide context for the tools that use them. Keep weight consistent with the input’s definition, including riding equipment where requested.

Use "Profile" → "Edit Profile…" to correct details. Renaming a profile keeps its identity; creating a second profile with a similar name creates a separate place for runs.

1. 01
   Open "Home" → "Garage" and add a vehicle.
2. 02
   Enter its identity and select the appropriate vehicle type.
3. 03
   Complete the geometry for each suspension channel in use, and the wheel-size/magnet values needed for speed measurement.
4. 04
   Save the vehicle and check its required fields before analysing a recording.

Sensor length

The measuring range of the installed sensor. It converts the recorded sensor signal into displacement.

Suspension stroke

The usable stroke of the suspension component. It is the reference for suspension travel in percent.

Wheel travel

The wheel’s usable travel. With the assigned leverage, it provides the wheel-travel reference.

Leverage curve

The relationship between suspension movement and wheel movement. Assign a matching saved curve where available — What a leverage curve does.

Wheel size and magnets

The wheel dimension and magnet count used by the speed sensor. Check the field’s stated units; a wrong wheel reference changes the calculated speed and distance.

Enter the values for the hardware actually installed. Changing a display unit does not correct an incorrect sensor length or stroke.

The vehicle’s "Setup sheet" timeline records what was fitted and adjusted, and when it changed. Each entry is the vehicle’s setup from its effective date and time until the next entry. A run is matched to the setup in force when its recording started, even if you download it later.

Start with an initial entry describing the settings you want to track, such as pressures, adjusters and component details. Add a new entry for each physical change, using the actual change time; the sheet saves field edits as you make them. Record the result and rider observations with the run so you can compare an adjustment with what happened on the course.

Example: the initial setup becomes effective at 10:00, and an adjustment is logged at 10:30. A run started at 10:25 receives the initial setup; a run started at 10:40 receives the adjusted setup. The download time does not decide which setup is used.

A curve stored in "Leverages" is available to choose; saving the curve there does not assign it to a vehicle or setup. Replacing a linkage or curve is a setup change to log — The Leverages library.

Assign the fitted leverage curve to each relevant suspension (if any), with the period when it was installed. The "Leverage" → "Change…" controls use "From" and "To" dates; an empty "To" means it remains fitted. This keeps a later linkage change from standing in for earlier sessions; review the treatment of earlier runs with no stored leverage before applying.

Add custom fields to the setup sheet for settings your vehicle needs beyond the standard fields. Use a consistent name and unit so later entries can be compared.

Use "Template" → "Export sheet template…" to reuse the field layout, and "Import sheet template…" to bring it into another sheet. Review the field changes before "Apply": a sheet template defines fields; it does not replace dated setup values.

1. 01
   The download identifies the rider recorded by the device, unless you explicitly choose a download destination profile.
2. 02
   The vehicle identity is matched to a vehicle in that rider’s Garage.
3. 03
   The software selects the most recent setup whose effective time is at or before the recording start.
4. 04
   The run stores a copy of that setup and its geometry for later analysis.

Stable recorded identities keep matching after a rename. Where a recording has only a name, the software uses the available name match; an unknown rider can be placed in "Guest" for you to resolve.

A matched vehicle with no setup at the recording time uses its available baseline geometry, without inventing a dated setup. Check "No setup" and missing-value prompts before drawing conclusions about suspension settings.

"Summary" collects the available measured statistics. Check its selection-synchronisation state before reading a value as the full-session result.

"Setup" holds the run’s rider/vehicle context, geometry, setup values, session information, score and observations. Fill it in while you can still identify what changed and how the vehicle felt.

Press "Save" to save the run’s setup, notes and staged assignments; "Discard" abandons the unsaved draft. Check the saved status before switching runs.

The save dialog offers the choices that apply to the current assignment. Later timeline edits do not silently replace the stored snapshots on other imported runs — Custom setup fields and corrections.

Leverage converts measured suspension travel into wheel travel. A varying curve represents the linkage through its stroke; a constant relationship uses the supplied stroke and wheel-travel values.

Use the curve that belongs to the actual vehicle and linkage. Store reusable curves in The Leverages library, then assign them in the dated Setup sheet for future runs or in the run’s controls for a specific analysis.

When no measured curve is assigned, the available suspension stroke and wheel travel define the constant conversion. Complete both values in the vehicle geometry and check the displayed reference.

This approximation does not reproduce a progressive or regressive linkage. Use a verified measured curve when the difference matters to the analysis.

A custom curve uses paired suspension-displacement and wheel-displacement measurements from the same vehicle. Measure both from a consistent unloaded reference across the usable range.

Obtain or measure the relationship using a safe workshop procedure appropriate to the suspension; dismantling and installation instructions belong to the relevant hardware documentation.

1. 01
   Open "Home" → "Leverages" and choose "New", or open a saved curve.
2. 02
   Enter the measured suspension and wheel-travel pairs in the table.
3. 03
   Use "Interpolate" to preview the fitted relationship.
4. 04
   Inspect the shape and check questionable measurements before applying it.
5. 05
   Complete the curve’s "Details" and save it.
6. 06
   Assign the saved curve to the appropriate channel in the vehicle’s dated setup — The Setup sheet timeline.

A manufacturer-supplied curve may be usable without exposing its editable points. Use the available assignment controls and keep its supplied identity.

"Home" → "Leverages" stores reusable curves across rider profiles. Search, filter and open the saved curves; use "Import" for a supported curve file or "Available online" for the offered catalogue.

Use "Export all…" or the curve’s export action to keep transferable copies. Deleting a reusable curve is a library operation, not a substitute for changing a vehicle’s dated curve assignment.

User time

Times calculated from GPS crossings of gate lines you draw on the map. Use this for recordings without external triggers or for an extra segment.

Trigger time

Times from external-trigger events recorded by the unit. Start, Finish, Start/Finish and numbered splits identify the timing roles.

An open lap has separate start and finish gates; a closed lap uses one start/finish gate. Split gates divide the course into sections so a total-time difference can be traced to where it occurred. For GPS timing, the gate lines must cross the recorded route in the intended direction.

Reuse the same gate set when comparing repeated runs on a course — The Laps library. Changing a gate changes the section being measured, so a different time may reflect a different boundary rather than a change in performance. Missing GPS crossings or trigger events can leave a lap incomplete; check the timing warnings before comparing results.

In Trigger time, use "Assign triggers" to override a recorded role for this run when required, or choose automatic role handling. Read missing-trigger and topology warnings before comparing lap times.

"Home" → "Laps" stores reusable User-time gate sets. Add location, track and extra information so similarly named courses remain distinguishable; import or export .bybLap files with the library controls.

Load the same gate set for repeated comparisons on the same course. If the saved gates belong to another route, check the warning and their intersection with the GPS trace.

"Save" updates an existing library lap; "Save as new" keeps the original and adds another set. Saving gates and applying gates to a run are distinct actions.

Open "Home" → "Trends" to read activity and available run statistics over the offered date ranges. Filter by vehicle when you want one setup history rather than the whole rider’s activity.

Use setup markers to relate changes to the dated timeline. Missing metrics appear as gaps or em dashes; they are not zero measurements.

Library trend statistics can exclude stopped time, while a run’s "Summary" may describe the full recording or your current selection. Check the stated scope before expecting those figures to match.

1. 01
   Enable connection mode using the instructions for your acquisition unit.
2. 02
   Join the unit’s Wi-Fi network and keep the connection when your platform warns that it has no internet.
3. 03
   Open "Device" in BYB and wait for the product and connection status to appear.
4. 04
   Check that the device shown is the unit you intend to configure.

Device buttons, LED patterns, mounting, pairing gestures and resets stay in the device manual. Use What determines availability to check which software controls your connected product supports.

1. 01
   Select the rider profile and the vehicle intended for the session.
2. 02
   Open the rider/vehicle controls on "Device" and load or select those saved identities.
3. 03
   Send the configuration using the control identified in What determines availability.
4. 04
   Wait for the operation to finish and check the rider and vehicle shown on the device page.

Choosing a profile in "Home" or saving a vehicle in "Garage" does not update the unit. Repeat the send operation when a different rider or vehicle will use it.

Sending identities prepares future recordings for routing. It does not move recordings already in your library; correct those with Correct a run’s assignments.

Open the relevant "Device" category, change the supported settings, and use its send/apply control. Wait for confirmation before leaving the connection or starting a session.

Open "Device" → "Live data" to check supported sensor values, IMU readings and GPS status before recording. Move each installed sensor and check that its channel responds.

For V3 Pro SAG measurements, vehicle selection, the temporary zero and Suspension/Wheel references, follow Live data and SAG in the Telemetry manual. Live SAG does not calibrate recordings; calibration of recorded runs is a separate workflow.

Use the device manual to enter its supported USB data mode before connecting. Open the software’s USB import controls and select the recordings to bring into the library.

USB imports also use rider routing and can place unknown riders in "Guest". Check the imported runs’ assignments and open them before removing their device copies — How rider, vehicle and setup are matched and I cannot find my runs after downloading.

Repeat the preparation checks when rider, vehicle, settings or sensors change.

Use the acquisition unit to start and stop recordings. For readiness, buttons, GPS fix and LED states, use Telemetry quick start or Chrono quick start.

When changing a physical setting between runs, note when the change took effect. Add that change to the setup timeline before importing the next batch, or check and reassign those runs afterwards — The Setup sheet timeline.

1. 01
   Reconnect to the device and open its "Runs" page.
2. 02
   Select the recordings you want to keep.
3. 03
   Leave "Download into:" on "Auto — by rider" unless this batch deliberately belongs to a specific profile.
4. 04
   Press "Download selected" and wait for completion.
5. 05
   Open "Home" and inspect the imported run groups under their matched rider profiles.
6. 06
   Open at least one downloaded run and check its data and assignments.

An explicit profile in "Download into:" overrides automatic rider routing for that batch. Use it deliberately; leaving the wrong destination selected can put the next rider’s runs in the wrong library.

"Download to folder…" saves a separate file copy when needed. Normal library downloads are managed by BYB; the file-folder destination is a different action.

1. 01
   Find the run in the library, including "Guest" if the rider was not recognised.
2. 02
   Use "Move to profile…" to place it under the correct rider.
3. 03
   Use "Assign vehicle" to select the vehicle from that rider’s Garage.
4. 04
   Use "Assign specific setup…" to choose a saved setup, or "Latest / at run time" to resolve the dated timeline.
5. 05
   Open the run and check the stored geometry and notes after the reassignment.

A run’s "Setup" selectors can also stage a vehicle or setup change. Press "Save" to commit the draft; changing a selector alone is not a completed assignment.

Use "Create profile from…" on an unknown recorded rider when that name should become a real rider profile. Moving an individual run to a profile does not teach automatic routing a new recorded name.

1. 01
   Check the selected rider profile and clear library search or filters.
2. 02
   Check the profile sent to the acquisition unit before the session.
3. 03
   Look in "Guest" for an unrecognised rider, and in any profile selected explicitly in "Download into:".
4. 04
   Move the runs to the correct rider and assign their vehicle and setup — Correct a run’s assignments.
5. 05
   Send the correct rider and vehicle before the next session — Send the rider and vehicle.

The currently selected profile is not necessarily the download destination. Normal downloads follow the rider recorded by the unit; the vehicle and setup are resolved within that rider’s library.

Open the run’s calibration control or the "Calibration" menu to check the active sources. A recording can have one sensor-calibration source and a different IMU-calibration source.

Manual sensor zeros override the chosen Hardware/Automatic baseline for the edited channels. Clearing the manual zeros returns those channels to the selected baseline; a disabled Hardware option means that this run has no usable hardware calibration.

1. 01
   Open "Stack view" or "Suspension view" and find the channel to correct.
2. 02
   Locate a sample where that sensor is at the known zero reference.
3. 03
   Open the chart’s context menu at that sample and choose "Set Zero Here" or the corresponding channel’s "Set Zero" action.
4. 04
   Check the recalculated chart and the active "Manual" calibration state.

For suspension travel, choose a known unloaded/full-extension reference, not the rider-loaded SAG position. For brakes or another supported channel, use the actual neutral reference for that measurement.

Use "Clear Zero" for an individual channel, or "Clear manual sensor calibration" for the manual sensor calibration. Clearing sensor zeros does not remove IMU calibration.

1. 01
   Check the unit’s recorded mounting orientation and find a stationary part of the run.
2. 02
   Select IMU "Hardware" to use a valid device calibration, or "Automatic" to find a stationary reference in this recording.
3. 03
   For a custom reference, open the chart context menu at the appropriate stationary sample and choose "Set IMU level here".
4. 04
   Check the reframed accelerometer and gyroscope traces against the known vehicle orientation.

Use "IMU Z axis points up" to match the orientation expected by the calibration. A reference sampled while the vehicle is moving or at an unintended tilt can distort later readings.

"Remove IMU calibration" and the IMU source controls apply to the IMU group only. They do not clear the suspension or other sensor zeros.

Reopen the run after calibration and check that the expected sources, values, notes and assignments are present.

Use the library’s export command to transfer a run, or create a complete library backup before moving to another computer — Export a portable BYB run and Back up a rider profile.

Opening a run creates a workspace for its recorded channels, measured statistics and saved context. Open a recording from the selected rider’s "Home" library, or inspect an external file with "File" → "Open Run…". Importing is the separate action that adds an external recording to the managed library — Find, import and organise runs.

A cloud-only library entry needs "Pull from cloud" before its recorded data can be analysed. Use the library’s export command when transferring a run — Export a portable BYB run. Check the run’s rider, vehicle and setup before using its results.

"Open in new window" gives a run its own workspace. Comparison links several recordings against a common reference — Compare multiple runs. Separate windows alone do not align their recordings.

Time or distance

Choose the horizontal axis supported by the view. Distance depends on usable movement data.

Suspension or wheel

Suspension is movement at the measured component. Wheel applies the assigned leverage or the available stroke-to-travel conversion.

Percent or millimetres

Percent uses the relevant full travel as its reference; millimetres gives displacement. Check the vehicle geometry before switching between them.

Selection synchronisation

When enabled on a view, its statistics follow the selected interval rather than the whole run.

A display choice changes the way the data is shown. It does not change what the device recorded or replace calibration — Calibration of recorded runs.

Available tabs depend on the recording and product — What determines availability. Use the workspace’s hide/show controls when you need more room for charts.

"Dashboard" gives an overview of the loaded run’s measured behaviour. Its cards group available measurements, including suspension position, compression and rebound statistics. Use it to identify which aspect of the run deserves closer inspection; only groups supported by the recording are shown.

Each value belongs to a channel, a statistic and a unit. Suspension travel describes component movement; wheel travel includes the assigned leverage, and percent expresses travel against its configured range — Units, reference and selection. Compare values only when their references and units match.

"Sync to selection" makes Dashboard and "Summary" describe the selected interval; otherwise they describe the whole run. A statistic summarises that scope without showing when individual events occurred. The mini-bars help compare displayed values; their length is not a target or a recommendation.

The shared cursor represents one moment in the run, linking the recorded channels with the map and any synchronised video. A selection represents an interval; zoom makes that interval easier to inspect without creating a new recording. Use the cursor to understand an event and the selection to understand the surrounding behaviour.

A view’s selection-synchronisation state determines the scope of its statistics. With synchronisation enabled, they describe the selected interval; with it disabled, they continue to describe the full run even while another chart is zoomed. A change in scope can change a result without any change to the recorded data.

The map shows the recorded GPS route and the position associated with the chart cursor. Use the route-colouring control to relate a recorded value to its location on the course.

The elevation view adds vertical context to the route. Missing or unreliable GPS reception limits map position, distance, elevation and GPS-derived timing; it is not repaired by changing suspension calibration.

Use the "Elevation" / "Video" selector to display a linked video in that area — Link and align a video.

"Stack view" aligns available channels on a common horizontal axis. Use it to see the sequence between movement, braking, speed and IMU events recorded by the unit.

"Suspension view" lets you inspect the corresponding traces in more detail. Choose the visible channels, travel reference and units before reading their values — Units, reference and selection.

Context-menu actions on the charts include supported manual zeros, an IMU reference and video alignment. Choose the action for the task; they are separate operations — Set a manual suspension or channel zero, Calibrate the IMU in a run and Link and align a video.

Position distribution

Shows how the samples are distributed through suspension travel. Check suspension/wheel and percent/millimetre references before comparing channels.

Velocity distribution

Shows the distribution of compression and rebound velocities. It complements travel usage rather than replacing it.

Stroke length

Groups compression and rebound events by movement length. Interpret event counts using the interval and available data shown by the view.

IMU distribution

Summarises recorded accelerometer and gyroscope values. The mounting orientation and calibration determine their reference.

Brake and speed distributions

Describe the recorded brake and speed channels. Distinguish GPS speed from a paired sensor’s speed.

Use the view’s zero-filter and display controls where available. Excluding zero-valued samples is a histogram filter, not the same operation as removing stopped time from a recording.

"Position vs velocity" shows how suspension velocity changes through travel. Use it alongside the time charts to locate the events behind a pattern.

"Incremental charts" show cumulative channel behaviour; "IMU charts" provide detailed accelerometer and gyroscope views. Check the active calibration if a cumulative channel drifts or an axis does not match the installation.

"Custom XY" explores the relationship between two recorded quantities. For example, speed on X and suspension travel on Y show how travel is distributed at different speeds. Available axes depend on the recording; "Time" on X instead shows how one quantity changes through the run.

Lines and Area

Connect sample pairs in recording order, helping show the path through the relationship.

Scatter

Shows individual sample pairs, helping reveal spread and unusual combinations.

Heatmap

Shows where sample pairs concentrate. A dense region means the recorded samples occur there more often, not that it is a preferred setting.

Custom XY is available with "Advanced Mode" enabled. Its "Sync to selection" state determines whether the relationship describes the selected interval or the full run — Cursor, zoom and shared selection. A relationship between two channels does not show when an event occurred unless you also inspect its time context.

Suspension axes follow the selected travel reference and units. Channels recorded at different sampling rates are paired by their nearest samples; check units and calibration before interpreting the relationship. A pattern alone does not establish its cause.

Open "Run Configuration" to inspect recorded identity, timestamps, acquisition settings, orientation, channels and timing information. Read-only fields remain read-only; editable fields depend on the file and product.

"Apply" writes the edited configuration into the recording and reprocesses it. This does not configure the acquisition unit.

"Auto-Tuning" uses measured suspension statistics to suggest the direction of adjustment for SAG, bottom-out, compression and rebound controls. Choose the rider level and available context controls that match the session.

Check whether it is analysing the whole run or the selected interval. An em dash means there is not enough usable data for that result; it is not a recommendation to leave an adjuster unchanged.

Make a deliberate adjustment, log it as a new setup and record a comparable run. Changing a display reference does not change the reference built into the tuning calculation.

1. 01
   Sign in and make sure the run is in your cloud library — Local and cloud copies.
2. 02
   Open "AI Coach" and choose "Review this run".
3. 03
   Review the data and setup that will be sent with the question.
4. 04
   Adjust the offered rider-context fields or your explanatory note if needed.
5. 05
   Enter a question about this run and press "Ask".
6. 06
   Read the answer with the measured data, then record any actual setup change in the timeline.

Measured figures on the review page come from the run; fix incorrect geometry or calibration at its source rather than describing a different number in the question. If the run changes during review, review it again before asking.

"AI Coach" needs internet and an available account allowance. The review step shows what leaves your device; sending the question is the action that uses a question allowance.

Use "Tools" → "Spring Calculator…" to estimate a coil spring rate from the inputs shown. Enter the required rider/load information, suspension dimensions, preload and desired SAG in their stated units.

Read the calculated rate and the offered neighbouring spring options as an estimate. Check the chosen spring’s compatibility and verify the installed SAG with Live data and SAG; log the actual spring in the setup sheet.

Comparison opens several recordings in a separate workspace so you can inspect their differences using the same axis and display reference. Prepare comparable runs first: check their vehicle geometry, calibration, course and setup notes.

Compare at least 2 runs, with a baseline you want to measure changes against. The first selected run becomes the reference. Keep channels, units, Suspension/Wheel references and the course section consistent, then interpret differences alongside each run’s setup and conditions.

Time alignment

Compares behaviour at the same elapsed time. Different speeds or start points mean those samples may come from different places on the course.

Distance alignment

Compares behaviour by travelled distance and enables gain/loss timing. It needs a distance source available in every run and comparable routes; equal distance alone does not prove the samples describe the same place.

Use matching gate definitions for lap or split comparisons — Lap manager: User time and Trigger time. Check the route-match indication and the selected interval before attributing a difference to an adjustment. Changes in pace, line or conditions can affect the result alongside changes in setup.

The comparison can include additional runs, including recordings from another rider’s library. Hiding a run’s traces simplifies the view without removing it from the comparison; the reference remains the baseline. Cloud-only recordings need a local copy before analysis.

Video synchronisation connects what you see on the course with what the acquisition unit measured. Use a recognisable event visible in both the video and the data to align them. Once aligned, you can inspect the vehicle’s behaviour and the corresponding recorded channels at the same moment.

Alignment offset

The camera and acquisition unit can start at different times. The offset shifts the video timeline so a frame and a recorded sample represent the same event; it does not change the measured data or the video’s playback rate.

Sync on

Playback drives the linked chart cursor. Inspecting another moment on the chart pauses playback and shows the corresponding video frame.

Sync off

The video and charts move independently, allowing you to find the matching event and establish or correct the alignment.

Link the file in the run’s video area, then establish the alignment with "Sync" off. Park the video at the chosen event and use "Sync video to this frame" at its matching data moment on a Stack or Suspension chart. Frame stepping and offset nudges help refine that match before turning synchronisation on.

The run stores the video link and alignment, not a copy of the video itself. If the file moved, use the video area to relink the actual file and verify the saved alignment.

A single alignment offset assumes both timelines keep the same elapsed time. Removing stopped time from a run shortens its timeline while the video continues, so alignment can drift after the cut. If the recording has no device gaps, returning to the untrimmed run preserves that time for synchronisation.

Auto-pause or another device recording gap is different: the unit never wrote those samples. Changing the offset cannot recover the missing data or make one alignment hold across the gap. Read the timing notice before using later frames to explain recorded events.

1. 01
   Open the run and select the interval to keep.
2. 02
   Use "File" → "Save Selection as New Run" when that action is available.
3. 03
   Name the new recording and inspect it before using it for comparison or sharing.

A selection creates a derived run; it does not turn the source recording into a shorter session. The derived run retains its source context and calibration so you can analyse the interval consistently.

"Remove stops" trims the view using the selected speed source, speed threshold, minimum stop duration and edge padding. Turn it off to restore the original view; saving a selection is the separate action that creates a derived run.

Review the resulting time axis before comparing statistics or aligning video — Missing videos and interrupted time. A stopped-time filter does not delete the underlying recording.

These actions are available only for supported products and data. Check the exported column names, units and interval before using the file in another tool; a CSV is not a BYB library backup.

Use the enabled export actions offered by your build. "Summary as Excel…", "Report as PDF…" and video-overlay export are disabled in the current shared software, so they are not completed report workflows.

To preserve an editable BYB recording, use Export a portable BYB run. For a complete rider library, use Back up a rider profile.

1. 01
   Use the run’s library menu → "Export…".
2. 02
   Choose a destination for the exported recording.
3. 03
   Open the copied run and check its notes, geometry, calibration and setup before handing it over.

BYB recordings use .byb or .chr, according to the acquisition product.

Linked videos are separate files. Include them separately or tell the recipient how to relink them — Missing videos and interrupted time.

1. 01
   Open "Settings" → "Connections".
2. 02
   Enter the other person’s BYB account email and choose "Send request".
3. 03
   Wait for them to accept, or accept an incoming request you recognise.
4. 04
   Check the connected account before sharing runs.

A connection makes that person available in the sharing controls. Receiving and importing shared runs depend on the receiving account’s access; the picker shows the available recipients.

"Withdraw" cancels an unanswered request. "Disconnect" prevents future sharing over that connection, but does not remove copies already delivered.

1. 01
   Choose the run or session’s cloud-sharing action in the library.
2. 02
   Select the intended connected recipient in the sharing picker.
3. 03
   Review the runs and any day note that will travel with them.
4. 04
   Choose "Share", or "Upload & share" if a required run is not yet online.
5. 05
   Check the displayed delivery/import status.

Sharing transfers a copy into the recipient’s account; it is not remote access to your current local file. Their delivered copy is separate from yours.

Use the offered shared-run import action to take a recording into your library. Link the sender’s rider to the profile you use for that rider, rather than mixing their runs with your own.

A cloud-only imported run still needs "Pull from cloud" before its data is available locally. Check both the import and download states.

Shared setup and vehicle snapshots travel with the run. If a linked curve or lap gate could not enter your pools, read the library notice and use "Retry" after resolving the missing item or capacity.

1. 01
   Open "Home" → "Leverages" or "Laps" and find the saved item.
2. 02
   Open its action menu and choose "Share in cloud with…" where available.
3. 03
   Choose the intended connected recipients and confirm the share.
4. 04
   Read the result for each recipient: copied, already held, waiting for room or unable to receive.

The saved curve or gate set must finish its normal cloud sync before it can be shared separately. A run’s "Upload & share" workflow is different; it does not make an unsynced library item ready for this action.

The recipient finds copied items in the library’s "Shared with me" filter, including through the notification. The same item arriving separately and with a run is recognised by its identity, so it does not create another copy.

Use "Settings" → "Account" to check online status and current allowances. "Push automatically new runs" controls automatic upload of newly imported device recordings on this installation.

Automatic upload depends on connectivity, account access and available capacity. "Guest" recordings stay local; resolve their rider before uploading.

Account status shows the current rider, storage and shared-pool allowances available to you. If an upload is waiting for capacity, resolve the indicated limit and retry; local analysis does not require deleting the run.

Use "Put all runs in the cloud" to offer existing local recordings for upload. It is distinct from automatic upload of new device imports and can skip items that cannot fit the current allowances.

Use account device management to release a computer you no longer use when a sign-in seat is needed. Reconnect after offline work to refresh cloud state and finish queued transfers.

Ride is the free base plan. Its cloud limits are 50 runs, 500 MB of storage, 100 MB per file, 1 rider profile, 3 vehicles and 2 signed-in devices. The setup, leverage and lap libraries allow 100 setup entries, 5 leverage curves and 10 lap gate sets.

Ride allows 2 sharing connections and can send runs to an eligible connected recipient. Receiving shared runs requires Professional access. These allowances govern cloud copies; local recording and analysis remain available when a cloud limit is reached.

Check "Settings" → "Account" for your current plan and remaining allowances. Compare cloud plans for the available tiers and their limits. If the plans page is unavailable, contact BYB Tech for the current options.

1. 01
   Select the rider profile to protect.
2. 02
   Choose "Profile" → "Export / Backup Library…".
3. 03
   Choose a destination with enough space and wait for a successful export.
4. 04
   Keep the completed, timestamped BYB-backup folder on separate storage.

The backup includes the rider’s recordings, Garage and setup timelines, day notes, shared lap and leverage pools, and the exported app settings.

1. 01
   Choose "Profile" → "Import Profile Backup…" on the destination installation.
2. 02
   Select the completed BYB-backup folder.
3. 03
   Review the rider identity, timestamp and content counts.
4. 04
   If that identity already exists, choose a separate copy or deliberately replace the existing profile.
5. 05
   Restore app settings only if you want to replace this installation’s preferences.
6. 06
   After importing, open a run and check assignments, calibration, curves and laps.

"Import as a separate copy" keeps the existing profile and gives the imported one a new identity. "Replace the existing profile" replaces that profile’s data with the backup.

"Profile" → "Recompute all runs…" re-reads and reprocesses library recordings to refresh their stored statistics. Use it when a correction or software change requires that refresh, rather than routinely after every download.

Stored calibrations are used during recomputation; original recordings are not rewritten by this maintenance action. Read the completion report and investigate any failed runs.

Update the software and acquisition unit through their respective controls; preserve the library before a major change.

Open "Settings" → "Updates" to check the offered software release and follow its download/install prompts. Close BYB when the installer requires it.

Open the connected unit’s device-update controls and follow the supported update procedure. The acquisition unit needs its own update; installing a new BYB software build does not update the unit automatically.

Use Telemetry updates or Focus maintenance for the product’s preparation and update instructions. For Chrono, open Device > Maintenance > Firmware update and follow the on-screen prompts.

Contact info@bybtech.it with the software/app version, acquisition product, connection status and the steps that reproduce the problem. Include the relevant message and a screenshot where it helps.

Use "Help" → "Report a Problem…" to package the available diagnostic information and open the prepared email draft. Review the report and attachments before sending; "Open Logs Folder" gives access to the saved logs when support requests them.

For a recording problem, preserve the original run before making corrections. Use the library’s export command and share the exported run through the support route requested by BYB, along with the rider, vehicle and setup you expected — Export a portable BYB run.