zion

Almost every time that I use [live.object] or[live.observer] I get ugly massages or errors to the 

 I am following the LOM logic step by step and 

Some times I can get rid of a massage or two but not sure that I am fully understand what it really means.. (is it a meter of priorities and initializations?)

live.object: Changes cannot be triggered by notifications. You will need to defer your response.

live.object: Live API is not initialized, use live.thisdevice to determine when initialization is complete

Hello there -
Almost every time that I use [live.object] or[live.observer] I get ugly massages or errors to the Max Console window - even though I am following the LOM logic step by step and my devices run very well(!!) 

Some times I can get rid of a massage or two but not sure that I am fully understand what it really means.. (is it a meter of priorities and initializations?) 

Here are the dominants-

live.object: Changes cannot be triggered by notifications. You will need to defer your response.

live.observer: 'DeviceIO' object has no attribute ''

live.observer: property : no valid object id

Hello there -
Almost every time that I use [live.object] or[live.observer] I get ugly massages or errors to the Max Console window - even th

red-yellow-massages-errors-when-using-live-object-and-live-observer

#1 and #2… do you initialize with live.thisdevice instead of loadbang? Do you always have a deferlow object after every live.observer? #1 is like the most basic/common error that every M4L dev needs to understand. If your code responds to an automatic change (triggered from a live.observer object), you need to put a [deferlow] between that live observer and any change to a live.object, such as an id message or setting a property value.

#3: you’re trying to observe something invalid on a DeviceIO LOM object. The M4L input/output routing stuff is tricky. Not sure why you wouldn’t have a valid property name (empty string) though.

#4: the thing you thought you were observing either isn’t set (Id 0) or has become invalid (like if a track your were observing got deleted, perhaps?). You are probably sending a “property <something>” message to a live.observer with a bogus or 0 id.

fwiw I think I saw in the most recent Live release notes that warnings / errors either are or can be suppressed in console somehow.

#1 and #2… do you initialize with live.thisdevice instead of loadbang?  Do you always have a deferlow object after every live.observer?  #1 is like the most basic/common error that every M4L dev needs to understand.  If your code responds to an automatic change (triggered from a live.observer object), you need to put a [deferlow] between that live observer and any change to a live.object, such as an id message or setting a property value.

#3: you’re trying to observe something invalid on a DeviceIO LOM object.  The M4L input/output routing stuff is tricky.   Not sure why you wouldn’t have a valid property name (empty string) though.

#4: the thing you thought you were observing either isn’t set (Id 0) or has become invalid (like if a track your were observing got deleted, perhaps?).  You are probably sending a “property <something>” message to a live.observer with a bogus or 0 id.

fwiw I think I saw in the most recent Live release notes that warnings / errors either are or can be suppressed in console somehow. 

I don't know where to start, some time errors happen some times not, and the logic is not clear to me yet..

Lets start with simple - #4 massage - appears even before opening editor. see picture.

observer Bug1.png

I tried to follow your logic according to #4 and I make sure that legal id is there before propriety is coming.. and still when I re-opening the Live project with the attached M4L device I get first thing that - 

Test to Send.amxd

Thank you for answering!!
I don't know where to start, some time errors happen some times not, and the logic is not clear to me yet..

Lets start with simple - #4 massage - appears even before opening editor. see picture.

 I tried to follow your logic according to #4 and I make sure that legal id is there before propriety is coming.. and still when I re-opening the Live project with the attached M4L device I get first thing that - 
"property: no valid object id", any idea why? 
Thanks ahead (-:

" #1 and #2… do you initialize with live.thisdevice instead of loadbang? 

Do you always have a deferlow object after every 

? (to initialize with live.thisdevice ect'..)

] just after every live.object or live.observer ?

And  TYLER MAZAIKA - by saying -
" #1 and #2… do you initialize with live.thisdevice instead of loadbang?  
Do you always have a deferlow object after every live.observer?"
You mean that I should - right? (to initialize with live.thisdevice ect'..)
[deferlow ] just after every live.object or live.observer ?
where can I read about it?
Thanks

observer Bug2.png

 connect at all so where I should put [deferlow]?

And what does 'notification' means when saying - 

'live.object: Changes cannot be triggered by notifications. You will need to defer your response.' 

How can I defer my response and what does it mean?

Here [live.object] does not connect at all so where I should put [deferlow]?
And what does 'notification' means when saying - 
'live.object: Changes cannot be triggered by notifications. You will need to defer your response.' How can I defer my response and what does it mean?
Thanks again!!

comes from [live.observer] when something changes. It is 

 your code that the state of something you care about in the Live set changed.

live.object: Changes cannot be triggered by

 : you are passing a message TO (not from) a [live.object] that was triggered by a 

 If it says "Changes cannot be triggered by" instead of "Setting the id cannot be triggered by" that means you're most likely passing a "set <something> <value>" message into the left inlet of [live.object] in response to a notification.

 : put a [deferlow] after the [live.observer]. Read the help documentation on [deferlow] to understand what it does.

You can probably search this forum for "you will need to defer your response" for this explanation written 45 different ways.

 notifications comes from [live.observer] when something changes.  It is notifying your code that the state of something you care about in the Live set changed.

live.object: Changes cannot be triggered by : you are passing a message TO (not from) a [live.object] that was triggered by a notification.     If it says "Changes cannot be triggered by" instead of "Setting the id cannot be triggered by" that means you're most likely passing a "set <something> <value>" message into the left inlet of [live.object] in response to a notification.

You will need to defer your response : put a [deferlow] after the [live.observer].   Read the help documentation on [deferlow] to understand what it does.

Always... I should've said this before... I'd recommend 1-forum-thread per type of error you don't understand. And search for the individual error messages in the forum. Lumping multiple different errors in one place makes it harder to address them, and it makes it harder for others in the future to find helpful forum entries, too.

Always... I should've said this before... I'd recommend 1-forum-thread per type of error you don't understand.   And search for the individual error messages in the forum.  Lumping multiple different errors in one place makes it harder to address them, and it makes it harder for others in the future to find helpful forum entries, too.

 I have learned a lot and you have been a great helpful so far.

I have some things to read and debug and maybe I'll come back here - Thank you so much!!

O.K  TYLER MAZAIKA I have learned a lot and you have been a great helpful so far.
I have some things to read and debug and maybe I'll come back here - Thank you so much!!
(;

Red / yellow massages / errors when using [live.object] and [live.observer]