Billy Biggs wrote:
There are other reasons this might happen with the ccdecoder code. For one, the filter used is not very good, and we need to improve it. We had alot of problems originally with that code because it would screw up the multiple CC channels, and get confused by XDS, and not look in both fields, etc. The code was based on some stuff hacked together by Nathan Laredo.
I kind of got the vibe that it was a little hacked. I grafted on some code that adds timestamps, gathers it into X-minute chunks, and shuffles it into a mysql database. So my version is even more hacked now. ;>
http://tvtime.sourceforge.net/ In CVS we have an improved version of Nathan's code, with still some bugs, and an attempt at a compliant cc renderer. There is still alot of work to do though, but we do intend to implement rendering per the spec.
Is there value in attempting to add hooks to separate text extraction versus display and formatting?
As difficult as the positioning and formatting code might be to write, this is all stuff I throw away anyways in my application, and others might want to do the same.
-- Trevor Boicey, P. Eng. Ottawa, Canada, tboicey@xxxxxxx ICQ #17432933 http://www.brit.ca/~tboicey/ "Hey, this emergency exit is painted on!" - Lenny
