tricks:sacn_unicast
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
tricks:sacn_unicast [2022/05/24 13:33] – [Art-Net broadcast to sACN unicast] 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 ===== | ===== sACN to sACN, multicast to unicast ===== | ||
- | Network | + | Network |
{{: | {{: | ||
Line 73: | Line 73: | ||
Hints: | Hints: | ||
* midimonster takes very low processing power (at least in my tests with 4 universes converted) | * 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' | + | * at least in my tests it was not possible to make this scenario |
* make sure that all network addresses are correct, and that firewalls are off or have the required rules set. | * make sure that all network addresses are correct, and that firewalls are off or have the required rules set. | ||
Line 116: | Line 116: | ||
</ | </ | ||
+ | An example file for mapping 4 universes {{ : | ||
+ | |||
+ | All you need to do is adjust this to your needs (in and out universes, target network addresses, maybe more mappings etc.), save this as monster.cfg (or drop this on midimonster.exe, | ||
+ | |||
+ | Hints: | ||
+ | * midimonster takes very low processing power (at least in my tests with 4 universes converted) | ||
+ | * make sure that all network addresses are correct, and that firewalls are off or have the required rules set. | ||
+ | * running anything else on the same computer Titan runs on is greatly discouraged for the Titan PC Suite, let alone for Avolites Titan consoles. | ||
+ | * if you need this on your console frequently then you might consider [[tricks: | ||
+ | |||
+ | ---- | ||
+ | |||
+ | ===== 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...) | ||
+ | |||
+ | {{: | ||
+ | |||
+ | ==== 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> | ||
+ | |||
+ | ==== Wireshark screenshots ==== | ||
+ | |||
+ | This is an example of how the sACN network traffic looks in wireshark: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Network addresses in this example (port 5568 is sACN): | ||
+ | |||
+ | 2.0.0.1 - Titan PC Suite | ||
+ | 2.0.0.10 - MIDIMonster | ||
+ | 2.0.0.50 - the ' | ||
+ | 2.0.0.100 - the ' | ||
+ | | ||
+ | 239.255.0.1, | ||
+ | Packets from 2.0.0.1 to 239.255.0.1/ | ||
+ | Packets from 2.0.0.10 to 2.0.0.100 or 2.0.0.50 are the unicast sACN from MIDIMonster to the ' | ||
+ | | ||
+ | This is an example of how the mixed Art-Nt/sACN network traffic looks like in wireshark: | ||
+ | |||
+ | {{: | ||
+ | |||
+ | Network addresses in this example (port 5568 is sACN, port 4809 is Art-Net): | ||
+ | |||
+ | 2.0.0.1 - Titan PC Suite and MIDIMonster | ||
+ | 2.0.0.10 - the ' | ||
+ | 2.0.0.50 - the ' | ||
+ | 2.0.0.100 - the ' | ||
+ | | ||
+ | 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 ' | ||
+ | |||
+ | Btw. 224.0.0.180 is another special auto-generated address which is used by CITP... | ||
+ | |||
+ | ==== Another idea: Raspberry Pi ==== | ||
+ | And very finally: [[https:// |
tricks/sacn_unicast.1653399182.txt.gz · Last modified: 2022/05/24 13:33 by icke_siegen