> For the complete documentation index, see [llms.txt](https://guide.prismlive.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.prismlive.com/desktop/guides/sources/media-source/using-media-source.md).

# Using Media Source

Windows, Mac

We’d like to provide some tips on using them in v4.

***

In Studio Mode, media sources do not play automatically after being added. Here’s a step-by-step guide:

{% stepper %}
{% step %}
**Add a media source in the source add window.**

<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*gGKMKKUkZy_iiPVkjQHzmA.png" alt="" width="563"><figcaption></figcaption></figure>

{% endstep %}

{% step %}
**Select the media file.**

<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*FofC_SRCdxzgmNsDt2-W5A.png" alt="" width="563"><figcaption></figcaption></figure>

{% endstep %}

{% step %}
**If media sources do not autoplay:**\
\
**Method 1:**\
Uncheck the ‘Restart playback when source becomes active’ option, then click the OK button. This will make the media source play automatically.

<figure><img src="https://miro.medium.com/v2/resize:fit:1400/1*6raJrnm2pIG-V1KlHqHBrA.png" alt="" width="563"><figcaption></figcaption></figure>

**Method 2:**

If you don’t uncheck the box as in Method 1, after adding the media source, click the ‘Apply’ button in Studio Mode to make the media source play.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2FVtM8qv9hieBKH362MJJI%2FGroup%2025.png?alt=media&amp;token=23949740-ed78-42bd-92c5-299abee3a82e" alt="" width="563"><figcaption></figcaption></figure>

**Method 3:**

To view the media source only in the EDIT screen, add the media source -> click the ‘Stop Media’ button -> click the ‘Restart Media’ button. This will make the media source play only in the EDIT screen.

<figure><img src="https://1019928184-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FlISC5rfB4Hnmbsjf8phq%2Fuploads%2F22B9LNYdzhoJK8KBl1TF%2FGroup%2026.png?alt=media&amp;token=c276fdb2-5223-4812-b3d9-3cdd9b335e15" alt="" width="563"><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

[Desktop](https://guide.prismlive.com/desktop/overview.md), [Guides](https://guide.prismlive.com/desktop/guides.md), [Sources](https://guide.prismlive.com/desktop/guides/sources.md), [Media Source](https://guide.prismlive.com/desktop/guides/sources/media-source.md)


---

# 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://guide.prismlive.com/desktop/guides/sources/media-source/using-media-source.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.
