docs(testing): log the Linux pass of v2.1.0-rc.5

[EtienneLescot]

Logs the Linux pass of v2.1.0-rc.5 in the manual e2e checklist's Results log. The pass covers only the diff since rc.4 (#1294, #1296). It ran on the Vivobook (Ubuntu 24.04, GNOME 46 Wayland, Radeon 610M), with the release AppImage and A/B runs against the rc.4 AppImage on the same projects.

Result: Partial.

1. fix(compositor): no Full Camera trail on a clip's first frame when its start is inexact in f32 #1294, Full Camera at export: fail at 3 of 5 cuts. In a 1080p60 export with five trims inside one Full Camera span, the first frames after cuts 3, 4 and 5 (frames 1094, 1369, 1588) show the camera smeared toward its PiP corner. rc.4 had the same three plus frame 600, which is the PR's 11.388 case and is now fixed. f32 rounding of the clip start does not explain the three that remain. The Windows rc.5 pass also has one cut left.
2. fix(preview): restart the playback clock at the requested time on a held frame #1296, pause on a held frame then a setting change: pass. The cursor and the playhead stay put. On rc.4 the cursor jumps back to the held frame's time.
3. Seek then play: no new hitch. On the held-frame take, rc.5 gives 29–30 changes/s, where rc.4 has 100–133 ms stills every 0.5 s. On the real take, rc.5 matches rc.4 at ~30/s. One A-B-A appears at play start in 1 of 4 rc.5 runs.
4. Linux seek into a still stretch, and past the last screen frame: smooth on rc.5.

A real Linux PipeWire take has no long held frame: the helper encodes a frame at every tick, even on a still screen with a still pointer. The held-frame path is therefore reached on Linux only with VFR media, so the held-frame take used here is the real take turned VFR with mpdecimate.

Docs only. No code change.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Documentation
  • Added Linux end-to-end test results comparing v2.1.0-rc.5 with rc.4. The notes report that pausing on a held frame and changing settings preserves the playhead and cursor position, with no regression in seek-then-play smoothness. They also record that the Full Camera export trail still shows three of five trim cuts, along with Linux capture details, test setup, observations, and coverage limits.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: defaults
• Review profile: CHILL
• Plan: Advanced
• Run ID: e520953d-97f5-4ba4-8dc3-d2061035534f

📥 Commits

Reviewing files that changed from the base of the PR and between dd3dfd3 and 57a7916.

📒 Files selected for processing: 1

• technical-documentation/testing/manual-e2e-checklist.md

🚧 Files skipped from review as they are similar to previous changes: 1

• technical-documentation/testing/manual-e2e-checklist.md

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 4 remain after this review.

📝 Walkthrough

The checklist records Linux end-to-end results for rc.5 compared with rc.4. It reports held-frame pause and settings behavior, trim-cut counts, seek-then-play smoothness, test conditions, and coverage limits.

Changes: Linux AppImage E2E results

Layer / File(s)	Summary
Record and qualify the rc.5 test results technical-documentation/testing/manual-e2e-checklist.md	The entry reports three of five Full Camera trim cuts in rc.5, compared with four in rc.4. It also records that changing settings while paused on a held frame preserves the playhead and cursor position, and that seek-then-play smoothness shows no regression. The entry includes test setup and coverage limits.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~2 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to 57a79

The Linux test results can be merged as a record of a partial pass; the remaining export failures are explicitly noted.

Pre-merge checks: 5

Check name	Status	Explanation
Title check		The title clearly identifies the documentation change and the specific Linux pass recorded for v2.1.0-rc.5.
Description check		The description explains the test scope, environment, results, issue coverage, and documentation-only impact. It does not use the repository template headings or checkboxes, and it does not explicitly…
Docstring Coverage		No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Description check

Explanation

The description explains the test scope, environment, results, issue coverage, and documentation-only impact. It does not use the repository template headings or checkboxes, and it does not explicitly state the related issue, release impact, or desktop impact fields.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Warning

Some tools did not complete. Review the errors below.

🔧 LanguageTool

technical-documentation/testing/manual-e2e-checklist.md

LanguageTool checks are incomplete because the per-file request limit of 5 was reached. Remaining text was skipped; findings from completed checks are retained.

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.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}