DAM 5.5 - ImageMagick image resizing issue
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎12-31-2011 02:59 PM
Just taking a look at the latest DAM 5.5 to see what's changed. Set-up was easy enough and the new interface and integration with DM look great. I installed the latest version of ImageMagick to check out image resizing (Medium and Thumbnail) and I had some unexpected results.
For example PNG files would resize properly and could be viewed (in DM client) on the View tab in Medium, Original, and Thumbnail sizes and the download button could be used to download each image. However, the download button (in the DAM client) will only download the Original size image regardless of the Download Size I choose in the dropdown. Interestingly, the URLs listed above the download area all work (if pasted into the browser).
On the other hand JPG images do not get resized at all - in any of the cases listed above. There are some error messages in the log (see below).
Have I missed some configuration or tuning?
Thanks, Bruce.
2011-12-30 22:57:08,412 ERROR [org.nuxeo.log4j.ThreadedStreamGobbler] stream.exe: unable to open module file `C:\ImageMagick\modules\coders\IM_MOD_RL_IMG_.dll': No such file or directory @ warning/module.c/GetMagickModulePath/683.
2011-12-31 09:58:10,770 ERROR [org.nuxeo.ecm.platform.picture.core.im.IMImageUtils] Resizing with ImageMagick failed
java.lang.IllegalArgumentException
at java.lang.ProcessImpl.<init>(ProcessImpl.java:181)
at java.lang.ProcessImpl.start(ProcessImpl.java:133)
at java.lang.ProcessBuilder.start(ProcessBuilder.java:1021)
at java.lang.Runtime.exec(Runtime.java:615)
at java.lang.Runtime.exec(Runtime.java:483)
at ...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-06-2012 10:37 AM
has anyone seen this issue??
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-09-2012 07:14 AM
This is a bug (looks like yet another path escaping issue caused by the backslashes used as filename separator under windows). Can you please open a jira issue and attach the full stacktraces to it?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-13-2012 01:09 AM
Reported in Jira (https
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎01-13-2012 01:19 AM
also reported https
