Skip to content
DarkBeaconHelp
← All guides

DARKBEACON GUIDE

Understand preview, save, and sync

Distinguish a live effect, persistent device storage, local profiles, and cloud sync before you disconnect or overwrite settings.

On this page

Applies to: DarkBeacon App

What you will understand

A current session (A previewed state that is active while the device remains connected but may not be stored permanently) is the state you can preview while a device is connected, but it may not be stored permanently. This article is the canonical model for preview, device storage, local content, and account content.

Applies to

Core explanation

  1. A visible change is not automatically persistent. Treat an immediate device change as a live preview until the App confirms otherwise.
  2. Save to device (Store the current settings on the device so they remain after the App disconnects or power is restored) controls power-cycle retention. After explicit success feedback, the device should keep the setting when the App disconnects or power returns.
  3. A local profile (A reusable set of settings stored by the App on the current computer) is reusable content on the current computer. It can differ from the active onboard state.
  4. Cloud sync (Upload or retrieve eligible account content over the network after signing in) requires an account and network. A current cloud copy does not prove that the device has been saved.
  5. Cancel and recovery return to the last confirmed state. Cancel, reload, or reapply a known saved profile before choosing an overwrite direction.
  6. Conflict handling protects current work. App 1.16.206 uses one conflict path for eligible profiles, macros, lighting, and sound content. Non-overlapping macro changes can be combined automatically; overlapping edits still require a user decision.

Limits and cautions

When two computers or profiles edit similar content, preserve both copies and compare target device, modification time, and preview result before overwriting. A conflict disappearing after an automatic merge does not save the merged result to the device.

Use Create and move profiles for profile work, Understand advanced key behaviors for advanced-key save expectations, and Sign in and use cloud sync for account conflicts.