[David Lawrence]

[Bill Davis] “Not if the 10 are useful to the vast majority of everyday editors – and the 20 are critical to only those who have niche “big facility” needs.”

Range export, persistent in/out points, audio sync markers are about as “everyday” as you can possibly get.

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Bill Davis] “Watch out David…

You’ve just described “magnetism” using the word “nice.”

That could eventually come back to haunt you.

; )”

LOL, I have no problem with ripple Bill. I just like being able to turn it off during the 90% of the time I don’t want or need it. 😉

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Jim Giberti] “Adobe added a little “Easy Bake Oven” for photographers to edit simple DSLR footage because everyone can shoot it now. A simplified, amateur product for the uninitiated.”

LOL, that’s really what it is, isn’t it?

But look! You can put dissolves between clips and they dissolve! Wow! How cool is that?

Seriously though, it’s a nice little add-on for DSLR photographers but that’s about it.

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Chris Harlan] “That would be my thought. Just one more little thing.”

Also interesting reading reviews of the UI:

iPhoto for iPad Hands On: Pretty and a Little Stupid?

iPhoto’s Mystery Meat Gestures

Not that it matters. They’ve already sold over a million copies.

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Chris Harlan] “Did anyone notice that Randy Ubillos’ title has changed? His title was “Chief Architect for Video Applications” but on iPad keynote video he is now “Chief Architect for Photo and Video Applications.””

Yup. As a matter of fact, he was the one giving the iOS iPhoto demo during the new iPad launch.

[Chris Harlan] “Do you suppose that is up a tier for Randy or down a tier for Video?”

Maybe both?

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Simon Ubsdell] “Interestingly the makers of x2pro have started to address this very elegantly with their implementation of roles in the AAF.”

Agreed. Looks like they’re doing some great work. Now let’s see if Apple can bring some of that elegance to FCPX. 😉

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Jeremy Garchow] “OK, and do you sit with the audio guys or are they offsite?”

Offsite. I get where you’re going 😉

My point is that I layout my audio tracks intentionally to make life easier for the audio guys. Or for me when I’m in STP. There’s more to it than just labeling, track order is important too and right now there’s no way to control that. Compound clips and controls hidden in the inspector add further complication.

I like seeing the exact same audio layout as my sound guys. It makes it easy to communicate and reduces potential for error.

[Jeremy Garchow] “Come on, dude. FCPX is perfect.”

So true! Luddite features like audio sync markers, persistent in/outs, and range export may damage the potential of FCP-X irreparably! 😉

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Jeremy Garchow] “Just curious, do you ever send your sequences off to audio post?”

Of course. OMF when I send to my sound guys. When I’m on my own, I actually prefer to round trip with Soundtrack Pro. Despite a few UI quirks, the workflow with STP is great and I have all the tools I need at my fingertips.

[Jeremy Garchow] “I would beg to differ again (Crazy, I know).”

LOL, well what’s crazy is 8 months and two updates out they still haven’t managed to provide basics like audio sync markers. What’s up with that? The fact that something this elementary is missing to begin with says a lot about their audio design assumptions and priorities. They have a lot of work to do.

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

I’m here for conversation, debate and learning with the smart ones, lol’s watching the crazy ones, and of course, Mr. Gallagher’s epic prose.

And please *don’t* change the name! Not yet, too early. FCPX still drives many of the best discussions here.

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl

[David Lawrence]

[Jeremy Garchow] “I know David L said that X’s timelines are incompatible with any other NLE, I would beg to differ. No offense, David, just pointing it out. Yes, sometimes it requires 3rd party support, sometimes it doesn’t, but that doesn’t bother me.”

No offense taken 😉

BTW, I wasn’t talking about interchange, which is clearly getting better. I was talking about the timeline itself, which is definitely odd man out in the post industry. Some folks like it and some think it’s a mess. I’m in the latter category. Maybe I’m weird but I think it’s important that the track layout I send to my sound guy looks the same as what I’m seeing in my NLE. I’m skeptical that roles will ever be as robust as a well organized track layout. I think it’ll be a while before we see this level of exchange from FCPX:
https://www.youtube.com/watch?v=onxjJbiQiW4
The reason this kind of exchange fidelity is possible is because the track-based world is a mutually understood language; a language that’s been shared by most time-based tools for decades. Apple has every right to try to reinvent that language, but choosing to go it alone instead of building on industry standards really only benefits Apple. They shouldn’t be surprised by an industry response like the ones from Bunim/Murray and Conan’s guys.

Of course if you’re happy with the workflow and don’t mind that timelines may look completely different as they move around the pipeline, by all means enjoy. All that matters is that it works for you.

[Jeremy Garchow] “The biggest thing that will stall FCPX completely (in my opinion) is not the Project or timeline or native format interfaces, but rather performance and reliability. People will find ways to work around any quirks, but if the program is crashing or in the one case we’ve heard about, corrupting beyond easy repair, then it will never get picked up by the late swath of professional editors, and I mean that in whatever pro space you work in. It needs more time in the oven.”

Agreed. I have a feeling that performance and stability improvements will be consuming the Pro Apps team for quite a while. For this reason alone, I wouldn’t hold my breath waiting for new features. They need to get the current release stable first.

_______________________
David Lawrence
art~media~design~research
propaganda.com
publicmattersgroup.com
facebook.com/dlawrence
twitter.com/dhl