Options
Related

[DMX Processing) HES/Hog Widgets/DP's and sACN/Artnet

Can someone please confirm something for me....

During a conversation with a friend of mine who is also a console programmer, the topic of DMX processing power came up and we were at a slight disagreement, that will end up with one person buying numerous beers when the answer is found.

Questions..

1. Do the HES USB DMX widgets share any of the DMX processing load with the CPU of the console if no physical DP8000 is present on the Hognet.

2. Does a DP8000 on the Hognet process DMX data for a HES widget that is connected via the consoles USB port and patched to the DP on the hognet? Or, must the widget be plugged into the DP's USB port for the DP to process the DMX data?

3. Does the H4 Console contain an actual DP8000 that does all the DMX processing, or is it another Virtual DP where the DMX data is processed through the consoles CPU?

4. Does the FB4 only have a Virtual DP, or is there a partial DMX processor in there?

Thanks

;)

JB
Parents
  • 0
    Interesting Marc,

    I thought that .........


    Any DMX processing from a USB widget is done from the patched DP, whether it be virtual or actual, onboard or offboard.... regardless of where in the USB buss the physical connection is. After all, USB is suposed to be just an interconnecting buss designed for extremely low latency.

    I also assumed that the difference between a virtual and actual DP was simply that, an actual DP has it' own CPU and memory that would do it's own DMX processing for it's own "Patch", where a virtual DP would do it's "DMX Patch" processing on the consoles shared cpu and memory regardless of where in the network (USB or Ethernet) it's plugged in at.

    I also thought that the H4 console does have it's own DP seperate from the console CPU. Thus giving it two seperate CPU's, one to run the 16 universes (8 onboard + 8 Offboard (widgets) or sACN/Artnet)) and one to run the console. The H4 internal DP is just built in to the console case and probably on the PCIe, or USB buss thus no reason to define it as a seperate network device (Change the IP). Where as the FB and RH don't have a seperate DP built into the console, thus the onboard CPU (Virtual DP) is running the widgets..


    Thanks for your insight Marc.. I guess I'm gonna need to pick up the bar bill next friday..

    :)

    JB
Reply
  • 0
    Interesting Marc,

    I thought that .........


    Any DMX processing from a USB widget is done from the patched DP, whether it be virtual or actual, onboard or offboard.... regardless of where in the USB buss the physical connection is. After all, USB is suposed to be just an interconnecting buss designed for extremely low latency.

    I also assumed that the difference between a virtual and actual DP was simply that, an actual DP has it' own CPU and memory that would do it's own DMX processing for it's own "Patch", where a virtual DP would do it's "DMX Patch" processing on the consoles shared cpu and memory regardless of where in the network (USB or Ethernet) it's plugged in at.

    I also thought that the H4 console does have it's own DP seperate from the console CPU. Thus giving it two seperate CPU's, one to run the 16 universes (8 onboard + 8 Offboard (widgets) or sACN/Artnet)) and one to run the console. The H4 internal DP is just built in to the console case and probably on the PCIe, or USB buss thus no reason to define it as a seperate network device (Change the IP). Where as the FB and RH don't have a seperate DP built into the console, thus the onboard CPU (Virtual DP) is running the widgets..


    Thanks for your insight Marc.. I guess I'm gonna need to pick up the bar bill next friday..

    :)

    JB
Children
No Data

www.etcconnect.com