> For the complete documentation index, see [llms.txt](https://unknown-56-works.gitbook.io/luigiscreen/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unknown-56-works.gitbook.io/luigiscreen/screens-and-streaming/multiple-screens.md). # Multiple Screens and Clones LuigiScreen supports multiple named screens. ## Independent screen settings Every screen keeps its own media source, FPS, viewer distance, world, location, width, height, enabled state and visibility permission. ``` /screen create spawn 7 4 /screen create shop 4 3 ``` The screens may be in different worlds and use different source types. ## Clone an existing screen Look at the upper-left block for the new display and run: ``` /screen clone spawn lobby ``` The new screen copies the source type and value, dimensions, FPS, distance, enabled state and visibility setting. Its world, location and facing come from the new wall. ## Shared loading and decoding LuigiScreen groups screens by their normalized source type and value: ```mermaid flowchart LR A["video: intro.mp4"] --> B["One shared media worker"] B --> C["Shared latest frame"] C --> D["spawn renderer"] C --> E["lobby renderer"] C --> F["cinema renderer"] ``` Three clones do not start three FFmpeg decoders. Each screen still performs its own MapEngine scaling and packet rendering because its dimensions, FPS and viewers may differ. The shared worker reads at the highest effective FPS required by its enabled screens. A slower clone discards replaced pending frames rather than building delay. ## Split a clone into another source ``` /screen source lobby image lobby.png ``` `lobby` now gets its own source group. The original worker continues if another enabled screen still uses the original source. ## Pause behavior A shared FFmpeg worker pauses only when no enabled screen in its group has a viewer within that screen's own distance. Disabling one clone does not interrupt other enabled clones: ``` /screen stop lobby /screen start lobby ``` --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://unknown-56-works.gitbook.io/luigiscreen/screens-and-streaming/multiple-screens.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.