-
Sharing practices for those who do not get corrupt frames
Hi,
I’m on job number 3 now with X. And the one thing they all have in common is that every time I export, I have corrupt frames that blink various colors or turn green. I’m on a mid 2011 Imac i7 3.4 16 gigs of ram.
Now two things are happening at random.
1. After sharing I find the green frames in the project and have to roll over the cut to fix it.2. The corruption shows in the exported video but is nowhere to be found in the timeline (project). I have also had 30 seconds of audio disappear in this fashion.
So I’m wondering if there is a certain practice that I should do when exporting. I am now clearing all renders prior to export. Are most of you exporting a “same as source” file out of FC first and then bringing that file into compressor? Or are you sharing directly from FC? Is it bad to continue editing while sharing? Should I export and HQ file first? This is driving me nuts.
As much as I dislike using the program, the truth is the multi-cam projects I’m doing are only possible in X. However, the time I’m losing on sharing I could stack clips in another program and save about a day or two at this rate.
Could daisy chaining FW800 drives cause this? A bad FW800 cable? I also use Magic Bullet recently, but had this problem before I installed it, and the corruption happens on clips with no filter and filtes alike at random.
-
9 Replies
-
I’ll assume you’ve tried a reinstall? Both final cut and OS X? And do you have FCP studio or any part thereof installed? The only time I’ve come across green frames was a friend who had legacy FCP installed on the same machine. A complete reinstall (minus any legacy FCP apps) fixed the issue for him.
For what it’s worth, I’ve done twenty something projects in FCPX and have yet to see a green frame myself. Earlier this week I had two projects exporting, footage from a CF card importing, and was making some minor tweaks to titles in a third project ready for export – all at the same time, no issue whatsoever (other than speed because I really was trying to do too much at once).
I always put my lack of any issues down to following Apple’s install recommendations to the letter and never having any legacy apps installed on the same computer.
It really sounds like you’ve got some sort of QuickTime issue – hopefully someone has a fix for you that’s slightly more refined that “nuke everything”..
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
Never thought about the FCP 7 thing. I indeed do have it installed. Funny thing is I had read on here of several people having it installed on the same system with no problem so I never thought of it. I haven’t reinstalled but I did upgrade it from 10.05 which had the same problem and it didn’t get any better. Also I upgraded the OS before going to 10.06.
I’ve done numerous projects on 7 that never had the problem either while having X installed. If it were a QT problem, shouldn’t I see it coming from my other NLE’s as well?
But I’ll try unistalling 7 and seeing if it makes a difference. Thanks for the tip.
-
You could also try creating a new user account on your Mac and using that to see if it helps, I don’t get the corruption on my system but it did help me troubleshoot another’s couple of issues a while ago.
Steve Connor
‘It’s just my opinion, with an occasional fact thrown in for good measure” -
Have all of these jobs been started as new events and projects after the update 10.0.6? Or were they updated from previous versions or imported from some other XML path, like 7toX or Resolve?
If so, have you tried a very simple test project created completely from scratch after the 10.0.6 update?
– Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
Apple have always strongly recommended not having legacy FCP installed on the same machine as FCPX. I think it’s one of those things that some people get away with and some don’t. I know the only time I had any can’t-get work-done issues with FCPX was when I decided to install DVD Studio Pro and Soundtrack Pro on my FCPX system.
The QuickTime issue thing is purely my theory but I suspect there are conflicts between ‘real QuickTime’ as installed and used by legacy FCP and the ‘pretend it’s QuickTime for backwards compatibility’ version that’s part of AV Foundation that FCPX uses. And somewhere inside the interrelated labrynth of OS X internal APIs, FCPX ends up accessing libraries that call the wrong bit of code, that messes with its stability. Just a theory though.
I do know that nothing short of a clean install got FCPX back on track after my legacy FCP fiasco.
Jeff Kirkland | Video Producer | Southern Creative Media | Melbourne Australia
http://www.southerncreative.com.au | G+: https://gplus.to/jeffkirkland | Twitter: @jeffkirkland -
The first project was in 10.05 which had the problem. This latest one is freshly started in 10.06. I uninstalled and reinstalled and am still getting the same problem. Actually now, I’m not getting the green frames. I’m getting complete freezes in various random spots (something that was also happening before along with the green frame).
I’ve also range exported the problem areas and of course they come out perfect. The problems happen at random spots.
I went to the apple site and it had instructions for having both software on the same system. I didn’t see any warnings against doing so. Also this problem only happens when exporting out of X. As far as QT is concerned, I can export out of 7, Avid and AE with no problem. I need Final Cut Studio for DVDSP to make dvd’s when I’m done.
Will I have to uninstall the whole suite? This is bad news if so, though I have a feeling uninstalling FCP 7 isn’t going to solve this problem for some reason. I thought the issue of 7 and X had to do with startup conflict. Both run fine with no issues.
-
It’s probably a bug related to a codec or filter effect or the GPU card. I doubt a reinstall of the software will fix anything.
Oliver
Oliver Peters Post Production Services, LLC
Orlando, FL
http://www.oliverpeters.com -
I’ve had some odd glitches on export on my 17″ pre thunderbolt MacBook Pro. Fairly sure it’s a problem with the memory but I haven’t had a chance put confirm it.
Michael Sanders
London Based DP/Editor -
Well I’ve uninstalled FCP 7 and still no luck. I’m wondering now if its a computer problem in which case I am not very savvy. I wouldn’t even know where to start at this point. Not having used it since the FCP X install, I went back to avid to try and export out footage and its giving me problems as well. I noticed I could export small clips, but it would get stuck when I went across several clips. Prior to the install I had no problems.
I’m not sure the two are related. I’d have to run more tests in avid to see whats really going on. I’d try from 7 but I uninstalled it. Wish I hadn’t now.
Reply to this Discussion! Login or Sign Up