Théo de la Hogue

I can confirm this trouble is not API related. if you have for example a [j.parameter options @type string @range "true false" "aez zre" "foo bar"] the Address is correctly...

here is a simple test patcher to reproduce the problem : ----------begin_max5_patcher---------- 384.3ocoRsraBCCD7bxWwJelRIPoP5INz+hRUkIrkZTv1xYCkGh+8tdMgRkJ Gpphhs2w6yY7w7L0B2NrQAOAu.YYGyyxDnHP1Y6L0F8tpZci3lxhe5VrV0Kc Eg6HAdceuNn2fDF.mmLNaCLi16QngBF6JXVPaWgvbEEZQ3cccCNWwlZ7.bHj N+tyAKzg4ptzWarXkq0J0X3YPa6FisFIoeJNC50T0GbcdKfUTZdJJG0ePOn7 w35vBYaz39CfW+NQtVpKScoug1WixL00EImhCSJw7E7+kzXVJdyrxcCUQnS4 4wkd+WFkGyVC81RbqoBgY0tJc88VljANjm+Ap2EHnrrbZGfwCECmze.+UvbO twQXJVycMUt.dATBsXz3IkWf9Yv5JxrEA9jmUR12eUcl9WUGQbJFKqOLU1hZ zMTmA2Tcth9Ktl9kDozd+VLzvuGEEHx+L6u1EhlS5IlFaxT5VUfI1N+kppzA t4ItyaCoRua5ipTntkXfEII57XkOk+EqAns7 -----------end_max5_patcher-----------

I assign to @nvuaille but maybe it is for @jcelerier ?

Congratulation for this new proposition @mrRay ! Even if I'm not really aware about the web service @lov mentions, I'm wondering to know if WebSocket is one of them ?...

thanks for the input @lov. so I guess what we can share with @laugre (the guy who worked on the WebSocket stuff) is more about the JSON format.

an idea could be : if the name of a node is {a, b, c} it creates 3 nodes called "a", "b" and "c". if the name of a node...

this depends on a feature of API : https://github.com/OSSIA/API/issues/22

yes the solution you proposed was quite the same than Blue Yeti proposed in the Runner example (that you can read here : https://www.dropbox.com/s/8prlpioqyg750y2/M_%20use%20case%20Arena.pdf?dl=0 ). in this solution Blue Yeti...

@bltzr found a temporary solution using a local boolean variable set to true when the trigger is triggered. then on the timenode there is 2 conditions : if variable ==...

this is certainly not applied into the core. I assign to me.