Flyspray:: Thu, 28 Jun 2018 19:03:05 +0000 Flyspray::CUPS Dyesub Backends: Recently edited tasks http://bugs.shaftnet.org/ 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.

]]>
http://bugs.shaftnet.org/index.php?do=details&task_id=603 http://bugs.shaftnet.org/index.php?do=details&task_id=603
FS#540: Investigate Fuji ASK 2000/2500/4000 (aka Nidec Copal DPB-6000/7000/4000) Solomon Peachy Wed, 26 Aug 2015 04:22:51 +0000 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

]]>
http://bugs.shaftnet.org/index.php?do=details&task_id=540 http://bugs.shaftnet.org/index.php?do=details&task_id=540
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?

]]>
http://bugs.shaftnet.org/index.php?do=details&task_id=539 http://bugs.shaftnet.org/index.php?do=details&task_id=539
FS#602: Support combining print jobs Solomon Peachy Fri, 15 Jun 2018 20:58:23 +0000 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.

]]>
http://bugs.shaftnet.org/index.php?do=details&task_id=602 http://bugs.shaftnet.org/index.php?do=details&task_id=602
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!

]]>
http://bugs.shaftnet.org/index.php?do=details&task_id=541 http://bugs.shaftnet.org/index.php?do=details&task_id=541
FS#558: Investigate new Sinfonia S3 (CHC-S2245) Solomon Peachy Thu, 22 Dec 2016 03:38:31 +0000 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.

]]>
http://bugs.shaftnet.org/index.php?do=details&task_id=558 http://bugs.shaftnet.org/index.php?do=details&task_id=558
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...

]]>
http://bugs.shaftnet.org/index.php?do=details&task_id=601 http://bugs.shaftnet.org/index.php?do=details&task_id=601
FS#550: Verify support for D707 Solomon Peachy Fri, 07 Oct 2016 02:03:18 +0000 Code's complete, but needs to be verified.

 

]]>
http://bugs.shaftnet.org/index.php?do=details&task_id=550 http://bugs.shaftnet.org/index.php?do=details&task_id=550
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.

]]>
http://bugs.shaftnet.org/index.php?do=details&task_id=600 http://bugs.shaftnet.org/index.php?do=details&task_id=600
FS#569: Figure out image processing algorithms for CP-98xx family Solomon Peachy Thu, 23 Mar 2017 04:06:21 +0000 They're an older-generation of the D70 family's.  Data tables are unfortunately embedded inside the drivers, which makes this a lot more challenging. Sigh.

(If nothing else, simply obtaining the RGB->YMC conversion/gamma tables would make the printers immediately useful..)

]]>
http://bugs.shaftnet.org/index.php?do=details&task_id=569 http://bugs.shaftnet.org/index.php?do=details&task_id=569