Steven Seagal wrote:apparently Autoswitch overscan is less impressive than LaceScan overscan: 96 bytes/scanline in monochrome instead of 100, and only 224 bytes at 50hz, instead of 236!
To correct a previous (hasty) statement...
96 bytes instead of 100 isn't a big difference, and at 96*8= 768, hires was also above monitor specs, not to mention the little HSYNC problem.
But apparently you get 480 lines max, compared with 500 for Lacescan.
224 bytes in colour mode are more than enough to reach the maximal resolution, which is still determined by HBLANK.
The fact that it's 224 (divisible by 4) at 50hz or 60hz is a big advantage: no GEM problems!
Probably the GLUE clock was needed to stop DE at the right time, there must be a counter in the circuit, with a different threshold for monochrome and colour, hence the mono detect line.