PDA

View Full Version : Annoying G-spot 2.21 bug


Swan
27th September 2003, 19:58
I capture video using a Canopus ADVC-100 (DV capturing device).
I edit the video in VirtualDub. I only do simple cuts, such as removing commercials from a file, or outputting a section of a larger file to a new file. What I do is very basic and I use DirectStreamCopy.

Recently I discovered what I believe is a bug in G-spot (v. 2.21). I'd like to hear if others can test and verify that they have the problem too. Or if it's a known bug.
When I open the captured (original) file in G-spot, under "stat", it reports that the "file length is correct".
But when I open the file I have edited and output using DirectStreamCopy in VirtualDub, G-spot claims the file has a "corrupt AVI header" and is likely not playable. The file plays just fine through Windows Media Player, and opens fine in Vegas Video and VirtualDub.

This only seems to happen on longer files. If I have, say, a one hour long avi file and edit out the commercials so that the exported avi is 45 minutes long, G-Spot will report the avi header as corrupt.
If I instead edit out ten minutes from the 1 hour file and export those ten minutes, the file will be reported as healthy by G-spot.

I don't think it's a VirtualDub problem, since G-spot says the same thing if I edit my original files with Vegas.
And I don't think it's the capturing software either, as I get the problem with files that I've captured using both Scenalyzer and Vegas 4.

Can anyone verify that they have this problem with G-spot too?