Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Pro1.5’s mediancoder exports QT to wrong drive!

  • Pro1.5’s mediancoder exports QT to wrong drive!

    Posted by Loucar on January 21, 2006 at 5:25 pm

    A puzzling phenomenon happens when I try and export a QT file using media encoder in Pro1.5. I set the destination to my export drive but when the encoding is finished I find that the .mov file in my export drive is only 1kb and instead there is a file with the name of the encoding preset (i.e. QuickTime 512k streaming PAL) in my system drive!?

    I’ve recently upgraded to PPro1.5 so I tried re-installing QT7 to see if that fixed the problem but no joy.

    Any ideas as to why this might be happening?

    Loucar replied 20 years, 3 months ago 3 Members · 3 Replies
  • 3 Replies
  • Dominic Osborne

    January 21, 2006 at 6:26 pm

    I’ve always had a phenomenon with QT exports from Permiere Pro 1-1.5 compared to Premiere 6.5 and below.

    For me, the files never seem to follow the data rates I give them, no matter how I create the files, so when I try to craete streaming QTs for example, they come out at stupid sizes like 80MB as opposed to any other web format I can make of an identical clip.

    Dominic Osborne
    —————
    Director & Head of Visuals
    Eight Eyed Sea Bass Ltd
    http://www.eighteyedseabass.com

  • Steven L. gotz

    January 21, 2006 at 8:21 pm

    What settings are you using in the Adobe Media Encoder. List all of them. It will probably become readily apparent that you are asking for something different than you really want.

    As for file size, that is a matter of the settings as well. But be aware that the Sorenson 3 codec in Premiere Pro is not the Sorenson 3 Pro codec that is WAY better. Get Sorenson Squeeze if you are going to export to Quicktime on a regular basis.

    Steven
    http://www.stevengotz.com

  • Loucar

    January 22, 2006 at 12:17 pm

    Sorry, you’re right, it was a matter of checking the settings when exporting alternate QTs in one go.

    I was thrown off the scent because this in turn affected even the single export of a QT (where you only have one option of saving the file in its destination) which took a reboot to resolve.

    Thanks for the help.

    Louis

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