Fix macOS warm-start recording finalization - #829
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (9)
Included review availability: Your plan provides up to 10 included reviews per hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe recorder now rejects non-monotonic timestamps and anchors resumed audio to the first post-resume video sample. The launch HUD updates pointer handling and timing. The stop control uses a styled native button. Diagnostics require a non-empty output file. ChangesRecording and launch behavior
Estimated code review effort: 3 (Moderate) | ~20 minutes Merge Risk: ⚪ Minimal · up to The PR is merge-ready after normal checks and review; no actionable merge-blocking risk remains. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
@coderabbitai review |
✅ Action performedReview finished.
|
Description
Fix macOS recordings that could leave a zero-byte MP4 after the countdown warm-start pause/resume. Also improve the stop-button visual and idle HUD click-through behavior.
Motivation
Audio could deliver the first post-resume sample before video and consume the shared timestamp adjustment. The following video timestamp could then move backwards, causing AVAssetWriter to fail and leave an empty recording. The idle HUD padding also intercepted clicks outside the visible controls.
Type of Change
Related Issue(s)
None.
Screenshots / Video
Not attached. The stop control is now a filled white square inside the existing red circular recording button.
Testing Guide
Automated validation:
Checklist