Repository navigation
Closed
Labels
bugSomething isn't workingSomething isn't workingstatus: fixed in mainWork is merged into main but may not be in a downloadable release yet.Work is merged into main but may not be in a downloadable release yet.status: pending releaseMerged change is waiting for a packaged desktop release.Merged change is waiting for a packaged desktop release.
Milestone
Description
Search existing issues
- I have searched the existing issues
Describe the bug
When recording a voiceover in a project that contains trimmed sections, the project playback skips over the trimmed sections, but the voiceover is stored as one continuous audio clip placed at the exact timeline position where the voiceover recording started. As a result, the voiceover does not follow the trims: it keeps playing through trimmed sections (which are never rendered or played) and ends up out of sync with the video content that follows.
Expected behavior
The voiceover should follow the same trim behavior as the video during playback and export:
- When playback reaches a trimmed section, the voiceover should stop/pause, and resume at the end of the trimmed section.
- The trimmed section should contain no voiceover audio, since it is never rendered or played (i.e. the voiceover should effectively be split around the trimmed ranges, or the trimmed portions skipped).
- Playback and rendered output should keep the voiceover aligned with the video it was recorded against.
To Reproduce
- Open a project and trim one or more sections out of the timeline.
- Record a voiceover starting before a trimmed section and continuing past it.
- Play the project.
- Observe that the video jumps over the trimmed section, but the voiceover continues as one continuous audio clip from its start position instead of skipping/pausing over the trimmed section.
Screenshots
OS
Windows
OS Version
Windows 11
Other OS
No response
Browser
No response
Browser Version
No response
Other Browser
No response
Device Type
No response
Other Device
No response
Additional context
No response
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't workingstatus: fixed in mainWork is merged into main but may not be in a downloadable release yet.Work is merged into main but may not be in a downloadable release yet.status: pending releaseMerged change is waiting for a packaged desktop release.Merged change is waiting for a packaged desktop release.
Activity
mikemikimike commentedon Oct 14, 2026
I have opened #1236 to fix this. The voiceover now records a snapshot of the timeline trims and playback speeds, then uses that recording clock for playback, export, transcript placement and cue selection, re-anchoring, and generated-audio insertion. When the playhead does not advance, the recording duration preserves the full take. Existing voiceovers without the snapshot keep their current behavior.
Local validation passed: 338 test files (4,786 tests; 8 skipped), changed-file Biome checks, both TypeScript checks, the Vite build, and
git diff --check. Four release-notes tests fail on the clean base as well and were excluded from the passing full-suite run; repository-wide lint has 148 pre-existing formatting diagnostics on both the base and this branch. A desktop preview/export smoke test remains outstanding.The upstream CI and diagnostic-artifact workflows remain
action_requiredon this fork PR. Rerunning them requires repository admin rights, which my account does not have. PR: #1236fix(editor): preserve voiceover recording spans (getopenscreen#1195)
fix(editor): map transcript cues through voiceover speed (getopenscre…
fix(editor): record voiceovers against the uncut timeline (getopenscr…
fix(editor): record voiceovers against the uncut timeline (getopenscr…
fix(editor): record voiceovers against the uncut timeline (getopenscr…
fix(editor): record voiceovers against the uncut timeline (#1195)
github-actions commentedon Oct 25, 2026
Fixed by #1236 and merged into
main.This change is assigned to the
Next Releaserelease milestone and is not necessarily available in the latest downloadable desktop release yet. It is currently marked asstatus: pending releaseuntil a packaged release containing it is published.EtienneLescot commentedon Oct 29, 2026
Moved into
v2.2.0as part of the pre-release cut.