Re: was - P700 and P900 full channel support

Walker Blackwell <[email protected]>
Newsgroups gmane.linux.printing.gimp-print.devel
Message-ID <[email protected]>
Dear Michael, 


> I've already explained why "32 options" isn't a limitation for PAPPL-based printer applications, and given that IPP is used for ALL kinds of printing you really can't say that one particular kind of printing can't be done - it *is* done, on a regular basis.

How would you go about proposing to use PAPPL in this context? Let’s say we want to use a different ink in the P900 printer (something commonly done in it’s older brethren 3880s, P800s, etc) and need to send non RGB data in order to do that. 

Epson does not share ESCP APIs with the open source community even though they use Linux and a slew of other FOSS to run their machines. Are you saying we can use IPP in this case? If we don’t know the targets and slots to hit with IPP how can we use it? They aren’t broadcast by the printer.

> 
> (and if we are being real here, most printed T-shirt stores use iron-transfer with standard inks for photos and screen printing for simpler/stock N-color designs)

I can tell you from first hand experience, that the industry is only slowly moving away from trans film towards Direct To Film inks but these require white still. A majority of small outfits are still silk screen and are forced to use the 1430 platform. A working 1430 goes upwards of 2grand per printer now where it used to cost $350 new.

best
Walker


> 
> 
>> In a lot of ways, I'm more concerned with these exotic uses than with day-to-day printing,
>> especially with IPP Everywhere and driverless printers.  These are niche markets, but they're
>> underserved and as we're not a business we're in a good position to support these use cases.
>> 
>>>> On Nov 2, 2021, at 8:22 AM, Michael Sweet via Gimp-print-devel <[email protected]> wrote:
>>>> 
>>>> FWIW, the P900 is an AirPrint printer, which means you should be able to use it out of the box without drivers using CUPS' IPP Everywhere support.  And it should support both sRGB and AdobeRGB like the P800...
>>>> 
>>>> 
>>>>> On Nov 2, 2021, at 8:06 AM, Walker Blackwell <[email protected]> wrote:
>>>>> 
>>>>> I just got a P900 in-house. I gotta boot a linux machine and start cracking. . .
>>>>> 
>>>>> I’m going to assume the P900 requirements are pretty close to the P800 (2 picoliter SureColor head though so maybe close to P600) but won’t know for sure until I get at it.
>>>>> 
>>>>> Best,
>>>>> Walker
>>>>> 
>>>>> 
>>>>>> On Nov 2, 2021, at 3:00 AM, Oliver Kowalke <[email protected]> wrote:
>>>>>> 
>>>>>> I checked out the git repo (branch master) and I started reading "The Developer’s Guide to Gutenprint".
>>>>>> Unfortunately I can not find the printers.xml as mentioned in the guide - instead ./src/xml/printers/escp2.xml contains the Epson models. Is this the correct file? Maybe the guide is not up-to-date?
>>>>>> 
>>>>>> In ./src/xml/printers/escp2.xml the SC-P700 and SC-P900 is not listed. Does this mean that both models are not supported yet or is it the wrong file?
>>>>>> 
>>>>>> 
>>>>>> Am Mo., 1. Nov. 2021 um 23:47 Uhr schrieb Robert Krawitz <[email protected]>:
>>>>>> On 11/1/21 1:29 AM, Oliver Kowalke wrote:
>>>>>>> 
>>>>>>>  It should be possible to support this, other than the violet channel.  We could support the violet
>>>>>>>  channel for raw printing (i. e. the user has to do the separations), but actually supporting the
>>>>>>>  violet ink for normal printing would be a fair bit of tuning work and would need to be hands-on.  If
>>>>>>>  you're interested in doing this, be prepared to put a lot of time and a fair bit of consumables
>>>>>>>  into it.
>>>>>>> 
>>>>>>>  The first thing to do would be to look at src/xml/escp2/inks/cmykrb.xml in the Gutenprint source
>>>>>>>  tree to see an example of what we did for the R1800 and R800, which is CMYK+red+blue (which is
>>>>>>>  actually closer to purple, but Epson calls it blue).  The most non-standard part of this is the
>>>>>>>  <Curves> section, which is a set of transfer curves for each ink channel by hue, starting with
>>>>>>>  blue=0.  I always tested these by printing a rainbow sweep pattern and trying to get as good of a
>>>>>>>  match as I could with ordinary CMY(K).
>>>>>>> 
>>>>>>>  My thought about this is that we should at least at first only support the violet ink in raw mode,
>>>>>>>  as effectively a spot color.
>>>>>>> 
>>>>>>> Your description applies to the violett channel?!
>>>>>>> Because I'm new to print driver development I'd like to start with supporting the matte black
>>>>>>> channel. At least I think it should be easier, right?
>>>>>>> What  would be your advice to start?
>>>>>> 
>>>>>> The channel ID for matte black will probably be the same as it is on every other printer that uses
>>>>>> matte black.
>> 
>> 
>> _______________________________________________
>> Gimp-print-devel mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
> 
> ________________________
> Michael Sweet
> 
> 
> 
> 
> 
> _______________________________________________
> Gimp-print-devel mailing list
> [email protected] <mailto:[email protected]>
> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel <https://lists.sourceforge.net/lists/listinfo/gimp-print-devel>

_______________________________________________
Gimp-print-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.