< Back to IRCAM Forum

MAX_ERR in object_attr_setvalueof

Spat
#1

Hi all,

did you ever had this kind of error message from spat.oper?

unknown MAX_ERR in object_attr_setvalueof defer

Spat 4.7.1 32bit running on Max 5.1.9
OSX Mavericks

same thing with Max 6.1.6 running in 32bit

Running Max 6.1.6. in 64bit doesn’t give this error message.

#2

What is the context ? How to reproduce ?

#3

The context is an articulated concert patch, I’ll try to prepare something simple to see if the error occurs and send it here.

#4

OK. I figured out the context. You’re recalling pattr preset.
You can totally ignore this error message. It has no impact at all (and the rest of your pattr should be properly restored)
(the ‘defer’ attribute is not yet implemented in spat.oper, and this throws this kind of error).

T.

#5

I am also having the issue in spat.oper which appeared with the latest update of spat. It doesn’t seem to impact audio or stability of a patch. The error message appeared every time I saved my patch, but sometimes doesn’t.
Also the new release notes indicate that defer option doesn’t work yet with spat.oper, still the @defer attribute is available in spat.oper. I quickly tried to enable or disable it to see if it corrected the error but it didn’t seem to change anything. I’ll try to check for a reproduction pattern…

Edit: Thank you T. for the explanation ^^

#6

Thanks for your feedback.
The error message will be removed in the next release.
In the meanwhile, dont worry, I’m quite confident this has no impact and your patch will run safely.

T.

#7

Yes, I’ve verified with a simple patch that the Error, doesn’t seem to affect datas.

btw, two more things:

  • when recalling different presets, if the spat.oper window is opened it move in another place of the screen…
    and the worst:
  • when one upgrades to a newer version of Spat and try to recall some presets from pattrstorage, there are always differences in “Atoms expected”…and the edited presets are not recalled at all.
    This happens even if the newer version of Spat is the immediate successive release.
    This oblige user to do the job from the beginning.

But i think you already know this issue.

#8

  1. When recalling presets, the ‘windowtopleft’ attribute (i.e. the position of the top-left corner of the window) is restored. So the window may move accordingly. No big deal…

  2. Yes, I’m aware of this silly/annoying issue with pattr and spat.oper (or other spat objects btw):
    pattr stores the list of all attributes as a list (which is insanely unreadable with spat.oper); in spat, this list is furthermore sorted alphabetically.
    Whenever a new spat version comes out with newly added attribute(s) (and this occurs quite frequently), this breaks compatibility with former pattr files as the size of the list changes, and spat is not able to recover the pattr data.
    This is a pity but I dont have solution to that issue yet.
    A (rather good) workaround is to instead store your presets in a dictionary (using the ‘dumpdict’ or ‘exportdict’ messages). However this is restricted to Max6, and your cannot interpolate presets like you would do with pattr.
    Hopefully someday pattr will support dictionaries, which would solve this issue.

Sorry about the inconvenience…

T.

#9

Thanks for the answer.
I don’t use interpolation at all with spat.
to use dict one has to know the data structure of Spat parameters, i think, do you have a simple dict example to use as a working base?

#10
  1. Use the “64 bit” version of Spat (the so-called 32-bit is Max5 compatible and, as a consequence, does not support dict)
  2. Have a look at the spat.oper help patch, in the sub patcher “working with dict in max6”. That should be rather straightforward and you dont need to know the data structure.

T.

#11

Thanks, I’ll have a loot at