Re: Editing scenario

[Jim Giberti] "But Walter, I was responding to your assertion that changing the timeline to be more traditional in organization would be very, very difficult because of the underlying foundation of the program. My example simply shows that it's incredibly simple."

That's fair, Jim. The sentence of mine that you quoted and responded to was a gross oversimplification on my part. You're right and I was wrong.

If you look to the paragraph immediately before my poor summary sentence, I think we may agree:

[Walter Soyka] "The timeline, as it stands now, is a direct expression of the data model revealed by FCPXML. All the tools in FCPX are built to manipulate the unique objects of this data model. Any changes to the timeline must be compatible with the parent/child data model, or the data model must change with it; any changes to the timeline may also require overhauling the NLE tools."

What I was trying to assert, in a mistaken response to Jeremy, was that FCPX's timeline's data model is foundational to the application, and changing it would be hard. You can work within it, but I think actually replacing it wholesale would require some pretty deep work.

By the way, I think your method is a brilliant -- a truly elegant hack to fit a traditional timeline into FCPX's structure and seemingly arbitrary container restrictions. I wish Apple had built this in, per Mr. Lawrence's multiple primaries. I do believe we could have the best of both models coexisting within FCPX.

Walter Soyka
Principal & Designer at Keen Live
Motion Graphics, Widescreen Events, Presentation Design, and Consulting
RenderBreak Blog - What I'm thinking when my workstation's thinking
Creative Cow Forum Host: Live & Stage Events