Skip to content

fix(project): sort scene segments when a project loads - #2821

Merged
richiemcilroy merged 2 commits into
CapSoftware:mainfrom
yashranaway:fix/sort-scene-segments-on-load
Oct 22, 2026
Merged

richiemcilroy merged 2 commits into
CapSoftware:mainfrom
yashranaway:fix/sort-scene-segments-on-load

Conversation

@yashranaway

@yashranaway yashranaway commented Oct 21, 2026 •

Copy link
Copy Markdown
Contributor

scene lookup assumes scene segments are in time order, but projects edited in the old tauri app can have them out of order. its add scene code scanned from the end and stopped at the last later scene instead of the first, so adding a scene at 3s to scenes at 1, 5 and 8 saved them as 1, 5, 3, 8. opening that in the new app skips the camera fade into the next scene.

now scene segments get sorted once when the project loads, so editor playback and export both see them in order without any per frame sorting. it's a stable sort, so scenes with the same start keep their order. editing oracles pass.

RetriggerView in GreptileConfidence Score: 5/5

The PR appears safe to merge; no actionable issues were found.

Summary

Scene segments now sort by start time when a project loads. Equal-start scenes keep their existing order.

  • Projects load scene segments in start-time order.

Reviews (1) · Last reviewed commit: "fix(project): normalize scene segment or..." · Reviewed by Greptile

@yashranaway

Copy link
Copy Markdown
Contributor Author

@greptileai review

@vercel

vercel Bot commented Oct 21, 2026

Copy link
Copy Markdown
Contributor

@yashranaway is attempting to deploy a commit to the Cap Software Inc Team on Vercel.

A member of the Team first needs to authorize it.

@richiemcilroy

Copy link
Copy Markdown
Member

@greptileai review

@richiemcilroy
richiemcilroy merged commit 052001e into CapSoftware:main Oct 22, 2026
53 of 61 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants