#ADPro HAM>PCX "glitches"
4 messages in this thread
Any suggestions on what we can do to avoid the 320xHAM problem in the
interim?
I finally got some memory stuck on my A2091 card and now have 4 meg
contiguous on my A2500. Much bettah.
Is there any fix for the ARZ/DYNA bleed? I suspect that it has something
to do with the hard drive host adapter as it happens on non-accellerated
machines too.
Thanks for a great product. Now the Pee Cee people can drool on their
own keyboards.
Lee Bosch
– via Whap!
I am afraid that there is nothing we can do to fix the 320 wide HAM into 24
bit-planes problem until our free automatic upgrade comes out in the near
future.
With respect to “arz/dyna bleed'' are you refering to background color
changes outside the image? As is, changes in the background color to the
left of pixel 0 and to the right of pixel 640? Is so, this is normal for
arz/dyna type pictures. Color register 0 (which is the background color) is
changing line to line. This causes a visible change in the border area if
the image is not overscanned.
pk
I seem to get some striation in the picture itself. I didn't read the
part about the border bleed though. This begs the question:
What exactly IS the relationship between ARZ1, DHR and ARZ0?
On another front, have you heard about a problem with full overscan HAM
images breaking up? I know it has nothing to do with your product as it
happens with SuperView and Dyna-Show. Again, I have an A2500/30.
ARZ0 is the same as DHR – up to 16 color register changes per high res
line. ARZ1 is slightly different in that color register 0 (the background
color) is clamped to black. Therefore, you get at most 15 color changes per
line and a non-weird border area if the picture is NOT overscanned.
As for your question about overscan HAM – I think I CAN give you an
explanation.
SuperView does not handle severly overscanned HAM images correctly in that
it over optimistically offsets such images too far to the left of the
screen. In doing so, some pixels on the left side get left off the
display's HAM computation causing awful HAM fringes on the left side. You
can confirm this is the case by using the SuperView option which disables
overscan. If the “break up'' goes away…then this was your problem.