Re: [Gimp-user] Fixing Hot/Stuck/Dead Pixels?
> > I have a digital camera which has developed a few stuck pixels and > > I'd like to automate the process of fixing them. > > > > I figure I can create either a bitmap with said pixels set or a > > text list of pixel coordinates, but how can I get Gimp to do an > > interpolation of the surrounding pixels at each of those points? > > If you have your bitmap with the dead pixels ready: > - add it as a layer to your photo. > - select by color, pick the color of the good pixels > - invert selection > - move to photo layer > - expand selection by 1 pisel (selection->expand) > - Gassusian blur (filter->bluer->gaussian blur) The blur, however, will still take in to account the value of the bad pixel, right? Is there any way to avoid that? > And..on gimp-devel, people are talking of a soon-to-be-reality macro > recorder that will let you automate this without typing a single line > of code. I was thinking of writing a plug-in and making use of some of the advanced interpolation algorithms present in the "panorama tools" suite, but that's a fair amount of work and a bit more than I'd like to bite of as a first attempt at such things. Brian ( [EMAIL PROTECTED] ) --- He who has infinite patience sees instant results. ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Fixing Hot/Stuck/Dead Pixels?
let me suggest thinline.c available at the registry. carol Brian White wrote: I have a digital camera which has developed a few stuck pixels and I'd like to automate the process of fixing them. I figure I can create either a bitmap with said pixels set or a text list of pixel coordinates, but how can I get Gimp to do an interpolation of the surrounding pixels at each of those points? Thanks! Brian ( [EMAIL PROTECTED] ) --- Until we are first independent, we cannot be interdependent. ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Fixing Hot/Stuck/Dead Pixels?
I have a digital camera which has developed a few stuck pixels and I'd like to automate the process of fixing them. I figure I can create either a bitmap with said pixels set or a text list of pixel coordinates, but how can I get Gimp to do an interpolation of the surrounding pixels at each of those points? Thanks! Brian ( [EMAIL PROTECTED] ) --- Until we are first independent, we cannot be interdependent. ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Hex Drawing
Ok, script on it's way, hmm.. I think I will just write a Python plugin for drwaing the hexes straight into The Gimp. It seens that people like it at all. And yes, when I first designed this script, it was also for drawing a board for a game. :-) Regards, JS -><- Mike wrote: Wow! That sounds really cool. Handy too. Could you possibly send me your script? A friend of mine likes to make board games and having a hex generator would be sooo helpful... Thanks, ~Mike ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Hex Drawing
On Tuesday 01 July 2003 17:12,Mike Thorn wrote: > I'm a little unfamiliar with PostScript, being new to Linux and > all. Can you tell me what that is and how your postscript file > interacts with GIMP? For a short answer: a Postscript file is a file in the Programing language called postscript, that is human readable if open in a text editor, and which is executed and generates a drwaing, when open in an apropriate appllication. The GIMP can open Postscript files as drawings. This script I made is one that renders an hexagon grid. I also have a GIMP plugin taht can save gimp Paths in postscript files that can be open in other such applications. . "In long:" Postscript is a page description language, first devised, almost 30 yeras ago, to be used to print pages. The idea is that the printers themselves should have a way to interpret a postscript program, and the program do generate one or more pages taht are to be viewed. Well, what happens is that a pritner able to proccess a postscript file does have to have not only a computer, but a lot of memory built-in. So, in most Unixes, there is a postscript interpreter taht functions as a printer driver, among other things. All your GUI programs generate postscript files when they are printing. These files are run automatically through the postscript interpreter (unless you do have a postscript enabled printer), which them sends printer data to the printer. This postscript interprter built in Unix and Linux in particular is the Ghostscript program. It's far more versatile than just a printer driver. With a couple of simple commands in postscript one can make beautiful vector drawings - and ghostscript allows saving them to a lot of other picture formats. The GIMP uses the Ghostscript program as a utility to open postscript files as drawings transparently. So, a little program made in postscript to generate a drawing, like an Hex Grid, can be open as if it were a picture. One of the advantages of it over a simple GIF or PNG with an hex grid, is taht a postscript file is human readable (unless generated by a program which deliberately obsfuscates it, like the Windows(tm) postscript drivers or CorelDraw). In particular, in this hex grid script I made, one can change the number of hexes and their size, just by modifing three decimal numbers on the last line of the file, with any text editor. Regards, JS -><- ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Hex Drawing
Hmm. Have not a gimp plugin, but I have wriiten some postscript for it a while ago. All one have to do is open it in The GIMP. I e-mailed Joao Paulo the Postscript file. If anyone else is interested, just write in. Regards, JS -><- On Tuesday 01 July 2003 15:46, João Paulo Vasconcellos wrote: > Hello everybody, > > does anyone knows if there is some kind of script that draws hex > grids ? > > I took a look at the registry, but found no one. > > ___ > Gimp-user mailing list > [EMAIL PROTECTED] > http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
[Gimp-user] Hex Drawing
Hello everybody, does anyone knows if there is some kind of script that draws hex grids ? I took a look at the registry, but found no one. ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Fonts in 1.3.x
Hi Sven, Thanks for the illuminating explanation of the font situation. I will start researching font contents & formats. Regards, -- --Jeff Jeff Trefftzs <[EMAIL PROTECTED]> http://www.tcsn.net/trefftzsHome Page http://gug.sunsite.dk/gallery.php?artist=68 Gimp Gallery http://trefftzs.topcities.com/ Photo Gallery ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
Re: [Gimp-user] Fonts in 1.3.x
Hi, Jeff Trefftzs <[EMAIL PROTECTED]> writes: > For some time now, on both 1.2.x and 1.3.x, I have noticed some > curiosities about the GIMP's font handling. I have downloaded and > installed a number of true-type fonts, most of which work fine, as long > as I run xfstt to serve them up, but a few of these fonts behave > differently depending on which tool I use to view them. > > In particular, using GIMP-1.2.5, the text tool by itself fails to show > any characters for several of my fonts, meaning I can't use them, > although the Freetype tool, while still not letting me use any of the > characters, will at least show them in the character grid. The freetype plug-in uses a completely different architecture to handle fonts. It's not surprising that it behaves differently as X11 font rendering (which is what the text tool in 1.2 uses). > In GIMP-1.3.15, I have similar problems, but now that I'm running > RH-9 (a Gnome-2 system), I find that Nautilus can display *all* of > my fonts, at least to the point of popping up the gnome-font-viewer > when I click on the font file in Nautilus. What are the plans to > unify font handling? I realize this is a horribly hairy problem. For 1.3 the font handling has been unified to the best extent. Nautilus displays the fonts on screen, so it uses the Pango Xft2 backend, while GIMP needs to render bitmaps and uses the Pango FT2 backend. Both backends do however use the same code to manage fonts and they do share the same configuration files. So basically you should be able to use the same fonts and you should get very similar results. There is one exception and that is fonts that do not provide an Unicode character table. Fonts that fail to do that can be considered broken. The Xft2 backend seems to be able to handle some of these fonts by creating an Unicode table from other info in the font. The Pango FT2 backend however fails to load these broken fonts. This probably needs to be improved at the Pango level. Sven ___ Gimp-user mailing list [EMAIL PROTECTED] http://lists.xcf.berkeley.edu/mailman/listinfo/gimp-user
