yeah, the number one trick is to work in the lowest res you can.
And use a modern computer... old computers could probably do just as
well, if you worked in C.
there are tons of other tricks, like processing every pixel in a
frame at once via veclib,
Which is probably written in C.
or converting picture objects directly to
ptrs to remove RB's image access overhead. its all pretty declare
heavy though.
To libraries written in C.
now that RB has ptrs, I've found my coding tricks have
changed a lot - i'm doing more and more in tight loops byte by byte.
Which is doing low level stuff, like you'd do in C.
but for blurs / distortions/ fft etc, the vImage and vDSP libraries
on mac offer huge speed gains. And lately I've been moving more and
more processing to the GPU via opengl.
I think you can guess my point on this one also ;)
Basically, the image processing code you made in RB, you are either
getting from using stuff made in C, or getting because RB in some
ways is starting to overlap C's approach.
All we really need is some nice proper typed pointers, a few syntaxy
stuff like *p++ , and the compiler to optimise pointer work.
--
http://elfdata.com/plugin/
_______________________________________________
Unsubscribe or switch delivery mode:
<http://www.realsoftware.com/support/listmanager/>
Search the archives of this list here:
<http://support.realsoftware.com/listarchives/lists.html>
