Interlacing

[ablwr]

AVAA doesn't have an entry for interlacing, but that is a very common video error.

[metacynicv2]

Hmm. I haven't to date considered interlacing an error or an anomaly but I can see where people would think it is an error and try to look it up. I can write one up.

…

On Sun, Apr 1, 2018 at 3:21 PM, Ashley ***@***.***> wrote: AVAA doesn't have an entry for interlacing, but that is a very common video error. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#196>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AI_8UWwC30t09a5Mnk6SOUxbVkfmju5nks5tkSihgaJpZM4TC8Gw> .

-- Kelly Haydon Audiovisual Archivist Fales Library and Special Collections New York University Phone: 212 998-2593 <(212)%20998-2593> Email: [email protected] *Please note that email is the fastest way to reach me*

[privatezero]

+1 for this, I definitely consider visible combing from interlacing an error, just an error on the monitor side (can't handle the signal) rather than the tape side.

Would probably be useful for people trying to figure out why all their digitized video looks funky via the computer!

[bturkus]

Maybe we also try to find some specific interlacement errors too? So two or more different categories--"Interlacement: it's not an error!," and then things like: "BFF captured and displayed as TFF," or "Poor standards conversion during duplication." I just had a great example recently--PAL Betacam shittily duped to NTSC VHS--but I don't think I'm in a good position to share it. Anyone have any ideas about the best way to recreate something similar?

…

On Sun, Apr 1, 2018 at 4:08 PM, Andrew Weaver ***@***.***> wrote: +1 for this, I definitely consider visible combing from interlacing an error, just an error on the monitor side (can't handle the signal) rather than the tape side. Would probably be useful for people trying to figure out why all their digitized video looks funky via the computer! — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#196 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AIkiXmnhfMfpbHTku6hZ8p4Kp79d0edbks5tkTPHgaJpZM4TC8Gw> .

-- *Benjamin Turkus | The New York Public Library* *Assistant Manager for Audio and Moving Image Preservation* Barbara Goldsmith Preservation Division 40 Lincoln Center Plaza, New York, NY 10023 T. 212.870.1609 <(212)870-1609> | [email protected] http://www.nypl.org/preservation https://twitter.com/NYPLPreserve *Lifelong Learning* | *Advancing Knowledge* | *Strengthening Our Communities *

[metacynicv2]

And then what about poor de-interlacing? That can bust things up too, no?

…

On Sun, Apr 1, 2018 at 5:01 PM, bturkus ***@***.***> wrote: Maybe we also try to find some specific interlacement errors too? So two or more different categories--"Interlacement: it's not an error!," and then things like: "BFF captured and displayed as TFF," or "Poor standards conversion during duplication." I just had a great example recently--PAL Betacam shittily duped to NTSC VHS--but I don't think I'm in a good position to share it. Anyone have any ideas about the best way to recreate something similar? On Sun, Apr 1, 2018 at 4:08 PM, Andrew Weaver ***@***.***> wrote: > +1 for this, I definitely consider visible combing from interlacing an > error, just an error on the monitor side (can't handle the signal) rather > than the tape side. > > Would probably be useful for people trying to figure out why all their > digitized video looks funky via the computer! > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub > <#196 (comment)>, or mute > the thread > <https://github.com/notifications/unsubscribe-auth/ AIkiXmnhfMfpbHTku6hZ8p4Kp79d0edbks5tkTPHgaJpZM4TC8Gw> > . > -- *Benjamin Turkus | The New York Public Library* *Assistant Manager for Audio and Moving Image Preservation* Barbara Goldsmith Preservation Division 40 Lincoln Center Plaza, New York, NY 10023 <https://maps.google.com/?q=40+Lincoln+Center+Plaza,+New+York,+NY+10023&entry=gmail&source=g> T. 212.870.1609 <(212)%20870-1609> <(212)870-1609 <(212)%20870-1609>> | ***@***.*** http://www.nypl.org/preservation https://twitter.com/NYPLPreserve *Lifelong Learning* | *Advancing Knowledge* | *Strengthening Our Communities * — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#196 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AI_8USk_UPJQMAILL_352wLfBVsXFyKVks5tkUARgaJpZM4TC8Gw> .

-- Kelly Haydon Audiovisual Archivist Fales Library and Special Collections New York University Phone: 212 998-2593 <(212)%20998-2593> Email: [email protected] *Please note that email is the fastest way to reach me*

[metacynicv2]

these are good questions

[retokromer]

I do like the «Interlacement: it's not an error! Yet…» approach!

[iamdamosuzuki]

I can think of times when interlacing would be a file issue. I've encountered instances in which a file made for progressive playback has not been properly de-interlaced. For example, upresing SD content to HD without properly de-interlacing. Also, I've seen DVDs that aren't interlaced properly and the interlacing artifact is visible on playback.

I've also encountered analog tapes that are poorly recorded and having exaggerated interlacing lines which aren't fully mitigated with deinterlacing filers.

And then of course what you've all already mentioned, which would be playback or monitor errors/mismatches, BFF/TFF mismatches, poor de-interlacing.