It'd be nice to finally replace gLEDiator as the pattern generator.
I have a few nodes in mind that would replace most of the functionality of that external software:
[ ] GLSL Shader Node
[ ] A code input window
[ ] Preferrably resizable
[ ] and with syntax highlighting / code completion (lightweight lib?)
[ ] Preview directly on the node?
[ ] JavaScript Render Node (optional)
[ ] Same as GLSL node
[ ] Sequencer Node
[ ] Enables coding a "playlist" of animations
[ ] Inputs: Generated frames from shaders
[ ] Outputs: Rendered frames from current shader
[ ] Text Fields
[ ] General: FPS? (if rendered here)
[ ] Per input: How long to stay at shader input
[ ] Per input: Transition style / time
[ ] Preview (Node)?
[ ] A way to preview the shaders, either by rendering them again in the browser or streaming the generated pixel data via e.g. websockets
But those are just some ideas, for actual implementation, more though should be put into it ^^"
It would probably also involve looking at the code of data flow through the rete node graph again, as it probably needs to be restructured a bit.
(Use the normal functionality of rete to go back on the node graph instead of the hacked forward-only way and render the shader in the sequencer node or sth like this)
kyomawolf
commented
4 months ago
It'd be nice to finally replace gLEDiator as the pattern generator.
I have a few nodes in mind that would replace most of the functionality of that external software:
But those are just some ideas, for actual implementation, more though should be put into it ^^"
It would probably also involve looking at the code of data flow through the rete node graph again, as it probably needs to be restructured a bit. (Use the normal functionality of rete to go back on the node graph instead of the hacked forward-only way and render the shader in the sequencer node or sth like this)