Forum Replies Created

  • Alegator

    August 30, 2006 at 11:38 pm in reply to: How can I do this in Premiere?

    Craig, I just tested your suggested method and it’s great, it does render all 16 clips in a single click. Unfortunately the few last clips still show A/V Synch issues. I will try doing the same with other software that I tested and that do not create a A/V Synch issue when rendering (I tested Ulead Media Studio Pro and VirtualDub)

  • Alegator

    August 30, 2006 at 10:10 pm in reply to: How can I do this in Premiere?

    Another way would be to batch export subclips to movies, is this possible in Premiere? Final Cut Pro has the batch export for clip rendering.

  • Alegator

    August 30, 2006 at 4:04 am in reply to: How can I do this in Premiere?

    then use Project Manger to convert them to “unique” avis
    Could you detail the steps to do this? Thanks!

  • Just an update. I experimented rendering the subclip with Premiere using a different method and it worked fine, the rendered movie has NO A/V synch issues. This is how I did it: instead of generating subclips I double clicked the captured file making it appear in the source monitor. I marked the in and out points for a given clip and instead of generating a subclip I dragged directly the marked clip in the source monitor onto the timeline sequence. I then went to FILE/EXPORT MOVIE. It seems that generating subclips in the asset window slows Premiere and creates this issue in rendering.

  • Hi, I did all of the following:
    1) The A/V synch problem is independent of the player used, I viewed the rendered movie in the monitor window within Premiere, in Windows Media Player, Nero Showtime, Cyberlink PowerDVD, etc…they all show A/V synch problem. (Audio comes out form the PC speakers using internal sound card).
    2) I rendered the same subclip with other video editing software (using the Premiere captured file as source) and there is NO A/V synch problem in the rendered file (I tried Windows Movie Maker and Ulead Video Studio 10 Plus).
    So the problem arises in the Premiere rendering process. I have no idea why Premiere is generating this problem. I’m starting to think that it might be hardware related?? I’m using a P4 3.06GhzHT, 2Gb RDRAM, 2 internal hard drives (7200rpm, 320Gb each), ATI X800XT AIW AGP, Voyetra Santa Cruz Sound Card.

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