Vegas 6b writes incorrect HuffYUV AVI

jbeale1 wrote on 8/11/2005, 2:35 PM
I'm using Vegas 6b to generate a 720x480 widescreen AVI using the lossless Huffyuv 2.1.1 codec. The source material is in the same HuffYUV format. Vegas appears to generate the AVI correctly and finish normally, but my playback applications (both VirtualDub and Windows Media Player) crash at the same point when playing the AVI. This point is about 48 seconds into the clip, during a crossfade. However I've done several crossfades before that point which played OK. I've used the HuffYUV 2.1.1 codec in my editing for several years without problems which is why I suspect something is going on with Vegas 6b. Anyone else had this problem?

GSpot Codec Information Appliance:
This is an invalid AVI file due to corruption of the data in the header. This is a serious problem, and this file is not likely to playable
Details: While processing chunk /RIFF:AVI, found bad length value 1073457668 at file offset 0x000107f8

VirtualDub 1.5.10 error message during playback:
An out-of-bounds memory access (access violation) occurred in module 'huffyuv'...
...while decompressing video frame 1435 with "Huffyuv v2.1.1" [biCompression=55594648] (VideoSource.cpp:1772).

Comments

B_JM wrote on 8/11/2005, 4:39 PM
ive never seen this problem and i use huffyuv a lot ...

try for hoots huffyuv 2,2 instead

B_JM wrote on 8/11/2005, 4:39 PM
i use 2.1.1 (patched version i think) myself though

john-beale wrote on 8/11/2005, 8:53 PM
I tried using the newer Huffyuv 2.2 codec with Vegas. I generated a new output AVI and it looked fine in the preview window while it was being generated. I then imported the huffyuv AVI back into Vegas,and looked at it- every frame of the file was corrupted. Here is a sample frame as exported from the huffyuv AVI in Vegas:
http://beale.best.vwh.net/misc/Vegas6b-huffyuv.jpg

Weird that no one else has seen this. Can it be bad hardware? But everything else has been working OK for some time. I also tried rendering the same video to regular DV AVI and also through DebugMode Frameserver to Canopus Procoder; both those renders worked fine.

GSpot Codec Information Appliance says this about the problem AVI file:
---------------------------------------------------------------------------
This is a valid AVI file.
The filesize is 3,954 MB (or 4,049,916 KB or 4,147,113,984 bytes).
Of that, roughly 3,368 MB (85%) is video data; the remaining 586 MB (15%) is audio. This file has 883 MB (or 904,563 KB or 926,273,024 bytes) of extra "garbage" at the end that is not part of the data yet is not marked as "junk" either. This is not usually a serious problem, however, and is unlikely to cause a problem.
DustBunny wrote on 8/11/2005, 10:04 PM
In your HuffYUV configuration, try checking on "Always suggest RGB format for output."
B_JM wrote on 8/11/2005, 10:22 PM
based on the picture posted -- that is not the problem (suggest RGB), though that does need to be checked ...

if it was me -- i would remove all huffyuv codecs from systems (and do a search) , remove and re-install vegas ... then install huffyuv again ..

i take it that this does not show up when rendering from any other program like virtualdub

trock wrote on 8/12/2005, 6:44 AM
I read somewhere (VideoHelp, I think) that Huffy 2.2. has problems and it's recommended to stick with 2.1.1.