Summary
ADSR Envelope Nodes and/or other value-setting node types do not properly set values in render, especially when used in conjuction.
What Type of Bug are you experiencing?
Audio
Steps to Reproduce
Insert a Trigger Route (Time) node (or any Trigger Route data type). Plug an Input to each Set for simulation. Apply different timing Value Inputs for each Set. Connect pin output Value (On Set) to ADSR Envelope (Fade or Audio) Release Time Input pin. Play audio and trigger simulation on Input Sets.
Expected Result
Release Time should update with chosen Set Value - audio render should render audio with a fade-out (Release) of the chosen Set Value time.
Observed Result
Release Time ignores chosen Set Value and fires instantly. Sometimes only “Set 0” works. “Set 1” definitely does not work.
Affects Versions
5.8
Platform(s)
Windows
Upload an image
Video
Additional Notes
I have tried troubleshooting this with the other data types and it seems to be the same behavior (Value Nodes, Routing Nodes, etc.). Plugging an Input value (Knobs/Sliders) seems to work fine since that is just brute-forcing a value, but automated trigger values do not.