View Full Version : Dev-Api-4 Testing
PowerMacG4
9th November 2003, 01:49
I cannot find any precompiled binaries online for testing purposes. Unfortunately when I compiled the XviD source tarball for today, the installed VFW binary doesn't appear in VirtualDub. This is very frustrating.
Why does no one publish Dev-Api-4 builds? Yes, the code may be unstable and not ready for production, but some of us enjoy fiddling around with new shiny builds, but don't have the time to figure out why our own builds arn't working (I followed the XviD build guide FAQ, and it built without error). If there are any tips you can give me to get my build to work, (yes, I installed it by using the INF file, and xvid.dll and xvid.ax are both in C:\WINDOWS\system32.. and registered) that would be great.
I just wanted to say that the shunning of public builds would only hurt XviD development, not help it. But if that is what the developers want, then so be it.
PowerMacG4
9th November 2003, 02:25
I finally got my xvid_20031109 build to be detected by VirtualDub (I was doing a Debug build of everything, not release), but I see none of the coveted dev-api-4 vfw features.
Is the XviD CVS Tarball different in some way? Is there some secret repository where I can get the updated vfw sources?
BoNz1
9th November 2003, 02:32
Are you just downloading the nightly tarball? Reason I ask is I don't think it is dev-api-4, I think it is 3. If you want 4 then get tortoisecvs and enter this in commandline cvs -d:pserver:anonymous@cvs.xvid.org:/xvid co -R -r dev-api-4 xvidcore Then go to xvidcore/build/win32 and open xvidcore.dsw and then build the libxvidcore.lib in win32 release. Then open up the vfw project file and build it in w32 release and then click on the ini and go to install and you are done. It is similar for the directshow. This is all you have to do the directshow and vfw are all including in xvidcore in api-4.
PowerMacG4
9th November 2003, 02:57
Oh, I did not realize the daily CVS Tarball was Dev-API-3... That makes much more sense now.
Ugh, TortoiseCVS requires a restart... *sigh*
BoNz1
9th November 2003, 03:30
Yup, you could try wincvs too, but IMO tortoisecvs is by far the best.
PowerMacG4
9th November 2003, 03:49
TortoiseCVS messed with my explorer shell extensions and added the annoying green/red/'?' file icon indicator. I cannot find any way to disable this other than uninstalling. Any options I am unaware of?
And by the way, I now have a successful Dev-API-4 build! :)
I hope the VFW changes by the time of release, because the new..'advanced' design really sucks in my opinion.
If you are interested in doing the same, I suggest you read:
http://www.xvid.org/modules.php?op=modload&name=phpBB2&file=viewtopic&t=1605
I know this link will probably be removed, but if you have trouble compiling it yourself (as I did) but are still interested in fiddling around NOLINK is your ticket. THIS IS NOT AN OFFICIAL, OR EVEN SEMI-OFFICIAL RELEASE IN ANY WAY. Do NOT use this for video archival! Use a stable build for those purposes. Have fun :)
BoNz1
9th November 2003, 05:30
Sorry, I know of no way to disable tortoisecvs' annoying shell, but it should only appear with stuff you have checked out and nothing else so I don't find it too annoying. BTW if you don't like the extended vfw stuff go into advanced options and then to debug and there is a checkbox that says display encoding status, uncheck it. Other than that I have no objections to the design, I suppose some might say it is a little bulky.
Koepi
9th November 2003, 09:14
If you'd follow our discussions you'd know that the main developers don't think dev-api-4 is ready for public testing.
I.e. will you give the necessary support to use it? I don't think so. Don't put up any binary of dev-api-4 yet. You'll get it if it's about usable.
Please respect the developers wishes.
Koepi
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.