Some basics, sorry if you already know them :
1#
Again, there is no clipping. What seem to be clipping is just “no scale applied”. Since no event hit the transform node, no transform was applied, and therefore the default y=1 & x=1 apply, wich mean they do not feedback stretch. They feedback in place over time, but do not stretch-feedback.
You can verify what is going on by clicking the port and check some values on the popup (and click on that popup if you want to pin it to the canvas).
2#
It is normal that adding an Allow First Event node fixed that, but it still doesn’t update further live-coded changes, since it was an Allow FIRST event only. Further events do not pass, and later modifications to your node are not updated.
What you did is correct, manually fire the port to see the changes, when it is not published.
There is a feature request that was planned for Vuo 2, but was delayed, where every change in editor live coding would automatically re-fire/reload the node : Fire an event from Node when an input value is changed in the Editor
Now, I just gave the manual another read, I did not know it either, and I don’t know why it is like that, but for standard non-protocol compositions like yours, published ports do not push changes downstream/forward the node chain. So what we did is correct, to add an Allow first event, or to directly connect it to a Fire on display refresh event only cable (shift-drag cable) for live coding/always updating node.
(Although for optimised compositions, we should only connect nodes to the computing lightest event flow, at start only if the node doesn’t change later, or once every second, or 60x/second. Differenciate live noodling (see feature request above) from updating the node in for the final composition itself). (For example, in your composition, use the Allow First Event cable to the Make Rectangle Layer instead of directly to Display Refresh if it doesn’t need a 60x/seconds update). (See joined comp 1).
3#
Last but not least, if you want the published ports to automatically update on changes, (without, in Vuo 2 like you mentioned, the need for “Allow changes” ), you can use a protocol mode composition (f.e. image generator mode). For these, the published ports do update the whole node chain on every change (see joined comp 2).
Calculate-Amplitude-Frequencies-03.2.vuo (8.4 KB)
Calculate-Amplitude-Frequencies-03.2 Protocol.vuo (7.95 KB)
It would be good to understand completely why this solves it whenever anyone has a chance. Sidenote I also changed the Colour Depth of the Feedback patch to 16bpc so it doesn’t leave behind ghost trails.