View Full Version : Crashbug (exception on unload) hopefully fixed
sh0dan
19th February 2003, 22:25
Yeah - it's not uncommon. For experiments sake I'll remove the "frame 0" test - I'm not sure if this will result in unexplained crashes - but disabling it until the next beta would be helpful!
I'll make some noise, when a test version is ready!
Edit: Got it to compile - Removing it seems to fix a "could not decompress frame 0" i have on RAW RGB24 AVI's.
WarpEnterprises
20th February 2003, 08:18
My version is the latest 2.0x.
But when I understand you correctly it's independent of 2.0 / 2.5 ?
Can you please explain a little more detailed where the error origins?
And why can the error only be seen every second call (ie refresh in vdub-mod) ?
sh0dan
20th February 2003, 10:42
Honestly I have no idea. The stupic thing about this is that I can only see the results of the changes, not the causes - Now I know why Avery swears so much! ;) (quote from Ben RG - now it also gives meaning to me ;-)
sh0dan
20th February 2003, 12:31
ok - I think I actually have a "fix-candidate" - without disabling the current code.
Some debugging revealed a potentially uninitialized variable being checked.
Again - I'll make some noise when a binary is ready.
(I'll merge the changes down into 2.0 branch also)
sh0dan
20th February 2003, 15:05
There is a Release Candidate for 2.08 on the CVS page.
Give me a go, and it'll be released ;)
sh0dan
21st February 2003, 13:08
@WE / hakko: How's your test going?
WarpEnterprises
21st February 2003, 14:07
@sh0dan:
Sorry, nothing tested yet (weekend is coming :) )
1) Do I see it right that the bugfix is only in your compile and the MAIN CVS branch which now is the 2.5branch ?
2) It seems that now is the time to officially stop adding functionality to 2.0, only bugfixing (i.e. no Turn, ...) . Do you agree?
sh0dan
21st February 2003, 14:16
2.0 has been updated:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/avisynth2/avisynth/source.cpp?only_with_tag=AviSynth-2_0
Don't know why it isn't shown correctly if sorted by date.
New features are not put into 2.0 - maintenance only! It has been so since 2.5 development started.
hakko504
21st February 2003, 14:19
Equally bad news here: haven't captured anything since before christmas - and about a month ago my Win98 gave me a BSOD and the message 'Please reinstall windows' so I defenestrated Win98 and installed Win2k instead. And just about a week later I got a DVD-R burner and I've been busy learning that one so far. And even worse: I'm proably going to work out of town for the rest of the spring, meaning my time for capturing/video encoding will be extremely limited in any case until after summer. You'll have to work this one out together with WarpE.
WarpEnterprises
24th February 2003, 08:33
Silly error this is. I wanted to test it with the new version, but couldn't reproduce it with the old one before (same source, script but did some of the usual install,... on the PC).
Anyhow the new version worked OK.
(only the installer seems to be buggy in associating AVS to notepad - it got ass. to WinZip, running it twice and it was ass. to Notepad again).
matrix
25th February 2003, 01:42
Need more reports?
Here it goes.
I had problems all the time with all releases after 2.05 including that. The usual error was 'could not decompress frame 0'
I downloaded a few days ago the release candidate, and it works beautiful now.
Just like 2.03, which is what I used up untill now, plus the extra features.
I'm happy with it.:D
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.