Re: [Gimp-developer] GIMP Image Size Limits
Hi, Kevin Myers [EMAIL PROTECTED] writes: Thanks for your reply. My tile cache size is set to 1GB (I have 1.5GB of RAM), which should theoretically help based on your comments. Also, upon further testing I have found that the problem I am encountering seems to be related to the physical dimensions of the image, rather than the file size or pixel count. For example, the GIMP is failing when the height of the image exceeds about 187.5 feet, regardless of whether using 72 dpi or 200 dpi. are you saying 188 _feet_ ? That would make about 162000 pixels of image height. How wide are these images? If I'd assume the same width, a single RGB layer would have more than 75GB of image data. Your operating system is not even able to address the amount of virtual memory you'd need to work with such a beast. I would be very willing to try the 1.3x source track. Unfortunately, I am limited to running under Windows at the moment, and my understanding is that 1.3x has not yet been ported to Windows, and that porting would be far too difficult for my amateur level porting skills. this is not true; actually the situation is the other way around. While GIMP-1.2 needed real porting work, all the libraries required by GIMP-1.3 now officially support the Win32 platform and it shouldn't be too difficult to get the GIMP-1.3 source compiled on Windows. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP Image Size Limits
On Fri, Jan 10, 2003 at 05:13:31AM -0600, Kevin Myers wrote: Yes, some of these images exceed 200ft in length. You may be wondering what they could be: images of well logs for oil and gas wells. These are essentially strip chart (graphical) recordings of various physical properties taken over the length of the borehole. Are you sure you want to use GIMP to work with this sort of things anyhow? What really do you want to do to them -- are you sure ImageMagick wouldn't be a better choice for most operations? /* Steinar */ -- Homepage: http://www.sesse.net/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP Image Size Limits
Hi Sven - My images are extremely long and relatively narrow, not anywhere near square. A typical image size would be approximately 200K pixels in length (height), by only 2K pixels in length, for a total image size of about 400M pixels. I have some images over 600M pixels, while others are somewhat smaller. Yes, some of these images exceed 200ft in length. You may be wondering what they could be: images of well logs for oil and gas wells. These are essentially strip chart (graphical) recordings of various physical properties taken over the length of the borehole. They are rather drastically scaled down already (typically 1 inch represents somewhere between 20 to 100 feet) in the vertical dimension, and detail is important, so further scale reduction is NOT practical. It is also impractical for other reasons that are too complex to get into here to split the images up into smaller sections. Bottom line: Again, I must state that the problem I am encountering is NOT related to the pixel count or file size! It occurs when the number of pixels on ONE axis multiplied by the resolution exceeds approximately 187.5 feet in length. Thanks for your comments re GIMP 1.3.x. Your positive impressions are somewhat surprising to me, since comments from Tor Lilqvist (the primary porter of GIMP 1.2.x to Windows), led me to believe that porting 1.3.x to Windows was going to be very difficult. Something to do with library interdependencies and lack of related tools under Windows if I remember correctly. Since Tor's porting skills are far beyond my own, and he's been involved with porting the GIMP for quite a while now, I tend to respect his opinions. However, anyone can occasionally miss something, especially if they are too busy with other things. Do you know anywhere I could find some instructions for installing GIMP 1.3.x under Windows? s/KAM - Original Message - From: Sven Neumann [EMAIL PROTECTED] To: Kevin Myers [EMAIL PROTECTED] Cc: gimp users [EMAIL PROTECTED]; gimp developers [EMAIL PROTECTED] Sent: Friday, January 10, 2003 4:46 AM Subject: Re: [Gimp-developer] GIMP Image Size Limits Hi, Kevin Myers [EMAIL PROTECTED] writes: Thanks for your reply. My tile cache size is set to 1GB (I have 1.5GB of RAM), which should theoretically help based on your comments. Also, upon further testing I have found that the problem I am encountering seems to be related to the physical dimensions of the image, rather than the file size or pixel count. For example, the GIMP is failing when the height of the image exceeds about 187.5 feet, regardless of whether using 72 dpi or 200 dpi. are you saying 188 _feet_ ? That would make about 162000 pixels of image height. How wide are these images? If I'd assume the same width, a single RGB layer would have more than 75GB of image data. Your operating system is not even able to address the amount of virtual memory you'd need to work with such a beast. I would be very willing to try the 1.3x source track. Unfortunately, I am limited to running under Windows at the moment, and my understanding is that 1.3x has not yet been ported to Windows, and that porting would be far too difficult for my amateur level porting skills. this is not true; actually the situation is the other way around. While GIMP-1.2 needed real porting work, all the libraries required by GIMP-1.3 now officially support the Win32 platform and it shouldn't be too difficult to get the GIMP-1.3 source compiled on Windows. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP Image Size Limits
Hi, Kevin Myers [EMAIL PROTECTED] writes: My images are extremely long and relatively narrow, not anywhere near square. A typical image size would be approximately 200K pixels in length (height), by only 2K pixels in length, for a total image size of about 400M pixels. I have some images over 600M pixels, while others are somewhat smaller. Yes, some of these images exceed 200ft in length. You may be wondering what they could be: images of well logs for oil and gas wells. These are essentially strip chart (graphical) recordings of various physical properties taken over the length of the borehole. They are rather drastically scaled down already (typically 1 inch represents somewhere between 20 to 100 feet) in the vertical dimension, and detail is important, so further scale reduction is NOT practical. It is also impractical for other reasons that are too complex to get into here to split the images up into smaller sections. Bottom line: Again, I must state that the problem I am encountering is NOT related to the pixel count or file size! It occurs when the number of pixels on ONE axis multiplied by the resolution exceeds approximately 187.5 feet in length. please file a bug-report with all the information that might be useful. Thanks for your comments re GIMP 1.3.x. Your positive impressions are somewhat surprising to me, since comments from Tor Lilqvist (the primary porter of GIMP 1.2.x to Windows), led me to believe that porting 1.3.x to Windows was going to be very difficult. Something to do with library interdependencies and lack of related tools under Windows if I remember correctly. Since Tor's porting skills are far beyond my own, and he's been involved with porting the GIMP for quite a while now, I tend to respect his opinions. However, anyone can occasionally miss something, especially if they are too busy with other things. Do you know anywhere I could find some instructions for installing GIMP 1.3.x under Windows? obviously Tor and Hans have some problems with the way we reorganized the code. I'm sure however that this can be solved. Due to the much improved abstraction layers in GLib-2.x, the GIMP-1.3 source tree is a lot more portable and should compile out-of-the-box provided you get the build system setup correctly. But then, I've never tried it myself, so you should probably ignore me. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] GIMP Image Size Limits
Hi, just for your information: The problem is being discussed further in http://bugzilla.gnome.org/show_bug.cgi?id=103030 and has been fixed in CVS in the meantime. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] FW: Patch for wishlist entry 75558
Can someone please look into this patch I've been submitted?
Ta,
Austin
---BeginMessage---
Title: Patch for wishlist entry 75558
Hi,
I wrote a patch for the bugzilla entry 75558, curve tool does not remember old
values.
I wrote a patch for this a while ago, but it seems to be removed in the newer
gimp versions because of some problems.
So I made the change again and hope that you can commit it to cvs.
This time I tested it with RGB and grayscale pictures. No problems whatever.
(patch is appended)
Thanks,
Ralf
--
Ralf Engels
Software design engineer
www.rengels.de
--- gimpcurvestool.c.old Fri Jan 10 12:30:05 2003
+++ gimpcurvestool.c Fri Jan 10 12:38:57 2003
@@ -289,17 +289,17 @@
if (!curves_dialog)
{
curves_dialog = curves_dialog_new ();
-}
-
- /* Initialize the values */
- curves_dialog-channel = GIMP_HISTOGRAM_VALUE;
- for (i = 0; i 5; i++)
-for (j = 0; j 256; j++)
- curves_dialog-curve[i][j] = j;
-
- for (i = 0; i 5; i++)
-{
- curves_channel_reset (i);
+
+ /* Initialize the values */
+ curves_dialog-channel = GIMP_HISTOGRAM_VALUE;
+ for (i = 0; i 5; i++)
+for (j = 0; j 256; j++)
+ curves_dialog-curve[i][j] = j;
+
+ for (i = 0; i 5; i++)
+{
+ curves_channel_reset (i);
+}
}
curves_dialog-drawable = gimp_image_active_drawable (gdisp-gimage);
@@ -333,6 +333,9 @@
gtk_widget_show (curves_dialog-shell);
curves_update (curves_dialog, GRAPH | DRAW);
+
+ if (curves_dialog-preview)
+curves_preview (curves_dialog);
}
static void
---End Message---
___
Gimp-developer mailing list
[EMAIL PROTECTED]
http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] FW: Patch for wishlist entry 75558
Hi, Austin Donnelly [EMAIL PROTECTED] writes: Can someone please look into this patch I've been submitted? can you please ask the submitter to attach the patch to the bug-report and to explain why it should be applied. Salut, Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] gimp-perl for windows?
On 10 Jan 2003, at 12:37, Joakim wrote: I have tried to find gimp-perl for win32 but I can't find it. The Gimp-Perl FAQ says that there is no port of gimp-perl for win32. Is the FAQ not updated or is it really true that their is no port? In the latter case, is anybody trying to do a port? No, there is no port, and as far as I know, nobody's trying to port it. I thought there had been discussion about this on the developer list, but I am not sure I found it: On 22 Dec 2001, at 1:47, Fabian Frédérick wrote: About Perl-Gimp for Windows, I've done a skeleton of that stuff Problem is it doesn't work with structs yet (Perl blessing doesn't work at all). On 19 Apr 2002, at 19:19, [EMAIL PROTECTED] wrote: [Scheme] does, however, run under windows, unlike gimp-perl, which should be very easy to port without Gtk. Porting Gtk should be easy too, if the destination is named cygwin. Unfortunately, the developers who do the windows port don't use the same config mechanisms as under unix/cygwin, and Gtk is proven to be hard to port to that environment. On 24 Apr 2002, at 18:49, [EMAIL PROTECTED] wrote: On Fri, Apr 19, 2002 at 10:34:19PM +0300, Tor Lillqvist [EMAIL PROTECTED] wrote: and Gtk is proven to be hard to port to that environment. ... but I still fear that porting gimp-perl might be quite a task. Why? I apart from trivial changes (gimp-perl has to parse the output of gimptool -n --install-admin-bin because gimptool doesn't have an option to output the pluginpath and can't be edited under windows), it compiled out of the box five minutes ago under windows 2000 using cygwin and the binaries from www.gimp.org/win32 (which, as I read it, are not really compatible with my environment anyways). I think the remaining problems are highly trivial (e.g. possible reliance on / instead of \, which mostly isn't a problem under windows anyways, socket functions etc.) It's just that this has to do somebody who knows windows better then me (I lack the time compiler to compile gimp c for windows just to test it). Perhaps you could try and port it yourself, or sponsor somebody who can. Or you could file an enhancement request at http://bugzilla.gnome.org. Good luck, -- branko collin [EMAIL PROTECTED] ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] writing plug-in on windows platform
Hello, I have basic C programming knowledge and looking for a starting point to learn writing gimp plugins. I am currently using windows platform. Any comments? Thanks in advance. __ Do you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now. http://mailplus.yahoo.com ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
