feat(pitch): re-time the deck to the recorded narration beats (2:12)#89
Conversation
The generated 1.2x narration (109.8s) was much shorter than the deck (188s) and its
per-frame holds were misaligned with the beats (F4 hero held 25s for a 2s line; F5
held 6s for a 12.5s line). Rather than pad the narration with dead air, I split the
real audio at its silence boundaries (ffmpeg) and re-timed the deck to those clip
lengths + a short visual tail.
- SLIDE_DURATION -> [5,18,8,8,5,14,12,13,9,22,9,9,12] (cover->F11 = 132s / 2:12).
- F5 fixed (6s -> 14s so its VO fits); F4 hero 25s -> 5s (clip 2s + dramatic hold).
- All "188s" labels -> "2:12" (title, cover meta, cover-cta, F-key button, playRange,
JS comment); cover "0:35-1:00 -> 0:34-0:39" F4 chip; close stat number dropped
("One run. One audited score.").
- Comment notes F8-F9 are replaced by a live /participate screen-recording in the
final cut (so the delivered video is ~2:30-2:50); the array keeps them for a
slides-only fallback.
Verified in browser: SLIDE_DURATION 13 elements summing to 2:12, cover meta renders
"2:12 · runtime", no "188" left, no console errors.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
|
Warning Review limit reached
More reviews will be available in 10 minutes and 9 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ✨ Finishing Touches🧪 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 |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the presentation deck's total runtime from 188 seconds to 2:12 and adjusts individual slide durations in the SLIDE_DURATION array. The review feedback points out two main inconsistencies introduced by these changes: first, the hardcoded slide timestamps in the HTML markup (e.g., <span class="time">) are now out of sync with the updated slide durations; second, the opening range (F1 to F4) duration is still hardcoded as "60s" in multiple UI elements and event handlers, whereas the new cumulative duration is 39 seconds.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| const SLIDE_DURATION = [ | ||
| 8, // 01 · Cover | ||
| 10, // 02 · F1 0:00–0:10 | ||
| 15, // 03 · F2 0:10–0:25 | ||
| 10, // 04 · F3 0:25–0:35 | ||
| 25, // 05 · F4 0:35–1:00 (HERO — 25s hold) | ||
| 6, // 06 · F5 1:00–1:06 | ||
| 24, // 07 · F6 1:06–1:30 | ||
| 24, // 08 · F7 1:30–1:54 | ||
| 26, // 09 · F8 1:54–2:20 | ||
| 26, // 10 · F9 2:20–2:46 | ||
| 9, // 11 · F10 2:46–2:55 | ||
| 5, // 12 · F11 2:55–3:00 | ||
| 5, // 01 · Cover (no VO — title hold) | ||
| 18, // 02 · F1 0:00–0:18 | ||
| 8, // 03 · F2 0:18–0:26 | ||
| 8, // 04 · F3 0:26–0:34 | ||
| 5, // 05 · F4 0:34–0:39 (HERO — clip 2s + dramatic hold) | ||
| 14, // 06 · F5 0:39–0:53 | ||
| 12, // 07 · F6 0:53–1:05 | ||
| 13, // 08 · F7 1:05–1:18 | ||
| 9, // 09 · F8 1:18–1:27 (live-rec in final cut) | ||
| 22, // 10 · F9 1:27–1:49 (live-rec in final cut) | ||
| 9, // 11 · F10 1:49–1:58 | ||
| 9, // 12 · F11 1:58–2:07 | ||
| 12 // 13 · Closing | ||
| ]; |
There was a problem hiding this comment.
The hardcoded presentation timestamps in the topbar of each slide (e.g., <span class="time">0:00 – 0:10</span> on Slide 2, <span class="time">0:35 – 1:00</span> on Slide 5, etc.) are now completely out of sync with the newly updated SLIDE_DURATION array.
For example, based on the new durations:
- F1 should be
0:05 – 0:23(instead of0:00 – 0:10) - F2 should be
0:23 – 0:31(instead of0:10 – 0:25) - F3 should be
0:31 – 0:39(instead of0:25 – 0:35) - F4 should be
0:39 – 0:44(instead of0:35 – 1:00) - F5 should be
0:44 – 0:58(instead of1:00 – 1:06) - ... and so on.
Please update the <span class="time"> elements inside the <section class="slide"> containers for slides 2 through 12 to match these new cumulative timings so that the displayed slide timestamps are accurate and consistent with the actual auto-advance durations.
| }); | ||
| document.getElementById('btn-play-opening').addEventListener('click', () => playRange(1, 4, 'opening · F1 → F4 · 60s')); | ||
| document.getElementById('btn-play-full').addEventListener('click', () => playRange(0, 11, 'full · cover → F11 · 188s')); | ||
| document.getElementById('btn-play-full').addEventListener('click', () => playRange(0, 11, 'full · cover → F11 · 2:12')); |
There was a problem hiding this comment.
The duration for the opening range (F1 to F4) is still hardcoded as 60s in several places, but according to the new SLIDE_DURATION array, the actual duration is now 39 seconds (18 + 8 + 8 + 5).
Please update the following references to reflect the new 39s duration:
- Line 1260:
<button id="btn-play-opening" ...><span>▶ Opening · F1→F4 (60s)</span>...-> change(60s)to(39s) - Line 1638:
playRange(1, 4, 'opening · F1 → F4 · 60s')-> change60sto39s - Line 1665:
playRange(1, 4, 'opening · F1 → F4 · 60s')-> change60sto39s
1 participant
Per the user's call: keep the generated 1.2x narration (109.8s), split it at its silence boundaries, and re-time the deck to those real clip lengths instead of padding the narration with dead air.
[5,18,8,8,5,14,12,13,9,22,9,9,12](cover->F11 = 132s / 2:12), matched to the measured beat clips (F1 16.7s … F9 21.0s … F11 6.3s) + a short visual tail.188slabels ->2:12; close-stat number dropped.The 11 beat clips were split to
~/Downloads/glasshat-narration-beats/for the video edit. Verified in browser (2:12, no 188 left, no console errors). Static HTML.