> For the complete documentation index, see [llms.txt](https://docs.vdo.ninja/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vdo.ninja/guides/telestrate-a-callers-video.md).

# Telestrate a caller's video

Draw or ping on a caller's live video and show the annotations in OBS, either over the caller's feed or as a transparent overlay.

VDO.Ninja's built-in **Draw/Ping on video** tool annotates a caller's camera or screen share. The marks are a synchronized overlay, not part of the caller's encoded video. The caller relays them to other viewers, and each OBS source or viewing link that should show them must include `&drawing`.

{% hint style="success" %}
**The short version:** Add `&drawing` to the OBS Browser Source URL. In the Director's Room, right-click the caller, select **Request draw access** or **Draw/Ping on video**, then select **Pen**.
{% endhint %}

![The director draws on the caller's video. The caller's browser relays the marks to viewers. An OBS link with \&drawing shows the marks; an OBS link without it shows the caller without marks.](https://2943598173-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MZHXv1G8N0MDxwotaT9%2Fuploads%2Fgit-blob-7715d3f22560d8a2e2fa205ae090c15b70d548be%2Froom-telestrate-path.svg?alt=media)

## Show the caller and annotations together

For a caller with the stream ID `PLAYER1` in room `YOUR_ROOM`, use this OBS Browser Source URL:

```
https://vdo.ninja/?view=PLAYER1&room=YOUR_ROOM&drawing&cleanoutput
```

For a complete room scene, add `&drawing` to the scene link:

```
https://vdo.ninja/?scene&room=YOUR_ROOM&drawing
```

Keep the room password and other connection options the same on the director, caller and OBS links.

## Start drawing

1. In the Director's Room, right-click the caller's video or screen share.
2. Select **Request draw access**. If access was already granted, the option reads **Draw/Ping on video**.
3. The caller gets a chat message asking to allow annotation and selects **Allow**.
4. When the drawing controls appear, select **Pen** and draw over the video.

The controls also include:

* **Ping** for a temporary marker
* a color picker
* **Clear** to remove all marks
* **Undo** to remove the last mark

Right-click the video again and select **Stop draw mode** when finished.

Adding `&drawing` to the caller's invite link pre-approves drawing, so requests are allowed without asking. Only do this when the caller expects annotations.

## Output only the drawings, on a transparent background

Add a separate OBS Browser Source with the same caller link plus `&transparent`:

```
https://vdo.ninja/?view=PLAYER1&room=YOUR_ROOM&drawing&cleanoutput&transparent
```

In that Browser Source's **Custom CSS** field, use:

```css
video {
    opacity: 0 !important;
}
```

The video stays active as the position reference but is hidden, so only the drawing canvas shows. Place this source above the game feed or other source you want annotated.

Match the Browser Source size and aspect ratio to the feed the telestrator draws on. A different crop or aspect ratio puts the marks in the wrong place.

{% hint style="warning" %}
Every VDO.Ninja view or scene link that should show the annotations needs `&drawing`. Without it, the caller appears normally but the marks don't.
{% endhint %}

## Troubleshooting

* Refresh the OBS Browser Source after adding `&drawing` or changing its Custom CSS.
* If the director still sees **Request draw access**, the caller hasn't approved yet.
* Don't add `&nodrawingrelay` or `&noshareddrawing` to the caller's link; they stop the caller relaying annotations to other viewers.
* For one caller's feed, use `&view=STREAM_ID`. For a composed room layout, use the scene link with `&drawing`.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.vdo.ninja/guides/telestrate-a-callers-video.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
