Trim ranges video load

[kentcdodds]

Clear trim ranges and selection state when a new video is loaded to prevent invalid ranges from persisting and causing UI/logic inconsistencies.

The resetPreviewState function previously did not clear trimRanges, selectedRangeId, or activeDrag. This allowed trim ranges from a previously loaded video to remain visible in the UI when a new, shorter video was loaded. These invalid ranges would then be silently filtered out during normalization, leading to a confusing "Add at least one trim range" error when the user attempted to process the video, despite seeing ranges in the UI.

---

 

---

Note

Ensure trim UI state is fully reset on new video load.

• Extend resetPreviewState to clear trimRanges, selectedRangeId, and activeDrag along with preview flags
• Prevents stale/invalid ranges from persisting across videos and causing normalization/validation errors

^{Written by Cursor Bugbot for commit 149ed09. This will update automatically on new commits. Configure here.}

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[github-actions]

🎉 This PR is included in version 1.13.1 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀