For a Gigatron 'Virtual' Screen:
The source of bytes to output is 4 bytes, horizontally,and then 2 bytes of 'time'.
That means after the 4 pixels, is a link, to be loaded, into the 'X' register. So, first the new index is read, into Accumulator. Next, the 'X' register is over-written with a 'new' index; of course often the identical value.
So, in time measured as '160' byte actions, I figured 26 bursts, of 4 (actual) pixels, at 6 bytes each...or 5 bytes. I kind of hesitate to have to track stuff, such as 6 bytes worth of (video) time, but actual 5 real bytes of substance (per burst of 4 pixels).
My question, not an expert, is it possible, as two pixel times are default 'blank' or no output; Can the two instructions, to load new index to ACC. Plus save the ACC. to X. Can that also output some default, like
light grey, during each horiz 'neglected' 2 pixels.
At any rate: Exciting part is, you get 100 bytes, up top, for SPRITES, animated at 16 X 16.
By messing with the links, you can 'link' the playback for interrupting expected flow, if that makes sense.
The SPRITE itself, holds control of how many bursts of 4 pixels are the movable SPRITE raster for immediate video output.
The mapping, of Virtual Screen, is each ROW at 256.
(Not 160).