After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 526810 - Trouble Running Map Object In Filter All Layers
Trouble Running Map Object In Filter All Layers
Status: RESOLVED OBSOLETE
Product: gimp-gap
Classification: Other
Component: filter all layers
2.4.0
Other All
: Normal normal
: ---
Assigned To: hof
hof
Depends on:
Blocks:
 
 
Reported: 2008-04-07 20:25 UTC by Gregory Ross
Modified: 2018-05-24 10:20 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gregory Ross 2008-04-07 20:25:46 UTC
Please describe the problem:
I am running Gimp Ver. 2.4.4 in Windows XP with Gap 2.4. I created several layers (all in RGB mode and all with alpha channels) and then went to Filter>Filter all layers. I select plug-in-map-object and click on apply varying. I set the options for the 1st layer and it maps perfectly. I set the options for the last layer and again it maps perfectly. When I select continue, it sets the visibility on each layer, but does not map any of the layers. If I go back to Gimp ver 2.2.17 it works perfectly. I have tried it on 5 or 6 different images I am working on. They all work in 2.2.17 and fail the same way in 2.4.4. I even went so far as to reinstall GAP, but have had no luck. I don't feel up to reinstalling Gimp, but I may have to.

Steps to reproduce:
1. Create multiple layers of same image.
2. Filters>Filter all layers>plug-in-map-object
3. Set values for first layer and last layer.
4. Press 'Continue'


Actual results:
The first and last layers map fine. None of the others map at all

Expected results:
I expected each layer to map slightly differently (based on my settings)to create a rotating plane. It works fine in Gimp 2.2.17

Does this happen every time?
This happens every time. I've tried it with several images.

Other information:
Comment 1 PhotoComiX 2008-04-08 15:09:33 UTC
i try to duplicate the bug, with windows xp and gimp 2.4.5 and Gap 2.4

"Filter all layer" seems to work correctly with all filters i try

BUT with "Map Object" there all calls where completed successfully, but that may be not evident since as result all layers but the first processed were identical

That because the in the second call of "filter all layer" "map object" used wrong data as imput, this was evident in the filter preview, and confirmed by the result
(here link for the XCF files http://www.box.net/shared/ild5fq00kc error is in the image of the cube)

Basically at the second call in the preview windows was visible a already mapped image as after first call, but mapped again...meaning that the input was wrong coming from the already processed layer, while output was correct.

All the other call were done as expected, but result was always same image

But then it should be hard interpolate between a image mapped once, and one processed twice.

Then i'm used to process gigantic image but "map object" if used by apply all layer seems to crash with everything bigger then 800x800
with 800x800 and 7 layer  was needed something as 55 minutes to complete "map object"

Apply other kind of mapping on Hi-Res images a 5000x4000 required me just a tiny fraction of that time...on bigger i had temporary freezing but never crash as with with" map object "

Comment 2 Gregory Ross 2008-04-08 18:37:37 UTC
Here is a little more info on what I am saying. I created a logo using a script-fu, duplicated the layer 34 times (35 total). Then I went to Filter>Filter all layers. Again I selected plug-in-map-object and clicked on apply varying. I set it to map a plane with transparent background. Under orientation I set rotation Y to -180 and clicked OK. It took about 5 seconds to render that layer. For the last layer I set rotation Y to 180. Again it took about 5 seconds to render that layer. The first and last layers rendered correctly (Text read backwards). When I clicked on continue it set visibility on all the other layers instantly (0 seconds). It never gave any indication that it was attempting to render the remaining layers. I get the exact same result as if I had hit the button that said Skip 33. The first layer and the last layer were correctly flipped horizontally. All of the remaining layers had no change at all.
Comment 3 Sven Neumann 2008-04-09 20:12:15 UTC
Filter All Layers is part of gimp-gap. Reassigning this report accordingly...
Comment 4 Gregory Ross 2008-04-11 22:38:06 UTC
I have tried using the filter all layers with eight other filters.
Half passed (worked) and half failed. The results are as follows:

Fail
====
plug-in-alienmap2
plug-in-apply-canvas
plug-in-blinds
plug-in-cartoon

Pass
====
plug-in-applylens
plug-in-bluebox
plug-in-borderaverage
plug-in-gauss

Comment 5 hof 2008-04-12 16:42:25 UTC
The GAP "Filter all layers" functionality
depends on iterator procedures that
are responsible to vary the parameter values.

Some of the plug-ins implement the iterator procedure,
or register their parameter structure in the file:
<GIMPDIR>lastval_descriptions.txt.
For all other plug-ins the fallback alternative iterator procedure
(that is provided by the GIMP-GAP package) is used.

Whenever new releases introduce changes in the parameter structure
of a plug-in, this breaks the "Filter all layers" feature,
and require an updated of GIMP-GAP to get it working again.

If you run gimp from a command prompt where you can see console output
you probably may see an error message like this:

ERROR: p_plug_in_map_object_iter  stored Data missmatch in size NN != MM

GIMP-GAP 2.4.0 was tested with GIMP-2.4.3
under Linux, where Map Object the other mentioned
filters all work well.

(see file gap/TESTPROT_iter_ALT for details
of the test)

Currently i don't have much time to work on GIMP-GAP,
I guess that there were changes in the Gimp Ver. 2.4.4
but had no time for further analysis yet.

So it will take some weeks until i check again
against the latest Stable Gimp release (currently 2.4.5)
Comment 6 Gregory Ross 2008-04-14 01:28:48 UTC
I updated GIMP-GAP but the problem persists. I also tried starting from the command prompt. I got no error messages at all. I ran through the entire procedure and had no error messages of any kind. I also tried using Map-object from 2.2 and it actually performed the map all layers with the box perfectly. However just using it normally to map a sphere, the sphere cam out weird. I am going to try it again and try to get more detail on what wasn't working right with the sphere. Also that doesn't fix the errors on the other filters.
Comment 7 PhotoComiX 2008-04-14 04:30:45 UTC
i just tested 3 of the filters supposed to fail

with gimp 2.4.5 windows xp 

plug-in-alienmap2 worked well

plug-in-blinds too no problem



plug-in-cartoon worked well 1 time
2 time something weird happened :on 8 layer 2 were absolutely unchanged

Note about cartoonize i must check if was something peculiar in the image, 1 of the 2 unchanged was the top layer and was visible also in the cartoon filter preview that even most dramatic setting do not have any visible effect
Comment 8 Gregory Ross 2008-04-14 19:37:31 UTC
I'm running 2.4.4 and maybe I need to try 2.4.5? I figure something has to work. I'm tired of going back and forth between programs all of the time. Maybe I can minimize failures by upgrading to 2.4.5.
Comment 9 Gregory Ross 2008-04-14 20:09:59 UTC
Fail
====
plug-in-map-object - still fails with ver 2.4.5 (1st and Last changed but all intermediate layers did not.)
plug-in-alienmap2 - still fails with ver 2.4.5 (1st and Last changed but all intermediate layers did not.)
plug-in-apply-canvas - still fails with ver 2.4.5 (1st and Last changed but all intermediate layers did not.)
plug-in-blinds - still fails with ver 2.4.5 (1st and Last changed but all intermediate layers did not.)
plug-in-cartoon - still fails with ver 2.4.5 (1st and Last changed but all intermediate layers did not.)

Comment 10 Gregory Ross 2008-04-14 20:52:18 UTC
I just upgraded to Gimp 2.4.5 and re-installed GAP 2.4.0 with no luck in resolving the problem. I also did the GAP Bug Fix and that didn't resolve the problem either. I am getting very frustrated, but at least I can still go back and use 2.2.17 if I want to use this feature.
Comment 11 Gregory Ross 2008-05-02 17:25:41 UTC
I was just wondering if there has been any follow up on this issue? I have set up Gimp for friends and family and they are running into this same problem. I am locating my installations for 2.2 so that they will have all of the features. It's hard to explain to someone new to Gimp, why they need two versions to access all of the functions. I am really surprised that it has still not been moved from unconfirmed. I thought by now it would have been cocfirmed.
Comment 12 GNOME Infrastructure Team 2018-05-24 10:20:31 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp-gap/issues/3.