Hello, Happy new year, and once again thank you for avifile, wich enable modern video software to Linux.
I have some remark about the global architecture of avifile. It seems that libavifile contains two main components : - stuff related to avi file format, and codec management - other... The "other" part seems to need graphical components, like Xv, DGA (for playing video I suppose ?) In my mind it has nothing to do with avi file format. But it is not a real problem . The real problem is that it is not possible to build an application using avifile without X-Window and heavy libraries. For example a little program using avifile can't be linked or can't run without X-Window. So it is possible to cut libavifile in two libraries, one for avi file and codec management, and another for graphical purpose ? I have a second remarks : I noticed that each time I construct an IAviReadFile object a new process (or thread ?) is launched. Then the signal management seems to be broken : I noticed strange behaviour when I tried to catch SIGINT for example. I suppose this way to do take advantage of multi-processor coputers, but Is it possible to avoid this behaviour, I would prefer to manage multi process myself in certain cases. Best regards, Pierre Hebert. _______________________________________________ Avifile mailing list [EMAIL PROTECTED] http://prak.org/mailman/listinfo/avifile
