Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Texgen.js – Lightweight Procedural Texture Generator

github.com

Post reply on HN
Print view View original

11–20 of 22 posts

Re: Texgen.js – Lightweight Procedural Texture Generator

#11

Post by BoppreH »

mrdoob2 wrote: post #7
BoppreH wrote: post #4

Earlier quoted context omitted.

Correct. But my doubts are over the output of the software. On one hand, the output depends on your artistic instructions, so you are entitled to it. On the other hand, the tool greatly restricts the solution space, so the tool itself (and consequently its author) has artistic merit over the result.

I think a simple way to explain the MIT license is that you can do whatever you want with it as long as you don't say that you created the library yourself. Textures that you create are as yours are images you create in Photoshop. Probably even more yours than that ;)

Oh, hello mrdoob.

My doubt is about authorship. If I make a texture with texgen, can I claim to be the author? Probably yes, but where do we draw the line? If I create a Minecraft world by selecting a single seed, and take a slice of the world as a 2D image, can I claim authorship? What if I didn't even change the seed, just pressed "create"?

I think it depends on the country, but thinking about authorship over procedural generators is weird.

Re: Texgen.js – Lightweight Procedural Texture Generator

#12

Post by mrdoob2 »

bgtnhz wrote: post #10
mrdoob2 wrote: post #9

Earlier quoted context omitted.

I did it like this because I wanted to create the drawing loop as efficient as possible, without switches or conditionals. That method gets executed per pixel so the less logic the better. If someone knows a better way I'm all ears!

I fail to see the logic behind optimizing around conditionals when you are running in an interpreted language.

I instrumented the code and using conditionals resulted in 2x the generation time per loop. These loops are executed only once so the VM doesn't have a chance to optimise them.

Re: Texgen.js – Lightweight Procedural Texture Generator

#13

Post by mrdoob2 »

BoppreH wrote: post #11
mrdoob2 wrote: post #7

Earlier quoted context omitted.

I think a simple way to explain the MIT license is that you can do whatever you want with it as long as you don't say that you created the library yourself. Textures that you create are as yours are images you create in Photoshop. Probably even more yours than that ;)

Oh, hello mrdoob. My doubt is about authorship . If I make a texture with texgen, can I claim to be the author? Probably yes, but where do we draw the line? If I create a Minecraft world by selecting a single seed, and take a slice of the world as a 2D image, can I claim authorship? What if I didn't even change the seed, just pressed "create"? I think it depends on the country, but thinking about authorship over proc…

I think this is a different issue...

I couldn't claim authorship of a machine generated work. I would feel better about claiming authorship of something I've spent a while working on and finding combinations until I get something I like.

Do you claim authorship of Photoshop's cloud filter?

Re: Texgen.js – Lightweight Procedural Texture Generator

#14

Post by javajosh »

Wow, what a strange and wonderful little program. I think it's neat how @mrdoob put together a little standard library of functions that can be chained together in a totally understandable abstraction "pass". It's a good project, too, for people who, like me, want to have a good template for doing general pixel-wise manipulation with canvas.

Thanks!

Re: Texgen.js – Lightweight Procedural Texture Generator

#15

Post by gavanwoolery »

mrdoob2 wrote: post #12
bgtnhz wrote: post #10

Earlier quoted context omitted.

I fail to see the logic behind optimizing around conditionals when you are running in an interpreted language.

I instrumented the code and using conditionals resulted in 2x the generation time per loop. These loops are executed only once so the VM doesn't have a chance to optimise them.

I've done similar in the past and can concur that it does have large performance benefits, at least in Chrome where I tested it.

Re: Texgen.js – Lightweight Procedural Texture Generator

#16

Post by SixSigma »

bgtnhz wrote: post #10
mrdoob2 wrote: post #9

Earlier quoted context omitted.

I did it like this because I wanted to create the drawing loop as efficient as possible, without switches or conditionals. That method gets executed per pixel so the less logic the better. If someone knows a better way I'm all ears!

I fail to see the logic behind optimizing around conditionals when you are running in an interpreted language.

Testing beats imagination.

Re: Texgen.js – Lightweight Procedural Texture Generator

#17

Post by flohofwoe »

bgtnhz wrote: post #10
mrdoob2 wrote: post #9

Earlier quoted context omitted.

I did it like this because I wanted to create the drawing loop as efficient as possible, without switches or conditionals. That method gets executed per pixel so the less logic the better. If someone knows a better way I'm all ears!

I fail to see the logic behind optimizing around conditionals when you are running in an interpreted language.

Stating the obvious, but I'm pretty sure that there are no longer any purely interpreting JS engines around, it's all JIT or AOT compiled, so optimizing for a compilation scenario definitely makes sense.

Re: Texgen.js – Lightweight Procedural Texture Generator

#18

Post by Argorak »

BoppreH wrote: post #11
mrdoob2 wrote: post #7

Earlier quoted context omitted.

I think a simple way to explain the MIT license is that you can do whatever you want with it as long as you don't say that you created the library yourself. Textures that you create are as yours are images you create in Photoshop. Probably even more yours than that ;)

Oh, hello mrdoob. My doubt is about authorship . If I make a texture with texgen, can I claim to be the author? Probably yes, but where do we draw the line? If I create a Minecraft world by selecting a single seed, and take a slice of the world as a 2D image, can I claim authorship? What if I didn't even change the seed, just pressed "create"? I think it depends on the country, but thinking about authorship over proc…

The concept you are talking about is the threshold of originality and it is indeed depending on country and a moving target:

http://en.wikipedia.org/wiki/Threshold_of_originality

As an example: if I use a seed to create a grainy texture, it probably isn't original. If I use the same image as a grain filter for a photograph, the result may be original (in a legal sense). Both operations are trivial and just a click of a button (or two), so I think the discussion about the ease is moot in that context.

Re: Texgen.js – Lightweight Procedural Texture Generator

#19

Post by M4v3R »

It's worth mentioning that Mr.doob (author of this code) is also an author of three.js graphics library and many astonishing demos. Check out his Github and home page (http://mrdoob.com) for (many) more interesting things!

Example: http://mrdoob.github.io/three.js/examples/webgl_terrain_dyna...

Re: Texgen.js – Lightweight Procedural Texture Generator

#20

Post by chengsun »

BoppreH wrote: post #2

Those are very beautiful. I played around, but could not create anything interesting. Adding the source for each sample, not only the first, could be a great addition. I have absolutely no idea how to achieve the effect of #7 or #8, for example. And I never understood the copyright status of this stuff. If I use texgen to create a texture, is it mine or mrdoob's?

The source for each sample is all in index.html: https://github.com/mrdoob/texgen.js/blob/master/index.html
Post reply on HN