ghosts in part of encoded file

I am encoding a DVB source (hockey, originally 544x480, 29.97,NTSC, Interlaced) to DVD (352x480, deinterlaced). Most of my encodes using the rather simple script below have come out fine. However, lately I have had two encodes where part of the game - maybe 20 minutes or so - shows ghosts as the players skate or the lines go by. There seems to be no difference in the source video from a problem part to a non-problem part; it is all originally interlaced and DVD2AVI doesn't suggest anything different at this part of the video. I have tried both TMPG and CCE and both have the problem. Here is my avs: movie="wjc1978.d2v" MPEG2Source(movie) FieldDeinterlace(blend=true) GripCrop(352,480) GripSize(resizer="BicubicResize") GripBorders() converttoyuy2() If anyone knows why this might be happening or can suggest any solutions, please let me know. Thanks. -gosens

the difference in the "good" bits and the bad bits is most probably the shutter speed used in the original recording. blend deinterlacing will be least noticable if the shutter is set to the field rate (1/50 for PAL, 1/59.95 for NTSC), so the motion blurring from one field matches up perfectly with the next. a lot of sports/action footage is shot with a much faster shutter to give the impression of more action (well, that's my guess anyway..). when this content is blend-deinterlaced you'll get very noticable ghosting (and it'll b0rk your encoder's motion search algos). so yeah, use sh0dan's suggestion (or one of the custom deinterlace scripts hanging around here, which preserve loads of detail at the cost of VERY slow encodes :))

oh yeah! i forgot aboot those slo-mo cameras. man, it'd be fun to have one of them. think about it! i'd do EVERYTHING in slo-mo! btw, blending several frames together != motion blur. there's awful dynamic range effects when that happens. overbright things turn grey rather than some rich colour. anyone who's seen HDRI 3d images compared to standard dynamic range images would see the difference... i wish camera sensors/DSPs could give floating-point output... of course any TVs that supported this would burn out people's eyes :)

blend=false