Andrew Richards
Forum Replies Created
-
[Erik Lundberg] “The XML from 10.1 seems to be very much the old familiar xml version 1.0 we (or at least some of us) has been staring at for (in my case) at least 8 years now (including the ?xml version=”1.0″ encoding=”UTF-8″? -tag…). They might have had to make up a bunch of new markers and tags and stuff to get this working, but it’s not that alien as what they threatened us with in the FAQ.”
XML v1 and UTF-8 encoding is just the standard header for XML syntax. The FCP X DTD is fcpxml, which is new. The DTD for legacy FCP was xmeml.
Apple has not yet posted developer documentation for FCPXML (aka AXEL).
Best,
Andy -
[David Roth Weiss] “I just tested to to see if XML Export was working, and it’s not working from a 10.1 timeline. So, what does that mean or imply to you?”
It implies you are inside a project timeline when you attempt to export the XML (just guessing). You need to highlight a project or event in their respective browser panes and then go to File > Export XML. Apparently, we don’t get to export project XMLs from within a timeline.
If that isn’t what you are doing and seeing, please share a bit more of what you are doing and seeing. It works perfectly for me. I just exported two event .fcpxml files and two project .fcpxml files and both imported right back in.
Best,
Andy -
[Marvin Holdman] “I assume shema=schema… right?
What is AXEL?”
Yes, schema, typo.
AXEL is Apple eXchange Editing Language, Apple’s name for the new schema. Though in the XMLs themselves they simply call the DOCTYPE “fcpxml”. AXEL is referenced in the Resources within the FCPX app bundle. Maybe AXEL is just an internal code they won’t be using publicly.
Best,
Andy -
[David Roth Weiss] “Apple should have spelled that out loud and clear. Every press release I’ve read today implies simply that XML Import/Export has been added to the 10.1 release. Nowhere is there any mention that it only supports special FCP X XMLs.”
Apple’s language, which I highlighted in my previous post, implies that it is an XML format specific to FCP X Proejcts and Events:
“import and export Final Cut Pro X project and Event information via a rich XML format”
Marketing 101 is accentuate the positive. They aren’t going to play up limitations in press releases, but they didn’t lie either. Are you sure you didn’t see “XML import and export” and immediately infer they had legacy XML import? I can see why it would be easy to jump to that conclusion, especially when everyone wants to be able to migrate their legacy FCP projects into FCP X somehow.
Best,
Andy -
[Craig Seeman] “Let’s just hope it’s not a $500 “quacker””
I bet there will be several of varying levels of sophistication with a range of prices.
Best,
Andy -
From Apple’s update page:
“Now you can import and export Final Cut Pro X project and Event information via a rich XML format. XML interchange enables a wide range of third-party workflows, including high-end visual effects, color grading, and media asset management. Blackmagic Design’s DaVinci Resolve, Square Box System’s CatDV, and many other third-party applications will offer XML-based workflows with Final Cut Pro X. (emphasis mine)
This is an all-new XML shema (AXEL), so it isn’t going to import FCP7 XML. Any third parties like they mention will need to develop a new parse for this flavor of XML.
Best,
Andy -
[Bernard Newnham] “Wondering what a “Xeon” actually is…just marketing or a different range?”
Multi-socket support and ECC RAM support are key differences. They also tend to offer more cores than their contemporary desktop counterparts. Xeons are not just a branding stunt.
Best,
Andy -
-
The Mac Pro’s rev cycle mirrors that of Intel’s Xeon chip rev cycles. It’s really just that simple. Sandy Bridge Xeons (the only new Xeon CPU rev since the Westmere Xeons presently in the Mac Pro came out) are only due to ship in November.
Unless Apple abandons the Xeon line for whatever becomes of the Mac Pro, they are joined at the hip to Intel’s release schedule for Xeon revs.
Best,
Andy -
[Michael Kammes] “Avid does indeed need the volume to be mounted in order to use it.”
Not just mounted, but exclusive for the sake of the MSM database, right? That’s why shared storage solutions like FinalShare and Xsan cannot host Avid bins for multiple users. The Avid is expecting to be the only host writing to the root of the volume, and they collide unless there is some mechanism there to direct traffic, which is what EditShare, Facilis, and ISIS/Unity are essentially doing (or are they?).
Thanks for indulging my ignorance on this.
Best,
Andy