
http://ae.dhs.nu/tmp/oversc.zip
/Troed
Cool, thanks. I only have a single ST, and it would be a pain in the butt for me to put it back to 'stock' to test things. I've been relying on Steem to be my ST reference point. There is the "blank" signal from the glue which I haven't looked at; perhaps it's involved.troed wrote: ↑Wed Jan 03, 2018 11:26 amI think testing with Hatari instead of STEem might help here. The current wakestate-code in STEem isn't really emulating the hardware but more of an in-between thing that works with the code that has already been published and tested. I'm quite sure Spectrum 512 has a uniform border color.
This is excellent. Exactly what I need - thanks again Troed. Your help is always invaluableI'm guessing left/right is of most interest? I believe I have some code by Evil/DHS that only displays a fullscreen, made for calculating number of visible lines. Both ST (230 byte) and STE-specific (224 byte) line variants.Can anyone suggest a program that displays a static image that extends into the overscan area? Preferably something that lets you specify which image, a picture viewer for example. With demos, there's usually crap flying everywhere and it's really hard to see what's going on.
What precisely does Hatari emulate better?
AFAIK Spectrum 512 works in Steem SSE, I think the rasters in the borders are quite normal.I think testing with Hatari instead of STEem might help here. The current wakestate-code in STEem isn't really emulating the hardware but more of an in-between thing that works with the code that has already been published and tested. I'm quite sure Spectrum 512 has a uniform border color.
I know I say it a lot lately, but... Steem doesn't display a black bar at that point, surely a real Atari displays continuous low-res pixels through the entire scanline without a gap?troed wrote: ↑Sat Jan 06, 2018 1:26 pmThe Shifter switches to the mono output pin and not RGB when in mono mode, effectively displaying black during that time. The Shifter does have it's own copy of RES but it takes effect "immediately" (4 cycle aligned).
You might be interested in some signal captures I'm doing at the moment: http://atari-forum.com/viewtopic.php?f=15&t=32918
Nope
Could you please post you scope shots in a thread maybe in member blog section
Whoa, so that 1st picture is actually correct? After the switch the mono and back, the output from the shifter is all garbled.troed wrote: ↑Sun Jan 07, 2018 10:33 amNopeAt cycle 444 when the switch to high resolution happens the real Shifter indeed displays black until the switch back to low happens. This is actually the reason why ULM chose to use medium resolution for their stabilizer instead (from cycle 440) since that doesn't happen.
This is so far out into the right border that very few TVs/monitors displayed it. A modern LCD of course does, especially if you can tweak horizontal position.
12 cycles is indeed the normal length of a HI-LO stabilizer.
Just let me know what else I should capture, else I will just continue with what I think is relevant when I find the time
/Troed
It's not during a normal screen mode, it's done by this program to avoid the end of the scanline, because the point where the scanline ends is much earlier in mono mode. It (the GLUE I think?) is waiting to hit a specific cycle number to end the line, so by changing that number to one that it already passed, you can skip over that point and make it continue outputting more pixels.