Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro AVCHD playback very choppy in PP CS5

  • AVCHD playback very choppy in PP CS5

    Posted by Tony Connoly on December 28, 2010 at 12:36 pm

    The same file, when played in Windows Media Player, is not choppy at all and looks very good.

    However, when played in the Source Monitor or from the timeline, is very choppy and full of artifacts. I haven’t even started adding effects.

    The file is 720p/30fps from a Pansonic GF1.

    Is this a codec issue or a system performance issue? I have a 7200rpm drive, 8 GB, and 2.66Ghz quadcore.

    If a performance issue, why does Windows Media Player handle it well? Media Player even managed to play it fine on a netbook computer.

    Thanks for your help.

    Tony Connoly replied 15 years, 7 months ago 3 Members · 4 Replies
  • 4 Replies
  • Jeff Pulera

    December 28, 2010 at 3:21 pm

    Right-click in the CS5 Program Monitor and look at Playback Resolution – it is set to HALF by default, but most users get better results at FULL setting for playback. Goes contrary to thinking, it would seem easier to play half quality, but I guess not!

    Do you have hardware Mercury Playback enabled using an nVidia display card? This is a must for decent performance with AVCHD footage in CS5.

    Also, be sure to use a dedicated video drive, not the C: drive for capture/playback.

    Jeff Pulera
    Safe Harbor Computers

  • Todd Kopriva

    December 28, 2010 at 6:43 pm

    Have you installed the Premiere Pro CS5 (5.0.3) update? The recent updates fix a lot of problems and include many performance improvements.

    ———————————————————————————————————
    Todd Kopriva, Adobe Systems Incorporated
    Technical Support for professional video software
    After Effects Help & Support
    Premiere Pro Help & Support
    ———————————————————————————————————

  • Tony Connoly

    December 29, 2010 at 2:11 am

    Brilliant! That seems to have fixed what now seems like a bug. Thank you.

  • Tony Connoly

    December 29, 2010 at 2:13 am

    I meant that setting the playback resolution to full rather than half fixed it. I was already running 5.0.3. Thank you both.

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