![]() |
AVI capture problem! Huffyuv glitched playback?
2 Attachment(s)
The .avi sample I posted a few days ago, about "video stuttering?" was captured about September 2016, with good results. This .avi capture sample was just done a few days ago, with same settings, but after having to Restore XP capture computer to earlier date (about 2015 restore point), because ATI MMC was not responding, and freezing, when hitting the Record Button, resulting in having to force a restart. After restoring XP Cap PC to earlier date, I was happily recording again a few days ago, and this file plays fine on original XP Cap PC with ATI Video Player, But looks all crazy after transferring, and playing on my Windows 7 PC, does it look crazy on your player? or is it just my playback system on Win 7 machine? The videos I Capped on Sept. 2016 play fine on My Win 7 system, But these recently capped files look all crazy! :unsure:
I've also attached a screen shot of what "crazy" looks like on my Win 7 system, just in case the sample plays ok on your system! |
Uh.... :huh1:
Yeah, that's what I get too. Something is corrupt with the capture. I've never seen anything like that before. |
Quote:
|
2 Attachment(s)
The sample Tape 42 008.avi from post #1 as compressed with huffyuv using a threshold of 480 lines for progressive video instead of the recommended 288 lines for interlaced/telecined video. I have my system huffyuv set up for 288 lines, and the sample would not play correctly in VirtualDub or any media player..
I re-set my own huffyuv to 480 lines threshold and the video played correctly in VirtualDub. I mounted that avi in VirtualDub and re-compreessed it to Lagarith YUY2, attached as A_Tape 42 008_Lagarith.avi. If you don't have Lagarith (and why don't you?), go here: https://lags.leetcode.net/codec.html I then re-set my huffyuv to the proper 288 lines threshold and opened and recompressed the Lagarith version into YUY2 huffyuv B_Tape 42 008_huff288.avi, attached. It plays correctly on all three of my PC's and two laptops that have huffyuv and with all 4 of their media players. |
Quote:
|
|
Thanks Sanlyn, got it, will set to 288!(was confused, because the early/older guide for "capture in .avi using AIW card" clearly says to set huffyuv threshold to 480(?) NTSC
|
Yes, I know. I started out with that guide myself. For years I kept wondering why my captures looked so weird when I played them on other PC's. Then I read a post somewhere in which someone quoted something about threshold from an ancient html page for the early huffyuv. I never found that original document, just a lot of ancient posts in doom9.
Huffyuv and Lagarith setup are mentioned in section #3 of the more recent settings guide about halfway down the page in this post: http://www.digitalfaq.com/forum/vide...html#post45239. |
http://www.digitalfaq.com/forum/vide...vi-file-3.html Well, here it all is! I simply forgot about this, Due to many months of not doing any capturing. When I recently restored my XP Capture PC back to 6/7/2015 state, it was back to wrong huffyuv settings all over again!..I had a vague memory of this, but no way to check settings that worked due to restore. Will set huffyuv again as it should be, make sure ATI MMC records properly, then create a New restore point!..Will make separate post later, about why ATI MMC was not recording, and was freezing when hitting the Record button recently.
|
I've removed that outdated Huffyuv configuration info from the guide. I'm really looking forward to our new site, as then I can proceed to add new guides and make some much-needed changes/updates.
|
Quote:
Trial and error using virtual dub as a player driven by a hunch about the threshold settings? Thanks in advancefor making me smarter. |
Quote:
Actually, it was from this parallel topic: http://www.digitalfaq.com/forum/vide...g-problem.html Maybe even some good guessing/experience? I've never come across that. At least, I don't remember it. Way back when, when the guide was written, players didn't hate the threshold change. At some point, I changed my method to just leaving it default. I'm really not sure why anymore. It was a good catch on his part. |
Quote:
Quote:
As far as guessing goes, only 4 are possible for huffyuv settings: 240, 288, 480, and 576. Setting my own huffyuv to 240 or 288 didn't solve the problem. Setting it to 480 or 576 resulted in proper playback -- but I'd hesitate to guess that someone using NTSC capture would set a PAL threshold of 576 lines. Determining interlace/noninterlace is iffy with MediaInfo and even more iffy with the obsolete (but often useful) GSpot. MediaInfo will often report telecined video as interlaced or progressive, but true telecine is some of both. A more foolproof way is to learn to do it yourself, first-hand and visually, with Neuron2's old html web page which has been resurrected, zipped, and posted just a few weeks ago, here: Neuron2_How To Analyze Video Frame Structure.zip. |
Ahh-Such a Tangled Web We Weave!..Sanlyn was correct (of Course)..Fixed!..All I had to do was change huffyuv Configure setting to 288 threshhold (from 480?) in ATI MMC PVR record setup! Apparently thats the setting I had for a few years, getting successful capture/transfer ,avi before recently resetting my XP CapPC back to 2015 state, which had 480 threshold setting!..:D...well,tried to upload successful 640MB .avi, but "connection was reset, try again later" anyway :salute:
|
Meant to say "Such a tangled Web "I" weave"!!..Anyway thanks for all the help! Now must remember to set New restore point on cap PC while everything is working correctly!!
|
Site design, images and content © 2002-2026 The Digital FAQ, www.digitalFAQ.com
Forum Software by vBulletin · Copyright © 2026 Jelsoft Enterprises Ltd.