Steve Roberts
Forum Replies Created
-
Have task manager open, and see if you’re maxing out your RAM. If so, go into the secret prefs: hold down shift when accessing the prefs — release the shift key only when the dialog box shows up. Try setting it to purge every 5 frames during make Movie.
Or … the movie is too big for the drive? Try the Animation codec or freeing drive space.
Or … is there something special happening at the freeze point? An effect?
Try rendering to TGA sequence, then bringing that in again and compressing to QT. If you crash during a TGA render, you can always pick it up where it left off.
BTW, why “none”? You should probably use Animation instead anyway. And you should be using Make Movie, not File>export, right?
-
Here’s one way that works best with a moving camera or moving rigging:
Duplicate the footage, placing the duped footage layer over the original footage layer. Select the dupe, and apply a two-point open mask over each wire. Once you’ve masked all the wires, apply the render>stroke effect, set to “all masks”, and set the stroke to “reveal original” (I think that’s the wording). You might need to animate the masks (mask shape parameter) to follow the wires as they move through the frame.
Now here’s the trick: slide the duped layer one or two frames in time. The strokes will then reveal the parts of the duped footage layer where the wire isn’t there yet, or has already passed by (depending on which way you slide the footage). These clean bits will cover up the wires in the original footage layer below.
Give it a go,
Steve -
Maybe you should reinterpret the clips, setting them to loop?
File>interpret footage>main.
Steve
-
American keyboards have no “eh” key. 🙂
Steve
(Fellow Canucklehead) -
Check out the Final Cut Pro forum. You might need the special FCP intermediate codec for working in HDV.
But for what it’s worth, HDV should be converted to something else such as Animation or Photo-JPEG as soon as it’s captured. It’s a lousy codec for editing and compositing — it’s an acquisition codec. You might need to have this conversion done on the FCP 5 machine.
Steve
-
Search the COW posts on “KCHR”.
Steve
-
Beyond Adobe’s recommendations, no books or authors follow the exam. This may be true since those who wrote the exam signed an NDA, so Adobe is in control of any supplemental materials, which, beyond the Classromm in a Book and the manual, do not exist, unless Adobe has put something new out.
Study the manual and the recommendations on the exam site, I say.
Steve
-
Not likely, in my opinion. 8-bit can cause banding. To picture that, imagine the difference between a smooth rainbow and one separated into 8 stripes. The 8-stripe one would suffer from an extreme case of banding.
Do you have a field-rendered source clip that has been scaled up or down? If so, you need to reinterpret the file (file>interpret footage>main) and separate the fields. DV NTSC uses lower field first, by the way.
If the source came with those lines, it may have been scaled before it got to you — in that case, you’d be, er, hosed.
Got a still?
Steve
-
There’s no advantage in that.
By “unsupported”, AE means that the feature will be rasterized in an SWF file. It will appear as it does in the comp window, but the resulting SWF will be a huge animated JPEG movie, not a small vector movie.
So creating a quicktime movie, then exporting that as SWF will probably get you the exact same big rasterized SWF file. To reiterate, it will look fine, but be a really big SWF. How big? Do a test.
If you don’t mind big SWFs, go ahead. Otherwise, if you really want 3D in a nice small vector SWF, I recommend starting with Swift3D, not AE. AE rasterizes just about everything, since it was designed as a video app, not a Flash app.
Anybody else?
Steve
-
It’s aspect ratio, not aspec ration. 🙂
Steve