disregard code?

[Ed Dooley]

Um,…Capture Now.
Ed

[Scott Witthaus]

no, I don’t want it to create a new clip on each break…just roll straight through…thats what Avid does on Live capture. Creates new TOD code as it imports…

Scott Witthaus
Senior Editor/Post Production Supervisor
Greybox, LLC
Richmond, VA USA
http://www.greybox.cc

[Walter Biscardi]

[Scott Witthaus] “no, I don’t want it to create a new clip on each break…just roll straight through…thats what Avid does on Live capture. Creates new TOD code as it imports…”

Yes, it’s Capture Now like Ed said. You need to go into your User Prefencers and tell FCP to “Warn After Capture” on the TC breaks and turn off “Start / Stop Detect” in your Log and Capture window.

Though I would leave Start / Stop detect turned on as it’s seamless and does not stop the capturing. This way you at least can recapture clips at a later date rather than FCP creating all new timecode that does not match what’s on the tape.

Walter Biscardi, Jr.
https://www.biscardicreative.com
HD Editorial & Animation for Food Network’s “Good Eats”
HD Editorial for “Assignment Earth”

“I reject your reality and substitute my own!” – Adam Savage, Mythbusters

[Scott Witthaus]

darn this new fangled FCP….

OK, so when I am making new clips, I am not losing any media, just breaking them out per camera start and stop. Thats good then, cause it will be easier to rename them into shots. Sorry for the basic question. One of the challenges I see with FCP is that settings can be changed or have to be made in a variety of places! Thanks all!

Scott Witthaus
Senior Editor/Post Production Supervisor
Greybox, LLC
Richmond, VA USA
http://www.greybox.cc

[Jerry Alto]

Scott- Just a little advice from a person with experience; don’t try and force FCP to work like an Avid…. it will only cause lots of frustration. Let go of all the Avid ways of doing things but use all of your editing experience and you will be flying with FCP in a couple of weeks. Some of the workflow will seem very strange at first but will make sense as you become more fimiliar with it. I came from m100 and it was real tough at first ’til I let go of the m100 workflow and accepted that I was in a whole new world. Good luck.
Jerry

G5 Dual 3GB Ram
FCP5 Studio
External 1 TB SATA Raid 0
Kona LH, Second system w AJA ioLA
Sony Z-1

[Debe]

I second that. I was trained on Avid in the early ’90’s. FCP fruatrated the bejeebers out of me for years until I finally wised up and took the first certification course at a local training center a few years back.

It’s a night and day difference in how much easier I find working with FCP now than before. Trying to create Avid-like workarounds really defeats the strengths of FCP and will make you think it’s an inferior tool, instead of a different tool with it’s own strengths.

Now that I know both equally well, I find I like working on either one just fine, and I’m really in a good situation when I get to choose which tool is best for the type of project I’m working on.

Trying to force FCP to work like Avid is going to make you feel like you’re banging your head against a wall. Trust someone who still has dents in the forehead, it’s much better to learn FCP for it’s strengths, rather than trying to force it to do things in a way it wasn’t designed. That’s not fair to you, and espeically not fair to your clients.

Sure, there are plenty of things that I wish FCP did better, or just did, period. However, considering where we started, and how far it’s come in a relatively short time, it’s still pretty darn impressive, especially when you factor in the cost.

my 2

[Scott Davis]

[debe] “Trying to create Avid-like workarounds really defeats the strengths of FCP and will make you think it’s an inferior tool, instead of a different tool with it’s own strengths.”

That is about the best repsose I’ve heard when Avid centric folk start complaing about non-Avid tools.

[Ed Dooley]

Repeat after me, “I am an Avidholic, it’s been (fill in the blank) days since I’ve had an Avid. With
your help, I know I’ll make it.” 🙂
Ed

[Scott Davis] “[debe] “Trying to create Avid-like workarounds really defeats the strengths of FCP and will make you think it’s an inferior tool, instead of a different tool with it’s own strengths.”

That is about the best repsose I’ve heard when Avid centric folk start complaing about non-Avid tools.”

[Scott Witthaus]

ah yes, I have heard this before. Actually, I have been on FCP for several years now, and Avid for many years. FCP certainly has its strengths, as does Avid. Both are simply tools. I use FCP or Avid for spot work, Avid for longer form (media management is superior in Avid).

No biggie here folks, I understand the toolsets. Just a simple question (on a wacky HDV project), one that was answered well before the worn out “don’t try to make FCP and Avid” lines hit the threaed! You also have to realize how many Avid features Apple “borrowed” to create FCP before you go there!

Respectfully,

Scott Witthaus

Scott Witthaus
Senior Editor/Post Production Supervisor
Greybox, LLC
Richmond, VA USA
http://www.greybox.cc

[Debe]

Gee, Scott.

I’m sorry.

All I meant to do was to help another editor make a transition and perhaps not have to go through some of the more frustrating things I encountered, or at least not go through them for as long.

We usually try to help one another here. I don’t know you, I don’t know your background. I was simply trying to help. It certainly wasn’t meant to be an “Avid vs. FCP” throwdown. At least not from my point of view.

It was meant to be helpful in the most best-intentioned of ways.

I’m truly sorry you took it the wrong way.

debe