Hello All I have an unusual problem. I need to limit the speed part of my composition renders at, and I mean 'really' limit it, not just set the rendering speed in QC.
I've attached the composition. You'll need either a file called 'lifeforce.avi' on the desktop, or you'll need to change the path of the movie loader (inside a macro marked 'load movie, prepare frame' or similar) to something that exists. A quick explanation of what happens, as it's perhaps not obvious: It gets frames from a movie, and then splits them into a structure containing each separate column of pixels from the source video. It does this at 640x480, so there are 640 images of 1x480 pixels in the structure. It does this in a series of macros, each of which steps through a section of the image and crops 1 column per frame. Because of that, it takes 40 steps to process one image, so this part runs a lot less than realtime. That structure then gets added to a queue of 640 images, so it builds up a massive structure of broken up images over time. In the render in image (which is the rendering stage), I take the columns and re-build the image, but as it renders left-to-right it also steps back in time, to build the slit scan. You'll see that the composition runs at good speed (I get 60fps here initially, it slows down as the queue builds up and the number of iterations increases), but it draws very, very slowly because another part of the composition (the frame divider part) runs much slower (around 1fps initially). I want to render it to a movie file, so ideally I need the whole composition to run at a fixed speed (the speed the divider runs at). Is there any way to do it? Or do I need to render it to disk as it is, capture an hour or two of video, then run it though something else to remove frames where there's no change? The only way I can think of is to split the frame divider up even more, until I have 640 macros cropping out one pixel column each, then combining it in javascript. I really don't want to make 640 macros :( Another question too - how the hell does structure sorting work?! You can see in the divider that I have a javascript patch combining the structures into a bigger structure, and putting the inputs nicely in order. The output structure is in a totally different order. Using a structure sort patch seems to just randomise the order! Because of that I have to have another javascript patch to get the right element further down the line. Using numbers or names seems to make no difference. Oh, I'm not sure this patch actually does proper slit scanning by the way, it's untested. I have another patch that does it well (and animated), but sometimes literally kills my mac because it hits the cpu + gpu hard, and saturates the bus until the whole machine gets really laggy. Hence this new version! Thanks for any help! Chris
slitscan h 2.qtz
Description: application/quartzcomposer
_______________________________________________ Do not post admin requests to the list. They will be ignored. Quartzcomposer-dev mailing list ([email protected]) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
