I was playing with an advatek controller and using a dmxOUTCHOP to send multiple universes to it. Normally I would use the ‘packet per channel’ format and sending multiple universes at once. It looks like that the update of 2023.12230 broke something since from that version onwards the output lags enormously (like leds being only updated after more than a second).
When using multiple dmxOUT CHOPs set to ‘packet per sample’ seems to work fine and doesn’t lag at all.
My guess is that it has something to do with this update:
‘Dmx out chop: Fixed incorrect send rate for channels after the first when using the Packet Per Channel format.’
Is there perhaps a workaround besides having multiple dmxoutCHOPs? And is this a bug or am I missing something?
I found a recent regression due to the aforementioned send rate change. The DMX Out CHOP isn’t respecting the value of the rate parameter in Packet Per Channel mode and is sending out at the timeline rate.
Is your timeline rate higher than the Advatek controller refresh rate, and the rate on the DMX Out CHOP? It could be that it’s sending at too high of a rate and filling up the controller’s buffer, introducing latency. If that’s what’s happening then lowering your timeline rate to match the DMX Out CHOP par value/controller refresh rate should work-around the bug.
Thanks for checking. Unfortunately, I don’t have the advatek controller here anymore, so I can’t test it with the latest stable. I did make a little tox when I was testing to have a proof of concept that did work in the old version, but not in the 2023.12370 version. The rate is set to me.time.rate so equal to the timeline rate.
If there is something I can ask to test, let me know. Perhaps the latest 2025 stable? Not sure anything changed there concerning the dmxoutCHOP.
Cheers,
tim
ps. attached tox file is very simple, but give this lagging behaviour with the advatek controller. Not visible in the patch, but the output lags on the ledstrips when connected.
There’s been a few fixes to the DMX Out CHOP in the latest 2025.30000 series of builds (though not directly related to this issue), so I’d say it’s worth testing. I’m also curious to know if you experience the same behavior with the DMX Out POP.
