Hey @k-yle,

Tried to send you email but it bounced. Is there a better way to contact you?

Lyndon

The devDependency eslint-plugin-import was updated from 2.18.2 to 2.19.0.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

eslint-plugin-import is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @types/node was updated from 12.12.1 to 12.12.2.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@types/node is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

The devDependency @typescript-eslint/parser was updated from 2.19.0 to 2.19.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/parser is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Ought to close and reopen the dgram socket on network disconnect/reconnect.

Could be an optional feature:

sACN.on('close', sACN.tryReopen);

I notice you can only have one universe on the sender.

Is there a recommended way to send data to multiple universes?

Although I define universes to listen to in the constructor of Receiver, Receiver.on("packet", ...) is called for all received universes.

Is this expected behaviour?

When sequence does not go up to 255, skips it for any reason, the sequence gets out of order for the remainder of the duration the process is running.

if the priority value is the same from two senders, the DMX slot data needs to be merged. ETC's implementation could be used.

The devDependency @typescript-eslint/eslint-plugin was updated from 2.6.0 to 2.6.1.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

@typescript-eslint/eslint-plugin is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Your Greenkeeper Bot 🌴

Until 2.3.2 the message event returned a Packet that contained slotsData. Although objectify existed, we could build our own logic to extract data from the buffer. Since I need the data in raw values (0-255) and as an array, I did that with a few lines of code.

Since 3.1.0 Packet deserializes the buffer directly to the same object as objectify did. Therefore I'd like to propose a change towards the old behavior, maybe including both worlds.

I would create a PR for that but wanted to discuss the issue with you first.

When calling new Receiver() with an interface that doesn't exist, Socket.addMembership() throws Error: addMembership EADDRNOTAVAIL which is not catchable since it happens in the callback.

Wouldn't it be a better idea to add a start() method to Receiver which returns a promise so we could handle the error properly?

Is it possible to specify a single IP to send sACN data to?

Using the below example, only universe 11 is sent via the desired interface, the others are sent via default.

const ip = "10.101.100.1";
const sacn11 = new Sender({
    universe: 11,
    iface: ip
});

const sacn12 = new Sender({
    universe: 12,
    iface: ip
});
const sacn13 = new Sender({
    universe: 13,
    iface: ip
});

Support RDMNet using the new E1.33 protocol

See also: https://github.com/ETCLabs/RDMnet

I found no documentated way to the select the interface the data is sent to.

The default interface is choosen automatically. In my case this is always the WiFi interface, even if it is turned off. For local loopback this is no problem, if the default receiver interface is used, too. This makes it impossible to comunicate over network if the computer has more than one network interface.

Hello together,
your receiver is very beautiful and it works perfectly. Now I want to implement the sender and the priority is 0, with the tool sacnview for windows.
And the sender only once sent the information.

`const { Sender } = require('sacn');

const sACNServer = new Sender({
universe: 1,
// see table 3 below for all options
});

async function main() {
await sACNServer.send({
payload: { // required. object with the percentages for each DMX channel
1: 100,
2: 50,
3: 0,
},
sourceName: "My NodeJS app", // optional. LED lights will use this as the name of the source lighting console.
priority: 188, // optional. value between 0-200, in case there are other consoles broadcasting to the same universe
});

}

main(); // wrapped in a main() function so that we can await the promise`

Hey there!

I just noticed that although documentation states universes must be between 0 and 63999, util.js throws RangeError: universe must be between 1-63999 when using 0. What am I supposed to use now?

Thanks a lot!