Still fighting Flying interlaced boxes

[Rafael Amador]

Hi Nate,
If you are watching interlaced footage in a LCD monitor, you have to expect the combing.
Depending of many factors,, will be more or less noticeable, but the interlacing is there.
If you want to avoid this, the only way is working progressive.

[Nate Stephens] “All edits are lower field except graphics and Boris which is ‘none’. “
Laying progressive graphics over interlaced footage will always look strange. Two different cadences.

[Nate Stephens] “And I still had a vibrating flutter on the top of the scaled down clips”
On those “vibrant’ picture, just drop the “Flicker” filter and you will be amazed how well works, without smoothing the picture.
rafael

http://www.nagavideo.com

[Nate Stephens]

Thanks but,

This work is be to exported to betacam sp NTSC for local cable playback.

I changed the settings on the graphics to lower (from none) and it did not eliminate the problem as viewed on my 19″ Sony PVM.

P2-30P imported at 29.97 according to the properties tag.

Thanks for the Flutter filter reminder. But that solution is only a cure for for the 8 bit timeline transcode and edit.

There has to be an easier way.. ( Just give me my old Sony Betacam and Cinewave.)

FCP, Mac Pro, Mac Book Pro, HPX500, HVX200, Betacam, Dvcam
Write for the Edit, Shoot for the Edit, Edit…..KISS Principle

[Adam Taylor]

its possible that your scaling and positioning are introducing the interlacing errors.

Always try to keep scaling to even whole numbers (ie. 46%, 72% etc).

Also , check the positioning co-ordinates and again try to keep them on whole pixel values.

adam

Adam Taylor
Video Editor/Audio Mixer/ Compositor/Motion GFX/Barista
Character Options Ltd
Oldham, UK

http://www.sculptedbliss.co.uk

[Rafael Amador]

[Nate Stephens] “I changed the settings on the graphics to lower (from none) and it did not eliminate the problem as viewed on my 19″ Sony PVM.”
Are you laying the graphics to the time-line again after changing the field-order?
Rafael

http://www.nagavideo.com

[Nate Stephens]

Yes I am using the same graphics in the timeline that were ‘none’. I went to properties and changed the settings to lower on the graphics and kept them in the time line. Do I need to export the none graphics as ‘lower’ and re-import them. That would be a bitch considering all the ‘none’ Boris 3d I have in the spot.

I never had this problem with betacam sp.

Is there a special setting when importing P2-30P. It shows up in the properties tab as 29.97-lower. Which should be what I want. Me thinks that the 30p is really 30psf – progressive segmented frames and that might be the problem… my best guess so far…..

Does anybody else have problems playing DVCpro50 out there Kona Lhi card?

FCP, Mac Pro, Mac Book Pro, HPX500, HVX200, Betacam, Dvcam
Write for the Edit, Shoot for the Edit, Edit…..KISS Principle

[Doug Beal]

Make sure your easy setup corresponds. There is a DVCPro50 NTSC in the Kona presets.
Check your RT settings if you are set to dynamic you are not seeing what’s really going on.
Follow the above suggestions re even numbers etc. the other thing that really affects how the boxes look is speed of movement. remember in SD NTSC field1 is drawn first on the screen top to bottom then field2 is drawn top to bottom so finding the right speed is critical. Motion blur will help
That being said this kind of work is better suited to “Motion” with field rendering turned on. FCP is frame based. DVCPro50 is equivalent to BSP without the dropouts. it’s an 8 bit format

Doug Beal
Editor / Engineer
Rock Creative Images
Nashville TN

[Rafael Amador]

[Nate Stephens] “Yes I am using the same graphics in the timeline that were ‘none’. I went to properties and changed the settings to lower on the graphics and kept them in the time line.”
After changing the field order in the Browser, you need to lay the clips again in the sequence.
The changes in the Browser do not affect the stuff already in the time-line.
Rafael

http://www.nagavideo.com

[Robb Harriss]

wish I could see it. But you know, your Betacam output is always interlaced, you’re not going to avoid it. You’re just facing what so many of us faced for years, and that’s sharp edges showing problems. Horizontal lines are the worst. The suggestion of the blur filter is probably the most helpful. Over the years, we developed all sorts of ways of tricking NTSC into behaving. All were only marginally successful. Editing on computer monitors is nothing more than deceiving at best. While some systems will allow you to see real interlaced video frames, most will not. Wait until you have an animation with the wrong field rendering. Now they’re really fun, especially when you don’t see it until you’ve spent a couple days in rendering. Ah, the memories. . .

Non-linear: all the time and nothing but.