Legacy ImageMagick Discussions Archive

Wow, that was fast. Sometimes I can't believe the support we get from an open-source software product. In any case, reverting to freetype 2.3.12 made no difference, as I guess you'd know by now. ImageMagick 6.6.7 also does not appear to have this problem, so I can at least get the machine back into ...

MacOS 10.6.7 ruby 1.8.7 rmagick 2.13.1 ImageMagick 6.7.0-7 q8 freetype 2.4.5 I have a program that builds images based on data and other images. With certain fonts, above a certain image size, I'm getting a memory error in annotate. Memory allocation failed `No such file or directory' @ fatal/draw.c ...

To update, other .psd files from that client do work fine with watermark and dissolve. Apparently something with this specific image is causing this problem.

Jim

you should not be getting an error unless your psd file is corrupt. what do you get from identify -verbose on your psd file? % identify -verbose crest.psd Image: crest.psd Format: PSD (Adobe Photoshop bitmap) Class: DirectClass Geometry: 2032x2561+0+0 Resolution: 600x600 Print size: 3.38667x4.26833 ...

usually the first layer of the psd file is the image composed from merging all the layers, so just use it as image.psd[0] rather than image.psd composite -dissolve 20,100 crest.psd[0] bg.jpg dissolve_psd_20.jpg gives an error "composite: No match." I originally ran into this problem in a ruby ...

I was attempting to use the dissolve operator to do color watermarking and ran into an issue because my watermark image is a .psd file, apparently with 2 layers. If I run the command: convert crest.psd crest.png I get 2 files: crest-0.png crest-1.png As far as I can tell, these files are identical ...

I had a look at coders/pdf.c, and it appears the calculation for MediaBox and CropBox are correct. However, the values are still not what they should be. That means the values used in the calculation must not be correct. % convert -version Version: ImageMagick 6.5.1-0 2009-04-03 Q8 http://www ...

I haven't tested yet with 6.5.0-9, however, any anyone at ImageMagick tell me whether they are planning on addressing these issues at all? If not, I can create my own hack to set these values properly.

Thanks,

Jim

I'm getting an assertion failure when converting an image (jpg and png) to pdf.

Assertion failed: (image->blob->type != UndefinedStream), function WriteBlob, file magick/blob.c, line 3756.

I just tested with 6.5.0-8, and when creating a pdf, the mediabox and cropbox are being set to the size of the image in pixels, no conversions are being done at all now. These values need to be set to the size of the image in points, or pixels/dpi*72.

Jim

I also had noticed that the mediabox and cropbox were not being calculated correctly. However, the image I was using for testing had resolution specified in PixelsPerCentimeterResolution, and I had already run into a different problem so I didn't test further at that time to see if an image with ...

Can you tell me what version has this patch?

Thanks!

I looked at some files created by Photoshop, and only the MediaBox parameter was set. The MediaBox parameter was set to the size of the image at 72dpi. So for example, creating a PDF using Photoshop from an image 14400 x 11200 at 400 dpi, the MediaBox parameter is set to 2592 x 2016, and the CropBox ...

I'm writing the file from rmagick as a pdf, and while I realize the image is saved in the pdf in some kind of image format, the users claim the pdf is higher quality than when saved as png or jpg (the ruby program can save in any of the 3 formats. Also, I don't need a page size of "letter". This ...