"Malignant PsF" and Vegas

MikeLV wrote on 2/21/2020, 6:01 PM

Can someone clarify for me about this issue:

https://www.provideocoalition.com/psf8217s_missing_workflow_em_part_1_benign_psf_versus_malignant_psf/

My Canon camcorder apparently shoots in progressive, but Vegas sees it as Interlaced.



With that in mind, what should I do to properly handle the footage in Vegas? And please ELI5 😀 Thanks!

Comments

EricLNZ wrote on 2/21/2020, 6:45 PM

You Canon is saving the files as "interlaced" although they are actually progressive, with each field taken at the same time. It is telling you so in your screenshot. In Vegas go to each clips properties and alter the interlacing to progressive. Alternatively if your project only contains these files you could try having the Projects Properties set to Deinterlacing Method - None.

MikeLV wrote on 2/22/2020, 2:56 PM

I notice that if I drop a PF30-filmed clip onto the timeline and choose in the project properties:

  • Field Order: None (progressive scan)
  • Deinterlace method: None
  • Resample Mode: Disable Resample

Then I don't see any interlacing in the video preview window. And I suppose when I go to encode, then I wouldn't need to deinterlace either. Please let me know if I understand this correctly?

fr0sty wrote on 2/22/2020, 4:31 PM

As long as your media was recorded progressive, and you have your project properties set to field order: none, de-interlace method: none, then any progressive media dropped onto the timeline should be properly displayed. Also, of course, choose a progressive render template from the render as dialog.

Systems:

Desktop

AMD Ryzen 7 1800x 8 core 16 thread at stock speed

64GB 3000mhz DDR4

Geforce RTX 3090

Windows 10

Laptop:

ASUS Zenbook Pro Duo 32GB (9980HK CPU, RTX 2060 GPU, dual 4K touch screens, main one OLED HDR)

Former user wrote on 2/22/2020, 4:36 PM

Some reading

https://en.wikipedia.org/wiki/Progressive_segmented_frame

EricLNZ wrote on 2/22/2020, 5:49 PM

@Former user Thanks for that. Interesting reading. I've often wondered why Canon cameras behaved this way but it appears it's not just Canon.