Forum Replies Created

Page 1 of 2
  • Dipalma

    May 15, 2007 at 7:57 pm in reply to: Alias issues …

    The page turn is a “wipe on” transition revealing a fullscreen comp. After the transition is complete, a “blueprint” style graphic “draws” on, but the width of the lines are wide enough and blurred only slightly. Honestly, I think it just moves too fast and too far acros the screen for AVID to deal with it.

    I could send them a fulscreen movie without the alpha and let them create the transition. Or send them the file as a matte and fill.

    Nic

  • Dipalma

    May 15, 2007 at 7:38 pm in reply to: Alias issues …

    Actually, that was referencing a different project … sorry. But the problem occurs AFTER the page turn transition with the alpha channel. The alpha channel has nothing to do with these issues. But your enthusiasm in possibly finding the solution, similar to Columbus finding land, was priceless … sorry to burst your bubble gum.

    Nic

  • Dipalma

    May 15, 2007 at 7:18 pm in reply to: Alias issues …

    I have done the search, but nothing seems out of the scope of what I am already doing. I might try to send them a test with field rendering turned off.

    Nic

  • Dipalma

    May 15, 2007 at 7:16 pm in reply to: Alias issues …

    I have preset render and output modules as AVID MCA. My instructions to the editor are to import into AVID as 601 pixel aspect ratio, NTSC 2:1 Interlaced (lower field first), invert existing alpha, and RGB levels (0-255). My comps and templates are set up for these import settings.

    I have been doing it this way ever since the gang in Tewksbury, Mass switched to a Meridien system. Am I doing something wrong?

    Nic

  • Dipalma

    May 15, 2007 at 5:22 pm in reply to: Alias issues …

    Very true … 99% of the NLEs that I import to are lower field first. In working with video footage, in my project window, I interpret footage based on where the footage originated.

    However, that does not apply to Photoshop layers. There is no logical need to interpret Photoshop layers.

    Thanks for your help, though. Effects blurs seem to be my only option.

    Nic

  • Dipalma

    May 15, 2007 at 4:42 pm in reply to: Alias issues …

    I can see it ever so slightly in the comp window but that’s because my screens are showing a progressive scan. It’s very noticeable after it renders and gets imported into an AVID or FCP (with DVC Pro 50 codec, lower field first). Now, of course, the Quicktime move it renders is going to look ugly because of the the field render. But once it’s imported, it should look pretty good.

    The layer itself is a very “cartoony” hilltop with a gradual curve against a soft gradient sky. The movement of the hill, rising from the bottom into the composion, is where it is most pronounced. And motion blur is not an option if rendering to an NLE separating fields.

    Is it me, or has AE 7 completely negated the field dominance of today’s digital NLEs? Perhaps I should render everything as an Animation Quicktime with field rendering off … and then leap out my office window … I’m only on the first floor …

    Nic

  • Dipalma

    May 15, 2007 at 4:13 pm in reply to: Alias issues …

    Yeah … I have been through all my render templates, preview preferences, comp settings … even my ATI Display settings … and shunned OpenGL like an adultress in church. To no avail.

    Nic

  • Dipalma

    December 8, 2006 at 6:40 pm in reply to: Particle Systems plug-in issue in AE …

    And I dig this idea, but having a problem getting the stars to emit randomly throughout the frame. They will be sparkling around a logo … fading iin and out randomly. PP is a tough one.

    Thanks!

    Nic

  • Dipalma

    December 8, 2006 at 6:22 pm in reply to: Particle Systems plug-in issue in AE …

    Nic would like Spaceman to share some of his spacejuice …

    Thanks for the advice … from everyone!

  • Dipalma

    December 8, 2006 at 5:14 pm in reply to: Particle Systems plug-in issue in AE …

    No change. Again, I think this is a color/transparency issue. Not to mention, purple is an unforgiving color in NTSC.

Page 1 of 2

We use anonymous cookies to give you the best experience we can.
Our Privacy policy | GDPR Policy