Are you sure it is the reVideoFrameImage that is the hog?
Because if it is the send then you might need a "with messages"
or if it is a socket issue then you might need a "with messages"

I actually can't remember which needs it.

HTH

Tom

On Feb 3, 2004, at 10:18 PM, Doug Lerner wrote:

I am calling revVideoFrameImage periodically and sending the grabbed frame
over a socket. The problem is that the revVideoFrameImage command itself
takes a noticeable amount of time: 1/4 - 1/2 second on my machine, 1 second
or more on slower machines.


In this app, at the same time people are doing other things, like text
input, etc. But during revVideoFrameImage everything else stops.

Is there a way of not having revVideoFrameImage itself hog the whole cpu
when it does its frame grab?


Thanks,

doug

_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution



Thomas J. McGrath III SCS 1000 Killarney Dr. Pittsburgh, PA 15234 412-885-8541

_______________________________________________
use-revolution mailing list
[EMAIL PROTECTED]
http://lists.runrev.com/mailman/listinfo/use-revolution

Reply via email to