Bret Williams
Forum Replies Created
-
Boring? That’s mature.
-
It should be interpreted as lower field first since it is lower field first DV footage. Then you should render it as such as well. Not doing so will create a stuttery fake progressive scan look you don’t want.
Perhaps you’re just not rendering right in AE. Best quality, full, 720×480, lower field first, non-square pixels, 29.97 etc. Make sure your comp is ntsc DV comp of same above.
There should be absolutely no need to worry about the even or odd or inbetween numbers in AE, but it can’ t hurt.
-
Ok, bad advice. You’re now creating a project that IS dependant on footage that you might delete. Render files are included. Render files come and go. Almost nobody gives the advice to NOT check the make self contained. Advice on this board is almost universally to make movie self contained and NOT recompress. There is no extra compression cycle. Simply put, the bits and bytes are simply copied into a new file, and only the bits and bytes needed are copied into the new file for use in AE. Making a dependant clip by not checking this box could mean you have to leave a 1 hour clip on your drive just because a 10 second portion is referencing it. There’s a place for reference movies, but for me it’s usually for exporting a 1 or 2 hour long clip for DVD compression or something like that.
-
Then what was the HD that FCP 4.5 HD was designed for?
-
Sounds like you’re probably shooting at 32khz. Use that easy setup instead.
-
If you created 70 pages and none of them are linked to a DW template then you have a problem. Your best bet is a find and replace. Assuming all pages were similar, and created by doing a save as or duplicate method this will probably work. Open a page and add the table cell and swf, etc. Then, open an unchanged page and compare the two in code view. You need to determine the section that changed and the section that you’ve added. For example if you split a cell, you’ll find the code for that cell (you can highligt it in design, then switch to code view) before it was split. This is what you will search for. Then, in the new page, determine what has changed. In the example given you’d highlight the two cells and switch to code view and copy. This would be the replacement for the search.
Check a couple individual pages before you do a sitewide search and replace. But it should get the job done if the pages were created in some consistent manner.
-
Did you open the file in something after you exported it? That’s usually the case. Like QT still has it’s hooks in it. And if you opened it in FCP it’s definitely in the 10 previous clips pull down in the viewer, so that’s why FCP has it’s hooks in in possibly.
-
Bret Williams
October 14, 2006 at 1:37 am in reply to: Trying to bring 720×540 square pixel QT into 720×486 nonsquare sequence?Yeah, they rendered an inverted alpha I bet. But I would probably have used AE to render it to your seq codec. It does a better job scaling, and it would only need the one render step. It would only take AE a few seconds to do it.
-
True in FCP because it’s sub pixel rendering pretty much sucks. I’ve never even thought about it in AE and I’ve never noticed soft footage.
-
Bret Williams
October 13, 2006 at 10:57 pm in reply to: Trying to bring 720×540 square pixel QT into 720×486 nonsquare sequence?Not sure why you’re not seeing it (probably an alpha channel issue) but you should render it at 720×486 in AE. Why would you render it at 720×540? I realize that is square, but AE takes care of mixing all the square and non-square issues. You should always work in AE at the native format you’re creating for for best results. If you must work in 720×540 (still don’t know why) then your last step should be to place that comp into a 720×486 comp before rendering. Avoids field mush if you’re using fields. If you’re not using fields, wouldn’t you want AE to do the scaling instead of FCP? FCP isn’t exactly known for scaling and subpixel rendering quality. Ugly.