Hundemeier

I don't know if I understood the question correctly, but the only way I can think of to change the universe of a listener is to unregister the listener and...

Even if it makes me seem rude, but I don't think this change should be made upstream into this library as is. I have several problems with it: 1. It...

> 1. E1.31 allows for alternate start codes ... Thanks for the additional resources! Since I never heared of the start code `0xDD` before, I surely will read and try...

If you are still up for it, you could now integrate your changes into the new sending implementation. I suggest inheriting from `output.py`, `sender.py` and `sender_handler.py`. This should be feasible...

> When `sender.manual_flush` is enabled, are the packets only sent when `sender.flush()` is called? Or does flush only send the sync packet? When `sender.flush()` is called, there is a for...

I think you just need to change one line: ```python import sacn import time HOST = 'localhost' PORT = 5569 # Whichever of these two is second fails with OSError:...

> is the sender always sending to the default port no matter the port parameter passed? Yes. The sender always sends out packets with a destination port of 5568. Sender:...

Sorry for the late reply: During thinking about your issue I am not totally sure if you simply spotted a "bug" in my Readme.md: the [example for receiving DMX data](https://github.com/Hundemeier/sacn?tab=readme-ov-file#receiving-1)...

Implementing a `bind_interface` parameter for `sACNreceiver` should not be any problem. However, did you encounter any issues on Linux when trying to receive multicast sACN packets? #42 suggests that it...