On Jun 3, 2008, at 10:45 PM, Christopher Wright wrote:
You're right about the TypeMuxed stuff -- can a mac have a muxed
device as the default? (I though isights were the only default, but
I'm totally guessing there). The default part was a fall-back
anyway, and wasn't in effect for this exercise.
There is a default for each possible media type. The default video
device will generally be the iSIght, while the default muxed device
will be one of the muxed devices connected to the computer, if there
are any.
I was thinking that a missing codec may have been an issue, but then
having the camera work in other settings on the same machine made me
rule that problem out. As it turns out, adding the audio-disabling
snippet appears to have fixed the problem (the user has now reported
a visible image, and is really excited :) -- If this isn't quite
expected behaviour (i.e. The "Hypothetically, it shouldn't be
necessary to disable the audio connection when there are no capture
outputs expecting audio, The capture session should know to just
ignore the extra stream in that case." part David mentioned a few
mails ago), let me know so I can write up a bugreport and supply
some sample code. I'm guessing QTKit's going to get a lot of
attention in the near future anyway, so maybe this is already on the
agenda?
Yes. Please go ahead and file a bug report, so we can try and track
down what is different when the connection stays enabled. Thanks for
the help and feedback.
Cheers.
David Underwood
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
