[RWP] What is OSC?

[Scott Chesworth]

Well most protocols boil down to configs written in text if you dig
deep enough don't they, but yeah it's handy that they haven't tried to
restrict access to that text in a desktop environment. In iOS, by
default at least, apps are so sandboxed that it'll probably count for
less. From my initial digging about in a few apps, the actual
configuration side of things seemed pretty accessible, it was when it
came down to dynamic content being fed back from the DAW to the app
that VoiceOver started dropping the ball. If you want to be able to
shove a handwritten config file directly into an app then Android is
probably the mobile environment better suited to the task, although
I've no idea whether an OSC client exists yet or if it'd be accessible
with Talkback. Seems like it's kinda early days on this stuff even for
the dudes who aren't throwing assistive tech into the mix. Still,
worth exploring if you've got the time!

Scott

On 6/4/13, Indigo <33indigo at charter.net> wrote:
> OSC seems to be accessible, in the sense that it's written in text; and
> the configuration file sort of explains what to do to fill it out; but
> it's another programming language, with fill in the blanks template.
> I just have all I can handle at the moment myself.
> Probably other people have already made OSC files to run an iPad with
> whatever other gear they have.
> They even made a rubberized tray on the top of my Casio XW-G1; plus a
> 3.5mm audio input just meant for an iPad to sit there and do its thing.
> If I had an iPad I'd google for an OSC file to control the iPad from the
> XW-G1; maybe via USB.
> Isn't it great how everything is trying to be 1 big happy family of
> gizmos; all talking to each other?
> Indi
>
>
>
> On 6/3/2013 2:04 PM, Scott Chesworth wrote:
>> I can think of plenty of reasons why you'd want to. Haven't found an
>> accessible app to do the job yet though.
>>
>> Anyone else had more luck?
>>
>> Scott
>>
>> On 6/3/13, Indigo <33indigo at charter.net> wrote:
>>> By the way, one can use the touch gestures from an iPad to control
>>> Reaper through OSC.
>>> I don't know why anyone would want to, but it's possible, irf you want
>>> to look cool, I guess.
>>> I don't know how much work it would be, but practically any device or
>>> program can be linked to control Reaper with OSC.
>>> Snip from reaper.fm; the link is at the bottom:
>>> OSC is a protocol for sending information between musical devices, over
>>> a network. Unlike MIDI, which is defined as a stream of bytes with
>>> specific meanings, OSC messages are human-readable text strings with no
>>> predefined meanings. It is entirely up to individual musical devices to
>>> define what specific messages mean and when those messages are sent.
>>> For two devices to work together (such as REAPER an and OSC control
>>> surface device), the user must configure one or both devices to send and
>>> receive messages that have meaning for the other device.
>>> For basic information about OSC, see the Open Sound Control web site.
>>> top  Requirements
>>> OSC-capable components include hardware control surfaces, standalone
>>> computer applications, apps for tablets and smartphones, and so on. In
>>> addition, there are middleware applications that can convert between OSC
>>> and MIDI, so that OSC can be used for 2-way communication with any
>>> MIDI-capable component, including almost any hardware control surface.
>>>
>>> To enable network communication between REAPER and an OSC device, go to
>>> Options/Preferences/Control Surfaces, and add a new OSC control surface.
>>> REAPER can receive messages from the device, send messages to the
>>> device, or both.
>>>
>>> To use an OSC device for basic one-way control input, enable "allow
>>> binding messages to REAPER actions and FX learn". This will permit OSC
>>> messages from this device to be used as action shortcuts and FX
>>> parameter learn mappings, just like any keyboard or MIDI control input.
>>>
>>> top  Pattern Config Files
>>>
>>> To use an OSC device for more than basic action shortcuts and FX
>>> parameter learn, you will need to configure either REAPER or the device
>>> to define the OSC messages that will be used for communication.
>>> The pattern config file (.ReaperOSC) is how REAPER defines the OSC
>>> messages it understands. In order to use REAPER with any OSC device, you
>>> can either create a custom pattern config file so that REAPER sends and
>>> receives messages the OSC device understands, or configure the OSC
>>> device to send and receive messages that REAPER understands, or both.
>>> To open the default pattern config file folder, select "open config
>>> directory" under "pattern config" in the OSC control surface settings
>>> dialog. The best way to create a new pattern config is to make a copy of
>>> the included Default.ReaperOSC file, rename the copy, and change the
>>> patterns defined in the file. Please see the extensive comments in
>>> Default.ReaperOSC for more detail about how messages are formed, and
>>> what the messages mean.
>>>
>>> top  Further exploration
>>> For more help on OSC in REAPER, to report bugs, to request additional
>>> functionality, to share pattern config files, or just to discuss the
>>> possibilities, please use the REAPER User Forum.
>>> osc
>>> end snip.
>>> http://www.reaper.fm/sdk/osc/osc.php
>>>
>>> _______________________________________________
>>> RWP mailing list
>>> RWP at reaaccess.com
>>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>>
>>
>> _______________________________________________
>> RWP mailing list
>> RWP at reaaccess.com
>> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>>
>
> _______________________________________________
> RWP mailing list
> RWP at reaaccess.com
> http://reaaccess.com/mailman/listinfo/rwp_reaaccess.com
>