derpeter

i see no reason not implement also WPE. If you want to try it yourself have a look at the video4linux plugin in the vocotmix2 branch. WPE sould be copy...

Thats a different layer of the problem. IMHO the core is the right place to figure out if recording is working or not, the question was how it figures that...

i would prefer to make it part of the gui as it should blink in sync with the overlay. otherwise it will make people crazy.

Could you explain where the benefit of including this into voctomix in favor of running a monitoring client in parallel is? As you probably want to monitor the whole system...

> What do you mean by "whole system"? > > With Prometheus monitoring, we already have extensive host monitoring with the [node_exporter](https://github.com/prometheus/node_exporter). We take a granular approach to keep things...

> The Prometheus client stuff I'm proposing inside voctomix is very specific. We just expose a couple of simple per-process metrics as "free" since the python client can easily gather...

regarding the meta data we may need a "meta data changed at" field. So if the "pre-recording" worker has already done its job (e.g. render a prerole) can be triggered...

Just for clarification: The worker would build the prerole, calculate a hash over the properties it uses and store that hash in new propertie? If thats the case i don't...

> > For me as an API consumer this sounds like this should be an operation with the meta ticket, even i'm aware that clients should not alter meta tickets...

> I would still suggest introducing a new ticket type that handles other video independent tasks like media publishing. I would also prefer to follow this path as it more...