Help In depth
Use another device as a remote, a prompter or a camera
With Pro, a phone as the prompter's remote or its camera, or a tablet or another computer showing the script, joined by a QR code with no account.
The prompter on one device can be controlled from another, or shown on another, and another device's camera can be the one you record. A phone in your hand becomes a remote; a tablet in a prompter rig, or a borrowed computer, shows the script, scrolling with the session; a phone on a stand films you while the computer records. The other device needs only a browser: no app and no account.
It comes with Pro (or a seat in an organization's plan), since the devices meet through Lectern's servers. The device that joins needs nothing: no app, no account, no Pro. Presentation clickers and foot pedals plugged into your computer work without it.
Start a session
- Open the prompter: Practice reading on a script, or Record with this script.
- Click the phone button above the script, Use another device.
- Starting a session needs you to be signed in, with Pro. Signed out, or without it, the dialog says so, with what to do.
- A QR code and a join link show. Scan the code with the other device's camera, or open the link in its browser.
The dialog lists who has joined (a remote on a phone, a prompter on a tablet, a camera and whether it's connected, and so on). Done closes it and leaves the session on. End session ends it, and the other devices say so.
A session lasts until you end it or close Lectern on the device that started it. Up to five devices can join.
On the other device
The join link asks what the device should be:
- Remote: big buttons for Start and Stop, Back a line and Forward a line, the speed (at a set speed) and the text size, and the script in small with the paragraph being read. Tap a paragraph to jump there.
- Prompter: the script, at the place being read. Start and Stop work here too, and tapping a word moves there. This screen sets mirroring and text size for this device only; Match the other device sets them back.
- Camera: this device's camera, sent to the device that started the session, which records it. See A phone as the camera.
Change role at the top goes back to the choice. The screen stays on while it's joined, where the browser allows that.
A Bluetooth clicker paired with the other device works too: Page Down and Page Up move a line, and B or . start and stop.
A phone as the camera
A phone's camera is often better than a computer's webcam. Join with the phone and choose Camera: it shows its picture, to frame yourself with, and sends it to the device that started the session.
- Back camera or Front camera switches between them.
- Microphone on sends the phone's sound too, and that's what's recorded, in step with the picture. Off, the starting device's microphone is recorded.
- While the starting device records, the phone shows Recording.
On the starting device, record with the script as usual (Record with it). Once the phone's connected, the recorder uses its camera, and says so under the picture: The phone's camera. Use this device's camera goes back to its own, and Use the phone's camera to the phone's again. With Camera + screen, the phone's camera is the camera there too.
The take is recorded and saved on the starting device, from the picture as it arrives. That's a live video connection, so its quality follows the network: on good Wi-Fi it's close to the phone's own, on a weak one it's softer, and it's sharpest a few seconds after connecting.
The phone and the starting device connect to each other directly. Some networks block that (often at workplaces and schools, and some phone data plans). Then, after about 15 seconds, the phone sends its picture through Lectern's cloud instead, and says so: it's a moment behind and softer than a direct connection, and the phone's own full-quality recording doesn't come across after. Putting both on the same Wi-Fi usually connects them directly. The Linux desktop app can't take a phone's camera yet; Lectern in a browser on Linux can.
Following your voice
When the prompter scrolls with your voice, the device that started the session listens. A prompter that joined can listen too, with its own microphone: turn on Follow my voice here. That's for when the starting device is out of earshot, like a computer in a church's tech booth with the tablet up front.
While both hear you, the starting device's place wins. When it hasn't heard you for a few seconds, it takes the place the other prompter hears.
At a set speed, every device shows the starting device's place.
If the connection drops
Each device tries again by itself, waiting a little longer each time, and says so at the top. Once it's back, it catches up with where the session is. If the device that started the session closes Lectern, the others say it isn't answering.
To report a connection problem, open Use another device on the device that started the session and choose Copy connection details. It copies what each device saw of the session's connections, with times, and you can paste that into your report. A joined device has Connection details too (the ⓘ button at the top, or the link at the bottom of the page), to copy or share its own. They hold no script text or names.
See also
Something here wrong or unclear? Tell us.