[Bf-committers] Texture synthesis node

[Vilem Novak]

Hello, 
I agree with this to some extent. 
As you might know i made some nodes (bilateral, bas-relief), 
and was thinking about developing some more - normalmap to displacement conversion, 
frequency based image tuning, maybe erosion algorithm for terrain generation.

I think image editing features are exactly what the compositor does.
There might be confusion in the name 'compositor', which assumes 
that this blender window is specifically for postproduction,
while it's allready a very versatile image processing tool.

The reasons for having such tools inside blender are these:

Direct pipeline integration - e.g. bilateral blur has usually 1 input(gimp has something similar), while in 
blender there are 2 inputs for direct pass input, and allow much more this way. And being originally an 
image editor tool, it suits very well for postprocessing tasks too.

Floating point precision - When I had bas-relief code externally, there were many problems with keeping the 
depth of the saved z-buffer and other trouble with formats, while in blender it just works like charm. 
Similar is with bilateral blur 'determinator' input.

Faster preview and feedback - we allready have a node to convert
 images to normalmaps, and I can imagine texture synthesizer
would be usefull because you could tweak the results seeing them 
directly on the mesh. Same could be with the nodes I mentioned I
would like to code sometime.
by the way I'd love to see animated textures getting synthesized :)

On the other side, disadvantage is the unnecessary code duplicity around
various graphic tools(gimp & blender). This might get in future solved
with integration of gegl? This was several times mentioned on 
irc, but so far is just an idea. 

Cheers, 
Vilda



> ------------ Původní zpráva ------------
> Od: Tyler Tricker <tntricker at gmail.com>
> Předmět: Re: [Bf-committers] Texture synthesis node
> Datum: 25.6.2009 01:20:53
> ----------------------------------------
> I think image editing features should be left to dedicated image software
> packages like gimp.
> 
> On Wed, Jun 24, 2009 at 7:06 AM, Wahooney <wahooney at wahooney.net> wrote:
> 
> > There is a plugin for GIMP that does this sort of thing very well, in
> > fact it's based on the paper that you've linked to. So for this
> > technique external may be better.
> >
> > However, a better idea would be another technique that maps the texture
> > straight to the mesh, I read about it a few years ago. It's very robust
> > and the results are quite amazing. I'll look for the paper and post it
> > here when I find it.
> >
> > Keith
> >
> > Aurel W. wrote:
> > > Hi,
> > >
> > > I was wondering if texture synthesis from images would be of use in
> > > texture nodes, or if it's better not to integrate this and do it with
> > > external tools. Implementing
> > > http://www.cc.gatech.edu/cpl/projects/graphcuttextures/ may be a good
> > > option. Depending on the type of algorithm and settings used,
> > > calculating such textures can take some time and I am concerned, if
> > > nodes which would take about 10-20 seconds or so to compute, still fit
> > > good into a node editor.
> > >
> > > What do you think, would this even be of use?
> > >
> > > Aurel
> > > _______________________________________________
> > > Bf-committers mailing list
> > > Bf-committers at blender.org
> > > http://lists.blender.org/mailman/listinfo/bf-committers
> > >
> > >
> > _______________________________________________
> > Bf-committers mailing list
> > Bf-committers at blender.org
> > http://lists.blender.org/mailman/listinfo/bf-committers
> >
> _______________________________________________
> Bf-committers mailing list
> Bf-committers at blender.org
> http://lists.blender.org/mailman/listinfo/bf-committers
> 
> 
>