ACM / DirectShow for WavPack?
Reply #24 – 2004-07-06 18:20:06
The fact is that my background is embedded systems and my native tongue fits very nicely in 94 ASCII characters, so unfortunately I am slower than most to pick up on UTF-8 and UNICODE, and I am actually proud of myself when I can make a dialog box work right. I have been concentrating on making the WavPack 4.0 format as efficient, robust and flexible as possible (with hardware decoding in mind), and am hoping that since it's completely open I might get some help on the areas that I don't have time to become expert in. You don't need to learn or understand unicode/UTF-8 to make your library not interfere with it. Just implement file I/O callback mechanisms instead of making your library take a char* filename. If you think that's problematic, provide alternate file open function that takes file path and uses its own standard implementation of the callback, just like libvorbis does. That's currently biggest issue with your code (as far as I've read into it) because making a non-broken DirectShow filter or foobar2000 component requires severe changes in your source, and not many people have time to do that (especially that your library may need updating later, so hacking would need to be re-applied). Implementing file I/O callback involves changes that are too big to for someone to just make them and send you a patch, since you should be the one who makes architectural/design decisions there.