There's a FMV player for the 8-bit Sega Master System ( https://github.com/bravesoftdz/tiler ,) which compresses to a fixed number of dynamically updated tiles. The codec in TFA and Tiler seem very similar, with Tiler also taking advantage of the SMS's ability to flip tiles horizontally or vertically.

A higher spec version of Tiler is available as TileMotion, which has a JavaScript demo decoding 1080p video in software here: https://gligli.github.io/tilemotion/demo/

Once you see the tile map of this in action, you realize how genius and simple this idea is. You can only update 32 tiles a frame but it can preload tiles in advance of them being displayed provided there is low enough motion and spare space to allocate.

Would love to see something like this ported to similar systems such as Amiga, Mega Drive and Neo Geo. All 68K, all tile based.

Also seeing that gameplay at the end, absolutely wonderful. Would not have figured it was even remotely possible on a system like that, but there it is.

Choosing 8×8 blocks is very likely highly suboptimal when it comes to the quality of the codec.

The point of the 4×2 tiles is exactly to avoid the blockiness artifacts of vector quantization (visible in the article).

Larger tiles increase the average error and entropy because of the way VQ works - it tries to find blocks that look like each other and then encode all similar blocks by referencing a single tile (usually choosing the "average" or "mode" the blocks).

As tiles grow larger, the chance to find highly similar blocks obviously decreases (and deviation from the representative tile increases).

Reducing one of the dimensions is probably better positioned on the quality-speed frontier.

I'm sure the effort is good, but the article is not. It reads like breathless corporate crap. It also doesn't have any video of this FMV, though what I see in the HTML source is an attempt to use a third-party site to embed youtube videos, which does nothing on Firefox.

Doesn't work:

    <iframe src="https://cdn.embedly.com/widgets/media.html?src=https%3A%2F%2Fwww.youtube.com%2Fembed%2FPhOa3KCE_nM%3Ffeature%3Doembed&amp;display_name=YouTube&amp;url=https%3A%2F%2Fwww.youtube.com%2Fwatch%3Fv%3DPhOa3KCE_nM&amp;image=https%3A%2F%2Fi.ytimg.com%2Fvi%2FPhOa3KCE_nM%2Fhqdefault.jpg&amp;type=text%2Fhtml&amp;schema=youtube" allowfullscreen="" frameborder="0" height="480" width="640" title="Command &amp; Conquer Intro on Atari ST" class="dr g ii al cs" scrolling="no"></iframe>

Let's go to the Youtube video it's meant to show: https://www.youtube.com/watch?v=PhOa3KCE_nM

Now let's put Youtube's direct embed code in there:

    <iframe width="560" height="315" src="https://www.youtube.com/embed/PhOa3KCE_nM?si=UfCxKD0RZbozo2BK" title="YouTube video player" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>

Now it works just fine.

This is a really cool project. That said, as genuine constructive feedback, I think it would be better if a bit more time was spent on improving the writing and prose of it.

I use LLMs to write too, and give it examples of my writing for style which gives a better starting base. Then I do at least a full copyedit pass, and usually rewrite (or shorten) at least 20-30% of the word count; until I’m happy to publish.

An increasing amount of writing following the same style, quirks, and relative lack of humanity makes reading and learning less engaging.

In case anyone wondering what the "famous" MOVEP instruction does, this:

    MOVE.L  #$AABBCCDD,D0
    MOVEP.L D0,(A0)

Writes to the 8 bytes pointed at by A0 in this format:

    AA xx BB xx CC xx DD xx

Where xx are bytes left as they are.

Something like this:

    MOVE.L  #$AABBCCDD,D0
    MOVE.L  #$11223344,D1
    MOVEP.L D0,(A0)
    MOVEP.L D1,1(A0)

Gives you this at the address pointed to by A0:

    AA 11 BB 22 CC 33 DD 44

I wanted to see how big the example clips encoded down to. Or is this just a technical test to see what it's capable of playing back, not an attempt to optimize the video size?

> Each 8×8 block is turned into a short DCT (Discrete Cosine Transform) feature vector; distance is measured there instead of raw pixels.

Was this your idea or the agent's? Because it feels peculiar to essentially describe JPEG, modulo the entropy coding, without mentioning its name. It was released in 1992 -- before C+C. Which makes me wonder why Westwood didn't just use JPEG too...

Fun fact, DCT's inventor: https://en.wikipedia.org/wiki/Nasir_Ahmed_(engineer)