< Back to IRCAM Forum

Have these mubu.process attributes ever existed?

Hello,

I had a big list of error messages on my ages-old live patch. Among them I had some from mubu.process:

“mubu.process: “slice.size” is not a valid attribute argument
mubu.process: “slice.size” is not a valid attribute argument
mubu.process: “slice.hop” is not a valid attribute argument
mubu.process: “slice.norm” is not a valid attribute argument
mubu.process: “scale.func” is not a valid attribute argument
mubu.process: “scale.base” is not a valid attribute argument
mubu.process: “scale.inmin” is not a valid attribute argument
mubu.process: “scale.inmax” is not a valid attribute argument
mubu.process: “scale.outmin” is not a valid attribute argument
mubu.process: “scale.outmax” is not a valid attribute argument
mubu.process: “scale.colindex” is not a valid attribute argument
mubu.process: “scale.numcols” is not a valid attribute argument”

I don’t know for how long these messages have been popping since they were hidden in a big flood of error messages. I don’t remember having seen them before.

So, how long ago have these attributes been removed? Or were they incorrect in this object from the very beginning???

Hi,

if you look in the help patches of these pipos, all the attributes still exist.
Maybe you don’t have the pipo objects in the Max Path?

Best

Hi Ricardo,

Aren’t thes objects included in the mubu package?

Yes, of course. Maybe you have old items in the Path? Can you check if the pipo helps work for you?
Best

Yes pipo help works. One additional information: this issue came after moving my patch from a Windows computer to a Mac ARM (M2).

ok. Does this happen only on OSX or also on Windows?
If you can share the patch I can try to reproduce the bug.

Interesting. It seems to happen on Windows too. Could some mubu update have broken something?

Here is the subpart of the patch. I can’t send the whole patch it’s much too complex and big. Please note it’s supposed to work with a polybuffer~ with several dozens of sounds.

process_subpatch.maxpat (1.1 MB)

thanks!
In your mubu.process you have just a pipo.mfcc in the pipo chain. But you declare attributes for pipo.scale and pipo.slice (which are therefore not instantiated). This gives the errors.

Best
Riccardo

Great, thanks!

then actually the error message is not clear. We will try to be more precise…

1 Like