Richard,
Have you tried using the pixMapID property? You may want to check the archives for the limitations of this (IIRC it may crash if you try to reference a stack which is not in memory), but...
set the imagePixMapID of image "snapshot" to the pixMapID of stack "someStack"
Then you could export the image?
Dunno for sure, but it may be quicker!
HTH, - Brian
Sarah,
Tried lock screen and lock messages. Didn't seem to help much. The slowness seems to be with the export snapshot command. I'd like to think there are other externals out there that are faster and can replace this one. That would be one solution.
A better solution would be to find a way to take a 10 second quicktime file and extract a 2 second section of it. Any idea how to do that?
Thanks. Richard
On Jan 30, 2005, at 6:36 PM, Sarah Reichelt wrote:
This seems very slow, can you try lock screen & lock messages to see if that speeds things up.
Sarah
On 30 Jan 2005, at 10:30 am, Richard Miller wrote:
I'd appreciate any suggestions for alternatives to the Export Snapshot command. We're finding it rather slow for our purposes, taking 2-3 seconds per snapshot. We have a specific routine that needs to generate 50 separate images, essentially breaking down 2 seconds of video into 50 frames. Any alternatives?
Thanks. Richard Miller Imprinter Technologies
_______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________ use-revolution mailing list [email protected] http://lists.runrev.com/mailman/listinfo/use-revolution
