Release notes to video: a Rust release as a team update
Release notes to video with an API: the Rust 1.99.0 release post became a short update video for an engineering team. Watch it, copy the request, see the cost.
How this was made. Audio and video overviews, slide decks, infographics and quizzes are made with Google's Gemini Notebook (formerly NotebookLM), on accounts that AutoContent operates. AutoContent has no agreement with Google. Google can limit or stop this access at any time.
- Length
- 5 min 45 s
- Credits used
- 50 credits
- Cost on the Starter plan
- €1.45
- Generation time
- 11 min 59 s
- Format
- Explainer video
- Job
- Team updates
- Language
- English
- Generated on
- 2026-11-03
This output used 50 credits, which is €1.45 on the Starter plan (€29 per month for 1,000 credits). Failed generations use none. Generation time runs from the request to the finished file; it depends on the sources, the options and the queue.
What came out, and what we would change
We sent the Rust 1.99.0 release post and asked for a short update video for an engineering team that uses Rust: what changed, what to try first, and anything that needs action when upgrading. The result is a 1280 × 720 MP4 of 5 min 45 s in five sections, from the upgrade command to the newly stable APIs. The same post also became a 1 min 46 s brief in this library.
The facts match the post: rustup update stable, the beta and nightly channels for testing, C-ABI variadic functions defined with the "C" and "C-unwind" ABIs, VaList and the VaArgSafe trait, naked variadic functions written with inline assembly, the three functions that settle layout information for raw pointers, and the APIs it names, such as Vec::into_parts and std::fs::set_times. As asked, no contributor is named.
One point is framed too strongly. The post says there is no change to the language semantics: the documentation now recommends against freeing memory after Box::leak and prefers Box::into_raw or Box::into_non_null. The video calls this "action required" and says you "absolutely must avoid" the pattern. Checking your code for it is good advice, but it is a recommendation. The video also says VaList matches the C type on "literally all targets"; the post says across targets.
Our request asked for "anything that needs action", and the video found something to call action. For release updates, say how strong the advice should be, for example "say plainly when nothing is required". The video took 11 min 59 s to generate and used 50 credits.
Transcript excerpt
Speech-to-text of the output, not edited and without speaker labels. It is part of the sample output.
The Rust team has updated the docs with a really strong new recommendation against a pattern known as roundtrip unleaking after calling box colon leak. So previously you might have leaked memory using box colon leak, and then later attempted to deallocate that exact same memory. Well, you need to stop doing this. While the actual language semantics haven't fundamentally changed in 1.99.0, this specific pattern has been flagged. Why? Because it has some pretty problematic interactions with current and potential future compiler optimizations.
Let's briefly touch on some quality-of-life improvements here. The safety requirements for retrieving size and alignment on raw pointers are now fully settled for both sized and non-sized types. Sized types were trivially safe and already possible, sure, but now we have full stabilization across three core functions. Layout for value raw, mem size of val raw, and mem align of val raw.
The exact request
The body that was sent to POST /content/Create, unchanged, and the same request as curl.
{
"resources": [
{
"type": "website",
"content": "https://blog.rust-lang.org/2026/10/01/Rust-1.99.0/"
}
],
"outputType": "video",
"format": "explainer",
"text": "A short update video for an engineering team that uses Rust: what changed in this release, what to try first, and anything that needs action when upgrading. Do not name individual contributors.",
"language": "English"
}curl -X POST "https://api.autocontentapi.com/content/Create" \
-H "Authorization: Bearer $AUTOCONTENT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"resources":[{"type":"website","content":"https://blog.rust-lang.org/2026/10/01/Rust-1.99.0/"}],"outputType":"video","format":"explainer","text":"A short update video for an engineering team that uses Rust: what changed in this release, what to try first, and anything that needs action when upgrading. Do not name individual contributors.","language":"English"}'
# then poll until "status" is 100:
curl -H "Authorization: Bearer $AUTOCONTENT_API_KEY" "https://api.autocontentapi.com/content/Status/<request_id>"How we checked it
- Transcript
- We transcribed the output with Whisper large-v3-turbo and compared the transcript with the source.
- Language
- Detected en, requested en.
- Loudness
- -20.4 LUFS integrated, true peak -1.9 dBTP.
- Notes
- Commands, variadics, VaList and VaArgSafe, naked variadics, the three layout functions and the APIs match the post. The Box::leak recommendation is framed as "action required"; "literally all targets".
- Checked on
- 2026-11-03. Failed generations are run again and never published.
More examples
All examples- Podcast · EnglishA critique podcast that reviews a style guide: PEP 2573 min 58 s · 10 credits (€0.29 on Starter)
- Podcast · EnglishTurn release notes into a team podcast: a real brief1 min 46 s · 10 credits (€0.29 on Starter)
- Podcast · EnglishA debate podcast from a style guide: two rules of PEP 85 min 39 s · 10 credits (€0.29 on Starter)