Brian Charles
Forum Replies Created
-
Watch the values for scale, when you drag the corner handles for scale it can flip because the values have gone into negative numbers.
Why not just scrub the scale value number?
-
I don’t have a solution, just a question and observation. Which OS are you running?
I’ve stayed with 10.6.8 on my 12 core and CS6 performance is much faster than CS5.5 – and I only have 32 GB of RAM.
I’m experimenting with 10.8 on another machine and its noticeably slower on I/O and disk operations.
-
Its not possible the way you are thinking. The alpha channel can only be read by a compositing program and does nothing for transparency when projected.
However, this may work for you:
Since the projector would projects black with your current render, why not render with a white background? Then you’d only have white light and no image in that area.
-
Do you mean
1) Rendering as in a Composition added to the Render Queue
or
2) RAM preview ?
-
If your footage is HDV its likely the format that’s causing problems in After Effects.
HDV is an MPEG2 format which means it does not contain whole frames of information and has to be transcoded before After Effects can play it back.
After Effects isn’t good at dealing with footage that needs on-the-fly transcoding.
As Dave suggested, you’re better off rendering the files out of Premiere in an AE friendly format (uncompressed, ProRes, etc) and using these in After Effects.
Premiere can deal with a variety of footage types far better than After Effects can, particularly with the Mercury Playback Engine which uses the CUDA on your Quadro card for the heavy lifting of transcoding. After Effects doesn’t use the Mercury Playback Engine.
As the inimitable Mr. LaRonde says:
Dave’s Stock Answer #1:If the footage you imported into AE is any kind of the following — footage in an HDV acquisition codec, MPEG1, MPEG2, AVCHD, mp4, mts, m2t, H.261 or H.264 — you need to convert it to a different codec.
These kinds of footage use temporal, or interframe compression. They have keyframes at regular intervals, containing complete frame information. However, the frames in between do NOT have complete information. Interframe codecs toss out duplicated information.
In order to maintain peak rendering efficiency, AE needs complete information for each and every frame. But because these kinds of footage contain only partial information, AE freaks out, resulting in a wide variety of problems.
-
[Walter Soyka] “Just a point of pedantry — Ae can use far more than 3GB per core. The 3GB per core figure in the multiprocessing preferences is the largest default minimum amount of RAM you can require Ae to allocate for itself, but if Ae needs more RAM and if more RAM is available, it can use it.
“As always Walter has the most accurate information, I would never accuse him of being a pedant. 😉
-
You may want to see this:
If you’re using CS6 see this: https://www.video2brain.com/en/lessons/global-performance-cache-and-persistent-disk-cache
After Effects can use 3GB per core. The disk cache should not be on your startup or applications drive. I’m using a 120 GB SSD dedicated to cache.
-
In my case, I’m the one paying for the software and the Production Premium Suite upgrade was less than 12 months of the Cloud.
The Cloud works well, several of my colleagues have gone that route, its really a matter of which will cost you less.
-
Add Shift to Nudge then 10 frames at a time.
-
[Philipe Karlsson] “”if i export h.264, mp4 with 2mbps / vimeo settings, i get bellow 5 mb.”
“I’m not having this issue on the retina mbp so it must be something else. I assume you are using the Render Queue and not exporting. When choosing the H.264 format I have access to the MainConcept controls.
My preference is to render a lossless, uncompressed version then compress using Adobe Media Encoder.
