> 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/mixer-scene-parameters.md). # Mixer/Scene Parameters Layout and design for the mixer in rooms/scenes, preload/hidden scene bitrate Mixer/Scene Parameters are viewer side options. You can add them to guest's URLs in rooms and scene URLs. ## **Room and Scene options** You have to add them to [`&scene`](/advanced-settings/mixer-scene-parameters/scene.md) or [`&room`](/advanced-settings/setup-parameters/room.md) or [`&view`](/advanced-settings/mixer-scene-parameters/view.md) URLs to change the behaviour of the Video Mixer.

Parameter	Explanation
`&solo`	Similar to `&scene`, but tells the system to be a solo-link
`&view`	Defines the stream(s) you are receiving, by their stream IDs
`&include`	Adds stream IDs within the viewer's room scope; does not import streams from outside the room
`&exclude`	Same concept as `&view`, except does the opposite
`&layout`	Shows the guest a return feed of the current mixer layout when using the Mixer App
`&activespeaker`	Auto-hides remote guests videos when added, if those guests are not speaking actively
`&order`	The order priority of a source video when added to the video mixer
`&slots`	Will force the auto-mixer to have that number of slots, even if there are more or less videos available to fill them
`&fakeguests`	Creates simulated guest videos
`&randomize`	Random video loading order
`&cover`	Has the videos fully "cover" their assigned areas, even if it means cropping the video
`&43`	Optimizes the video mixer for 4:3 videos
`&portrait`	Optimizes the video mixer for 9:16 videos
`&square`	Optimizes the video mixer for 1:1 videos
`&forceviewerlandscape`*	Keeps all incoming videos oriented (rotated) so that the aspect ratio is always above 1
`&animated`	Videos in a group scene will slide around the screen when being re-arranged
`&manual`	Disables the auto-mixer, allowing for a custom mixer to be used
`&locked`	Will force a the VDO.Ninja's mixer output keep the mixed render contained to a specific aspect-ratio, regardless of the browser's window size
`&poster`	Lets you specify a poster image for videos that have not yet started playing
`&hideplaybutton`	Will hide the default big play button that overlays a video when auto play is not allowed
`&motiondetection`*	Does a few things when it detects motion in a video

\*NEW IN VERSION 24 ## **Only Scene options** You have to add them to [`&scene`](/advanced-settings/mixer-scene-parameters/scene.md) or [`&view`](/advanced-settings/mixer-scene-parameters/view.md) URLs.

Parameter	Explanation
`&scene`	Defines the link to be treated like a scene
`&scenerestore`	Restores a guest's selected scene assignments after reconnecting
`&scenetype`	Shows only the last added video to a scene
`&autoadd`	Auto-adds the specified stream IDs to the scene
`&hiddenscenebitrate`	Can be used to force videos not added yet to a scene to run at the specified bitrate
`&preloadbitrate`	Can be used to change the pre-load target bitrate for scenes
`&waitimage`	You can add a custom image which shows up while waiting for the `&scene` or `&view` link
`&waitmessage`	You can add a custom message which shows up while waiting for the `&scene` or `&view` link
`&waittimeout`	Specifies a delay for `&waitimage` and `&waitmessage` while waiting for the `&scene` or `&view` link

--- # 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/mixer-scene-parameters.md?ask=&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.