Old 04-28-2018, 12:44 PM   #1
deailes
Human being with feelings
 
Join Date: May 2010
Posts: 90
Default Action: Adjust track FX parameter 1-16 OSC

Hiya guys

For the life of me i cannot figure out how to modify the OSC config pattern file to control the 16 actions for Adjust track FX parameter.

On reviewing i thought i would have to possibly add these as specific actions referencing the command_id but i cannot get that to work in Hexlar Touchosc at all.

To be fair,well likely, i maybe not have set it up correctly!

Would anyone know how i would go about editing this.

I had set up an action like:

ACTION i/action t/action/@ -- on the pattern config file

Then on page 2 of ipad template I have set up a fader with an adddress of:

/2/action/950

or

/2/950


Should this work in the way i think it should. Am i missing something quite simple. IE how to i correctly send the CommandID from the Ipad?

Cheers

Last edited by deailes; 04-28-2018 at 01:37 PM.
deailes is offline   Reply With Quote
Old 04-28-2018, 01:50 PM   #2
azslow3
Human being with feelings
 
Join Date: Nov 2017
Location: Heidelberg, Germany
Posts: 797
Default

I guess a good way to control currently focused FX parameters is (assuming you start from the default pattern):
* in the pattern file, change DEVICE_FX_FOLLOWS from "DEVICE" to "LAST_TOUCHED"
* from OSC client, send /fxparam/X/value (X = 1..16), with float parameter in range 0. to 1.
(default FX_PARAM_VALUE rule will make it work).
I think that is also the only way to get the "feedback", so allow your control in OSC client to follow actual value.

Theoretically, it should be possible to send /action/950/cc with parameter 1. to 127.
Or "allow binding messages" for OSC, and "learn" OSC as a MIDI binding.
But I have not tested that...
azslow3 is offline   Reply With Quote
Old 06-18-2018, 04:38 AM   #3
Stroudy
Human being with feelings
 
Stroudy's Avatar
 
Join Date: Jul 2014
Location: London
Posts: 733
Default

I'm just getting my head into OSC messages...

Can you control the FX Parameters 1-16 with OSC? And, crucially have feedback?

How would this look in the OSC message and in the .ReaperOSC file?
Stroudy is offline   Reply With Quote
Old 06-18-2018, 01:52 PM   #4
azslow3
Human being with feelings
 
Join Date: Nov 2017
Location: Heidelberg, Germany
Posts: 797
Default

(for example)
Code:
DEVICE_FX_PARAM_COUNT 16
DEVICE_FX_FOLLOWS LAST_TOUCHED
...
(already in default configuration)
FX_PARAM_VALUE n/fxparam/@/value n/fx/@/fxparam/@/value n/track/@/fx/@/fxparam/@/value
So, you send "/fxparam/1/value" and get it as feedback (default configuration will also send string to display and the name of that parameter)

Note that in the default config you can also set first 2 values from the device (so as initialization). In that case you do not need to create own pattern at all...
azslow3 is offline   Reply With Quote
Old 06-26-2018, 03:21 AM   #5
Stroudy
Human being with feelings
 
Stroudy's Avatar
 
Join Date: Jul 2014
Location: London
Posts: 733
Default

I just don’t understand the syntax. I'm trying to figure this out.

Documentation is so poor. I cannot find how this all works.

I assume n/ means number and s/ means string.



I'm using Lemur and I thought 'value' would be replaced with, in this case, 'x', which would be 0.00 - 1.00

I seriously don't understand how it all goes together. Do I replace the @? the 'n', the 's'?

Code:
FX_PARAM_VALUE n/fxparam/@/value n/fx/@/fxparam/@/value n/track/@/fx/@/fxparam/@/value
Why are there all these patterns? What do they do?

Sorry, going crazy
Stroudy is offline   Reply With Quote
Old 06-26-2018, 04:48 AM   #6
Stroudy
Human being with feelings
 
Stroudy's Avatar
 
Join Date: Jul 2014
Location: London
Posts: 733
Default

I also think we might not be talking about the same thing, so I just wanna check...

I would be the same thing as these actions


That gets used here, on the Track Controls:

Stroudy is offline   Reply With Quote
Old 06-26-2018, 01:15 PM   #7
azslow3
Human being with feelings
 
Join Date: Nov 2017
Location: Heidelberg, Germany
Posts: 797
Default

Quote:
Originally Posted by Stroudy View Post
I also think we might not be talking about the same thing, so I just wanna check...
Well, you are right. I do not think that is exposed to API/OSC.

But the format of OSC pattern is rather detailed described in the default file, with "n"/"f"/"s" meaning. The interpretation of "@" depends from particular quantity in question, more precisely the number of numerical parameters it accept. F.e. FX parameter has general form "Track X, FX Y, Parameter Z". So, if there are 3 "@" in the pattern, they are interpreted as X, Y and Z. If there are 2, "X" is assumed to be "current track" (the meaning is configurable). The same with just one "@", means "current Track", "current FX", specified on "@" place parameter.
The value is never the part of OSC identifier, so it is referenced by type (n,f,s,etc.) only. Text used, so everything except the type prefix and @, has no special meaning and just has to be in form acceptable as OSC identifier.
azslow3 is offline   Reply With Quote
Old 06-27-2018, 02:26 AM   #8
Stroudy
Human being with feelings
 
Stroudy's Avatar
 
Join Date: Jul 2014
Location: London
Posts: 733
Default

azslow3, thanks for the details!

I think I'll have to try and find a way to use midi to communicate the Track Controls in the action list.

AFAIK there's no way to send incremental or decremental values over OSC, right? So instead of say..


0.00...0.01...0.02...0.03

this...

+0.01...+0.01...+0.01...

I'll try and get Lemur to spit out something Reaper can use its 'Relative Values' inside the action list.
Stroudy is offline   Reply With Quote
Old 06-27-2018, 04:07 AM   #9
azslow3
Human being with feelings
 
Join Date: Nov 2017
Location: Heidelberg, Germany
Posts: 797
Default

I must admit I had now luck with ACTION_RELATIVE patterns
(/action/<ID>/cc/relative in the default configuration).
azslow3 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 08:19 PM.


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