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

pocketsphinx-continuous

v1.1.0

Published

A node wrapper around pocketsphinx_continuous

Downloads

4

Readme

pocketsphinx-continuous

A node wrapper around pocketsphinx_continuous

Build Status Coverage Status Code Climate Dependency Status

Prerequisites

What does it do?

It just uses the pocketsphinx_continuous command to listen for voice commands, and trying to detect your speech commands based on this. This means you could write your own speech to text scripts around that.

Since pocketsphinx_continuous is able to use dictionaries as arguments, you can get a pretty accurate result, without even transmitting data over the internet.

Usage

var Psc = require('pocketsphinx-continuous');
var ps = new Psc({
  setId: '1337'  // A "set id". See explanation below.
  verbose: false // Setting this to true will give you a whole lot of debug output in your console.
});

This will return a new instance of pocketsphinx-continuous that you can listen to different events on:

Events

data

This is called whenever a sentence or word is recognized and completed.

ps.on('data', function(data) {
});

debug

This will only be called if verbose is set to true. It will give you all output from stderr from the parent process.

ps.on('debug', function(data) {
});

error

Something went wrong with the underlying pocketsphinx_continuous process. It was either closed or terminated. The err parameter might be an exit code or an error object.

ps.on('error', function(err) {
});

What is a "set id"

For the sake of simplicity, I have used the so-called lmtool to generate a dictionary and language model. This will give you a download consisting of a couple of files, and they are usually named in a specific way. For example if your submission generated a "set id" of 1337, then the files inside the downloaded archive would be named (among other) 1337.lm and 1337.dic. These are the ones we use. So if you have downloaded a different dictionary and/or language model, you can rename them to an arbitrary string (preferrably both of them the same) and use that as the setId config parameter.

When you use this module, make sure these files are in the working directory.

Licence

MIT