Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Exporting FLV crashes

  • Exporting FLV crashes

    Posted by Matt Davy on July 28, 2009 at 11:54 am

    I have a 500mb avi file that I need to encode into an FLV file.
    I brought it into premiere pro cs3, placed on the timeline and then used the Media Encoder to create an FLV. I used the settings of original resolution (950×640) bitrate of 2000kb/ps. There is no audio with this clip.

    When I export it using these settings it goes fine until about the 20% mark. Then it slows down until at around 26% the percentage is no longer visibly incrementing. It will occasionally jump maybe one or two percent.

    I continue doing other processes and premiere pro will eventually become unresponsive, it will not maximise anymore and in the end I am forced to End the Process using Task manager.

    The clip is only 14 seconds long and has been created in 3ds Max.

    I have 110Gb free on my C: drive and over 300Gb free on my E: drive (where it is exporting to)

    I eventually gave up and used the Adobe Flash Video Encoder using exactly the same settings. It took about 20 seconds and the output FLV is fine.

    What I want to know is why premiere cannot handle this? I have used the media encoder countless times with no problems, although it has always seemed slow… I have changed my Media Cache to be on my E: drive as this always has lots of space just in case, as I read disk space can be an issue.

    Please, any ideas?

    I can’t really sit and watch it export all the way through as I have countless other things to do at the moment.

    Cheers,

    Matt.

    Matt Davy replied 16 years, 9 months ago 1 Member · 1 Reply
  • 1 Reply
  • Matt Davy

    July 31, 2009 at 8:59 am

    I am still having this problem, it only seems to occur when trying to encode video exported from 3ds max in uncompressed avi format. I have managed to get around it by using Targa sequence’s instead. I am still a little puzzled, as it can’t be the file size as I’ve worked with much much bigger files before with no issues.

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