Adolfo Rozenfeld
Forum Replies Created
-
the i7 range of processors is currently not supported, and there are known issues with the multiprocessing feature in a computer that has such processor(s).
A bug fix update will add support for these processors.
You may want to turn off multiprocessing until that update is released.Adolfo Rozenfeld · Adobe
-
You know? There’s a text preference for high-quality PAR correction.
It’s called “Viewer Odd Zoom Quality” in the preferences file.
It’s not officially supported, so if it affects performance negatively for you, turn it off again.
Adolfo Rozenfeld · Adobe
-
Leaving 1 GB of RAM free for other applications may be a little optimistic when you have 4 GB. Remember it’s recommended to have about 2 GB per core, so you may want to lower the amount you leave free for other apps.
Adolfo Rozenfeld · Adobe
-
Danny: to avoid the error you’re getting, after picking your distribution format, you usually want to pick a preset for that format which has “same as source” as part of the name. Otherwise, there will be a conflict between the Comp/Render Queue pixel dimensions, and the size specified by AME. Please note that when you select a preset which is not “same as source”, AME will instruct you in a comment field to change the size specified in AE’s Output Module.
Note that in some cases, even if you pick “same as source” you may still get this error if the format you’re going to only accepts specific sizes. For example, if you chose MPEG-2 for NTSC DVD (not your case), only 720×480 would be acceptable.
Adolfo Rozenfeld · Adobe
-
Danny, Dave:
When in the After Effects Render Queue you specify a format that’s typically used for distribution (H264, MPEG-2, Flash video), the Adobe Media Encoder dialog appears when you invoke the Output Module’s format options.
As Dave said, because of the way After Effects works, AME can’t do multipass encoding (note that for some formats this produces critical quality advantages; for others, not so much). But it’s true that as of today, exporting to distribution formats in AE is more about convenience than having the ultimate quality option.However, starting from CS4, the Adobe Media Encoder also exists as a standalone application.
If you have Production Premium or Master Collection (ie, if you didn’t buy After Effects as an individual product), you can avoid rendering an intermediate, uncompressed file for encoding later. Instead, you can open the After Effects Composition directly in Adobe Media Encoder, and encode using 2-pass VBR encoding. As a source for encdoing, of course, the “raw” After Effects Comp is the same or higher quality than an uncompressed file.
If you did buy After Effects as an individual product, you can still render an uncompressed or slightly compressed file, and use that as a source for encoding in AME.
As for H264 (even MPEG-2) being correct if you’re not “too picky”…
I agree with you if this was about using them as acquisition formats, but distribution is that they were made for.
Given enough data rate (say, 25-30 Mbps) H264 should look gorgeous. It’s what you see in a Blu-Ray disc. At such data rates, 2-pass MPEG-2 also looks better than it has any right to. And it’s less demanding on CPU muscle than H264. Playing full HD H264 video requires a powerful computer.An uncompressed HD file can be about 100-120 MEGABYTES a second. It would require special hard drives, or a stripe set to play back correctly.
Adolfo Rozenfeld · Adobe
-
This applies to CS4 mostly.
CS3 introduced this kind of multiprocessing, but didn’t expose a direct way to specify the number of cores/processors to leave free. So, if you didn’t have enough memory to use all of them, it would just shut down.Adolfo Rozenfeld · Adobe
-
I think in that case, yes, the solution you came up with would work just as well as other possible solutions.
Dave’s solution is an entirely different route. No better or worse. I guess it would take more or less the same time to set up, so it’s up to you.
Adolfo Rozenfeld · Adobe
-
I wouldn’t recommend using 4 cores with 4GB of RAM. The background processes used for multiprocessing will starve.
With just 4 GB of RAM, I would set Multiprocessing to leave 6 CPUs free, and use the remaining 2 cores. And you definitely want more RAM. As Kevin said, at least 2 GB per core. So, while 16 GB of RAM would be recommended for an octo-core, you could get for example an extra 4 GB an use 4 cores.Adolfo Rozenfeld · Adobe
-
If I understand correctly, you want the first line revealed, stop for a while, then reveal the second and third, stop for a while, etc?
If so, you only need one animator with one range selector (set to lines and index) and you only need to animate “start” in the range. When you want it to stop, copy the last keyframe and paste it two or three seconds later, then resume the animation (using hold keyframes wouldn’t work because you would get jumps in the values).
You don’t need to animate the opacity. The animator/selector system is deisgned so that as characters (or words or lines) go from a selected state to deselected, the animator properties’ values (like opacity, or position, or fill saturation, etc) react according to the intensity of the selection. So, if you just set Animator Opacity to 0, the lines will all have zero opacity when they start, but will become opaque as the start of the range goes from line 1 to line 2, etc. When the selector starts in line 6 and ends in line 6, no line is selected, so no line has an opacity of zero.
Adolfo Rozenfeld · Adobe
-
Anything that could be useful to you would make a good feature request, especially if you explain why is it important to you.
I intend to write an article on the amazing cool possibilities that are hidden in the text engine. But first I have to work on the space where such an article would appear 🙂
Adolfo Rozenfeld · Adobe