Sequencer starts weird

[bhurlow]

@claude clicking the start sequencer button pauses for a weird amount of time. I expect pressing start to immediately reset the clock to now and begin the sequence. It seems like it might be waiting for the next 1 beat to come around instead

[bhurlow]

Claude finished @bhurlow's task —— View job • claude/issue-65-20250708_030013 • Create PR ➔

---

Sequencer Start Timing Issue Fixed ✅

I've successfully fixed the sequencer start timing issue where the start button had an unexpected delay instead of immediately resetting the clock and beginning the sequence.

Todo List:

• Read CLAUDE.md for repo-specific instructions (no file found)
• Find and analyze sequencer-related code (found sequencer.tsx)
• Identify the timing logic causing the delay
• Fix the start behavior to reset immediately
• Test the fix if possible (unable to run tests without bash permissions)
• Commit changes and create PR

Root Cause:

The delay occurred in the Rust sequencer code (lib/src/stage.rs) where play_at_time() would set last_step_time = time and wait for step_interval (125ms at 120 BPM) before triggering the first step.

Fix Implemented:

Modified both sequencer_play() and sequencer_play_at_time() methods in lib/src/stage.rs to immediately trigger the current step when starting:

1. Added trigger_current_step() method that triggers instruments based on current step patterns
2. Call trigger_current_step() immediately when play is pressed
3. Then set up normal timing for subsequent steps

This ensures the sequencer starts immediately without waiting for the next beat timing.

Changes Made:

• Modified lib/src/stage.rs lines 237-247 to add immediate step triggering
• Added trigger_current_step() method (lines 250-268) to handle immediate instrument triggering
• Committed changes with detailed explanation

---