View Full Version : VD 1.7.8: "Truncated or invalid compressed audio..."?
shae
11th June 2008, 16:16
Using VirtualDub 1.7.8 to open an AVI with AC3 I get the following message:
Truncated or invalid compressed audio format detected (18 bytes, should be 36). Attemping to fix.
VD 1.6.15 doesn't complain.
Any idea what's that mean?
(It's funny how VD's error/warning messages superficially seem detailed, but are always completely unclear. :)
setarip_old
11th June 2008, 20:46
Hi!Attemping to fix.And are you able to successfully continue?
shae
11th June 2008, 21:30
I can use the file seemingly fine. But I'm not sure what latent side effects it may have, or what it actually means, which makes me reluctant to use this version (like the warning about VBR MP3 and the associated potential desync).
setarip_old
11th June 2008, 23:16
what latent side effects it may have, or what it actually meansAlthough I'd speculate it's simply an "information notice" and is successfully processed, I'd suggest you check at VirtualDub-specific forums and blogs for specific information...
squid_80
12th June 2008, 03:48
Ignore it. It's common to get that message with AC3 since a lot of programs don't seem to know how to create a valid WAVEFORMATEX structure for it.
Usually when new warning dialogs are added to virtualdub it means the cause has been recognized/fixed. Using an older version because it doesn't show the warning is a bad idea - it doesn't show the warning because it doesn't know there's a problem.
(What the error message really means - the cbSize field was 18 when it should be 0).
shae
12th June 2008, 04:27
I'd suggest you check at VirtualDub-specific forums and blogs for specific information...Perhaps one day I'll have to register at the VDub forum, but it wasn't today. :)
Using an older version because it doesn't show the warning is a bad idea - it doesn't show the warning because it doesn't know there's a problem.It seemed to work okay so far, and who knows how the new one will "attempt to fix", particularly with those cryptic messages.
(What the error message really means - the cbSize field was 18 when it should be 0).Indeed it is. Too bad the error message wasn't something like "Audio strf.cbSize indicates 18 addition bytes available, but strf ends right after cbSize. Assuming cbSize of 0."
Why's WAVE_FORMAT_DVM used for AC3, BTW?
squid_80
12th June 2008, 05:31
I don't know. I've never been able to find any information on WAVE_FORMAT_DVM, I think 0x2000 might have been picked at random for wFormatTag by whoever first started using AC3 and it's just stuck ever since.
shae
12th June 2008, 16:14
Thanks.
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.