I must rather shamefacedly admit that my seemingly clever 'binaryDecode' method is actually just extracting the red channel -- so not very clever :(

Best,

Mark

On 3 Dec 2007, at 21:41, BNig wrote:


the timing on a MacBook Pro 2.33 GHz for the scripts is

on average 190 Milliseconds for the whole thing, i.e. passing the original file to Colorsyncscripting, creating the grayscale file on disk and reading
the file into Revolution and display the image.

if you change the applescript so that you keep Colorsyncscripting open
instead of closing it as the current script does then the whole thing takes
about 90 Milliseconds. This of course if you intend to do multiple
conversions. Right now ColorSyncScripting is closed after five seconds, if you set the filename of the image and start the conversion within this time
you get the 90 milliseconds as it is.

It also helps to put into a startup script that starts ColorSyncScripting during startUp, somehow it "initialises" applescript and revolution and
ColorSyncScripting is ready when you do the first conversion.

a script like this would do:
------------
on openStack
put "tell application " & quote & "ColorSyncScripting" & quote & " to
launch" into forASVar      
do forASVar as applescript
if the result is not empty then answer the result
end openStack
---------------

the timing for the two variants strictly within Revolution to do the same as
the applescript variant:

Ron Woods: 1080 milliseconds
Mark Smith 660 milliseconds ( the binarydecode variant)

having set the paintcompression to "RLE" on startup these values change to:
Ron Woods: 800 milliseconds
Mark Smith 400 milliseconds ( the binarydecode variant)

just setting the imagedata with the "RLE" startUp
22 milliseconds !! brilliant

all measurements made with the same picture 640 by 480 pixels


thank you for pointing me to the RLE and PNG problem, I was not aware of this. I use set imagedata in correcting movies for shifts, this involves 900 to 1200 images/movie of 768 by 576 pixels, and the 400 milliseconds it takes for each image on an iMac 2 GHz definitely add up. the actual taking apart of the image and putting it back together again in Revolution is quite fast
(about 60 milliseconds). So I will try to set the paintcompression on
openstack.

BTW I very much like your stacks on imagemanipulation in Revolution, it is
amazing what you do with them

Thank you.

Bernd






Wilhelm Sanke wrote:


On Mon Dec 3, 2007 BNig niggemann at uni-wh.de wrote:

Ken,

if you are on MacOSX system > = 10.4 and you just want the image to be
grayscale then you can try an applescript for colorsyncscripting.
it is a lot faster than Revolution. It takes Revolution from "set the imagedata of image x to y" for a 640x480 on a MacBook Pro 2.3 about 280
Milliseconds to display the image. So whatever you do you have this
overhead.


You did not tell us in your post how fast using "applescript for
colorsynscripting" actually is?

Concerning the occurring "overhead" you mention when you display the
changed imagedata from a variable in Revolution, like "set the imagedate
of img "x" to changeddata",  you have to take into account which
paintcompression is set. PNG can be up to ten times slower than RLE.

See bug # 5113 "Slower speed of imagedataprocessing with engines >2.6.1 and PNG compression" with the attached test stack. Curiously, this bug is still left as "unconfirmed" although we had a discussion about this
on the improve list half a year ago.

On my 2 GHz machine to display a 640x480 image from a changed imagedata variable takes 50 milliseconds with the paintcompression set to RLE and
580 when set to PNG.

The Revolution engine defaults to RLE, but the Rev IDE changes that to
PNG on startup.

For fastest imagedata processing use engine 2.6.1 and the Metacard IDE -
or set the paintcompression to RLE on openstack.

Regards,

Wilhelm Sanke
<http://www.sanke.org/MetaMedia>

_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution



--
View this message in context: http://www.nabble.com/Any-suggestions- on-how-to-%22onion-skinning%22--tf4892376.html#a14139524
Sent from the Revolution - User mailing list archive at Nabble.com.

_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription 
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to