bmdwire 1.1.0__tar.gz

bmdwire-1.1.0/LICENSE

@@ -0,0 +1,15 @@
+bmdwire is one distribution carrying four differently licensed packages.
+Each package directory holds the licence that governs everything under it,
+and an installed copy ships all of them:
+
+  atemwire/       LGPL-3.0-only  (a fork of pyatem; see atemwire/LICENSE,
+                                  atemwire/LICENSE-gpl3.txt and atemwire/NOTICE)
+  hyperdeckwire/  MIT            (hyperdeckwire/LICENSE)
+  ultimattewire/  MIT            (ultimattewire/LICENSE)
+  videohubwire/   MIT            (videohubwire/LICENSE)
+
+Everything else in this repository (the workflows, this file, the brand
+assets under docs/) is MIT, Copyright (c) 2026 Lucas Romanenko.
+
+Not affiliated with or endorsed by Blackmagic Design Pty Ltd. ATEM,
+HyperDeck, Ultimatte and Videohub are trademarks of Blackmagic Design.

bmdwire-1.1.0/PKG-INFO

@@ -0,0 +1,92 @@
+Metadata-Version: 2.4
+Name: bmdwire
+Version: 1.1.0
+Summary: Python libraries for Blackmagic Design broadcast devices: ATEM switchers, HyperDeck recorders, Ultimatte keyers and Videohub routers
+Author: Lucas Romanenko, Martijn Braam and the OpenAtem contributors
+License-Expression: LGPL-3.0-only AND MIT
+Project-URL: Repository, https://github.com/lucas-romanenko/bmdwire
+Project-URL: Issues, https://github.com/lucas-romanenko/bmdwire/issues
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Development Status :: 4 - Beta
+Classifier: Operating System :: OS Independent
+Classifier: Topic :: Multimedia :: Video
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: atemwire/LICENSE
+License-File: atemwire/LICENSE-gpl3.txt
+License-File: atemwire/NOTICE
+License-File: hyperdeckwire/LICENSE
+License-File: ultimattewire/LICENSE
+License-File: videohubwire/LICENSE
+Provides-Extra: images
+Requires-Dist: pillow; extra == "images"
+Provides-Extra: test
+Requires-Dist: pytest; extra == "test"
+Requires-Dist: pytest-timeout; extra == "test"
+Requires-Dist: pillow; extra == "test"
+Dynamic: license-file
+
+<p align="center"><img src=".github/banner.png" alt="bmdwire: Python libraries for Blackmagic Design broadcast devices. One package, four device families, one version." width="100%"></p>
+
+Python libraries for Blackmagic Design broadcast devices: one package, one version, four device families.
+
+[![CI](https://github.com/lucas-romanenko/bmdwire/actions/workflows/ci.yml/badge.svg)](https://github.com/lucas-romanenko/bmdwire/actions/workflows/ci.yml) [![PyPI](https://img.shields.io/pypi/v/bmdwire.svg?label=pypi)](https://pypi.org/project/bmdwire/) ![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)
+
+```sh
+pip install bmdwire
+```
+
+| Import | Purpose | License | Docs |
+|---|---|---|---|
+| **`atemwire`** | ATEM switchers: the native UDP protocol, a connection pool, macro bytecode, "Save Switcher State" profiles | LGPL-3.0-only | [atemwire/README.md](atemwire/README.md) |
+| **`hyperdeckwire`** | HyperDeck recorders: transport control and clip listing over TCP 9993, clip upload over FTP | MIT | [hyperdeckwire/README.md](hyperdeckwire/README.md) |
+| **`ultimattewire`** | Ultimatte 12 keyers: archive and restore over the native TCP protocol, Smart Remote 4 compatible zips | MIT | [ultimattewire/README.md](ultimattewire/README.md) |
+| **`videohubwire`** | Videohub routers: state snapshot, crosspoint routing, labels over TCP 9990 | MIT | [videohubwire/README.md](videohubwire/README.md) |
+
+All four are pure standard library except atemwire, whose small C extension ships prebuilt for Linux, macOS and Windows on CPython 3.10 to 3.14, so installing needs no compiler. Pin the version in a requirements file (`bmdwire==1.1.0`) so a later release cannot change your install under you.
+
+## atemwire stands on pyatem
+
+**atemwire is a fork of [pyatem](https://git.sr.ht/~martijnbraam/pyatem) by
+Martijn Braam and the OpenAtem contributors.** Years of reverse engineering
+the ATEM protocol came before any of this, and that work is what made the
+rest possible. It branched at upstream commit `8f45831` (2026-03-14) and was
+then developed for months against live switchers: transport reliability
+fixes, a declarative wire-format layer, corrected and extended message
+coverage, macro upload, and profile save and restore.
+
+The licence is unchanged and not negotiable: **LGPL-3.0-only**, the same as
+upstream. Improvements to atemwire stay open, as they should. The other three
+libraries here were written from scratch and are MIT. The distribution's
+licence expression is `LGPL-3.0-only AND MIT`, and each package directory
+carries the text that governs it.
+
+If you want the original rather than this fork, it is at
+<https://git.sr.ht/~martijnbraam/pyatem> and it is still maintained.
+
+## Why one package
+
+The four libraries share an author, a shape and a purpose: they are the device layer of one broadcast control application, extracted and published so others can use them. Until 1.0.x each was its own PyPI project with its own version number. Nothing downstream ever wanted them apart, and four numbers to track for one release train was confusion with no benefit, so since 1.1.0 they are one distribution: one tag, one version, one line to pin. The import names did not change.
+
+The four old names stay on PyPI at their last 1.0.x release and are not updated. They are not shims either, on purpose: a release of `atemwire` that depended on bmdwire would break `pip install -U atemwire`, because pip installs the dependency first and then removes the old package's files, which are the same paths bmdwire just wrote. **If an environment already has any of the four old packages, uninstall them before installing bmdwire** (`pip uninstall atemwire hyperdeckwire ultimattewire videohubwire`). Two distributions owning one module directory work until one of them is uninstalled. A fresh virtualenv, a pipx install or a container build never has this problem.
+
+## Development
+
+```sh
+git clone https://github.com/lucas-romanenko/bmdwire.git
+cd bmdwire
+pip install -e ".[test]"      # builds atemwire's C extension in place, needs a compiler
+python -m pytest
+```
+
+The editable install matters: a plain `pip install .` puts the extension in site-packages, and `python -m pytest` run from the checkout then imports the source tree without it and fails on `atemwire.mediaconvert`. The suite needs no hardware. CI runs it on Python 3.10, 3.12 and 3.14 for every push and pull request, and builds an sdist and a wheel to prove the metadata.
+
+A release is a tag `v<version>` on `main` whose version equals `project.version` in `pyproject.toml`; pushing it builds the sdist and the wheels and publishes them to PyPI. `pip show bmdwire`, not a hand-typed number, is how to know what is installed.
+
+Not affiliated with or endorsed by Blackmagic Design Pty Ltd. ATEM, HyperDeck, Ultimatte and Videohub are trademarks of Blackmagic Design.

bmdwire-1.1.0/README.md

@@ -0,0 +1,58 @@
+<p align="center"><img src=".github/banner.png" alt="bmdwire: Python libraries for Blackmagic Design broadcast devices. One package, four device families, one version." width="100%"></p>
+
+Python libraries for Blackmagic Design broadcast devices: one package, one version, four device families.
+
+[![CI](https://github.com/lucas-romanenko/bmdwire/actions/workflows/ci.yml/badge.svg)](https://github.com/lucas-romanenko/bmdwire/actions/workflows/ci.yml) [![PyPI](https://img.shields.io/pypi/v/bmdwire.svg?label=pypi)](https://pypi.org/project/bmdwire/) ![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue.svg)
+
+```sh
+pip install bmdwire
+```
+
+| Import | Purpose | License | Docs |
+|---|---|---|---|
+| **`atemwire`** | ATEM switchers: the native UDP protocol, a connection pool, macro bytecode, "Save Switcher State" profiles | LGPL-3.0-only | [atemwire/README.md](atemwire/README.md) |
+| **`hyperdeckwire`** | HyperDeck recorders: transport control and clip listing over TCP 9993, clip upload over FTP | MIT | [hyperdeckwire/README.md](hyperdeckwire/README.md) |
+| **`ultimattewire`** | Ultimatte 12 keyers: archive and restore over the native TCP protocol, Smart Remote 4 compatible zips | MIT | [ultimattewire/README.md](ultimattewire/README.md) |
+| **`videohubwire`** | Videohub routers: state snapshot, crosspoint routing, labels over TCP 9990 | MIT | [videohubwire/README.md](videohubwire/README.md) |
+
+All four are pure standard library except atemwire, whose small C extension ships prebuilt for Linux, macOS and Windows on CPython 3.10 to 3.14, so installing needs no compiler. Pin the version in a requirements file (`bmdwire==1.1.0`) so a later release cannot change your install under you.
+
+## atemwire stands on pyatem
+
+**atemwire is a fork of [pyatem](https://git.sr.ht/~martijnbraam/pyatem) by
+Martijn Braam and the OpenAtem contributors.** Years of reverse engineering
+the ATEM protocol came before any of this, and that work is what made the
+rest possible. It branched at upstream commit `8f45831` (2026-03-14) and was
+then developed for months against live switchers: transport reliability
+fixes, a declarative wire-format layer, corrected and extended message
+coverage, macro upload, and profile save and restore.
+
+The licence is unchanged and not negotiable: **LGPL-3.0-only**, the same as
+upstream. Improvements to atemwire stay open, as they should. The other three
+libraries here were written from scratch and are MIT. The distribution's
+licence expression is `LGPL-3.0-only AND MIT`, and each package directory
+carries the text that governs it.
+
+If you want the original rather than this fork, it is at
+<https://git.sr.ht/~martijnbraam/pyatem> and it is still maintained.
+
+## Why one package
+
+The four libraries share an author, a shape and a purpose: they are the device layer of one broadcast control application, extracted and published so others can use them. Until 1.0.x each was its own PyPI project with its own version number. Nothing downstream ever wanted them apart, and four numbers to track for one release train was confusion with no benefit, so since 1.1.0 they are one distribution: one tag, one version, one line to pin. The import names did not change.
+
+The four old names stay on PyPI at their last 1.0.x release and are not updated. They are not shims either, on purpose: a release of `atemwire` that depended on bmdwire would break `pip install -U atemwire`, because pip installs the dependency first and then removes the old package's files, which are the same paths bmdwire just wrote. **If an environment already has any of the four old packages, uninstall them before installing bmdwire** (`pip uninstall atemwire hyperdeckwire ultimattewire videohubwire`). Two distributions owning one module directory work until one of them is uninstalled. A fresh virtualenv, a pipx install or a container build never has this problem.
+
+## Development
+
+```sh
+git clone https://github.com/lucas-romanenko/bmdwire.git
+cd bmdwire
+pip install -e ".[test]"      # builds atemwire's C extension in place, needs a compiler
+python -m pytest
+```
+
+The editable install matters: a plain `pip install .` puts the extension in site-packages, and `python -m pytest` run from the checkout then imports the source tree without it and fails on `atemwire.mediaconvert`. The suite needs no hardware. CI runs it on Python 3.10, 3.12 and 3.14 for every push and pull request, and builds an sdist and a wheel to prove the metadata.
+
+A release is a tag `v<version>` on `main` whose version equals `project.version` in `pyproject.toml`; pushing it builds the sdist and the wheels and publishes them to PyPI. `pip show bmdwire`, not a hand-typed number, is how to know what is installed.
+
+Not affiliated with or endorsed by Blackmagic Design Pty Ltd. ATEM, HyperDeck, Ultimatte and Videohub are trademarks of Blackmagic Design.

bmdwire-1.1.0/atemwire/LICENSE

@@ -0,0 +1,165 @@
+                   GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 3, 29 June 2007
+
+ Copyright (C) 2007 Free Software Foundation, Inc. <https://fsf.org/>
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+
+  This version of the GNU Lesser General Public License incorporates
+the terms and conditions of version 3 of the GNU General Public
+License, supplemented by the additional permissions listed below.
+
+  0. Additional Definitions.
+
+  As used herein, "this License" refers to version 3 of the GNU Lesser
+General Public License, and the "GNU GPL" refers to version 3 of the GNU
+General Public License.
+
+  "The Library" refers to a covered work governed by this License,
+other than an Application or a Combined Work as defined below.
+
+  An "Application" is any work that makes use of an interface provided
+by the Library, but which is not otherwise based on the Library.
+Defining a subclass of a class defined by the Library is deemed a mode
+of using an interface provided by the Library.
+
+  A "Combined Work" is a work produced by combining or linking an
+Application with the Library.  The particular version of the Library
+with which the Combined Work was made is also called the "Linked
+Version".
+
+  The "Minimal Corresponding Source" for a Combined Work means the
+Corresponding Source for the Combined Work, excluding any source code
+for portions of the Combined Work that, considered in isolation, are
+based on the Application, and not on the Linked Version.
+
+  The "Corresponding Application Code" for a Combined Work means the
+object code and/or source code for the Application, including any data
+and utility programs needed for reproducing the Combined Work from the
+Application, but excluding the System Libraries of the Combined Work.
+
+  1. Exception to Section 3 of the GNU GPL.
+
+  You may convey a covered work under sections 3 and 4 of this License
+without being bound by section 3 of the GNU GPL.
+
+  2. Conveying Modified Versions.
+
+  If you modify a copy of the Library, and, in your modifications, a
+facility refers to a function or data to be supplied by an Application
+that uses the facility (other than as an argument passed when the
+facility is invoked), then you may convey a copy of the modified
+version:
+
+   a) under this License, provided that you make a good faith effort to
+   ensure that, in the event an Application does not supply the
+   function or data, the facility still operates, and performs
+   whatever part of its purpose remains meaningful, or
+
+   b) under the GNU GPL, with none of the additional permissions of
+   this License applicable to that copy.
+
+  3. Object Code Incorporating Material from Library Header Files.
+
+  The object code form of an Application may incorporate material from
+a header file that is part of the Library.  You may convey such object
+code under terms of your choice, provided that, if the incorporated
+material is not limited to numerical parameters, data structure
+layouts and accessors, or small macros, inline functions and templates
+(ten or fewer lines in length), you do both of the following:
+
+   a) Give prominent notice with each copy of the object code that the
+   Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the object code with a copy of the GNU GPL and this license
+   document.
+
+  4. Combined Works.
+
+  You may convey a Combined Work under terms of your choice that,
+taken together, effectively do not restrict modification of the
+portions of the Library contained in the Combined Work and reverse
+engineering for debugging such modifications, if you also do each of
+the following:
+
+   a) Give prominent notice with each copy of the Combined Work that
+   the Library is used in it and that the Library and its use are
+   covered by this License.
+
+   b) Accompany the Combined Work with a copy of the GNU GPL and this license
+   document.
+
+   c) For a Combined Work that displays copyright notices during
+   execution, include the copyright notice for the Library among
+   these notices, as well as a reference directing the user to the
+   copies of the GNU GPL and this license document.
+
+   d) Do one of the following:
+
+       0) Convey the Minimal Corresponding Source under the terms of this
+       License, and the Corresponding Application Code in a form
+       suitable for, and under terms that permit, the user to
+       recombine or relink the Application with a modified version of
+       the Linked Version to produce a modified Combined Work, in the
+       manner specified by section 6 of the GNU GPL for conveying
+       Corresponding Source.
+
+       1) Use a suitable shared library mechanism for linking with the
+       Library.  A suitable mechanism is one that (a) uses at run time
+       a copy of the Library already present on the user's computer
+       system, and (b) will operate properly with a modified version
+       of the Library that is interface-compatible with the Linked
+       Version.
+
+   e) Provide Installation Information, but only if you would otherwise
+   be required to provide such information under section 6 of the
+   GNU GPL, and only to the extent that such information is
+   necessary to install and execute a modified version of the
+   Combined Work produced by recombining or relinking the
+   Application with a modified version of the Linked Version. (If
+   you use option 4d0, the Installation Information must accompany
+   the Minimal Corresponding Source and Corresponding Application
+   Code. If you use option 4d1, you must provide the Installation
+   Information in the manner specified by section 6 of the GNU GPL
+   for conveying Corresponding Source.)
+
+  5. Combined Libraries.
+
+  You may place library facilities that are a work based on the
+Library side by side in a single library together with other library
+facilities that are not Applications and are not covered by this
+License, and convey such a combined library under terms of your
+choice, if you do both of the following:
+
+   a) Accompany the combined library with a copy of the same work based
+   on the Library, uncombined with any other library facilities,
+   conveyed under the terms of this License.
+
+   b) Give prominent notice with the combined library that part of it
+   is a work based on the Library, and explaining where to find the
+   accompanying uncombined form of the same work.
+
+  6. Revised Versions of the GNU Lesser General Public License.
+
+  The Free Software Foundation may publish revised and/or new versions
+of the GNU Lesser General Public License from time to time. Such new
+versions will be similar in spirit to the present version, but may
+differ in detail to address new problems or concerns.
+
+  Each version is given a distinguishing version number. If the
+Library as you received it specifies that a certain numbered version
+of the GNU Lesser General Public License "or any later version"
+applies to it, you have the option of following the terms and
+conditions either of that published version or of any later version
+published by the Free Software Foundation. If the Library as you
+received it does not specify a version number of the GNU Lesser
+General Public License, you may choose any version of the GNU Lesser
+General Public License ever published by the Free Software Foundation.
+
+  If the Library as you received it specifies that a proxy can decide
+whether future versions of the GNU Lesser General Public License shall
+apply, that proxy's public statement of acceptance of any version is
+permanent authorization for you to choose that version for the
+Library.