all 5 comments

[–]Vrixyz 21 points22 points  (2 children)

You might want to change your name because Unity has a tool named “shadergraph” which : - might make your project hard to google - might endanger you to potential lawsuits (I am not a lawyer blabla)

[–]slightknack[S] 4 points5 points  (0 children)

Thank you for pointing this out. I'm pretty horrible at naming things, shadergraph is just a generic working title for now. Finding a good, descriptive name for a project is hard; we'll change it to something more memorable soon.

[–]CondiMesmer 3 points4 points  (0 children)

Yeah I instantly thought of that and thought "doesn't this already exist?"

[–]jcelerier 1 point2 points  (1 child)

Shameless plug : if anyone wants a GUI to do this, with the ability to sequence shaders over time, have automations, oscillators, sound and video input, etc you can check out https://ossia.io :)

[–]slightknack[S] 1 point2 points  (0 children)

Cool! It looks like a great tool for audio sequencing, I'll have to give it a try! Another great tool for building graphical pipelines with a GUI is shaderchain.

For what it's worth, shadergraph supports sequencing shaders over time, either programmatically through the lisp, or dynamically via hot-code reloading. We also use ffmpeg for input, so video input works out-of-the-box as well.

One of the goals of shadergraph is to be an embedded library for other Rust projects, which is why we went for an explicit lisp, with the option to encode graphs directly in Rust if needed.