OSC Receiver and Sender
Re: OSC Receiver
actually i say keep it, might serve a function for the future!
btw i have the perfect device to try this on in a real world situation... but it is part of a commercial pack, do you allow me to try? of course i will send it to you for free
btw i have the perfect device to try this on in a real world situation... but it is part of a commercial pack, do you allow me to try? of course i will send it to you for free
Scope, Android, Web, PC Plugins and Sounds:
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
Re: OSC Receiver
maybe keep it as a pad, but have it initialize to 8000w_ellis wrote: ↑Thu Dec 21, 2017 7:37 am Any thoughts on my earlier question about where to store the OSC port number? I could easily create a dedicated preferences file for it, which might be safest. I think it's misleading to have it as an input to the module, as it can only be one value across all devices.
Scope, Android, Web, PC Plugins and Sounds:
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
Re: OSC Receiver
will if we are keeping port as a parameter couldn't we just have each useage of it provide a port entry option for the user? so each device that embeds this will have to pull a text fader to the panel where the user sets the ports, and that's it no? takes care of multiple instances and everything i think.
Scope, Android, Web, PC Plugins and Sounds:
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
Re: OSC Receiver
aaaaaaaaaaaaaah lol sorry im getting too excited - port won't do on the broadcasting side, since it will be broadcasting on 1 port nevermind, just curious. so yes i get the reasons behind the setup now, i'm in if you go for what you described
Scope, Android, Web, PC Plugins and Sounds:
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
Re: OSC Receiver
Try this new version out: Scope DLL
The main reasons not to allow individual ports per device/instance:
- Will create firewall pain every time a new port is used. At the moment users will need to enable the relevant port once ever.
- It's inefficient in the module to have multiple instances of the OSC Receiver object, as the architecture neatly supports multiple listeners on the same port. It would drive up memory usage to have one per device/instance
See how you get on with patching this version. I think it's pretty easy to use.
The main reasons not to allow individual ports per device/instance:
- Will create firewall pain every time a new port is used. At the moment users will need to enable the relevant port once ever.
- It's inefficient in the module to have multiple instances of the OSC Receiver object, as the architecture neatly supports multiple listeners on the same port. It would drive up memory usage to have one per device/instance
See how you get on with patching this version. I think it's pretty easy to use.
Re: OSC Receiver
As an example, I passed 1, 10001 and 1 into the 3 inputs and was able to control values by passing messages with addresses /1/10001/1/x
Re: OSC Receiver
We can agree that Ocean Swift gets the Device UID range from 10000 to 19999 as an early adopter benefit (when you've build more than 10,000 devices we'll give you a new range!)
Re: OSC Receiver
Oh, and of course I'm happy for you to try this out in one of your devices. We'll need to do some digging about licensing, but I'm sure there's ways to sort it out.
Re: OSC Receiver
awesome give me 10 minutes ill post here my test tool and a conversion module for scope that takes the integers and converts them to int32 (what scope knobs usually like)
Scope, Android, Web, PC Plugins and Sounds:
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
Re: OSC Receiver
I've just finished the first version of the Sender, which you can find here: Scope DLL
Seems to work inside the SDK. Will be interested if anyone gets time to point the sender outside, especially to a different PC. Note that you can set a different Port + Host per instance of the sender, as there's no problem with having many instances of that (compared to listen ports for receiving).
Here's an animated gif showing it in action!
Let me know if it's not clear what all the parameters mean. I'll probably not be able to do much coding until early Jan, when I get back from Munich.
Seems to work inside the SDK. Will be interested if anyone gets time to point the sender outside, especially to a different PC. Note that you can set a different Port + Host per instance of the sender, as there's no problem with having many instances of that (compared to listen ports for receiving).
Here's an animated gif showing it in action!
Let me know if it's not clear what all the parameters mean. I'll probably not be able to do much coding until early Jan, when I get back from Munich.
Re: OSC Receiver and Sender
P.S. I spoke with Faxi over WhatsApp and clarified that you can pass full int32 values over the OSC messages, so no need to scale them. I think that's the best use of the protocol and then scale for display at either end.
Re: OSC Receiver and Sender
--
- Attachments
-
- oscosv2.png (9.06 KiB) Viewed 318727 times
Last edited by faxinadu on Sun Jan 07, 2018 11:28 am, edited 1 time in total.
Scope, Android, Web, PC Plugins and Sounds:
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
Re: OSC Receiver
.I'd put the relevant data in an ini-file (own or cset). And don't forget to do initiate another module as receiver, if the 1st one is deleted.w_ellis wrote: ↑Thu Dec 21, 2017 7:37 am Any thoughts on my earlier question about where to store the OSC port number? I could easily create a dedicated preferences file for it, which might be safest. I think it's misleading to have it as an input to the module, as it can only be one value across all devices.
Re: OSC Receiver and Sender
for the sender can there be a generic version with no ids? so with scope one could control anything that accepts osc.
Scope, Android, Web, PC Plugins and Sounds:
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
Re: OSC Receiver and Sender
confirmed sender works here on same pc, tomorrow will test more
Scope, Android, Web, PC Plugins and Sounds:
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
Re: OSC Receiver and Sender
Not totally sure what you're looking to achieve, but perhaps you could try using broadcast addresses? See here for details: https://docs.microsoft.com/en-us/dotnet ... p-services
Re: OSC Receiver and Sender
Big progress on android app, core technology is set up and working!
Scope, Android, Web, PC Plugins and Sounds:
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
Re: OSC Receiver and Sender
Impressive.
Look forward to more controls for real time parameter modulation.
Look forward to more controls for real time parameter modulation.
Re: OSC Receiver and Sender
Scope, Android, Web, PC Plugins and Sounds:
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/
http://www.oceanswift.net
Music
https://faxinadu.bandcamp.com/