Hi, > I guess when XFree folks could agree on XVideo strings - we could > agree an this simple thing :) but we need more flexible and usable interface than Xv is for its purpose... (I miss V-sync and stride handling from Xv for example, not talking about deinterlacing and hw iDCT/MC)
so i still prefer 3 different code each designed/optimized for its purpose, than one common but limited one. > > yes, i think, and i don't understand where is the problem for you. > > win32 loader, acm and vfw api is already c, and now we have directshow > > in c too. the only thing to do is replacing :: by _ in calls to directshow > > api :) > > It's not that simple - I'll have to create also wrapper classes :) why? you have videodecoder.cpp etc already you don't have to touch them. just move them out of libwin32codec or move others (C code) to a subdir. or you mean DS_VideoDecoder.cpp ? shouldn't be a big bumm to do > I think I'll try to concentrate on this over the next weekend. ok > We have still few problems about configure for this package - > I guess this library doesn't have to be that much portable so > some simple configure script 'in the ffmpeg' style might be created > & used - but I would be probably the last person who would be doing > this :) (I've already spend a lot of time with current avifile configure.in) ok i think we can do that. pl just rewrote mplayer's configure script in a nice, modular way, so it's 5 min to construct a customized script for libwin32* stuff from it. just tell me what should be checked for. > > > Which is the thing I do not understand - you should become member of > > > Redhat, mandrake, slackware, debian or whateever other differenet distro > > > you like :) > > why? > > So you would be paying more attention to package maintainers :) ah :) especially in slackware :) A'rpi / Astral & ESP-team -- mailto:[EMAIL PROTECTED] http://esp-team.scene.hu _______________________________________________ Avifile mailing list [EMAIL PROTECTED] http://prak.org/mailman/listinfo/avifile
