7 ScriptReadr Self-Tape Tips
ScriptReadr does a lot of listening — it's following along as you speak, deciding when your line is "done," and cueing the next one at the right moment. Most of the time it just works. But it's still listening to a live take, not reading your mind, so it helps to know how it actually makes that call. Here are seven things I've learned building the app and using it on my own tapes that'll get you a smoother scene partner.
1. Place the device where it can clearly hear you
ScriptReadr is using your device's mic and speakers, so where you set the device matters more than people expect. Put it somewhere close to you — closer than you'd think — without blocking the microphone, so it can pick up your voice clearly over any room noise. This also solves a second problem: if the device is sitting right next to the camera, the recorded lines play back at full volume right next to the lens, and they can overpower your own performance in the audio. Move the device in close to you (and off to the side of the camera) and you get a clean read on your voice without the other lines drowning you out.
2. Cut lines short if you need to be interrupted
If your character gets cut off mid-sentence, you don't need a special trick — just delete the last few words of the line in the ScriptReadr scene editor. ScriptReadr waits until you've said every word it knows about before moving on, so if the line only has the first half of the sentence typed in, that's all it's listening for. You can keep talking past it in the actual read — finish the sentence out loud like your character would — but ScriptReadr will already have moved on and started playing the next line underneath you, exactly like a real scene partner talking over you.
3. Use timed action blocks for longer silent beats
Written lines are listening for speech, and they'll wait up to about 10 seconds of silence before assuming you're done and moving on. Short glances, reaction beats, or a pause in the middle of a line are fine — you've got plenty of room there. It's the longer silences that cause trouble: a real physical action, a slow look, anything that's going to eat up several seconds with nothing said out loud. For those, use an action block instead of stretching a written line's silence budget. Action blocks run on their own timer — they'll hold for however long you set, not the written-line timeout — so you can actually play the moment at its real length instead of racing through it to beat the clock.
4. Split extremely long lines into a few short ones
ScriptReadr is generally very good at knowing when you've finished a line, but a long speech is harder — past a certain length, it can think you've wrapped up before you actually have and jump ahead, clipping your last few words. If you notice that happening on a monologue or a long chunk of dialogue, break it into two or three shorter lines in the editor instead of one long one. The scene reads the same to you as the performer; it just gives ScriptReadr more, smaller checkpoints to cue off of.
5. Have different readers voice different characters
Because ScriptReadr runs entirely online, you're not limited to reading every other part yourself. Send different characters in the scene to different people — each person records just their own part, from wherever they are. Hearing an actual different voice for every character (instead of you doing all the voices, or one reader doing every part) makes a real difference for your eyelines and your reactions — you react differently to a different voice than you do to your own.
6. Talk over recorded lines for quick back-and-forths
If you're in a fast, overlapping argument scene, don't bother typing out every single line word-for-word. Have your reader record their side of the exchange, and then talk over their recording the way you would in a real argument — cutting them off, jumping in early, stepping on their last word. It reads as an actual back-and-forth instead of a polite line-by-line exchange, and it'll bump up the pace and intensity of the scene a lot more than waiting your turn would.
7. Rewrite the line to match what ScriptReadr actually hears
If ScriptReadr is struggling to cue off a particular line, check the scene report to see what it actually
heard you say. Speech recognition sometimes hears something reasonable-but-wrong — if your line is "I'm
in the ATP" and the report shows it keeps picking up "I'm in the ATV," just change the line in the editor
to I'm in the ATV. You're not changing your performance, you're just telling ScriptReadr what
to listen for so it cues the rest of the scene the way it's supposed to.