Legacy ImageMagick Discussions Archive

I've just started using the 16-bit functionality of a video encoder I'm testing out. Unfortunately, it looks like IM can't read the 16-bit files that it outputs. My command lines: convert -size 1280x1264 -depth 8 -sampling-factor 4:2:0 out.yuv out.png convert -size 1280x1264 -depth 16 -sampling ...

Thanks, I did miss that. I added it to my PyMagickWand set.

BTW, there's a problem in the morphology docs: ScaleGeometryKernelInfo doesn't have its signature shown, instead ScaleKernelInfo is listed twice.

I would like to use Morphology in my current project, there's some really powerful stuff in it. Is there a MagickWand interface to it yet? I suspect there's not, since I looked over the code. If not, can you post a short snippet demonstrating how to combine Wand and Core APIs without accidentally ...

In this case, the Q8 version would be better than the Q16, since it'll halve the memory and some of the processing required. (Everything is natively stored in expanded 8- or 16-bit in memory, even if it's only 1-bit packed on disk.) You might have to use some form of partitioning, but it would be ...

Many zooms in and out will always give you distortion. That's just how it works. Why on earth would you expect it to look good when you throw away 50-90% of the information and then try to regenerate it with an algorithm, 25 times in a row? That's unrealistic. If you can perform any kind of ...

Thanks, the Hit/Miss & Pattern Matching methods on the page help solve another problem I was about to start experimenting with. Awesome!

I looked through the documentation and the filter list and didn't see this, so I'm wondering if it's something that's in IM or that someone has implemented it in script. Many image-editing programs have a local min/max filter that uses 3x3, 5x5 etc, and it's handy in some instances. (For instance ...

Well, it turns out that this was because there was another, older, set of IM dlls in my path. By dynamically setting the correct IM path to be FIRST instead of last, it turns out that it works fine. Sorry about that.

I'm loading an image, reading the properties, deskewing, and saving. I've extended sickos' PyMagickWand to work with the current version and I haven't had any trouble on previous IM-using projects up until I tried to use Deskew. Here's my results, please let me know if I'm doing something wrong: b ...

I'm on Win7 x64, using IM 6.6.1-6 2010-04-23 Q16 (no OpenMP). IM is one of the very few programs that can properly handle YCbCr in tiff. Some software (like XnView) converts the colors incorrectly, most won't open it at all. It's created with ffmpeg, which added the capability in 2007: ffmpeg -i ...

Not sure why, I created it in 7zip and can open it in regular zip software, but I uploaded another one created in windows explorer.

This image causes a crash, only in x64 windows compiles, not either 32-bit. If I get a chance I'll further debug it.

fmw42 wrote:-compose subtract will wrap. try using -compose minus. see http://www.imagemagick.org/Usage/compose/#subtract and http://www.imagemagick.org/Usage/compose/#minus

That's the intent. Check my command lines again - if I used minus, it'll destroy the recreated image.

I installed the 32-bit, Q8 version, and the bug does not appear. I was originally using the x64 Q16 version. I've just verified that the 32-bit Q16 version is incorrect as well. It looks like this line in composite.c: if (pixel < 0.0) pixel+=(QuantumRange+1.0); It looks like the floating point ...

Hello, I'm trying to use subtract for a research project. It mostly works quite well, the original image is reconstructed perfectly, but in a few spots huge errors manifest - where it seems to create a difference of 255 in one or more channels. In all other cases I've verified that the difference is ...