View Full Version : Nic's 22/04/02 DSF Backword Compatibility
amirlsm
24th April 2002, 12:22
Nic's 22-04-2002 Xvid.dll produces code that in not backward compatible with older Xvid DSFs
1) Can anyone point out the benefits that the incompatible format has?
2) Can backward compatibility of the DSF be restored in future versions or is it preventing 100% MPEG-4 compatibility?
Amir
Ouch! I haven't heard anything about this....
Nothing's changed lately that could cause this, of which I am aware. Anyone else with similar experiences?
-h
chemmajik
24th April 2002, 13:01
I was going to mention it also but thought I was dreaming. Its effected the other builds too. I used to compare 4cc code changing, but its broken & turns green when using divx. It happened about a week ago... Right after the 14-16 build I think oops, I shoulda mentioned something like this sooner. It happened in whatever code that effected Nic's & the regular no post processing umaniac DSF.
rui
24th April 2002, 14:10
Well, i posted this some thread below:
This isn't related with mv hints+lumi, but i didn't wanted to open a new thread only for this, so i hope cult doesn't mind. Here goes:
I've tried a new build that uManiac has in his site, xvid.alpha.21.04.2002.1720, but when trying to play xvid clips encoded with prior builds, a error message appears, saying:
xvid.dll implements a newer api version; update your directshow filter
Then i tried to replace the xvid.ax that came with this build, with the xvid.ax that comes with Nic's and Koepi's builds (it's Nic' ds filter with post processing), but i get the same error, which i expected since Nic's ds filter is also prior to this new uManiac's build.
And then Koepi said this:
API version changed from 2.0 to 2.1.
Nic has to recompile his filter to make it work properly with that again...
Which Nic did, and all went well. I can play clips made with prior builds with no error.
amirlsm
24th April 2002, 14:32
Originally posted by rui
Which Nic did, and all went well. I can play clips made with prior builds with no error.
Right, but you can't play the new Xvid files on platforms with any of the old Xvid.ax... You have to upgrade your DSF.
Nothing wrong with updating the DSF, I just wonder if loosing backword compatibility is a good thing at this stage since none of the releases is yet 100% stable.
Amir
Right, but you can't play the new Xvid files on platforms with any of the old Xvid.ax... You have to upgrade your DSF.
This disturbs me greatly.
So, if I make an mpeg4 stream (any specific options?) with today's CVS, and try playing it through vfw with an old xvid.dll, it won't work?
If it's just dshow that can't play it, I'm not greatly concerned. If old builds can't play new bitstreams through vfw (via say VirtualDub), we have a big problem.
-h
amirlsm
24th April 2002, 15:15
Originally posted by -h
If it's just dshow that can't play it, I'm not greatly concerned. If old builds can't play new bitstreams through vfw (via say VirtualDub), we have a big problem.
I checkedit. It's only the DSF. vfw works fine with OLD dll for NEW files.
Amir
saVe
24th April 2002, 15:20
i opened the some very new files (build from 220402) in vdub, so no dsf is involved.
tried the following builds:
301101(must be one of the first ones) - no
120102 - no
200102 - no
270102 - yes
170302 - yes
so, except for the really old builds, everything seems to work just fine.
Nic
24th April 2002, 15:21
Sorry for joining this late....
Its because the API changed, I don't know exactly what did change....
When you try with old builds is the only error you get
"xvid.dll implements a newer api version; update your directshow filter"
If so then its because the DShow filter has to communicate with the XVID.DLL to decode...& cant because of the different API version.
-Nic
amirlsm
24th April 2002, 16:32
So I guess we shall all just upgrade to the latest build and close this thread.
Thanks,
Amir
vBulletin® v3.8.11, Copyright ©2000-2026, vBulletin Solutions Inc.