@Lars Kemmann:Thanks Lars, we've been going through a similar thought process ourselves and plan to add a status very similar to what you describe ![]()
We can't do the ETA accurately, since it is dependent on too many factors (network bandwidth at the event location, backlog of editing/conversion, etc.) ... basically by the time we'd know an ETA it would be moments from making it available. We will see what we can do though.