shoggoth wrote:I base this suspicion on other code Didier has written (he detects the pixel format in the console by checking the video base address in TOS, for example.)
I thought Aniplayer relied on the EdDI cookie, that allow programs to use the vq_scrninfo() function. If the screen driver gives correct values for vq_scrninfo(), then the display should work for all applications that call this VDI function.
No guess about what happens when the EdDI cookie is not present, but the coder must assume that the screen is Atari standard.
shoggoth wrote:I base this suspicion on other code Didier has written (he detects the pixel format in the console by checking the video base address in TOS, for example.)
I thought Aniplayer relied on the EdDI cookie, that allow programs to use the vq_scrninfo() function. If the screen driver gives correct values for vq_scrninfo(), then the display should work for all applications that call this VDI function.
No guess about what happens when the EdDI cookie is not present, but the coder must assume that the screen is Atari standard.
Don't think it does.
The SV drivers use the same NVDI driver in e.g. 1920x1080x16bpp (SV-specific mode) and 320x480x16bpp (VIDEL mode). It's the same driver, which returns the same vq_scrninfo() (it's NVDI; with screen drivers; it has vq_scrninfo(), offscreen bitmaps, the lot) info, and hence Aniplayer should use the same pixel format. It doesn't. I've noticed however that even 320x480x16bpp (SV-mode) works in Aniplayer (iirc). This means Aniplayer might even do something as far fetched as checking the size of the screen to determine the pixel format.
I'd love to be wrong though, because I'd like to be able to use Aniplayer in proper resolutions.
patjomki wrote:
And my SuperVidel is running fine except the fact that the ATARI logo in the ct60 boot screen is totally distorted. Is this normal?
Normal, unfortunately. Didier haven't blitter-patched TOS very much, and since we can't snoop the operations of the blitter, it current looks like that.
I found out, if you use bootconf.prg to set 80 columns, no linedoubling, 65536 colors,
the boot ATARI logo is displayed correctly. On the videl output (i have the VGA adapter
plugged), you don't get a valid screen output, but on Supervidel output is working.
Only the white background is a little bit shaded, you can notice it as soon boot messages
scroll the screen upwards.
patjomki wrote:
And my SuperVidel is running fine except the fact that the ATARI logo in the ct60 boot screen is totally distorted. Is this normal?
Normal, unfortunately. Didier haven't blitter-patched TOS very much, and since we can't snoop the operations of the blitter, it current looks like that.
I found out, if you use bootconf.prg to set 80 columns, no linedoubling, 65536 colors,
the boot ATARI logo is displayed correctly. On the videl output (i have the VGA adapter
plugged), you don't get a valid screen output, but on Supervidel output is working.
Only the white background is a little bit shaded, you can notice it as soon boot messages
scroll the screen upwards.
The same in APEX, the normally non-usable 640x480x16bit resolution works on SuperVidel, no hacks needed. I was a bit baffled at first and thought I had accidently set 8bit mode. But nope, it was 16.
It's on my eternal todo-list. There are reasons for not releasing the source code at this point. No good ones, but still, reasons If anyone would like to discuss driver development or want to write their own drivers using similar methods, I'm more than willing to share knowledge naturally.
Not sure if this is driver related but I cant seem to get sv_xbios.prg to run from auto. If I run it manually from desktop I get supervidel output and all seems well. I've got things stripped down to the bare minimum and only nvdi.org and sv_xbios.prg in auto and I've tried changing the start order but nothing.
I assume the settings (sv.inf) are ok since I can start it from desktop.
Nature bros kindly helped me set things up at sommarhack but we never got past this problem. Tos is 1.03c and I've tried both with and without nvdi in auto. Apart from that it's empty.
shoggoth wrote:What happens when it's launched from /auto/? I've noticed that CT60-TOS sometimes "forgets" to set the _CPU-cookie properly (for example).
I can see the text output from sv_xbios.prg flash on the screen and then I get garbage on videl output but nothing on supervidel. Actually I cant remember if I get garbage on videl when run from auto or when run manually, its probably the other way around, garbage on videl when run manually and just a white screen if run from auto.
deeez wrote:Nvram is dead I think, perhaps thats whats causing the problem? Boot resolution is st-low I guess?
Who knows? I'm trying to come up with something that's different in your machine compared to mine..
Are you using the "replace NVRAM" option in the CT60 CPX thingy? I've enabled this option, my NVRAM is dead, and I've set the boot resolution to 640x480x1bpp. I'm using 1.03c as well, no bus speeder, nothing.
No date set though.
If anyone would like to discuss driver development or want to write their own drivers using similar methods, I'm more than willing to share knowledge naturally.