fields being labeled wrong on import

[Jeremy Garchow]

Was this footage captured with FCP 6 as well?

Even the mighty After Effects interprets footage wrong sometimes, it’s fairly common.

[Josh Weiss]

There was no captured footage, this is purely generated material. It is either completely from After Effects or from a 3d package then into after effects, either way the initial source should be inconsequential.

[Jeremy Garchow]

[JWedit] “either way the initial source should be inconsequential. “

In your case, yes, but there’s been some issues with footage captured and then used in different versions of FCP. (V5 and 6 for example)

Sorry to keep grasping at straws, just trying to help.

At least it’s easy to fix what you are trying to do. FCP ALWAYS guesses premultiplied mattes wrong, and it doesn’t ask you what you want when imported either. Perhaps some feedback to Apple will do some sort of good.

https://www.apple.com/feedback/finalcutpro.html

[Gary Adcock]

[jwedit] “The same happens for footage that was imported in 5.1 and footage imported in 6. As Jeremy said, no consequence in 5.1 and there is a consequence in 6. There are no filters on these clips. Does anyone else have any idea”

I have not seen what format you are working with in this thread, but I am going to assume that it is HDcam at 23.98 sf.

you understand that the format for 1080 is a segmented frame, ie:plays back as interlace correct?

gary adcock
Studio37
HD & Film Consultation
Post and Production Workflows

[Josh Weiss]

Gary,

We are working in 8 bit uncompressed, progressive renders.

Anyone else have any ideas, or at least a way to change the way final cut brings the clips in without having to change every clip we edit.

[Gary Adcock]

[JWedit] “We are working in 8 bit uncompressed, progressive renders.”

8 bit what???
Like I said I have not seen a frame size or rate. I do not care what bit depth.

what format? 1080, 720, or SD

there is little for us to go on to answer the questions

gary adcock
Studio37
HD & Film Consultation
Post and Production Workflows

[Josh Weiss]

SD 720 x 486

[Martin Baker]

As FCP can’t tell whether an imported movie has fields or not, it must be working to an internal list of rules (just like After Effects does) when it imports a file. If it sees a 720×486 movie then it’s a reasonable assumption (99%+ of the time) that it should be interpreted as Lower Field First. There aren’t any import options to change this behaviour so the only option is to change the field order manually after import.

Certainly in FCP6 changing the field order from LFF to None on a progressive source in a progressive sequence does make a difference. If you don’t then half of the vertical resolution gets thrown away because each source frame will get deinterlaced.

Martin
Digital Heaven, London UK
Unique plug-ins and tools for Apple Pro Apps
———-
Avid2FCP
For Avid editors learning FCP

[Josh Weiss]

Martin

Thanks for the advice, but in our workflow that means that about 30 times a day we will be manually changing every clip that we edit. If anyone has any quick work around or at least a way to quickly change multiple clips that would be great. Thanks again.

[Gary Adcock]

[jwedit] “in our workflow that means that about 30 times a day we will be manually changing every clip that we edit. If anyone has any quick work around”

create a new easy set up with the field order corrected and use that for your seq setting.

FYI

In SD — PAL is upper field , NTSC is lower field first.

g

gary adcock
Studio37
HD & Film Consultation
Post and Production Workflows