Re: [Gimp-user] interactive batch processing

2018-12-09 Thread Gary Aitken

On 12/9/18 4:38 PM, Bob Long wrote:

Gary Aitken wrote on 10/12/18 4:50 am:

...

Is there a way to do one of the following:

A. Start gimp with a list of file names to process, and have it
load only the first on the list.  Then when one quits or closes the
image, load the next one, etc?

B. I can feed the list of file names to a python-fu script, which
then can open and display the image.  Is there a way for a
python-fu script to wait for, or be notified of, the closing of an
image display?  This would allow the script to effectively pause
and allow processing before opening each successive image.
gimp-context-push/pop seem like they may somehow enable this but
it's not clear to me how they are used.

...

Have a look at this script:

http://gimpchat.com/viewtopic.php?f=9=4846=183034=sequential_processing#p183034


On 12/9/18 7:06 PM, Akkana Peck wrote:

Gary Aitken writes:

...

Is there a way to do one of the following:

A. Start gimp with a list of file names to process, and have it load only
the first on the list.  Then when one quits or closes the image, load
the next one, etc?


I don't know of one, though I would find it useful -- when processing
a lot of images from a photo outing, for instance.


B. I can feed the list of file names to a python-fu script, which then can
open and display the image.  Is there a way for a python-fu script to
wait for, or be notified of, the closing of an image display?  This
would allow the script to effectively pause and allow processing before
opening each successive image.  gimp-context-push/pop seem like they
may somehow enable this but it's not clear to me how they are used.


I don't know of a way to do that. However, you could do something like:

def wait_until_image_closed(filename):
 '''Poll GIMP's image list, return when there's no longer an
open image connected to filename.
 '''
 while True:
 for img in gimp.image_list():
 if img.filename == cur_filename:  # or whatever test you want
 return
 time.sleep(1)

Or better yet, get the current image before starting the loop, then
loop until that image is no longer in the image list.

I know polling is slightly icky, but I've done it in several GIMP
Python plug-ins when there was no notification available.

For this task, though, I'd be tempted to use an easier approach:

Start GIMP (with no files yet).

In a shell window, cd to the directory with the files I want to
process, and do this (with whatever list of files you want):

for fil in *.jpg; do
   gimp $fil
   read x
done

The first file comes up as a GIMP window. Process it, and when
you're ready for the next image, go to the shell window and hit
return, and the next file comes up in GIMP.

It's not quite as clean since you still have to hit return for each
image, but that's still a lot easier than navigating to each new image
in the File->Open dialog.


Thanks both of you for your suggestions and pointers.  I think all of
those will enable me to work out a solution.

Thanks again.

Gary
___
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] interactive batch processing

2018-12-09 Thread Bob Long
Gary Aitken wrote on 10/12/18 4:50 am:
> In the past I have interactively batch processed images via a shell
> script
> that invokes gimp for each image.  This is both inconvenient and slow.
> Inconvenient because there are parameters I need to enter into some
> python-fu
> scripts that are the same for each of the images, and slow because of the
> gimp startup and shutdown each time.
>
> Is there a way to do one of the following:
>
> A. Start gimp with a list of file names to process, and have it load only
>    the first on the list.  Then when one quits or closes the image, load
>    the next one, etc?
>
> B. I can feed the list of file names to a python-fu script, which then
> can
>    open and display the image.  Is there a way for a python-fu script to
>    wait for, or be notified of, the closing of an image display?  This
>    would allow the script to effectively pause and allow processing
> before
>    opening each successive image.  gimp-context-push/pop seem like they
>    may somehow enable this but it's not clear to me how they are used.
>
> It seems like gimp-display-get-window-handle might be useful somehow, if
> there were a means to be notified when the window is destroyed.
>
> Any thoughts / hints would be much appreciated.

Have a look at this script:

http://gimpchat.com/viewtopic.php?f=9=4846=183034=sequential_processing#p183034

Maybe that will do what you want.

-- 

Bob Long


>
> Thanks,
>
> Gary
___
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] interactive batch processing

2018-12-09 Thread Gary Aitken

In the past I have interactively batch processed images via a shell script
that invokes gimp for each image.  This is both inconvenient and slow.
Inconvenient because there are parameters I need to enter into some python-fu
scripts that are the same for each of the images, and slow because of the
gimp startup and shutdown each time.

Is there a way to do one of the following:

A. Start gimp with a list of file names to process, and have it load only
   the first on the list.  Then when one quits or closes the image, load
   the next one, etc?

B. I can feed the list of file names to a python-fu script, which then can
   open and display the image.  Is there a way for a python-fu script to
   wait for, or be notified of, the closing of an image display?  This
   would allow the script to effectively pause and allow processing before
   opening each successive image.  gimp-context-push/pop seem like they
   may somehow enable this but it's not clear to me how they are used.

It seems like gimp-display-get-window-handle might be useful somehow, if
there were a means to be notified when the window is destroyed.

Any thoughts / hints would be much appreciated.

Thanks,

Gary
___
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] [Gimp-developer] FW: different Vignette parameters 2.8 vs 2.10

2018-12-09 Thread Henk Koning via gimp-user-list
Dear All,

Today I have been able to fine tune the vignette in 2.10 just as I like it to 
be. Don't know what put me off on previous attempts... 

I apologize.

I propose to cancel this issue.

Henk

-Original Message-
From: gimp-developer-list  On Behalf Of 
Alexandre Prokoudine via gimp-developer-list
Sent: vrijdag 7 december 2018 07:27
Cc: gimp-developer 
Subject: Re: [Gimp-developer] FW: different Vignette parameters 2.8 vs 2.10

пт, 7 дек. 2018 г., 5:50 Owen erote:

> Hi,
>
>
> Not a developer, but I note that in 2.10.6  it is described as a gegl 
> operation. I cannot find Vignette in 2.8.22


Tools > GEGL tool

Choose Vignette in the drop-down list.

Alex
___
gimp-developer-list mailing list
List address:gimp-developer-l...@gnome.org
List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list
List archives:   https://mail.gnome.org/archives/gimp-developer-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