Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Animating stills

  • Animating stills

    Posted by Mark Hollis on September 4, 2009 at 4:31 pm

    I do a weekly show using Adobe Premiere Pro version 1.5. Old computer, long-running show and we’ll upgrade come January (but not before).

    I have to regularly animate documents into the screen. I have come up with several nice moves that use the Motion tab in conjunction with Simple 3D. Production is standard NTSC.

    Often, when I check these animations on a monitor, I get unacceptable jitter in the image as it’s moving. Then, when it stops, it’s fine. I can add rotation and it’ll not jitter.

    I have used the Interlace option in Adobe’s Photoshop to try to take out this jitter. This sometimes works, sometimes does not. Apparently Premiere does not have a “motion blur” effect that will take the onus off the motion.

    Has anyone had this problem and can anyone point to a recepie that will allow me to use Premiere (or that and Photoshop) to take out this motion jitter as I am animating a document into the picture over a background.

    The document is usually an 8.5″x11″ 72 Pixel-Per-Inch document.

    What if there were no hypothetical questions?

    Mark Hollis replied 16 years, 7 months ago 2 Members · 4 Replies
  • 4 Replies
  • Chris Buttacoli

    September 6, 2009 at 11:06 pm

    When you say jitter, I think of the image jumping around slightly during moves. Is that what you mean, or are you talking about interlace flicker, where the fine detils of the image move in and out of the scan lines?

    I know adding a slight directional blur of one pixel or so can help flicker, I wonder if it can do the same with jitter?

  • Mark Hollis

    September 8, 2009 at 1:04 pm

    This is not that kind of jitter.

    It’s about ten lines of the image as it comes in — but interlaced, so you don’t see every other line. This does not show up in computer monitors, as the output of these monitors is frame-based and not field based. The movement is not so fast as to suggest that this is simply an interlace artifact.

    This is clearly an animation artifact. And I can do the exact same animation elsewhere and I don’t have this problem.

    I have been wondering if this is an issue with starting the animation on an odd frame versus an even frame. I haven’t had to worry about something like that since the early 1990s!

    What if there were no hypothetical questions?

  • Chris Buttacoli

    September 10, 2009 at 1:22 am

    Is turning fields off on just those animation clips out of the question?

    If you do upgrade, I highly reccomend also using After Effects. These moves are SO much easier to control in AE, you will never try in an editing app again. Plus AE has motion blur and 3d lighting to cast realistic shadows. And now with the dynamic link setup, you never need to exit Premiere. The the final results will outweigh the small learning curve.

  • Mark Hollis

    September 10, 2009 at 2:53 pm

    I am doing these compositions in After Effects. And an upgrade is just not possible. The computer we’re using is really pokey by today’s standards and just cannot run CS4.

    I am learning AE as it will be part of my workflow to come. I acquired this (very good) job after working for a number of years on the Avid DS, which can be seen as a combination editor and compositor, so I do understand compositing.

    I also know that AE and Premiere CS3 (and forward) are wonderfully integrated so that, within Premiere, you can simply click on an AE composition and edit or change it within AE without stopping. The current workflow with AE 6.5 and Premiere Pro 1.5 are not well integrated.

    We’ll probably go to FCS in January, but I intend to keep AE in the mix, as FCS is not a compositing application.

    I have successfully animated the still image of documents in AE. They seem to be all right and that will probably be my workflow henceforth. There seems to be no solution for this issue from within Premiere.

    What if there were no hypothetical questions?

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