All you need are the differences (without compressing anything). Instead of saving raw screen$ data, you generate the difference between two frames as optimized machine code that only updates the screen addresses that need updating. There is a tipping point at which it would be quicker to simply refresh the entire screen. You may also want to insert entire screen refreshes every X frames to allow a fast forward.
This cannot be that difficult. Regards, Stefan -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Roger Jowett Sent: zaterdag 28 mei 2011 01:56 To: [email protected] Subject: Re: Loading stuff from machine code with the ROM functions ok this is it my last daft email to the gang of 4! please as i dont have a clu if masterbasic compresses a screen when it saves it what would happen if you take two screens from my animation if you compress them both and look at teh two compressed screen fils surely the difference between teh two comrepssed screens is teh tiny onscreen difference between one screen$ and teh next - no i didnt think so either but still clutching at straws is fun surely once you have decompresed teh first screen the rest only really need to be the tiny differences that are made to that first image though i realise ol z80b is sturgling to get 4kb into video ram and that is jsut with copying not reading from a port whichshe has to do to read teh atom is there no other way of ziping things up a bit please?
