APC40 & live.observer possible bug

[aminoplacid]

Wondering if anyone with M4L & APC40 could try to confirm this situation. I have a very simple Max For Live patch that is supposed to observe the track 1 volume on the APC40 (assuming the APC40 is the 1st or only control surface enabled) and report the value. It only requires that the user push the goto message then the property message to start observing. This is based on my understanding of the live.observer object as per Mike Chenetz' tutorials.

What is happening is when I have the APC40 on then open Live, drag this patch in, click the messages in the proper order, the volume slider doesn't get observed. If I power cycle the APC40 and move the track 1 volume control, it starts reporting as I would expect. I have cleared out all my settings for Live and still this happens.

This goes against all logic as far as I can tell. If anyone can replicate this please post so it can get reported. Seems like a rather big issue especially if this happens with other controllers.

If I'm off my rocker, please also let me know (wouldn't be the first time).

Thanks!


----------begin_max5_patcher----------
913.3oc6X1zjZBCFG+r9oHCmsND.QsSur6zKcl8Tu1YGGDBZZgDljfUamse1
adgWTKfr1Uc6N8BujDR9+7i+OjD94vAVKoaQbKv6AeALXvOGNXftHUACJtef
UZv1vj.ttYVI3Mnwj7TUqFYpeS.iDjhZqZ4czbQBRn6.mhRyBDgqwjUKXnPg
Q.tSlL1dD.55oN45quQVD3whmAGoGC5xu9NneY2a5awtLjoWrrFArhSnAxd8
wpAiIEn.wVfHAKSzsDVKOLoTckExC1fhVDHDL7xbAp9JdAZJXiJ3SxQz3xhK
Ke+wDShoZgWH4CpjxhPLUs1MTYNAazUiOJOCghRvos8zbAJi2VknsYTBhnQO
bbqCtX2Az5fFjJMF55bl1XGjJAqd3ar1x2XMUGVNz3fj8da0X7slxDc37NpK
2f43N5sTZzIhm.BgJBDXJYQ0n1zPkPIq5qrTiZWTJAS9lpu3cIaZjIpL09zv
g0mzGeZ3ndlcSPeWlcUlZIPaE0AAcIGw1HMqmYd8bEUASczo0yZIs1oyz55L
5XJo9U+cLoYAbOMIxZup43eXrtUj8vbcmyfOxWD7fUn+.PYLZFhI1AzeNnYB
A6wW9zDZt9Z+VHDrcBcqoSWtGYTutYt31NW7bmoXgmdpfIvtbNy5137Radfu
flmUTAEDJGTFMYAOmEGDh3.6xh3.emmsipfbFGEblcWVpIudcTgzzT0jTGir
O.tOGmDA1QyYff7HLEfhikQOXMhUQX4GOQgzbyjbNMhP61Q3bsqyWuXj4Z.5
LuY.5YcaMVsQoOa0YLGyVszDp1icGoN3oNJO.2KNafLPayGwglSS6JuzYxIf
C3ShfDb39hOjlPYmVYWab9vEBmt18ml9uYn4E1b51GZ58euYu7ltvd.Sm2Lv
7inM3PDPtVWANTpd4drvUsZMNJBQNZGj8aFESd9zhz8No471g4sZ1j6zSyJW
pxCx0ycoralM8a7ayLttVlzc50wtAuVfMlQSunnsv1oWNieWj0+eNx1xFOxR
xWIQ3ud16X0a1dyHOwsyO605hm43UDU1Z0UuR2dlhRXx4BI2dvH3smQ59Uug
fi9am5.SU9gfiK2XQXoJK1eInN3hPbAln+WP60F0eu..qZT8LEkxKEGkQwDQ
gF77lNdR4F98fU2.drw2t8UpS5gTOLbNoR+KUjFLmjd9WWMA66azqnl5gjt9
JB1CEAOSEIu4og+F7vMxdA
-----------end_max5_patcher-----------

[aminoplacid]

[bump]

Can anyone confirm? This one is killing me.

[S4racen]

Doesn't the live.path need to feed out of the middle outlet to the live observer?

Cheers
D

[aminoplacid]

I've tried it both ways and get the same behavior. Feeding out of the left output of live.path is the way that Mike Chenetz demonstrated on the max4live.info site too.

[aminoplacid]

I appreciate you taking a look at this and confirming my suspicions. I will forward this thread to support.

[charlybeck]

it seems me having the same problem. not only that i don't get it working - i tried two devices which are said to accept matrix button presses and it doesn't work too.

here's my topic:
viewtopic.php?f=35&t=195890&p=1539682&h ... r#p1539682