Play endauto.wav before transition.mp3 and run client timers independently

[Copilot]

Two changes: (1) Play endauto.wav before transition.mp3 at end of autonomous period, (2) Client timers should start synchronized with host but run independently without periodic server updates.

Audio Sequence at End of Autonomous

• Extended useDisplayAudioService hook to support onEnded callback:

const playAudio = useCallback((key: string, onEnded?: () => void) => {
  // ...
  if (onEnded) {
    audio.onended = () => {
      audio.onended = null;
      onEnded();
    };
  }
  // ...
}, []);

• Updated TRANSITION state handler to chain audio playback:

case 'TRANSITION':
  playAudio('endauto', () => {
    playAudio('transition');
  });
  break;

Independent Client Timers

• Both display/page.tsx and score/page.tsx now capture timer_started_at on timer start
• Local timer calculation uses captured start timestamp instead of polling server values
• Removed updateTimerDisplay(data) calls from polling loops
• Timer resets when match state returns to NOT_STARTED

This ensures all clients start at the exact same moment (via server timestamp) but calculate elapsed time locally, eliminating timer drift from network latency.

Original prompt

At the end of the autonomous period, play the "endauto.wav" file before playing the "transition.mp3" audio file. Also the timer on the camera and the scoring mode clients should start at the same time as the host timer, but should run independently and not try and update periodically from the host timer.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Preview	Comments	Updated (UTC)
ftcscorer	Ready	Preview	Comment	Nov 30, 2025 1:53am