From: Capt. S. *-J. <st...@3i...> - 2002-08-07 20:52:50
|
not sure how to handle the xanim dlopen situation, (in fact, I've never=20= looked at that code ;)) but, if the xanim wrapper opens the xanim codecs, then would it be=20 possible to treat it as a special case? Moving right along... I'm not sure on what the state of openqt's codec loader is, but I do=20 know that we're working on a rather handy little codec which will be=20 made available for OpenQT as an OQT codec. Now, our requirements are a single binary which can handle multiple=20 fourcc's (somewhere about... 40 or so ;)) So, essentially OpenQT needs to be able to enumerate its codecs, to find=20= out which fourccs can be handled by which codecs (ie use the term codec=20= to mean the actual .so and fourcc to mean the actual decoding function=20= which handles that fourcc etc) point is, from OQT's perspective that's how it should see it, just which=20= codec and what fourcc to tell it. Now, I can imagine that a tree such as the following should be able to be=20 constructed at launch time OpenQT 3ivx 3IV1 3IV2 DIV3 DIVX mp4v ... XAnim cvid rle8 ... OpenDivX DIVX DivX4 DIV3 DIVX JPEG jpeg mjpa mjpb So basically, OQT asks the OQT codecs for a list of fourccs they = support, Now, the 3ivx plugin would answer with its list of fourccs, but the=20 XAnim plugin would have to inspect/query and build a list of fourccs to=20= answer with. That's okay, the XAnim plugin knows how to query XAnim=20 plugins... (the idea being xanim decoders are actually not OpenQT codecs, they're=20= decoders which are used by the XAnim OQT decoder) etc etc etc for extra bonus points, add a Rehash() command to OpenQTs API to force=20= it to rescan its plugin directories and rebuild its codec list ;) Essentially, the filename shouldn't matter one whit, and in fact, only=20= serves to differentiate different codecs... ie OpenDivX.so is different=20= to DivX4.so -- This is only the beginning! Capt. Stux *-Jedi = mailto:st...@3i... 3ivx=AA is a registered international trademark. Really. **** DISCLAIMER **** "This e-mail and any attachments thereto may contain information which = is misleading and/or protected by vain legally positivistic rights and are supposedly intended for the sole use of the recipient(s) named above. = Any use of the information contained herein (including, but not limited to, reading it by accident, on the loo, or word of mouth in any form) by persons other than the designated recipient(s) is, um, well, prohibited. If you have received this e-mail in error, accident, humour, mischievous bcc, mailing list glitch, recursive bounce of a co-recipient, sendmail bug, yet another winsock worm, Claire Swire, or the sender just stuffed=20= up because your name was next to the proper one in his address book, please notify the sender either by telephone or by e-mail (yeah we know, as if you would, but then you'd be amazed, some people) and delete the = material from any computer. This means empty your Trash and Recycle Bin, of=20 course. And zero the data just in case. Do it six times so the feds can't get at it. Oh, and don't forget your RAM chips; take them out of your computer for at least a day so the transistors can reset. And for chrissake don't leave them in your freezer because we read on Slashdot how that can inhibit the degenerative process. Thank you for your cooperation." |