Re: Composition rendering time instance

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



hi,

Danko Dolch schrieb:
> What about taking the cache with you? e.g. switch to another workstation
> - would be cool to have an option to store the cache external too...

cool, yes. But even more "corner cased" than the case of very expensive
compositions already is for GIMP.


> yahvuu wrote:
>> Personally, i wouldn't mind to assign some GBs to GIMP in order to make my
>> life easier. Those who do mind, could set the 'persistent cache' size to zero
>> in order to make shure GIMP cleans up when closing the session.
>>   
> That would be fine - question is:
> 
> a) save only the final image
> 
> b) save all the results of the GEGL graph nodes during a session so that
> not all nodes have to be calculated if only the last one is changed...
> 
> c) create a dedicated "cache" or "proxy" node that can be assigned by
> the user

a) only the tree gets saved. The final image aka full resolution bitmap gets
   only created when exporting (e.g. to JPEG). This bitmap is then available
   from the disk cache in case subsequent actions need it. In the example,
   that was exporting again to a different file format.

b) yep, that's what the disk cache should do (for expensive calculations)
   and ideally this data should persist across editing sessions.

c) This is a very interesting idea. Allow me to translate for GIMP, a better
   name would probably be something like a "render full resolution" operation.

   - "render", because GEGL cares for all necessary caching automatically
     during editing (please correct me if i'm wrong).
     So for GIMP, the real purpose is to save some intermediate results
     together with the composition, that is to render them.
     (During editing the full resoluton will almost never get rendered
      when the screen is smaller than the image size)

   - "operation", because GIMP will not expose the GEGL tree on the UI,
     but instead will have linear operation chains.

So indeed, that's a cool way to give the user fine-grained control about
how much (redundant) rendered data should be saved with the composition.

That's clearly an expert feature, so it won't hurt much if it has to be
controlled by some 'scary' operation.

... i'm convinced now.



greetings,
peter

_______________________________________________
Gimp-developer mailing list
Gimp-developer@xxxxxxxxxxxxxxxxxxxxxx
https://lists.XCF.Berkeley.EDU/mailman/listinfo/gimp-developer

[Index of Archives]     [Video For Linux]     [Photo]     [Yosemite News]     [gtk]     [GIMP for Windows]     [KDE]     [GEGL]     [Gimp's Home]     [Gimp on GUI]     [Gimp on Windows]     [Steve's Art]

  Powered by Linux