Creative Communities of the World Forums

The peer to peer support community for media production professionals.

Activity Forums Adobe Premiere Pro fields/compression..?????

  • fields/compression..?????

    Posted by Stuart Ireson on March 20, 2008 at 6:59 pm

    Hey all!

    I’m very new to Premiere (only version 6 unfortunately) and Im very pleased with what ive done on it… However, there are a few concepts that I still fail to understand…

    Fields/Deinterlacing….

    I’m still very confused. Are the little corrugated lines on the edges (of moving things particularly) supposed to be there at all, or just a little… ? It alllooks great in the timeline monitor of course. But in exporting most of my footage has a small amount of comb-like lines on moving edges, but some of my footage has quite bad lines – when exported. But am i right in thinking that this may be because I am looking at them on a progressive scan computer monitor and that they may in fact be ok on a video monitor/tv… which i cant try right now? Arghh.. so confusing.

    And the help section in premiere is not very helpful.It was shot on DV – a PD-170 so I’m assuming lower field first should be the correct setting/

    Codecs… Yeah I can get a quite satisfactory AVI with the DixX compressor but how universally accepted is this codec…?If I make copies will others have problems if they dont have this codec? Which are the most universal codecs? Though all the others seem to provide muchless quality.

    Thanks for ny light you may be ableto shed..!

    Stoo

    Vincent Rosati replied 18 years, 1 month ago 2 Members · 1 Reply
  • 1 Reply
  • Vincent Rosati

    March 21, 2008 at 8:05 pm

    The ‘corrugated’ lines in frames that have motion is interlacing. The length of the lines relates to the amount of motion.
    When editing interlaced video on a computer monitor, each ‘frame’ you see is actually two separate ‘fields’ being displayed at the same time.
    NTSC is described as 29.97 Frames Per Second, however if the video is interlaced it is more accurate to say that it is 59.94 Fields Per Second, or 60i.

    If you are shooting interlaced, and your goal is to produce a DVD you should edit and encode as interlaced, as DVD players deinterlace when necessary. This even includes desktop DVD players such as PowerDVD or InterVideo WinDVD Player.

    Deinterlacing is a destructive operation, but you can achieve desirable results when done carefully.

    If you are editing for streaming or desktop display, you should deinterlace.

    Potentially, there are a bunch of problems you could be seeing on your display. Video production is complicated. It’s not easy to make it acceptable. It’s even more difficult to make it nice.

    Chances are, if you are in an NTSC region than your video is Lower Field First. I tell every editor to get a free copy of GSpot…
    https://www.headbands.com/gspot/
    You can open your video files with it to see what the field order is.

    Your Premiere project specs should match your desired output. And, your source files should match your project specs.

    As far as DivX, it looks great, but there are a lot of DivX videos floating around that are poorly encoded, which has left a sour taste in my mouth.
    Yes, if a viewer doesn’t have the correct codec, they will have playback issues.
    MPEG1 is very common, but doesn’t look that great.
    MPEG2 looks great, but has playback issues.
    Real looks great, but many people don’t have Real or Real Alternative.
    MP4 looks great, but there are playback issues.
    WMV looks great and is very common, this is what I would choose for a delivery format.
    FLV is also available, it will play in Flash enable browsers, but requires an uncommon standalone player to play from the desktop.

    As you know, editing and encoding are two different things. Make notes and save presets as you test your bitrate settings so you’ll know how to encode a good looking video with whichever codec you choose.

    Vince

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