Yes, with PAL = 288
With NTSC = 240

No hook

An example,see screen

I think we're having a language barrier issue.

I know the proper settings (and 288 works as a threshold for both PAL & NTSC if you stick to standard SD resolutions). I was deliberately trying to find out which wrong settings can trigger the decode error.

Okay, so a known incompatibility was introduced when other developers modified the original Huffyuv 2.1.1 to create the CCE-SP patch, 2.2.0, MT, and the other off-shoots.

Huffyuv 2.1.1 encodes and decodes any Huffyuv file according to the rule that interlaced = true when lines > 288.

The original CCE-SP patch replaced this with a global setting stored in an INI file.

With 0.2.4, the CCE-SP patch wrote a flag into the file so it was no longer reliant on the INI file's threshold to determine whether the interlaced encoding mode was used. But Huffyuv 2.2.0, from a different author, introduced a different flag to do the same thing. So the author of the CCE-SP patch pulled 0.2.4 and made 0.2.5 mutually-compatible with Huffyuv 2.2.0.

For ffmpeg's Huffyuv, the patch removing the hardcoded threshold (src code) mentions the incompatibility with older versions:
Having said all of that, this only explains the problem with decoding the OP's file if he created it using a Huffyuv version older than CCE-SP patch 0.2.5.

---

EDIT: I successfully decoded the file, at any rate. Huffyuv's debugging option was helpful. The "Ignore is-interlaced flag" setting causes the decoder to behave the same way as the CCE-SP patch versions before 0.2.4; the global Field Threshold setting from the INI is used to determine the decoding mode.

I used AVISource("test pentrex 5 ATI MMC 7-10-15.avi",fourcc="HYMT") to force Huffyuv-MT to decode this HFYU file, since 2.2.0 lacks the "Ignore is-interlaced flag" setting and I don't feel like installing another version.

Attachment 4974
Attachment 4976

288 / Field processing enabled
Attachment 4975

576 / Field processing disabled (with Avisynth Info)
Attachment 4977

The frame rate is bad, and I hear clicking in the audio track.

Thanks, msgohan. Answered many questions.

From your post #37:
http://www.digitalfaq.com/forum/atta...file-sanlynjpg

The image you posted uses the script for 03.avi to process the dark clip 01.avi. The same script can't be used for both videos, they have different problems. The script that I used for the video shown in your image was different and involved 2 steps in 2 scripts.

The script for Step1 is below. The original black borders (which are too bright and too noisy) were cropped from the video and the core image was run in Avisynth. The borders are replaced later in Step2. At the same time I loaded four VirtualDub filters and saved the output of that Step1 process as YV12 lossless (I used Lagarith lossless compression).

Step1:
The four VirtualDub filters loaded and run with the script were CamcorderColorDenoise 1.6MT, DeFlicker1.3b1, ColorMill, and Gradation Curves. The script and the filters were run using "full processing mode" and saved as "Step1" using lossless YV12 on output.

Step2.
The saved YV12 video fom Step1 video was opened using script #2 below:
I have attached "For_Avisynth.zip" which contains Avisynth plugins you might not have:
autolevels_0.6_20110109.dll, AvsRecursion.dll, awarpsharp.dll (for awarpsharp2), ContrastMask.avs, DeHalo_Alpha (as "DeHalo_alpha_MT2.avsi"), FFT3dGPU.dll, gradfun2db.dll, GradFun2DBmod.avsi,hqdn3d.dll, RemoveDirt_v09 (with RemoveDirt.dll and RemoveDirt.avs), RemoveSpotsMC.avs, rgTools-x86, TemporalDegrain.avs, and VariableBlur_070. These filters are core plugins and support files for TemporalDeGrain, ContrastMask, awarpsharp, etc.

I have also attached "For_VirtualDub.zip". It contains two VirtualDub plugins you might not have: CamcorderColorDenoise 1.6MT and DeFlicker1.3beta1.

Also attached is "hufftMT_01_Step1_VDub.vcf" with the settings I used for the 4 VirtualDub filters run with Step1.

You could try running both scripts together as one, but the processing will be too slow and could sometimes hang VirtuaLDub. I often use two separate steps for very slow processing.

Big thanks... am in the work.

I have used most filters long since, but only seldom, because I primarily only Capture.
50 devices always in order hold a lot of time needs.

Yes. with 2 steps I know since RemoveNosieMC from heini011
http://forum.doom9.org/showthread.php?t=110078

But here mostly I do not have so bad material like now with Woodstock.

The fact that with "QTGMC (InputType=1" I know of course... that "Mode=1" for progressive material is, in contrast to "Mode=0" this is for interlaced material.
One reads a lot..., however, everything can not always keep in the brain if the brain is small.:o

Video that is in decent condition requires much less work. Usually the video I work with doesn't require this much effort or time. But sometimes the video is so bad, you have no choice if you want better results. In any case, it is very rare that I can use exactly the same filters for every video, especially with analog source because it differs so widely.

Yes, is quite clear, there is not only a Script for all springs.
Although I have VDub and also still VDubMod, I have landed in the postprocessing with Edius.
this has the advantage, I see the picture like it is given correctly also thus in the connected view device and not in the PC monitor which is good for Interlaced nothing.

First becomes gecapturt, in YUY2... then only picture] with Avisynth TGMC is prefiltered of the Stream [in the fashion MT a little bit.
This claps rather fast and I can go on working on another PC.

As well as it looks I must remove a lot of newer Plugins to load old Plugins.
TemporalDeGrain from old 0.9 packages. my version is from 2011.
ContrastMasc does not clap here, finds not all Plugins.
RemoveSpotsMC also does not clap.

In principle, no rhomb [#] of the line should be in front in it :D

Must load all Plugins in a separate folder and then appeal.

Thank you msgohan, for a while I was getting kind of lost in all this (but learning). The source VHS tape was was from a commercial video producer, made about early 1990's, may, or may not, have had some form of copy-guard?, and TBC was used (always). Earlier caps of Home-made tapes played fine on cap PC and others UNTILL I messed with/changed Huffyuv versions and settings on XP cap PC. Have v2.1.1/patch 0.2.2 (by Rainbow Software) and v2.1.1 mt patch 1.0.1 (by m_elijah)..both non 64bit, downloaded from this site. I think mt ver. was working good b4., but then I changed to non-mt version, (using ATI MMC/AIW 9600xt) and then set YUY2 comp to: "Predict gradient"/RGB comp set at "Convert to YUY2"/Field Treshold to "480" lines, and "Enable full size output buffer" box checked...BTW,After transfering file to other PC, got error "VLC cannot play HFYU format" when ...So I'm assuming the problem is with Cap PC (Something I did/changed:hmm: probably)

Supplement
sanlyn... I must take for a ride the Plugins in a separate unterfolder and appeal separately, thus klappts.

However, I may not cut so much, see picture

Basically, all these troubles should be gone if you go back to the MT version. But the thing I bolded is what caused this issue. Setting Field Threshold to 480 is not only unnecessary, it's incorrect unless you're compressing standard content that is 480p or above. Setting this causes the incompatibility problem, and the compression ratio suffers because you're encoding interlaced material using progressive mode. When the output isn't garbled, the video is still lossless and 100% matches the original, but it's larger than it needs to be.

When you're ready to post another sample, I would like to see one direct from the VCR to the capture card, to eliminate more hardware variables.

I believe there come with the 1st step a few wrong "dll" to the use.
Processing claps with from 3.40 to 3.60 fps.

With my easy "first settlement" here also as the 1st step, it works in the MT fashion with from 19 to 20 fps.

On the left in the picture = TGMC [the first settlement]
On the right in the picture = 1st step/Avisynth with VDub
File as mpeg2.... folds so it with the high-level store in the net.

2. Film clip = in Edius the Croma something reduces in left picture half.
--------------------
Now this is only one example, as a rule it is encoded to AVC + AAC + in MBAFF.

Thank you!...which setting is best?...The recommended/must setting is 480 for NTSC users, as mentioned in the "Capture AVI using ATI AIW card" guide, but that may have applied to the earlier, single version of Huffyuv?
Yes, always (for now) VCR to cap card only samples, (and LOL!, that's what I was trying to do originally!)..but learning more stuff about all this due to problem!..Meanwhile, I recently posted a working,good file, just b-4 I monkeyed around with cap PC: http://cdn4.digitalfaq.com/rockovids...tAVtoolbox.avi ....Can you tell what my settings were from this file?...

Should we be able to? The default field threshold is usually 288. Did you try that recently?

Nope. Sorry to say that lordsmurf simply got this one wrong. The setting is a > switch, not a >=, so a capture at 480 with the threshold set to 480 will be in progressive mode. The line about "Interlace requires more than 280 lines of resolution in the digital world, so PAL users can choose 288 or 576" is not accurate either: capture cards will discard one field when set to 288 height, the same as when capturing NTSC at 240.

The default value of 288 works perfectly fine for both NTSC and PAL so long as you stick to only standard capture resolutions: those with heights of 240, 288, 480, and 576 (and there hasn't been a reason to capture below 480 since the early 2000s). Even the author of the CCE-SP patch who criticized the fact that 288 was hardcoded and originated the Field Threshold option admitted this!

His suggestion of capturing NTSC with 288 lines isn't even possible with any capture card I'm aware of. It's a ridiculous idea that no one would ever seriously do. The only real value of giving us the option is that it allows us to alter the number accordingly if we're doing a capture at EDTV or HDTV resolutions.

(sanlyn) I wasn't sure if that was even possible, but nevermind, I'll concentrate on fixing the present problem and sticking with those settings that work..(sanlyn)Thanks, will try that soon.

(msgohan)Thanks, Lots of info to digest, both here, and also reviewed the Doom9 posts..will dig back into cap PC and settings soon.

rockovids
Read sometimes the 2nd contribution

Since you're capturing NTSC you should use field treshold of 240 lines, 288 is for PAL.

http://forum.videohelp.com/threads/2...-about-huffyuv

:argue:(Hee-Hee!) Thanks Goldwing ,This is the best smile icon that I could find for feeling like a ping-pong ball right now, but I will take what everyone says, and try it out, One thing for sure, I will take notes this time, about the final settings that do work on my system!... I do have the system restore option from 2012,but that is a last resort. Only about 5 years experience with computers, but I have learned from this site, that every situation is different, with VHS capture/software/hardware..for a while I was/am guilty of easy monkey-see,monkey-do!:yikes: