Animation - i call this interference-1
Hi
Another play with Nodebox this Time
i had the idea of animate it
here the link to video
https://go.screenpal.com/watch/cZjrjzV9Hii
the Nodebox File is attached
- intereference-1.zip 1.21 KB
Keyboard shortcuts
Generic
| ? | Show this help |
|---|---|
| ESC | Blurs the current field |
Comment Form
| r | Focus the comment reply box |
|---|---|
| ^ + ↩ | Submit the comment |
You can use Command ⌘ instead of Control ^ on Mac
1 Posted by lastvector on 21 Aug, 2024 08:54 AM
forgot a picture
2 Posted by lastvector on 21 Aug, 2024 09:49 AM
just play with the parameters
to get many variations
here is one of them
https://go.screenpal.com/watch/cZjrQ5V9Hqf
Support Staff 3 Posted by john on 22 Aug, 2024 12:16 PM
Gottfried,
Once again I am inspired by your work!
Your code was straightforward. I simplified it a bit out of habit and then decided to add some color just for fun. Then I started tweaking things (as you were already doing), and then added more knobs, and played with the generating shape, making it stranger, and rotating it, and softening it, and swaying it back and forth.
Then I added even more adventurous features like a zoomed in version of itself inside a hole in its center. Then took that out. At once point a glitch appeared and it took me hours to get rid of it. Then I decided I liked the glitching and put it back in. More changes and then birds appeared out of nowhere. Then I started playing with color again.
After many hours of this, the final result bears little resemblance to your piece - on the surface. But if you look at my code - which I am posting here - you can see that the bones are the same.
As before, I just posted this on my Instagram and Threads accounts with a note saying that it was a riff based on the work of a fellow Nodebox artist. Feel free to riff on my work if you want. I included two different color schemes generated with different methods so you could see how I did that.
You can see the video here: https://www.instagram.com/p/C--JgjiJPrY/
An unexpected but rewarding journey. Thank you.
John
Support Staff 4 Posted by john on 22 Aug, 2024 12:33 PM
OOPS
I just realized that I had added a code library to that file at one point, then removed the node but forgot to take out the reference. As a result, you will get an error if you try to open it.
Here is another copy. You should be able to open this one.
5 Posted by lastvector on 22 Aug, 2024 01:02 PM
Hi John
Wow, these Birds looked almost three-dimensional to me.
I think one of the points of this forum is also to exchange
ideas and inspire each other. I feel the same way about
your work.
Since you have way more Nodebox knowledge than I do,
things can come out of it that simply wouldn't occur
to me. Find this always pretty interesting and a way to
learn something new.
As far as the reuse of projects is concerned.
As i wrote before feel free to use them and extend
them to your like. I am happy to see the Results.
As i saw that "NULL" Node in your Nodebox Tree
could you explain why you set them, whats the
reason for it ?
Have a nice day
gottfried
Support Staff 6 Posted by john on 26 Aug, 2024 07:17 AM
Gottfried,
Re the null1 node in my Nodebox tree.
That is a remnant from some earlier experimentation I was doing. I kept fiddling with the code just above that node. And every time I changed something, I would have to reconnect the scale1 and compound4 nodes (and maybe something else no longer there) below it.
I got tired of this, so added the null node so that I would have a single point of contact between the stuff above I was constantly changing and the stuff below which was relatively stable.
I sometimes do this when I am actively changing nodes in a network. This case is pretty mild, but sometimes there is a node which feeds ten other nodes below it scattered all over the tree (quite common with frame nodes in an animation). If you ever need to replace that node you then have to rewire all ten of those connections - which may cause new errors if you miss one. So when things are in flux in a network with choke points I will sometimes use a null node to preserve the downstream connections so that I can just change the one node that feeds the null node. Makes experimentation less painful.
When the network is finally complete, I may go back and remove those null nodes. But they don't do any harm, so, as in this case, I may just leave them.
Good question - thanks for reminding me to answer it.
John
7 Posted by lastvector on 26 Aug, 2024 01:02 PM
John
Thanks
Sounds useful, I think I'll add that trick to my toolbox
gottfried
8 Posted by indefiniteness on 16 Feb, 2025 12:38 AM
I had to chime in on this one. I wanted to put it out there that at this point, I will usually have a considerable amount of these Null nodes and most of the time I do this purely for organizational/aesthetic purposes - some similar to what John is talking about but also, more often than not, my reason are my own eccentricity and I cannot stand cables going everywhere... But as mentioned, it is also functional for the routing aspect and reducing errors. I will name them sequentially after the parent node (if I'm not being lazy) and when I do this, I will even stack multiple null nodes from various top regions on top of a single grid point. But since they are labeled, if I need to debug, I just slide them from the top of each other. Though, I also usually use several vertically aligned null nodes for, again, the single connection point already mentioned, but sometimes, to transport value a long distance from top to a bottom region and keep all the connections as vertical lines, using a final null node per cable below this to 'pull'the connection over left or right (to get the familiar "S" shape in the cable) and hop that crest over or tuck the trough below nodes between the previous null node and current one to final connection port. I if have time later I will share what I mean.
Support Staff 9 Posted by john on 16 Feb, 2025 02:31 AM
Indefiniteness,
I know exactly what you mean by using nodes for link management; I sometimes do the same thing.
I think of that use case as "cable ties". In a past life I once worked in a lab with hundreds of computers on racks. The lab manager was nutty about using color-coded cable ties everywhere to keep things tidy. I say "nutty" but actually this was very sensible and almost mandatory. Without these cable ties the whole lab would quickly descend into chaos.
Like you, I think keeping tidy Nodebox networks is actually quite important; I'm always going on about it. If your network becomes a rat's nest it becomes much harder to find bugs and understand what's going on. I think Nodeboxing is also much more pleasant if you keep your networks tidy. It's a bit like Marie Kondo's prescription for a happier life through tidiness by "choosing what sparks joy."
One thing that DID surprise me about your note was your idea of purposely stacking null nodes on top of each other. I sometimes do this by accident and become frustrated by the bizarre behavior that results when I connect an input to the top node while what what appears as the output of that node is actually coming from a lower node in the stack.
This keeps happening to me. I found it so frustrating that I once suggested to Frederik that he make it impossible to stack nodes on top of each other. Until now it never occurred to me that there might be a practical reason to (temporarily) stack nodes as you sometimes do. I might even give that a try in certain situations next time they arise.
Thanks for chiming in!
John
10 Posted by lastvector on 16 Feb, 2025 11:13 AM
Indefiniteness
thank you
Understand the point for organizational purposes
and also that there can be aesthetic reasons for it
and I will keep it in mind when Nodeboxing
gottfried