| Category: | Bug report |
Priority: | High |
Status: | New |
| Project: | Severity: | Block |
Resolution: | Open |
|
| Component: | Reproducibility: | Always |
Assigned to: |
Hi,
When using an expression that returns a Java.awt.Image instead of an URL, the quality becomes extremely poor.
This is due to, as far as I can tell, a heavy jpeg (or jpeg style) compression that is done after receiving the Java.awt.Image from the expression and before printing to a specified format.
I triple checked the result for the scaling method we use (even rewrote it to be sure); I am the author of the original file (so I'm sure the original quality isn't at fault); and when feeding the original file as an url, it is perfectly clear and sharp, so your scaling methods are also not at fault.
Kind regards,
Maarten Van Coile
| Attachment | Size |
|---|---|
 report3264083304410197441.pdf | 61.65 KB |
 1.png | 430.36 KB |
v5.6.2
2 Comments:
Proof of concept: I forcibly feed JR a Java.awt.Image with a transparency layer thus forcing your renderer to to PNG. The resulting image shows no sign of jpeg-style compression artefacts.
Please include details on how the image is loaded as a java.awt.Image object, and the JRXML of the report where the image is displayed. We need a complete test case to understand what's happening.
Regards,
Lucian