APC40 Button_Matrix -> Value property missing (?)

charlybeck · Post by **charlybeck** » Thu Jul 25, 2013 12:45 am

Hello,

tonight i digged a bit into controlling my apc40. I used two existing several devices for learning / comparing.

Each device is supposed to react on button presses of the apc 40 but it doesn't work. [1]

Digging a bit deeper i found there is the Button_Matrix control object which is supposed to have a property 'value'.

However, when i observe this property (live.observer) i only get bangs but no values as it is shown on a web example. [2]

Also there is the LOM.Navigator which shows properties of the Button_Matrix but there is no value property.

Of course i have enabled input in the control surface settings for the apc40.

The midi in/out for apc40 is turned of, however i tried switching it on but i guess it doesn't matter.

Any help out there?

czeers,
charly

[1] i used apc_FxSeq by marc egloff, FBO Drum O Box and the LOM.Navigator
[2] http://synthfan.info/2012/09/18/the-apc ... -for-live/

charlybeck · Post by **charlybeck** » Thu Jul 25, 2013 1:18 am

ok got it....

the 'set_report_values' functions needs to be called with parameter 1...

seems there has been some api change... not so nice...

charlybeck · Post by **charlybeck** » Thu Jul 25, 2013 1:34 am

set_report_values is there on the buttons but actually not on the button_matrix...... crisis...

JuanSOLO · Post by **JuanSOLO** » Fri Jul 26, 2013 3:51 pm

I'm not at home right now, so I cant be precise.
However, in the Mark Egloff step sequencer you will find a matrix object hooked up to an unpack and a few more math type objects.

I used this bit of patching to learn how to get the button matrix form the APC40 to spit out whatever I needed, specifically, button 1 is "1" when pressed "0" when released.
button 2 is "2" when pressed "0" when released. All the way up till 40.

charlybeck · Post by **charlybeck** » Sat Jul 27, 2013 7:19 pm

Hi i succeded observing the apc40 buttons.

however i receive no more messages when i add the FBO-Drum-o-Box.

Guess it has something to do the drum-o-box allocates an exclusive access to the apc40.

I see also the native apc40 support from live is disabled when the drum-o-box is added as an device.

I will open another thread for this issue.

APC40 Button_Matrix -> Value property missing (?)

APC40 Button_Matrix -> Value property missing (?)

Re: APC40 Button_Matrix -> Value property missing (?)

Re: APC40 Button_Matrix -> Value property missing (?)

Re: APC40 Button_Matrix -> Value property missing (?)

Re: APC40 Button_Matrix -> Value property missing (?)