/**
 * Recording-relative clock for the timeline.
 *
 * Built-in capture layers timestamp events with {@link now} rather than raw
 * `performance.now()`, so event times read as "ms since recording started"
 * (the first event is ~0) instead of "ms since the app page loaded" — which is
 * also meaningless to the panel, an iframe with its own time origin. The origin
 * is re-zeroed on each rising edge of recording via {@link resetClock}.
 */
/** Re-zero the clock; called when recording transitions off → on. */
export declare const resetClock: () => void;
/** Milliseconds since the last {@link resetClock}. */
export declare const now: () => number;
/**
 * Convert a recording-relative time (from {@link now}) back to a
 * `performance.now()` value, i.e. milliseconds since `performance.timeOrigin`.
 * Chrome DevTools' `console.timeStamp` expects that timebase.
 */
export declare const toPerfTime: (t: number) => number;
/**
 * The inverse of {@link toPerfTime}: a `performance.now()` value, the clock
 * app code can read, on the recording's clock. Custom events go through it.
 */
export declare const fromPerfTime: (t: number) => number;
//# sourceMappingURL=clock.d.ts.map