i’m aware how type inference in VL works, that’s not the issue.
in my case i originally had the problem that the type was not propagated through a matroska of another process node, making it impossible to set the type by inference. that made me think that i totally did not get something when it is so complicated to make a type explicit.
i repatched the whole thing flat and inference worked as expected.
i guess this is a bug then for the type propagation. i’ll see if i can reproduce it in a new, clean patch and will see if i just had bad luck.
regarding the UX: the OSC simple nodes are nice. still - if i have to explicitly set the Count on the input pins (with the ArgsToValues node) i find it a little strange to infere the types implicitly. (i know, it make sense codewise but setting parameters explicitly upstream AND implicitly downstream for the same message feels strange to me. i’ll get used to it)