Hi,
I am currently maintaining the avicap part of avifile, so I'm responsible for
your problems.
On Wednesday 28 May 2003 15:21, Przemysław Bruski wrote:
> Hi,
>
> I'd like to report some problems I've encountered using/compiling avifile
> 0.7.37. My compiler version is gcc 2.95.4 20011002 (Debian prerelease).
>
> I use an "ancient" linux distribution - debian woody, which does not
> have the latest QT installed (I have qt 2.3.1) - this explains some of the
> problems I've run into. Short comments on the patch:
I have fixed some of your problem already in CVS - at least for Qt2.3.2
Ok, I might have to install and use an even older Qt to be on the safe side.
Kabi: how low should I go?
> avirec.cpp - avirec doesn't work since it doesn't supply the codec name
Fixed in cvs.
> v4lwindow.cpp - my QT doesn't have that sophisticated toString method :-(.
Fixed in cvs.
> Hope it's not a problem to use the default format.
> v4lwindow.h - I needed this - maybe the stdio.h got ifdef'ed away
I'll fix it.
> somewhere in the include tree main.cpp - I get a segfault when I try
> to compare a QString initialized with NULL with anything (while(!(res ||
> trans_path[i]=="")); )
Ok, it'll get fixed.
> Attached patch should apply cleanly on 0.7.37 - sorry, I am behind a
> firewall and don't have the access to latest CVS version.
Argl. Sorry to hear that.
> Unsolved problem:
>
> I also managed to cause a segfault (only once) in memcpy section of the
> following code in capproc.cpp
Never happend to me...
> The segfault appeared when I was exiting the avicap program, so this seems
> to be some kind of synchronization problem.
Any other ideas what might have caused the segfault, did you anything
different from what you done usually?
Or did you try to use the sdl/fs-renderer? (Which explains at the moment every
segfault when it get's used)
I should have disabled that before the release, my fault.
> Sorry, no full thread trace :-(
Were you just testing avicap (and avirec), or are you using avicap/avirec for
recordings?
Because at the moment there's only one single avicap/avirec user known to me,
which makes (beta-)testing on different computers or reporting bugs and
improving avicap at bit difficult, without user writing on this list ;-)
If you actually use avicap/avirec, I'm open for any bug reports or suggestions
etc
About the CVS/Firewall problem:
Is this a firewall you can configure/ask the admin to do it?
Cause, if you are an avicap/avirec user, I'd like you to help us with
developing, downloading the newest CVS and see if it still compiles and runs
etc
If you can't change the firewall *somewhere* there should be a 'nighly build'
of our cvs archive, that can be accessed per http.
Doesn't sourceforge to that automatically, or ...?
Else I could send you patches to 0.3.37, I'd really like to have a second
avicap/avirec user/tester ;-))
Alex
--
Alexander Rawass
mailto:[EMAIL PROTECTED] http://www.raw-ass.net
...but some day you'll be a STAR in somebody else's SKY...
_______________________________________________
Avifile mailing list
[EMAIL PROTECTED]
http://prak.org/mailman/listinfo/avifile
