Why FCP?

No kidding. If that scars you, check this out:

waltind said:
teh correcponding

I swear english is my second language, and typing doesn't help my skills out any ...

when the credits roll on our short just make sure that I haven't done this:

Teh Ned
:cheesy:
 
So I know you've all been waiting on pins and needles to hear how the two methods of capturing went here are the results (my thoughts are below):

CaptureTest.jpg


Well it looks like the comments about the start stop detection were right. It does not do a reliable detection of each of the scenes / takes. You can see minor differences in the time code start times for each clip.

Even if this feature worked correctly I would still not use it just do to the fact that I would have to go back in and rename each clip so that I knew what it was. Currently this method names each clip as Segment 01, 02 ... Which is of no help to me, as I've got my clips numbers by scenes and takes. It is just easier to have someone log the clips as we go, preferably into a laptop, and then have FCP capture them correctly with the names already to go, this makes it a hell of a lot easier to organize and find clips when I need them. Anyway, hope this helps, as I'm sticking with my method of capturing.

BTW- yet another thread sucessfully hijacked by a related but tangential question ...
 
David Jimerson said:
Absolutely you'll have many, many clips.

But what Brian and John describe can allow for this (which I do in Vegas all the time):

Be disciplined about stopping the camera and starting recording at each take with a slate.

Capture with scene detection.

Then, as long as you were judicious in the use of the slate and kept the discipline, after you capture a tape, you should have a folder full of thumbails, each of which being the slate for each take. (Of course, if you weren't judicious, you'll have doubled-up takes somewhere, but you should have a written shot log, too.)

It is then unnecessary to log the takes manually.

I find it to be an excpetional time-saver. It works so well, I can't even imagine why you'd call it "home movie-esque."

It's not 'home movie-esque'. That's just a chop-shot at non FCP users. (no offense KAI; you my nizzle :cheesy: :beer: )

The reality is that it is an old school way of doing things. Nothing wrong with it; just not the most efficient method of doing things. I can't imagine doing it any other way with drive space being as abundant as it is.

I'm sure it goes both ways however. FCP having some way of doing something that VEGAS users would be like 'Whoaaa!' (Keanu voice)

At one point though; as Brian has done, an FCP user's is gonna have to admit that it's wacky and 'needs a fixin'
 
But in all honesty, I would be willing to bet that Vegas has ways of doing things that would make a FCP (or Premier, or Avid) user go, "Whooa"! And vice a versa.

Yet, I am distress about this capture situation.

Ryan, does the spead sheets you provided allow for batch capture of 24pa footage?
 
DV Metadata is SO underutilized in video software it's not even funny. In a perfect world, we would have on import: f/stop, shutter speed, time, date, and the timecode numbers. On export, the computer could offload tapes in a way with a random time/date code which would trigger the Start / Detection for the practical import of repurposed DV material (capture your edited footage and re-edit it) but none of these things have ever been implemented in any NLE I'm aware of.

Sorry, I'm an idea guy.
 
thisiswells said:
Sorry, I'm an idea guy.

I'm an idea guy", is a great quote, from Night Shift, with Michael Keaton.

"Feed mayonaise to tuna fish. I'm an idea man, Chuck".

Keep up the good work Brian. I love your ideas... I've been thinking about that 7" touch screen all day...
 
thisiswells said:
DV Metadata is SO underutilized in video software it's not even funny. In a perfect world, we would have on import: f/stop, shutter speed, time, date, and the timecode numbers. On export, the computer could offload tapes in a way with a random time/date code which would trigger the Start / Detection for the practical import of repurposed DV material (capture your edited footage and re-edit it) but none of these things have ever been implemented in any NLE I'm aware of.

Sorry, I'm an idea guy.

WHOA! (In Keanu voice)
 
David G. Smith said:
Ryan, does the spead sheets you provided allow for batch capture of 24pa footage?

The spread sheet is format agnostic. It is specific only to FCP. So if you have 24pa, 24pn, 60i, 720p ... well you get the idea- it will work. All you're doing is typing in the time code, name, discription, and any other notes and then exporting it as a batch capture list. What lets the computer know how to capture the footage is you capture settings.

The image above is from a batch capture that I just did today, so I know it works. :)
 
thisiswells said:
Sorry, I'm an idea guy.

Don't appoligize- it's cuz of idea guys like you that things change and get better. Those are some great ideas, and you could probably make a bundle of money if you developed an app to work with FCP to do just that ...
 
David G. Smith said:
image on the left is batch captured cips and image on the right is start/stop detected sub-clips correct?

Yep. Left is using the Excel Spread sheet, right is start stop.
 
John_Hudson said:
It's not 'home movie-esque'. That's just a chop-shot at non FCP users. (no offense KAI; you my nizzle :cheesy: :beer: )

The reality is that it is an old school way of doing things. Nothing wrong with it; just not the most efficient method of doing things. I can't imagine doing it any other way with drive space being as abundant as it is.

I'm sure it goes both ways however. FCP having some way of doing something that VEGAS users would be like 'Whoaaa!' (Keanu voice)

At one point though; as Brian has done, an FCP user's is gonna have to admit that it's wacky and 'needs a fixin'

OK I agree, it was a lil pot shot ;) It's just my mentality showing through. I like complete control over my process and workflow. That's why AE, flame, etc are my tools vs something like Motion. I don't like software to do ALL my thinking and creativity for me, because 1) if something gets jacked up, you won't quickly know where to look, 2) what's the fun in that?! , and 3) when applications, plugins, etc start taking the majority of the workload, that's when your work can start to look like everyone elses, and there's more chance for less creativity/originality.

Now, believe me i'm not saying logging and capturing has anything even remotely to do with creativity, i'm just referring to my workflow in general. I also agree that if Apple says a feature is in their public release of a product, it'd better frickin work how they say.

We should form a class action suit against them claiming our collective carpal tunnel is from the manual logging we had to do because their start/stop detection doesn't work.

:)
 
kai said:
We should form a class action suit against them claiming our collective carpal tunnel is from the manual logging we had to do because their start/stop detection doesn't work.

:)

LOL!
:thumbsup:
 
kai said:
I like complete control over my process and workflow ... I don't like software to do ALL my thinking and creativity for me

Yeah the more control the better, and that's not just because I'm a control freak :grin: A lot of times I want things named / processed a specific way and teh auto features just don't seem to think like I do, so they mess it all up and create more work for me ... (Besides being unoriginal, and looking like all the other stuff out there.)
 
kai said:
OK I agree, it was a lil pot shot ;)
We should form a class action suit against them claiming our collective carpal tunnel is from the manual logging we had to do because their start/stop detection doesn't work.
:)

Don't say Class Action too loud to Apple. They have too many iPod Nanos packed in a warehouse to take it as a joke.... :cry:
 
Back
Top