<nodecg-obs-scene>

nodecg-obs-scene is a Polymer element that provides realtime data bindings with information about a given scene in OBS Studio. It's made to be used with nodecg-utility-obs and nodecg-widget-obs.

For documentation on how to set up and use nodecg-utility-obs and nodecg-widget-obs, see nodecg-obs.

Requirements

• NodeCG v0.9.x
• nodecg-utility-obs and nodecg-widget-obs will also need to be added to your bundle. See the main nodecg-obs documentation for instructions on how to do that.

Install

nodecg-obs-scene should be installed as a dependency of your bundle.

Due to limitations of Bower, you'll need to install bower-npm-resolver to install nodecg-obs-scene.

1. Install bower-npm-resolver via npm:

   cd nodecg/bundles/my-bundle
   npm install --save bower-npm-resolver

2. Add bower-npm-resolver to a .bowerrc file in the root of your bundle (create it if it does not exist):

   {
      "resolvers": [
          "bower-npm-resolver"
      ]
   }

3. Install nodecg-obs-scene via Bower

   bower install --save npm:nodecg-obs-scene

$ bower install --save nodecg-obs-scene

Table of Contents

• Example
• Features
• Planned Features
• Events
• Caveats

Example

<link rel="import" href="../bower_components/nodecg-obs-scene/nodecg-obs-scene.html">

<!-- A simple example element that prints if a given OBS Studio scene is in "preview", "program", or "none". -->
<dom-module id="my-element">
    <template>
        <style>
            :host {
                display: block;
            }
        </style>
        
        <nodecg-obs-scene scene-name="test-scene" state="{{sceneState}}"></nodecg-obs-scene>
        <div>test-scene is currently in: [[sceneState]]</div>
    </template>
    
    <script>
        class MyElement extends Polymer.Element {
            static get is() { 
                return 'my-element';
            }
            
            static get properties() { 
                return {
                    sceneState: String
                };
            }
        }
        
        customElements.define(MyElement.is, MyElement);
    </script>
</dom-module>

Features

• Realtime updates on the Preview/Program state of a scene, via either events or the state property.

Planned Features

• None at this time, but there's a ton of things that this element could do if there's a strong case for it, such as:
  • Enumeration of sources in the scene
  • Two-way bindings of source properties, such as visibility, position, transform, etc.
  • A bunch more that I haven't thought of yet!

Events

<nodecg-obs-scene> will emit an event whenever the status of the scene specified by the sceneName property changes. There are three such events:

• program
• preview
• none

You can listen to them with addEventListener or with Polymer's annotated event listeners:

sceneElement.addEventListener('program', () => { /* ... */ });
sceneElement.addEventListener('preview', () => { /* ... */ });
sceneElement.addEventListener('none', () => { /* ... */ });

You can also use the state-changed event emitted by Polymer, if you'd like to catch all state changes:

sceneElement.addEventListener('state-changed', e => {
	console.log(e.detail.value); // Will be one of "program", "preview", or "none".
});

Caveats

• If a scene is in both Preview and Program, nodecg-obs-scene will always report it as being in Program.
• You may need to call .refresh(true) on your instance of nodecg-obs-scene on initial page load, because the first state change event may happen before the rest of your code is ready.