When I'm trying to convert a jpg image to pcl image using the following command line,
"PATH\bin\convert.exe" -sample 454x157 -density 300x300 "PATH\images\02000001_CBerger.jpg" "PATH\images\pcl\02000001_CBerger_453x156_c.pcl"
I have a crash report:
I'm currently using the latest 6.4.3.7... and it worked with 6.3.6 version.
Do you have any idea?
regards
Thierry PARET
Crash converting a JPG to a PCL
Re: Crash converting a JPG to a PCL
Can you post a URL to your image so we can download it and reproduce the problem. We tried a number of our images and they converted to PCL without complaint.
Re: Crash converting a JPG to a PCL
Sure...
You can take it from http://thierry.paret.free.fr/02000001_CBerger.jpg.
Let me know if you have any problems to get it?
regards,
Thierry
You can take it from http://thierry.paret.free.fr/02000001_CBerger.jpg.
Let me know if you have any problems to get it?
regards,
Thierry
Re: Crash converting a JPG to a PCL
We ran your command against the image you posted with ImageMagick 6.4.3-10, the latest release, and it completed without complaint. See if 6.4.3-10 works for you.
Re: Crash converting a JPG to a PCL
Oups Sorry I forgot to mention I was using the option "-type Bilevel"...
I need to use this setting to create black or white pcl for printers which are not supporting color.
the command is:
"PATH\bin\convert.exe" -type Bilevel -resize 454x157 -density 300x300 "PATH\images\02000001_CBerger.jpg" "PATH\images\pcl\02000001_CBerger_453x156_c.pcl"
Hope you will be able to reproduce now with the real command line.
Sorry again
regards,
Thierry
I need to use this setting to create black or white pcl for printers which are not supporting color.
the command is:
"PATH\bin\convert.exe" -type Bilevel -resize 454x157 -density 300x300 "PATH\images\02000001_CBerger.jpg" "PATH\images\pcl\02000001_CBerger_453x156_c.pcl"
Hope you will be able to reproduce now with the real command line.
Sorry again
regards,
Thierry
Re: Crash converting a JPG to a PCL
We can reproduce the problem you posted about and will have a fix for it in the Subversion trunk by sometime tomorrow. The patch will also be available in the next point release in a week or two. Thanks.