• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: FCP X XML
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: FCP X XML


  • Subject: Re: FCP X XML
  • From: Gregory Clarke <email@hidden>
  • Date: Wed, 21 Sep 2011 15:18:17 -0700

I can see many examples where adding a new Project or Event is the right thing to do, but updating an existing Project or Event would be useful too. A hypothetical example (based on apps I've made before) would be an external logging tool. The media is already ingested and in an Event; the logging app is used to create ranges and add keywords and other metadata to the clips; so after logging it would be better for the user if the original Event was updated with the new metadata instead of making a duplicate Event. 

Thoughts?

Greg

On Sep 20, 2011, at 6:54 PM, Jon Chappell wrote:

The documentation seems to imply that it will create new projects and events and cannot be used to update existing ones.

Regards,
Jon Chappell.
CEO, Digital Rebellion LLC.
http://www.digitalrebellion.com

On Tue, Sep 20, 2011 at 6:20 PM, Andrew Mees <email@hidden> wrote:
Hi Rainer
Just woke up to the new XML docs so haven't had time to look yet …. but does the XML import have an "update" function?  If so then that should allow changes to be made through 3rd party XML manipulation without breaking anything.

Just a quick thought
Andy



On 21 Sep 2011, at 06:02, Rainer Standke wrote:

> Hello all,
>
> early in the new doc describing FCP X XML there is this:
>
> "Important: FCPXML Version 1.0 describes certain project data that is useful for exchanging with other
> applications. It does not describe all possible data, and therefore is not a substitute for the native project file
> when archiving a project or moving a complete project from one system to another."
>
> This sounds like workflows that rely on getting a sequence XML out of FCP, manipulating the XML, and finally putting the XML back into FCP will potentially break things, as in: the returned sequence will drop things that where in it in the first place. Is that correct?
>
> Also, what is it that gets lost?
>
> Thanks,
>
> Rainer _______________________________________________
> 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
References: 
 >FCP X XML (From: Rainer Standke <email@hidden>)
 >Re: FCP X XML (From: Andrew Mees <email@hidden>)
 >Re: FCP X XML (From: Jon Chappell <email@hidden>)

  • Prev by Date: Re: Random marker timebases
  • Next by Date: Motion template title effect broken by 10.0.1 update
  • Previous by thread: Re: FCP X XML
  • Next by thread: Re: FCP X XML
  • Index(es):
    • Date
    • Thread