extOSC is outdated. Over the past few years, I’ve been too occupied to dedicate time to extOSC. I couldn’t respond to bug reports or help users with solutions. This year, I finally have the opportunity to return to extOSC, but looking at its code, I don’t feel motivated to patch it up.
I started working on extOSC in 2016, back when I was just beginning to learn network programming. Since then, I’ve gained a lot of experience. Now, looking at extOSC’s code, I realize I want to rewrite it entirely — I can’t abandon its development, as many people have used it over the years, and I still receive messages about it.
That’s why I’m announcing work on extOSC 2:
- Remove the separation between OSC Receiver and OSC Transmitter, creating a unified interface.
- Decouple OSC from Unity, while retaining Unity components for integration.
- Drop official support for WSA (Windows Store Apps), but provide ways to add it painlessly for those who need it.
- Fix issues you’ve reported over the years (thank you for your patience!).
If there’s anything you’d like to see in the new version, please share your ideas here.
extOSC is outdated. Over the past few years, I’ve been too occupied to dedicate time to extOSC. I couldn’t respond to bug reports or help users with solutions. This year, I finally have the opportunity to return to extOSC, but looking at its code, I don’t feel motivated to patch it up.
I started working on extOSC in 2016, back when I was just beginning to learn network programming. Since then, I’ve gained a lot of experience. Now, looking at extOSC’s code, I realize I want to rewrite it entirely — I can’t abandon its development, as many people have used it over the years, and I still receive messages about it.
That’s why I’m announcing work on extOSC 2:
If there’s anything you’d like to see in the new version, please share your ideas here.