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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@kissmybutton/motorcortex-video

v2.2.2

Published

**Table of Contents**

Downloads

82

Readme

MotorCortex-Video

Table of Contents

Demo

Check it out here

Intro / Features

Using MotorCortex-Video you can add video and many video effects in your clips.

The Plugin exposes three Incidents in total:

  • the video Clip
  • the Playback incident
  • the VideoEffect incident

Getting Started

Installation

$ npm install --save @kissmybutton/motorcortex-video
# OR
$ yarn add @kissmybutton/motorcortex-video

Importing and loading

import { loadPlugin } from "@kissmybutton/motorcortex";
import MCVideo from "@kissmybutton/motorcortex-video";
const VideoPlugin = loadPlugin(MCVideo);

Creating Incidents

Clip

The Clip is used to create a new video clip and you can pass to it all of the core video information such as the source and the size:

const VideoClip = new VideoPlugin.Clip(
  {
    sources: [
      "http://path/to/the/video/file.mp4",
      "./path/to/the/video/file.ogg", // alternative source for browser compatibility issues
    ],
    width: 640,
    height: 360,
  },
  {
    selector: ".your-selector", // or host: your-host
  }
);

Clip Attrs

  • sources: an array of sources to be used for your video. Is expected to be an array as you might need to pass more than one sources (e.g. an mp4 and an ogg)
  • width: (optional / defaults to 640). The desired width of the video in pixels. You only need to define it by an integer
  • height (optional / defaults to 360). The desired height of the video in pixels. You only need to define it by an integer
  • startFrom (optional / defaluts to 0). If passed the video will be loaded directly with start on the specified millisecond
  • ⚠️ audio (optional, defaults to false). The videos always render muted unnless you explicitly set audio to true

Playback

The Playback Incident is used to define the execution of the video. The only thing to set is the duration.

const Playback = new VideoPlugin.Playback({
  selector: "!#video", // that's mandatory, it should always have the value "!#video" and it targets the video of the VideoPlugin.Clip
  duration: 20000, // the duration of the playback in milliseconds
});

IMPORTANT

All Playback Incidents should have as a selector : !#video

Adding Incidents in your clip

clipName.addIncident(incidentName,startTime);

Contributing

In general, we follow the "fork-and-pull" Git workflow, so if you want to submit patches and additions you should follow the next steps:

  1. Fork the repo on GitHub
  2. Clone the project to your own machine
  3. Commit changes to your own branch
  4. Push your work back up to your fork
  5. Submit a Pull request so that we can review your changes

License

MIT License

Sponsored by

Kiss My Button