Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro Typical worflow?

  • Typical worflow?

    Posted by Evrard Blom on June 6, 2006 at 10:40 am

    Hello,

    I now know from previous post that my worflow is a real nightmare thats why rendering takes so long (i waited 2 full days to get a 1h41 AVI).

    What i usually do is rent a camera, shoot, transfer everything to hard-drive as AVI, do the cuts, all the edits, SFX, Video FX, etc, render all to AVI (for archive) and burn DVDs for distribution.

    Now can anyone suggest me (in A,B,C,D) what their worflow would be to do the same?

    In fact iam biochemist, just came to the multimedia field as a hobby first then trying to be serious lol, not very used with advanced technics, video formats differences, etc.

    Thank you for your helps

    Mbelli replied 19 years, 11 months ago 3 Members · 7 Replies
  • 7 Replies
  • Steven L. gotz

    June 6, 2006 at 1:24 pm

    It sounds like you are doing it in a fairly normal and reasonable fashion. The reason for the long render is probably the effects you are applying to the footage. Auto levels and color correction is pretty tough on a PC.

    If you rendered a little bit at a time, overnight, during meals, while taking breaks, you could accomplish a lot more. Instead of the entire hour plus, just render a minute here and a minute there as you are doing your editing. If the entire project is rendered, the export to a DV AVI will be quite fast.

    And if you use that DV AVI to export (transcode) to DVD or MPEG2-DVD, it will go pretty fast as well. If you use the original footage to create the DVD, it will take a very long time as well.

    Steven
    https://www.stevengotz.com

  • Evrard Blom

    June 6, 2006 at 1:51 pm

    Very Interesting. Never thought i could render small pieces at a time. That comes to
    pre-render one sequence at a time, here and there right?

  • Steven L. gotz

    June 6, 2006 at 2:09 pm

    Let’s define “render”. That is when you create preview files, not when you export a file.

    You can move and resize the workarea bar to just render the area under it (by pressing the Enter key).

    So you could set it to be one minute in duration, so that each time you render, you move it ahead and render the next minute.

    Steven
    https://www.stevengotz.com

  • Evrard Blom

    June 6, 2006 at 4:03 pm

    Great Steven, just one more question if you don’t mind: just to know how the things work, how can doing this procedure help accelerate the eventual final rendering of the movie to file?

    Thank you

  • Steven L. gotz

    June 6, 2006 at 4:47 pm

    Simply this…. Premiere Pro will use the preview files that you created to see the clips in real time when it creates a DV AVI file. After all, the preview files are nothing more than DV AVI files, so it is a simple job for Premiere Pro to read them and create the final output.

    The program does not use the preview files while exporting to DVD however.

    Feel free to check out the preview files using a media player. You’ll see what I mean. Start a new project, put a short clip on the timeline. Add a slight blur. Render. You will see that when you play the newly created preview file in another application, it is basically the clip plus the effects.

    Then do this. Export the file to a DV AVI. Time it. Now, delete the preview file and export again. Without the preview file it will take longer to export.

    Steven
    https://www.stevengotz.com

  • Evrard Blom

    June 6, 2006 at 11:22 pm

    Thanks a lot Steven, i really have learned many new things in this serie of discussions.

  • Mbelli

    June 7, 2006 at 12:57 am

    Remember also that fast drives in a RAID and a fast dual core PC makes a big difference in rendering and encoding speed. A couple of days to render even a 2-hour AVI seems like a lot to me. Maybe it’s time to upgrade your computer and drives.

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