< Back to IRCAM Forum

Onseg: offset attribute: bug?

for onseg it says in the documentation that there is an offset attribute.
but attrui does not find it.
Bug or error in the documentation?

it is there, last row in the inspector, or under “Time Offset …” in attrui.

Well, the crazy thing is, I think it was there once, but not anymore. I don’t see Time Offset in attrui.

This is what I’ve checked it with:


----------begin_max5_patcher----------
452.3ocqTssTCBCD8Y3qHSdF6.Tqs5uhSmNKvZMNPRljPEGG+2MYCTwZam9f
Ovk8B6ky4D9LMgWoFPKm8D6YVRxmoIIjqfijQ6DdGLT2BVJMN3bldAOKFRCt
5WEx86LXsKVlhM4KxyXEqJhOHqxxE4rsiejruSHaQGUvhebp5cm5UzPMUU81
ckS8Lll6CMFaHmerxZv.cnCM6PIT0RIjGB8UZZ3V1MtjR7ceKmZnCGnci20W
0yB2bn0425qfBOrbNHju9eBDJtAPvBGvlc9r8Cyt.cInAdbcG22DN1UgTgyy
l7L3QNIz9hnEmO.W.W+avNPq+SXCZgNcKdrpGiDFz8dszu7IAsAbTIJxyChm
wHGPSkxFCPtHN8ejYWnMpZzZmyvrmg9FgZKSIs3Mv2qeLRzatNeWdV999yv2
KWdYFOKdIjN5U11Y3A0WdqPd5oaZ1C9+MHYU8l5oJOdbi8yz2PvA3DJ4rbno
aVVchFsxON1o+D73hUAPYU3w5xiFmYR8JGOAaGqOMUdh6MkIXtIiLExn4Jxz
fGDS4uj7.FOq37TRug1D9vC2yieppwqriRMu3wKW7sjDERuz0pg3pSZmzuR+
Fjqn4vO
-----------end_max5_patcher-----------

weird, it says “nothing” when pasting your patch, but when reselecting offset, it stays there

I’ve tried reinstatiating the object, making a new attrui and connecting that to mubu.process, but it does not come back. Any other ideas?

I’ve made a screenshot. Maybe you see something I don’t see.

{
“version” : “Beta Version 8.5.3 (28228fc7cb9) (x64 mac)”,
“platform” : “mac”,
“arch” : “x64”,
“osversion” : “Mac OS X Version 11.7.2 (Build 20G1020) x86_64”,
“samplerate” : 44100,
“iovs” : 128,
“sigvs” : 128,
“scheduler_in_audio_interrupt” : “on”,
“audio_drivername” : “Core Audio”,
“audio_driver_subname” : “”,
“license” : “permanent full”,
“machine_id” : “cd274cd9bcdc90cbddd6b99753891dac”,
“addons” : {
“rnbo_v1” : “term license”
}
,
“eventinterval” : 2,
“schedinterval” : 1.0,
“overdrive” : “on”,
“pollthrottle” : 40,
“queuethrottle” : 10,
“sysqelemthrottle” : 1000,
“refreshrate” : 33.333332061767578,
“schedslop” : 25.0,
“eventprobing” : 1,
“mixerparallel” : “on”,
“mixercrossfade” : 0,
“mixerlatency” : 30.0,
“mixerramptime” : 10.0,
“videoengine” : “viddll”,
“gfxengine” : “glcore”,
“packages” : {
“ACToolkit” : “0.9.8”,
“adsr221” : “0.0.3”,
“angus” : “”,
“Antescofo” : “”,
“AS-Sampler” : “0.0.1”,
“AudioMix” : “1.0.3”,
“bach” : “0.8.2”,
“BEAP” : “1.0.4”,
“BLOCKS” : “1.2.8”,
“boids_max” : “1.0.0”,
“cage” : “0.7.0”,
“catart-mubu” : “1.5”,
“CidLink For Max” : “0.1.2”,
“CNMAT Externals” : “1.0.5”,
“CNMAT-ODOT-CPMA” : “”,
“Collab-Hub” : “0.3.4”,
“cv.jit” : “2.0.1”,
“dada” : “0.3.0”,
“Delicious Tutorials” : “1.0.2”,
“Dicy2 for Max” : “”,
“Digital Orchestra Toolbox” : “1.2.0”,
“EAMIR SDK” : “2.9.0”,
“ease” : “1.2.3”,
“ejies” : “3.2.5”,
“faustgen” : “”,
“FFT-Part 5” : “7.1.0”,
“filter” : “0.2.6”,
“FluidCorpusManipulation” : “1.0.5”,
“ForumMaxApps-Mlys” : “”,
“ForumMaxApps-OMax” : “”,
“ForumMaxApps-SoundBox” : “”,
“ForumMaxApps-Spat” : “”,
“ForumMaxApps-SuperVP” : “”,
“FrameLib” : “1.0.1”,
“FTM” : “2.7.5.BETA”,
“Gen CV Tools” : “1.0.1”,
“gen~ Plugin Export” : “2.1.0”,
“Gestural-Sound-Toolkit-master” : “”,
“Gesture&Sound” : “2021-11”,
“gl3” : “0.3.3”,
“go” : “1.0.0”,
“Grainflow” : “1.0.0”,
“hap” : “1.0.6”,
“HISSTools Impulse Response Toolbox (HIRT)” : “2.1.0”,
“ICST Ambisonics” : “3.0.2”,
“ICST_ambisonics_2_3_2” : “”,
“imp.push” : “”,
“ISF” : “1.0.3”,
“Jamoma” : “1.0.1”,
“jasch objects” : “0.8.3”,
“jit.mo” : “1.1.6”,
“Jitter Recipes” : “0.1.4”,
“Jitter Tools” : “1.0.7”,
“jk.push 2” : “2.0.3”,
“karma” : “1.6.0”,
“LeapMotionForMax” : “”,
“link” : “1.5.5”,
“LowkeyNW” : “1.3.1”,
“mat.oo” : “1.0.1”,
“Max for the Visual Arts” : “2.55.3”,
“Max Hardware Library” : “1.0.1”,
“max-mxj” : “8.2.0”,
“Max-SDK” : “8.2.0”,
“maxforlive-elements” : “1.0.6”,
“MaxISiS_V1.2.8c” : “”,
“maxorch-main” : “”,
“MaxSoundBox” : “09-2022”,
“MC Movement Studies” : “1.0.2”,
“mi-gen” : “1.1.0”,
“min-api” : “”,
“min-devkit” : “0.6.0”,
“Mira” : “1.2.1”,
“Miraweb” : “1.2.7”,
“ml.lib” : “1.1.5”,
“ml.star” : “1.3.0”,
“Modalys” : “3.7.0”,
“MTS-ESP” : “1.0.0”,
“MuBu For Max” : “1.10.5”,
“MuBuExamples” : “03-2022”,
“Music-and-Computing” : “”,
“NajoModularInterface_2” : “”,
“Node for Max” : “2.0.4”,
“Nonlinear Sequencer” : “1.0.2”,
“odot” : “1.3.4”,
“OMax4.6” : “”,
“orchidea” : “0.7”,
“Patter Tools” : “1.0.1”,
“PeRColate” : “1.3.2”,
“petra” : “1.2.0”,
“PGS-1” : “0.0.6”,
“ppooll” : “”,
“RISE” : “1.0.4”,
“RNBO” : “1.1.0-dev.61”,
“RNBO Guitar Pedals” : “1.0.0”,
“RNBO Synth Building Blocks” : “1.1.2”,
“RTC-lib” : “8.3.0”,
“Sadam Library” : “20.3.7”,
“sampler” : “1.1.0”,
“Samplor” : “3.45.0”,
“sensel” : “0.5.2”,
“smFilterPack” : “0.0.3”,
“Somax-2.4.0” : “”,
“Sound Design Toolkit” : “3.0.0”,
“soundworks” : “”,
“spat5” : “5.2.9”,
“SuperVPForMax” : “2.18.5”,
“Syphon” : “1.0.9”,
“th.mcutilities~” : “1.0.0”,
“The QAC Toolkit” : “1.0.2”,
“TS.Modular” : “1.0.1”,
“Upshot” : “1.2.0”,
“VIDDLL” : “1.2.8”,
“Virtual Sound Macros” : “”,
“Vizzie” : “2.2.1”,
“VR” : “1.0.1”,
“Vsynth” : “1.4.0”,
“XRAY” : “1.0.2”,
“XY Coordinates Generator Pack” : “1.0.1”,
“zero” : “1.0.4”,
“zsa.descriptors” : “1.3.0”,
“µK Bundle” : “0.0.1”
}

}

is it possible that you have an older version of pipo.onseg.mxo in your path? You can put pipo.onseg in an object box, Max will complain but the “List externals…” menu item will work.

That helped: the file was in my folder called “Max for Live Device Project/Max for Live Devices”.
Inside this folder there was a folder called “SKataRT Project”.
And herein was the magic folder called “discarded” that contained the pipo.onseg object.

I don’t remember how this got there, but I’ve discarded the folder and everything works again :slight_smile:

glad you found it! Yes, Live really makes a mess when using M4L devices.

1 Like