Old 11-13-2014, 04:16 PM   #1
K-BooGiE!
Human being with feelings
 
K-BooGiE!'s Avatar
 
Join Date: May 2012
Location: ATL
Posts: 36
Default GlovePie & Wildcards (OSC)

I'm having the hardest time with "@"
wildcards.

Eg: s/track/@/name
GlovePie: osc1.track.@.name //Syntax error

is there a workaround?
K-BooGiE! is offline   Reply With Quote
Old 11-13-2014, 06:41 PM   #2
K-BooGiE!
Human being with feelings
 
K-BooGiE!'s Avatar
 
Join Date: May 2012
Location: ATL
Posts: 36
Default

Maybe escaping "@"
or unicode0040

or?

var.foo = @ //syntax error

Osc2.track.var.foo.name

or?

var.foo = unicode0040

Osc2.track.var.foo.name
K-BooGiE! is offline   Reply With Quote
Old 11-13-2014, 08:21 PM   #3
K-BooGiE!
Human being with feelings
 
K-BooGiE!'s Avatar
 
Join Date: May 2012
Location: ATL
Posts: 36
Default

NOBODY?

Where's Banned.. when you need him
K-BooGiE! is offline   Reply With Quote
Old 11-14-2014, 07:20 AM   #4
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Right here, pal!

I'm not familiar at all with GlovePie's syntax though... sorry! But surely, some other REAPER users familiar with its OSC implementation are. Iirc, Anton9 is the man you should speak to on this one.

In any case, you should understand that the "@" is unique to REAPER, and NOT part of the OSC specs. REAPER will send a specific *number* (for the track, FX slot, or parameter used) instead of the literal "@" symbol.

So, on GlovePie's end, you should NOT try to use the "@" symbol AT ALL. You should either explicitly use numbers (1, 2, 3, etc.) in the OSC addresses corresponding to all different tracks, FX, and parameters (the 'dumb method'), or use *variables* which correspond to track, FX slot and/or parameter number, and then process the messages using those variables (the 'smart method').

Hth, for now!
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 11-14-2014, 07:07 PM   #5
K-BooGiE!
Human being with feelings
 
K-BooGiE!'s Avatar
 
Join Date: May 2012
Location: ATL
Posts: 36
Default

Quote:
Originally Posted by Banned View Post
Right here, pal!

I'm not familiar at all with GlovePie's syntax though... sorry! But surely, some other REAPER users familiar with its OSC implementation are. Iirc, Anton9 is the man you should speak to on this one.

In any case, you should understand that the "@" is unique to REAPER, and NOT part of the OSC specs. REAPER will send a specific *number* (for the track, FX slot, or parameter used) instead of the literal "@" symbol.

So, on GlovePie's end, you should NOT try to use the "@" symbol AT ALL. You should either explicitly use numbers (1, 2, 3, etc.) in the OSC addresses corresponding to all different tracks, FX, and parameters (the 'dumb method'), or use *variables* which correspond to track, FX slot and/or parameter number, and then process the messages using those variables (the 'smart method').

Hth, for now!
Ahh man thx for responding!!!... I like the wildcard function:-( its just a syntax error, it makes glovepie aware of whats going on and can respond when you select some thing.... I didn't want to do the dumb method 1400 lines easy! i did try.. i got maybe 200 lines.."this isnt gonna work right if i have to change one thing". I did try a var with a range

var.x = range((1-100)/10)
debug = var.x //Result = but got nothing back //Keep trying

I did hit up Anton9 on the PM...I seen his name when I was digging deep in the forums.

Looked at oscIIBot? but i dont wanna put a 2 app in the mix just to rescript osc messages.


PM Anton9 for me
Thanks!
K-BooGiE! is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT -7. The time now is 09:24 PM.


Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2024, vBulletin Solutions Inc.