Evan

I have a M4L patch that I made as a demo, and have run into some interesting issues while using javascript. I have two js objects in my patch: one that handles LED information based on incoming audio signals reported at 50 ms intervals. I have another js object that observes the state of the solo and mute buttons of my live set and outputs an array indicating LED brightness levels. Everything works great until I start sending data into the LED js patch. The js patch is observing the solo/mute buttons stops reporting the values. Does anyone have any explanation as to why data coming into one js object would affect the behavior of another js object?

It would've saved me an hour of debugging if the object that was actually problematic stopped working instead of another seemingly unrelated object. My instinct is that it has something to do with the fact that the object that stopped working was polling the API. But the live.observer objects that I setup to do the same task continued to work.. So it must have something to do with the js.

If someone wants to see the patches to get a better idea of what's going on I'd be happy to provide them. I was thinking maybe someone had a theoretical answer though.

I have a M4L patch that I made as a demo, and have run into some interesting issues while using javascript. I have two js objects in my patch: one that handles LED information based on incoming audio signals reported at 50 ms intervals. I have another js object that observes the state of the solo and mute buttons of my live set and outputs an array indicating LED brightness levels. Everything works great until I start sending data into the LED js patch. The js patch is observing the solo/mute buttons stops reporting the values. Does anyone have any explanation as to why data coming into one js object would affect the behavior of another js object? 

If someone wants to see the patches to get a better idea of what's going on I'd be happy to provide them. I was thinking maybe someone had a theoretical answer though.


js-objects-stops-outputting-data-when-another-gets-lots-of-data

sounds strange and not what I would expect so it might be something to do with your patching... send over if you want and I'll have a look

Make sure global level variables have a 'var' before them

at top level without the var then other objects appear to share that variable somehow (not clear that they share the data but they do seem to be able to initialise each others variables)

Make sure global level variables have a 'var' before them 

at top level without the var then other objects appear to share that variable somehow (not clear that they share the data but they do seem to be able to initialise each others variables)


You could try adding a deferlow to one or both of them

js objects stops outputting data, when another gets lots of data