Skip to content


Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?

Latest commit


Git stats


Failed to load latest commit information.
Latest commit message
Commit time


OSC plugin for Unreal Engine 4 and Unreal Engine 5 to send and receive OSC messages with blueprints!

It uses oscpack, a C++ library for packing/unpacking OSC messages, by Ross Bencina. It also uses OscPkt, a very minimalistic OSC library, by Julien Pommier.

Migrating from UE4-OSC to UE-OSC

This plugin has been working for Unreal since 2014 (UE4.4!) and it continues today with UE5!

I decided to change its name from UE4-OSC to a more generic UE-OSC.

To migrate an existing project using UE4-OSC to UE-OSC, add the following in the Config/DefaultEngine.ini file.

+PackageRedirects=(OldName="/Script/UE4_OSC", NewName="/Script/UE_OSC")


Dannington made a super tutorial!

Watch it to properly install the plugin and get some brilliant ideas on how to use it!

Also, go to the UE forum dedicated thread:


Install Visual Studio 2019 on Windows (Community edition works) or XCode on MaxOSX.

Create a "C++" project, or convert a "Blueprint" project to "C++".

Create a "Plugins" directory in the project root (near the "Content" directory) and put the "OSC" folder of the plugin in it. (e.g. "/MyProject/Plugins/OSC")

Run the "*.uproject" file: the plugin is compiled automatically.

Alternatively, right-clic the "*.uproject" to generate Visual Studio or XCode project files.



Set the listening port as "Receive From" in the plugin settings. (Edit/Project Settings/Plugins/OSC)

Add a OscReceiverComponent to your Blueprint class and bind the OnOscReceived custom event, or subclass the OscReceiverActor and bind the OnOscReceived custom event.

The OnOscReceived event gives: the OSC address, the OSC parameters and the IP of the sender.

The OSC parameters is an array of OSC elements. To read the content, either:

  • chain PopFloat/Int/Bool/String/Blob functions to get the first value, or
  • use the standard GET function and AsFloat/Int/Bool/String/Blob functions to cast the element to its value. This is slightly more efficient.


OscReceiverComponent has an AddressFilter parameter. If not empty, OnOscReceived is called if and only if the address pattern of the incoming message matches the AddressFilter.

Standard OSC pattern matching is supported against AddressFilter.

Pattern matching is case insensitive.

When using AddressFilter, the address given in the OnOscReceived event is not the address of the incoming message, but what is left after the address filter.


  • AddressFilter=/Foo + OSC message address pattern=/Foo => OnOscReceived event with Address=None
  • AddressFilter=/Foo + OSC message address pattern=/Foo/Bar => OnOscReceived event with Address=/Bar
  • AddressFilter=/Foo + OSC message address pattern=/*/Bar => OnOscReceived event with Address=/Bar

Alternative pattern matching

If AddressFilter does not work for you, the function MatchOscAddressPattern() provides a similar feature you can use in C++ or Blueprint.

Pattern matching is case insensitive.


Set the "Send Targets" addresses in the plugin settings. (Edit/Project Settings/Plugins/OSC)

You can also add new targets dynamically, using the "Add Send Osc Target" function. It is especially useful for "ping"-like behavior.

Send a single message with "Send Osc" or a bundle of messages with "Send Osc Bundle".

The "Send Osc" function takes: the OSC address, the OSC parameters and the "target index" of the destination.

Build the OSC parameters for a message:

  • chain PushFloat/Int/Bool/String/Blob functions, or
  • fill an array of "Osc Data Elem" with the standard array functions and the FromFloat/Int/Bool/String/Blob functions.

The "target index" refers to an index in the "Send Targets" array in the settings, or to the result of the "Add Send Osc Target" function.

Inputs (experimental)

List the messages that should be UE inputs (like a game controller). A new input is created for each message.

Bind OSC inputs to UE action in the usual "Input" project settings.

General information


The plugin uses the standard UE logging system.

Check your logs (Window/Developers Tools/Output Log) before asking for help!

String limitation

Historically, the plugin handles OSC string using "FName". Unfortunately, the length of a "FName" is limited to 1024 characters. So this plugin does not handle long strings correctly.

If you need long strings, prefer using blobs.


The OSC protocol supports buffers as "blob".

This plugin implements them as "Array". It plays nicely with the "Extended Standard Library" plugin by "Low Entry".

Engine version

Get the right branch for your engine version: "master" for the latest version, "before4.8" for 4.4, ..., 4.7, etc.

If the plugin does not work/build for the current version, feel free to create an issue or email me!


OSC plugin for Unreal Engine 4 Blueprints







No releases published


No packages published

Contributors 4