Use of implementation in art project

[thomasp85]

Hi

I'm a generative artist working on a series of work that require me to implement simplex noise in glsl. I've accepted that I probably wont do as good a job on that as you've already done, so I would like to use your implementation. However, the code of the final project is size-sensitive so I cannot include an MIT license text in it. Will you be ok with me using and modifying (to reduce size) your code for 2D simplex noise without the addition of this text? Since this is an art project that will likely generate sale of the final pieces I'm also very happy to donate a sum to a charity of your choice.

best
Thomas

[stegu]

(Please contact me directly at ***@***.*** for some details I think you will find interesting. It concerns recent unpublished work on improving the noise functions, where we could probably work out some kind of honorary pre-release terms for you to use it in your project.) If every byte counts, which is a situation I fully understand, I would consider it enough if you included a brief acknowledgement somewhere in the documentation, presentation or some other reasonably accessible description of the software but stripped the code clean from most comments, keeping just one line with a simple link to the Github repo. If even that is inconvenient to you, I imagine a special license for personal use in this particular project would be an option. Ian McEwan and I let Ashima Arts claim the formal copyright on our joint work, to allow him to spend work hours on the project. That company no longer exists, but Ian should have a say in it if you need a special license. Let me know if you have trouble including even the line "// github.com/ashima/webgl-noise" in the GLSL code and we can talk further. Your offer to donate some of your profit is appreciated, but that's not a requirement. My choice of charity would be the Free Software Foundation, fsf.org, but I would also say that if you have an art project that generates a profit, cherish the moment and keep at least most of it for yourself! /Stefan

[thomasp85]

Hi Stefan

I appreciate your response. I have no problem in including a link in the source code pointing to this. It was only the full MIT License text that would be prohibitively large. The project will include a long form discussion on the technicalities of the art in which I will surely acknowledge your work. If such a setup is fine with you it is also fine with me. However, if you or Ian prefers a special licensing agreement I'll also be happy to work with you on this. I'll be sure to send some funds towards FSF in your name when the project is released.

I'll also shoot you a mail about the other thing 🙂

Thanks for your time

Thomas

[unicomp21]

@stegu published yet?

[stegu]

In review. If things go the way I hope, publication is imminent.

…

On Wed, 15 Sep 2021, 12:51 John Davis, ***@***.***> wrote: @stegu <https://github.com/stegu> published yet? — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAFGK2S2FWACICRQCEPPPL3UCB3E5ANCNFSM5EA46I3Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[unicomp21]

@stegu published?

[stegu]

Accepted for publication, about to start the final touch-up phase with the editor. Home safe, no need to keep it under cover, but I'd still like the article to be the first public mention of it. If you like, I could send you a sneak preview of the code along with a link to some online examples that are not yet public. Just let me know.

[unicomp21]

That would be great! How do I send my email address privately?

…

On Tue, Nov 2, 2021 at 12:56 PM Stefan Gustavson ***@***.***> wrote: Accepted for publication, about to start the final touch-up phase with the editor. Home safe, no need to keep it under cover, but I'd still like the article to be the first public mention of it. If you like, I could send you a sneak preview of the code along with a link to some online examples that are not yet public. Just let me know. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#26 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAEFL7IRQ5N6S25MROTXBLLUKAQ4JANCNFSM5EA46I3Q> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[stegu]

My private mail address is in no way secret -- I have splattered it willy-nilly all over the Internet already. Mail me on ***@***.*** and I'll send you the sneak preview.

[timmb]

@stegu Is the implementation in psrdnoise2D.glsl the equivalent to the approach in your 2022 paper? ("Tiling Simplex Noise and Flow Noise in Two and Three Dimensions").

It has the same function name but the commit date is earlier than your above comments. Is there a glsl implementation of your 2022 approach available?

Thanks
Tim

[stegu]

The Github link in the paper points to the implementation of the algorithm that is described in the paper. There are some older versions floating around, but my Github repo with the name "psrdnoise" has the version(s) described in the paper. The commit date is earlier because publication takes ages, and most of the repo was finished and online a year before the paper was formally published. The tutorial section could be somewhat later, at least in part. https://github.com/stegu/psrdnoise Thanks for your interest in my work! Let me know if you have any questions. /Stefan Gustavson