Moving off topic from the original thread topic, so feel free to skip this post and I'll try not to go too far in to detail.
Originally Posted by grahamlthompson:
“I know but the results are not as good as original footage.”
Probably not, but it's better than not having the choice at all, which is the case if your original source is only the film-like 24/25/30-fps.
Originally Posted by grahamlthompson:
“What exactly are the problems with editing interlaced footage.”
Partly that you and your software has to be interlace aware, retain that structure and be able to work with it (e.g. if I import interlaced footage into some software, it treats it as a single frame. If I then apply a sharpen filter to that, the interlace structure around the area of movement is sharpened.) People who know more about this than me are probably aware of how to deal with it, but it's an additional complexity and nuisance.
AFAIK, there are other potential problems caused by the fact that we never have a complete set of odd *and* even lines for any given point in time.
Slowing footage down (e.g.) 4 times? If we have successive fields (1) odd (2) even (3) odd (4) even then the obvious answer is repeat each field four times (e.g. 1a, 1b, 1c, 1d, 2a, 2b, 2c, 2d, 3a, etc.) but although 1b should be an even-lines field, it has to be be derived from the original frame 1, which only contains odd lines.
One could deinterlace to 25/30-fps, but that loses quality and changes the appearance. I suspect that modern software like Vegas *should* be able to use information from near-static backgrounds for adjacent fields to generate full resolution detail at 50/60-fps, and for faster-moving objects where this was not practical, half resolution interpolation probably wouldn't be noticable because the objects *were* moving. But that'd still be an additional complexity, and probably requires processing power to generate- as well as the resultant interpolated 50/60-frame progressive output then needing the same amount of power/memory to handle as "native" 50/60-frame footage.
Similar issues should apply to rescaling and other distortion effects.
Also, as far as I know, interlaced footage is slightly filtered vertically to reduce "twittering", so you'd be starting off with marginally lower quality video.
Didn't want to sound like I was making a deal of this, but you did ask.
Originally Posted by grahamlthompson:
“You still need a state of the art PC and a long wait to re-code.”
Aren't you going to end up recoding it anyway, unless you plan on watching the original unedited footage, or editing it in a way that doesn't require re-encoding most of the original source (a la VideoReDo)?
Originally Posted by grahamlthompson:
“Try doing that starting with 1080p50. To get reasonable footage from 1080p50 you really have to keep the 50fps frame rate and reduce the resolution to 1280 x 720 (720p).”
Or you could interlace it at the final rendering stage, which I would probably find acceptable for viewing the end product personally (YMMV!)