Should Apple attend NAB this year?

[Craig Seeman]

[Chris Harlan] “Oddly, I think that’s one of the issues that defines the Industrial-strength dividing line we so debate here”

I don’t disagree (to use a double negative). What made FCP legacy so valuable is that there was always a way to do the “uncommon” thing one needed to do. It may well be that despite the fact than any number of features were better in either Avid or Premiere Pro, with FCP it just seemed there were more ways to dig out of a problem.

Currently its much harder to dig out of many problems with FCPX. I think that will change over time but I think Apple is taking a different approach regarding how FCPX grows in that direction. Apple’s approach seem to gear more towards developing hooks for third party utilities and we can and are certainly debating that as a design philosophy.

As one example, some might say FCPX XML might be alien and it might be powerful and the debate whether the Alien or the Power will win. I think some see 10.0.3 as the first version where promise begins to show as 7toX became possible and the hooks were fixed to the point MagicBullet Looks could finally be released. Hooks, although a very rough beta, show that Broadcast Monitoring solutions will work (at some point).

If FCPX divergent philosophy from FCP7 is to be a hub for third party solutions for niche handling the hooks do need to be robustly developed. This year will be interesting in that regard.

[Chris Harlan]

[Craig Seeman] “I think some see 10.0.3 as the first version where promise begins to show as 7toX became possible and the hooks were fixed to the point MagicBullet Looks could finally be released. Hooks, although a very rough beta, show that Broadcast Monitoring solutions will work (at some point).”

Yes. 10.0.03 has renewed my interest primarily because of few less-publicized developments like file relinking. It is little things like that that give me some hope that I may again find a home here. Or at least a summer house. Seeing what happens with this XML is quite interesting for me. Xto7 will finally allow me to play with X a little more seriously, so I’m looking forward to that, sometime after up fronts and May screenings. I don’t know if I will eventually like the user metaphor–bin-less, trackless, roles, etc.–but I’m happy X is moving into an arena for me where it becomes a matter of taste and not lack of features that is the deciding factor.

[Jeremy Garchow]

[Shane Ross] “I beg to differ. I captured all the time directly into FCP via Log and Capture. Batch captured, captured now…output to tape. ALL within FCP. I never used the capture/output apps provided by AJA, Matrox, or BMD. It was not “absolutely required.””

So you don’t consider AJA, Matrix, BMD third party?

Then I guess we see the world differently.

You could not capture from tape without buying third party.
Sorry guys, it’s true.

If AJA or whoever can hook in to FCPX, then it will essentially be the same thing, except you will have a capture interface that is designed by the people who made the software, instead of FCP’s goofy interface.

And potentially, if you have an AJA or whatever card, that capture utility will be the same across all applications if you choose.

I also see this is a good thing. Perhaps you don’t, thats fine.

Tape capture from non firewire sources in FCP legacy absolutely required a third party

Jeremy

[Timothy Auld]

Didn’t realize non firewire sources were excepted. Sorry.

Tim

[Chris Harlan]

[Jeremy Garchow] “So you don’t consider AJA, Matrix, BMD third party?

Then I guess we see the world differently.

You could not capture from tape without buying third party.
Sorry guys, it’s true. “

Sigh. Jeremy, of course you need to buy the hardware, and of course the hardware has drivers. The point is that FCP had a built in utility that allowed you to edit directly from i/o makings on a timeline. X doesn’t, right? Am I missing something here, or isn’t that the point?

[Jeremy Garchow]

[Chris Harlan] “The point is that FCP had a built in utility that allowed you to edit directly from i/o makings on a timeline. X doesn’t, right?”

X does not.

But it does have a “tape capture” interface. It’s rather limited, but then again so is capture card support at this time.

You can sigh. It’s OK, but we see this differently.

[Chris Harlan]

[Jeremy Garchow] “[Chris Harlan] “The point is that FCP had a built in utility that allowed you to edit directly from i/o makings on a timeline. X doesn’t, right?”

X does not.

But it does have a “tape capture” interface. It’s rather limited, but then again so is capture card support at this time.

You can sigh. It’s OK, but we see this differently.”

I’ve been sighing all day today. I guess I just see it as semantics. I personally have not had to insert edit to tape in over a year and a half, and that broke a three year hiatus. Of course, the one time I HAD to do it, saved several thousand dollars AND let me get enough sleep on that particular night that I could actually call it sleep, and not a nap.

But that specific function is what this fracas is about, right? And, I get that you are saying that hopefully Apple will allow hooks into that tape capture interface that card makers can grab on to. But that right now, it is not there. So, I guess, is this debate to decide if, say, the hidden Decklink module behind FCP capture module should be called a supplied driver or a 3rd party App?

[Jeremy Garchow]

[Chris Harlan] “I guess I just see it as semantics. “

I think it’s important to point out the similarities and differences.

[Chris Harlan] ” So, I guess, is this debate to decide if, say, the hidden Decklink module behind FCP capture module should be called a supplied driver or a 3rd party App?”

Both. They will write (have already written) drivers that will supply their third party app.

If X allows this capability, I’d much rather have the manufacturers running the show as they can interface with their card the best. VTR Exchange has always been more reliable than FCP’s log and capture, but maybe that’s just me.

Capture will be a lot easier than output.

X will need some work here.

I never insert edit, I always start over and restripe the whole tape with a clean run.

Although, I rarely layoff to tape anymore, I do use rs422 to Kipro pretty frequently though. No inserts allowed there quite yet, either.