M4L jsliveapi error: Changes cannot be triggered by notification

Oct 21, 2012 at 4:14pm

M4L jsliveapi error: Changes cannot be triggered by notification

Hi All,

I’m building an Lemur interface for Live.

My device is built around a js object which
1) gets the values from its input (from the Lemur) to update the values of Live tracks volume
2) observes the volume of these Live tracks and send their values to the lemur when they change

I’m avoiding feedback loops by ignoring observed values during 100 ms each time a value is read from the input.

The problem i have is that, say i have a 2 tracks Live project, if i change the volume of track 0 via the Lemur (hence via the input of my js object) and, at the same time, i change the volume of track 1 via the mouse (hence via the observer), i get those “Changes cannot be triggered by notification” errors (even though the volumes changes are performed as expected).

Can anyone please help me to get rid of these?

Here is the javascript:

var numTracks = 2;
var inhibTime = 100;
var osc_path = "/Live/Volume";

inlets = 1;
outlets = 1;

var liveVolumeSliders = new Array;
var liveVolumeInhib = new Array;

function bang() {
	for (var track_i=0;track_i
#64857
Oct 23, 2012 at 6:15pm

Anyone?
There’s probably something i’m doing wrong but i can’t figure what :(

#233863
Oct 23, 2012 at 6:40pm

Hi,
I’ve not had a close look at your script, but I came across this error once when passing information in and out of javascripts in M4L – A defer low object solved the problem. Hope this gives you a pointer to success!
Leigh

#233864
Oct 24, 2012 at 12:17pm

Thanks for the answer, i’ll try that!
Where did you put the deferlow? on the input or output of the js object?

#233865
Oct 25, 2012 at 9:31am

Ok, so i tried the deferlow object on both the input and output of the js object but the problem stays the same.
Can anyone have a look at the code and tell me what i’m doing wrong? Please?

#233866

You must be logged in to reply to this topic.