I have some code which captures live-video-data via SGDataProc and
which calls SGIdle from inside a thread. This worked wonderful
under OS X 10.3.x.
Now, after upgrading to Tiger, this code stopped working after
capturing five frames, I get the following Error-code back from
SGIdle:
-4384
-4384 is not a QuickTime error code, nor is it a CoreAudio error
code, nor is it a publicly defined error code. So I don't know where
this is coming from. What are you capturing? Video only? Video +
SGSound? Video + SGAudio? You might need to share code.
Looking at Sequence Grabber sample code, SGIdle is usually called
from inside a timer (NSTimer, CFTimer, carbon Timer, Windows timer,
whatever). Is there a reason you need to call it from a thread?
SGIdle is the call in which the Sequence Grabber will perform writes
to disk (if new data is available). It is therefore the call from
which the SGDataProc will fire. Just ask yourself whether this
thread you've created is the appropriate place to be doing disk
writes + whatever processing you're doing in your SGDataProc.
If I stop and restart the capturing when an error occures, I get
the following Error-code:
7492
This is not a real error code. If you look at it in a binary
calculator, it's actually the characters " D" (that's "space", "D").
So this looks like half of a four-char-code, maybe.
-Brad Ford
QuickTime Engineering
_______________________________________________
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
