alt.hn

5/2/2026 at 2:26:38 AM

Create an MP4 video of a web page scrolling at a steady speed

 https://github.com/upenn/web-scroll-video

by shawnzam

5/2/2026 at 7:52:46 AM

This has to be intentional. I refuse to believe that someone would do this unintentionally. You are literally making video of a website, the app doesn't have any other feature, yet you don't show us the example!? What causes this? It has to be intentional, but why?

by dvh

5/2/2026 at 8:48:33 AM

They've probably just asked their agent to create code and a readme. Adding example is too complicated for AI and doing it manually is extra work.

People are too lazy to do actual work now in the age of AI.

by archargelod

5/2/2026 at 9:49:29 AM

This isn’t even an original idea either. Claude proposed to build something similar to me when I asked him how I could present my 2500+ saved Telegram links so that I can browse them more efficiently.

If the author of this repository was proud of their craft (which they can’t be), they would want to show us “how cool it looks” in an example.

by Diti

5/3/2026 at 2:57:03 AM

I added a demo

by shawnzam

5/4/2026 at 6:30:03 AM

Is it possible to save the run as instructions too so you can recreate it without an LLM?

by victorbjorklund

5/4/2026 at 11:44:43 AM

Yes, each run generates a `.cue` file.

`node src/scroll-video.mjs --script examples/wharton-faculty-demo.cue`

If the cue file does not specify out:, the MP4 is written next to the cue file with the same basename.

by shawnzam

5/2/2026 at 3:09:14 AM

You could do this with ffmpeg on a screenshot PNG.

ffmpeg -i screenshot.png -vf \ "crop=iw:1080:0:n*(20000-1080)/600,format=yuv420p" \ -t 10 -r 60 output.mp4

by andrewstuart

5/2/2026 at 5:01:06 AM

Title of the post fails to describe what this fully does and you didn't seem to have read the repo. This generates a live interaction with the website, with scrolls, timings, clicks, route navigations, etc. A mixture of AI generated cues that you can use via skills + scripts to be feed with those cues that will process the video automatically via headless chromium and ffmpeg. Seems really interesting

by arecsu

5/2/2026 at 6:05:34 AM

What problem does this solve?

by burgerone

5/2/2026 at 7:30:22 AM

Seems pretty useful to be able to write your documentation videos as steps and generate new videos everytime the platform changes. Let’s say you have 200 videos showing how to do different things and now the UI changes.

You can either leave the videos as is (and get more confused customers) or you can spend a lot of hours recording 200 videos again. Or you can run this and get the 200 videos done in the background. Let’s say that your app is changing every month because you are early in your iteration. That is a lot of time saved every month.

by victorbjorklund

5/2/2026 at 7:45:16 AM

Or you want to produce demo videos in multiple languages.

by JimDabell

5/4/2026 at 6:28:51 AM

That’s a great usecase too.

by victorbjorklund

5/2/2026 at 7:05:13 AM

Say you have documentation with a video showing the user how to open a page, click a button, scroll, etc. Instead of having to re-record those videos every time you update the UI you can use this library to automatically recapture it on every push.

by haaz

5/2/2026 at 6:06:28 AM

Many websites have looping or scroll-triggered animations, or play gifs / videos that a static image wouldn't capture.

by wbobeirne

5/2/2026 at 7:04:35 AM

i bet you its in aid of advertising somehow

by globalnode

5/2/2026 at 6:39:59 PM

[dead]

by shawnzam

5/3/2026 at 9:31:06 PM

Sent you an email.

by chistev

5/2/2026 at 2:26:38 AM

[flagged]

by shawnzam