Andreas Schulz wrote: > Stephen, > > After some time, I now had reason to check the Pronto code > conversion of congruity, just to discover an error in the code:
Thanks for the patch. I guess I missed that bit when I was reading the spec! I've checked in the fix to congruity SVN. > You just copy the burst/space times entered as Pronto hex code > to the IR signal that is passed to libconcord. > > However, in Pronto codes burst/space times are given in units of > the IR carrier cycle (which is provided by the second hex word, > in units of Pronto clock cycles), whereas libconcord expects > burst/space times in microseconds. > > So, what is missing is to multiply the Pronto duration values > by the IR carrier cycle (in microseconds). > > See attached patch for the correction, where I also introduced > the value PRONTO_CLOCK=4145146 (Hz) to replace the 'magic' > value of (1000000 / .241246). > > Andreas ------------------------------------------------------------------------------ The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your production scanning environment may not be a perfect world - but thanks to Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700 Series Scanner you'll get full speed at 300 dpi even with all image processing features enabled. http://p.sf.net/sfu/kodak-com _______________________________________________ concordance-devel mailing list concordance-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/concordance-devel
