Is this Interlacing? Pictures included.

You need to provide more information

Source specs, project/sequence settings, export render settings, etc

Do the artifacts occur throughout the clip every frame or regular intervals?
 
The artifacts happen throughout the clip. Source was 60i.

Here are the properties for the clip

File Path: J:\pp\**************
Type: AVI Movie
File Size: 303.5 MB
Image Size: 720 x 480
Pixel Depth: 32
Frame Rate: 29.97
Source Audio Format: 48000 Hz - 16 bit - Stereo
Project Audio Format: 48000 Hz - 32 bit floating point - Stereo
Total Duration: 00:01:23:26
Average Data Rate: 3.6 MB / second
Pixel Aspect Ratio: 0.9091

AVI File details:
Timecode:
Reel name: **************
User Timecode: 08:00:00:11
Reel name: ***************
Contains 1 video track(s) and 1 audio track(s).
Interleave: 1 : 28.59

Video track 1:
Size is 287.93M bytes (average frame = 123.44K bytes)
There are 2516 keyframes.
Frame rate is 29.97 fps
Frame size is 720 x 480
Depth is 24 bits.

Audio track 1:
Size is 15.37M bytes
Rate is 48000 samples/sec
Sample size is 16 bits
 
Did you render as progressive? If so, AME will deinterlace the footage (but Adobe's deinterlacing quality is pretty low, but you shouldn't see what you're getting in that screenshot)

EDIT: sorry I didn't see your last post

Do your sequence settings match the clip? Is this 4:3 NTSC DV footage ?

(nice content BTW LOL . I can see the uncensored title :) )
 
Last edited:
PDR said:
Did you render as progressive? If so, AME will deinterlace the footage (but Adobe's deinterlacing quality is pretty low, but you shouldn't see what you're getting in that screenshot)

EDIT: sorry I didn't see your last post
Click to expand...

So what do you think.. It's frustrating to render for 8 hours and get this crappy result.
 
I am concerned about this, only because I cant get it to work correctly. Moving forward, this piece of footage was the last of the 60i stuff because now I'm shooting progressive.

What's even stranger is the fact that I rendered a clip yesterday with some of the same 60i stuff and it came out great, no interlace lines.

Being a new editor I thought it was just something that I overlooked.
 
Does field order match for sequence (DV is lower field first).

Any dropped frames during capture? This could screw up the cadence and deinterlacing

I suggest instead of rendering the whole sequence and wasting time troubleshooting, limit your testing to 10-20 sec clips until you figure out your workflow and what you're doing wrong
 
PDR said:
1. Does field order match for sequence (DV is lower field first).

2. Any dropped frames during capture? This could screw up the cadence and deinterlacing

3. I suggest instead of rendering the whole sequence and wasting time troubleshooting, limit your testing to 10-20 sec clips until you figure out your workflow and what you're doing wrong
Click to expand...

1. Not sure what you mean by this?

2. None

3. Great idea
 
Are you using a preset that matches your footage? ie NTSC DV ? The field order for DV is usually (always) bottom field first, but Premiere should automatically set this for you

When you place your clip on the timeline is there a red render bar (before you add any effects?)
 
PDR said:
When you place your clip on the timeline is there a red render bar (before you add any effects?)
Click to expand...

I just made a new sequence and added the aforementioned clip into it and NO, I don't see a red bar above it.

BTW, I appreciate your help!
 
I'm stumped. Not sure why you're getting that.

Adobe's deinterlacer leaves jaggies as deinterlacing artifacts (or blends if you use blend deinterlacing), but not combing like the screen shot you posted

But you said some other clips from the same camera worked fine with this process/workflow?

Describe what kind of editing did you do? ie. What kind of effects?

Do a test: If you render the clip straight without any effects but using the same settings (ie. just place it on the timeline and export a 10sec clip) , what happens?
 
PDR said:
1. Describe what kind of editing did you do? ie. What kind of effects?

2. Do a test: If you render the clip straight without any effects but using the same settings (ie. just place it on the timeline and export a 10sec clip) , what happens?

3. But you said some other clips from the same camera worked fine with this process/workflow?
Click to expand...

1. I use the most simple effects. Fade to black/white.

2. Currently I have a clip in AME it should be finished in 15 min (no effects)

3. Correct, I rendered a clip yesterday using the same footage and it came out clean. No artifacts! The ONLY difference is the whole sequence was slowed down between 50 and 80%
 
What? 15min for a 10sec clip? What are your system specs? There is no way it should take that long. Are you playing games in the background?

If this is for web delivery, you won't notice the difference between using "MRQ" and not using it. It's way, way slower with it on. You can test this and prove it for your own eyes

How did you do the slowdown on the clip that worked (what method did you use?)

Are you sure you used the exact sequence settings and render settings?
 
Actually it is 50 minutes. No games I hate'em. I just purchased Dedicated computer to cut on.

AMD 2.5 Duo 8GB ram

EDIT: my mistake I think I took a 10 minute clip instead of 10 seconds, I'll know in a few minutes
 
Ok, I see now. It was a 7 second clip.

EDIT: I see what I did. The footage was 7 second but I rendered 10 minutes on the sequence.
 
Last edited:
Beased on @PDR's advice I'm going through the setting one-by-one to see if I missed anything. I came across this setting on the general page (see attached). Can someone explain what this is for?
 

Attachments

  • 9.jpg
    9.jpg
    61.3 KB · Views: 0
That's the field order, DV is lower field first, and that's the correct setting from the information you've provided about your footage

AVCHD and HDV are usually top field first.

If you have a matching preset, Adobe should automatically set it for you

When you export, and set to progressive in AME, it will deinterlace it (albeit poorly)
 
You must log in or register to reply here.
Back
Top