By now we know how to use a teleprompter from the point of view of a content creator in front of the camera. But remember, that’s not all we do in our world of limited resources. We’re also the audio engineer, cameraman, lighting director, and so many other roles.
So today instead I want to go through with you the preparatory work that goes into setting up the teleprompter before we can actually use it, operating the software side where we boot up our tablet, load the script, and press play, and then how you can manage the small details while you’re actually in the middle of a recording session.
Let’s start off with a run-through of a typical session, and then we’ll look at some a list of advanced features you might want in teleprompter software.
I use a tablet to display the script because it’s easiest to use a free webapp even if Teleprompter apps are available, not only because the cost is less, but because I don’t have to worry about someone else changing the feature set. I can even change some of the details myself or add a feature if I find I need one. And to top it off, I can save it offline and put it on any device with a web browser.
So what kinds of things can go wrong with a teleprompter in daily use? Well, all of these things I’m about to tell you didn’t all happen to me on a single day, but I did experience each of them multiple times over the last few years.
So imagine you’ve set up your hardware along the lines of my previous post. And now…
You notice that you forgot to turn on the tablet ahead of time. You’ll now get to twiddle your thumbs for several minutes. Or worse, you forgot to turn it off last time and now the battery is dead. That’ll be several more minutes at least, please.
You also might find yourself spending 15 minutes trying to load your script via Bluetooth file transfer, or the same amount of time trying to copy it via USB cable or flash card, because you have to go through all the connection settings, find the right path, and then with a multi-fingered magician’s trick start the copy.
As you finally sit down to check that the script is visible from where you’re sitting or standing, you notice the effect of your set lighting on the glass of your teleprompter: light is reflecting off your white shirt or the wall and then onto the glass again, because some light is leaking through the back or around the sides, or the tablet’s screen isn’t bright enough, or the particular text colors you chose look feeble.
You’re in the right spot, your clothes aren’t scrunched up, and you can finally ready to start recording, but wait! Your smartphone is attached to the back of your teleprompter. Time to get up, walk around to the back, press the record button, and go back to your spot. Fun!
Wait, wait, get back up again! You forgot to set the playback/scroll speed, font size, margins, etc. Any false step means doing it all over again, because these factors also collectively affect the number of words scrolling upwards per second. This holds for any other functionality requiring interacting with the tablet.
Now you settle in and start reading comfortably. Suddenly see a mistake in your script, then another! Anything from bad spelling to a sentence you wanted to change but forgot to. What do you do? For now you could just muddle through if the problem isn’t too serious. Wouldn’t it be better though to edit the script in place without having to do all those steps above all over again? And what if you could save those changes for later?
The text of the script isn’t the only thing you can edit, though. You’ve probably marked up the text to add colors that represent something, or you’ve added FontAwesome icons to represent gestures, facial expressions, or when to point to something. If one of those wrong, it’s not as easy to edit as plain text is.
While reading did you mispronounce a word, say the wrong thing, or maybe just not speak quickly enough, so the text scrolled offscreen? Well, you’ll have to scroll back upwards some amount and start over. Guess what, scrolling upwards means getting up, walking to the tablet, finding a good spot in the script where you can start over, then walking back, …
Last but not least, if you’re like me, then you often make mistakes and have to do multiple takes of more than one scene. How do you remember which one is the best so you can delete the others without worrying? I used to go with what seemed a good rule: “The last take was best, because otherwise I would’ve done another take that was better.” Alas, that’s not always the case, especially when you’re under time pressure.
What a disaster. Surely we can do better with a bit of planning and work. And by “do better” I mean both reducing the amount of time you spend recording (before, during and after), and improving quality by minimizing mistakes, imposing some calm, and not having to fix your clothes (and hair, for those vain ones amongst you) after walking around so much.
So what would it look like if we could draw up our own ideal scenario, just conceptually for now? I can synthesize the above into six main points right away:
There are many ways we could reach these goals, but we’re going to have to settle for something specific that we can actually accomplish.
So let’s break those down as much as possible into some generic project specs that would meat those goals and might actually be doable (in code or otherwise):
We can do most of that directly in software, mostly using techniques we either already know, or can easily learn. In fact, I sense a challenge…
So next time, we’re going to look through a few open source Teleprompter apps, see how they’re constructed, and see if we can improve on them. I can almost guarantee you they don’t handle the software feature set above. And why depend on someone else when you can easily do it yourself?
Did you like this article? Does it reflect your skills? Würth Phoenix is always looking for talented, enthusiastic individuals to help us drive our business. In fact, we’re currently hiring for many different roles here at Würth IT Italy.