Enhanced ARX True High Resolution Display Driver
Re: Enhanced ARX True High Resolution Display Driver
Both work fine.
Re: Enhanced ARX True High Resolution Display Driver
It is good news, I suppose ?
I will leave the NOP in though, so it won't stumble when run on EightyOne.
I'm now trying to find a way to interlace two 64 pictures and get 4 grayscale levels (probably acceptable only on phosfor monitors, if I ever make it work).
It should exist already in WRX mode.
Would you mind to try also one of the samples built for the 64 rows mode ?
I will leave the NOP in though, so it won't stumble when run on EightyOne.
I'm now trying to find a way to interlace two 64 pictures and get 4 grayscale levels (probably acceptable only on phosfor monitors, if I ever make it work).
It should exist already in WRX mode.
Would you mind to try also one of the samples built for the 64 rows mode ?
Re: Enhanced ARX True High Resolution Display Driver
You post it and I will try it!
Re: Enhanced ARX True High Resolution Display Driver
I posted a "sampler" one page ago (actually it is in page #3). It includes 64rows and 8K stuff (arx64*.p).
Re: Enhanced ARX True High Resolution Display Driver
While testing the new code on EO I noticed it could not work properly on 60hz sets. I don't remember how the old one was behaving, though.
Re: Enhanced ARX True High Resolution Display Driver
Updated timing values, they look correct on EO.
I'm also adding a new feature, at a very beta release level to deal with an intelaced picture, the artifacts are espected (see picture) and in this moment it gets useful to see black areas (compared to gray). Could anybody see how it looks on the real hardware ? I'm expecting a relevant flicker on a traditional TV and a better result on high persistency monitors (green phosphor, etc..)... if the picture keeps the sync
The new test cases are with/without the break detection, 64/192 rows.
They all should be able to compensate the timing on 50hz and 60hz TV sets
This ideally implies 10 different tests (which should also be verified on different monitors), but obviously I'm not asking that much.
EDIT: please ignore the greyscale mode, I think there's still too much missing for useful feedbacks.
I'm also adding a new feature, at a very beta release level to deal with an intelaced picture, the artifacts are espected (see picture) and in this moment it gets useful to see black areas (compared to gray). Could anybody see how it looks on the real hardware ? I'm expecting a relevant flicker on a traditional TV and a better result on high persistency monitors (green phosphor, etc..)... if the picture keeps the sync
The new test cases are with/without the break detection, 64/192 rows.
They all should be able to compensate the timing on 50hz and 60hz TV sets
This ideally implies 10 different tests (which should also be verified on different monitors), but obviously I'm not asking that much.
EDIT: please ignore the greyscale mode, I think there's still too much missing for useful feedbacks.
Last edited by stefano on Fri Apr 12, 2024 1:53 pm, edited 1 time in total.
Re: Enhanced ARX True High Resolution Display Driver
I can test but only on LCD monitor as I no longer have a CRT monitor, also is this to be tested with UDG4ZXpand or just plain zeddy?
Re: Enhanced ARX True High Resolution Display Driver
Right, this makes a difference ..both?
..in the meantime I found a way to work this out:
I'm afraid it won't be healthy for your eyes !
I've already put the latest driver version online, I think it is already better than the previous ones.
..in the meantime I found a way to work this out:
I'm afraid it won't be healthy for your eyes !
I've already put the latest driver version online, I think it is already better than the previous ones.
Re: Enhanced ARX True High Resolution Display Driver
More about the gray library, I have 3 possibilities,:
the current driver shows a first frame 2 times, a second one only for 1 time.
This is in theory correct because the picture would allow a higher persistence to one of the two allowing a dark gray and a light gray.
By the way the 2 frames in a raster picture are interlaced. This uneven count will probably make the lines "bounce" up and down.
It can help in shuffling the overall result but perhaps it will bounce the frames making the picture more fuzzy.
Otherwise, I could avoid the unbalanced persistence. The result would be much like the screenshot I've pasted, two identical gray levels but slightly "shifted" plus black and white.
A further possibility could be to deal with a 6 frames counter trying to give every frame a preferred position. I think something would still need to bounce, but... well we should try and see.
the current driver shows a first frame 2 times, a second one only for 1 time.
This is in theory correct because the picture would allow a higher persistence to one of the two allowing a dark gray and a light gray.
By the way the 2 frames in a raster picture are interlaced. This uneven count will probably make the lines "bounce" up and down.
It can help in shuffling the overall result but perhaps it will bounce the frames making the picture more fuzzy.
Otherwise, I could avoid the unbalanced persistence. The result would be much like the screenshot I've pasted, two identical gray levels but slightly "shifted" plus black and white.
A further possibility could be to deal with a 6 frames counter trying to give every frame a preferred position. I think something would still need to bounce, but... well we should try and see.
Re: Enhanced ARX True High Resolution Display Driver
I think the best compromise is to cycle between 4 frames, a first one (light gray) appearing only 1 time and the second one (dark gray) being displayed 3 times (thus a white frame interposed only one time).
The result seems plausible, observing it on EO, (this is the best screenshot I could take, the dark and light levels look inverted because of the flicker) I've updated also the WRX version:
Originally the WRX version was designed to reduce the flickering (sacrifying the 2 gray levels), but I think it was never tested on the real hardware.
Please let me know if the diamond looks dark or light.
The result seems plausible, observing it on EO, (this is the best screenshot I could take, the dark and light levels look inverted because of the flicker) I've updated also the WRX version:
Originally the WRX version was designed to reduce the flickering (sacrifying the 2 gray levels), but I think it was never tested on the real hardware.
Please let me know if the diamond looks dark or light.