Comments on: Content Aware Image Resizing: GPL Implementation http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/ Tue, 06 Jan 2009 08:19:36 +0000 http://wordpress.org/?v=2.6.1 By: Delia http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-119415 Delia Thu, 01 May 2008 21:07:16 +0000 http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-119415 Thanks for the code. The results that I’ve got were ok, not what I was expecting, but still ok. I am used to a resizing tool I found at reshade.com and the results I got with it were the best compared to other tools so I guess I got used to compare it to those results. But averaging the result I got on my computer they were ok, I’m just waiting for the better version. Anyway thanks for sharing. Thanks for the code. The results that I’ve got were ok, not what I was expecting, but still ok. I am used to a resizing tool I found at reshade.com and the results I got with it were the best compared to other tools so I guess I got used to compare it to those results. But averaging the result I got on my computer they were ok, I’m just waiting for the better version. Anyway thanks for sharing.

]]> By: Mathias Lux http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-52930 Mathias Lux Tue, 25 Sep 2007 06:52:41 +0000 http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-52930 I've resolved this one :) check out the new v3 ... I’ve resolved this one :) check out the new v3 …

]]> By: Mathias Lux http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-43435 Mathias Lux Thu, 06 Sep 2007 07:48:20 +0000 http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-43435 I just double re-checked (even debugged) and M is recalculated each time. Also the gradient image is updated each iteration. I think I'm stuck right here :) I just double re-checked (even debugged) and M is recalculated each time. Also the gradient image is updated each iteration. I think I’m stuck right here :)

]]> By: Peter http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-43152 Peter Wed, 05 Sep 2007 17:47:52 +0000 http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-43152 Hey Mathias, I don't think that's a problem, my code always takes the first one, too. I suspect the cause of those artifacts is that you do not recompute the seam cost map (called M in the paper) after each iteration of the algorithm. The paper is not very clear in that section, but I think you have to update the energy map e (since the derivatives change for the pixels near the seam you just removed) and then recompute the seam cost map. I could be wrong, though... Hey Mathias,

I don’t think that’s a problem, my code always takes the first one, too. I suspect the cause of those artifacts is that you do not recompute the seam cost map (called M in the paper) after each iteration of the algorithm. The paper is not very clear in that section, but I think you have to update the energy map e (since the derivatives change for the pixels near the seam you just removed) and then recompute the seam cost map. I could be wrong, though…

]]> By: Mathias Lux http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-43144 Mathias Lux Wed, 05 Sep 2007 17:01:37 +0000 http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-43144 hmm .. I think I know what the reason for these artifacts is: The selection of the seam for backtracking is the bad one in my opinion. I always start from left and take the first minimum value I encounter. I should take a random one. I'll try to fix this along with the sliders :-) thx for the report! hmm .. I think I know what the reason for these artifacts is: The selection of the seam for backtracking is the bad one in my opinion. I always start from left and take the first minimum value I encounter. I should take a random one.

I’ll try to fix this along with the sliders :-)

thx for the report!

]]> By: Peter http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-43099 Peter Wed, 05 Sep 2007 13:34:26 +0000 http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-43099 I've just tried you GUI tool, and I have found that, at least on my computer, it seems to produce artifacts in the image. I, too, have implemented the algorithm (in C++ though), and my results do not have those diagonal seam patterns. I think at some point my results looked similar though, but I can't really remember what the reason was. I suspect it may have something to do with the seam cost map. Here is a screen shot of our programs running side by side, both times resizing the identical coastline image from the paper to 250x250 pixels (I made a screen shot of the original image from the youtube video so I could compare my results): http://img409.imageshack.us/img409/6797/unbenanntxs5.png Great work though, it's cool to see someone is implementing the marking part of the paper. Keep it up, I'm looking forward to seeing what you come up with :) I’ve just tried you GUI tool, and I have found that, at least on my computer, it seems to produce artifacts in the image. I, too, have implemented the algorithm (in C++ though), and my results do not have those diagonal seam patterns. I think at some point my results looked similar though, but I can’t really remember what the reason was. I suspect it may have something to do with the seam cost map.

Here is a screen shot of our programs running side by side, both times resizing the identical coastline image from the paper to 250×250 pixels (I made a screen shot of the original image from the youtube video so I could compare my results):

http://img409.imageshack.us/img409/6797/unbenanntxs5.png

Great work though, it’s cool to see someone is implementing the marking part of the paper. Keep it up, I’m looking forward to seeing what you come up with :)

]]> By: Ahijado’s blog » Blog Archive » Adicto al “blogging”: 78% http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-42090 Ahijado’s blog » Blog Archive » Adicto al “blogging”: 78% Mon, 03 Sep 2007 07:01:38 +0000 http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-42090 [...] una noticia relativa a la implementación GPL del cambio de tamaño de una imagen “sin pérdida” de calidad, he visto una entrada sobre la adicción al blogging. En dicha entrada se enlaza a una dirección [...] [...] una noticia relativa a la implementación GPL del cambio de tamaño de una imagen “sin pérdida” de calidad, he visto una entrada sobre la adicción al blogging. En dicha entrada se enlaza a una dirección [...]

]]> By: Mathias Lux http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-42086 Mathias Lux Mon, 03 Sep 2007 06:44:31 +0000 http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-42086 Yeah I know, unfortunately I just did this for small images (e.g. 640x480). With bigger ones one has a performance problem. As for the scroll bars: I can do this, sure. I'll update and blog again. Yeah I know, unfortunately I just did this for small images (e.g. 640×480). With bigger ones one has a performance problem. As for the scroll bars: I can do this, sure. I’ll update and blog again.

]]> By: Smite http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-41880 Smite Sun, 02 Sep 2007 19:21:08 +0000 http://www.semanticmetadata.net/2007/08/30/content-aware-image-resizing-gpl-implementation/#comment-41880 A few comments re: the GUI app 1) Opening a large photo does not result in scrollbars when needed, making it impossible to mark needed/unwanted areas that are off-screen 2) After specifying a height and width smaller than the current photo, and clicking the Resize button, my CPU went to 100% for a short while, but once that was complete, nothing changed in the GUI. Is there something special I have to do to see / use the resulting resized image? A few comments re: the GUI app
1) Opening a large photo does not result in scrollbars when needed, making it impossible to mark needed/unwanted areas that are off-screen
2) After specifying a height and width smaller than the current photo, and clicking the Resize button, my CPU went to 100% for a short while, but once that was complete, nothing changed in the GUI. Is there something special I have to do to see / use the resulting resized image?

]]>