Re: [Gimp-user] When black and white is not black and white
You may try Colors -> Component -> Decompose, then select LAB space, BW image is the L, thats a lot better than anything else I have tried Regards -Original Message- From: LancerTo: gimp-user-list@gnome.org Cc: notificati...@gimpusers.com Date: Tue, 06 Jun 2017 06:02:29 +0200 Subject: [Gimp-user] When black and white is not black and white I am a school teacher. One of the checks I ask students to do in order to test the contrast of their graphics work, is to convert the images to grayscale and see whether images are still clear. There are two methods students are using to convert their images to grayscale for this test... Method 1: flatten image, then Colors > Hue-Saturation => slide the saturation slider down to zero. Method 2: image => mode => grayscale Either of these methods results in a grayscale image, but the grays are not exactly the same. For example, if I have absolute red (#FF) next to blue, the grayscaled-blue may match the grayscaled-red depending on the tone *and* the method used. Method 1: Absolute red (#FF) will grayscale-match absolute blue (#FF) Method 2: Absolute red (#FF) will grayscale-match a slightly lighter shade of blue (#2626FF) Why are the two methods of grayscale having a different result? I would have thought that conversion to grayscale would be the same process as dragging down the saturation of an image. ...and given that they are different, which is the better method to use in terms of testing for contrast in media assignments? -- Lancer (via www.gimpusers.com/forums) ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] UFRAW - what am i missing?
UFRaw is not currently working in any 64 bit windows systems Regards 2016-04-19 8:08 GMT-04:00, Ofnuts: > > UFRaw is not preinstalled. Some builds (by Partha) may include UFRaw, > but this is normally an add-on. > > On 15/04/16 16:16, sjemmett wrote: >> I've just upgraded from 2.8.14 to 2.8.16. As i recall reading in the >> documentation, 2.8.16 has ufraw preinstalled. I've tried to edit a .NEF >> (nikon) >> raw file with no joy. I can edit the same .NEF file in 2.8.14. >> >> any idea what I'm missing? >> >> tnx >> > > ___ > gimp-user-list mailing list > List address:gimp-user-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list > List archives: https://mail.gnome.org/archives/gimp-user-list > ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] Clone Tool
I joined to this enhancement request with a slightly different proposal, instead of a moving point to clone (which is the actual behavior) it would be better a full warp deformable cloning area for the clone tool. For Domster, here is your solution 1. duplicate the layer 2. Rotate the duplicated layer (or warp transform it) 3. place a mark with the clone tool on duplicated layer 4. select original layer and start cloning. This is what the enhancement shall do in background happy gimping! Alex 2015-12-23 20:20 GMT-05:00, Domster: > Hello, > > i need the clone tool very often. In PS you can rotate the cloned part > before > starting to use the tool. This is very helpful when for example you want to > fix > some flashlights in the iris of an eye. I can't find something similar in > Gimp. > Is there a solution? > > Thank you! > > Rainer > > -- > Domster (via www.gimpusers.com/forums) > ___ > gimp-user-list mailing list > List address:gimp-user-list@gnome.org > List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list > List archives: https://mail.gnome.org/archives/gimp-user-list > ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] Can't open nef images in gimp 2.9.3
Dear Partha 2015-12-21 12:19 GMT-05:00, Partha Bagchi: > Alex, > > 1. Open GIMP 2.9.3 > 2. Open the File Dialog (File -> Open) > 3. From the drop down list, click on raw image ( File type = raw > image, Extension = 3fr, ari, arw, cap, cine, cr2, etc.) > 4. Open your NEF image. > > This will open UFRaw and then do your processing and then open it in GIMP. > > Tell me if this does or does not work. I just tested it and it's fine. > > You are correct that NEF itself is broken and I'll investigate why. > > Thanks, > Partha > When trying this procedure indeed, the ufraw soft is launched but it says TIFF image error Unknown field with tag 36867 (0x9003) encountered So I think it tries to open it as a TIFF image. Eventhough it still opens the image as thumbnail, very odd. Regards Alex ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
[Gimp-user] Can't open nef images in gimp 2.9.3
Hello One of the greatest things of the new gimp 2.9.3 is the handling of nef files (raw camera images), they even appear in the file format list, great! But in my windows 8 x64 bits with Partha's build it just doesn't open, when trying to do that GIMP says image can't be opened, but i can open the image even on windows photo software (the one that is fullscreen) and it is ok. I dont know if this is a bug of GIMP or something specific to windows so i'll wait until someone else can duplicate this issue. Regards Alex ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] Can't open nef images in gimp 2.9.3
2015-12-21 11:36 GMT-05:00, Partha Bagchi <parth...@gmail.com>: > On Mon, Dec 21, 2015 at 11:12 AM, Alex Vergara Gil > <alexvergara...@gmail.com> wrote: >> 2015-12-21 9:54 GMT-05:00, Alexandre Prokoudine >> <alexandre.prokoud...@gmail.com>: >>> On Mon, Dec 21, 2015 at 5:44 PM, Elle Stone wrote: >>> >>>> Using default GIMP 2.9.3 updated a couple of days ago on Linux, and >>>> opening >>>> a CR2 file, the resulting image is the correct size, and only 8-bits >>> >>> https://sourceforge.net/p/ufraw/feature-requests/274/ >>> >>> Unsure if this made it to 0.20+ though. And anyway, there have been no >>> installers of UFRaw for Windows for a long time (0.19.2 was the last >>> one, and it was before the aforementiond patch). >>> >>> Alex >> >> Yes Elle, thats a bit different error, but still an error. Is there >> some official suport for NEF files inside GIMP, maybe through GEGL? >> >> Alex > Yes, there is only for NEF. If you are using my build then select NEF > image, it should open a 32-bit floating rendition. > > Bottom line as I said below, don't use the automatic detection feature. > Dear Partha Thank for your reply, and for your daily builds!, I can confirm both ways: 1. open NEF files with automatic detection yiels an error, gimp cant open image 2. selecting nef file in the list yields an image, but only a tiny little thumbnail, as Elle said before So this might be a bug, are you handling nef files with some plugin? Regards Alex ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] Can't open nef images in gimp 2.9.3
2015-12-21 9:54 GMT-05:00, Alexandre Prokoudine: > On Mon, Dec 21, 2015 at 5:44 PM, Elle Stone wrote: > >> Using default GIMP 2.9.3 updated a couple of days ago on Linux, and >> opening >> a CR2 file, the resulting image is the correct size, and only 8-bits > > https://sourceforge.net/p/ufraw/feature-requests/274/ > > Unsure if this made it to 0.20+ though. And anyway, there have been no > installers of UFRaw for Windows for a long time (0.19.2 was the last > one, and it was before the aforementiond patch). > > Alex Yes Elle, thats a bit different error, but still an error. Is there some official suport for NEF files inside GIMP, maybe through GEGL? Alex ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
Re: [Gimp-user] ai files in gimp
Dear Liam Thats exactly my problem, fonts are not converted properly, even when the same font is installed in my system, it just puts the rendered text without transparency overlapping the enclosure, also enclosures are rendered wrongly (smaller than should be). It seems a conversion problem, but I know going from vector to bitmap is not straightforward. Thats the main reason why i wanted GIMP to handle vector layers, with a final preview and some control from users side about the final conversion. Regards Alex 2015-12-03 0:53 GMT-05:00, Liam R. E. Quin <l...@holoweb.net>: > On Tue, 2015-12-01 at 15:21 -0500, Alex Vergara Gil wrote: >> Hello! >> >> Is there a way of importing ai files into gimp? > > I've used inkscape on the commandline (in Linux) to convert ai files to > png in the past, and it's worked fairly well as long as I have the > right fonts installed. > > How were you converting the files to PNG? What problems did you have? > Can you share a sample file? > > (ignore if you've already solved it all!) > > Liam > > -- > Liam R. E. Quin <l...@holoweb.net> > > ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
[Gimp-user] ai files in gimp
Hello! Is there a way of importing ai files into gimp? I know i canuse them in inkscape but i need to insert some figures in my project, i need them to be very resolutive but converting them to png is not what i expect, results are a disaster. Any hints? Regards Alex ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list List archives: https://mail.gnome.org/archives/gimp-user-list
[Gimp-user] feature request: alpha level
Hello GIMP developers: I am working on a project where I need to set all pixels below a level as alpha channel, is there a quick way to achieve this? The level can be both set a priori or adjusted dinamically, the second way is prefered. Right now my workflow includes: 1. duplicate layer. 2. use color level in duplicate layer, in menu COLOR - LEVEL. 3. add alpha mask to original layer 4. copy duplicate layer into the alpha mask of the original. 5. delete duplicate layer. 6. If result is not ok then return to 1. As you can see this workflow is a headache, specially point 6 which is often achieved. Any thoughts Alex ___ gimp-user-list mailing list List address:gimp-user-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-user-list
[Gimp-user] Fw: A Sad case of regression.
You've never heard of Adobe Premiere, Kdenlive, Apple Final Cut, Apple Logic, Audacity, Cubase, Ardour, Blender? That's OK. Now you have Using the examples of video editing packages is rather disingenuous as they are all project based programs that work on the expectation of combining multiple files and outputting in a different format. A very different case. Not so different: Imagine that you have a jpg image and you want to add a png layer to it then in which format the GIMP must save the work.yeah xcf. So I really think xcf shall be the default save option, now when you speak of save as things became philosophycal in which definition of what save as means is primordial. So to avoid all of this the export way is OK. Care to give any examples of the genre of image editing programs that insist on defaulting to working on intermediate formats ? What became annoying here is that GIMP means GNU IMAGE Manipulation Program, not GNU XCF Manipulation Program. So the only annoying thing that remains is the name, but I think for historical reasons it shouldn´t be changed. As for programs that work on intermediate formats, I think every other program do this, even photoshop (remember psd). Sometimes it's better to accept a program's development has gone wrong and return it to a more acceptable workflow that matches the expectations of it's users. Sometimes it´s better to accept a program´s user has gone wrong and accept the correct workflow that allows more productivity and less mistakes. I speak for myself here, since I was a detractor of this way of save/export and now I can live better thank to this kind of workflow. Paul Holman www.colourprofiles.com ___ ___ gimp-user-list mailing list gimp-user-list@gnome.org https://mail.gnome.org/mailman/listinfo/gimp-user-list
Re: [Gimp-user] HATE the new save vs. export behavior
El 03/05/2012 09:42 a.m., Richard Gitschlag escribió: I'm on the fence. On one hand, I fully understand the reason for this change; on the other, it's such a sudden change (compared to every previous version of GIMP ever) that it CAN (and, really, should) be handled better: When you use the Save As command and type a filename other than XCF, I would personally want to see, instead of simply telling you that Save is only for GIMP's native .xcf format and use the Export command for other formats, give it a prompt -- have it ask something like 'Save' uses GIMP's internal image format only - would you like to Export a copy in [file format]? [export / cancel] Likewise, if you've opened up an image from a non-XCF format, the Save (not Save As) command should ask whether you intend to save the file in GIMP's native XCF format or re-export it back to the original file format. (Current behavior is to pop up the Save As dialog box, just the same as with a new image -- which tends to result in situation #1 described above) -- Stratadrake strata_ran...@hotmail.com Numbers may not lie, but neither do they tell the whole truth. +1 with this this seems to be the best approach I've seen in this discussion Alex From: maur...@bcs.org.uk To: gimp-user-list@gnome.org Date: Thu, 3 May 2012 15:53:31 +0100 Subject: Re: [Gimp-user] HATE the new save vs. export behavior On Thursday 03 May 2012 10:15:29 Jay Smith wrote: when editing a JPG, repeatedly saving/exporting to JPG (your step 4) reduces the quality (actually compresses / deletes data). Having been away I've just been reading this thread, and would like to add my wish to those others who are unhappy at the sudden change in the Save dialogue. In my case, I am not repeatedly saving/exporting' to JPG, but only once per image (to write annotation), and I would guess that applies to many other users of Gimp - though possibly a minority. Having thus introduced myself to the wonderful Gimp, I am tempted to go on to make use of more powerful functions. Is there really no room for a simple compromise that would satisfy both the more professional and the more casual users? Where there's a will there's a way... Regards, -- /\/\aurice (Retired in Surrey, UK) ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list ___ gimp-user-list mailing list gimp-user-list@gnome.org http://mail.gnome.org/mailman/listinfo/gimp-user-list