Re: fax receiving in wrong page layout

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 16.05.2012 09:39, schrieb Tobias Powalowski:
> Am 15.05.2012 16:07, schrieb Karsten Keil:
>> OK you can start the daemon with -k, the then temporary files
>> and directories are not deleted (default in /tmp/). Then you will
>> also see the .tif file from spandsp).
>> 
>> The mISDNcapid flow is on receive: raw Bchannel data is piped to
>> spandsp, spandsp does everything and creates a tiff file,
>> depending which format CAPI did request (SFF or TIFF), it
>> transform the tiff file to SFF (default) or it send the TIFF data
>> directly via DATA_B3_IND to the application.
>> 
>> So the bug could be in SPANDSP or in the SFF transformation
>> (most likely here).
>> 
>> This week I'm on a business trip, so I can not test it. But I
>> think now that it is tracked down to fine/standard issue I maybe 
>> can reproduce it in my lab later.
>> 
> Hi here the result of my tests: - spandsp-0.0.5 is not compatible,
> build error on misdnuser - spandsp-0.0.6pre{18,19,20} work as
> attached in normal mode - spandsp-0.0.6_snapshots>=20120328 are not
> receiving anything, but send report is printed with success.
> 
> Tiff files attached, the send and received one from /tmp looks imho
> ok but the transformed one from hylafax/recvq/ is wrong.
> 

Hopefully fixed now. The SFF generation had a wrong limit for the
decision about high/low vertical resolution.

Karsten

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.16 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAk+7+K0ACgkQo5VVC52CNcS3IgCbBlsoW7Pvy11v1+7UKlJDsJXA
iG8An2zmHceRcgBnfppRZTknrhUXka+w
=rap6
-----END PGP SIGNATURE-----