Devin Crane
13
COW Coins
4
Storage & Archiving Coins
Forum Replies Created
-
Your not using a Kona Card are you? I switched some settings on mine and got better render times although it was still slower that before.
-
I’m having the same problem on a Quad 3ghz Mactel and a ATI 1900xt card. The motion files consist of a shape with a mask for the background and some text with text behaviors added to them.
-
The card may have a difference in rendering but the problem is not with the card, I have the same card, but is taking 5x as long to render the same project in FCP6 than it did in 5.1.4
-
It’s not prefs, or the card, or the ram, or anything other than FCP6 neeind to have this fixed. It is only utillizing 100% of the processors instead of 180%-190% like it use to use before FCP6. It’s the code.
I’ve had the same problem with a 4x3ghz Mac Pro 1900xt card, 4GB ram, Xserve Raid. And takes 7hours to render an SD 58:30 with 20 .motn files overlayed on the timeline. Use to take 1 hour.
-
I switched to the Normal and my proofer who is not tech minded noticed a difference in quality right away.
-
I’m having the same problems to. I think they upped the quality on the Motion File render if you go into the Sequence Settings you can uncheck the render Motion files at best quality this will give you better render times but the quality drops. After looking at the best and the step down, I’ve opted to stay with the best. My 58:30 is taking close to 5-7hours on a 3ghz Mac Pro.
-
What do you mean by overhead with TCP/IP Protocol? Doesn’t Editshare use this? We are thinking of getting an Xserve and hooking it up to our current Xserve via Fibre Ch and connecting our workstaions via GigE. I’m not an IT guy so the protocol stuff is what I’m still learning about.
Thanks for any input
Devin Crane -
Tried it and was going to take 8 hours to render a 10 sec clip on a 4 core Mac Pro. I don’t know if it had anything to do with it being a multiclip or what but the processors were running past 200%.
-
FYI The 4.0 Driver has since been fixed according to AJA.
-
AJA has issued a beta to the 4.0 driver, it is something that they are working on at this time.
https://www.aja.com/ajashare/KonaLS_v4.0b143.tar this has fixed the problem.