Re: [Gimp-developer] Kudos to The GIMP Developers!
On Thu, Sep 25, 2003 at 06:18:44PM +, Tor Lillqvist wrote: > > You're right. If you could tell me such a program... I would have used > > it. The nearest approximation was xfractint but it's cumbersome to use > > and doesn't have a gradient editor (and I'm not sure whether it's > > capable of rendering 2x14000 pixel images). ;-) > > Wouldn't it then be quicker to render the fractal in smaller pieces in > GIMP, output as ppm files, and the just slap the pieces together with > pnmcat and convert to PS with pnmtops? I wasn't aware of pnmcat. Apart from that, it's a bit difficult to render fractal tiles with FractalExplorer... And I'm a bit afraid of rounding errors at the edges... it depends on how FractalExplorer handles them - does it render [xmin,xmax] or [xmin,xmax)? Bye, Tino. -- * LINUX - Where do you want to be tomorrow? * http://www.tu-chemnitz.de/linux/tag/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Kudos to The GIMP Developers!
Tino Schwarze writes: > You're right. If you could tell me such a program... I would have used > it. The nearest approximation was xfractint but it's cumbersome to use > and doesn't have a gradient editor (and I'm not sure whether it's > capable of rendering 2x14000 pixel images). ;-) Wouldn't it then be quicker to render the fractal in smaller pieces in GIMP, output as ppm files, and the just slap the pieces together with pnmcat and convert to PS with pnmtops? > > (And if your desired output file format is PostScript, why not let the > > printer do the job ;-) > Muhahaha. The printer took about 8 hours to RIP the precalculated stuff. > The Xeon/2.4GHz took about an hour to render the fractal. Yeah, that was mostly a joke... --tml ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Kudos to The GIMP Developers!
On Wed, Sep 24, 2003 at 06:21:47PM +0300, Tor Lillqvist wrote: > So the huge image you generated is a fractal? Isn't it a bit silly to > render such images (especially if they are huge) with GIMP, where all > of the image's pixels are kept in memory (or the tile cache) all the > time? Aren't many fractals such that you could calculate the value of > each pixel independently of the others, with a very simple and minimal > (non-interactive) program? You're right. If you could tell me such a program... I would have used it. The nearest approximation was xfractint but it's cumbersome to use and doesn't have a gradient editor (and I'm not sure whether it's capable of rendering 2x14000 pixel images). ;-) > (And if your desired output file format is PostScript, why not let the > printer do the job ;-) PostScript is after all a programming > language... Just send the printer a PostScript program that calculates > the desired image. For many fractals, it might be surprisingly short.) Muhahaha. The printer took about 8 hours to RIP the precalculated stuff. The Xeon/2.4GHz took about an hour to render the fractal. I thought about that, but I'm not familiar with Postscript (I guess, the gradient stuff would be the most complicated - I used a custom gradient). Bye, Tino. -- * LINUX - Where do you want to be tomorrow? * http://www.tu-chemnitz.de/linux/tag/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Kudos to The GIMP Developers!
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tino Schwarze wrote: | Hi there, | | I'd just like to say: Well done. I managed to create a A1 poster at 600 | dpi - a whopping 1.1 Gig of picture data (about 2x14000 pixels). | While GIMP 1.2.4 crashed while rendering the fractal, GIMP 1.3.20 | managed to get it done and even save it as Postscript. Weehee! | | BTW: Is it possible that there is a 3 Gig limit on per-process memory? | The machine has 6 GB, no ulimits and I got a "could not allocate x | bytes" message when I gave 3 Gig tile cache to GIMP (it took about 500 | Meg for other stuff, so I settled with 2.5 GB tile cache and still got a | 3 Gig swap file plus 3 Gig memory usage). If you are using IA32, on linux, then yes there is a 3 Gig limit on per-process memory. 1 gig for the kernel and 3 gigs for the process. If you are using Opteron, Itanion, Power4, G5, UltraSPARC, or Athalon 64, then you don't have that limit. - -- Dan -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.3 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQE/cf4yad4P1+ZAZk0RAhT6AKCWSVCrb8iqNDsBRamHFOyxrkvuqACfVS5t ZYYakwlna9ufenHocYObxYc= =54ge -END PGP SIGNATURE- ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Kudos to The GIMP Developers!
On 24-Sep-2003, Tino Schwarze wrote: > BTW: Is it possible that there is a 3 Gig limit on per-process memory? > The machine has 6 GB, no ulimits and I got a "could not allocate x > bytes" message when I gave 3 Gig tile cache to GIMP (it took about 500 > Meg for other stuff, so I settled with 2.5 GB tile cache and still got a > 3 Gig swap file plus 3 Gig memory usage). Its up to how your os and processor arch works. Like, x86 has a limit of 4 gigs per process, and Linux is defaultly setup for something like 3 gigs for the process, 1 for the kernel. You could be hitting that. -- Patrick "Diablo-D3" McFarland || [EMAIL PROTECTED] "Computer games don't affect kids; I mean if Pac-Man affected us as kids, we'd all be running around in darkened rooms, munching magic pills and listening to repetitive electronic music." -- Kristian Wilson, Nintendo, Inc, 1989 signature.asc Description: Digital signature
Re: [Gimp-developer] Kudos to The GIMP Developers!
Hi, [EMAIL PROTECTED] (Tino Schwarze) writes: > BTW: Is it possible that there is a 3 Gig limit on per-process memory? > The machine has 6 GB, no ulimits and I got a "could not allocate x > bytes" message when I gave 3 Gig tile cache to GIMP (it took about 500 > Meg for other stuff, so I settled with 2.5 GB tile cache and still got a > 3 Gig swap file plus 3 Gig memory usage). On a 32bit platform a single process cannot allocate more than 4GB so I guess you've been hit by that limit somehow. You will need a 64bit architecture in order to address memory beyond 4GB. We haven't tested this but if you were using a 64bit platform GIMP-1.3 should allow you to extend the tile cache beyond 4GB even. Sven ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
Re: [Gimp-developer] Kudos to The GIMP Developers!
So the huge image you generated is a fractal? Isn't it a bit silly to render such images (especially if they are huge) with GIMP, where all of the image's pixels are kept in memory (or the tile cache) all the time? Aren't many fractals such that you could calculate the value of each pixel independently of the others, with a very simple and minimal (non-interactive) program? (And if your desired output file format is PostScript, why not let the printer do the job ;-) PostScript is after all a programming language... Just send the printer a PostScript program that calculates the desired image. For many fractals, it might be surprisingly short.) --tml ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
[Gimp-developer] Kudos to The GIMP Developers!
Hi there, I'd just like to say: Well done. I managed to create a A1 poster at 600 dpi - a whopping 1.1 Gig of picture data (about 2x14000 pixels). While GIMP 1.2.4 crashed while rendering the fractal, GIMP 1.3.20 managed to get it done and even save it as Postscript. Weehee! BTW: Is it possible that there is a 3 Gig limit on per-process memory? The machine has 6 GB, no ulimits and I got a "could not allocate x bytes" message when I gave 3 Gig tile cache to GIMP (it took about 500 Meg for other stuff, so I settled with 2.5 GB tile cache and still got a 3 Gig swap file plus 3 Gig memory usage). Bye, Tino. -- * LINUX - Where do you want to be tomorrow? * http://www.tu-chemnitz.de/linux/tag/ ___ Gimp-developer mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-developer
