Flyspray:: http://bugs.shaftnet.org/ Flyspray::CUPS Dyesub Backends: Recently opened tasks 2018-09-18T18:08:41Z 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.

]]>
FS#603: Support using external LUT http://bugs.shaftnet.org/index.php?do=details&task_id=603 2018-06-28T19:03:05Z 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#602: Support combining print jobs http://bugs.shaftnet.org/index.php?do=details&task_id=602 2018-06-17T17:57:58Z Solomon Peachy 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. 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.

]]>
FS#601: Figure out a way to add a generic test harness for file parsing http://bugs.shaftnet.org/index.php?do=details&task_id=601 2018-05-13T13:09:37Z Solomon Peachy Right now there's no way to parse the input files without the printer being attached first. Would require shimming libusb... 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 http://bugs.shaftnet.org/index.php?do=details&task_id=600 2018-04-28T21:53:04Z Solomon Peachy 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. 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#599: Enhance Magicard driver to allow for different options on the duplex side. http://bugs.shaftnet.org/index.php?do=details&task_id=599 2018-03-18T18:45:05Z Solomon Peachy 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. 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? http://bugs.shaftnet.org/index.php?do=details&task_id=597 2018-03-16T19:38:04Z Solomon Peachy 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.   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.

 

]]>
FS#596: Figure out if Citizen CW-02/OP900II are closer to CX or CY series http://bugs.shaftnet.org/index.php?do=details&task_id=596 2018-03-27T00:04:19Z Solomon Peachy ...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. ...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#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 2018-02-16T12:11:44Z 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#592: Investigate Sony UPCX1 http://bugs.shaftnet.org/index.php?do=details&task_id=592 2018-01-28T13:39:04Z Solomon Peachy 300 dpi, 4" or 5" wide media. Not sure if it uses sheet or roll media. 300 dpi, 4" or 5" wide media.

Not sure if it uses sheet or roll media.

]]>