Old 02-29-2012, 10:10 AM   #281
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 10,316
Default

Quote:
Originally Posted by musicbynumbers View Post
Can OSC be used to assign a few controllers to the selected track's "track controls" section (I mean the ones you assign to show up in the MCP or TCP as knobs) in such a way that when you change track, the assigned controllers now control the newly selected track's "track controls".
You can do this by assigning the OSC controls to the existing actions "adjust track FX parameter 01", etc.
schwa is offline   Reply With Quote
Old 02-29-2012, 10:11 AM   #282
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 10,316
Default

Quote:
Originally Posted by johnrule View Post
I didn't see a response to this, so I will ask again:

Is there any way to covertly load a project (i.e. without the dialog)?

I would like to send a string (via OSC, UDP, TCP, or even HTTP) to load a new project by file path.
Not yet. You could also load up the projects you want and use the existing actions "next project tab" and "previous project tab".
schwa is offline   Reply With Quote
Old 02-29-2012, 10:30 AM   #283
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by schwa View Post
You can do this by assigning the OSC controls to the existing actions "adjust track FX parameter 01", etc.
I suggest the naming of those actions is changed to mention OSC: "(MIDI CC/OSC only)".
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 02-29-2012, 11:10 AM   #284
musicbynumbers
Human being with feelings
 
musicbynumbers's Avatar
 
Join Date: Jun 2009
Location: brighton, uk
Posts: 12,753
Default

Quote:
Originally Posted by schwa View Post
You can do this by assigning the OSC controls to the existing actions "adjust track FX parameter 01", etc.
Thanks, I did try that though (albeit few releases ago) and I got erratic results but will try again when I have time and report back
musicbynumbers is offline   Reply With Quote
Old 02-29-2012, 12:12 PM   #285
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Also, using actions for that purpose does not generate OSC feedback.
Thus it seems very useful to add a dedicated bidirectional OSC pattern for track fx parameters (and while you're at it, please increase the number of available parameter slots a bit).
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 02-29-2012, 01:00 PM   #286
diversgens
Human being with feelings
 
Join Date: Oct 2010
Location: France
Posts: 125
Default

Quote:
Originally Posted by schwa View Post
Sorry, can you be more specific? Are you saying that the touchosc screen works as you expect, but you don't see how to make lemur behave the same way?
I only have a screenshot of TouchOsc used with Logic (image attached) and what i try to do is the behaviour marked red with the name of the insert instead of the numbers. Is it possible ?
Attached Images
File Type: jpg logicpad2.jpg (66.0 KB, 71 views)
diversgens is offline   Reply With Quote
Old 02-29-2012, 01:25 PM   #287
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 10,316
Default

Quote:
Originally Posted by diversgens View Post
I only have a screenshot of TouchOsc used with Logic (image attached) and what i try to do is the behaviour marked red with the name of the insert instead of the numbers. Is it possible ?
The device should receive FX_NAME messages for the current track (/fx/1/name, fx/2/name, etc by default). The buttons you marked are mapped to FX_BYPASS in the LogicPad config file. If you are designing a Lemur template, you should be able to place FX_NAME labels next to FX_BYPASS buttons to get the behavior you want.
schwa is offline   Reply With Quote
Old 02-29-2012, 01:46 PM   #288
diversgens
Human being with feelings
 
Join Date: Oct 2010
Location: France
Posts: 125
Default

Quote:
Originally Posted by schwa View Post
The device should receive FX_NAME messages for the current track (/fx/1/name, fx/2/name, etc by default). The buttons you marked are mapped to FX_BYPASS in the LogicPad config file. If you are designing a Lemur template, you should be able to place FX_NAME labels next to FX_BYPASS buttons to get the behavior you want.
Yes this is exactly what i have done but the list of each FX_NAME is not actualized until i click on the FX_BYPASS or FX_EDIT for each insert.
For example if a have three track with three insert on each and click on a NEXT_TRACK button, i (sometimes) see the name of the first insert; to see the two other i have to click on each FX_EDIT or FX_BYPASS button.
I have monitoring the output from Reaper on PD but never see a send for all the insert per track. I hope being clear enough ...

edit: i add a screenshot to explain what i want to do
Attached Images
File Type: jpg Fx_name2.jpg (58.1 KB, 78 views)

Last edited by diversgens; 02-29-2012 at 02:05 PM. Reason: add screenshot
diversgens is offline   Reply With Quote
Old 02-29-2012, 02:11 PM   #289
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 10,316
Default

Ah... that we can fix.
schwa is offline   Reply With Quote
Old 02-29-2012, 02:34 PM   #290
BenK-msx
Human being with feelings
 
BenK-msx's Avatar
 
Join Date: Jun 2008
Location: Whales, UK
Posts: 5,676
Default

hi i am not getting any joy with all things LAST_TOUCHED (FX)..

any chance of a clue?

'focused' for example is doing fine..

I have this in reapers config: (for touchosc)

FX_FOLLOWS_LAST_TOUCHED /fxfollows/last_touched

and then this:

FX_PARAM_NAME /fxfollows/last_touched/lparname@
FX_PARAM_VALUE /fxfollows/last_touched/lfxpar@
FX_PARAM_VALUE_STRING /fxfollows/last_touched/lparval@


the listen window fills up as expected with these when i operate the device, but i get NADA reponse in the last touched parameter department from reaper.

where have i been a thicky?

btw i am expecting to get value & name feedback plus control of the last touched (by mouse) fx parameter, just to be clear. thanks in advance.

Last edited by BenK-msx; 02-29-2012 at 02:58 PM.
BenK-msx is offline   Reply With Quote
Old 02-29-2012, 02:42 PM   #291
Subz
Human being with feelings
 
Subz's Avatar
 
Join Date: Jun 2006
Location: UK
Posts: 2,963
Default

Quote:
Originally Posted by BenK-msx View Post
hi i am not getting any joy with all things LAST_TOUCHED ..

any chance of a clue?

'focused' for example is doing fine..

I have this in reapers config: (for touchosc)

FX_FOLLOWS_LAST_TOUCHED /fxfollows/last_touched

and then this:

FX_PARAM_NAME /fxfollows/last_touched/lparname@
FX_PARAM_VALUE /fxfollows/last_touched/lfxpar@
FX_PARAM_VALUE_STRING /fxfollows/last_touched/lparval@


the listen window fills up as expected with these when i operate the device, but i get NADA reponse in the last touched parameter department from reaper.

where have i been a thicky?

btw i am expecting to get value & name feedback plus control of the last touched (by mouse) fx parameter, just to be clear. thanks in advance.

feel free to look at my preset that follows last touched & focused fx on page 4 of touch osc only http://forum.cockos.com/showthread.php?t=97866

i dont fully understand it as i just modded the original LogicTouch preset

but the info you need may be there

Subz
Subz is offline   Reply With Quote
Old 02-29-2012, 02:44 PM   #292
musicbynumbers
Human being with feelings
 
musicbynumbers's Avatar
 
Join Date: Jun 2009
Location: brighton, uk
Posts: 12,753
Default

Quote:
Originally Posted by Banned View Post
Also, using actions for that purpose does not generate OSC feedback.
Thus it seems very useful to add a dedicated bidirectional OSC pattern for track fx parameters (and while you're at it, please increase the number of available parameter slots a bit).
this

If naming a track control can also update the OSC device's GUI it would be amazing, especially if it can do this for the selected track as I change tracks.
musicbynumbers is offline   Reply With Quote
Old 02-29-2012, 02:55 PM   #293
BenK-msx
Human being with feelings
 
BenK-msx's Avatar
 
Join Date: Jun 2008
Location: Whales, UK
Posts: 5,676
Default

Quote:
Originally Posted by Subz View Post
feel free to look at my preset that follows last touched & focused fx on page 4 of touch osc only http://forum.cockos.com/showthread.php?t=97866

but the info you need may be there

Subz
cheers.. though yours was what got me started subz
following focus is working great, but can't see anything in there for last touched fx parameter unfortunately despite that, following the example of 'focused' i thought it would be easy, but its a no go for some reason.. can't fathom it.


so any help from anywhere on getting LAST TOUCHED FX PARAMETER stuff going as mentioned above #290 would be greatly appreciated!
BenK-msx is offline   Reply With Quote
Old 02-29-2012, 03:09 PM   #294
diversgens
Human being with feelings
 
Join Date: Oct 2010
Location: France
Posts: 125
Default

Quote:
Originally Posted by schwa View Post
Ah... that we can fix.
Yesss, thank you, will wait for it.
diversgens is offline   Reply With Quote
Old 02-29-2012, 03:26 PM   #295
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by BenK-msx View Post
[...]I have this in reapers config: (for touchosc)
[...]
/fxfollows/last_touched
[...]
Try sending a 1 to that address first to activate that mode (sorry, can't test atm; I use a different pattern, sending mode name to
Code:
/fxfollows
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 02-29-2012, 04:23 PM   #296
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by BenK-msx View Post
[...] where should i be sticking this '1' sending from the device (touch osc)?
Try:
Code:
/fxfollows/last_touched 1
That is, use a space between the address and the value.

PS: tried using OSC with that huge thing in your avatar pic yet?
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 02-29-2012, 04:33 PM   #297
MuhamedAli
Human being with feelings
 
Join Date: Feb 2012
Posts: 1
Default good work

this is good work!
MuhamedAli is offline   Reply With Quote
Old 02-29-2012, 04:35 PM   #298
BenK-msx
Human being with feelings
 
BenK-msx's Avatar
 
Join Date: Jun 2008
Location: Whales, UK
Posts: 5,676
Default

so something like this? just from touchosc - leave reaper config alone?
/fxfollows/last_touched 1/lfxpar@

just the last_touched 1 yields not much.

man i feel like a dirty noob.

thanks for assisting. its getting on my nerves now, feel close...


oh that thing? is neither huge nor controllable - 18in firewire mixer/interface -
BenK-msx is offline   Reply With Quote
Old 02-29-2012, 04:51 PM   #299
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

No; sorry if I was a little ambiguous.

(1) First you send the 1 to activate the desired mode (you have to do so only once, for each time you switch to a different mode).

(2) After that, you can send values according to the pattern(s) you have set up.

So I guess the series of messages would be something like:
Code:
/fxfollows/last_touched 1

/fxfollows/last_touched/lfxpar1 0.5
/fxfollows/last_touched/lfxpar2 0.0
/fxfollows/last_touched/lfxpar3 1.0
(etc.)

Quote:
Originally Posted by BenK-msx View Post
[...]oh that thing? is neither huge nor controllable - 18in firewire mixer/interface -
It need not be controllable to be a controller. Those sliders don't send any MIDI?
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 02-29-2012, 05:10 PM   #300
BenK-msx
Human being with feelings
 
BenK-msx's Avatar
 
Join Date: Jun 2008
Location: Whales, UK
Posts: 5,676
Default

wasn't sure if multiple msgs could be sent from one 'thing' in touch osc so i made a push button to send:

/fxfollows/last_touched 1

then a slider to send:

/fxfollows/last_touched/lfxpar1 (and tried lfxpar@)

still no joy i'm afraid.

i'll call it a day - been at it for ages, and best not waste both our time... ! thanks v much for the help though.

its weird as I have everything else working, params following focus, page, track, insert numbers, plug & track names etc. just last touched fx parameter, one of my fave reaper features is not working.


i'm not doing something right or its just not working - time will tell. pleased with my controller so far though.

and no sorry that interface is part old school analog mixer and part multi-in firewire interface. no midi. - cheers.

edit: ok after reading release notes and things i'm starting to think that
'last touched fx parameter' is not yet supported?.

seems that the last touched implementation refers to controlling the last 'plugin' you touched in reaper, with your device, not an individual parameter.


FEATURE REQUEST
to control and hear from the last touched FX parameter. PLEASE!!

Last edited by BenK-msx; 02-29-2012 at 05:38 PM.
BenK-msx is offline   Reply With Quote
Old 02-29-2012, 06:09 PM   #301
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 10,316
Default

Quote:
Originally Posted by BenK-msx View Post
edit: ok after reading release notes and things i'm starting to think that
'last touched fx parameter' is not yet supported?.

seems that the last touched implementation refers to controlling the last 'plugin' you touched in reaper, with your device, not an individual parameter.
That is correct. The control surface can have an active track and an active FX, but there's no sense of an active FX parameter.
schwa is offline   Reply With Quote
Old 02-29-2012, 06:18 PM   #302
Subz
Human being with feelings
 
Subz's Avatar
 
Join Date: Jun 2006
Location: UK
Posts: 2,963
Default

Quote:
Originally Posted by BenK-msx View Post
edit: ok after reading release notes and things i'm starting to think that
'last touched fx parameter' is not yet supported?.

seems that the last touched implementation refers to controlling the last 'plugin' you touched in reaper, with your device, not an individual parameter.


FEATURE REQUEST
to control and hear from the last touched FX parameter. PLEASE!!
the first pre that supported action binding to osc did that im sure?

not sure why they stopped supporting that data feedback (or can this be enabled in the config file?)

Subz
Subz is offline   Reply With Quote
Old 02-29-2012, 06:48 PM   #303
BenK-msx
Human being with feelings
 
BenK-msx's Avatar
 
Join Date: Jun 2008
Location: Whales, UK
Posts: 5,676
Default

Quote:
Originally Posted by schwa View Post
That is correct. The control surface can have an active track and an active FX, but there's no sense of an active FX parameter.
ah thanks schwa for this info, was going nuts there,
be nice if it did though...

reaper knows what the last touched param is, so spit that bad boy out! (he said over-simplifying)

--

joking aside, the one drawback of last touched parameter (its v useful) is/was that user has no feedback of what they are adjusting, i could be looking at track 8's fx chain, and inadvertantly adjust something on a plug on track 32, with no idea what it was or how much i adjusted it by.

OSC could rescue that by providing plug name,param name and value and it would be fab.


lots to do in many areas, so patience required.

@SUBz - not sure about that, you can bind to the action but getting feedback from it i've not heard of. seem to recall you had the idea for adjust last touched - a good one

Last edited by BenK-msx; 02-29-2012 at 06:58 PM.
BenK-msx is offline   Reply With Quote
Old 03-01-2012, 03:08 AM   #304
Sexan
Human being with feelings
 
Sexan's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 2,452
Default

One does not simply not implement track receives
Sexan is offline   Reply With Quote
Old 03-01-2012, 06:09 AM   #305
Sexan
Human being with feelings
 
Sexan's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 2,452
Default

Please! Headphone mixing needs it
Sexan is offline   Reply With Quote
Old 03-01-2012, 08:55 AM   #306
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by schwa View Post
You can do this by assigning the OSC controls to the existing actions "adjust track FX parameter 01", etc.
I just tried this, but failed. I'm using the default OSC configuration), sending messages with this pattern:
Code:
/action/950 [f] 0.5
... but no joy. I also tried if perhaps these actions requires integer values (scaled from 0-127) as arguments, since it seems to be designed as "MIDI only" feature, like this:
Code:
/action/950 [i] 63
... but that still doesn't seem to work (it would be quite confusing with action numbers being integers as well, plus being able to send multiple actions in a single message).

Am I using the wrong message pattern? (note: the [i] and [f] are from REAPER's OSC listen window, I'm not literally sending those as characters.)
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 03-01-2012, 09:05 AM   #307
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by Sexan View Post
Please! Headphone mixing needs it
I guess being able to select the tracks (e.g. by number, and get name as feedback) from which the selected track receives could become a bit messy: without some clever handling, just routing some knob to track number, and giving it a twist at full input volume is would not be something I want to hear in my headphones.

But getting names from existing receives, and being able to adjust their levels and pan would be much simpler, very much like we already have currently for sends. I think we should just start there, and see about the rest a bit later. I definitely see how it would be very useful to set up sub mixes remotely, but it just seems a bit more complicated, like many other things that would be interesting to add.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ

Last edited by Banned; 03-01-2012 at 05:09 PM. Reason: removed excess "a"
Banned is offline   Reply With Quote
Old 03-01-2012, 09:29 AM   #308
Sexan
Human being with feelings
 
Sexan's Avatar
 
Join Date: Jun 2009
Location: Croatia
Posts: 2,452
Default

Quote:
Originally Posted by Banned View Post
and being able to adjust their levels and pan would be much simpler, very much like we already have currently for sends.
This is what I want
Sexan is offline   Reply With Quote
Old 03-01-2012, 09:37 AM   #309
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

I think the directionality of the current OSC configuration is still unclear in many cases, and should be improved by using less ambiguous names and clearer concepts.

For one important example, the concept of
Code:
TRACK_FOLLOWS DEVICE, LAST_TOUCHED
currently works the wrong way around, and should rather be named something like
Code:
DEVICE_TRACK_SELECTION_FOLLOWS SELF, LAST_TOUCHED_IN_REAPER
Of course we still need something like
Code:
TRACK_FOLLOWS
However, I think a better name would be
Code:
REAPER_TRACK_SELECTION_FOLLOWS
and the allowed arguments should somehow refer to the specific control surface, e.g. using its "Device name". What control surface(s) REAPER's track selection should follow should be a setting specific to REAPER, not to a particular (OSC) control surface.

I haven't even tested this yet (and I probably will ), but since multiple (OSC) control surfaces are allowed, each with its separate state, and thus selected track, I can think of many nightmare scenario's with the current configuration.

Control surface device names could also be used as arguments in messages to set other control surface devices' states, so that e.g. device 1 may follow the selection made by device 2 as well.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 03-01-2012, 10:06 AM   #310
Subz
Human being with feelings
 
Subz's Avatar
 
Join Date: Jun 2006
Location: UK
Posts: 2,963
Default

any plans to support rotary controls as relative controllers in 3.16?

Subz
Subz is offline   Reply With Quote
Old 03-01-2012, 11:07 AM   #311
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by Subz View Post
any plans to support rotary controls as relative controllers in 3.16?
OSC messages should not care if the controllers used are rotaries. Do you have a controller with rotaries that sends OSC messages, and if so, what is its syntax for relative mode (if you can not arbitrarily change it)?

If those controls are just sending plain MIDI, we already can achieve this by means of bridging MIDI (incl. relative control modes using MIDI) to OSC outside of REAPER. The 'bridge' part is informed about the absolute values of parameters in REAPER, since REAPER sends them as feedback, and those parameters can then be manipulated by the MIDI controller sending relative control values to the bridge. I.e. the bridge can do the absolute OSC <--> relative MIDI conversion.

And as far as OSC clients go (as opposed to 'dumb' MIDI controllers), they should probably be smart enough to do the same thing.

Not saying I don't want relative control support for OSC too, I still do.

It also occurred to me the other day that when the FR of being able to poll current values would be implemented, one could use that to implement relative control in even more flexible ways (since that removes the dependency on REAPER sending feedback). If I want to add x to an unknown parameter value y, and can e.g. send "?" to get the current value back, it's easy enough to do x + y myself (or have an app do it for me, of course). In other words, the FR for relative control and the FR for polling current values could in fact be considered as one.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 03-01-2012, 11:40 AM   #312
Subz
Human being with feelings
 
Subz's Avatar
 
Join Date: Jun 2006
Location: UK
Posts: 2,963
Default

Quote:
Originally Posted by Banned View Post
OSC messages should not care if the controllers used are rotaries. Do you have a controller with rotaries that sends OSC messages, and if so, what is its syntax for relative mode (if you can not arbitrarily change it)?

If those controls are just sending plain MIDI, we already can achieve this by means of bridging MIDI (incl. relative control modes using MIDI) to OSC outside of REAPER. The 'bridge' part is informed about the absolute values of parameters in REAPER, since REAPER sends them as feedback, and those parameters can then be manipulated by the MIDI controller sending relative control values to the bridge. I.e. the bridge can do the absolute OSC <--> relative MIDI conversion.

And as far as OSC clients go (as opposed to 'dumb' MIDI controllers), they should probably be smart enough to do the same thing.

Not saying I don't want relative control support for OSC too, I still do.

It also occurred to me the other day that when the FR of being able to poll current values would be implemented, one could use that to implement relative control in even more flexible ways (since that removes the dependency on REAPER sending feedback). If I want to add x to an unknown parameter value y, and can e.g. send "?" to get the current value back, it's easy enough to do x + y myself (or have an app do it for me, of course). In other words, the FR for relative control and the FR for polling current values could in fact be considered as one.

i wont pretend i fully understand OSC

but the 'Rotery' control in TouchOSC just sent 1 or 0 depending witch way you turn it, (i think) in Reaper this will make whatever its mapped to go from Max to Min only

this of course could all come down to user ignorance though!

my intention is just to make the endless rotery control in my OSC controller to go up or down from where it is, or map it to jog/scrub wheel (i have not tested weather this currently works as of yet though so jog may work as is)

Subz
Subz is offline   Reply With Quote
Old 03-01-2012, 12:34 PM   #313
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by Subz View Post
[...] but the 'Rotery' control in TouchOSC
It's good to be that specific.
Quote:
Originally Posted by Subz View Post
just sent 1 or 0 depending witch way you turn it, (i think) in Reaper this will make whatever its mapped to go from Max to Min only
That makes sense, as it is similar to one common method for using relative control with MIDI.

However, we don't have to follow or copy any existing standard (whatever MIDI, TouchOSC, or anything else is doing), especially if we can think of a better one.

As long as were using a single OSC address for any particular parameter, and we are already using values ranging from 0.0 to 1.0, imho it would be too confusing to use integer 0 / 1 numbers for relative control, while using float numbers (including 0.0 and 1.0) for 'absolute' control (they look too similar in human readable form, especially when the .0 gets truncated).

Another option would of course be to add a dedicated address. But I think that does not make much sense. We would be doing so mainly to accommodate the legacy convention of sending 1's and 0's, that originated from an ancient namespace (MIDI CC#) where it simply was 'impossible' to have a negative value at all. Hence, "0" occasionally got to be misused to mean "-1". I don't see a good reason to stick to that convention with OSC, where we are free to just say "-1" if that's what we really mean to say.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 03-01-2012, 12:55 PM   #314
Subz
Human being with feelings
 
Subz's Avatar
 
Join Date: Jun 2006
Location: UK
Posts: 2,963
Default

as long as it for-fills my intentions

"my intention is just to make the endless rotery control in my OSC controller to go up or down from where it is, or map it to jog/scrub wheel"

it can be called or follow whatever keeps all happy

on that note i have had fun naming OSC control's whatever i want (well as long as it starts with a "/" )


Subz
Subz is offline   Reply With Quote
Old 03-01-2012, 01:07 PM   #315
BenK-msx
Human being with feelings
 
BenK-msx's Avatar
 
Join Date: Jun 2008
Location: Whales, UK
Posts: 5,676
Default

ok last touch param is all good now! - yay,
just waiting on that param name bug fix..

got vumeters working following selected track using /track/vu which i swear didn't work before but is now.. ! hohum

Last edited by BenK-msx; 03-01-2012 at 01:40 PM.
BenK-msx is offline   Reply With Quote
Old 03-01-2012, 02:16 PM   #316
BenK-msx
Human being with feelings
 
BenK-msx's Avatar
 
Join Date: Jun 2008
Location: Whales, UK
Posts: 5,676
Default

just a little tip for the vumeters in touchosc

i've found if you create a (red) LED
and set the value range to ~ .882 to .94

edit: my meters on the this testing laptop with reaper are set to have max +24 range (not that i mix like that!) , which may be a factor in getting the right values.


iv got a nice 0db clip indicator that just starts to fade in above 0db and quickly goes to bright red at +3,4
can adjust to taste.

nice!
BenK-msx is offline   Reply With Quote
Old 03-01-2012, 02:56 PM   #317
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 10,316
Default

Quote:
Originally Posted by Banned View Post
I just tried this, but failed. I'm using the default OSC configuration), sending messages with this pattern:
Code:
/action/950 [f] 0.5
At the moment, actions marked "midi cc/OSC" can't be triggered using the /action/@ method. They can only be triggered by binding an OSC message to the action the normal way (the same way you would bind a MIDI or keyboard shortcut).
schwa is offline   Reply With Quote
Old 03-01-2012, 03:09 PM   #318
schwa
Administrator
 
schwa's Avatar
 
Join Date: Mar 2007
Location: NY
Posts: 10,316
Default

Quote:
Originally Posted by Banned View Post
It also occurred to me the other day that when the FR of being able to poll current values would be implemented
BTW there is an existing protocol for this (though REAPER doesn't support it yet).

http://opensoundcontrol.org/files/osc-query-system.pdf ("current value" being the most interesting part).
schwa is offline   Reply With Quote
Old 03-01-2012, 04:19 PM   #319
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by schwa View Post
At the moment, actions marked "midi cc/OSC" can't be triggered using the /action/@ method. They can only be triggered by binding an OSC message to the action the normal way (the same way you would bind a MIDI or keyboard shortcut).
I also tried using the Learn dialog and actions list, but still didn't see how to send values to the action.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned is offline   Reply With Quote
Old 03-01-2012, 04:22 PM   #320
Banned
Human being with feelings
 
Banned's Avatar
 
Join Date: Mar 2008
Location: Unwired (probably in the proximity of Amsterdam)
Posts: 4,868
Default

Quote:
Originally Posted by schwa View Post
BTW there is an existing protocol for this (though REAPER doesn't support it yet).

http://opensoundcontrol.org/files/osc-query-system.pdf ("current value" being the most interesting part).
Yes, that is exactly the sort of thing I had in mind.
__________________
˙lɐd 'ʎɐʍ ƃuoɹʍ ǝɥʇ ǝɔıʌǝp ʇɐɥʇ ƃuıploɥ ǝɹ,noʎ
Banned 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 02:09 AM.


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