Re: [hylafax-users] Bad pixel count (meaning)

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

Michael Hallager wrote:
> Feb 26 08:15:52.36: [26453]: RECV/CQ: Bad 1D pixel count, row 125, got 1965, 
> expected 1728
> Feb 26 08:15:52.68: [26453]: RECV/CQ: Bad 1D pixel count, row 126, got 2336, 
> expected 1728
> Feb 26 08:15:53.00: [26453]: RECV/CQ: Bad 1D pixel count, row 127, got 1768, 
> expected 1728
> Feb 26 08:15:53.00: [26453]: RECV/CQ: Bad 1D pixel count, row 128, got 2739, 
> expected 1728
> Feb 26 08:15:53.32: [26453]: RECV/CQ: Bad 1D pixel count, row 129, got 3274, 
> expected 1728
> Feb 26 08:15:53.96: [26453]: RECV/CQ: Bad 1D pixel count, row 130, got 1820, 
> expected 1728
>
> The PDF sent to me is sometimes corrupted and unviewable, though I received a 
> fax today full of these errors and I could view the PDF.
>
> For some unknown reason these errors do not seem to appear on every session 
> with this machine, just around half.

These is how corrupt image data appears to the G3 decoder.  So you 
should only ever see this in non-ECM sessions.

At the end of every MH and MR image there will be an RTC which will also 
appear as "Bad pixel count" with a count of "0".  But you'll notice that 
it detects it later as RTC and adjusts the line count appropriately.

Thanks,

Lee.



____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*