npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@networkoptix/webrtc-stream-manager

v0.1.15

Published

![Nx Meta Logo](https://meta.nxvms.com/static/images/logo.png)

Downloads

18

Readme

Nx Meta Logo

WebRTC Stream Manager License: MPL--2.0"

What is @networkoptix/webrtc-stream-manager?

This package simplifies playing back videos via WebRTC from Nx Meta VMS mediaservers versions 5.1 or later.

What can it do?

The exported WebRTCStreamManager class handles establishing a WebRTC connection with the mediaserver.

When initializing the connection using the connect static method, a video element could optionally be passed as an argument to be used to gather metrics as part of the stream switching algorithm.

The WebRTCStreamManager defaults to showing live but also allows for updating the playback position to play streams from archive. The playback position could also be updated; when the position is updated all WebRTCStreamManager instances playback positions are synced to the new time stamp.

Authentication and reconnections are handled automatically by the library for as long as there's an active subscription to the observable returned by WebRTCStreamManager.connect.

Usage

The WebRTCStreamManager class exposes a connect static method which is used to initialize a connection.

The connect static method could accept either a WebRtcUrlConfig or WebRtcUrlFactory as the first argument.

Using WebRtcUrlConfig is the recommended way to connect since it allows the library to handle more complicated aspects of establishing a connection like choosing the right authentication method bases on vms version as well as working with the relay. The WebRtcUrlFactory method is deprecated and is only supported for backward compatibility.

Example webRtcUrlConfig:

The WebRTCStreamManager.connect method takes as a first argument a config. The systemId, cameraId, and system access token are required. Other properties are optional.

const webRtcConfig = {
  systemId: '{system_id}',
  cameraId: '{camera_id}',
  accessToken: '{access_token}'
}

Example usage

The connect static methods returns an observable emits streams and errors.

To update a video element to use that stream we set the srcObject to the stream if it exist.

To start autoplaying you can also set muted and autoplay to true.

Target element

<video id="someTargetId" autoplay muted></video>
const targetVideoElement = document.querySelector('video#someTargetId')

Initializing connection and setting video source

const connectionSubscription = WebRTCStreamManager.connect(webRtcConfig, videoElement).subscribe(([stream, error]) => {
  if (stream) {
    targetVideoElement.srcObject = stream;
    targetVideoElement.muted = true;
    targetVideoElement.autoplay = true;
  }

  if (error) {
    handleError(error)
  }
});

Closing the connection

The connection could either be closed manually by unsubscribing from the subscription returned by WebRtcStreamManager.connect(...).subscribe(...) or by using rxjs operators like takeUntil.

Manually unsubscribing
connectionSubscription.unsubscribe();
Using rxjs takeUntil
const notifier$ = new Subject();

WebRTCStreamManager.connect(webRtcConfig).pipe(
  takeUntil(notifier$)
).subscribe(handleStream);

// Somewhere else in the code
notifier$.next();