Mark

button

message

counter

print

live.thisdevice

comment

live.observer

live.path

the live.observer is sending it's values twice when the m4l device is initialized.

if yes, is there any way to overcome this, in order to receive the values only once?

if this is a bug, does anyone know if it has been fixed?

the live.observer is sending it's values twice when the m4l device is initialized.
is this behavior normal?
if yes, is there any way to overcome this, in order to receive the values only once?
if this is a bug,  does anyone know if it has been fixed?
i'm using max 7.0.3 and ableton 9.7.3
thanks



 
the live.observer is sending it's values twice when the m4l device is initialized.
is this behavior normal?
if yes, is there any way to o

why-is-live·observer-sending-values-twice-in-initialization

Not sure if it's normal behaviour but you can easily avoid repeated values by inserting [change], or [zl.change] for lists.

Bang your path live_set first (right to left rule/ toggle object) and you'll just get one list, not two.

If the problem is only on my pc then it's probably a bug that has been fixed.

Or else it's either supposed to work that way, or it's a bug that hasn't been fixed.

Anyway I managed to work around the problem, but still it would be good to know if this is normal behaviour for live.observer.

It still gives me more than one list.
Did you test the patch you pasted?
If the problem is only on my pc then it's probably a bug that has been fixed.
Or else it's either supposed to work that way, or it's a bug that hasn't been fixed.

Anyway I managed to work around the problem, but still it would be good to know if this is normal behaviour for live.observer.


I've tested this, sure. Just one list, OSX and (!) Win.

I've put your patch into a device, saved and reloaded the Live set and get 2 lists.

BUT, when unchecking 'Persistent Mapping' of the observer, both patches yours and the original give only 1 list.

@Herr Markant
I've put your patch into a device, saved and reloaded the Live set and get 2 lists.

markant i suppose your live.observer had persistent mapping disabled when you tested?

thanks broc, good to know this.
 markant i suppose your live.observer had persistent mapping disabled when you tested?


I have this issue today with Live 11.1.5 and Max 8.2.2 and 8.3.1.

The first time the example from Herr Markant is pasted it works fine. After that it outputs twice as OP also mentioned.

In the small example below it also prints twice to the console. In a normal patch it also outputs twice to other objects in the patch, so it's not a print issue.

A weird thing is happening when I change the property ‘cue_points’ to ‘tracks’ and then double click live.thisdevice. It still outputs twice. However, the first time after the change, the first output shows the id’s of the cue points and the second output the id of the track. As if the observer memorized the previous property..

When I double click again on live.thisdevice, I get twice the id of the track.

Why is this happening and what is a real solution?

I have this issue today with Live 11.1.5 and Max 8.2.2 and 8.3.1.

The first time the example from Herr Markant is pasted it works fine. After that it outputs twice as OP also mentioned.

 Persistent mapping has no effect at all. 

In the small example below it also prints twice to the console. In a normal patch it also outputs twice to other objects in the patch, so it's not a print issue.

A weird thing is happening when I change the property ‘cue_points’ to ‘tracks’ and then double click live.thisdevice. It still outputs twice. However, the first time after the change, the first output shows the id’s of the cue points and the second output the id of the track. As if the observer memorized the previous property..
When I double click again on live.thisdevice, I get twice the id of the track.

Why is this happening and what is a real solution?

stil the same issue here..
someone knows a workaround ?

I wonder if this is what is happening on Push 3 standalone, rendering some takeover/live.observer devices to stop functioning (more or less) randomly. First time a device is loaded after power up, everything works correctly, but creating a new set and adding the device will sometimes no longer work, as if the observer stops working correctly

why is live.observer sending values twice in initialization?