Differences

This shows you the differences between two versions of the page.

--- tricks:sacn_unicast [2022/05/24 14:21] – [Trivia] icke_siegen
+++ tricks:sacn_unicast [2022/05/25 06:02] (current) – [sACN to sACN, multicast to unicast] icke_siegen
@@ Line 39: / Line 39: @@
 ===== sACN to sACN, multicast to unicast =====
-Network sctructure:
+Network structure:
 {{:tricks:sacn_1.png?600|}}
@@ Line 73: / Line 73: @@
 Hints:
   * midimonster takes very low processing power (at least in my tests with 4 universes converted)
-  * at least in my tests it was not possible to make this work with MIDIMonster directly on the console: it does run but doesn't output as required - the nodes see the universes but there is no data. I believe it is not possible to have two applications on the same machine which both attempt to send to the same port, and one also listens to the other.
+  * at least in my tests it was not possible to make this scenario work with MIDIMonster directly on the console: it does run but doesn't output as required - the nodes see the universes but there is no data. I believe it is not possible to have two applications on the same machine which both attempt to send to the same port, and one also listens to the other.
   * make sure that all network addresses are correct, and that firewalls are off or have the required rules set.
@@ Line 129: / Line 129: @@
 ===== Trivia =====
+==== Picture: my test drive ====
 Yes, I really did try this with some computers (and Wireshark and sACN View - and the network switch is in the middle...)
 {{:tricks:sacn_testing.png?600|}}
+==== Video: another test, on a D9 ====
 And yes, I also tried running this directly on a console (and made one of those shaky videos with my mobile phone):
 {{youtube>35oClm_2i9Y?medium}}
+==== Wireshark screenshots ====
+This is an example of how the sACN network traffic looks in wireshark:
+{{:tricks:wireshark.png?600|}}
+Network addresses in this example (port 5568 is sACN):
+.0.0.1 - Titan PC Suite
+.0.0.10 - MIDIMonster
+.0.0.50 - the 'client' to the left (sACN View)
+.0.0.100 - the 'client' to the right (sACN View)
+.255.0.1, 239.255.0.2, 239.255.0.3, 239.255.0.4 are the automatically generated multicast addresses.
+  Packets from 2.0.0.1 to 239.255.0.1/2/3/4 are the multicast sACN sent from Titan.
+  Packets from 2.0.0.10 to 2.0.0.100 or 2.0.0.50 are the unicast sACN from MIDIMonster to the 'clients'.''
+This is an example of how the mixed Art-Nt/sACN network traffic looks like in wireshark:
+{{:tricks:wireshark_artnet.png?600|}}
+Network addresses in this example (port 5568 is sACN, port 4809 is Art-Net):
+.0.0.1 - Titan PC Suite and MIDIMonster
+.0.0.10 - the 'client' in the middle (sACN View)
+.0.0.50 - the 'client' to the left (sACN View) (no packets to this screnshot)
+.0.0.100 - the 'client' to the right (sACN View) (no packets to this screnshot)
+  Packets from 2.0.0.1 to 255.255.255.255 are the broadcast Art-Net sent from Titan.
+  Packets from 2.0.0.1 to (3.g.) 2.0.0.10 or 2.0.0.50 are the unicast sACN from MIDIMonster to the 'clients'.''
+Btw. 224.0.0.180 is another special auto-generated address which is used by CITP...
+==== Another idea: Raspberry Pi ====
+And very finally: [[https://midimonster.net/download.html|MIDIMonster]] is available for Windows, for OSX, and for Linux. Of course the next idea would be to run this on a Raspberry Pi. But this is probably something for someone else to do. Please let me know if you want to go down this route :-) .