# Output & Live View: Integrating with a mixer

> Getting the output into the production chain.

Glider documentation · Playout & On Air · Web page: https://cgglider.com/docs/live-output/integration/

Sections of this page: [Output tab](https://cgglider.com/docs/live-output.md) · [Live view](https://cgglider.com/docs/live-output/live-view.md) · [What the output can see](https://cgglider.com/docs/live-output/public-state.md) · [Going live](https://cgglider.com/docs/live-output/going-live.md) · [Integrating with a mixer](https://cgglider.com/docs/live-output/integration.md)

- Add /view/<pageId> as a browser source at the page's frame and frame rate (Settings › Show › Format; 1920 × 1080 by default). A source of another size shows the whole frame, scaled to fit.
- The desktop app always serves /view on port 4100, so the source URL survives a restart. Set GLIDER_PORT to use another port; if the port is busy at launch, the app takes a free one for that session and notes it in its log.
- Enable transparency in the source: the page is already transparent, but the source must not composite it onto black.
- Give the source the machine's real frame rate; a 30 fps source makes 50 fps motion judder.
- Interact with the page once if it needs to play audio — browsers block autoplay until then.
- Keep the output window unminimised; a backgrounded tab is throttled and motion stutters.