These comments refer to Tioga drivers, which is what
you appear to be making:
1. Because I had a lot of problems in the earlier OS versions
with various formats, I stick with kPMXRBGB_32 and just
throw away the bytes I don't need.
2. The PMJobStreamGetNextBand routine returns with a structure
describing the band. The structure doesn't have a width, but
widthInBytes = band.size / band.height
and
widthInPixels = widthInBytes * 8 / band.depth,
so the second line begins widthInBytes past the first line.
In my drivers, I extract the RGB info and toss the X values.
>> I have met a problem when I get 24 bit RGB data.
>> In the hp SamplePM, I set the kPMRequestedPixelFormatKey
>> as kPMRGB_24, the kPMRequiredBandHeightKey as 48*5,
>> the kPMConverterResHorizontalKey as 600, the
>> kPMConverterResVerticalKey as 600 in converterSetupTicket.
>> I printed document in A4 paper.
>> When debugging, I get the print data from the method
>> of TEnginePCL::PrintBand(). In the bandBuffer data,
>> the first line data is 24 bit RGB and it is correct.
>> But from the second line to the last line, the data
>> is 32 bit (kPMXRGB_32 pixel format) RGB data.
>> Why the second line data is 32 bit RGB data ??
>> And does the second line data begin from "bandBuffer
>> + bandWidth * 4" ? ( bandWidth = (pageWidth * 600) / 72)?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Printing mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/printing/email@hidden
This email sent to email@hidden
