strange display with live objects (gray diagonal lines)

julienrobert's icon

I am sing live.dial object comming from the last version of max/msp.

While tweeking with its parameters, sometimes, its display change for nothing. Some gray diagonals appear and I can not anything about it. Why? What are these diagonals?

I would post a print screen of it but the new forum does not seem to let me do it...

Emmanuel Jourdan's icon

the stripes disappear when you save the patch, right? It's there to indicate to the Max for Live user that a change in a live.* object occurred and that he has to save the device in order to have those changes reflected in Live.

julienrobert's icon

you're right. it disappears when I save it.

nick rothwell | project cassiel's icon

Is the stripe decoration documented? The reason I ask is that my understanding (based on, if I recall correctly, a message from DZ several months ago) is that the striping is an indication that existing Live automation data may be invalid.

Emmanuel Jourdan's icon

It has to do with the fact that changing a parameter aware object will have some implication on the Live behavior. Until you save the device, Live won't know about those big changes.

Guillaume LEGER's icon

Hi!
As a beginner, I wanted to say your questions and answers about this behavior is still valid today in 2021.
The grey zebra background for objects in max MSP or max for live, which appear sometimes, disappear when you save the patch !

toro erhard's icon

Hi everybody.

For some reason these diagonal lines do NOT disappear after I save the patch. Also, does anybody have any idea why they appear in the first place?

Just using standalone Max 8 creating noise particles on a Mac book pro.

Thanks in advance

notsteve's icon

Same behaviour. Saving doesn't change it. I once accidentally titled one of bpatchers to the same name of an internal object. I erased all the instances, but that's when the dialogue lines started - and it's the same object. If I copy everything to new patches (ugh), everything works again. For a while…