Script

TunaCut Teleprompter

Most prompters put your script over the thing you are recording. This one puts it around it — two strips docked to the top and bottom of the desktop, with a clean 16:9 hole between them that is exactly the rectangle being captured.

Why the hole is the point

If you are recording your own screen — a demo, a walkthrough, anything where the camera is you and the content is the display — a prompter overlay ends up in the recording. Reserving space instead means the script is on screen for you and absent from the file.

Real appbars. The strips reserve desktop space the way the taskbar does, so maximised windows stop at their edge rather than sliding underneath them.
The prompter owns the rectangle. The recorder asks for a free area; the prompter snaps it to a legal, even 16:9 multiple and publishes back what it actually settled on. One component decides, so the two can never disagree.
Coordinates are physical pixels, always. On a 4K panel at 200% scaling the same four numbers describe two rectangles that differ by a factor of two — which is the kind of bug that looks like it works for months. Nothing on the wire is ever a scaled unit.

It is wired to the recorder

Press Teleprompter in the recorder and three things happen at once: the strips go up, the recorder's desktop capture region snaps to exactly the free area between them, and the floating record panel docks into the bottom of the prompter's own control bar.

So the thing you look at while you talk and the thing that stops the take are in the same place, and the region you configured and the region being recorded are the same rectangle by construction rather than by hand.

Settings that matter on a shoot

How thick each strip is, and how much of the control bar the record panel may take.
Whether the capture region snaps to the strips at all — off, if you would rather place it yourself.
Where the prompter executable lives, or blank to let the recorder find it.

It is a separate program on purpose. The prompter and the recorder are two processes with two lifetimes: a prompter that crashes must not be able to take a recording with it, and a recorder that is busy must not be able to stutter your script.

The take and the words start together

Then the session lands in the editor with the screen region as just another angle.

The editor → The recorder →