Capture video 's BAD quality in Premiere pro 2

[yunakokimama]

I capture video from sony handycam DCR-TRV 340. I export video from premiere pro.

then, export to video ( setting: Microsoft DV Avi; Compressor DV NTSC frame rate 29.97)

I am creating sign language presentation. When I sign, I can see the LINE on my hand because I move hand. It is not smooth video. Can see static Line when hand move. How can I make smooth video???
What is the best way to export video from premiere pro2?

[JohnnyMalaria]

Can you post an image?

Do you see this on the final DV - as viewed on a proper monitor - not Premiere's preview?

[daamon]

It sounds like you might be seeing interlace lines because you're viewing on a PC monitor which displays the picture differently (called "progressive" display).

Read up on what both "interlace" and "progressive" are to understand them.

Try playing the output DV AVI from Premiere Pro in something like PowerDVD or WinDVD on your PC - these adjust the playback of interlace material to be viewed OK on a progressive screen.

But, yes, as JohnnyMalaria says - an image would be very useful.

[DavidNY]

Here is the problem I have, maybe its the same issue.

http://www.mozilla.com/en-US/ffflicks/Daredevil-s.mov

The horizontal lines are most noticable where there's motion.

[daamon]

I'm having trouble playing the file back. My Quicktime player says it needs to download updates to play the file, then reports that the updates don't exist.

Can you do it in a different format? WMV, Xvid, MPEG1 etc. And something smaller than nearly 9Mb would be good...

[DavidNY]

Sorry, here's a still off that. Notice the horizontal lines, particularly near the legs, skateboard, shadow and horizon.

http://drnet.net/etc/firefoxflicks1.jpg

[JohnnyMalaria]

You're seeing interlacing.

Conventional TV signals use interlacing. Each frame is actually made up of two "fields". For NTSC, the (approximate) 30 frames per second is really 60 fields per second. The fields are arranged like this to make the frame:

Line 1: AAAAAAAAAAAAAAAAAAAAAAAAA
Line 2: BBBBBBBBBBBBBBBBBBBBBBBBB
Line 3: AAAAAAAAAAAAAAAAAAAAAAAAA
Line 4: BBBBBBBBBBBBBBBBBBBBBBBBB

etc when A are B are the two fields. The fields are snapshot of whatever the camera sees taken 1/60 second apart, so, where there is movement in the subject, you get the artifacts that you see in your example.

But, it is only an artifact of using the computer. The software is taking both fields and displaying them at the same time as if the image was a real, single frame.

If you intend your final edited video to be viewed on a TV, don't worry about the artifacts. The TV will display the fields correctly.

If you intend you final edited video to be viewed on a computer, then you should deinterlace the video. If you search the forum for "deinterlacing" or "deinterlace", you'll find many threads!

[DavidNY]

I have burned DVDs with this artifact and watched them on many different NTSC interlaced TVs. The lines are still there.

My workaround for PPro has been to right click on clip in timeline>Field Options...>Always Deinterlace.

[daamon]

I have burned DVDs with this artifact and watched them on many different NTSC interlaced TVs. The lines are still there.

Then you're doing something wrong or you have a different problem.

Footage shot on a DV camcorder, as yunakokimama is doing, is (unless set otherwise and only possible on some cameras) interlaced. I have shot many, many hours on DV cams, all interlaced, edited in Premiere Pro 1.5, encoded to MPEG for DVD, authored, burned to DVD and viewed and not had interlace lines show. So have many other people.

My workaround for PPro has been to right click on clip in timeline>Field Options...>Always Deinterlace.

Deinterlacing effectively deletes one half of the information (by removing one of the two fields JohnnyMalaria has already explained) and so degrading quality by softening the picture.

[DavidNY]

Yes, "deinterlace" is a workaround, definitely not a true fix.

The editors I work with have the same issue (and are just quietly using the workaround), but I'd really like to fix the issue.

I thought it might be something odd with the incoming video, but I've tried a number of sources and end up with the same artifact.