< Back to IRCAM Forum

Bug: maxsize in mubu.track

The attribute @maxsize does not seem to do anything (see attrui)
Changing attrui does not change the value in the inspector.
Changing the maximumsize in the inspector sets it back to 6136.


----------begin_max5_patcher----------
366.3ocmRsrSCCCD7ryWgkOGpbZIzJNw+ABE4jr.tMwNxOJAp5+NNqcZKuDH
Nj3rS1WyL9PFgUqGAKidK8dJgbHiPPnI.RJlv5EiMcBKlFSAunq2xxi+xAiN
Dt2W6W3LhlczoOcf0U6ej1KL6.ikdWnGV4a.sfy4yEKawRCs6pxYLs20AN2q
CPboXr7zC8gTJCBWyyR0SUFnwEyZcwBdNsnbyzwx0qvikK3mpQ46kpPiQNTb
FLNNDcUB0J1CsUgkJz8JgyYjHcRRRRSHr8foVawsr.gNlkM+9XV9eTMm5uW9
MBxF1I1ZD8fCLUfRT2gCj+ih0IBO03nwDEd1uJd7UQMj+eDuhK3NVGqSp97E
Kb1S3eTPrZuoYlAItSOO81vUIoR3jZ0E4TFy4KiULLDbFaJYbDAIXqFEiM4X
nTECKwPCrWNmOdGfILAIxEzGuAWK13MWyhkpaAiJXXQJG74vHQ2TELI6fHxC
zzyNl8tZ1GM6
-----------end_max5_patcher-----------

{
“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”
}

}

Hi,
I can’t reproduce the problem.
Changes in attrui and inspector are well synchronised here.
Best

I think I see why it works on your side.
If I reload the patch, the settings are applied.
If I edit the patch they are reverted.
I think it should work without reloading.

To reproduce: open a new patcher, rebuild the patch below, and see if you can change arguments without reloading the patch.


----------begin_max5_patcher----------
1449.3ocuXssiihCD84juBTdNSDlKAx7TuR6i69ELZTjCXHdFhMx1zWlQy9s
ukswDbBoCSu81sTCAiwUUm5TWr+4xEqNvelHWE74fuDrXwOWtXgYH8.K5edw
pS3mKZvRyzVwHOwO7sUqsuRQdVYF9T2gtMJAt36A5epHR0gtpfSXw2IBYvCv
ZHo+fDjFFF7PqfTRpBdg.uPQOQT35ZRo8YAkUe9WJLsIHJcqdATB5yE7FYPz
nmX3Svb+yNAVQ4rf+h2UxHR4eie1ohsXUwQXo1KHEJqkljtIbcPZRh9VdVr9
VTzlvfu1+MvByE14FtAkGFuKBktMeaTVR5ZXnHyuB2YeyV8P4IYgo44QwoQ6
RPQqCPiVOV2IJqgnLPH57f7Nkaz39QokF7Dv3Ok5LA6zTuzRr5zpUq6+ePBR
7ijx8vWAF4drBPGiSn2Q16IWr5Qh3.WZVFjYnesbo65uVtdlb.XoUb1q.vQZ
zbcPRnAniRbWec.oEK.uohH1SX3CMFsLbRvBcMXkbSv5.lUC.0avNeMtdqfW
.DMO19WvckT9WCJIxBwmkjF.P9LmII0AOnIpmCGLyXyQdqIn.oCJrSeigg6n
wAOX95MkN9MxMh5nfHOxaJAdVraPoBKTTo9AkdpfNVCSSBPRamJfxzWevo4g
NCqgxHE7Nlw5h5GrhyTZc1Xw+gfhadE+MJAY721a4oY5awoib35kqBW34S+e
MJKZRhSxH0QC8FxjlqdEeJZW9cC+n.jYiBeCjKpl43Dg.3nDQWCv8cpUrSoJ
4mvT19CfGpT5fKM9ljkuIINMNKAkraa5trsoCXgBePt+Qpj1GG4hX.ZZEQTb
jCYAD6OTOxGX7cdWFVMtfRXJCEbrCrA+BfMiGwxzz4zsz4K9fJAg7CeNPmPx
Ai9H1htPzp3tYty1Zxei1YxqjOlmgan0rGojmNCWNSGBeIBFtoh1P7dQmjz1
.bSc3DDcN9U7VbAE778ARzGmR4YDL7RObPw4MfkLa.15igbB7Fy2MvMuPTET
QQC4HgVezHu3Ap6bkjfTCNkonFVcvmDhRmj2LwWOhAem0dtZpuHqp8RWDtdz
EOppgA9Htoy5jujn4htb7kNE+LUIb.jj3SsMjAphO+96jWjWTb55pY9jiKM4
oU9mnrRX1T+XDGYpkKotHJzMHNSf8dTmmnkpi9Lmw8D35lnsgp1OO.erqsiQ
UiQWOQSJqIyCFFujy0u6yVlBp5YFPtAWcsI3FNKHbD+PPpzEagRv9tEcJVmu
JJbFMwX0.ndjbF8133Obcev7pJnl9TjhqJWXV9mNRHMVVgmjbEzG00xpK7Uy
xCQNcfTNdksLlAzXBG48XlPrVy7DdeJrqJHFdCJTsf5oq9TkQkdLs0Jmnl7k
qv39DVMxgXFkTBTHeKbBaWSr5ZK64TnnvMd7pwD3ALlgacjPnkwyegkWMYE2
q6c47lbr51XI8IzlK4WSn58EEMhYyEwPU.ii+zUTbK83lEFNm+ZdkFth3XIi
HeBhWhi7PyeHztnvcQ6zrks6L+kmGlsKLCM4P2JszT9mK3UCkPe+14QCGWdR
26tv1wRPon6TCm2tASGBj+s5b21PUbloUJTV5UaEdFacEM6lpiidk8z9dtEM
qq3eBlHO2MAg9cqhPuIPH5ZqEcSasBbjlsN712apdO9cz6eHGHa5yzv4YT+9
6AWqH1ZJ1i3Y00.Q96rS+t1dTH5C130Eomvxi+ns7X6du+Pc6tClaB6Oal1u
Q6LGDwEGFowD0i6CJRdmnvsT8TrfQYpgPdJaX+peY37zzyYRXetxI6CRNIyP
Nlin3+rjL4juqrPuGR5CB6z5J5MfcVRHtsE1Qjre5Fg.b7uY6jHes4QJy9nY
2wP6F5Fary2rymUXnK.pBBJ6D1xvOu0d9jP24kDACBgsm.KXdfHMw2lSxts+
HxLoAV9qk+KPbgfeQ
-----------end_max5_patcher-----------

yes, ok I can reproduce.
The maxsize of the track is forced to a minimum value of 6136 by the mubu.process (which manages the attributes of its output track). If you try to set the maxsize to a value higher than 6136 then it works.
I’ll look more closely in the debugger soon.
Thanks

1 Like