Kris Anderson
Forum Replies Created
-
Then that’s where your problem was occurring.
You were digitising (correctly) with lower field dominance in FCP and then importing with PAL upper field dominance in Avid. Your Avid import setting should have been lower field dominant (assuming the clips were exported in with lf dominance).
-
Just out of curiosity, were you working in PAL or NTSC?
-
John, I think you’ll find my understanding of field dominance as it relates to PAL and NTSC is correct if you research it a little further.
FCP and Avid are both capable of upper and lower field dominance depending on the setup of the project. They are not limited to one or the other.
So we can help you get to the bottom of this can you please tell us your working format, project settings, sequence settings, ingest settings etc. Are you working in PAL, NTSC or HD? If HD, which format?
With FCP, are your ingest, sequence and export settings all the same? Then with Avid, are your import and export settings the same?
There are a number of places your field issue could be creeping in. Let’s start from the beginning of your workflow and see if we can isolate where things are going wrong.
-
Still not digging Interplay. Had an editor overwrite entire sequences that I had worked on this week. Local media is invisible to my suite even though I can see the .mxf files on my drives. No lock out functions like in Unity…. and Avid specifically state “do not share projects” in their “Interplay do’s and dont’s” guide. Totally at odds with how we work and have done for years. Great for finding cips and I like Avid but interplay just blows from an editorial pov.
-
iTunes requires Quicktime to function. As Apple is always updating the program, it usually requires the latest version of QT, which is at odds with Avid’s required version of QT which is usually a few updates behind.
-
Avid is not upper field dominant, and FCP is not lower field dominant. As mentioned, field dominance is related to video standards, such as PAL/NTSC, not an NLE.
I’d say the reason you’re not seeing the error on the QT’s is because you’re watching them on a computer monitor. Computer monitors do not display interlaced fields. DV (Pal/NTSC) and NTSC are lower field dominant. PAL is upper field dominant.
I’d check your digitise and export settings from FCP and your import/export settings in Avid. Both programs will do what you tell them to do. Check what you’re telling them is correct.
-
If you’re a student you can pick up an SDI Mojo for around $950 from sellers on ebay. This will give you proper video input/output.
I’m curious as to why you keep calling them “Avid” monitors? The Avid software is simply running on an off the shelf PC or Mac, so not sure why you think the colour issue is caused by Avid.
Personally, I grade in Avid a lot when budget doesn’t allow us to go to a higher end suite. With an SDI out and a calibrated SDI capable CRT monitor, whatever I do in the suite looks exactly the same when I see it on air.
-
Fair call Grinner. I’m starting to come around… just blew my )previously very successful) workflow out of the water. Time for an old dog to learn a new trick. I’ll get there!
-
The problem is not the Avid application. It does what you tell it to do based on what your eye is seeing on your computer monitors. Computer monitors are not accurate for colour grading purposes. As mentioned earlier you need a Mojo and a proper, calibrated broadcast monitor to make accurate colour decisions.
-
Same problem here. All Unity media is fine but my 8tb local array media is all offline, even though a “reveal file” command shows the .mxf files in the correct folder. Really pissing me off.