You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all, I'm hoping to connect to a web socket server using [ws.client] and so far I have run into some crashes. So far I've just been working off of the help example. By sending a bang to the object I can get it to connect about half of the time (usually after a long delay) and then any subsequent bangs cause Max to crash. Does this object still work with Max 8.2.2?
Hi all, I'm hoping to connect to a web socket server using [ws.client] and so far I have run into some crashes. So far I've just been working off of the help example. By sending a bang to the object I can get it to connect about half of the time (usually after a long delay) and then any subsequent bangs cause Max to crash. Does this object still work with Max 8.2.2?
{
"version" : "Version 8.2.2 (85d93eb32e9) (x64 windows)",
"platform" : "windows",
"arch" : "x64",
"osversion" : "Microsoft Windows 10 (build 19044), 64-bit",
"samplerate" : 44100,
"iovs" : 512,
"sigvs" : 64,
"scheduler_in_audio_interrupt" : "off",
"audio_drivername" : "ad_mme",
"audio_driver_subname" : "",
"license" : "permanent full",
"machine_id" : "282d36d3df2a7aaacfd5289ea1d3d197",
"eventinterval" : 2,
"schedinterval" : 1.0,
"overdrive" : "on",
"pollthrottle" : 40,
"queuethrottle" : 100,
"sysqelemthrottle" : 1000,
"refreshrate" : 33.333332061767578,
"schedslop" : 25.0,
"eventprobing" : 0,
"mixerparallel" : "off",
"mixercrossfade" : 0,
"mixerlatency" : 30.0,
"mixerramptime" : 10.0,
"videoengine" : "viddll",
"glengine" : "gl2",
"packages" : {
"11clicks" : "",
"BEAP" : "1.0.4",
"gl3" : "0.2.9",
"jit.mo" : "1.1.6",
"Jitter Tools" : "1.0.2",
"max-mxj" : "8.2.0",
"Max_Worldmaking_Package-master" : "",
"maxforlive-elements" : "1.0.4",
"Mira" : "1.2.1",
"Node for Max" : "2.0.4",
"VIDDLL" : "1.2.5",
"Video & Graphics" : "7.2.0",
"Vizzie" : "2.2.1"
}
}
The text was updated successfully, but these errors were encountered: