Dester Wallaboo
Forum Replies Created
-
Yes…. running 10.0.1 and all plugs are current.
-
I recommend using Sheer codec instead of Animation or others. It’s 100% lossless and supports 10-bit color space with alphas. Plus it has a fantastic color-space conversion algorithm. It compresses at half the size of Animation codec. So it’s a win-win situation.
https://www.bitjazz.com/en/products/sheervideo/
-
i7 iMac is certainly fast enough.
Does it play realtime after it goes through the entire sequence once?
For instance…. I’m on an 8-core Mac Pro with 12GB RAM… and there are many times when I build a lengthy RAM preview that it won’t play real-time for the first pass…. but after it goes through it once….. all subsequent passes are RT.
-
This problem is a memory issue in CS5. Since it’s 64-bit it takes every dang resource it can get its grubby little hands on. I found that I frequently have to flush the RAM in order to keep it perky. I’m running 12GB on this box and it still brings it to a stutter if I don’t constantly refresh the RAM on a heavy project. Also.. I’m pretty certain that CS5 has some memory leaks that need to be addressed. And yes… I’ve had multiprocessing turned off as it has its own set of issues.
On top of this… there is the weird rendering issue where CS5 ALWAYS looks at the layers below, even if the top layer is a non-alpha channel, full-screen video file. For instance… like most AE artists when we need to render a patch you usually bring in the previous render… the cut “holes” in the timeline so that only the new areas need to take full attention from AE. In CS4, After Effects would look at the top layer, conclude that it was indeed covering everything below that layer, and then ignore everything else below… clipping along nicely until it hits a patch hole where it needs to render everything below. This isn’t so with CS5… CS5 now looks at EVERYTHING below the video file regardless…. it’s really annoying. I now have to make a duplicate comp and throw away everything below that is covered up by the video file in order for it to move at any reasonable pace.
Totally annoying and unacceptable.
-
Nope… no changes…. nothing. It makes no difference. I’ve tried this on multiple projects with the same result in CS5.
-
Nope… it doesn’t work… same issue… it looks at everything. Definitely a new CS5 bug.
-
Nope…. the persistent, never-ending audio scrub bug STILL exists and is as bad as ever. I’ve worked this on numerous machines and they ALL have the same problem.
-
Because 90% of the civilized world uses After Effects in their daily workflow.
Why on earth won’t Apple support the standard?
I have people who have moved from PC to Mac (Premiere Pro to Final Cut Pro) and this is their #1 complaint by a long shot. I’ve used Premiere Pro and I’ve got to tell you… the ability to take Premiere Pro files directly into After Effects is an awesome time saving feature.
Automatic Duck is just peachy… but $500 friggin’ dollars a seat???? They must be out of their bloody minds!
Apple could do it… or at least buy up the assets of Automatic Duck and make it part of their full package. It would be a boon for their product.
-
I was afraid that was the answer.
Mind-boggling that Apple hasn’t made this a standard feature in FCP.
-
Is the footage interlaced?