Hi Milton,
Just so you know, what you have described in option 2 (and 3) is
identical to the current expected and understood behavior of the video
input patch. Pressing play in the editor viewer will stall briefly as
the iSight or whatever other QT compatible device is configured.
Stopping will release the devices exclusive access and allow other
software to potentially grab it.
As far as I am aware, no one has ever complained about this, and this
is and has been the expected behavior of video devices. This holds
true for other applications, similar to FCP etc. Final Cut does not
have exclusive access to to hardware when the app is open. Only when I
initialize a digitizing session in log and transfer. Final Cut even
goes so far as releasing video output if the application is not front
most (so I can use say, my AJA output in After Effects, or hell, QC,
which ive done). My point is, what you describe is what is expected
from end users.
As far as performance concerns are... concerned, I think it is safe to
say the above is perfectly acceptable. When users stop in the QC
editor they are stating they are finished with video output and only
wish to edit the scene graph in QC and *not run it*, or perhaps even,
I dont know, use the hardware in another app? As long as you maintain
exclusivity for the duration of a start/stop cycle, that is more than
good enough and is 100% what is expected.
if I had to quit Quartz Composer or close the QC composition just so I
could use the hardware elsewhere I would personally view that as a
majorly irritating workflow
Im going to say that I may not understand the down low details of why
you *must* retain exclusivity for the duration of the plugin being
open or QC/a QC composition being active, and trust that you really,
really do.
I would say go for option 2 or 3, but it does not seem to meet you
criteria.
So, uh, I guess I dont know what to tell you then, perhaps others can
be of more help.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Quartzcomposer-dev mailing list ([email protected])
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/quartzcomposer-dev/archive%40mail-archive.com
This email sent to [email protected]
