Help requests (new threads)

Installed files

Wed, 22 Jul 2009 19:58:55 +0000

It would be helpful to have in the documentation a list of the files structure which should be installed after compiling from the source.

I am compiling from the source on OS X and the following was installed,

 /usr/include/lqr-1/lqr.h /usr/include/lqr-1/lqr/ lqr_base.h lqr_carver_bias_pub.h lqr_carver_list_pub.h lqr_carver_pub.h lqr_carver_rigmask_pub.h lqr_cursor_pub.h lqr_energy_pub.h lqr_gradient_pub.h lqr_progress_pub.h lqr_rwindow_pub.h lqr_vmap_list_pub.h lqr_vmap_pub.h

Small patch needed to compile liblqr on Mac OS: change upstream package?

Thu, 16 Jul 2009 08:52:57 +0000

Hi,
being a relatively new "digiKam fan and user", I'm trying to create a "Portfile" for digiKam for the MacPorts project.
Now digiKam 1.0 beta 2 comes with a private version of your liblqr (version 0.4.1). This library does not compile on Mac OS without a little patch.
The patch is to remove the "inline" keyword in two lines. I tested that patch on Linux, and liblqr still compiles. I don't know if it affects functionality or security, though. But if you think it is ok to do so, I'd suggest you apply these changes to the next release, so that liblqr and digiKam 1.0 in the future can compile on Mac OS without any extra patches.

A tiny patch and an invitation

Sat, 25 Apr 2009 21:04:31 +0000

Hi,

Gilles Caullier is asking if you could you include this small patch for the next release ?

http://websvn.kde.org/trunk/extragear/graphics/digikam/imageplugins/contentawareresizing/lqr/lqr_base.h?r1=958077&r2=959015

You could also join us at to follow implementation of Lqr in Digikam and discuss with us the possible features:
https://bugs.kde.org/show_bug.cgi?id=149485

Thanks,

Julien

How implementation works

Sat, 25 Apr 2009 09:22:54 +0000

Hi,

We have a question about your implementation, what do you implement ? I think you implement V ersion B, did you ever tried to implement Version A ? does it create too many artefacts ?
Is your implementation O(h*w*s) where h= height w=widht and s= number of pixel to delete in one direction (assuming we just reduce in one direction) ? or is it O(h*w) ?

Version A

1- Compute energy
2- Find all paths of least energy
3- Delete the required number of paths

Version B

1- Compute energy
2- Find one path of least energy
3- Delete this path and update energy
4- Find another path of least energy, go to step 3

Thanks for your help.

Julien

Deleting a carver object

Fri, 03 Apr 2009 18:09:12 +0000

Hi,

we use the LQR in an image plugin of the digiKam image editor (well we are writing a plugin at the moment).

The problem is that we have a crash when the plugin is finishing. This is due to the way we assign the image data to the carver. The data comes from a DImg object (digikam image object) that holds the data.
We pass the pointer to the carver, but after the carver is destroyed by the appropriate function call, the DImg object crashes in the destructor because it tries to free the data (which has already been done by the carver).

My actual question is: do we need to call this destroy method or will it be enough to just do "delete carver;" in the destructor of the plugin?
If not, we need to do a deep copy of the image data first (like we do now) and provide this copy to the carver object. But this is not very efficient of course.

Andi

I'm on Windows

Thu, 21 Aug 2008 21:29:52 +0000

How do I install it?

Install problems

Wed, 18 Jun 2008 14:32:09 +0000

I have Ubuntu 7.10 and Gimp 2.4.2 how can I install the Liquid Rescale Library?

Using Other features

Fri, 07 Mar 2008 06:23:57 +0000

I am part of the ImageMagick development team, where an initial experimental liquid resize has already been added for batch processing of images.

However I am finding very little information on doing just about anything else! Is there a more comprehensive manual some where?

Things I want to include is some of the lower level functions that should be available in the library such as getting a mask of the the seams that would be removed from an image, when it is seam carved.

This information is useful for generating smoother images by compressing the pixels in the areas removed, rather than just deleteing the pixels out-right!