Mitch Ives
Forum Replies Created
-
[Mike Jackson] “I’ve been having these same rendering issues for the last month, on two vastly different edit systems… Crossfades mis-rendering, going black, having shots freeze, text overlays mis-rendering or vanishing entireley… even banding in dips to black! “
After removing the two 1GB Apple memory modules and leaving nothing in but a matched pair of 4GB modules, I am now getting all the things that others are reporting… green screen that was rendering that doesn’t appear rendered anymore… cross-fade issues. I even got some instances where double clicking a clip in the timeline loads a different clip in the Viewer. Doing it twice manages to load the correct clip.
This is all on one of the 2008 MacPro 8-cores. Everything is a fresh install. I’m beginning to think they should call these machines the Mac Edsel instead of the MacPro. None of our other machines do this. Primatte Pro Keyer works fine on every machine but the 2008 MacPro 8-cores. Something is definitely different on these machines…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
[walter biscardi] “And of course the better question really is, “Anyone want to guess how many new features Apple will include in Studio 3 while not fixing many of the basic flaws that affect our day to day workflow?””
This is sad… but true. Glad someone said it.
I also wish we could go back in time to when QuickTime was for the pro Apps, not the iToys. Lately it seems like every QT update is for security relating to the iTunes music store, and each one seems to give those of us trying to make a living more problems with our Pro Apps. Personally, I’d like to see a bifurcation… one version of QT for the Pro Apps and a second for the iToys. That way you wouldn’t have to choose between having an iPhone or getting FCP to work properly…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
[Wayne Carey] “What codecs are you using when you see these render issues?
I’ve been using AJA Kona3: DVCProHD 1080i29.97 and I haven’t seen this. Maybe we can find a common thread in this issue. “
Same codec…
[Wayne Carey] “As for you, Mitch. You error is probably related to memory. Apple recommends certain memory requirements for the Mac Pro system for FCP. You system should have something like 2 gig, 4 gig, 8 gig, or 16 gig. Anything else can cause issues similar to yours.
Don’t ask me why. But I know that FCP is really particular about it memory requirements. Here’s what Apple says:
https://docs.info.apple.com/article.html?artnum=304492 “
Thanks for taking the time to direct me to this. I don’t know how I managed to miss this, but I’ll yank the two 1 GB modules and just leave the two fours in… easy enough. Again, thanks Wayne…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
[Wayne Carey] “I have not seen this issue at all and we’ve done alot of work with these systems. I wonder if it has something to do with the 4 gig range of memory. “
Actually, we have 10GB in the 2008 8-core, but then again our render issue is different than Walter’s and some of the others…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
[Warren Eig] “What issues are you guys having in what programs rendering? I have the previous generation 8-Core 3.0 GHz Mac Pro with 16GB of Ram and so far I’ve been trouble free… Well of course I just cursed myself, didn’t I? “
First, we’ve discovered that the previous 8-cores and the new 8-cores are totally different machines. Primatte has now confirmed that their new version 4 keyer will not run on the new 8-cores. It crashes immediately. Works fine on the old 8-cores.
On long renders (28 min.) FCP quits. If you do a third at a time no problem. I believe Walter (and others) are having a different issue, actual problems with the video image when it’s rendered.
[Jeremy Garchow] “Like what and what OS are you on?”
This is a 2008 8-core MacPro, running 10.5.2 and using FCP 6.0.2. We have the new plug-in mgr and EFI firmware installed. At this point, we’re trying anything… hell I may even try QT 7.4.5, we’re that desperate…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
[walter biscardi] “Maybe, I have to master off one more episode and then I’ll have all of those clear and we can go ahead, throw the 4GB RAM back in and see if that fixes it. “
I think I missed a chapter here. Did you determine that it was a RAM issue? I have a pair of 4GB modules in the new 8-core, and we’re experiencing some oddities during renders…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
Well, it works on an Intel Mac with 10.5.2 and FCP 6.02, using the same footage. This makes it an 8-core MacPro problem or a Kona 3 problem…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
For us, monitoring is fine IF you don’t have the inputs connected at the same time. Input was fine if you didn’t have the outputs connected. Basically, the moment you opened the Log & Capture window in FCP, you were hosed. So if you need a deck connected and want to capture, then you might need a GEN 10.
The bottom line is that the GEN 10 is a great piece of kit… and I can’t recommend it highly enough… $400 isn’t much to be completely happy and get back to enjoying the rock solid nature of AJA products…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
Shane:
I have no problems with short renders… even 10 minutes worth. It’s 28 minutes that brings it on. This sequence has a lot of green screen and I’m using a number of Livetype backgrounds on the keys, so that may be the issue. A week ago I had zero problems rendering 52 minutes of HDcam footage, but it had no keying and no LT backgrounds.
Raphael:
Not running DiskWarrior or TechTools. Perhaps I’ll give that a try.
Zak:
I’m using Livetype backgrounds, but not Motion. My issue sounds a lot like yours… the fact that some else is having issues with transparent black backgrounds, and you are experiencing issues with Motion, makes me suspect it may be related to the LT backgrounds…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com -
[Ramona Howard] “Since your stepping into HD, also check out their new Gen10 Tri-sync generator. For $400 it’s a steal and a MUST. “
You got that right. We lost a hell of a lot of production time, chasing some odd sync issues with both SD and HD. The Kbox SDI out had one problem, while the Kbox YUV out had another.
AJA Tech support got involved and nobody could explain why everything worked out fine on the Kona LH, but would not work on the Kona 3. Eventually, Rudy suggested to tech support that I try a GEN 10 as a long shot. That fixed it all.
Tech support has acknowledged that the Kona 3 achieves sync in an entirely different manner than the other Kona boards. The also acknowledge that the Kona 3 is a lot finickier on sync. Persoanlly, I think it’s the all digital nature of the Kona 3. The Kona LH series and the HD Io do not have this problem, but they both have analog capability that the K3 does not.
So, I’ll echo your comment… I think a GEN 10 ought to be bundled to the Kona 3 box…
Mitch Ives
Insight Productions Corp.
mitch@insightproductions.com