Test .avi file to see if it has RFI problems?
 

Well, Here we go again. This time I Un-plugged my Mitsubishi HS-HD2000U VCR from the power strip coming from my UPS which other things are plugged into...(XP Capture PC, and 2 Monitors/AVtoolbox)..And ran Directly to UPS, because some recent, previouse captures still showed signs of RFI or something making wiggly/jiggly/ video noise on Video input from VCR..After many hours of trial and error, I narrowed it down to the VCR and/or Cables....Then I Captured a small .AVI file to share here, which played fine on Capture XP PC. But after transferring .avi file to USB stick,and then to Video PC..It looks like Psycodelic Steam Train!!WTF??..Will try Transfer to USB stick again later, but thought I would share with others my typical luck with all this PC/Capture stuff!..

Don't Give Up!!..Keep working at it!!:knock:

BTW this is a copy of a Professionally made VHS which closely resembles my home-made footage for analysis porpoises:laugh2:

however, looks terrible :eek:

My Huffyuv_MT,Screen 2
view Huffyuv_MT in the new VDub,Screen 3

I agree, looks like a codec issue. I have been recently fond of FFV1 through ffdshow, you might have better luck trying that out. Not sure if there is a guide around here for it, but you may also want to try lagarith.

I'd go for Lagarith. More widely compatible, and even VLC Player supports it now. Besides, you can't save YV12 working files with huffyuv except the ffdshow huff version, which changes every time somebody at ffdshow gets bored. Huffyuv is still preferred for YUY2 capture, but the same dll version can look different on every machine. My captures are huffyuv but get archived as Lagarith when transferred off my capture PC.

I'm surprised you hadn't notice that compatibility problem with huff earlier. some people suggest UT video codec. Another great geek idea until you find out how many people don't use it, and many media players won't decode it.

ffv1 is OK I guess for private use, but like many people I'm tired of installing or setting-up every niche codec that comes along, so I don't even look at a lot of forum samples that use them.

To save all or part of HFYU video as Lagarith, open the file in VirtualDub, set Lagarith as compression and desired colorspace output, then save with "fast recompress".

Does this subsample or is it a true copy?

Define subsample. Are you talking about changing the colorspace? That's not being discussed here.

It's a true copy using a different compressor. You use the same colorspace for output that is used for input.

If you open a YUY2 huff video in Avisynth, apply YV12 filters, then try to save it in that same YV12 with huffyuv, you're out of luck. huff will resample and save as another colorspace.

Does ffv1 make a true copy if the original compressor isn't ffv1? How about ZIP? If you take a zip file and unzip it, then save it as RAR or 7z, is the result a true copy? Do you use the same ffv1 compressor/thread/etc.,etc. settings for every file and every PC and CPU you used it with? How much time do you spend getting into your PC's detailed specs and trial runs of ffv1's settings?

Not changing the color space, but as the capture will likely be at 4:2:2, will the conversion sample that capture at 4:2:2 or make an exact copy?

Thanks all!..This never happened B-4 with any MPEG or AVI files from my capture (XP) PC, In Fact the same file plays fine on Capture PC with ATI File player, this is 1st time it looks horrible on my Win 7 PC, just was wondering if it looks bad, on other PC's.(If you are seeing what I am seeing...(Horrible multi-colered zig-zag noise covering most of screen,with a train barely visible in the middle of it!)...I did recently re-install Huffyuv single/regular version after reading that was better than the multithread version for capturing...so right now both versions are on my Capture PC, But I made sure to select the single/regular version in ATI MMC Codec Huffyuv "configure" dialog box...Maybe I should remove the Multi-threaded versoin? and not have both versions on the same PC?:screwy:

I have both versions on my PC. No problems. But now and then I encounter samples in post where huffyuv doesn't open properly without using tricks like enabling ffdshow's version, or using something like DirectShowSource, and sometimes it just never decodes correctly so I ignore that sample. Your problem might be MMC, which overwrites several YUV registry entries with ATI's own versions of some codecs. You don't need MMC to capture or edit lossless AVI. Most users never install it (drivers, WDM capture, and Control Panel are all you need). You might have some additional codec packs installed somewhere; those all-in-ones create horrible situations, the only one that doesn't create damage is the ffdshow package (and you should disable their version of huffyuv in the configuration panel). That happened to me some years back, solved only by completely removing ATI and reinstalling it without MMC's and its codecs. MMC's player was hot stuff in 2002, but it's pretty old hat by now anyway. But it's your choice, use whatever you want.

A question I asked earlier but didn't get a reply: if you run that huffyuv video in an Avisynth script that requires YV12 filters, how do you save that file in huffyuv? The codec doesn't support YV12, which leaves you with no choice but to re-convert back to YUY2 again or to RGB. Those re-conversions work only up to a point before you start seeing damage....Oh, well, that's a different subject anyway.

It's pretty clear there's a problem with huffyuv. Like I said, I use the older huff version for capture because it's fast on my slowpoke old AGP machines. But it gets copied to hard drives for transfer elsewhere by fast recompress with Lagarith. If I try to open those original huff captures on another PC, I get the same junk you saw in half my media players, and VirtualDub opens them correctly only when opened via Avisynth scripts. Unless your ATI cards are the same or similar ATI+MMC vintage on all your other machines, huff becomes a problem. It pops up now and then on other forums, too.

Yes I put together my XP/ATI 9600XT capture system about 2010 following the DFAQ guides, But kept it "clean" on purpouse, not having anything but ATI/Creative sounblaster software on it, but just added virtual Dub 1.9.11+filters to it,so I can capture using it, instead of MMC..Plus I Just added Avidmux 2.6.10/V-Dub 1.9.11+filters/Audacity/and G-spot to my Win 7 PC, after-which I all that, is when the problem started. No added Codec packs, exept maybe any that may have come with recently added programs?

Hmm. AviDemux has no version of huffyuv of its own, nor does VirtualDub. But let's go back a bit. Other users already know that all versions of huffyuv install differently on different machines and different operating systems. Sometimes it works in a universal manner, sometimes it doesn't. No one knows exactly why, and no one has an answer. In my own work I have two old slowpoke XP AGC machines for capture with huffyuv. Those huffs play OK on a couple of newer non-ATI PCs but won't behave on two others. And as I said, I've downloaded huffyuv samples from various forums, some made with ATI WDM capture and some made with other setups. Most work, some don't. Forum members report they can read the video, others report that the same video won't decode. Huff is known to be inconsistent with Win7 and Win8. Using 32-bit versions of Avisynth/VirtualDub and filters on one system and 64-bit on another is another problem.

One thing you can try on your non-ATI PC: go into VirtualDub -> "Options" -> "Preference" and the "Display" category in the left-hand list. Disable DirectX playback, then restart VirtualDub. If DirectX is already disabled, enable it, then restart VDub. If that doesn't solve the problem, then it's more complicated.

Another trick that sometimes makes a difference: Go into the huffyuv configuration window. If "always suggest RGB" is enabled, disable it. It should be disabled anyway.

Better yet, it's easy enough to make an experiment. Install Lagarith on both PCs. You can download it here: http://lags.leetcode.net/LagarithSetup_1327.exe. The Lagarith installer puts 32-bit LAG into XP, and automatically puts 32-bit and 64-bit in different locations in Win7/64. On your capture PC, open a huff sample and do this in VirtualDub:
- set "Video" -> "color depth" to YUY2
- set "Video" -> "compression" to Lagarith lossless codec.
- You will see the small Lagarith configuration menu. In the window are 4 checkboxes. The only box that should be checked is "Use Multithreading". Uncheck all the others.
- On the right-hand side, set the "Mode" window to YUY2.
- Click "OK" and exit from those menus.
- In the VDub top "Video" menu, enable "fast recompress".
- Save the new AVI.

The AVI should play normally on both PCs in VLC (if it's a newer edition), VirtualDub, MPC-BE, and WMP.

Thanks for the info! (BTW my win 7 PC is 64bit)... actually good to know how huffyuv behaves on different systems, and from different sources...(Affects both capture and playback of captured files?)...And I can tend to really get things mixed-up sometimes, but eventually get it!..All the test .avi/huffyuv files I have captured in past have had no problems on playback (Like the UP844 one I recently uploaded for analysis). So there is obviously something I have changed on both XP/Win7-64 PC's by removing, then re-installing huffyuv on XP Capture PC..(Based on confusion whether to use the single or multithread versions on Cap PC, which I currently have Both versions installed in Programs)...I was successfully using the multithread (2 core) version before on Cap PC, But then stumbled on an older thread with a comment by kpmedia to never(?) use the multithread vers. to capture....But I Shouldn't have tried to fix something that wasn't broke!!:rolleyes: I will try your suggestions, Also will check on my PC for those original huff files that were working b-4.

Plain Huffyuv non-MT/non-64 is my choice.
KISS (keep it simple, stupid).

That video sample plays all garbled for me. Is that your problem?

Right. I should mention stick to 32-bit wherever you can. Supposedly, caps made with huff-MT and huff-nonMT should be readable by any version of huffyuv. It usually is, but no one can explain those odd birds that show up and ain't decodable on another machine.

The capture isn't affected. It's transferring to another system that brings up the playback problem. The original itself isn't changed -- except in the case of the saved sample you posted, but that's not the original capture, it's just an edited and recompressed copy as "interpreted" by VirtualDub on another PC.

Legend has it that's it's really Windows registry's fault. I don't doubt it. If you ever look inside that beast, it's enough to make you cringe.

Yes,all garbled/Psycodelic...Train barely visible in center...didn't have this problem untill I recently monkeyed around with huffyuv codec on XP Cap PC!...It was working OK last few years with Multithread(?) version, and ATI MMC..I am now thinking I had my PC guy install huffyuv along with MMC install, back in 2010, when I wasn't very computer literate....Now I have mixed everything up by Un-installing original huffyuv,then Re-installing both single and multi versions:o I will also try another test Cap and see if it's OK.

Wow Man! Think I'll go ride my bike/have some dinner, then come back to this later,but won't give up!..Thanks again:unsure:

Huffyuv is uninstalled in the Control Panel, which I hope is the way you're removing it.

This same problem drove me nuts a few years back, I even screamed and moaned in a couple of forums. Then I saw it happen to others. I figure I should have bought faster CPU's than the skinny 2GHz AMD's I used for my capture PCs, but...well, you know how it goes on a tight budget and you're just not patient enough at the time to invest another $50. But the huff/Lagarith routine is working OK so far. Eventually you'd need Lagarith anyway to work with YV12.

Yes: Control panel>Programs>"Huffyuv (Remove Only)"

That CPU are fine for Huffyuv. No bottlenecks on the CPU.

Yep, it's pretty nifty for a dual-core. I even had After Effects CS3 running with it and a BluRay player. But maybe just a tad pokey during capture for Lagarith back in 2007. But huff is so predictable and reliable with those AIW's, I just can't let go of it.
:)

Why remove, is a matter deactivating with VCSwap.
Period put.

My Huffyuv_MT version from 2007,see screen

and here a short cutting with Huffyuv_MT
Pal, VHS Capture, ancient tape.Ca 240 MB

www.ww-consulting.ch/DL/Huff_MT.rar

Your link shows up as a malicious website. Access is blocked by Kaspersky and Avira antivirus.

It's a false alert from what I can tell.

If I bypass the warning, I get a blank page. Will try it again later.

[EDIT] After 15 or 16 red malicious site warnings and 5 frozen browser tabs in 2 browsers, I finally got a standard browser download window. The main download page never painted completely.

The huff_Mt capture was decoded, but it's too dark and noisy to be a usable capture. It';s been deinterlaced for no particular reason and alternate frames discarded, so 50% of the original video is missing, motion is clumsy. Perhaps this was done for internet posting, but it's still not a useable image. Has oversharpening artifacts, lots of horizontal tape noise, and has noisy, wiggling edges (no line tbc?). It doesn't play properly in my VirtualDub -- no filters are mounted, but the output pane flickers. This looks like deinterlaced DV recompressed with muff_MT -- at least, that's what the artifacts look l like to me. Looks to be a copy of something, because even the black borders have the same noise as the images. I could be wrong.....

OOps. Never mind. Plays OK in Virtualdub. My antivius scan slowed things down a bit. My fault.

Very bad condition, as you probably know. After adding some luma gain in Avisynth, it now looks as if the source is a tape duplicate. Has been through some processing, such as deinterlacing and masking of the boittom border head switching noise that places the image off center, instad of cropping and adding balanced borders. Stiil, you might be able to rescue the clip, up to a point.

Below is frame 178 of the original sample, with borders removed. The image below that is a YUV histogram showing crushed darks, which doesn't include the black borders. There's no luminance above RGB 128, which is pretty dark. There is also a lot of luma flicker and some line timing distortion.

frame 178 (original, borders removed):
http://www.digitalfaq.com/forum/atta...1&d=1436892317

frame 178 (original, YUV levels histogram):
http://www.digitalfaq.com/forum/atta...1&d=1436892382

But with a lot of work you can get a clear but still fairly noisy video out of it:
http://www.digitalfaq.com/forum/atta...1&d=1436892440

The attached m2v version has no audio. The original audio track has an invalid PCM sampling rate. Still some bad ghosting and edge ringing.

This was only one test video, original from UYVY.
So a Rohcapture, without filtering.

Clear the film has mistake, because it was sent original in 25P and then was struck up on VHS.
Then Avisynth filter "PhaseShift" + SelectEven () helps there and QTGMC

The VHS tape is given to me here in such a way, totally has 3 same tapes.
Original the film with 16 mm of camera was taken up, stored away in 1969 and then in NTSC.
I have here the version PAL.
Film name "Woodstock" is hopefully to be written this permitted here.

Tomorrow, unfortunately, I do not have a better film quality and will look after it. With us it is 24:00 o'clock

Supplement_ audio is absent, now I notice only.
In the original it is embarrassing available.......

I suppose there has been already built with the norm change by NTSC to PAL big dung.
Then still progressively on interlaced on VHS.
Thus it looks, in 25P
Pity for the work

I wonder if the problem with Huffyuv files not decoding properly on another system is due to a mismatch of the interlaced decoding flag between the encoder and the decoder. The original version of Huffyuv uses a hardcoded value while later versions let you specify the number of lines that triggers the different coding method.

Note to admin: Perhaps good Idea for admin to change title of my original (this thread) to read: "Test file to see if Huffyuv/codec problems?". I uploaded sample file before realizing how messed-up it was, because it played ok on the capture PC!. I was intending to get RFI opinion, but thread wound up being a very good learning experience about Huffyuv/Lagarith instead. Once I get my Cap system working good again, (with playable files!) then I will start a new thread too see if still any RFI present on my captures:cool:

Some have noted the interlace parameter problem, but it doesn't seem to have fixed anything. Years back, I took old huffyuv caps from an old PC and couldn't read them in Virtualdub on a different machine, but they decoded properly when opened with Avisynth. At least, I think that's the way I worked around it. Its been so long ago, I don't even remember exactly how I did it, LOL!.

The audio bitrate on the first sample was non-standard and gave two of my mpeg encoders an error:
For my histograms I used PC levels. As your EDIUS image shows, converting PC levels to TV levels brings the blacks up to RGB16. However, the EDIUS vectorscope and waveform still show clipped (compressed) darks at RGB 16. Whether dark detail is crushed at RGB 0 or at RGB 16 is not the issue. The issue is that darks are compressed into a narrow range. The vectorscope and waveform also show useable data is cut off below the midrange. In other words, the tape is too dark.
http://www.digitalfaq.com/forum/atta...1&d=1436978119

YUV Levels histograms show the different black levels for PC and TV.
left image = PC levels show clipping at RGB 16 and below, and suppressed midtones.
right image = TV levels clipping above RGB 16, which is raised from black to dark gray. Very little midtone data. PC levels raises the black border to RGB 16, but data is still dark gray with little detail. Usually the borders are RGB 0 anyway rather than RGB 16. Most of the darks in the image are obscured and at the same dark level as the borders.
http://www.digitalfaq.com/forum/atta...1&d=1436978264

ColorFinesse was set up in After Effects to examine the same video at TV 16-235 levels for PAL BT.601. A screen capture of the ColorFinesse color system setup is attached as AE Color Finesse - video system setup.png. The image below demonstrates how the video would display as TV RGB. There are 4 charts: Luma waveform (upper left), YC waveform (upper right), YRGB waveform (lower left), RGB Histogram (lower right). All show data compressed at or below RGB 16, which displays at "TV Black" on TV. All charts show cutoff below the midtones.
http://www.digitalfaq.com/forum/atta...1&d=1436978704

The histograms below show the effect of adjusting gamma and using a basic contrast mask to elevate gamma in the range at and below RGB 128. 16-bit dithering was used with the SmoothAdjust plugin to level out gaps in the RGB range and to heighten brights above RGB 128. The histograms show increased detail and output in YUV levels (left) and in RGB TV display (right). There is still some super-black data in the display, but that area contains no details anyway and is mostly RGB 0 black border.
http://www.digitalfaq.com/forum/atta...1&d=1436978925

The newer samples have several problems. Sample #3 is oversaturated and looks almost like animne. I still don't know why users deinterlace video unless it's for web or PC-only display.

And thank you, Goldwingfahrer, for the clip with audio. Attached is a version of the earlier HuffMT.m2v...but now with sound!
:)

I have provided test with mpeg2 first, with the Procoder, see Screen.


Yes, I know, I can play there in edius [6.08 + 7.50 with the curve YUV something, today I have also made, however, does not become so great.
On 3 VHS of tapes and today on a new package with 2 VHS of tapes [part 1 +2] and also on the Blu-ray-Stram [m2ts Codec WVC-1] the Intro is exactly equally black.

But on the Blu-ray at least the audio is quite good.

I have already noticed this if I look at the Stream, see Screen 2 in VDub.
RVB is RGB [is a French programme, green =Verte]

Okay, this was only one teststream.
Do not forget, tape VHS, is original the film in NTSC 23.976 and was encoded very badly to Pal.
now I have 5 springs here [inclusive of the Blu-ray] and in the kalibibrierten TV + in the calibrated Eizo SX and also [interlaced] in the professional studio controlling monitor I see that the colours are oversaturated and the picture very badly.
Unfortunately, I have no better spring, must still continue to search.

And still what... I am a fan from interlaced, no matter whether in mpeg2 Stream or in MP4 Kontainer as a MBAFF [MBAFF = Interlaced] mostly TFF.

Analogously Captures are here always TFF when I see, however, that a film original in 25p was sent and then improperly badly on VHS it was covered up, this tries to consider with Avisynth and PhaseShift.

However, I see... has not succeeded me here.

Thanks for him type with Color finesse, I have AE in the Adobe package CS6.
Work with it, however, not enough there my Stream always in UYVY or YUY2 are given and picture rushing in
Y canal have. Adobe anus effect can work only in the RGB.

... my translation hopefully well comes across....

interesting analysis tool. I noted some entries you show in red:

** Number of Audio Streams: The audio is AC3. The use of MPEG-1 Layer 2 obsolete in many countries, not used commercially in the U.S. for prime releases. It is not high quality audio compression.

**Horizontal Size = 704: PAL and NTSC 4:3 captured from VHS occupy only 704 horizontal pixels in a 720x480 capture frame. 704x480 is valid for DVD and BluRay. However, BluRay 16:9 DAR requires full width 720x480 for standard definition.

** Top Field First: encoded as progressive, so no field order is specified.
** DCT Type (Frame): The encoding is progressive, frame-based, no pulldown.

Yes, it is shocking the way some people process video, even if the source is old fashioned VHS. One can only do the best they can muster with the tools available to repair.

Well...I'm not sure what the "anus" effect means. I do noise removal and basic levels determination in YUV in Avisynth. Most Avisynth filters are YV12, a few work with YUY2. NLE's are not good repair tools -- after all, they are primarily editors, not total restoration tools. They process color well, but better when I use Avisynth to set the colorspace. Premiere, After Effects, and other expensive NLE's have color filters for YUV and RGB.

The 03.avi sample was difficult to correct. It has less noise than the earlier video. But the color is terrible, as you say. The first step was levels. saturation, and gamma correction in YUV (Avisynth). Chroma exceeds RGB 0-255 at both ends of the spectrum, in both YUV and RGB. Wide chroma and luma contrast can work with film, but the film spectrum is too wide for digital video. In the image below, the high saturation makes the colors "glow" and "bloom". The colors and levels are innaccurate, unrealistic, and unconvincing.
http://www.digitalfaq.com/forum/atta...1&d=1437014328

http://www.digitalfaq.com/forum/atta...1&d=1437014448

Levels correction and noise removal were run in Avisynth. This was followed by moderate color and gamma refinement in RGB (VirtualDub). YUV to RGB conversion was run in Avisynth. RGB return to YV12 was also run in Avisynth.
video Encoder: TMPGEnc Plus 2.5.
Video/audio remux to Dolby AC3: TMPGEnc MPEG Editor v3.

not everything what is there red it is recognised as wrong.

Yes, I know this. Various programmes inflate simply on 720.
Here, besides, I had with Adobe Encore of early problems, it could start with 704 x 576 nothing.
I have distributed TMPGEnc old and also the newer version, from the Authoringtool as well as from the Codierer, but on 3 PCs.
My favorite tool for the DVD production is still Ulead a power tools 2.

Yes, with Avisynth. I learnt here a lot in the Doom9 / Gleitz forum of user LigH, scharfis_brain, Didée and other.

Yes, YV12... I knows most filters work in this plan are.

here to the view control I can send under edius interlaced stream from timeline about the Canopus NX map by YUV or by Y/C in the tubes 50 hertz of studio controlling monitor.
Edius I already have since the first version, at that time still with Storm DV, the analogous by the way by Y/C in UYVY capturen was able... nice old time.

Yes, in Avisynth it would be the best....., unfortunately I have there a picture only in VDub on a progressive screen and not by the controlling monitor with 50 hertz interlaced.
I must deal there sometimes more with Avisynth.

Perhaps, they show me sometimes the Script you have provided, then I get on, I am not a beginner in VDub and Avisynth.

They should look sometimes at the picture like it is stored on the Blu-ray... I soon catch in to cry...:D

I used the Avisynth script shown below, followed by two Virtualdub filters. The script was opened in VirtualDub and the VirtualDub filters were applied to Avisynth input. The VirtualDub output can be saved to YV12 (I used Lagarith lossless compressor for YV12 output).

In the script, QTGMC is used in progressive mode ("InputType=1")

The Avisynth filters used:
- SmoothAdjust v2.62 http://latoninf.free.fr/d9/SA/SmoothAdjust-v2.62.7z
The doom9 thread for SmoothAdjust. The filter includes the functions SmoothTweak and SmoothLevels: http://forum.doom9.org/showthread.php?t=154971
- FixChromaBleeding http://avisynth.nl/index.php/FixChromaBleeding, which requires ChromaShift http://avisynth.nl/index.php/ChromaShift.
- HQdering http://avisynth.nl/index.php/HQDering (the web page also has links for Deen and MaskTools2).
- QTGMC http://forum.doom9.org/showthread.php?t=156028.
- AddGrainC (is included with QTGMC support files package)

VirtualDub filters used:
- ColorMill v2.1 http://fdump.narod.ru/rgb.htm
- Gradation Curves http://members.chello.at/nagiller/vdub/index.html.

I have attached a VirtualDub .vcf filter settings file for the settings I used. If you have not used .vcf files previously: a .vcf is a simple text file that can be opened with Windows Notepad for reading (but not a good idea to change the text!). To load the filters and settings into VirtualDub, Use "File.." -> "Load processing settings...", and navigate to the location of the .vcf file. Most users keep the .vcf file in the same folder with their video project. Don't place .vcf files in the VirtualDub plugins folders.

The two VirtualDub filters mentioned must be in your VirtualDub plugin folder.

Everything can be tweaked and refined as you wish. I ran out of time for perfection.

Cool... big thanks.
When do you sleep, actually?

FixChromaBleeding and HQdering is not to be found any more on the aforesaid side, however, it has still found in my archive.

The first step is done, if the "ts" file has though not taken separate the file gecapturte anew [YUY2] with VDub to Lagarith YV12 coding.

Then the next step is with VDub. I have there 3 versions. 1,9.11 + 1.10.4 + 1.10.5...
must decide me sometimes for a version.

Every night. :)

Damnation! :smack:
It's been a while since I downloaded from those links. It appears they have moved. For those who don't have the missing plugins, I have attached For_Avisynth.zip. It contains Deen, FixChromaBleeding, ChromaShift, and HQdering. The version of Deen I have been using is the 2005 version.

For those who don't have the VirtualDub filters, I have attached For_VirtualDub.zip. It contains Gradation Curves and ColorMill.

Use 1.9.11. I still see occasional complaints about the other versions.

The script and VirtualDub filters used for 03.ts can't be used for the darker clip. They have completely different problems. I will forage for the filters I used for the dark clip and post later. It may take a day or two, I will be traveling for family affairs for the next couple of days and won't have my computer.
:depressed:

DirectShowSource I take for over 10 years not really more, there were earlier a lot of problems with it. One never knew which decoder there was taken, even if one had adapted the "Merit", there always remained a risk.
Mostly demuxe I the Streams and work on only the picture contents by means of Avisynth.
Besides, the Capturestreams are given in YUY2 [Canopus NX] or in Lagarith, or come directly by SDI to the PC.
There reaches "AviSource"
Now for "Ts" I would have used rather LWLibav.

In addition as the 3rd filter I have still inserted ChromaShift in the filter chain VDub.
Blue colour of the shirt of the reporter is something too far on top.

With TGMC and the settings I get no so good result like with the above Script.... Cool.
Only the picture rushing something is mostly to be eliminated, it must not be completely, however, the Encoder draw mostly the picture still a little bit softy.

I did a few test encode-decodes and I wasn't able to trigger the problem this way. For example, encoding a Huffyuv-MT file with "lines" set to 576 and decoding it with "lines" set to 288 was no problem. However, ticking the box that says "Ignore is-interlaced flag" for the decode side did corrupt the image.

Attachment 4970
Attachment 4971