Bugfix: DMX start code not set

Fixed a bug, where the DMX start code was not set on received packets (Thanks to @mthespian ! See #29 for more information).

Added DMX start code to DataPacket

Thanks to @mthespian, data packets now support the DMX start code present in DMX data. Previously, this code was limited to being 0x00.

See #27 for more information.

Performance improvements for receiving and sending

Due to a debugging statement, the sending and receiving hot paths were slower than necessary. The debugging statements were removed and the performance improved.

Note that this means the logging output will now be different (missing messages when a packet was send or received).

See #25 for more information and thanks to @shauneccles !

Exception on parsing DataPacket with non-DMX start code

Fix: When creating a DataPacket with invalid DMX start codes (i.e. not 0x00) an exception is thrown (Thanks to @niggiover9000 ! See #11 for more information)

Manual flush with only a subset of active universes

When using a manual flush, only a specified list of universes can be flushed (Thanks to @CrazyIvan359 ! See #22 for more information)

Custom universe for sync-packets

The universe used for the sACN-sync messages can now be set when creating a sACNsender (Thanks to @CrazyIvan359 ! See #21 for more information)

Fixed sequence number not increasing

The sequence number of the sync-packet when using a manual flush was not increased, but it should have been.

Thanks to @BlakeGarner for spoting this issue and submitting a pull-request (#19) for fixing!

Fix logging

The internal logging of the receiver_thread and output_thread was using the root logger instead of its module-logger.

Thanks to @mje-nz for the pull request solving this issue!

See #18 for more information.

Housekeeping for PyPI

This release only includes housekeeping for the PyPI automated release mechanism

Manual Flush

This release marks the addition of the manual-flush feature