Add MITT

[d-albrecht]

Added animation file for "Matt's Infotainment Two-Thousand"

Last year Matt was a bit disappointed that the animation of the so-called scanner of one of the main "characters" of David Hasselhoff's '90s show wasn't working. As I have some fond memories of this TV show myself (and my main animation project seems done so far), I jumped deep into this rabbit hole of information and legends. Turns out that the animation isn't just a moving light or line. There is much more... These are eight individual halogen lights that more or less turn on immediately, but they have some afterglow and that is what makes the light sequence so special/iconic.

I'm not a electronics engineer or chemist by any means, so I approached the task more programmatically and tweaked the parameters until it looked good. Actual halogen bulbs might look totally different but for the sake of a (quite low-res) Christmas tree, this should look just fine.
see generator-source
see simulator example
If your simulator can handle the (still in pull-request-state) feature of variable frame times (a.k.a. if the simulator ignores the first column), you can link to this animation. If not, then this file might break your simulator. Honestly, I could have done this without the new variable frame times, because the animation doesn't actually use them, but at least once I wanted to try to give Matt's tree a hint of the desired animation speed. If the tree is quicker, my animation will still be at around 30 fps.

I guess no-one would have come after me for using the name "KITT" but I liked he idea of making this a more standupmaths and Christmas themed animation, hence the different color choice and the new name.

[oliverdunk]

Hey @d-albrecht 👋 Since we haven't settled on a solution for variable frame times, did you want to upload a version without that column? It seems to run ok at https://santiagodg.github.io/mptree/ but I can't promise the extra column would work on the tree.

All of that said - the effect looks great! Like your detailed writeup too.

[d-albrecht]

Honestly, I could but I don't want to right now. The thing here is, that I used the first column for this trick. If the python code ignores this column completely, then the frame timings should just get ignored, too, and the remaining file content is 100% compatible with the default format definition.

I chose to implement it that way to exactly prevent cases where the format isn't compatible. If the old runner-code is used then the first column is ignored (and the frame timings is whatever the RPi can manage to achieve), and if the new runner-code is used then the frame timings are used to achieve a specific animation speed. The only incompatibilities I had were with some tree simulators that checked the file more thoroughly than the python-code ever did (hence established their own format definitions).

So, I'm pretty sure, that this animation will work no matter what (unless you use a completely different runner-code that assumes another, different format definition). In that sense, this version is just as close to the format definition than a not-timed animation would be. Hence, please just go ahead and merge.