View Single Post
Old 08-29-2019, 05:01 PM   #4367
Freex
Human being with feelings
 
Freex's Avatar
 
Join Date: Jul 2011
Location: Northern Ireland
Posts: 585
Default

Quote:
Originally Posted by Geoff Waddington View Post
WOW, you got there quickly !

In order for Reaper to cause the OSC surface to go to the right page, it must be named explicitly and EXACTLY -- it's the equivalent of the FX name in the .zon file -- it must be exact.

So, since spaces are disallowed, you end up with the same as the filename, a pretty ugly thing.

Now, think url.

You will see things like

Code:
Widget Home/ShowFXWindows
	Control /Home/ShowFXWindows
	FB_Processor /Home/ShowFXWindows
WidgetEnd

Widget VST__UAD_Ampeg_SVTVR_Classic__Universal_Audio__Inc__/Input
	Control /VST__UAD_Ampeg_SVTVR_Classic__Universal_Audio__Inc__/Input
	FB_Processor /VST__UAD_Ampeg_SVTVR_Classic__Universal_Audio__Inc__/Input
WidgetEnd

Zone Home
	OnTrackSelection MapSelectedTrackFXToWidgets
	Home/ShowFXWindows SetShowFXWindows
ZoneEnd

Zone "VST: UAD Lexicon 224 (Universal Audio, Inc.)"
	SelectedTrackNavigator
	VST__UAD_Lexicon_224__Universal_Audio__Inc__/Program FXParam 0
	VST__UAD_Lexicon_224__Universal_Audio__Inc__/Bass FXParam 1
	VST__UAD_Lexicon_224__Universal_Audio__Inc__/Mid FXParam 2
	VST__UAD_Lexicon_224__Universal_Audio__Inc__/Crossover FXParam 3
	VST__UAD_Lexicon_224__Universal_Audio__Inc__/Treble_Decay FXParam 4
	VST__UAD_Lexicon_224__Universal_Audio__Inc__/Depth FXParam 5
	Toggle+VST__UAD_Lexicon_224__Universal_Audio__Inc__/Rear_Outs FXParam 10
	Toggle+VST__UAD_Lexicon_224__Universal_Audio__Inc__/Mode_Enh FXParam 13
	Toggle+VST__UAD_Lexicon_224__Universal_Audio__Inc__/Decay_Opt FXParam 16
	Toggle+VST__UAD_Lexicon_224__Universal_Audio__Inc__/Wet_Solo FXParam 12
ZoneEnd
Looks a bit intimidating, but if you treat the part before the slash as a url, most of which you ignore, you see the actual familiar structure -- Program FXParam 0, etc.

OK, now use the editor to load the .touchosc layouts in CSI/Touch OSC Layouts

Now take a look at CSI/Surfaces/OSC/TouchOSC.ost

See how the names cross-reference.

OK last part, take a look at CSI/Zones/TouchOSCPad.zon and CSI/Zones/TouchOSCPhone.zon, see how this works ?

It's really the same as Midi, just a little bent -- you end up with a larger .ost file as compared to Midi, and you also need to make pages for the OSC device.


Yours will look a lot simpler for the C4 screen

Code:
Widget Home/RotaryD1
	Control /Home/RotaryD1
	FB_Processor /Home/RotaryD1
WidgetEnd

Zone Home
	Home/RotaryD1 someAction
ZoneEnd
Let me know how it goes.
I sure that all makes sense, but I'm lost....

I started to reverse engineer to try and understand whats going on,

but did you say the FXzone files will need to be different for OSC and MIDI
Freex is offline   Reply With Quote