Re: [Gimp-user] GIF animation automation and revert diff

2012-10-30 Thread Bgs


 Thanks Rob! These look really great. I'll give them a try :)

Regards
Bgs

On 10/25/2012 05:38 PM, Rob Antonishen wrote:
Take a look at AnimStack http://registry.gimp.org/node/26501which 
provides a whole batch of features for creating animations.


And to revert a diff animation layer stack, try the unoptimoze filter 
http://docs.gimp.org/2.8/en/plug-in-optimize.html


-RobA

-
Quae dissolvi non possunt.


*From:* Bgs b...@bgs.hu mailto:b...@bgs.hu
*To:* gimp-user-list@gnome.org mailto:gimp-user-list@gnome.org 
gimp-user-list@gnome.org mailto:gimp-user-list@gnome.org

*Sent:* October 25, 2012 8:30 AM
*Subject:* Re: [Gimp-user] GIF animation automation and revert diff

   Ok... just to clarify. It seems there are no ideas so I actually do
have to develop it myself... :)

Bests
Bgs


On 10/09/2012 09:58 PM, Bgs wrote:

  Hi,

 I've been playing a bit with GIF animations and there are two things
 I'd like to do but haven't found any trivial solution for.

 1) I have a background type of layer and several smaller ones. I want
 to make an animation where these additional layers appear and
 disappear. The hard way to animate this is to duplicate the background
 and merge in all variations I want and create an animation from that.
 This has three drawbacks: a) It's a rather long handiwork to do it b)
 by default it produces a full-frame animation that needs to be
 optimized c) the default differential optimization might not produce
 the best result in terms of size.

 My question for the more experienced ones is: Is it possible to script
 creation of such images without creating a full fledged plugin?
 Example: I have background and layer1 through layer8 as small
 overlaying layers. I want to create a blinking/glowing effect by
 turning on and off layer1-8 in a random(like) way. Let's say I create
 a dozen of such layer on/offs and cycle the result as a GIF animation.

 2) Once I created an optimized GIF animation (differential) is there
 an easy way to convert it back to a full-frame layer structure? (This
 has practical sense for example with a couple of frames taken from a
 video).

 Thanks
 Bgs

 ___
 gimp-user-list mailing list
gimp-user-list@gnome.org  mailto:gimp-user-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-user-list


___
gimp-user-list mailing list
gimp-user-list@gnome.org  mailto:gimp-user-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-user-list


___
gimp-user-list mailing list
gimp-user-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-user-list


Re: [Gimp-user] GIF animation automation and revert diff

2012-10-25 Thread Bgs


 Ok... just to clarify. It seems there are no ideas so I actually do 
have to develop it myself... :)


Bests
Bgs


On 10/09/2012 09:58 PM, Bgs wrote:


 Hi,

I've been playing a bit with GIF animations and there are two things 
I'd like to do but haven't found any trivial solution for.


1) I have a background type of layer and several smaller ones. I want 
to make an animation where these additional layers appear and 
disappear. The hard way to animate this is to duplicate the background 
and merge in all variations I want and create an animation from that. 
This has three drawbacks: a) It's a rather long handiwork to do it b) 
by default it produces a full-frame animation that needs to be 
optimized c) the default differential optimization might not produce 
the best result in terms of size.


My question for the more experienced ones is: Is it possible to script 
creation of such images without creating a full fledged plugin? 
Example: I have background and layer1 through layer8 as small 
overlaying layers. I want to create a blinking/glowing effect by 
turning on and off layer1-8 in a random(like) way. Let's say I create 
a dozen of such layer on/offs and cycle the result as a GIF animation.


2) Once I created an optimized GIF animation (differential) is there 
an easy way to convert it back to a full-frame layer structure? (This 
has practical sense for example with a couple of frames taken from a 
video).


Thanks
Bgs

___
gimp-user-list mailing list
gimp-user-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-user-list



___
gimp-user-list mailing list
gimp-user-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-user-list


Re: [Gimp-user] multi-threaded Gimp

2012-10-19 Thread Bgs


 Hi,

On 10/19/2012 10:29 PM, Liam R E Quin wrote:



so if one would allocate a target memory area in RAM first and then fill the
mem map with the to-be-saved data one could open a file handle right from the
start and copy the mem portions to disk as they get filled by the compression
algo.

The problem with this is that you don't know in advance how much memoro
to allocate or where to write, because the compression varies depending
on patterns of light and dark (for example) in the image.


I've never actually coded png compression so correct me if I'm wrong.

If you have n cores. You allocate n blocks of memory assuming worst 
compression outcome and start to parallely compress blocks you only use 
a reasonably small amount of memory. (n times the worst case size of a 
png tile). For each block that is ready and can be appended to the disk 
file, you write out the block ans start to compress the next unhandled 
block. Of course this is asynchronous as some blocks will finish to 
compress before the next-to-be-written-out is still working, but you 
still speed up compression by a big factor and still have a small and 
static compression buffer.


If you add a write-out-queue you can achieve a more effective 
parallelism while still limiting memory usage.


Just my 2c.

Bye
Bgs





Or another approach would be make a copy of the image in RAM and do the save
in the background. That way when using the same file name one would even
narrow the state transition of the file to a minumum.

It's done in a separate process right now, but copying the image in
memory, if it's, say, a one gigabyte image, might be problematic. And
the images that need to be sped up are the fast ones.

It might be faster in some cases for gimp to do a merge visible layers
before a save, I don't know.

Liam



___
gimp-user-list mailing list
gimp-user-list@gnome.org
https://mail.gnome.org/mailman/listinfo/gimp-user-list