If I recall correctly, the "Always Transmit Data" option was added specifically for this scenario, but that was before we had the new threaded Channel Output classes. We could possibly enhance the ChannelOutputBase class to allow a subclass to indicate that its output thread should start at startup and always stay running. Currently the Channel Output threads are spun up on demand and torn down when there is no output needed (ie, no sequence, effect, pixel overlay, testing, etc.) I'd want to think through the ramifications though. Some users may not want DMX output on all the time, they could be relying on the current functionality to put their controller into test mode. "Always Transmit" could be a flag in the channel output setup rather than a global flag.