Remote pad on another device

Whoever helps with the live opens the pad in a browser, on a phone, a tablet or a computer: on the same network, or from anywhere through the internet.

Pairing

In Settings, Remote access, turn on either way (or both) and pair the device: a phone or tablet scans the QR code, and a computer opens the link under it, copied and sent to it alone. The key travels in the code and in the link itself and never crosses the network; the link is never shown, since your screen may be on air. On this network, the first time, Windows may ask to let Vovó through its firewall: allow it. When the firewall keeps devices out (the question was cancelled, never came, or the network changed kind), Remote access says so under the address, and so does pre-flight: Allow asks Windows once, and lets in only this network's devices, on Vovó's port.

Through the internet

With "Take devices from anywhere" on, the device reaches Vovó through the relay, on mobile data or any Wi-Fi, with nothing to open in the firewall. The relay only passes on encrypted messages it cannot read. A device paired before this was on needs a new code; a code made with it on works at home too.

Your own relay

Vovó uses its own relay unless Settings, Remote access, names another: a relay of your own keeps the devices' traffic with you. Devices paired through another relay need a new code.

Permissions

Each device sees and presses only the pad groups you allow, and may or may not write in the team's conversation, read it and use panic. Editing actions, scenes or settings is never remote.

Whoever runs the live with you may also, if you allow it: approve or discard what waits before going on air (the persona's answers), ask the persona, read the console, put an OBS scene on air, seeing whether OBS streams (nothing else of OBS, and never stopping the stream), talk on air, share its own screen, use the actions' panels, and see the OBS preview and hear the live, which only another Vovó on this network shows and plays. Each is a permission of the device, and most become a tab on its pad. What someone approves there leaves the queue for everyone, and the console says who approved.

The remote pad

At its top, beside the profile, is the name you gave the device when pairing it. A search over the pad finds a button by its name, or a whole group by its own, whatever the accents. Beside it, the same layouts as on the computer: a grid, by group, or the groups side by side. Each phone keeps its own choice. The buttons' shape and their density are the profile's, as in Settings, Pad, until whoever holds the phone picks their own with the sliders beside the layouts. Holding a button opens its sheet, with its name and a star that puts it among that phone's favorites. All of it is kept in that phone's browser and nowhere else, so your pad, and what your other devices see, stay as you set them. The page on your network and the one through the internet are two addresses to a browser, and each keeps its own.

Panic is the octagon at the top, first of its buttons, then sharing the screen and the microphone: the first tap arms it, in red, and says so, the second, within a moment, clears the overlays. While it is on, a red bar under the top says so, with Restore.

Controls on the remote pad

Control buttons show their value there too, or "Not known" with no overlay open. A tap switches on or off, picks the option or adds one; a counter's corner opens a sheet to take one away, type a number or start over, and a tap on a text opens the sheet to type it.

The team's conversation

You and whoever helps run the live write to each other here, out of the live's sight: in Team, its icon at the window's right edge under Chat and AI, while the profile takes devices; on a device's Team tab; and in the side bar of another Vovó joined to the live. A device's line shows on your screen overlay too, with its sound, which plays once for lines close together; it never waits in the bell, and your own lines never show on the overlay. Off air, a Windows notification says who wrote and the line too, at the same pace, and not while you are reading the conversation.

Writing and reading are two permissions of a device: Client writes; Operator writes and reads. A device reads back to the day it was paired, never earlier, so a new helper does not read what an earlier team wrote.

It is kept on this computer, in Vovó's database, and nowhere else: a phone or another Vovó is sent the newest lines and asks for the ones before as it scrolls, keeping none once it closes; through the internet they go encrypted end to end, and the relay cannot read them. It goes into backups with the rest of the database, goes with its profile and with Erase everything, and a duplicated profile starts without it. It lasts as long as the version history (Settings, Backup: 1, 7, 15, 30 or 90 days, a year, or for good); older lines go when Vovó starts.

The bin at the top of the page clears the whole conversation for everyone, after asking twice; only you have it. A device takes back a line of its own, for everyone: a right click on it, or holding it on a phone, then Delete for everyone. With the game in front, a "Write to the team" button of the pad sends its line with a press or its hotkey, and vovo team "…" does from a terminal or a button box.

The side bar is part of Vovó's window, which a display capture in OBS shows; the screen overlay never shows in a capture.

Talking on air

A device allowed to talk on air has a microphone button at the top of its pad. Hold it, speak and let go: the voice goes on the live a moment later, from the scene's overlays, as with a walkie-talkie. Drag the finger away before letting go to cancel; a touch too short is not sent, and 30 seconds is the most at once. The device is told whether it played on the live, or whether only you heard it because no overlay was open. While it plays, its icon is in the middle of the status bar and the screen overlay says who is talking; the console and the audit say who talked, and panic refuses it. Actions hear it as remote.talk, to show who is talking while they talk.

Browsers open the microphone only on a secure page: the pad through the internet is one, the pad on this network is not. Pair the device with "Take devices from anywhere" on. On the phone, talk with headphones: what comes out of its speaker, the live included, would go on air with the voice. To hear it yourself, set the scene's Browser Source to "Monitor and Output" in OBS's Advanced Audio Properties, as for the pad's sounds.

Panels on the remote pad

A device allowed the actions' panels has a Panels tab: the same panels as at the computer, drawn the same way, one at a time, with their own sections. A few are chips at the top, each with its icon; with more than five, one button names the one in front and opens the list of them, with a search. When no open scene shows the action, it says its buttons reach nobody, and they wait faded. A raffle's list grows there as people join, a form opens a sheet to type in (a name to add, say), a button that asks twice says "Sure?" first, and the controls move as on the pad. The action hears it as the panel event, the console and the audit say which device did it, and nothing reaches it during panic. A long list shows its first 100 lines there, and its search, in a sheet, looks through all of it: Vovó answers with the lines that hold what is typed, and their buttons act on those lines.

A device allowed to share its screen has a screen button at the top of its pad, in a computer's browser (a phone's has no way to share one). It asks Vovó for a share page of its own, which opens in another tab, where the browser asks what to share. From there it is a guest like any other, under the name you gave the device: what it shares waits in the bell until someone puts it on air, here, in Integrations or with a "Guest's screen" button, and panic takes it off. A device that may also approve can put its own screen on air, so give both only to whom you would let do that. Its page holds for 12 hours, and ends with the permission or the device.

Another Vovó's live

Whoever helps run the live and has Vovó on their own computer can run it from there rather than from a browser: the same pad, in the window they know, with hotkeys that work with a game in front.

You pair it in Settings, Remote access: Pair a device, Another Vovó. Vovó makes a code (it starts with VOVO1-), hidden on screen since your screen may be on air: copy it and send it to that person alone. It lasts an hour and works once: at its first connection the other Vovó is given a key of its own, and the code left in a chat no longer opens anything. The bell tells you when another Vovó connected with a code, with Revoke for one you did not expect.

On their side: New profile, From another Vovó, and paste the code (the first run asks the same, for someone who installs Vovó only to help). The live opens as a profile, under Remote in the profile menu, its picture with a globe and the window in its colour, so it never passes for one of theirs. It has the pad of the groups you allowed, and a Connection page in place of Settings: whose live it is, how it is reached, what that computer may do (you decide it, here), and Forget, which tells your Vovó to revoke it. Panic follows the live chosen. Away from your Vovó its pad fades and says it is waiting, and connects again by itself; revoked, it says so.

Its chat is there to read, with a line read aloud on air, and to write in as themselves (see below); its persona to ask; what waits for approval comes to its bell; the team's conversation is in its side bar; OBS's scene is in its status bar. Editing your actions, scenes or settings is never there. What the team writes is told there by its sound and by a Windows notification with who wrote and the line, which its Connection page switches off: on a whole screen shared to your live, the notification would show too.

What you allow the device, it does from the window. Your actions' panels come under Panels. With "See the OBS preview" allowed, its Connection page has the OBS preview switch, and the icon after your OBS's scene in its status bar: what your OBS sends, in the small window, on that computer. Only while it reaches your Vovó on the same network: through the internet the switch says "Only on the same network" and waits, and "Open the live on Twitch", on the same page, opens your channel in its browser instead. Its buttons take hotkeys of that computer's, chosen on its Connection page and kept there, never one its own pad uses; they work while your live is the one chosen. Its favorites, from a button's menu, and the buttons' shape and density, on its Connection page, are that computer's own too, yours until it chooses, and never reach your Vovó. With talking on air allowed, its microphone in the header records while held and goes on your air when let go (dragged away, nothing goes), or a key held does the same, and it says whether it played on your live or only you heard it, with no overlay open; the same headphones as on a phone, or your live comes back through its speakers. With sharing allowed, its screen button opens a share page in its browser, which asks what to share, and the picture waits for you as a guest's does.

With the music allowed, the note at its window's right edge opens your player in its side bar, and Listen first plays your songs there, 30 seconds at a time ([Music](help:music)).

Writing in its chat

Whoever helps from their own Vovó writes in your chat as themselves, never as you. On the live's Connection page, under Chat, Connect signs in a Twitch account of their own with a code at twitch.tv/activate, opened in the browser where Twitch is their own account. Vovó asks Twitch only to write in chat with it: it reads nothing of the account and moderates nothing. From then on the side bar's chat has a field that says whose lines it writes, and a line goes from that computer straight to Twitch: your Vovó does not carry it, and sees it come back in the chat like anyone's. The field shows only where the live lets that computer read its chat; a phone has none, since Twitch's own app writes there.

One account writes in every live that computer joins, and stays when one of them is forgotten; Disconnect takes it away, and so does Erase everything. Twitch holds it to the channel's rules (slow mode, followers only, AutoMod), most of which a moderator of the channel passes. A line Twitch does not deliver is said there with Twitch's reason, and "Back to the field" puts it where it was typed. The channel's own account never writes from another computer: connected there, the page says so and the chat stays read only.

Hearing the live

Whoever runs your live from their own Vovó on the same network can hear it as it happens, without Twitch's delay, and set a sound off right on cue: your microphone and what plays on your computer, each with a volume of its own on their side.

What they hear is what you say and what you hear, not exactly what goes to Twitch. A call or a video in another tab goes too, when it plays on the device chosen; an overlay sound you do not hear does not. For them to hear the sounds they set off, hear the overlay yourself: in OBS, set its Browser Source to "Monitor and Output" in the Advanced Audio Properties.

In Settings, Remote access, under "Hearing the live", choose the microphone and the device whose sound goes, both Windows' default until you choose. Each has a switch: off, it goes to nobody, and stays off until you switch it back on, Vovó closed and opened again included. With OBS connected, a microphone you mute in OBS (its mixer, a key, a Stream Deck) is not sent either. Your microphone is open only while someone listens, and Windows shows its mark meanwhile.

While someone listens, headphones show in the middle of the status bar; pressing them says who, and has the same two switches. The device's line in Remote access says it is listening, and the console says when it starts. Only another Vovó with the permission "Hear the live" hears it, and only on the same network as this computer: the sound never goes through the internet.

On their side, the speaker in the corner of the OBS preview turns the sound on and off, and with the pointer over the preview shows a volume for the voice and one for the computer. The headphones after the OBS preview's icon in the status bar do the same without the picture, and Connection has the switch, the two volumes and the device it plays on. Each time Vovó starts it is silent, and closing the preview takes its sound with it. While they hold the microphone to talk on air, it goes quiet, so their recording does not carry your live back onto it.