Flyspray:: http://bugs.shaftnet.org/ Flyspray::CUPS Dyesub Backends: Recently edited tasks 2019-03-10T14:17:38Z FS#575: Investigate Sony B&W Thermal MedSci models http://bugs.shaftnet.org/index.php?do=details&task_id=575 2019-03-10T14:17:38Z Solomon Peachy UPD-897MD, UP-X898MD, and so forth the UP-D898MD appears to be superficially similar to the Mitsubishi models, complete with the 1280 pixel print head (maxing out at 1280x4000ish) and similar adjustment knobs. They may have the same engine under the hood, but they're not likely to be semi-compatible with the Mitsubishi models. UPD-897MD, UP-X898MD, and so forth

the UP-D898MD appears to be superficially similar to the Mitsubishi models, complete with the 1280 pixel print head (maxing out at 1280x4000ish) and similar adjustment knobs. They may have the same engine under the hood, but they're not likely to be semi-compatible with the Mitsubishi models.

]]>
FS#571: Check for error statuses in the Kodak 605 processing loops. http://bugs.shaftnet.org/index.php?do=details&task_id=571 2019-01-30T03:17:19Z Solomon Peachy We don't check any error codes at all.  In part because I don't know what's an error and what isn't.  With access to a printer this would be a lot easier.. We don't check any error codes at all.  In part because I don't know what's an error and what isn't.  With access to a printer this would be a lot easier..

]]>
FS#552: Write network backend for CPnP printers http://bugs.shaftnet.org/index.php?do=details&task_id=552 2019-01-30T01:01:59Z Solomon Peachy The 'selphy_go' code showed how to detect CPnP models and send JPGs over to be printed.. Using the CP900, I discovered how to send raw YMC data over CPnP.  This means we can write a native CPnP CUPS+Gutenprint backend for that model. Unfortunately we won't know if the newer selphyneo models support non-jpeg CPnP printing -- The Windows driver uses WSA/WSD and Macs appear to use AirPrint.  The only way to find out is to write it first. The 'selphy_go' code showed how to detect CPnP models and send JPGs over to be printed..

Using the CP900, I discovered how to send raw YMC data over CPnP.  This means we can write a native CPnP CUPS+Gutenprint backend for that model.

Unfortunately we won't know if the newer selphyneo models support non-jpeg CPnP printing -- The Windows driver uses WSA/WSD and Macs appear to use AirPrint.  The only way to find out is to write it first.

]]>
FS#540: Investigate Fuji ASK 2000/2500/4000 (aka Nidec Copal DPB-6000/7000/4000) http://bugs.shaftnet.org/index.php?do=details&task_id=540 2019-01-29T22:01:39Z Solomon Peachy They are all related; The 4000 is an 8" version, and the 2000 is an older, slower version of the 2500, both 6" models.   All are rebadged versions of Nidec Copal printers -- ASK4000 == DPB-4000C1, ASK2500 == DPB-7000, ASK2000 == DPB-6000 They are all related; The 4000 is an 8" version, and the 2000 is an older, slower version of the 2500, both 6" models.

 

All are rebadged versions of Nidec Copal printers -- ASK4000 == DPB-4000C1, ASK2500 == DPB-7000, ASK2000 == DPB-6000

]]>
FS#595: When trying to enumerate printers, don't block for a long time when one's busy http://bugs.shaftnet.org/index.php?do=details&task_id=595 2019-01-17T14:43:54Z Solomon Peachy This is a particular problem when we have more than one model of the same printer family attached, and one or more of them are busy doing something -- but we can't query the serial number when the printer is claimed. This may require a two pass approach -- first try to probe everything with minimal timeouts.  If we don't succeed in finding the one we want, re-try the probe with longer timeouts.  In both cases, we shouldn't report a failure until we finish walking the entire list. This is a particular problem when we have more than one model of the same printer family attached, and one or more of them are busy doing something -- but we can't query the serial number when the printer is claimed.

This may require a two pass approach -- first try to probe everything with minimal timeouts.  If we don't succeed in finding the one we want, re-try the probe with longer timeouts.  In both cases, we shouldn't report a failure until we finish walking the entire list.

]]>
FS#608: Make Gutenprint more cross-compile friendly http://bugs.shaftnet.org/index.php?do=details&task_id=608 2019-01-17T14:36:14Z Solomon Peachy The problem is that, at compile time, we rely on some host-compiled stuff to generate data files and whatnot. We need to compile the same stuff for the target. I wonder if it may be worth moving to a more unified Make environment.. The problem is that, at compile time, we rely on some host-compiled stuff to generate data files and whatnot. We need to compile the same stuff for the target.

I wonder if it may be worth moving to a more unified Make environment..

]]>
FS#603: Support using external LUT http://bugs.shaftnet.org/index.php?do=details&task_id=603 2018-12-16T01:23:59Z Solomon Peachy The official drivers come with a file called 'P95D.lut' that consists of a 16-byte header followed by 34 bytes of LUT that neatly fit into the "gamma" header.  I see two approaches: Add another gamma enumeration, for "external LUT" Have the backend read the file and fil the job at runtime Permanently store the file in the backend, fill job at runtime Have Gutenprint fill in the gamma table from hardcoded value Allow gutenprint's gamma table to be overridden. I'm thinking that pushing this into Gutenprint (hardcoded, but overridable via an option) is the right way to do this. The official drivers come with a file called 'P95D.lut' that consists of a 16-byte header followed by 34 bytes of LUT that neatly fit into the "gamma" header.  I see two approaches:

  1. Add another gamma enumeration, for "external LUT"
    • Have the backend read the file and fil the job at runtime
    • Permanently store the file in the backend, fill job at runtime
  2. Have Gutenprint fill in the gamma table from hardcoded value
  3. Allow gutenprint's gamma table to be overridden.

I'm thinking that pushing this into Gutenprint (hardcoded, but overridable via an option) is the right way to do this.

]]>
FS#539: Consolidate CW-01 and DNP backends http://bugs.shaftnet.org/index.php?do=details&task_id=539 2018-09-18T18:10:15Z Solomon Peachy There's a great deal of overlap; the main difference is the format of the print job. It may make sense to fold the CW-01 stuff into the DNP backend (including the spool format), but alternatively perhaps just a shared library? There's a great deal of overlap; the main difference is the format of the print job. It may make sense to fold the CW-01 stuff into the DNP backend (including the spool format), but alternatively perhaps just a shared library?

]]>
FS#550: Verify support for D707 http://bugs.shaftnet.org/index.php?do=details&task_id=550 2018-09-18T18:09:48Z Solomon Peachy Code's complete, but needs to be verified.   Code's complete, but needs to be verified.

 

]]>
FS#604: Use a simpler URI scheme http://bugs.shaftnet.org/index.php?do=details&task_id=604 2018-09-18T18:08:41Z Solomon Peachy Currently the URI scheme is a little convoluted:      prefix://iManufacturer/iModel?backend=XXX&serial=YYYY I'd like to move to something much simpler:      prefix://backend/serial Now that the core code returns a unique, per-model string that can be used to look up the backend, this is a far simpler approach to take.  We'll have to support the old scheme indefinitely though. Currently the URI scheme is a little convoluted:

     prefix://iManufacturer/iModel?backend=XXX&serial=YYYY

I'd like to move to something much simpler:

     prefix://backend/serial

Now that the core code returns a unique, per-model string that can be used to look up the backend, this is a far simpler approach to take.  We'll have to support the old scheme indefinitely though.

]]>