Unai Barruetabeña

I'm very beginner max for live user. I've been using synthedit until a month, which is very different from max. I bought a Roland integra 7 sound module and started making an editor in max, everithing ok, but then I decided to make some "addons" like an envelope generator, which is a copy-paste from another device and then adapted (lots of hours reading tutorials). The addon works fine, but I get a ""$" variable out of range (1)" error. I expended a lot more hours reading and trying a lot off tricks from the forum, but I can't find were the error is. Can anyboddy tell me how can I find a solution?

comment

button

message

gswitch

scale

toggle

gate

live.text

pattr

attrui

function

change

flonum

ggate

line

metro

expr

live.numbox

prepend

rslider

outlet

inlet

live.menu

live.button

bgcolor

route

vexpr

live.thisdevice

live.colors

plugsync~

stripnote

unpack

midiparse

panel

live.dial

autopattr

pattrstorage

preset

midiformat

midiout

midiin

Hi there:
I'm very beginner max for live user. I've been using synthedit until a month, which is very different from max. I bought a Roland integra 7 sound module and started making an editor in max, everithing ok, but then I decided to make some "addons" like an envelope generator, which is a copy-paste from another device and then adapted (lots of hours reading tutorials). The addon works fine, but I get a ""$" variable out of range (1)" error. I expended a lot more hours reading and trying a lot off tricks from the forum, but I can't find were the error is. Can anyboddy tell me how can I find a solution?


Hi there:
I'm very beginner max for live user. I've been using synthedit until a month, which is very different from max. I bought a Roland 

""-variable-out-of-range-can't-solve

i havent looked at you patch, but mister $ is restricted to 1-9

also, when used inside a message box object, you dont need to/have to write the data type behind it (such as $i1 - it is just $1 in message box)

but that error message could also be something else, i´ve seen it in other contexts.

also, when used inside a message box object, you dont need to/have to write the data type behind it (such as $i1 - it is just $1 in message box)

check for those 2 issues first.

but that error message could also be something else, i´ve seen it in other contexts.

Thank's for the reply. I've seen those possible issues in the forum and checked them, I think it's all ok, but i'll have a second look to $i1/$1, as you say the "i" isn't necessary in messages, no?

Thank's for the reply. I've seen those possible issues in the forum and checked them, I think it's all ok, but i'll have a second look to  $i1/$1, as you say the "i" isn't necessary in messages, no?
Thanks again.


No way, I can't find where the problem is, any ideas please?

there appears to be something seriously wrong with your patch-- it causes max to freeze when I paste it into a new patcher window. Try posting just the part of the patch that illustrates your difficulty, otherwise no one can really help.

[metro $1] seems to cause that problem here. (Near lower right corner of your patch.)

Thanks a lot for your time!! I'll have a look as soon as possible and tell you the result.

Well, I had a look and for a moment I thought I had find the problem. As you, bill, said there was a problem with metro. There was a "recieve tempo" object but there was no "send tempo" object to send the tempo, so I thought that de $ variable was receiving a zero value. I fixed it with a "plugsync" connected to a "send tempo", It hasn't fixed the error, but now works much better, of course (LOL). Thanks a lot!!

Well, I had a look and for a moment I thought I had find the problem. As you, bill, said there was a problem with metro. There was a "recieve tempo" object but there was no "send tempo" object to send the tempo, so I thought that de $ variable was receiving a zero value. I fixed it with a "plugsync"  connected to a "send tempo", It hasn't fixed the error, but now works much better, of course (LOL). Thanks a lot!!

OK, Bill Canty, sorry for my ignorance, reading references, tutorials and forum I understand that the $1 argument is absolutely out of place in metro object, isn't it? In some examples I saw no argument at all, I mean, only metro and nothing else. May be this is the best option in my case, don't you think so? Thanks for your time again.

Hi Unai, I haven't actually had much of a look at what you're doing with [metro]. I just deleted things in your patch till I realized that's where the problem was, then made a new patch with just [metro $1] and got the same error message. Error messages are sometimes the best way to figure out whether or not you can do something. ;-)

Giving it an initial value as an argument, or leaving it blank then sending a value to its right inlet are both simple and valid options.

it can be a good idea to leave the console window open while programming.

 I understand that the $1 argument is absolutely out of place in metro object

yes., for sure.

it  can be a good idea to leave the console window open while programming.


OK! Thanks a lot for tour help, you've been really kind , It's working fine now and I hope I will leave the editor available for the community soon! Cheers

"$" variable out of range, can't solve