Description
Since the code is open source, the custom hashing algorithm is easy to write in another language, the main config file (.vha2) is json, and the thumbnails/clips/filmstrips are live in predictable places with predictable file formats I think there's some benefit to offloading future "obscure" or "limiting" features to a simple 3rd party api that you expose from vha.
For example, if someone wants to regenerate all the clips using some custom nonsense they write (I'm speaking very much about myself here) or change the thumbnail of a clip every day using a custom thumbnail gen thing, this is all pretty doable by outputting different, but compliant, mp4/jpg at the correct location.
But we then need a way to send a signal to the app saying "things have change for hash X or video Y or whatever" if we want that update reflected at runtime.
An exposed API interface, or an ability to send and send messages to vha stdin or something similar to would open up the app.
Some of the other issues I've seen (like people who run vha on a separate server but use it on a different client) could be facilitated by opening up this framework.
TLDR: provide a way to send signals to a running VHA app (tcp port/rest api/stdin/etc) to let it know an external program has updated the state of:
- the json definition of a clip
- the thumbnail/clip/filmstrip of a clip
Once the signal is received it should "reload" that info from disk, or do a cache invalidation, or reload it however makes the most sense on your end.