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

@mikw99/nodered-osc-to-emberplus

v1.4.7

Published

a specialzed node to bridge osc-values to a lawo-console

Readme

nodered-osc-to-emberplus

A specialized node to bridge a limited range of osc commands to a lawo console.
Last output of each node is for debugging.
Added two additional nodes for Ember-to-Ember and Ember-to-OSC,
these are still in the test phase. Any feedback on bugs is hugely appreciated.

Prerequisites in flow: Target and Source addresses are accessed via flow.context arrays with matching index.

To make managing your target and source arrays easier, EmberOut accepts separate arrays for different DSP targets.
You could also put all targets into one array, if that is more convenient for you.
v1.4.0 Adds a node that guides you through the creation of arrays, at the moment only for EmberOut. It reacts to msg.topic "create". In Templates folder you also find flows with a customisable function instead.

It is also recommended to run only one ember+ Node per subflow, and create the necessary arrays for each.

For EmberOut:
oscDictFader -> emberDictFader
oscDictGain -> emberDictGain
oscDictPFL -> emberDictPFL
oscDictGrp -> emberDictGrp
oscDictGrpPFL -> emberDictGrpPFL

For EmberIn:
emberInputDict -> oscOutputDict
emberInputDictPFL -> oscOutputDictPFL
emberInputDictGrp -> oscOutputDictGrp
emberInputDictGrpPFL -> oscOutputDictGrpPFL

For EmberX:
emberInputDict -> emberOutputDict
emberInputDictGrp -> emberOutputDictGrp

You also need:
ignoreListDict

You need the ignoreList array, which should contain every right channel of stereo channels in the ember targets, if you filled out the other arrays automatically. It will prevent timeouts when trying to set values for these channels. \

Aside from the osc-input, you also need to be able to inject a number of command code words.
msg.topic "reconnect" msg.topic "get Nodes" msg.topic "reScan" msg.topic "disconnect"
Workflow:

  1. Put target IP into node config.
  2. inject msg.topic "reconnect".
  3. inject msg.topic "get Nodes".
  4. wait for "get Node" operation to be finished.