Search

Forum

Auto Patch Does Not Reset DMX Address on New Universe

 2 Replies
 0 Subscribed to this topic
 47 Subscribed to this forum
Sort:
Martin Designs
New Member
Posts: 1
New Member
  • Quote
  • Reply

I have encountered an issue with the Auto Patch function when assigning DMX addresses to multiple fixtures.

When the current universe becomes full and the dialog "Continue until the end?" appears, Capture correctly creates a new DMX universe. However, instead of restarting the DMX address at Address 1 in the new universe, it continues counting from the previous universe.

Actual Behavior

Actual:

  • Universe 1 – Address 469
  • Universe 2 – Address 74

as a result, the DMX patch becomes incorrect and requires manual correction.

Does anyone have this Issues? 

Thanks for the Support

Capture 2026 Ver. 2026.0.39

martinp
Advanced Member
Posts: 73
Advanced Member
  • Quote
  • Reply

In the options menu, how is the patch across universe boundarys set?  The default is on which would explain what you are seeing.

NotAnotherTom
New Member
Posts: 6
New Member
  • Quote
  • Reply

Yeah, this is due to the way Capture have implimented the "Patch fixtures across universe boundaries". It literally just continues the fixture across the two universes.

Obviously for traditional fixtures this doesn't really work, as we're generally using a copper 5 pin cable to get the signal to the fixture, and no fixtures are able to receive data even if you did find a way to mush it on to a single data + and data - pair.

This is mainly aimed at having larger pixel based installations or custom pixel tape fixtures, where you can only get 170 RGB pixels on each universe, but there are controllers that will receive multiple universes over artnet or sACN, and output that as a single pixl data stream, allowing much longer runs and more efficient cabling.

If you turn off the "Patch fixtures across universe boundaries" option in the universes tab, and then repatch the fixtures, it will patch them in the way you want them to be.

Personally I think that option should default to Off, otherwise it will make a mess more often than not.