Rob Gordon

As I understood it Max is run in a kind of sandbox inside of Live. I do a lot of work with javascript in Max so, in attempt to understand the environment, I made a fresh midi effect with a js object just to list the properties of the global this.

var global = (function () {
    return this || (1, eval)('this');
}());
log(this);


js: {
js:     "global": {
js:         "Jitter3DUtils": {},
js:         "JitterGUIUtils": {
js:             "trackers": []
js:         },
js:         "JitterReposUtils": {
js:             "interpbits": 8
js:         },
js:         "update": "function() { action(function(note) { note = shift(note, 'y', 1); note = shift(note, 'x', 1); return note; }); }",
js:         "i": 3
js:     }
js: }


Okay, the jitter utils make sense. But the 'update' function I recognize as a piece of code from another one of my M4L Device's, and the 'i' seems like some stray for loop accidentally using a global variable. (Not the best programmer...) But what seems surprising is that the device that would have attached that code to the global namespace wasn't active in this live set. It was a fresh live set, and this was a completely blank device. I had also just started live fresh.

Is this to be expected? It doesn't seem good. Also- does anyone have a suggestion about how to get rid of it, and/or avoid it in the future?

var global = (function () {
	return this || (1, eval)('this');
}());
log(this);


JS variables stored permanently in M4L namespace