What it does
I wrote them for cartridge, which runs a libretro core as an FFGL source inside Resolume, but there's nothing cartridge-specific in them. They're ordinary ROMs and they'll run in anything.
The point of a moving test card over a static one is that every panel has motion you can count: a marker stepping one cell per emulated frame, a bar moving one pixel per frame, a square inverting every frame. A dropped or repeated frame doesn't show at all in a static pattern, and it's obvious in these. The overscan display gives you a number, 'the path is eating 6 pixels off the left', instead of 'it looks a bit off'.
- testcard — colour bars, crosshatch, frequency burst and countable per-frame motion
- inputtest — the platform's own pad, with controls that latch once seen
- overscan — nested safe areas and ruler ticks, with asymmetric corner markers
- Everything original under MIT: no console BIOS, no commercial ROM
- Found that cores disagree about the NES picture: three return 256x240, QuickNES returns 240x224
Where it stands
In development, and moving quickly. All seven targets build and six are verified, which here means the ROMs were run in an emulator core and somebody looked at the frames, not just that they assembled. The C64 ROMs are built and structurally checked but have never been run, because every C64 emulator needs a BIOS and I'm not shipping one. Nothing has been run on real console hardware, and the GBA ROMs can't be: the logo field a real BIOS checks is Nintendo's artwork, so it's zeroed on purpose.