Flyspray:: Flyspray::CUPS Dyesub Backends: Recently edited tasks http://bugs.shaftnet.org/ 2018-09-18T18:10:15Z FS#539: Consolidate CW-01 and DNP backends 2018-09-18T18:10:15Z 2015-08-26T04:12:50Z

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?

Solomon Peachy http://bugs.shaftnet.org/:539
FS#550: Verify support for D707 2018-09-18T18:09:48Z 2016-10-07T02:03:18Z

Code's complete, but needs to be verified.

 

Solomon Peachy http://bugs.shaftnet.org/:550
FS#604: Use a simpler URI scheme 2018-09-18T18:08:41Z 2018-08-14T20:25:58Z

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.

Solomon Peachy http://bugs.shaftnet.org/:604
FS#603: Support using external LUT 2018-06-28T19:03:05Z 2018-06-28T19:03:05Z

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.

Solomon Peachy http://bugs.shaftnet.org/:603
FS#540: Investigate Fuji ASK 2000/2500/4000 (aka Nidec Copal DPB-6000/7000/4000) 2018-06-19T00:25:26Z 2015-08-26T04:22:51Z

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

Solomon Peachy http://bugs.shaftnet.org/:540
FS#602: Support combining print jobs 2018-06-17T17:57:58Z 2018-06-15T20:58:23Z

As a way to prevent wasting media, when using 6x8" media, automagically combine consecutive 4x6" jobs to a single 8x6" print and submit that to the printer behind the scenes.

The D90 and Kodak 68xx do this automatically in the printer, and others (eg Mitsu D70 family) do this in the driver.

Extend the backend core to support this generically, and try to add specific support to printers/families that can use this feature.

Solomon Peachy http://bugs.shaftnet.org/:602
FS#541: Validate Mitsubishi CP-D90 support 2018-05-20T02:11:13Z 2016-04-28T22:41:05Z

It looks like it's an evolution of the D70 family, with one critical exception -- it appears as if the color/thermal compensation is performed in the printer instead of the driver!

Solomon Peachy http://bugs.shaftnet.org/:541
FS#558: Investigate new Sinfonia S3 (CHC-S2245) 2018-05-13T17:04:11Z 2016-12-22T03:38:31Z

Replacement for the S2145, it's main fature is high capacity (900 print) media.

https://www.sinfo-t.jp/eng/printer/chc_s2245.htm

Initial investigation implies it may require host-side image processing, not unlike the S6145.

Solomon Peachy http://bugs.shaftnet.org/:558
FS#601: Figure out a way to add a generic test harness for file parsing 2018-05-13T13:09:37Z 2018-05-10T02:14:19Z

Right now there's no way to parse the input files without the printer being attached first.

Would require shimming libusb...

Solomon Peachy http://bugs.shaftnet.org/:601
FS#600: Add support for CUPS Command files 2018-04-28T21:53:04Z 2018-04-27T15:48:17Z

CUPS defines a "command filter" that gives the ability to perform some actions and queries.

  • ReportLevels -- marker-levels and whatnot.  Highly useful.
  • ReportStatus -- Once we get unified reporting in place, will be handy.
  • AutoConfigure -- Allows the PPD defaults to be updated based on printer configuration.  (!!)
  • PrintSelfTestPage -- For printers that support it
  • [and others that don't matter]

There appears to be no way to distinguish betwen a command filter vs print filter via the cmdline or environment.  traditionally these are seperate executables that expect different input data.  I'd like to figure out a way to make the backends detect the command stream vs the normal backend data, and do it all in one executable.

Solomon Peachy http://bugs.shaftnet.org/:600