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
    The DP8k launches a process we simply call the "OB" (output board)..

    On all desks with DMX output, we also launch pretty much the same OB process. It does get a bit of process priority but it sharing processing with console operations. We feel we have enough processing capacity on Hog4 to maintain our output/feedback performance benchmarks while not impacting the user's input/feedback.

    The actual output devices (widgets, acn, artnet, etc, super duper widget) are really just simple plugins to the engine.. We don't care how the outputs are mapped.. The engine is the same regardless.

    It is a bit of a balancing act and each show is different but our performance benchmarks are checked with each build to ensure we have not created bottlenecks on the console's.

    I hope this helps
Reply
  • 0
    The DP8k launches a process we simply call the "OB" (output board)..

    On all desks with DMX output, we also launch pretty much the same OB process. It does get a bit of process priority but it sharing processing with console operations. We feel we have enough processing capacity on Hog4 to maintain our output/feedback performance benchmarks while not impacting the user's input/feedback.

    The actual output devices (widgets, acn, artnet, etc, super duper widget) are really just simple plugins to the engine.. We don't care how the outputs are mapped.. The engine is the same regardless.

    It is a bit of a balancing act and each show is different but our performance benchmarks are checked with each build to ensure we have not created bottlenecks on the console's.

    I hope this helps
Children
No Data

www.etcconnect.com