[Andrew Richards]

[Rainer Wirth] “one year has gone by, since FCPX was released.”

Previewed. It was released on June 21st, 2011. It’ll be a year in a couple months. If Apple hadn’t been releasing meaningful feature updates to it every few months, I probably wouldn’t split hairs on the release date. But they have been, so I think it is only fair to start the clock when they actually released it.

Best,
Andy

[Andrew Richards]

[TImothy Auld] “Gulfstream V. You can stand all the way up in those.”

G5?

Naw.

G6.

https://www.youtube.com/watch?v=w4s6H4ku6ZY

Best,
Andy

Some contents or functionalities here are not available due to your cookie preferences!

This happens because the functionality/content marked as “Google Youtube” uses cookies that you choosed to keep disabled. In order to view this content or use this functionality, please enable cookies: click here to open your cookie preferences.

[Andrew Richards]

[Jeremy Garchow] “It gets weirder, our storage is actually NTFS. “

Well damn, now I haven’t even got a hypothesis.

Best,
Andy

[Andrew Richards]

[Jeremy Garchow] “We use metaSAN which is file based, so that might have something to do with it. It also works over ethernet as well. I have not tried it on volume level as it’s not how it’s setup over here.”

I’ve been trying to get a definitive answer on this, and have yet do do so. From what I can tell, FCPX is discriminating by filesystem. metaSAN is not its own filesystem like Xsan, but rather a shared HFS+.

One thing is for sure, SAN Locations are very poorly documented, especially in terms of technical requirements.

Best,
Andy

[Andrew Richards]

[Bill Davis] “Clearly your focus is more on the code underpinnings of the software than most of us who are largely focused on the user interface.”

I’m an engineer, not an editor. Once upon a time I wanted to be an editor, and I actually have my BA in Film. I quickly gravitated to the tech side though. Now my specialty is large-scale shared storage (StorNext/Xsan in particular). I’m interested in how FCPX might evolve into a collaborative facility tool, hence my earlier speculation. I want don’t want the death of Final Cut Server to be in vain!

I’m not a developer, but I find that world fascinating. One of these days I’ll teach myself to code more than shell scripts.

[Bill Davis] “I appreciate the time you take to post here from that perspective and I always look forward to reading what you write here.”

And I spend waaaay to much time reading and posting in here!

Best,
Andy

[Andrew Richards]

[Aindreas Gallagher] “the things that freak me out as a goggling half observer are: incidents of project corruption, incidents of event corruption, autosave fails, project bloat, and a possibly incorrect approach to the database substructure itself. Some people on here really know what the FCPX database is made of, there were discussions, I don’t recall them being cut and dried.”

The Project and Event database files are CoreData-based and leverage SQLite (one of the persistent data stores that CoreData can address). So there is some OS-level stuff that could be to blame for the problems we’ve seen reported, or it could be app-level stuff incorrectly calling CoreData. Or both. Only the dev team could know.

One thing I find really interesting is that Lion added a new CoreData class (NSIncrementalStore) that looks like it could be used to point FCPX at shared Events and even shared Projects on a shared database like a SQL server.

Best,
Andy

[Andrew Richards]

Render files live with the Project, so store your Project externally and the Render files will go with it.

Best,
Andy

[Andrew Richards]

I’m not going to get into my personal politics on these forums, but for the sake of furthering the discussion, here is an essay originally published on Slate in 1997 on this subject by Nobel Prize winning economist, Princeton University professor, and NY Times columnist Paul Krugman.

Best,
Andy

[Andrew Richards]

Dude, that’s so meta!

Best,
Andy

[Andrew Richards]

If you find yourself working at the limits of your hardware, optimizing to ProRes is a good way to ease the burden. Also remember that FCPX lets you edit immediately with H.264 while it transcodes and relinks to ProRes transparently in the background. And that is true background processing, unlike rendering which waits for an idle mouse. It does cost significant storage space though.

Best,
Andy