I got it kind of working. I found Toms old article about how to access imagebuffers the quick'n'dirty way, using a redirected Bank that points to an Imagebuffer, then use CreateComaptibleDC etc to make Bitblit writing to it. I tried to use GetDIBits, but it refused to work (I only get a black rectangle), maybe I made something wrong with the BitmapInfo Struct. Anyway, I used GetBitmapBits like in your example, although MS says it's obsolete (using 16 Bit) and you should use GetDIBits instead. A least it worked.
Now my problem is: I get approx 0.7 frames per second when I use it together with an open Movie that plays frame by frame, using mciSendstring Step...
So the whole task is:
Play an Aviframe
blitblit this to the Comptible Image
Move the Bits to the Blitz Imagebuffer
I can't believe that this is so slow. I made some tests with RTLMoveMemory and it moves 720*576*4Bytes (my frame size) a thousand times in 14 milisecs.
If I play the Avi Frame by Frame without to copy or blit anything, then I get decent framereates, maybe 15 or 25 per second. Maybe there is some kind of Data collision on the bus since the Bitblit and Movie playing commands may be parallel threads on the system level ?
The most efficent way would be to redirect MCI to draw the movie directly into the blitz image buffer. I just made some more tests and it seems, bitblt is the worst brake here.
If I could use MoveMemory instead, that would be cool.
will this Odysee ever end :/
Now my problem is: I get approx 0.7 frames per second when I use it together with an open Movie that plays frame by frame, using mciSendstring Step...
So the whole task is:
Play an Aviframe
blitblit this to the Comptible Image
Move the Bits to the Blitz Imagebuffer
I can't believe that this is so slow. I made some tests with RTLMoveMemory and it moves 720*576*4Bytes (my frame size) a thousand times in 14 milisecs.
If I play the Avi Frame by Frame without to copy or blit anything, then I get decent framereates, maybe 15 or 25 per second. Maybe there is some kind of Data collision on the bus since the Bitblit and Movie playing commands may be parallel threads on the system level ?
The most efficent way would be to redirect MCI to draw the movie directly into the blitz image buffer. I just made some more tests and it seems, bitblt is the worst brake here.
If I could use MoveMemory instead, that would be cool.
will this Odysee ever end :/