Using a Net3 or Response Gateway for DMX Input with higher sACN priority

Issue

A Net3 DMX or Response DMX Gateway is configured as a DMX Input, and the "Port # Input Port Priority" is changed to a higher value, but the output port (on the same or another gateway) is still merging all sources as HTP. sACNview shows the packets coming from the Gateway are at priority 100. Is there a way to send sACN per-address priority at a higher value?

Cause of Issue & Solution

Yes, this can be changed in the Concert software. The reason this issue is occurring is the "Port # Input Port Priority" field changes the Per Universe priority value. The DMX Gateways are capable of sending unique Per Address priority of all 512 addresses individually, so one editable field is not sufficient. Thus Concert uses a different menu to set those values.

1. Right-click on the Gateway in Concert and choose 'Per-Address Priority'
2. In the window that opens, click on the port that needs to be configured. A big green arrow points to the currently selected port.
3. In the table below that you can edit individual values for each DMX Input Address, or you can:
   1. Click the [Set All...] button to change all 512 addresses to the same value
   2. Click the [Range Set] button to assign a common value to a continuous range of addresses
4. Click [Apply Changes] to save them.
5. If already in Live Edit the changes should automatically send to the Gateway, otherwise Send Device Configuration to upload changes to the Gateway.