Web Page Renderer

Dynamic content inputs/Web page renderer

A powerful way of getting external web data/images/animations/audio into Composer is by using the Web Page Renderer input. External web pages can be fetched, including web pages running JavaScript.

The Web Page Renderers support HTML transparency, meaning content can be partly transparent from a Web Page Renderer.

There are two different Web Page Renderers, Chromium and Ultralight. The Chromium version renders content faster but is incompatible with the runtime version of Linux. At the time of writing, the Ultralight version has limited web page support due to limitations in the underlying library (3rd party). Future updates of Composer will contain updates to the Ultralight version.

 The Web Page Renderer will capture the visual content of a web page at the same frame rate as the scene is being rendered, only limited by the system’s performance.

Both Web Page Renderers (Chromium and Ultralight) have a similar GUI interface. Below is the Chromium interface.

• Url - Web page URL. HTTP or HTTPS. (Example: https://composer.docs.vindral.com)
• Reload page URL (button) - Reloads the webpage
• Cef renderer load state - Status. 
• Dimensions:
  • Renderer width - Renderer width (pixels)
  • Renderer height - Renderer height (pixels)
• Scrollbar(chromium only)
  • ScrollBar X-Pos - Set horizontal scrollbar position
  • ScrollBar Y-Pos - Set vertical scrollbar position
• Commands:
  • Start page rendering (button) - Load the page and start rendering
  • Stop page rendering (button) - Stop rendering
• Configuration:
  • Start rendering when loaded - Enable this option to automatically start rendering the webpage when the project loads. (Default)
  • Auto reload page on error - Enable this option to automatically reload the page if the last load attempt failed (HTTP result other than 200)
  • Enable web page console logging - Enable this option to add logs from the webpage console to the Composer log file.
• Performance and properties:
  • Video queue size - number of video frames captured (buffered) but not yet rendered. 
  • Page render performance: Time to render the page.
• Render Options - These options, together with Render Tuning (see Performance and Options), help optimize performance by letting Composer automatically decide whether the input should be rendered.

  When your project’s Render Tuning option is active, Composer manages each input’s rendering automatically for best performance.
  These options allow you to override that behavior and manually decide if this input should be rendered or excluded from the scene.

  Render Tuning vs Render Options:

  • Render Tuning works at the project level (see Performance and Options), automatically managing which inputs are rendered across all Scenes for optimal performance.
  • Render Options work at the input level, letting you manually override or fine-tune how a specific input behaves within Composer’s automatic rendering process.

  • Invisible (do not render in scene) - The input will not produce any visible output in the scene, regardless of whether Render Tuning is enabled at the project level.

  • Do not render input
    • Let Composer decide (default) - Composer automatically decides whether the input should be rendered, based on the active Scene and if Render Tuning is enabled.
    • Manual configuration - Allows you to manually control rendering behavior using the Render switch (see below).
  • Render - A toggle switch is available only when Manual configuration is selected.
• Audio - Configure metering, gain, pan, auxiliary sends, mute/solo, routing, and audio channel remapping for this input. See Audio options for more information.
• Optional TAGS
  • TAGS - Add a "tag"  that can be used in the input smart search function. It is possible to add several tags by separating them with a SPACE character.

 For more information on Chromium and Chromium Embedded Framework, visit

https://www.chromium.org/Home

https://en.wikipedia.org/wiki/Chromium_Embedded_Framework