Re: [Gimp-user] I need to know how much was cropped with autocrop
maybe creating a layer = copy of the image size-way; make it invisible (that should avoid autocropping it) and then compare it's size and position with the cropped image. On 8/1/07, David Feinzeig [EMAIL PROTECTED] wrote: I am writing a plugin that, among other things, autocrops an image. But, I need to know how much was cropped from all four sides, to deal with alignment issues. Any idea how I can do this? Thanks! Dave ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user -- LEGENY Jozef ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] I need to know how much was cropped with autocrop
On 8/1/07, David Feinzeig [EMAIL PROTECTED] wrote: I am writing a plugin that, among other things, autocrops an image. But, I need to know how much was cropped from all four sides, to deal with alignment issues. Any idea how I can do this? Thanks! Dave If you create a rectangular path that matches the image boundaries, you can calculate the offset and amount cropped from the difference between the corner coordinates of the path and the corner coordinates of the layer. OTOH if you're just autocropping a *layer*, not an image, you can just compare image corners to layer corners. HTH. ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] Question about GIMP CMYK support.
On Wednesday 08 August 2007 09:19, Owen wrote: 2. Do you really need to make cmyk plates? Printing companies do, yes. Cheers; Leon -- http://cyberknights.com.au/ Modern tools; traditional dedication http://www.taslug.org.au/ Member, Tasmania Linux User Group http://slpwa.asn.au/Member, Linux Professionals WA http://osia.net.au/ Member, Open Source Industry Australia http://linux.org.au/PastCommittee Member, Linux Australia ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] I need to know how much was cropped with autocrop
On 8/1/07, David Gower wrote: OTOH if you're just autocropping a *layer*, not an image, you can just compare image corners to layer corners. While looking into this, I notice that autocropping an image uses the active layer, not the projection, to determine the resultant image boundaries. (Would this be a bug?) Based on this behavior, there is no real advantage (from a scripting standpoint; you still have to process each layer individually) to doing a crop image as opposed to a crop layer. By processing each layer individually, its boundary offsets and dimensions remain relative to the original image, easing the task of comparing their before and after values. ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] I need to know how much was cropped with autocrop
Hi, On Wed, 2007-08-08 at 11:35 -0400, [EMAIL PROTECTED] wrote: While looking into this, I notice that autocropping an image uses the active layer, not the projection, to determine the resultant image boundaries. (Would this be a bug?) No. That's what the plug-in does and it seems that's what the plug-in author wanted it to do. Sven ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] I need to know how much was cropped with autocrop
[EMAIL PROTECTED] writes: While looking into this, I notice that autocropping an image uses the active layer, not the projection, to determine the resultant image boundaries. (Would this be a bug?) If you want a plug-in that crops the image according to the contents of all layers, not just the active one, I have one: http://shallowsky.com/software/gimp/autocropall.c -- ...Akkana Beginning GIMP: From Novice to Professional: http://gimpbook.com ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
[Gimp-user] large tile sizes and large images on Freebsd
Hi list, I run FreeBSD 6.2 (2 gig ram) and use gimp-2.2.17 for editing my large (1x1pixels) photos. This works when the tile cache is set to 256MB but this is not enough for fast editing. When I set the tile cache to 512MB or more it stops with error: GLib-ERROR **: gmem.c:135: failed to allocate 16384 bytes I checked in top while the gimp was opening the image and I still had 400MB free before it stopped (not counting my 4000MB free swap). I have another computer with Fedora 7 and less RAM (1 gig) and here this does work, tile size is set to 512MB and editing is rather fast. I found this old thread: http://www.mail-archive.com/gimp-user@lists.xcf.berkeley.edu/msg07633.html wich a bit the same. So my questions are: -Is there some magic setting wich allows the tile size to be bigger ? -Can't the gimp be configured to not save to disk after every edited pixel ? If you put one pencil dot on an image it takes 4 seconds before you can do the next. -Is there a way to work in ram only ? Can I for example buy 2 additional gig and then force the gimp to use only this memory and give me a messages out of memory when this does not work ideas ? kind regards below is the full output: $ gimp --debug-handlers --stack-trace-mode always scan13.tif GLib-ERROR **: gmem.c:135: failed to allocate 16384 bytes aborting... gimp: terminated: Abort trap: 6 #0 0x28cea6cd in wait4 () from /lib/libc.so.6 #1 0x28cc96ad in waitpid () from /lib/libc.so.6 #2 0x28c75242 in waitpid () from /lib/libpthread.so.2 #3 0x28a3ad79 in g_on_error_stack_trace () #4 0x080646b4 in ?? () #5 0x083ace00 in ?? () #6 0xbfbfd560 in ?? () #7 0x in ?? () #8 0x24075e00 in ?? () #9 0x in ?? () #10 0x in ?? () #11 0x in ?? () #12 0x in ?? () #13 0xbfbfd584 in ?? () #14 0x28d631a0 in ?? () from /lib/libc.so.6 #15 0xbfbfd5b4 in ?? () #16 0xbfbfd5b4 in ?? () #17 0x0282 in ?? () #18 0x28c904b4 in ?? () from /lib/libpthread.so.2 #19 0xbfbfd5a8 in ?? () #20 0x080646e1 in ?? () #21 0x0001 in ?? () #22 0xbfbfd5b4 in ?? () #23 0x0006 in ?? () #24 0x28c904b4 in ?? () from /lib/libpthread.so.2 #25 0xbfbfd980 in ?? () #26 0xbfbfd6c0 in ?? () #27 0xbfbfd5c8 in ?? () #28 0x0806421d in ?? () #29 0x28d631a0 in ?? () from /lib/libc.so.6 #30 0x09042d00 in ?? () #31 0xbfbfd5d8 in ?? () #32 0x28c8e3d1 in __error () from /lib/libpthread.so.2 (script-fu:13073): LibGimpBase-WARNING **: script-fu: wire_read(): error ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
Re: [Gimp-user] large tile sizes and large images on Freebsd
Bram Van Steenlandt wrote: Hi list, I run FreeBSD 6.2 (2 gig ram) and use gimp-2.2.17 for editing my large (1x1pixels) photos. This works when the tile cache is set to 256MB but this is not enough for fast editing. When I set the tile cache to 512MB or more it stops with error: GLib-ERROR **: gmem.c:135: failed to allocate 16384 bytes I checked in top while the gimp was opening the image and I still had 400MB free before it stopped (not counting my 4000MB free swap). I have another computer with Fedora 7 and less RAM (1 gig) and here this does work, tile size is set to 512MB and editing is rather fast. I found this old thread: http://www.mail-archive.com/gimp-user@lists.xcf.berkeley.edu/msg07633.html wich a bit the same. So my questions are: -Is there some magic setting wich allows the tile size to be bigger ? -Can't the gimp be configured to not save to disk after every edited pixel ? If you put one pencil dot on an image it takes 4 seconds before you can do the next. -Is there a way to work in ram only ? Can I for example buy 2 additional gig and then force the gimp to use only this memory and give me a messages out of memory when this does not work ideas As the original poster of that thread, let me tell you what I know. 1. No magic. I assume there's something bad happening between glib and the FreeBSD memory allocation routines, but whatever it is carried across 5.3 to 6.2. I'm pretty sure I logged a bugzilla case, but in the end, I switched to a linux platform and lost interest. I get the feeling that the GIMP devs don't use FBSD and as long as it builds and runs, they're not all that interested in what seems like corner cases. 2. You could try setting undo level to 0 at the risk of not being able to recover from any mistake 3. nope, at least not that I've found 4. nope Don't bother with film-gimp or whatever they're calling the project these days. It does HDR, but their big memory handling is even worse. Turns out that the images projected in theaters are actually not all that hi rez. Your eye fills in the missing spots frame by frame. If you built KDE for your desktop, you might want to check out Krita as an image editor. Last I looked at it (which is maybe 9 mos), I still liked the GIMP better, but it (krita) handles images completely differently, so it might be worth a shot. Didn't get a chance to run any of my scans through it. ___ Gimp-user mailing list Gimp-user@lists.XCF.Berkeley.EDU https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-user
