Hi, > > yesterday I updated to avifile-0.7.7-20020523 and experienced several > > bugs. > > > > 1.) The open-buttons from the graphical surface don't work, so I have to > > using > > this is strange - it shouldn't be a problem
I forgot to write that the other buttons work fine. > > > 2.) When using some VideoCodecs, a lot of lines with pp xx (where xx are > > numbers, e.g. 10, 20, 30, ...) are written to the shell, this includes > > for example Divx5.0 (the linux Divx5.0). > > Known issue - you may dissable autoquality and set the hight mode > you could use without drops - you may also select different decoder > (i.e. ffdshow, Win32DS) > Or you may try to ask Eugene (are you still here ??) for update. I guess only a forgotten printf debug line causes it, so I thought its not difficult to fix it (when you have an idea where to find this line). Well, perhaps I'll try to find this line myself (when I find some time during the weekend). > > > 3.) Avicap crashes when I try to select the codec with this message: > > > > <Win32 plugin> : Win32 LoadLibrary failed to load: btvvc32.drv, > > /usr/lib/win32/btvvc32.drv, /usr/local/lib/win32/btvvc32.drv > > You may remove win32 plugin - I know there are > some drivers which makes this problems - you may remove them > from /usr/lib/win32 - usually IntelVideo codecs (indeo) are the elementar > source of these troubles - so try to move them away if you don't need them > - they sometimes works for recording too - but these are just limited > cases... Hmm strange, I'm using avicap for more than a year now, but I've never seen this error-message before. > > 4.) I have a video here, where only a green screen is shown with several > > codecs (for example with OpenDivx3.11), but for example the Win32 Divx4.0 > > DirectShow codec whows it fine. I have attached a small example (I hope > > all of you excuse sending 24 kb). > > This is quite normal - it depends on the quality of decoders - sometimes > you have to check several codecs before you find the best one - general > advice is - use ffmpeg in this cases - it should be the best one of them... Isn't there a way to detect that the codec doesn't work properly and so another codec is tried automatically? Best regards, Bernd _______________________________________________ Avifile mailing list [EMAIL PROTECTED] http://prak.org/mailman/listinfo/avifile
