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

bitcodin

v0.7.0

Published

Bitcodin API wrapper

Downloads

15

Readme

bitmovin

build status npm version Coverage Status

The bitmovin API for NodeJS is a seamless integration with the bitmovin cloud transcoding system. It enables the generation of MPEG-DASH and HLS content in just some minutes.

Installation

Change directory to your project folder and install with NPM.

cd your/project/folder
npm install bitcodin --save

Usage

Before you can start using the api you need to set your API key.

Your API key can be found in the settings of your bitmovin user account, as shown in the figure below.

APIKey

An example how you can set the bitcodin API is shown in the following:

var bitcodin = require('bitcodin')('THIS_IS_MY_API_KEY');

Each Api call with the bitcodin object returns a promise, which can be processed like follows:

bitcodin.input.list()
    .then(function(inputs) {
        console.log('inputs', inputs);
    }, function(err) {
        console.error(err);
    });

Example

Creating a new Transcoding Job

This example shows the process of creating a new input and a new encoding profile. When the above mentioned objects are created a new transcoding job will be created.

var bitcodin = require('bitcodin')('THIS_IS_MY_API_KEY'),
    openMovieUrl = 'http://eu-storage.bitcodin.com/inputs/Sintel.2010.720p.mkv',
    createInputPromise, createEncodingProfilePromise;

// Create bitcodin Input
createInputPromise = bitcodin.input.create(openMovieUrl);

// Create bitcodin encoding profile. The ApiAry documentation which explains how such a
// encoding profile should look like can be found at the link below
// http://docs.bitcodinrestapi.apiary.io/#reference/encoding-profiles/create-an-encoding-profile
var encodingProfileConfiguration = {
    "name": "bitcodin Encoding Profile",
    "videoStreamConfigs": [
        {
            "defaultStreamId": 0,
            "bitrate": 1024000,
            "profile": "Main",
            "preset": "premium",
            "height": 768,
            "width": 1366
        }
    ],
    "audioStreamConfigs": [
        {
            "defaultStreamId": 0,
            "bitrate": 256000
        }
    ]
};

createEncodingProfilePromise = bitcodin.encodingProfile.create(encodingProfileConfiguration);

// Create a bitcodin job which transcodes the video to DASH and HLS. The ApiAry documentation which explains
// how a job configuration object should look like can be found at the following link below
// http://docs.bitcodinrestapi.apiary.io/#reference/jobs/job/create-a-job

var jobConfiguration = {
    "inputId": -1,
    "encodingProfileId": -1,
    "manifestTypes": ["mpd", "m3u8"]
};

Q.all([createInputPromise, createEncodingProfilePromise]).then(
    function (result) {
        console.log('Successfully created input and encoding profile');
        jobConfiguration.inputId = result[0].inputId;
        jobConfiguration.encodingProfileId = result[1].encodingProfileId;
        
        bitcodin.job.create(jobConfiguration)
            .then(
            function (newlyCreatedJob) {
                console.log('Successfully created a new transcoding job:', newlyCreatedJob);
                console.log('MPD-Url:', newlyCreatedJob.manifestUrls.mpdUrl);
                console.log('M3U8-Url:', newlyCreatedJob.manifestUrls.m3u8Url);
            },
            function (error) {
                console.log('Error while creating a new transcoding job:', error);
            }
        );
    },
    function (error) {
        console.log('Error while creating input and/or encoding profile:', error);
    }
);