Steve Roberts
Forum Replies Created
-
Never heard of it, but the “mpg” is a clue. AE won’t like it. You need to use VLC player (or whatever can open the file) and convert to a Quicktime movie, to Animation codec or Photo-JPEG.
Or you could search for “mpgv” “quicktime” “download” to see if there’s a codec. You may need Quicktime’s MPEG-2 components — check the Apple site.
But do convert before importing into AE.
-
Second that.
-
If you’re really stuck try opening it in a dumb word processor like Notepad. Search for “Apple Video Media Handler”. You may find the codec (e.g. “HHH.264” ) eventually appearing sometime after that text string.
I’d paste the code into this post, but the COW couldn’t show it.
-
(“Lossless” is irrelevant — it’s not the codec. Don’t need to know that, but thanks. )
Import the video in question (the one that comes in as 1 FPS) into AE and see what codec the file is. It should show when you select the file in the Project window. Is it Animation or something else?
In Quicktime, open the movie in question, then select File>export, the select “movie to Quicktime movie”, and click on “options”. In the dialog, select Animation, current frame rate, best quality, under “size” select “current”. Hit OK and Save.
Import that into AE and tell us what codec AE thinks it is.
-
What is the codec of the footage after capture?
Can you use Quicktime to export to something like Animation or Photo-JPEG codec? -
Regarding compression when rendering out of AE, you can a) compress to the codec of your FCP sequence, or b) compress to the Animation codec (negligible compression), then compress to your FCP sequence codec with Quicktime Pro. This is what I do with DVCPRO HD. Your mileage may vary.
Regarding gamma issues between the two apps due to the RGB vs. YUV processing, search the COW for “gamma”, FCP, “final cut Pro”, that sort of thing.
It will never be exactly the same. You just don’t want to see any differences. I’d import the FCP footage into AE from cut to cut, so any slight difference between AE and non-AE footage is covered by the cut when brought back into FCP. If, however, you have a long take with one short AE effect in the middle (such as a Star Trek transporter effect, I’d consider importing the clip into AE with handles on it so you can dissolve on either end of the AE footage to smooth out any tiny mismatch, possibly masking around the affected area.
That’s my experience. Others may have a better solution.
-
Steve Roberts
January 28, 2010 at 12:37 am in reply to: C4D, no reflection from lights on my objectsIsn’t there a C4D forum?
-
Steve Roberts
January 27, 2010 at 11:55 pm in reply to: how to scale/zoom into an image till one pixel equals videosizeHow about duping the layer, setting the upper one to draft, and animating its opacity from 0 to 100 as you zoom in?
-
Remove Grain works by analyzing the noise on a frame of your choosing, then effectively applying an opposite algorithm to your footage. It’s very effective, and was optimized for both film grain and video noise.
(You should enable temporal filtering for best results. Hey Todd K, could you ask the tech boys to enable it by default?)
Yes, if you’re talking about compression artifacts, such as MPEG-2, there should be no guarantees, since the amount of artifacts is likely to vary widely from frame to frame. No, Remove Grain is best when dealing with noise acquired during initial image acquisition. In my opinion.
(As I’ve written before, I used to give demos for the developers.)