search

jamoma / JamomaMax

Implementation of Jamoma for Cycling'74 Max:
http://www.jamoma.org
41 stars 9 forks source link

j.remote dataspace is not properly synchronized #742

Open theod opened 10 years ago

theod commented 10 years ago

Here is an example : 


----------begin_max5_patcher----------
711.3oc0WssjhBCD8Y7qnKdlU4t39zteGas0TAHpwBRrBAGcmZ922bAUlwKf
VNNpUIRZZRN8I8oS6aCrrSYqwU1vOg+.VVuMvxRaRYvpYrkcIZcVApR6lcFq
rDSE1NlmIvqEZ69i.wbLED7MffAYyQzYXkIXEpnFCS4rR8PNtjIvae+BBEmw
po5Iwuw3TFUTQ9GVYyyenaiYZcIqVTfEZjr05T9rT83c9sDIxlSnydgiyDlX
yOHR9XvKzS+SrZRgffgtveadIRtNLXoK9gmucKfPQkZfX+aNAUzNtyXELtY9
cGFGEGED3Huyar7Sr5Ne4sSjKWqkQFCD51PvSY68ACTWb5I+SwuJw3AzeACk
mJob6KgB8NCgMIvvTpqwIpq9tmft75ltLKpXyRrY5s0X8oiUBC6Mo398SJmR
p5MBxwUBNaCPD.hlK0jo0jhbs9bIhKQq.ygWIh4fDjPkDkRhP55FHGIPUKQY
GWAG7kofmD1V.Gn2BBGebxexCr9sDWUglgOXSYGuNplJ2UTrJheiUyg5xdd9
lZgIGm7FeEItmHo0+qfefYHB0A9Dekmda03MT0D+yQUgeuT0zBlbNtn31u6i
HcCGF4.Qtmq5VR2A9txHufonzBbaA+AjhLRPx5T2qiEVLzzDBLkwtH5Kr6CL
Mzmm6Y4u3qIwwo02aGEcaShZNfLTe134yghdRxgtsDjoyy3dvOAO6Zr8MRHk
YvuTPQ12QFobe.b8c+2YN3jDibz8rc5es5vtoOsG5.7S+8JMhU1+HmVwp4Ya
WissUC6QspiMBEIHLZKmF+AelSxywz1YA4jJUhgNhcO5laugiaOfS38CN8.M
Q2MzDzCz3c2PS3CEZR5AZhuanY7CEZh6AZRtRzXJ.gVtbElW0LkZfHKeuv7+
dhczCITyPcSw1b7JxV+MNf3xRrBY80Zto.45jX6Ap048A+2MXgjq
-----------end_max5_patcher-----------
theod commented 10 years ago

Notice in TTViewerReceiveAddressCallback there is a try to handle this but it doesn't work and it is very cpu consuming !

theod commented 10 years ago

For the moment I'll remove the bad code in TTViewerReceiveAddressCallback to optimize the code but this bug will need some changes I can't do for 0.6.0 milestone.

theod commented 10 years ago

Actually the TTViewer should be notified when its TTReceiver is notified by the TTNodeDirectory that the address have been created.