I'm experimenting with moving slitscans such as this movie
on youtube (not mine).
To create this, I've written several max/msp programs while researching this. They are are based on non-realtime processes but it takes a lot of time. I wonder if it coudn't go faster or even instant.
What I did so far:
The programs I made are all based upon the jit.matrix commands: srcdimstart - srcdimend - dstdimstart - dstdimend. I copy pixel line per pixel line to the destination-movie. I tried to increase this workflow by letting the program do only a part of the whole image, so I could run multiple instances to benefit from multicore processing. Works good, but still way too slow with decent resolution images: to create a moving slitscan, I have to play the source-movie as many times as there are pixels in the width, which is pretty time consuming
If you look at a movie file as a cube of pixels - one frame forms a slice, all the frames forms the cube - we are used to traverse this cube always in one direction: from the front (start) to the back (end). What I would like to do is traverse this video cube from the right to the left.
I was wondering if this could be done by "simply" navigating in a different way through the movie data package instead of running through this long copying process. If you have only spacial compression (like Motion JPEG A), I guess the data package is just a bunch of pixels, so why not just 'play' the movie, but then in a different direction, from the right to the left. Instant slitscan.
I guess it won't be that simple, but I thought to ask the question here, since I don't know much about the structure of a spacial compressed quicktime movie.