[Donal O kane]

How are you importing the footage from AE into media composer?

All quicktime imports are changed to 8-bit … except for AMA linking and fast importing of DNxHD codec quicktimes
https://community.avid.com/forums/p/96816/554911.aspx

So going from 10-bit to 8-bit will destroy gradients?

[Donal O kane]

for step 3 when applying the LUT to the track ….

do you add it to both input and output format?

[Donal O kane]

Hi,

Sounds like a dead/dying graphics card … if you access to another one try swapping it out or try replacing it.

or you could try this … seems a bit wild !
https://www.google.co.uk/search?client=safari&rls=en&q=Fix+your+8800gtx+Graphics+Card+(STEP+by+STEP)+by+Baking+it+in+the+OVEN.&ie=UTF-8&oe=UTF-8&redir_esc=&ei=gbL_TeXkOdG4hAfG1rGcCw

“The problem is lead free solder (and to a lesser degree, insufficient cooling) on your card, I’m betting it’s a revision 1 but they all suffer from failed solder joints”

Apparently you can bake these cards in the oven (the first video in the above link shows how (but bake it face up).

I’m not recommending 🙂 just pointing out a possible solution 🙂

I’d try replacing the card with a borrowed one first to make sure that that is the problem..

Good luck

[Donal O kane]

The update to resolve 8.1 which is due out any day now is supposed to have better avid round tripping ..
however it isn’t here yet and your project is …

I have found that certain things cause the AAF import in DaVinci to behave in what I can only describe as a screwy way.
1) Transitions other than a simple fade (dips to colour included)

2) FX but Motion effects especially … you have mixed these down so should be ok.

3) Non-alphanmumeric characters in clip names … this sometimes seems to be the case but not always

4) Different sized handles … has caused certain clips to be duplicated in my timeline … stretched to full handle length (pushing all other clips out of sync)

5) Sometimes resolve just plain doesn’t like a sequence and I have duplicated/renamed/mixed down portions/whole seqs (this will of course loose your handles) to try and get it work and the magic combination is in there somewhere but I haven’t cracked the exact combination yet.

Resolve renders do weird things with handles on the trip back to avid .. adds black if the handles are not long enough and then when you relink it starts at the (black) start of the handles not the clip start point.

Hope some of the above helps

[Donal O kane]

I get this sometimes, no rhyme or reason to it as far as I can tell … up to date nvidia and cuda drivers & no monitors … reseated card etc …

I shutdown … (wait for 20 or so seconds type shutdown) … and restart usually goes away for a while.

[Donal O kane]

There is an option when you right click on any of the clips in the color tab timeline for batch unlink.

[Donal O kane]

I really hope someone will post an answer that fixes this for you completely, but for me its the holy grail of FCP.
Stop crashing randomly!

Things to check:
what version of FCP are you running 7.03?
Quicktime version?
os x?
have you run any automatic update since the crashes appeared? Leopard had a quicktime update a few weeks back didn’t it? or was it snow leopard?

How are your hard drives and IO device, I put the blame on my random crashes on these two. Especially with HD footage.
Are your harddrives too full, can you run a speed test, blackmagic & aja have one.
If the average speed is ok but every so often you get a big dip in speed occurring this could cause dropped frames and crashes … mostly dropped frames for me.
This is why good hardware raid boxes cost what they cost, are worth it and are next on my to-purchase list.

IO device, what are you using and have you updated drivers recently?

Oh and is it in any way regular, can you test the same sequence playout without the closed captioning to see if it is the closed captioning causing the problems?

Also some would call it a last resort but do you have a carbon copy cloner (ccc) backup of you system drive that you could plug in or restore from?
Some times I find that a system that has been working perfectly will develop gremlins and a complete format and os x and fcp reinstall works to oust problems (thats why you make a ccc backup of a freshly installed system to restore from instead of sitting through the reinstall every time).
It is also a good idea to ccc your current setup in case it doesn’t fix the problem.
All this takes time but if it fixes random problems that cost you time and money and errors in front of clients it can be worth staying in late/setting going overnight in my experience.

Good luck

[Donal O kane]

The best way to do this is to trick fcp and color.

So FCP and color are looking at your footage currently in a particular folder or group of folders on your hard drive.

With FCP and color closed you can rename these folders, and exactly recreate this structure .. and I mean exactly … file names and relative positions.. with your prores footage so that when you open FCP & FCP, they look for Drive>Directory>File 1 and find it .. but it is now a prores file.

Just tested works with FCP and color as long as files are the exact same name and in the exact place.
Color renders the new files as pro res and only difference is in the sequence settings when you send to FCP … but thats easy to change.

[Donal O kane]

where is the footage coming from?

[Donal O kane]

weird.

If you want can you email me you fcp project .. i’ll have a look and see if I see anything

donal.okane at gmail dot com