Announcement

Collapse
No announcement yet.

Simple OSC Output/Input Examples (4.23.1)

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    Simple OSC Output/Input Examples (4.23.1)

    For anyone interested here are four simple OSC output patches using the new 4.23.1 beta OSC Blueprints.

    Sending simple OSC messages: https://ccrma.stanford.edu/~rob/ue4/ue4_4.23.1.OSC.png

    Receiving simple OSC messages: https://ccrma.stanford.edu/~rob/ue4/...SC_receive.png

    Sending bundles of messages: https://ccrma.stanford.edu/~rob/ue4/...OSC_bundle.png

    Parsing out 2 different namespaces for incoming messages: https://ccrma.stanford.edu/~rob/ue4/...namespaces.png

    Note: In the receiving example, OSC is being sent from another computer, hence the "AddWhitelistedClient" node. That IP could also have been added in the CreateOSCServer node. Also, these are just trial/error working versions so far, not sure if they're ideal examples.


    p.s Thanks Aaron, Ethan, Arthur and team! Built-in OSC!!
    Last edited by robhamilton; 11-10-2019, 06:03 PM.

    #2
    Thanks guys!

    Comment


      #3
      Hi Rob, I'm trying to re-create your Receiving example, but I'm new to blueprints and having some problems understanding:

      - what is the variable type used for your Received OSCMessage variable and your My OSC Server variable?
      - I see that with the OSC plugin there a few new OSC variable types available, I assume [ Recieved OSCMessage ] uses this but not sure about the OSC server, OSCAddress?

      - what is connecting to and triggering the [ Custom Event OSCMessageReceived ] node?

      - I never tried to make a custom event before, I was able to sort of recreate yours but I don't know how yours has a message variable input, mine just has target, is yours a specific OSC event dispatcher type?

      Click image for larger version

Name:	OSC_Help.png
Views:	154
Size:	79.3 KB
ID:	1696750

      Comment


        #4


        1. Right Click and Create Custom Event - give it a name (eg OSCMessage_Event)

        2. Drag the Red output from the OSCMessage_Event object onto the Red Event input on the Bind Event object

        3. Right click on the OSCMessage_Event object and Refresh Nodes

        4. A Blue message output should appear on the OSCMessage_Event object

        5. Right click on the Blue output on the OSCMessage_Event object and choose 'promote to variable' - this creates a SET new variable (of type OSC Message)

        6. You can then re-name this new variable to something (eg Received OSCMessage)

        Comment

        Working...
        X