There is a tool called Shark that comes with the Mac OSX developer
tools.
Learn about and and use it, with and without the effects.
If you are on Windows then find a similar tool.
I think you will find that once QuickTime starts compositing and
depending on your settings in your effect, that the blitters all use
a different code path and operate in different ways, thus slowing
things down.
On 26-May-06, at 6:26 PM, Chuck Bueche wrote:
Hi Folks,
I've gotten my own effect up and running and am seeing a really bad
frame rate. I started with the Dimmer2EffectWindows sample (and
eventually commented out *all* of the pixel-pushing in the
EffectFilter* files).
- My source media is 1264x720, 30 fps.
- On my system I can play two of these simultaneously with no
apparent performance hit (roughly 10 mbits/sec).
Even the simplest effect (even a complete NOP applied to only one
source, for that matter) causes the frame rate to drop to 15 fps
or less.
Is this simply due to moving a complete image around in RAM, rather
than changed pixels per frame? Is there something I've missed
that would cause this?
Thanks,
Chuck Bueche
_______________________________________________
Do not post admin requests to the list. They will be ignored.
QuickTime-API mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quicktime-api/email@hidden
