#DigiView 3.0
4 messages in this thread
I've found a problem. Digi-View 3.0 is not setting up the screen size
properly. (in overscan only) I wrote a up a quick program today that
patches the IFF files. I'll upload it tomorrow. Not sure if your problem
with quickflix is the same as the one that bit me, but if quickflix is
doing it's thing correctly then the problem probably is the same one.
Dale
Odd… In what way are they not setting the screen size properly? (More
than idle curiosity… I've been working on some Amiga overscan stuff for
a little while, and will be saving to IFF, so I'd like to avoid doing it
wrong…)
At longword offset 9 in the IFF file, they are leaving the screen size
set to the non-overscan values. (320/400, 320/200 etc) Some programs may
not mind this, but SuperView seems too. I have no idea what that location
is for. I don't have the IFF spec. I found it by comparing Digi-View
overscan pic's with pic's created by some of the other programs.
(Sculpt-3d, and Impulse products) The program I wrote reads the longword at
offset 5 and duplicates it to offset 9. Seems to fix things right up. Of
course without any info on the IFF file format, I don't know what I'm
doing. Just that it works. Take a look at a IFF pic file with newzap,
you'll see what I'm doing. Dale
Hmmn. The longword at offset 5 (which, BTW, isn't GUARENTEED to be at that
offset, but generally is…) is the actual size of the bitmap. The
longword at offset 9 is something referred to as the "page" size. While I'm
not sure if this size should be used to determine if the image uses
overscan or not, I'd think it *should* be the same size or larger than the
bitmap size itself. I'd have to read up on it more carefully to be sure
what the case is… –>Steve Bennett