Some nice aerial shots of Sydney, Australia

Some great shots of Sydney from the air. We have the AWA tower, Commonwealth Bank building, Centrepoint Tower and there are even 4 frames of an apartment we stayed in the year this movie was made. (I have watched this video too many times!)
Oops, scratch that. This is Mega City from The Matrix. A hybrid of Chicago, various scenes from California and the city of Sydney.
But in reality, this is a demonstration of Baggers' 256x96 video driver, running a movie under KyeDos, with Floyd-Steinberg image manipulation by James Moxham, along with image pre-processing, scaling, and timing manipulation.
See the next post for the movie.
We have skin tones, action shots, dark indoor scenes, and also outdoor scenes. Some blue, green, gray/brown colors, as well as a nice black/yellow/red explosion near the end.
This is probably pushing video on the propeller to the limit. 24k of hub ram, and Baggers has managed to fit this code in with 54 longs to spare. So for the moment, audio is a bit beyond this, though it might be possible in XMM Catalina C.
It is of course, entirely appropriate for The Matrix, that the TV version of Kyedos is in greenscreen.
I'll post code in a bit as I need to sleep. 'Tis 1:49am and my real job is taking 17h per day. That is, of course, if my real job really exists. Maybe it is just a simulation in The Matrix...
Oops, scratch that. This is Mega City from The Matrix. A hybrid of Chicago, various scenes from California and the city of Sydney.
But in reality, this is a demonstration of Baggers' 256x96 video driver, running a movie under KyeDos, with Floyd-Steinberg image manipulation by James Moxham, along with image pre-processing, scaling, and timing manipulation.
See the next post for the movie.
We have skin tones, action shots, dark indoor scenes, and also outdoor scenes. Some blue, green, gray/brown colors, as well as a nice black/yellow/red explosion near the end.
This is probably pushing video on the propeller to the limit. 24k of hub ram, and Baggers has managed to fit this code in with 54 longs to spare. So for the moment, audio is a bit beyond this, though it might be possible in XMM Catalina C.
It is of course, entirely appropriate for The Matrix, that the TV version of Kyedos is in greenscreen.
I'll post code in a bit as I need to sleep. 'Tis 1:49am and my real job is taking 17h per day. That is, of course, if my real job really exists. Maybe it is just a simulation in The Matrix...
Comments
This looks a *real breakthrough* - a brilliant result for those of us who have studied your developments!
T o n y
-Phil
Have you seen this?
It shows how well the Floyd Steinberg technique actually works. (video is 320x200)
It also shows how well balanced the 16 colors of the C64 actually was (compared to the spectrum for an example)
Might be worth experimenting with color depth vs number of pixels. At the moment it is 1 byte per pixel but with only 16 colors you could get 2 bytes.
One limiting thing seems to be the data rate from the SD card. Previously with the 160x120 driver it was reading at about the right frame rate. 256x96 was reading around half speed so to get the speed right every alternate frame has been removed. I think the frame rate might be around 7.5 per second now.
Baggers is working some magic with interlacing dual props to increase the memory. Maybe one could have dual sd cards too?
When I get home I'll post the code. There is some vb.net code to resize the screen as youtube videos all seem to be slightly different. And there is a scaling factor as 256x96 ends up a "wide screen", so you need to squeeze it first so it ends up right. I did some experiments with a picture of a circle to test this out.
As for fitting it into one prop, it could probably go smaller, I just kept removing routines in Kye's SD code, until it fit
If you use BST and remove all unused routines, it will show you what it can get to. ( I've not done this yet )
Also using that driver should do 256x192 16 colour!
To test out the origin x,y and the size of the cropped photo - use the single picture option first before running the movie creator. The movie takes a while so do a short test one first.
The number of frames in the spin program is half the source number as every alternate frame is skipped.
@Baggers, 256x192x16color will be just perfect for the C GUI I'm writing. Cheers!