[sane-devel] PNM Driver problem scanimage (sane-backends) 1.0.22; backend version 1.0.22

2012-11-02 Thread Stef
On 02/11/2012 20:20, Alejandro Imass wrote: > I think I solved it, and it has to do with the maxlen param on the > read(). If I use (0) it fails but if I use 32768 it works. On other > scanners the 0 is equivalent to the maxlength but in the PNM it seems > to need to be explicit. > Hello,

[sane-devel] PNM Driver problem scanimage (sane-backends) 1.0.22; backend version 1.0.22

2012-11-02 Thread Alejandro Imass
OK. We thought that 0 was equivalent to max length on that arch. On Fri, Nov 2, 2012 at 5:28 PM, Stef wrote: > On 02/11/2012 20:20, Alejandro Imass wrote: >> >> I think I solved it, and it has to do with the maxlen param on the >> read(). If I use (0) it fails but if I use 32768 it works. On othe

[sane-devel] PNM Driver problem scanimage (sane-backends) 1.0.22; backend version 1.0.22

2012-11-02 Thread m. allan noah
What happens if you call sane_get_parameters in your perl code, after sane_start? allan On Fri, Nov 2, 2012 at 3:01 PM, Alejandro Imass wrote: > On Fri, Nov 2, 2012 at 1:04 PM, m. allan noah wrote: >> Can you try to get some debug logs of the backend, to compare the two >> programs? >> >> SANE

[sane-devel] PNM Driver problem scanimage (sane-backends) 1.0.22; backend version 1.0.22

2012-11-02 Thread Alejandro Imass
I think I solved it, and it has to do with the maxlen param on the read(). If I use (0) it fails but if I use 32768 it works. On other scanners the 0 is equivalent to the maxlength but in the PNM it seems to need to be explicit. -- Alejandro Imass On Fri, Nov 2, 2012 at 3:01 PM, Alejandro Imass

[sane-devel] PNM Driver problem scanimage (sane-backends) 1.0.22; backend version 1.0.22

2012-11-02 Thread Alejandro Imass
On Fri, Nov 2, 2012 at 1:04 PM, m. allan noah wrote: > Can you try to get some debug logs of the backend, to compare the two > programs? > > SANE_DEBUG_PNM=255 scanimage ... 2> scanimage.log > SANE_DEBUG_PNM=255 perlprog ... 2> perlprog.log > > Maybe the perl code needs an additional call somewhe

[sane-devel] PNM Driver problem scanimage (sane-backends) 1.0.22; backend version 1.0.22

2012-11-02 Thread Alejandro Imass
OK. I'm going to have to set-up a separate test program for the Perl part because the calls are embedded in some complex code. Will be back shortly... On Fri, Nov 2, 2012 at 1:04 PM, m. allan noah wrote: > Can you try to get some debug logs of the backend, to compare the two > programs? > > SANE

[sane-devel] PNM Driver problem scanimage (sane-backends) 1.0.22; backend version 1.0.22

2012-11-02 Thread m. allan noah
Can you try to get some debug logs of the backend, to compare the two programs? SANE_DEBUG_PNM=255 scanimage ... 2> scanimage.log SANE_DEBUG_PNM=255 perlprog ... 2> perlprog.log Maybe the perl code needs an additional call somewhere, or maybe there is a bug in the backend. allan On Fri, Nov 2,

[sane-devel] PNM Driver problem scanimage (sane-backends) 1.0.22; backend version 1.0.22

2012-11-02 Thread Alejandro Imass
Hello, I am wondring if something has changed in the API to the pnm driver. I'm running Sane 1.0.22 on Mac OS X and the command line scanimage works fine with the PNM driver at index 0 (pnm:0). But when I access it through the Sane.pm Perl interface to sane I get no data on the read() call. The