Re: XML into FCS annotations
Re: XML into FCS annotations
- Subject: Re: XML into FCS annotations
- From: Eryk Vershen <email@hidden>
- Date: Mon, 14 Jul 2008 19:08:17 -0700
Peter,
I assume you mean Final Cut Server, when you say FCS. (We tend use FCS
for Final Cut Studio and FCSVR or FCSvr for server.)
FCP markers are not accessible in FCSVR. It says so in the manual.
I assume you have done some testing and are aware of the limitations
on annotations in the current FCVSR. You can't globally search
annotations; there is no way play just an annotated section;
annotations on the master asset are not visible when viewing an
element related to that asset.
There is no programmatic way to create annotations. (Well, you could
write directly to the database, but that is "violating your warranty".)
Sorry,
-eryk
On Jul 14, 2008, at 5:42 PM, Helena Ju wrote:
Hi Peter!
I *think* you can do what you want with markers, and markers can
even be exported with a QT Export of a sequence or clip. You can
bring markers in via XML.
-Helena
On Jul 13, 2008, at 12:09 PM, Peter Wiggins wrote:
All,
Having finally got the XML out of Filemaker to link perfectly with
the original media in FCP (thanks everybody for your help) I'm now
trying to do something similar.
I want to take the Filemaker XML and change that into FCS
annotations so producers can navigate to scenes and view the
proxies on laptops. is there an easy way to do this? Does FCS
accept XML or any other third party logging references? Just a
note here to say we have about 500 items logged per two hour
quicktime.
A workaround I thought would achieve this was to export the XML
from Filemaker into FCP and relink as normal, then make subclips of
all the clips and then get FCS to make thumbnails of all the
subclips from the uploaded FCP project. This should work, but I
think you have to have the original media in the FCP browser window
to make a subclip, so it is a bit longwinded!
Any help appreciated :)
Peter
_______________________________________________
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
_______________________________________________
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
_______________________________________________
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