OLA ArtNet Roadmap - Revision history

Peternewman: /* Multiple ArtNet Devices */ Switch to interwiki links

2014-12-28T16:49:32Z

‎Multiple ArtNet Devices: Switch to interwiki links

Nomis52: /* Multiple ArtNet Devices */

2014-12-20T17:45:52Z

‎Multiple ArtNet Devices

Nomis52: /* Increased Input Ports */

2013-04-04T04:48:22Z

‎Increased Input Ports

Nomis52: /* Increased Output Ports */

2013-04-04T04:46:09Z

‎Increased Output Ports

Nomis52 at 04:44, 4 April 2013

2013-04-04T04:44:15Z

Mrpackethead: /* Investigate Optimizing the Send Path */

2013-03-08T23:55:45Z

‎Investigate Optimizing the Send Path

Mrpackethead: /* Usecases */

2013-03-08T23:52:43Z

‎Usecases

Mrpackethead: /* Usecases ==== Usecases */

2013-03-08T23:43:05Z

‎Usecases ==== Usecases

Mrpackethead: /* Usecases */

2013-03-08T23:42:36Z

‎Usecases

Mrpackethead at 23:01, 8 March 2013

2013-03-08T23:01:49Z

@@ Line 35: / Line 35: @@
 === Multiple ArtNet Devices ===
-Right now only a single ArtNet Device is created. This should be changed so that OLA creates [https://github.com/OpenLightingProject/ola/blob/master/plugins/artnet/ArtNetPlugin.cpp#L46 one device per logical interface].
+Right now only a single ArtNet Device is created. This should be changed so that OLA creates [[code:plugins/artnet/ArtNetPlugin.cpp#L46|one device per logical interface]].
-Currently the ArtNetNode object binds to the wildcard address ([https://github.com/OpenLightingProject/ola/blob/master/plugins/artnet/ArtNetNode.cpp#L1596 code]) which means trying to create a second instance will fail.
+Currently the ArtNetNode object binds to the wildcard address ([[code:plugins/artnet/ArtNetNode.cpp#L1596|code]]) which means trying to create a second instance will fail.
 We need some research into how broadcast traffic is handled with multiple interfaces.  Ideally each instance should bind to the broadcast addresses for the specified logical interface.

@@ Line 35: / Line 35: @@
 === Multiple ArtNet Devices ===
-Right now only a single ArtNet Device is created. This should be changed so that OLA creates [https://code.google.com/p/open-lighting/source/browse/plugins/artnet/ArtNetPlugin.cpp#45 one device per logical interface].
+Right now only a single ArtNet Device is created. This should be changed so that OLA creates [https://github.com/OpenLightingProject/ola/blob/master/plugins/artnet/ArtNetPlugin.cpp#L46 one device per logical interface].
-Currently the ArtNetNode object binds to the wildcard address ([https://code.google.com/p/open-lighting/source/browse/plugins/artnet/ArtNetNode.cpp#1636 code]) which means trying to create a second instance will fail.
+Currently the ArtNetNode object binds to the wildcard address ([https://github.com/OpenLightingProject/ola/blob/master/plugins/artnet/ArtNetNode.cpp#L1596 code]) which means trying to create a second instance will fail.
 We need some research into how broadcast traffic is handled with multiple interfaces.  Ideally each instance should bind to the broadcast addresses for the specified logical interface.

← Older revision		Revision as of 04:48, 4 April 2013
Line 46:		Line 46:

	=== Increased Input Ports ===		=== Increased Input Ports ===
		+
		+	This is more challenging since it requires multiple IP addresses on the host in order to work correctly (that is, have the ports show up in ArtPollReplies). [[libartnet]] supported the concept of merging node instances, we should do something similar in OLA. It may be challenging to work out the corner cases when this interacts with the multi-device change.

← Older revision		Revision as of 04:46, 4 April 2013
Line 42:		Line 42:

	=== Increased Output Ports ===		=== Increased Output Ports ===
		+
		+	This shouldn't be too hard. Only the first 4 ports will be represented in the ArtPollReply responses. We'll need to store the net, subnet and port ids on a per-port basis. Right now the net & sub-net values are the same for all ports in a node.

	=== Increased Input Ports ===		=== Increased Input Ports ===

@@ Line 1: / Line 1: @@
 This describes proposed changes to the [[OLA]] [[ArtNet]] plugin to make it more usable. Some of the use cases that have been requested include:
 * Receiving broadcast ArtNet data and unicasting to a static list of destinations
 * Converting many universes (10s, 100s?) from ArtNet to E1.31 and visa versa.
+* Receiving broadcast ArtNet data on one interface, and then sending using ArtNet2 / ArtNet 3 on another interface.
 Artnet-1 to Artnet-2.   There are some media servers that do not support Unicast Art-net at all, and all packets are broadcast. When the number of universes exceeds some threshold ( typically >20 ) many end devices can't cope with the number of packets that are needed to be discarded.  You end up with irractic and laggy results.  ( end devices typically have low power embedded microcontrollers ).     Broacast packets need to received from a console/media server and retransmitted in unicast. Its important to be able to either use the Art-net poll mechanism to auto-populate which universes are required on which devices or to use a 'static' routing system. Because we are listening to an Art-net Speaking console, we need to be listen to a large number of universes.
@@ Line 16: / Line 11: @@
 A typical device that we would want to listen to could be a GrandMA VPU.   It does not support Static assignment of Universes to IP address',  and there is a requirement to be able to send more than 4 universes to an Art-net device..
 == Requirements ==
@@ Line 26: / Line 17: @@
 * Support more than 4 ports in both directions
 * De-couple the ArtNet universe from the OLA universe number to support any-way patching. i.e. patch ArtNet universe 5 to OLA universe 3.
 == Proposed Changes==
@@ Line 31: / Line 23: @@
 === Investigate Optimizing the Send Path ===
-The [http://man7.org/linux/man-pages/man2/sendmmsg.2.html sendmmsg] syscall was added in Linux 3.0. It allows multiple datagrams to be sent with a single syscall. sendmmsg would allos us to reduce the number of syscalls required for each ArtNet packet when unicasting. This scope of this change is to make the required changes and then benchmark the performance.
+The [http://man7.org/linux/man-pages/man2/sendmmsg.2.html sendmmsg] syscall was added in Linux 3.0. It allows multiple datagrams to be sent with a single syscall. sendmmsg would allow us to reduce the number of syscalls required for each ArtNet packet when unicasting. This scope of this change is to make the required changes and then benchmark the performance.
 Steps:

@@ Line 37: / Line 37: @@
 * Add a method to the UDPSocket class to enable a single data message to be sent to many addresses
 * Modify the ArtNetNode::SendDMX method to use the new UDPSocket method
 === Multiple ArtNet Devices ===

@@ Line 6: / Line 6: @@
 == Usecases ==
 Using OLA as a 'protocol' converter, to allow equipment that is otherwise incompatible to work together.
 Artnet-1 to Artnet-2.   There are some media servers that do not support Unicast Art-net at all, and all packets are broadcast. When the number of universes exceeds some threshold ( typically >20 ) many end devices can't cope with the number of packets that are needed to be discarded.  You end up with irractic and laggy results.  ( end devices typically have low power embedded microcontrollers ).     Broacast packets need to received from a console/media server and retransmitted in unicast. Its important to be able to either use the Art-net poll mechanism to auto-populate which universes are required on which devices or to use a 'static' routing system. Because we are listening to an Art-net Speaking console, we need to be listen to a large number of universes.
@@ Line 13: / Line 17: @@
-Using OLA as a 'protocol' converter,  from Art-net to E1.31
+''Using OLA as a 'protocol' converter,  from Art-net to E1.31
+''
 Similar to above, but receiving Art-net and transmitting in E1.31..   It woudl be good to be able to support E1.31 in both Multicast and Unicast.