Tally Data Recording (and possible uses)

[hrueger]

We originally had the recording of Tally Data in place (next to the logs in the settings panel) and this is still in place.
However, I'd like to record tally data in a machine-readable and persistent way.

I suggest that we store the tally data as JSON somewhere on the disk (timestamps, addresses, busses, device ids) and render this JSON data in the UI. We could have multiple ways of rendering:

• Plain Text (like it is currently)
• some sort of timeline
• statistics (which camera was on air most of the time, etc)

What do you think?

I also have the idea (but I don't know if it is out of scope of TA) that we could generate a MultiView Project File for DaVinci Resolve from the Tally Data, just like the ATEM Mini Pro ISO and the ATEM Mini Extreme ISO do. In case you don't know, they record all cameras to separate files, keep track of the cuts you do on the ATEM and then generate a DaVinci Resolve Project file with all the video tracks and cuts on the exact timestamps where you did them live. This allows for post production to just change a few cuts and export the video again.
However, this is not possible on the other ATEM models as they don't do separate recordings or recordings at all. I thought about using Hyperdecks for this. TA would need to know when the HyperDeck recording started in order to align the video tracks in the project file.

A DaVinci Resolve Project file is not hard to generate as it is just basic XML.

In my opinion this would be a great and useful feature but as I said earlier, maybe it is out of scope?

[MatteoGheza]

• some sort of timeline
• statistics (which camera was on air most of the time, etc)

I also have the idea (but I don't know if it is out of scope of TA) that we could generate a MultiView Project File for DaVinci Resolve from the Tally Data, just like the ATEM Mini Pro ISO and the ATEM Mini Extreme ISO do.

Great ideas!
I think that having stats of which camera was on air most of the time would be fantastic!

[hrueger]

Then TallyArbiter would probably need some way of knowing when the event / stream / etc starts and ends, because (at least I work like that) you'd setup everything first and test it and that should not be included in the statistics.
Could be something like markers in a timeline?

This would also be needed for the DaVinci Resolve project generation thing.

[MatteoGheza]

I think we can add new buttons for starting the "timeline" (in a new section of settings).
We can use source "recording/streaming" status ({{RECORDING}} and {{STREAMING}}), too.

[MatteoGheza]

We can add a section "Timeline" were we display a real-time-updated timeline with buttons for starting and stopping the "event", and some inputs for name and description.

[hrueger]

I like that 👍

[josephdadams]

Love this. Sort of what I was thinking with #199. Would be a great feature!