Flyspray:: Sun, 16 Dec 2018 01:23:59 +0000 Flyspray::CUPS Dyesub Backends: Recently closed tasks FS#603: Support using external LUT Solomon Peachy Thu, 28 Jun 2018 19:03:05 +0000 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 Solomon Peachy Wed, 26 Aug 2015 04:12:50 +0000 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 Solomon Peachy Fri, 07 Oct 2016 02:03:18 +0000 Code's complete, but needs to be verified.


FS#604: Use a simpler URI scheme Solomon Peachy Tue, 14 Aug 2018 20:25:58 +0000 Currently the URI scheme is a little convoluted:


I'd like to move to something much simpler:


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.

FS#541: Validate Mitsubishi CP-D90 support Solomon Peachy Thu, 28 Apr 2016 22:41:05 +0000 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!

FS#601: Figure out a way to add a generic test harness for file parsing Solomon Peachy Thu, 10 May 2018 02:14:19 +0000 Right now there's no way to parse the input files without the printer being attached first.

Would require shimming libusb...

FS#600: Add support for CUPS Command files Solomon Peachy Fri, 27 Apr 2018 15:48:17 +0000 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.

FS#596: Figure out if Citizen CW-02/OP900II are closer to CX or CY series Solomon Peachy Thu, 22 Feb 2018 19:35:06 +0000 ...or if they need their own designation in Gutenprint and selphy_print.

It looks like they don't map entirely cleanly to either for avialable print options, but the real question is the firmware version tests for features.

FS#599: Enhance Magicard driver to allow for different options on the duplex side. Solomon Peachy Sat, 10 Mar 2018 21:54:23 +0000 At minimum, the overcoat hole is different on front vs back (eg smartcard vs magstripe).

Magstripe probably only belongs on the back, smartcard on the front.

Holokote and holopatch likely need to be different too.

FS#597: Allow for aliases in backend names? Solomon Peachy Thu, 22 Feb 2018 19:40:13 +0000 That would allow us to present a 'modern' name for the backend but still provide backwards compatibility.

eg: dnpds40 -> dnp_citizen or mitsu9550 -> mitsu9xxx or mitsup95d->mitsu_p9x

Another approach would be to make things more fine-grained.