Bug: Unexpected Behavior in coll when incrementing index
I believe this is new behavior in coll. If I store a series of items using a numeric index from 1 to 10, and use either the bang or next messages to output the messages in sequence, and then I use a specific number to recall an index, the pointer in coll is not set to that number but instead continues to increment from wherever it left off from the last bang/next message.
i.e. Lets say I hit bang 5 times, and the coll is now on index 5. I then send it a 1 message and it outputs 1. But then I hit bang again, it outputs the data from index 6. I would expect it to output data from index 2. Using goto 1 is a workaround for this but does require the extra bang afterwards and i'm pretty sure this would break older patches. Correct me if I'm wrong!
{
"version" : "Beta Version 8.2.0 (665eec03d3c) (x64 mac)",
"platform" : "mac",
"arch" : "x64",
"osversion" : "Mac OS X Version 11.6 (Build 20G165) x86_64",
"samplerate" : 48000,
"iovs" : 256,
"sigvs" : 256,
"scheduler_in_audio_interrupt" : "on",
"audio_drivername" : "Core Audio",
"audio_driver_subname" : "",
"license" : "pace",
"machine_id" : "cfa128ff7ac5ec05b89b2e131833f0bd",
"eventinterval" : 4,
"schedinterval" : 1.0,
"overdrive" : "on",
"pollthrottle" : 30,
"queuethrottle" : 10,
"sysqelemthrottle" : 200,
"refreshrate" : 223.332992553710938,
"schedslop" : 1.0,
"eventprobing" : 1,
"mixerparallel" : "on",
"mixercrossfade" : 0,
"mixerlatency" : 30.0,
"mixerramptime" : 10.0,
"videoengine" : "avf",
"glengine" : "gl2",
"packages" : {
"BEAP" : "1.0.4",
"CNMAT Externals" : "1.0.4",
"cpDelayNetworks" : "0.a.1",
"ease" : "1.2.2",
"ejies" : "3.2.4",
"FFTease 3.0 Package" : "",
"FFTJIT" : "0.a.1",
"Fluid_Decomposition" : "1",
"gl3" : "0.2.9",
"hap" : "1.0.6",
"jasch objects" : "0.7.2",
"jit.mo" : "1.1.6",
"Jitter Tools" : "1.0.0",
"link" : "1.5.5",
"LyonPotpourri 3.0 Package" : "",
"Max ToolBox" : "15",
"max-mxj" : "8.2.0",
"Max-Test" : "7.0.3",
"maxforlive-elements" : "1.0.2",
"MaxSoundBox" : "03-2018",
"Mira" : "1.2.1",
"Modalys" : "3.6.1",
"n4m-examples-master" : "",
"Node for Max" : "2.0.4",
"PeRColate" : "1.3.2",
"petra" : "1.1.0",
"RISE" : "1.0.3",
"sc-max" : "0.1.",
"smFilterPack" : "0.0.3",
"th.scala-main" : "",
"vb.mi-objects" : "0.0.2",
"VIDDLL" : "1.2.5",
"Video & Graphics" : "7.2.0",
"Vizzie" : "2.2.0",
"wave-terrain-synthesis" : "",
"zsa.descriptors" : "1.2.0"
}
}
@NICK I think this is how it has always worked, at least since Max 7.3.6. It is my understanding that sending a number to coll does not update the index pointer, though goto, bang, next, prev, start, and end will.
looks like i’m 0 for 3 on this beta! guess i’ll just have to wait for the next one :)