To echo what Helena mentioned, FCP closes the viewer item when
reconnecting ( because that is what is going on... updating the clip
to match the new file ) because the clip in the viewer may be going
through dramatic changes. It could be argued that the viewer should be
smarter to handle the change dynamically or that FCP should reopen the
viewer after some delay. This behavior has not changed since 1.0 as
far as I am aware when reconnect was a much more static operation.
I am not familiar with FCP Apple Events, but the key would be to know
edit which is being viewed ( kFCPOpenItemInProject may be what Rainer
was suggesting). Knowing only the file is not sufficient because of
course a file can be used in many project in many different places.
Even a standard file that is edited only once exists in both the
browser and sequence.
On Feb 11, 2009, at 8:25 AM, Rainer Standke wrote:
Isn't there an Apple event that loads an item? You could call that
after your update. Might have to introduce a little delay to allow
for FCP closing it first.
On Feb 9, 2009, at 15:02 , Helena Ju wrote:
If the file in the viewer changes, we have to close the viewer.
On Feb 9, 2009, at 3:00 PM, Nelson Shawn wrote:
I have a QT file located on a network drive that gets updated
(it’s a growing file). I can either change focus outside of FCP or
send the Apple Event kFCPMediaFileKey and FCP will successfully re-
load the now bigger file (it has the same name).
But the big problem is that I lose the file from the Viewer
window! The process of reloading the same file happens
instantaneously and kicks me out of it. Is there a trick to get
FCP to not freak out and boot the file from the Viewer?
Do not post admin requests to the list. They will be ignored.
Pro-apps-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden