From Jan Kundrát to ~martijnbraam/openatem
> When I do an apt search I do not see a libhandy-1 but I do see a > libhandy-1-0. installed that but still get the same error. You will need the -dev or -devel versions of these packages as well (i.e., not just the .so libraries, but also the .h, .pc,... files as well). With kind regards, Jan
From Jan Kundrát to ~martijnbraam/openatem
Since there are typically no server-side MQTT ACLs, this has to be enabled explicitly. There's some duplication of code between this implementation and the one in the HTTP backend. The most straightforward way of fixing that is to convert these early returns into proper exceptions, but I'm too lazy for this and I'm gonna be using this feature tomorrow :). Signed-off-by: Jan Kundrát <jkt@jankundrat.com> --- openswitcher_proxy/frontend_mqtt.py | 43 ++++++++++++++++++++++++++--- proxy.toml | 1 + 2 files changed, 40 insertions(+), 4 deletions(-) [message trimmed]
From Jan Kundrát to ~martijnbraam/openatem
This should be used carefully because it blindly propagates all fields, including possibly security-sensitive ones such as streaming keys. Connection to MQTT is currently neither authenticated not encrypted. On the other hand, this is super-useful for applications such as tally lights, yay! Signed-off-by: Jan Kundrát <jkt@jankundrat.com> --- build-aux/nl.brixit.Switcher.json | 2 +- openswitcher_proxy/__main__.py | 3 ++ openswitcher_proxy/frontend_mqtt.py | 54 +++++++++++++++++++++++++++++ proxy.toml | 7 +++- 4 files changed, 64 insertions(+), 2 deletions(-) [message trimmed]
From Jan Kundrát to ~martijnbraam/openatem
I'm writing a frontend which actually *connects* to an external server, so let's not make any assumptions here. The only downside is that we cannot easily print out what section of the config file is getting handled before we initialize its handler. I think this is better than calling a parameter for MQTT server's hostname to connect to "bind". Signed-off-by: Jan Kundrát <jkt@jankundrat.com> --- openswitcher_proxy/__main__.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/openswitcher_proxy/__main__.py b/openswitcher_proxy/__main__.py index 2a0779f..7dd4c07 100644 --- a/openswitcher_proxy/__main__.py [message trimmed]
From Jan Kundrát to ~martijnbraam/openatem
Jan Kundrát (2): proxy: do not assume all frontends "bind" somewhere proxy: add a read-only MQTT frontend build-aux/nl.brixit.Switcher.json | 2 +- openswitcher_proxy/__main__.py | 7 ++-- openswitcher_proxy/frontend_mqtt.py | 54 +++++++++++++++++++++++++++++ proxy.toml | 7 +++- 4 files changed, 66 insertions(+), 4 deletions(-) create mode 100644 openswitcher_proxy/frontend_mqtt.py -- 2.33.0
From Jan Kundrát to ~martijnbraam/openatem
Signed-off-by: Jan Kundrát <jkt@jankundrat.com> --- pyatem/field.py | 53 ++++++++++++++++++++++++++++++++++++++++++++++ pyatem/protocol.py | 2 ++ 2 files changed, 55 insertions(+) diff --git a/pyatem/field.py b/pyatem/field.py index 67e03af..d2cd92f 100644 --- a/pyatem/field.py +++ b/pyatem/field.py @@ -1560,6 +1560,59 @@ class FairlightTallyField(FieldBase): return '<fairlight-tally {}>'.format(self.tally) [message trimmed]
From Jan Kundrát to ~martijnbraam/openatem
The Atem Mini Extreme has got two AUX outputs ("HDMI OUT 1" and "HDMI
OUT 2"). Two of the inputs, HDMI1 and HDMI2, support a special "direct
mode" where they can be passed through to an HDMI output at a lower
latency (perhaps just via a HDMI retimer?). This is similar to the
original Atem Mini series where this was only supported for HDMI1. Now,
on the Extreme, HDMI1 can be low-latency-put to HDMI OUT 1, and the
HDMI2 can be passed through to HDMI OUT 2. This is a problem because the
code would not know the difference, and there was apparently just one
bit for the "can be sent to AUX" flag.
The catch is that on the Atem Mini Pro at least, the "can be sent to
HDMI OUT 1" bit is always 0, even on the newest FW. On the Atem Mini
Extreme, I have not seen any source with available_aux == 1 and
available_aux1 == available_aux2 == 0. The only sources where
[message trimmed]
From Jan Kundrát to ~martijnbraam/openatem
I'm seeing that particular port type not just for the Multiview output from the ME, and also for the "status displays" (audio, recording, streaming). Tested on the Atem Mini Extreme and Atem Mini Pro. Signed-off-by: Jan Kundrát <jkt@jankundrat.com> --- pyatem/field.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pyatem/field.py b/pyatem/field.py index 7c60605..7130cea 100644 --- a/pyatem/field.py +++ b/pyatem/field.py @@ -279,7 +279,7 @@ class InputPropertiesField(FieldBase): [message trimmed]
From Jan Kundrát to ~martijnbraam/openatem
Signed-off-by: Jan Kundrát <jkt@jankundrat.com> --- pyatem/field.py | 33 +++++++++++++++++++++++++++++++++ 1 file changed, 33 insertions(+) diff --git a/pyatem/field.py b/pyatem/field.py index 2277483..7c60605 100644 --- a/pyatem/field.py +++ b/pyatem/field.py @@ -2042,6 +2042,39 @@ class MultiviewerInputField(FieldBase): 5 1 bool Supports enabling the safe area overlay 6 2 ? unknown ====== ==== ====== =========== [message trimmed]
From Jan Kundrát to ~martijnbraam/openatem
Signed-off-by: Jan Kundrát <jkt@jankundrat.com> --- pyatem/command.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pyatem/command.py b/pyatem/command.py index 907fa69..1562e9a 100644 --- a/pyatem/command.py +++ b/pyatem/command.py @@ -37,7 +37,7 @@ class CutCommand(Command): class AutoCommand(Command): """ Implementation of the `DAut` command. This is equivalent to pressing the CUT button in the UI[message trimmed]