I have this working now. For the record, I was able to get it to display one frame in ten by using that Javascript frame counter and an image multiplexer, so that only one frame in ten is the image, the rest being nil. Disabling background erasing leaves a steady image that's only updated when the frame counter sends out a pulse. The speedup is quite significant and I can now get up to around 500 fps on a good day, though it varies quite a bit, seemingly at random (I'm guessing this is either due to temperature or to whatever background processes happen to be running). It's also possible to use an LFO instead of the frame counter, which results in the screen updating at a constant framerate, no matter how fast or slow the simulation is running, which sometimes looks better.
Thank you Christopher for all your help. Nathaniel On 14/03/2008, Christopher Wright <[EMAIL PROTECTED]> wrote: > > > Okay, I have it working now. Seems like I had to reboot (or log > > out) for the option change to take effect. > > > I think just restarting QC was necessary for DisableVBLSync on my > machine. *shrugs* glad it's up and running. > > > > But the speedup still isn't as much as I'd like - even with small > > images going through the filters it can only get up to 110-120 fps > > full screen and about 250 in a small window. However, if I disable > > the billboard (there's just one which pastes the output from the > > accumulator to the whole window) then it jumps up to about 900. > > > It's 900ish because it's not doing anything -- Not evaluating any part > of the graph. This is important in a moment... > > > > Which I guess means that pasting to the display is the bulk of the > > work, so I need to only display about one frame in ten if I want to > > get it as fast as possible - do you know if there's any way to do > > that in QC, or will it mean going the thin app route? > > > > ... like now :) To see your composition graph's peak speed, try > attaching the output to something that does next to no work, but is a > red patch. For example, attach the output image to the enable input > of an empty Iterator patch set to 0 iterations -- this means the > iterator does essentially no work, but the rest of the graph gets > evaluated anyway. This will tell you how fast QC can process your > graph without any graphical output overhead. By disabling the only > output, it causes QC to stop executing _any_ of the patches, which > probably isn't what you want. > > To illustrate, it'll look something like this: (it looks like total > nonsense, but the input gets to execute sure enough -- if you mouse > over the output you can see the scan results) > > > > > > Let me know if this doesn't make any sense, it's a bit hackish at best. > > To then display one frame in 10, you can make a frame counter from the > javascript patch (notes on how to do this here: > http://kineme.net/Applications/Compositions/Demoeffects#comment-881 > ), and then modify the JS a bit to have an output that's true 1 in > every N frames -- attach that to a billboard, and the graph's output > as well to the billboard, and you should probably get something close > to what you're looking for. > -- > [ christopher wright ] > [EMAIL PROTECTED] > http://kineme.net/ > > > >
_______________________________________________ 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]
