bug ??? on pads

Discuss problems and solutions.
oran-outan
Newbie
Posts:39
Joined:18 Dec 2011 17:30
bug ??? on pads

Post by oran-outan » 23 Feb 2012 19:45

hi

from max/msp when i sent a list message ( 0 0 0 0 0 0 )/ (1 1 1 1 1 1 ) of six element with argument "freeze" or "color" + osc address on a pad with 6 columns, the list is decay to 1 element on pads : the first element of the list is the 2nd pad, the 2nd element of the list is the third pad,....

is there a bug ? or not ?

thanks
f
Attachments
freeze.tiff
freeze.tiff (14.89KiB)Viewed 4963 times

axel_liine
Liine Staff
Posts:126
Joined:14 Dec 2011 12:12

Re: bug ??? on pads

Post by axel_liine » 23 Feb 2012 20:55

I can't see the attachment. Can you post a screenshot of the Max patch ?

Macciza
Regular
Posts:1325
Joined:07 Dec 2011 04:57
Location:Sydney, Australia.

Re: bug ??? on pads

Post by Macciza » 23 Feb 2012 23:05

Hi
Can't reproduce your shift problem, butI can see a potential issue or two here . .
Pop a message box in so you can inspect the messages that are sent . ..

It looks like your address would end up with /control/bow color - The space is a complication here
Prepend adds the space. Did you want /control/bowcolor or /control/bow/color ?
If you are trying to vary the color you need to make it '/control/bow @color' for attributes . . .

Also the arguments and data range is important - color generally expects 0 to 8355711 and color for Pads can be {int, int} for off/on color as well,
Also the Pads do not have a 'Freeze' attribute so that won't work at all, sorry . . .

Sending /color/bow/x will set the state of the Pads correctly as per your list values 0/1 . . .
No bug that I could see . . .

Cheers
MM
iMac 2.8G i7 12G 10.6.8/10.7.2, Legacy Dexter/Lemur, Liine Lemur/iPad2, KMI SoftStep, 12Step & QuNeo , B-Controls, Mackie C4 etc
MaxMSP, Live Suite, Native Instrument stuff, etc Modified Virtual Guitar System etc All Projects/Modules © CC-BY-NC-SA[*][/b]

oran-outan
Newbie
Posts:39
Joined:18 Dec 2011 17:30

Re: bug ??? on pads

Post by oran-outan » 24 Feb 2012 11:01

hi

yes i try to change the pad color....
if i used /control/bow @color i have the same problem !
i join a screenshot of the patch

in fact, i want make osc looping to visual feedback of the interaction whose i do :
i make manual control on pads (touch with fingers), and sent control from max stuff on same pads (from a sequencer or from interactif feedback control mapping). all used the same lane on the max patch, then i make osc loop. when i touch pads the osc feedback comeback with decay or fault.

my interest is to make interactive control on pads... ---> if i touch it quickly the pads is like a trigger (touch : 1, no touch : 0), but if i stay in touch more than 5 seconds the pads come like a switch and stay in 1 (hold the comeback to 0 and stay in 1)...i can take off my finger...
then if i touch it again and take off finger he come back to pad and down to 0, and come back a trigger...

certainly the best is to do that directly on lemur app ! but how do that ?
best
f
Attachments
oscosc.tiff
oscosc.tiff (47.93KiB)Viewed 4939 times

axel_liine
Liine Staff
Posts:126
Joined:14 Dec 2011 12:12

Re: bug ??? on pads

Post by axel_liine » 24 Feb 2012 12:42

A couple problems here :
- the Pads must be set to 'Multicolor' in the Editor settings
- the attribute name is "colors", not "color". Therefore you should send /control/bow @colors a b c d e f
- you won't tell the difference between color 0 and color 1, try larger values

oran-outan
Newbie
Posts:39
Joined:18 Dec 2011 17:30

Re: bug ??? on pads

Post by oran-outan » 24 Feb 2012 13:46

sorry, but always no...

in link the lemur template

here the max5 patch
you can test...
best


----------begin_max5_patcher----------
912.3ocyXszbaBCD9r8uBMb1kHIDBnmZO1SsGZOkISGdnPnEiX.bSZyj+6EI
AAbLXdXahGOCFIdn86a2ucWwyqWo4wehkqA9H3VvpUOud0J4ThIVUMdk1V2m
7icyk2llOe6VVRg1F00JXOUHmOkmU.95O9d8EtmmTjG8Ol3hHrNrd5rPO0xA
0gHSpMci7LjE0r8YHcH3tpmI0sv+gnjvelw7KTOLgHdk.DEJ9iZKNhgsdljc
a46JhYERqtd0SyX4kFuaQDOQZXsPgOOlmMUSKJPBdt2u9.1nMzSb2Jgt1myh
bi05X8agFLAI..wpevDkTiETqU4dWeEAKl5k0qEG1LRGY4K0ikMf6pSpmHod
KocZBGf5wCP8pas3uoL0qWKRDbAz7bSB0d8cNaGTQI8mDFyZGEz1ogF1o4E1
ZkkNplCswcuNWpzsZzCc4wyBXY6CtM6cvwlXfHW3nA1ik7wAp5rR2CCHG1Qf
hywhSLrj3FaHiSH1pflAiSNHdPDLn0kfyZXW29T0LnEAxYAQGltCQczwlDcC
jNF6rLI8LHlJRTlm.AQCH8HSU5In5J429r94H+H8hqzPDiFkVWzyIJ0NexpR
.jxRB.hhlSVXUk.FaJKARwCHr52a2kWBgW.UUe8P.9x2.tAkN2bPo0tThJkZ
RwiNVWAcRffytSBjpXiBScClEq1QcP9C774W8npAOiyZPt4BDi2WAUPAWmm6
OcUOUo5UscQfmNg71bsM4A6ItzjNQdCd93scAo4hfo55t1k+AbfP3bSeZfTI
NwCEZ0QWilKQqGaKSC5FxNfItwubMy3w23weD7IoSLG.a9M8N5QPIiPvJImZ
Dx9LI1LlJYgWvMyPkcTgcjB.KmQtWlwsmk1YzcVhdU4ghM5zOXwJ7Y+JLOJX
O5Fz5bCv3KdCBYrB9tLvehx2whmQftphngsTyWUgANEkOh79U5H082fnleSG
9J+e0tHvlV5lyK.n6P7oJyom+NM5J03roI6pcrNacRmzD058K.J+H8dLFJgf
TeCC7z0MT6S.1xkQKNJ4seoRokJleetHuLGgesWndSMfFqMfkWDk7Zq621TT
u0M8PTP.KoMb1FEjxKS9UYDf65zyLVaR7kmFzldigeosIyqOZRzy4Y2lHVFh
beFPUuzlMiNQqcLF6xxeVig9V1.+wHFQKKKI5O6Zylniw0IZtFfVNdZL1D8J
jmD0elsMUN3k0+mkRSSe
-----------end_max5_patcher-----------

axel_liine
Liine Staff
Posts:126
Joined:14 Dec 2011 12:12

Re: bug ??? on pads

Post by axel_liine » 24 Feb 2012 14:54

oran-outan wrote:sorry, but always no...

in link the lemur template

here the max5 patch
you can test...
best


----------begin_max5_patcher----------
912.3ocyXszbaBCD9r8uBMb1kHIDBnmZO1SsGZOkISGdnPnEiX.bSZyj+6EI
AAbLXdXahGOCFIdn86a2ucWwyqWo4wehkqA9H3VvpUOud0J4ThIVUMdk1V2m
7icyk2llOe6VVRg1F00JXOUHmOkmU.95O9d8EtmmTjG8Ol3hHrNrd5rPO0xA
0gHSpMci7LjE0r8YHcH3tpmI0sv+gnjvelw7KTOLgHdk.DEJ9iZKNhgsdljc
a46JhYERqtd0SyX4kFuaQDOQZXsPgOOlmMUSKJPBdt2u9.1nMzSb2Jgt1myh
bi05X8agFLAI..wpevDkTiETqU4dWeEAKl5k0qEG1LRGY4K0ikMf6pSpmHod
KocZBGf5wCP8pas3uoL0qWKRDbAz7bSB0d8cNaGTQI8mDFyZGEz1ogF1o4E1
ZkkNplCswcuNWpzsZzCc4wyBXY6CtM6cvwlXfHW3nA1ik7wAp5rR2CCHG1Qf
hywhSLrj3FaHiSH1pflAiSNHdPDLn0kfyZXW29T0LnEAxYAQGltCQczwlDcC
jNF6rLI8LHlJRTlm.AQCH8HSU5In5J429r94H+H8hqzPDiFkVWzyIJ0NexpR
.jxRB.hhlSVXUk.FaJKARwCHr52a2kWBgW.UUe8P.9x2.tAkN2bPo0tThJkZ
RwiNVWAcRffytSBjpXiBScClEq1QcP9C774W8npAOiyZPt4BDi2WAUPAWmm6
OcUOUo5UscQfmNg71bsM4A6ItzjNQdCd93scAo4hfo55t1k+AbfP3bSeZfTI
NwCEZ0QWilKQqGaKSC5FxNfItwubMy3w23weD7IoSLG.a9M8N5QPIiPvJImZ
Dx9LI1LlJYgWvMyPkcTgcjB.KmQtWlwsmk1YzcVhdU4ghM5zOXwJ7Y+JLOJX
O5Fz5bCv3KdCBYrB9tLvehx2whmQftphngsTyWUgANEkOh79U5H082fnleSG
9J+e0tHvlV5lyK.n6P7oJyom+NM5J03roI6pcrNacRmzD058K.J+H8dLFJgf
TeCC7z0MT6S.1xkQKNJ4seoRokJleetHuLGgesWndSMfFqMfkWDk7Zq621TT
u0M8PTP.KoMb1FEjxKS9UYDf65zyLVaR7kmFzldigeosIyqOZRzy4Y2lHVFh
beFPUuzlMiNQqcLF6xxeVig9V1.+wHFQKKKI5O6Zylniw0IZtFfVNdZL1D8J
jmD0elsMUN3k0+mkRSSe
-----------end_max5_patcher-----------
Can't see the Lemur template link. Can you elaborate on what happens exactly ?

oran-outan
Newbie
Posts:39
Joined:18 Dec 2011 17:30

Re: bug ??? on pads

Post by oran-outan » 24 Feb 2012 19:28

hi

i'm on macbookpro 10.7with max 5
iPad (version 1) with IOS 5
- I create a WIFI local host with automatic IP
- on max used udpsend object to send OSC message (to Lemur app)
host (LemurIP ): 192.168.x.x ---- port 8000

from max when i sent a list message of six element on pads with 6 columns with address : /control/bow @colors 0 0 0 0 0 0 or 1 1 1 1 1 the list is decay to 1 element on pads == the first element of the list is the 2nd pad, the 2nd element of the list is the third pad,....

send 1 or 800000 don't make any different
he made the same with argument @freeze
if my osc message is good i think lemur take the @colors like a value and not like an argument. but i don't understand all of the lemur stuff !

in fact i try this stuff (to change color than on/off pad) because i create osc loop (see higher on forum subject), and have time decay whose causes fault on control.
in general, i have problem with osc message send in realtime, or on osc loop stuff. i have time decay...

used port 8000 or 8001 can change something ? or is there a possibility to create a personal number port ?

i used touchosc before and don't had this kind of problem
your suggest are welcome...

best
Attachments
padstest.jzml
(2.47KiB)Downloaded 126 times

Macciza
Regular
Posts:1325
Joined:07 Dec 2011 04:57
Location:Sydney, Australia.

Re: bug ??? on pads

Post by Macciza » 26 Feb 2012 04:35

Hi
It seems that there may be an issue when using custom paths,but there is a workaround
The Pads will respond to the Object name -controlbow- but we can't have '/' in name obviously . . .

However, if you wrap it in a Container then the default name can be control/bow - container/object
You would then refer to it as such in code which would not hurt either I suppose
I suppose it actually does fit in nicely with OSC concepts and terminology i
Bit of a wiry one there, but got it kinda worked out . . .

Hope that helps

Cheers
MM
iMac 2.8G i7 12G 10.6.8/10.7.2, Legacy Dexter/Lemur, Liine Lemur/iPad2, KMI SoftStep, 12Step & QuNeo , B-Controls, Mackie C4 etc
MaxMSP, Live Suite, Native Instrument stuff, etc Modified Virtual Guitar System etc All Projects/Modules © CC-BY-NC-SA[*][/b]

axel_liine
Liine Staff
Posts:126
Joined:14 Dec 2011 12:12

Re: bug ??? on pads

Post by axel_liine » 26 Feb 2012 15:40

Custom OSC paths apply only to a give variable, here the 'x' variable.
Setting an object's attribute require to use its normal address, which is /controlbow here.
By sending /control/bow @colors a b c d, you're effectively sending a message to the x variable of the object : {'@colors", a, b, c...}. The result is the Pad will try to set its sub-pads states to each of the items in the message, which is not what you want.

Post Reply