> 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/advanced-settings/settings-parameters/and-rampuptime.md).

# \&rampuptime

When a guest connects, this tries to load video from that guest for a few seconds, even if not yet added to a scene

Sender-Side Option! ([`&push`](/advanced-settings/setup-parameters/push.md))

## Options

Example: `&rampuptime=4000`

| Value           | Description        |
| --------------- | ------------------ |
| (integer value) | ramp up time in ms |

## Details

`&rampuptime=6000` is a sender-side parameter. Previously it was 4-seconds, but now it defaults to 6-seconds.

When a guest connects, this just tries to load video from that guest for a few seconds, even if not yet added to a scene. It helps the browser judge total bandwidth availability better, so bitrates can ramp up slightly faster later when actually added needed.

Related to this, the target bitrate for this ramp up period has been increased to 1500-kbps, rather than 1000; this could already be changed with [`&preloadbitrate`](/advanced-settings/mixer-scene-parameters/and-preloadbitrate.md) (sender side), but based on feedback I'm nudging it up a bit.

## Related

{% content-ref url="/pages/wOmmOQoQwQhVJh0gBlTZ" %}
[\&preloadbitrate](/advanced-settings/mixer-scene-parameters/and-preloadbitrate.md)
{% endcontent-ref %}


---

# 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/advanced-settings/settings-parameters/and-rampuptime.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.