# Working with OSC as variables

**URL:** <https://in-thread.sonic-pi.net/t/working-with-osc-as-variables/2840>\
**Category:** Support, Help & Resources\
**Created:** [October 24, 2019, 10:56am UTC](https://in-thread.sonic-pi.net/t/working-with-osc-as-variables/2840 "2019-10-24T10:56:37Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![robin.newman](https://avatars.discourse-cdn.com/v4/letter/r/76d3ee/32.png) [@robin.newman](https://in-thread.sonic-pi.net/u/robin.newman)\
**Post date:** [November 6, 2019, 1:45pm UTC](https://in-thread.sonic-pi.net/t/working-with-osc-as-variables/2840/16 "2019-11-06T13:45:46Z")

</div>

Are OSC messages working locally? Try the other [example I posted for you](http://in-thread.sonic-pi.net/t/test-osc-control-program-for-sonic-pi/2864/3)  
Have a look at the log files, particularly erlang.log You could build 3.2dev but you need to be aware of the changes I have pointed out (using sync “/osc\*/…” instead of sync “/osc/…” and using port 4560 instead of 4559.

---

_[View the full topic](https://in-thread.sonic-pi.net/t/working-with-osc-as-variables/2840)._