[Gimp-user] Image resizing based upon image content
There is an amazing video describing an image resizing algorithm that removes (or adds) pixels based upon their importance to the subjecto of the photo. Can this be implemented in The Gimp? Apparently it will soon be a part of Photoshop. The video is here: http://www.techcrunch.com/2007/08/28/adobe-hires-co-inventor-of-image-resizer-technology/ Dotan Cohen http://what-is-what.com/what_is/gimp.html ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Image resizing based upon image content
saw that the other day -- very cool. On 8/29/07, Dotan Cohen [EMAIL PROTECTED] wrote: There is an amazing video describing an image resizing algorithm that removes (or adds) pixels based upon their importance to the subjecto of the photo. Can this be implemented in The Gimp? Apparently it will soon be a part of Photoshop. The video is here: http://www.techcrunch.com/2007/08/28/adobe-hires-co-inventor-of-image-resizer-technology/ Dotan Cohen http://what-is-what.com/what_is/gimp.html ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user -- Anthony Ettinger Ph: 408-656-2473 var (bonita, farley) = new Dog; farley.barks(very loud); bonita.barks(at strangers); http://chovy.dyndns.org/resume.html http://utuxia.com/consulting ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Image resizing based upon image content
Dotan Cohen wrote: There is an amazing video describing an image resizing algorithm that removes (or adds) pixels based upon their importance to the subjecto of the photo. Can this be implemented in The Gimp? Of course it can be implemented in GIMP. It just takes someone with the time and ability to write the code for a plug-in that implements the algorithm. -- Cheers! Kevin. http://www.ve3syb.ca/ |What are we going to do today, Borg? Owner of Elecraft K2 #2172 |Same thing we always do, Pinkutus: | Try to assimilate the world! #include disclaimer/favourite | -Pinkutus the Borg ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] pdb.gimp_by_color_select malfunction
pdb.gimp_by_color_select malfunction. linux debian etch amd64 gimp 2.3.13 (no other updated libs required) I have a python routine that uses: pdb.gimp_by_color_select Everything works fine for smaller files but the subroutine does not work correctly (does a select all, instead of the requested select by color) when I use it on larger ones. The current picture is 8000 X 6500 px. I tried pdb.gimp_by_color_select_full too, but it also fails. I can pause the execution of the python script right after the python pdb.gimp_by_color_select. The GUI indicates a select all condition! I can then use the GUI Select - by color which works perfectly! Ideas??? Stephen -- Stephen Moss [EMAIL PROTECTED] ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] pdb.gimp_by_color_select malfunction .. workaround
Fellow python users, After some more work on the problem I discovered that: - small files opened in the GUI are select - none but - larger files are opened select - all Workaround: Put a pdb.gimp_selection_none(image) before the pdb.gimp_by_color_select_full(drawable, Stephen -- Stephen Moss [EMAIL PROTECTED] ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] pdb.gimp_by_color_select malfunction .. workaround
On 8/30/07, Stephen Moss [EMAIL PROTECTED] wrote: Fellow python users, After some more work on the problem I discovered that: - small files opened in the GUI are select - none but - larger files are opened select - all I find this extremely difficult to believe. I think it's more likely something about the image that causes gimp_by_color_select to behave in a way you don't expect. For example, if your huge image is indexed, that might cause this effect you mention; the threshold selection options (eg, in 'magic wand' and 'select by color' tools) do work in indexed mode, but the result often isn't meaningful (since the threshold is applied to the colormap indices of the pixels, rather than the actual colors they point to.) Does toggling 'sample merged' effect the result? I have done my tests with: Antialiasing ON (does nothing anyway, AFAIK) Feather OFF Select transparent areas ON Sample Merged OFF Select by: COMPOSITE (if you had been using the wrong value here, it could have tripped you up too.) On a 8000x6000 PNG image (on an AMD Duron, Ubuntu 6.06, GIMP [latest from SVN] ), I have tried to reproduce your problem with both an indexed and a grey image, and neither display the behaviour you mention. The select menu always shows 'None' as disabled and 'All' as normal after the image is opened, indicating that the selection is currently empty (None). In fact, the menus do not indicate whether all pixels are selected -- you can see that the 'All' menu entry is never disabled, so even when the selection already covers everything, you can still Select-All. If you want to check the state of the selection, there is a 'Selection Editor' dockable you can access which provides a clear display of the current selection mask. Lastly, it's possible that the file plugin for whatever format your image is in is interpreting some data wrongly and so mistakenly resetting the selection mask to this confusing state. What format is your input file(s)? ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
