question: how do i define remote for a m4l instr?

[11olsen]

hello, can you help?
how do i define which parameters of my m4l intrument are controlled by the live remote input. you know - the blue hand is on the device. the order of the 8*8 parameters.

[hoffman2k]

hello, can you help?
how do i define which parameters of my m4l intrument are controlled by the live remote input. you know - the blue hand is on the device. the order of the 8*8 parameters.

With the "Order" attribute of a parameter or in the Order column in the parameter inspector.
0 is Device On/Off, so start from 1.

[11olsen]

thanks!

[Surreal]

i have said it elsewhere, but i would LOVE to separate 'order' from this functionality. i had to use order to control loading...which means i can't give up the order i have.

[broc]

+1

The combined functionality of 'order' and 'number' makes no sense.

Btw, is this documented somewhere?

[pid]

predictably, totally +1 here broc and all. this order combined thing is utterly ridiculous and counterintuitive to how max itself works. i long for many more columns in that "Parameters View" etc...

yes it is documented. really amusingly. my favourite entry is in the ref page for parameter view:

"
Properties
Name Type Description
Order int Order
"

that is all.

[Surreal]

it would be nice to have a parameter with 2 ints.

<page> <number>


pretty please
EDIT: aha! - http://forum.ableton.com/viewtopic.php?f=3&t=143688

[swishniak]

ive been trying to add remote device (blue hand) to a patch using the object hierarchy but i cant get it to work. instead the first controller (of any remote device control surface) turns the device off, even though i started at one (and tried 2, etc).

its a pretty simple patch i wanted to make so i could automap at least 8 paramenters to a nord micro modular. . got the ccs going out. that part is working..

if anyone wants to take a look: http://www.mediafire.com/?37n71jmhrrpecix

[amounra93]

+1 to the ordering thing...I kinda understand why it is such as it is, but we should definitely have different properties for init order and automation order.

instead the first controller (of any remote device control surface) turns the device off, even though i started at one (and tried 2, etc).

The first parameter of a device (parameter 0) is always on/off, no matter how you order the rest of them. Start from 1.

[swishniak]

instead the first controller (of any remote device control surface) turns the device off, even though i started at one (and tried 2, etc).

The first parameter of a device (parameter 0) is always on/off, no matter how you order the rest of them. Start from 1.

like i said, i started at 1

?

[hoffman2k]

ive been trying to add remote device (blue hand) to a patch using the object hierarchy but i cant get it to work. instead the first controller (of any remote device control surface) turns the device off, even though i started at one (and tried 2, etc).

its a pretty simple patch i wanted to make so i could automap at least 8 paramenters to a nord micro modular. . got the ccs going out. that part is working..

if anyone wants to take a look: http://www.mediafire.com/?37n71jmhrrpecix

That is a .adv file. Useless without the device.

[swishniak]

sorry about that

here it is (a week later)

http://www.mediafire.com/?jark9q1355c5wcr

hopefully someone can still give me a tip. thanks.

[swishniak]

another thing; i realized something might be wrong with my automap/remote settings. my control surfaces (oxygen / trigger finger / nano kontrol) all automap to non-m4L macros in live, but when the blue hand is on a max device it is not recognized.. any ideas?

[Surreal]

are your parameters 'automated and stored?'