Kris A. wotipka
Forum Replies Created
-
Hi Ed,
I was speaking of some of the more advanced features of H.264. It has been a while since I read through the spec but I seem to remember it being able to handle a couple of layers of content (ie. like multitrack audio but to the animation layers).
The FCP 8 or 9 comment was more to the:
“Won’t it be nice when you can have your video (as video) on one layer in H.264 and then have the graphics on another (vector) layer which would be rendered back in as vector on top of the video stream on the client’s end.” How’s that for a run on sentence.
kw
kris@wotipka.com
Image maker -
Ed,
I just finished a Flash project that was heavy on video. It was your typical Powerpoint slide grind but we didn’t want the horrible DV quality screen transfers that are often associated with type of project. We shot the video greenscreen and converted it to .flv with cuepoints for the screen changes. Now, we had to go through some pretty extreme compression (6 hours of video on a CDROM plus all of the flash content). At the end of the project, the video looked pretty great but the graphics were excellent (recreated the slides in flash). All of the video compressed well except for one gentleman who’s head didn’t seem to want to divide by 16.
So the client was happy and I am using this on a few other projects so the setup has paid for itself. However, I am like you and can’t wait to take advantage of vector in 264. Maybe in FCP 8 or 9.
kw
kris@wotipka.com
Image maker -
In theory, you could use the markers to set IN and OUT points and then render out just those segments from there. There may be a way to automate this but it is beyond my knowledge. FCP has quite a few “command line” type interface commands that do all sorts of advanced things. Unfortunately, I am not the one to ask. Wish I were.
kw
kris@wotipka.com
Image maker -
Using QT conversion, you are “converting” it to something. Do you need to convert it to something? Does it need to be resized or converted to another codec? If not, then this is not the way to do it. If you want same quality / size / codec as the timeline sequence, then just save as quicktime. You should notice your render time get way shorter if your timeline has already been rendered and you can playback the timeline without the “needs rendering” slate coming up.
kw
kris@wotipka.com
Image maker -
I was working with my my second 16:9 DVCAM project and forgot to set the capture setting to DV NTSC Anamorphic. So on playback everything was 4:3 squeeze. I figured out that you can check the anamorphic setting in the bin and it changes the attribute of the clip so that when it plays in the viewer, it is 16:9. I doubt that this sets the anamorphic marker in the original QT clip but it works inside FCP.
Just my 2 cents. Hope it helps.
kw
kris@wotipka.com
Image maker -
I have gotten QT video with six individual audio tracks so I know it is possible. They would have to set it up correctly on their end before they make the copy for you.
kw
kris@wotipka.com
Image maker -
Try creating a new sequence. File>New>Sequence I believe. Saying that these two items are missing, sounds like a missing timeline to me.
kw
kris@wotipka.com
Image maker -
I am afraid you will have to explain your response a bit more. I am not understanding your post.
kris@wotipka.com
Image maker -
Also from the FCP 6.0.2 Release notes:
“Gamma Import Option Has Been Renamed
In Final Cut Pro 6.0.2, the Imported Still/Video Gamma option in the Editing tab of the User Preferences window has been renamed Imported Still/RGB Video Gamma.”
There are 4 options for this setting:
Source
1.80
2.20
2.22
CustomCould it be that this will overwrite the gamma flag and force FCP to use the gamma of choice? This is strictly speculative that it is doing the RGB>YUV calculation and FCP is just reading the gamma wrong. If there is an encoding error, I doubt that this will have the affect desired.
kw
kris@wotipka.com
Image maker -
DISCLAIMER: I do not have AE. I am working on this issue for a friend of mine. I am very familiar with the whole YUV<>RGB issue. I came across this and figure I would pass it on to this group in the hopes of helping find a solution. Please do complain if it doesn’t work.
https://kb.adobe.com/selfservice/viewContent.do?externalId=kb402801
From the website:
In order to provide consistency between platforms, After Effects CS3 adds a metadata tag to exported QuickTime movie files that specifies what gamma adjustment to use. When this tag is present, QuickTime Player uses that value instead of what it normally would use for that codec, and the resulting adjustment is consistent between Mac OS and Windows.
The value that After Effects CS3 uses for this tag is always 2.2. This value is correct for most YUV codecs such as DV and v210. However, for RGB codecs, 2.2 is not often the correct value. This means that files that use RGB codecs (such as Animation or None) are over-corrected and look washed out or too light.
kris@wotipka.com
Image maker