-
Notifications
You must be signed in to change notification settings - Fork 125
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
faxing with T.85 compression cuts bottom #25
Comments
Neither of those PDF files look quite right. There seems to be one pixel row missing from the longer one, and one character row missing from the shorter one. If there is a problem in spandsp it must be provoked by something specific in this particular image, as most pages transfer accurately. Can I get a source image file and the related received files using the different compression schemes? |
This is the original. |
The problem with fax00000073.pdf lacking the last pixel row is also present in a4_p.pdf, so it seems we can ignore that. \ If I extract the TIFF images from fax00000073.pdf and fax00000074.pdf they are not sendable as FAXes, because their resolution is set to 72dpi by 72dpi for some reason. If I edit the files to have a proper FAX resolution I can send the images between 2 instances of spandsp, using T.85 L0 compression, and the result looks OK. I tried this with an audio connection and with a T.38 connection. I did not use Freeswitch. I did the tests using my testbench for spandsp. I wonder if something in Freeswitch causes the file to be closed before the last part is written when T.85 L0 is used? |
Hi char11, I'm facing the issue same as you now. Could you please tell me your solution after that if you had already resolved? |
Faxing from freeswitch to freeswitch with ECM on and T.85 L0 compression cuts bottom. With T.6 or ECM off and T.4 everything is ok.
fax00000073.pdf
fax00000074.pdf
The text was updated successfully, but these errors were encountered: